
40
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.
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.
•
Source port (MD) can be a VLAN, where the VLAN traffic received on that port pipe where its members are present is
monitored
•
Single MD can be monitored on max. of 4 MG ports.
Port Monitoring
Port monitoring is supported on both physical and logical interfaces, such as VLAN and port-channel interfaces. The source port
(MD) with monitored traffic and the destination ports (MG) to which an analyzer can be attached must be on the same switch. You
can configure up to 128 source ports in a monitoring session. Only one destination port is supported in a monitoring session. The
S4048–ON supports multiple source-destination statements in a single monitor session.
The maximum number of source ports that can be supported in a session is 128.
The maximum number of destination ports that can be supported is 4 per port pipe.
644
Port Monitoring
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...