Remote port monitoring
In remote port monitoring, the source port resides on a local interconnect module and the network analyzer port resides on a different switch.
A dedicated VLAN on all participating switches carries the mirrored traffic for each remote port monitoring session. The traffic from all the monitored ports on multiple interconnect modules is mirrored to a mirror-to port (MTP). As the mirrored traffic is sent to an external switch, the MTP must always be an uplink port. The capacity of the physical hardware determines the maximum number of sessions you can configure.
There are a maximum of four MTP quotas available for each logical interconnect. Therefore, maximum of four remote port monitoring sessions can be configured in one logical interconnect. Each session allocates an MTP quota for mirroring the Ethernet traffic in one direction, either ingress or egress. In a session, if Ethernet traffic is mirrored in both ingress and egress direction, two MTP quotas are used.
For example, consider remote port monitoring sessions A and B. Session A, uses one MTP quota to mirror Ethernet traffic in one direction, either ingress or egress. Session B, uses two MTP quotas to mirror Ethernet traffic in both directions— one MTP quota for ingress direction and another MTP quota for egress direction. Therefore, in one logical interconnect, session A and B together have consumed three MTP quotas.
- Connections
- Network sets
- Internal networks
- Private VLAN domains
- The uplink port used in a remote port monitoring session must not be a LAG member.
- Remote port monitoring is supported with HPE Virtual Connect SE 40Gb F8 Module for HPE Synergy and HPE Virtual Connect SE 100Gb F32 Module for HPE Synergy.
- Centralizes traffic analysis by mirroring the Ethernet traffic to network analyzers that are connected to remote switches.

