why the l2protocol statistics is not showing the lacp input/output packet

yjhd · Created Dec 26, 2018 09:00:23

The l2protocol-tunnel group-mac command enables the switch to replace the multicast destination MAC address of Layer 2 protocol packets with a specified multicast MAC address.

GongXiaochuan · Created Dec 28, 2018 02:57:18

link aggregation applies to various methods of combining (aggregating) multiple network connections in parallel in order to increase throughput beyond what a single connection could sustain, and to provide redundancy in case one of the links should fail

Finn92 · Created Dec 29, 2018 02:41:30

Layer 2 protocols running between user networks, such as MSTP, LACP, and HGMP, must traverse a backbone network to perform Layer 2 protocol calculation.

Generally, the destination MAC addresses in Layer 2 protocol packets of the same Layer 2 protocol are the same. For example, the MSTP PDUs are BPDUs with the destination MAC address 0180-C200-0000. Therefore, when a Layer 2 protocol packet reaches an edge device on a backbone network, the edge device cannot identify whether the Layer 2 protocol packet comes from a user network or the backbone network and sends the Layer 2 protocol packet to the CPU to calculate a spanning tree. As a result, the user network devices calculate a spanning tree with backbone network edge devices but not with user network devices.

SupperRobin · Created Dec 29, 2018 07:42:38

Multiple tenants in data centers need to be isolated, but switches cannot implement refined isolation. Therefore, MUX VLAN applies only to office networks of small enterprises, but does not to multi-tenant scenarios in large data centers.

why the l2protocol statistics is not showing the lacp input/output packet

Third Party’s Trade Secret

My Followers

Enterprise

Consumer

Corporate

Carriers

why the l2protocol statistics is not showing the lacp input/output packet

Third Party’s Trade Secret

My Followers