Clear Port Mirroring; Link Aggregation Control Protocol (Lacp) - Enterasys SecureStack C2 Configuration Manual

clear port mirroring

Usage
Note that LAG ports and their underlying physical ports, as described in "Link Aggregation
Control Protocol (LACP)" on page 5‐32, cannot be mirrored.
Example
This example shows how to create and enable port mirroring with
.1.11 as the target port:
ge
C2(su)->set port mirroring create ge.1.4 ge.1.11
C2(su)->set port mirroring enable ge.1.4 ge.1.11
clear port mirroring
Use this command to clear a port mirroring relationship.
Syntax
clear port mirroring source destination
Parameters
source
destination
Defaults
None.
Mode
Switch command, read‐write.
Example
This example shows how to clear port mirroring between source port
.1.11:
ge
C2(su)->clear port mirroring ge.1.4 ge.1.11

Link Aggregation Control Protocol (LACP)

Using multiple links simultaneously to increase bandwidth is a desirable switch feature, which
can be accomplished if both sides agree on a set of ports that are being used as a Link Aggregation
Group (LAG). Once a LAG is formed from selected ports, problems with looping can be avoided
since the Spanning Tree can treat this LAG as a single port.
Enabled by default, the Link Aggregation Control Protocol (LACP) logically groups interfaces
together to create a greater bandwidth uplink, or link aggregation, according to the IEEE 802.3ad
standard. This standard allows the switch to determine which ports are in LAGs and configure
5-32 Port Configuration
Specifies the source port of the mirroring configuration to be cleared. For
a detailed description of possible port‐string values, refer to "Port String
Syntax Used in the CLI" on page 5‐2.
Specifies the target port of the mirroring configuration to be cleared.
Caution: Link aggregation configuration should only be performed by personnel who are
knowledgeable about Spanning Tree and Link Aggregation, and fully understand the ramifications
of modifications beyond device defaults. Otherwise, the proper operation of the network could be
at risk.
.1.4 as the source port, and
ge
.1.4 and target port
ge