Port Monitoring
Port monitoring (also referred to as mirroring ) allows you to monitor ingress and/or egress traffic on specified ports. The mirrored traffic
can be sent to a port to which a network analyzer is connected to inspect or troubleshoot the traffic.
Mirroring is used for monitoring Ingress or Egress or both Ingress and Egress traffic on a specific port(s). This mirrored traffic can be sent
to a port where a network sniffer can connect and monitor the traffic.
Dell Networking OS supports the following mirroring techniques:
•
Port-Mirroring — Port Monitoring is a method of monitoring network traffic that forwards a copy of each incoming and outgoing
packet from one port of a network router to another port where the packet can be studied.
•
Remote Port Monitoring (RPM) — Remote Port Monitoring allows the user to monitor traffic running across a remote device in the
same network. Here the mirror traffic is carried over the L2 network, so that probe devices in the network can analyze it. It is an
extension to the normal Port Monitoring feature. This feature is generally referred as RPM, where mirror traffic is carried over L2
network.
•
Encapsulated Remote-Port Monitoring (ERPM) — ERPM is a feature to encapsulate mirrored packet using GRE with IP delivery so
that it can be sent across a routed network.
Topics:
•
•
•
•
Configuring Monitor Multicast Queue
•
Enabling Flow-Based Monitoring
•
•
Encapsulated Remote Port Monitoring
•
ERPM Behavior on a typical Dell Networking OS
•
Important Points to Remember
•
Port Monitoring is supported on both physical and logical interfaces like virtual area network (VLAN) and port-channel.
•
The monitored (the source, [MD]) and monitoring ports (the destination, [MG]) must be on the same switch.
•
In general, a monitoring port should have no ip address and no shutdown as the only configuration; Dell Networking OS permits a limited
set of commands for monitoring ports. You can display these commands using the
?
command. A monitoring port also may not be a
member of a VLAN.
•
There may only be one destination port (MG) in a monitoring session.
•
Source port (MD) can be monitored by more than one destination port (MG).
•
Destination port (MG) can be a physical interface or port-channel interface.
•
A Port monitoring session can have multiple source statements.
•
Range command is supported in the source statement, where we can specify a range of interfaces of (Physical, Port Channel or VLAN)
types.
•
One Destination Port (MG) can be used in multiple sessions.
•
There can be a maximum of 128 source ports in a Port Monitoring session.
•
Flow based monitoring is supported for all type of source interfaces.
40
Port Monitoring
693
Содержание S4048T-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 11 2 1 ...
Страница 148: ...Figure 10 BFD Three Way Handshake State Changes 148 Bidirectional Forwarding Detection BFD ...
Страница 251: ...Dell Control Plane Policing CoPP 251 ...
Страница 363: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 363 ...
Страница 511: ...Figure 64 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 511 ...
Страница 512: ...Figure 65 Inspecting Configuration of LAG 10 on ALPHA 512 Link Aggregation Control Protocol LACP ...
Страница 515: ...Figure 67 Inspecting a LAG Port on BRAVO Using the show interface Command Link Aggregation Control Protocol LACP 515 ...
Страница 516: ...Figure 68 Inspecting LAG 10 Using the show interfaces port channel Command 516 Link Aggregation Control Protocol LACP ...
Страница 558: ...Figure 84 Configuring Interfaces for MSDP 558 Multicast Source Discovery Protocol MSDP ...
Страница 559: ...Figure 85 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 559 ...
Страница 560: ...Figure 86 Configuring PIM in Multiple Routing Domains 560 Multicast Source Discovery Protocol MSDP ...
Страница 564: ...Figure 88 MSDP Default Peer Scenario 2 564 Multicast Source Discovery Protocol MSDP ...
Страница 565: ...Figure 89 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 565 ...
Страница 729: ...protocol spanning tree pvst no disable vlan 300 bridge priority 4096 Per VLAN Spanning Tree Plus PVST 729 ...
Страница 841: ...Figure 115 Single and Double Tag TPID Match Service Provider Bridging 841 ...
Страница 842: ...Figure 116 Single and Double Tag First byte TPID Match 842 Service Provider Bridging ...