White Papers

tagged TenGigabitEthernet 0/1-3
mac access-group flow in
shutdown
Dell#
The following example shows you how to congures a source as a physical interface only for ERPM.
Dell(conf)#monitor session 3 type erpm
Dell(conf-mon-sess-3)#)source vlan 100 dir rx
Dell(conf-mon-sess-3)# erpm source-ip 1.1.1.1 dest-ip 100.1.1.2
Dell(conf-mon-sess-3)# flow-based enable
Dell(conf-mon-sess-3)# no disable
The following example congures the port extender ports so that they are tagged and untagged members of VLAN 100. With regard to the
source as a VLAN, the supported direction of mirroring is rx only. You must also apply an access list to the VLAN with the rules that match
with the keyword “monitor”.
Dell(config-ext-macl)#do sh run mac
!
mac access-list extended test
seq 10 permit any any count monitor
Dell(config-ext-macl)#
Dell(config-ext-macl)#do sh run int vlan 100
!
interface Vlan 100
no ip address
tagged peGigE 3/0/1
mac access-group test in
shutdown
Dell(config-ext-macl)#
Port Monitoring on VLT
Devices on which VLT is congured are seen as a single device in the network. You can apply port monitoring function on the VLT devices
in the network.
Port monitoring enables ingress or egress trac traversing on a port to be sent to another port so that the trac can be analyzed. The
port to which trac is sent for analysis is called the mirroring port. This port is connect to a port analyzer, which performs the trac
analysis function.
Depending up on the location of the port to which the port analyzer is connected, port monitoring is classied into three categories: local
Port mirroring, remote port mirroring (RPM), and encapsulated remote port mirroring (ERPM).
NOTE
: For more information on port monitoring, see Port Monitoring.
The port monitoring or mirroring function when applied to VLT devices works as expected except with some restrictions. You can congure
RPM or ERPM monitoring between two VLT peers. As VLT devices are seen as a single device in the network, when a fail over occurs, the
source or destination port on one of the VLT peers becomes inactive causing the monitoring session to fail. As a result, Dell Networking OS
does not allow local Port mirroring based monitoring to be congured between VLT peers. However, you can create local Port mirroring
monitoring sessions separately on individual devices that are a part of the VLT conguration.
NOTE
: For more information on conguring VLT, see Conguring
VLT.
VLT Non-fail over Scenario
Consider a scenario where port monitoring is congured to mirror trac on a VLT device's port or LAG to a destination port on some other
device (TOR) on the network. When there is no fail over to the VLT peer, the VLTi link (ICL LAG) also receives the mirrored trac as the
786
Port Monitoring