- Table of Contents
-
- H3C S12500R Ethernet Switch Router Series Config Examples-Release 36xx-6W100
- 01-Login Management Configuration Examples
- 02-RBAC Configuration Examples
- 03-Software Upgrade Examples
- 04-Ethernet Link Aggregation Configuration Examples
- 05-Port Isolation Configuration Examples
- 06-Spanning Tree Configuration Examples
- 07-VLAN Configuration Examples
- 08-VLAN Tagging Configuration Examples
- 09-DHCP Snooping Configuration Examples
- 10-Cross-Subnet Dynamic IP Address Allocation Configuration Examples
- 11-IPv6 over IPv4 Tunneling with OSPFv3 Configuration Examples
- 12-GRE Tunnel Configuration Examples
- 13-GRE with OSPF Configuration Examples
- 14-OSPF Configuration Examples
- 15-IS-IS Configuration Examples
- 16-BGP Configuration Examples
- 17-Policy-Based Routing Configuration Examples
- 18-OSPFv3 Configuration Examples
- 19-IPv6 IS-IS Configuration Examples
- 20-Routing Policy Configuration Examples
- 21-IGMP Snooping Configuration Examples
- 22-IGMP Configuration Examples
- 23-MLD Snooping Configuration Examples
- 24-Basic MPLS Configuration Examples
- 25-MPLS L3VPN Configuration Examples
- 26-ACL Configuration Examples
- 27-Control Plane-Based QoS Policy Configuration Examples
- 28-Traffic Policing Configuration Examples
- 29-GTS and Rate Limiting Configuration Examples
- 30-Priority Mapping and Queue Scheduling Configuration Examples
- 31-Traffic Filtering Configuration Examples
- 32-AAA Configuration Examples
- 33-SSH Configuration Examples
- 34-IP Source Guard Configuration Examples
- 35-Ethernet OAM Configuration Examples
- 36-CFD Configuration Examples
- 37-DLDP Configuration Examples
- 38-VRRP Configuration Examples
- 39-BFD Configuration Examples
- 40-NTP Configuration Examples
- 41-SNMP Configuration Examples
- 42-NQA Configuration Examples
- 43-Mirroring Configuration Examples
- 44-sFlow Configuration Examples
- 45-OpenFlow Configuration Examples
- 46-MAC Address Table Configuration Examples
- 47-Static Multicast MAC Address Entry Configuration Examples
- 48-IP Unnumbered Configuration Examples
- 49-Congestion Avoidance and Queue Scheduling Configuration Examples
- 50-Attack Protection Configuration Examples
- 51-Smart Link Configuration Examples
- 52-RRPP Configuration Examples
- 53-BGP Route Selection Configuration Examples
- 54-IS-IS Route Summarization Configuration Examples
- 55-MPLS OAM Configuration Examples
- 56-MPLS TE Configuration Examples
- 57-VXLAN Configuration Examples
- 58-NetStream Configuration Examples
- 59-EVPN-DCI over an MPLS L3VPN Network Configuration Examples
- 60-PTP Configuration Examples
- 61-S-MLAG Configuration Examples
- 62-MPLS SR Configuration Examples
- 63-Puppet Configuration Examples
- Related Documents
-
Title | Size | Download |
---|---|---|
43-Mirroring Configuration Examples | 1013.32 KB |
|
H3C S12500R Switch Router Series |
Mirroring Configuration Examples |
|
Copyright © 2021 New H3C Technologies Co., Ltd. All rights reserved. No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd. The information in this document is subject to change without notice.
|
Contents
Example: Configuring local port mirroring
Example: Configure Layer 2 remote port mirroring
Example: Configuring local flow mirroring
Example: Configuring flow mirroring in a flexible way
Introduction
This document provides configuration examples of port mirroring and flow mirroring.
Prerequisites
The configuration examples in this document were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.
This document assumes that you have basic knowledge of HP port mirroring and flow mirroring.
Example: Configuring local port mirroring
Network configuration
As shown in Figure 1, configure local port mirroring to monitor the Internet traffic and bidirectional traffic of the Marketing department and the Technical department.
Software versions used
This configuration example was created and verified on R3606.
Restrictions and guidelines
When you configure local port mirroring, follow these restrictions and guidelines:
· A local mirroring group takes effect only when you configure both source ports and the monitor port for the group. When you configure the monitor port, do not use a port of an existing mirroring group.
· Use a monitor port only for port mirroring, so the data monitoring device receives and analyzes only the mirrored traffic.
· For the correct operation of port mirroring, disable the spanning tree feature on the monitor port if it is a Layer 2 interface.
Procedures
# Assign IP address 10.1.1.1 to HundredGigE 3/0/1.
<DeviceA> system-view
[DeviceA] interface hundredgige 3/0/1
[DeviceA-HundredGigE3/0/1] ip address 10.1.1.1 24
[DeviceA-HundredGigE3/0/1] quit
# Assign IP addresses to HundredGigE 3/0/2 and HundredGigE 3/0/4 in the same way 10.1.1.1 is assigned to HundredGigE 3/0/1. (Details not shown.)
# Create local mirroring group 1.
[DeviceA] mirroring-group 1 local
# Configure HundredGigE 3/0/1 and HundredGigE 3/0/2 as the source ports of the mirroring group.
[DeviceA] mirroring-group 1 mirroring-port hundredgige 3/0/1 hundredgige 3/0/2 inbound
# Configure HundredGigE 3/0/3 as the monitor port of the mirroring group.
[DeviceA] mirroring-group 1 monitor-port hundredgige 3/0/3
Verifying the configuration
1. Display information about mirroring group 1 on Device A.
[DeviceA] display mirroring-group 1
Mirroring group 1:
Type: Local
Status: Active
Mirroring port: HundredGigE3/0/1 Inbound
HundredGigE3/0/2 Inbound
Monitor port: HundredGigE3/0/3
2. Use Wireshark for packet analysis:
# Ping 56.56.56.6 from a Technical department host (10.1.1.2). (Details not shown.)
# Use Wireshark on the data monitoring device to capture the ping packets.
Figure 2 Ping packet analysis in Wireshark
The analysis shows that the data monitoring device can monitor the packets sent from the Technical department.
Configuration files
#
mirroring-group 1 local
#
interface HundredGigE3/0/1
port link-mode route
ip address 10.1.1.1 255.255.255.0
mirroring-group 1 mirroring-port inbound
#
interface HundredGigE3/0/2
port link-mode route
ip address 12.1.1.1 255.255.255.0
mirroring-group 1 mirroring-port inbound
#
interface HundredGigE3/0/3
port link-mode route
mirroring-group 1 monitor-port
#
interface HundredGigE3/0/4
port link-mode route
ip address 56.56.56.5 255.255.255.0
#
Example: Configure Layer 2 remote port mirroring
Network configuration
As shown in Figure 3, configure Layer 2 remote port mirroring to monitor the outgoing traffic from the Technical department.
Analysis
To ensure correct forwarding of mirrored packets, assign the ports that connect intermediate devices to the source and destination devices to the remote probe VLAN.
Software versions used
This configuration example was created and verified on R3606.
Restrictions and guidelines
When you configure devices for remote port mirroring, configure them in the order of the destination device, the intermediate devices, and the source device.
When you configure the monitor port for the remote destination group on the destination device, follow these restrictions and guidelines:
· Do not use a port of an existing mirroring group.
· Use the monitor port only for port mirroring.
· For the correct operation of port mirroring, disable the spanning tree feature on the monitor port if it is a Layer 2 interface.
· For the monitor port to forward mirrored packets to the data monitoring device without VLAN tags, assign the monitor port to the remote probe VLAN as an access port.
When you configure the remote probe VLAN on the source and destination devices, follow these restrictions and guidelines:
· Use an existing static VLAN that is not in use.
· Use the remote probe VLAN for port mirroring exclusively.
· The remote mirroring groups on the source device and destination device must use the same remote probe VLAN. Use this VLAN only for the same remote mirroring group on the source device and destination device.
· Do not assign source ports of the remote source group to the remote probe VLAN.
· To ensure the operation of mirroring, do not enable any of the following features on the egress port:
¡ Spanning tree.
¡ IGMP snooping.
¡ Static ARP.
¡ MAC address learning.
· A port of an existing mirroring group cannot be configured as an egress port.
· A mirroring group contains only one egress port.
· To implement Layer 2 remote mirroring when the source ports are Layer 3 interfaces, you must use the egress port method.
Procedures
Configuring Device A (the destination device)
# Create VLANs 2 and 3.
<DeviceA> system-view
[DeviceA] vlan 2 to 3
# Create VLAN-interface 2 and assign an IP address to it.
[DeviceA] interface vlan-interface 2
[DeviceA-Vlan-interface2] ip address 10.1.1.1 24
[DeviceA-Vlan-interface2] quit
# Create VLAN-interface 3 and assign an IP address to it.
[DeviceA] interface vlan-interface 3
[DeviceA-Vlan-interface3] ip address 12.1.1.1 24
[DeviceA-Vlan-interface3] quit
# Configure HundredGigE 3/0/1 to operate in bridge mode, configure the port as a trunk port, and assign the port to VLANs 2, 3, and 5.
<DeviceA> system-view
[DeviceA] interface hundredgige 3/0/1
[DeviceA-HundredGigE3/0/1] port link-mode bridge
[DeviceA-HundredGigE3/0/1] port link-type trunk
[DeviceA-HundredGigE3/0/1] port trunk permit vlan 2 3 5
[DeviceA-HundredGigE3/0/1] quit
# Configure HundredGigE 3/0/2 to operate in bridge mode, configure the port as a trunk port, and assign the port to VLANs 2 and 5.
[DeviceA] interface hundredgige 3/0/2
[DeviceA-HundredGigE3/0/2] port link-mode bridge
[DeviceA-HundredGigE3/0/2] port link-type trunk
[DeviceA-HundredGigE3/0/2] port trunk permit vlan 2 5
[DeviceA-HundredGigE3/0/2] quit
# Create a remote destination group.
[DeviceA] mirroring-group 1 remote-destination
# Create VLAN 5.
[DeviceA] vlan 5
[DeviceA-vlan5] quit
# Configure VLAN 5 as the remote probe VLAN of the remote destination group.
[DeviceA] mirroring-group 1 remote-probe vlan 5
# Configure HundredGigE 3/0/3 as the monitor port of the remote destination group.
[DeviceA] mirroring-group 1 monitor-port hundredgige 3/0/3
# Configure HundredGigE 3/0/3 to operate in bridge mode, configure the port as an access port, and assign the port to the remote probe VLAN.
[DeviceA] interface hundredgige 3/0/3
[DeviceA-HundredGigE3/0/3] port link-mode bridge
[DeviceA-HundredGigE3/0/3] port access vlan 5
# Disable the spanning tree feature on HundredGigE 3/0/3.
[DeviceA-HundredGigE3/0/3] undo stp enable
[DeviceA-HundredGigE3/0/3] quit
Configuring Device B (the intermediate device)
# Create VLANs 2 and 3.
<DeviceB> system-view
[DeviceB] vlan 2 to 3
# Create VLAN 5.
[DeviceB] vlan 5
[DeviceB-vlan5] quit
# Configure HundredGigE 3/0/1 to operate in bridge mode, configure the port as a trunk port, and assign the port to VLANs 2, 3, and 5.
[DeviceB] interface hundredgige 3/0/1
[DeviceB-HundredGigE3/0/1] port link-mode bridge
[DeviceB-HundredGigE3/0/1] port link-type trunk
[DeviceB-HundredGigE3/0/1] port trunk permit vlan 2 3 5
[DeviceB-HundredGigE3/0/1] quit
# Configure HundredGigE 3/0/2 to operate in bridge mode, configure the port as a trunk port, and assign the port to VLANs 2, 3, and 5.
[DeviceB] interface hundredgige 3/0/2
[DeviceB-HundredGigE3/0/2] port link-mode bridge
[DeviceB-HundredGigE3/0/2] port link-type trunk
[DeviceB-HundredGigE3/0/2] port trunk permit vlan 2 3 5
[DeviceB-HundredGigE3/0/2] quit
Configuring Device C (the source device)
# Create VLANs 2 and 3.
<DeviceC> system-view
[DeviceC] vlan 2 to 3
# Configure HundredGigE 3/0/1 to operate in bridge mode, and assign the port to VLAN 2.
[DeviceC] interface hundredgige 3/0/1
[DeviceC-HundredGigE3/0/1] port link-mode bridge
[DeviceC-HundredGigE3/0/1] port access vlan 2
[DeviceC-HundredGigE3/0/1] quit
# Configure HundredGigE 3/0/2 to operate in bridge mode, and assign the port to VLAN 3.
[DeviceC] interface hundredgige 3/0/2
[DeviceC-HundredGigE3/0/2] port link-mode bridge
[DeviceC-HundredGigE3/0/2] port access vlan 3
[DeviceC-HundredGigE3/0/2] quit
# Create a remote source group.
[DeviceC] mirroring-group 1 remote-source
# Create VLAN 5.
[DeviceC] vlan 5
[DeviceC-vlan5] quit
# Configure VLAN 5 as the remote probe VLAN for the remote source group.
[DeviceC] mirroring-group 1 remote-probe vlan 5
# Configure HundredGigE 3/0/1 as the source port of the remote source group and the mirroring direction as inbound.
[DeviceC] mirroring-group 1 mirroring-port hundredgige 3/0/1 inbound
# Configure HundredGigE 3/0/3 as the egress port of the remote source group.
[DeviceC] mirroring-group 1 monitor-egress hundredgige 3/0/3
# Configure HundredGigE 3/0/3 to operate in bridge mode, configure the port as a trunk port, and assign the port to VLANs 2, 3, and 5.
[DeviceC] interface hundredgige 3/0/3
[DeviceC-HundredGigE3/0/3] port link-mode bridge
[DeviceC-HundredGigE3/0/3] port link-type trunk
[DeviceC-HundredGigE3/0/3] port trunk permit vlan 2 3 5
[DeviceC-HundredGigE3/0/3] quit
# Disable the spanning tree feature and MAC address learning on the egress port HundredGigE 3/0/3.
[DeviceC-HundredGigE3/0/3] undo stp enable
[DeviceC-HundredGigE3/0/3] undo mac-address mac-learning enable
[DeviceC-HundredGigE3/0/3] quit
Configuring Device D (the source device)
# Create VLAN 2.
<DeviceD> system-view
[DeviceD] vlan 2
[DeviceD-vlan2] quit
# Configure HundredGigE 3/0/1 to operate in bridge mode, and assign the port to VLAN 2.
[DeviceD] interface hundredgige 3/0/1
[DeviceD-HundredGigE3/0/1] port link-mode bridge
[DeviceD-HundredGigE3/0/1] port access vlan 2
[DeviceD-HundredGigE3/0/1] quit
# # Create remote source group 1.
[DeviceD] mirroring-group 1 remote-source
# Create VLAN 5.
[DeviceD] vlan 5
[DeviceD-vlan5] quit
# Configure VLAN 5 as the remote probe VLAN for the remote source group.
[DeviceD] mirroring-group 1 remote-probe vlan 5
# Configure HundredGigE 3/0/1 as the source port of the remote source group and the mirroring direction as inbound.
[DeviceD] mirroring-group 1 mirroring-port hundredgige 3/0/1 inbound
# Configure HundredGigE 3/0/2 as the egress port of the remote source group.
[DeviceD] mirroring-group 1 monitor-egress hundredgige 3/0/2
# Configure HundredGigE 3/0/2 to operate in bridge mode, configure the port as a trunk port, and assign the port to VLANs 2 and 5.
[DeviceD] interface hundredgige 3/0/2
[DeviceD-HundredGigE3/0/2] port link-mode bridge
[DeviceD-HundredGigE3/0/2] port link-type trunk
[DeviceD-HundredGigE3/0/2] port trunk permit vlan 2 5
# Disable the spanning tree feature and MAC address learning on the egress port HundredGigE 3/0/2.
[DeviceD-HundredGigE3/0/2] undo stp enable
[DeviceD-HundredGigE3/0/2] undo mac-address mac-learning enable
[DeviceD-HundredGigE3/0/2] quit
Verifying the configuration
1. Verify mirroring group configurations on devices:
# Display information about mirroring group 1 on Device C.
[DeviceC] display mirroring-group 1
Mirroring group 1:
Type: Remote source
Status: Active
Mirroring port: HundredGigE3/0/1 Inbound
Monitor egress port: HundredGigE3/0/3
Remote probe VLAN: 5
# Display information about mirroring group 1 on Device A.
[DeviceA] display mirroring-group 1
Mirroring group 1:
Type: Remote destination
Status: Active
Monitor port: HundredGigE3/0/3
Remote probe VLAN: 5
2. Use Wireshark for packet analysis:
# Ping a Marketing department host (12.1.1.2) from a Technical department host (10.1.1.2). (Details not shown.)
# Use Wireshark on the data monitoring device to capture the ping packets.
Figure 4 Ping packet analysis in Wireshark
The analysis shows that the data monitoring device can monitor the outgoing traffic from the Technical department.
Configuration files
· Device A:
#
mirroring-group 1 remote-destination
mirroring-group 1 remote-probe vlan 5
#
vlan 2 to 3
#
vlan 5
#
interface Vlan-interface2
ip address 10.1.1.1 255.255.255.0
#
interface Vlan-interface3
ip address 12.1.1.1 255.255.255.0
#
interface HundredGigE3/0/1
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 to 3 5
#
interface HundredGigE3/0/2
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 to 2 5
#
interface HundredGigE3/0/3
port link-mode bridge
port access vlan 5
undo stp enable
mirroring-group 1 monitor-port
#
· Device B:
#
vlan 2 to 3
#
vlan 5
#
interface HundredGigE3/0/1
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 to 3 5
#
interface HundredGigE3/0/2
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 to 3 5
#
· Device C:
#
mirroring-group 1 remote-source
mirroring-group 1 remote-probe vlan 5
#
vlan 2 to 3
#
vlan 5
#
interface HundredGigE3/0/1
port link-mode bridge
port access vlan 2
mirroring-group 1 mirroring-port inbound
#
interface HundredGigE3/0/2
port link-mode bridge
port access vlan 3
#
interface HundredGigE3/0/3
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 to 3 5
mirroring-group 1 monitor-egress
· Device D:
#
mirroring-group 1 remote-source
mirroring-group 1 remote-probe vlan 5
#
vlan 2
#
vlan 5
#
interface HundredGigE3/0/1
port link-mode bridge
port access vlan 2
mirroring-group 1 mirroring-port inbound
#
interface HundredGigE3/0/2
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 to 2 5
mirroring-group 1 monitor-egress
Example: Configuring local flow mirroring
Network configuration
As shown in Figure 5, configure local flow mirroring to mirror the following traffic:
· HTTP traffic from the Technical department.
· Packets that the Marketing department hosts receive from the public server cluster during non-working hours from 18:00 to 08:30 (the next day) on working days.
Analysis
To configure local flow mirroring, you must perform the following tasks on Device A:
· Define traffic classes and configure match criteria to classify packets to be mirrored.
· Configure traffic behaviors to mirror the matching packets to the port that connects to the data monitoring device.
Software versions used
This configuration example was created and verified on R3606.
Procedures
1. Assign IP addresses to interfaces on Device A:
# Assign IP address 35.35.35.5 to HundredGigE 3/0/1.
<DeviceA> system-view
[DeviceA] interface hundredgige 3/0/1
[DeviceA-HundredGigE3/0/1] port link-mode route
[DeviceA-HundredGigE3/0/1] ip address 35.35.35.5 24
[DeviceA-HundredGigE3/0/1] quit
# Assign IP address 56.56.56.5 to HundredGigE 3/0/3 in the same way 35.35.35.5 is assigned to HundredGigE 3/0/1. (Details not shown.)
2. Configure a QoS policy to mirror HTTP traffic from the Technical department:
# Create ACL 3000 and configure a rule to match packets from the Technical department to the Internet.
[DeviceA] acl advanced 3000
[DeviceA-acl-ipv4-adv-3000] rule permit tcp destination-port eq 80 source 10.1.1.0 0.0.0.255
[DeviceA-acl-ipv4-adv-3000] quit
# Create traffic class classifier_research, and configure the match criterion as ACL 3000.
[DeviceA] traffic classifier classifier_research
[DeviceA-classifier-classifier_research] if-match acl 3000
[DeviceA-classifier-classifier_research] quit
# Create traffic behavior behavior_research, and configure the action of mirroring traffic to HundredGigE 3/0/2.
[DeviceA] traffic behavior behavior_research
[DeviceA-behavior-behavior_research] mirror-to interface hundredgige 3/0/2
[DeviceA-behavior-behavior_research] quit
# Create QoS policy policy_research, and associate traffic class classifier_research with traffic behavior behavior_research in the QoS policy.
[DeviceA] qos policy policy_research
[DeviceA-qospolicy-policy_research] classifier classifier_research behavior behavior_research
[DeviceA-qospolicy-policy_research] quit
3. Configure a QoS policy to mirror traffic that the Marketing department hosts receive from the public server cluster:
# Create a periodic time range off-work1, setting it to be active between 0:00 and 8:30 during working days.
[DeviceA] time-range off-work1 0:00 to 8:30 working-day
# Create a periodic time range off-work2, setting it to be active between 18:00 and 24:00 during working days.
[DeviceA] time-range off-work2 18:00 to 24:00 working-day
# Create ACL 3001, and configure two rules to match packets from the public server cluster to the Marketing department hosts in non-working hours on working days.
[DeviceA] acl advanced 3001
[DeviceA-acl-ipv4-adv-3001] rule permit ip destination 12.1.1.0 0.0.0.255 source 14.1.1.0 0.0.0.255 time-range off-work1
[DeviceA-acl-ipv4-adv-3001] rule permit ip destination 12.1.1.0 0.0.0.255 source 14.1.1.0 0.0.0.255 time-range off-work2
[DeviceA-acl-ipv4-adv-3001] quit
# Create traffic class classifier_market, and configure the match criterion as ACL 3001.
[DeviceA] traffic classifier classifier_market
[DeviceA-classifier-classifier_market] if-match acl 3001
[DeviceA-classifier-classifier_market] quit
# Create traffic behavior behavior_market, and configure the action of mirroring traffic to HundredGigE 3/0/2.
[DeviceA] traffic behavior behavior_market
[DeviceA-behavior-behavior_market] mirror-to interface hundredgige 3/0/2
[DeviceA-behavior-behavior_market] quit
# Create QoS policy policy_market, and associate traffic class classifier_market with traffic behavior behavior_market in the QoS policy.
[DeviceA] qos policy policy_market
[DeviceA-qospolicy-policy_market] classifier classifier_market behavior behavior_market
[DeviceA-qospolicy-policy_market] quit
4. Apply the QoS policies:
# Apply QoS policy policy_research to the inbound direction of HundredGigE 3/0/1.
[DeviceA] interface hundredgige 3/0/1
[DeviceA-HundredGigE3/0/1] qos apply policy policy_research inbound
[DeviceA-HundredGigE3/0/1] quit
# Apply QoS policy policy_market to the inbound direction of HundredGigE 3/0/3.
[DeviceA] interface hundredgige 3/0/3
[DeviceA-HundredGigE3/0/3] qos apply policy policy_market inbound
[DeviceA-HundredGigE3/0/3] quit
Verifying the configuration
1. Display local flow mirroring information on Device A.
[DeviceA] display qos policy interface
Interface: HundredGigE3/0/1
Direction: Inbound
Policy: policy_research
Classifier: classifier_research
Operator: AND
Rule(s) :
If-match acl 3000
Behavior: behavior_research
Mirroring:
Mirror to the interface: HundredGigE3/0/2
Interface: HundredGigE3/0/3
Direction: Inbound
Policy: policy_market
Classifier: classifier_market
Operator: AND
Rule(s) :
If-match acl 3001
Behavior: behavior_market
Mirroring:
Mirror to the interface: HundredGigE3/0/2
2. Use Wireshark for packet analysis:
# Use a Technical department host (10.1.1.2) to access the IP address 46.46.46.4 and port 80 through Telnet. (Details not shown.)
# Use Wireshark on the data monitoring device to capture the packets.
Figure 6 HTTP traffic analysis in Wireshark
The analysis shows that the data monitoring device can monitor the HTTP traffic from the Technical department.
# On a non-working hour of a working day, ping a public server (14.1.1.2) from a Marketing department host (12.1.1.2). (Details not shown.)
# Use Wireshark on the data monitoring device to capture the ping packets.
Figure 7 Ping packet analysis in Wireshark
The analysis shows that the data monitoring device can monitor the traffic that the public server cluster send to the Marketing department during non-working hours on working days.
Configuration files
#
time-range off-work1 00:00 to 08:30 working-day
time-range off-work2 18:00 to 24:00 working-day
#
acl advanced 3000
rule 0 permit tcp source 10.1.1.0 0.0.0.255 destination-port eq www
acl advanced 3001
rule 0 permit ip source 14.1.1.0 0.0.0.255 destination 12.1.1.0 0.0.0.255 time-range off-work1
rule 5 permit ip source 14.1.1.0 0.0.0.255 destination 12.1.1.0 0.0.0.255 time-range off-work2
#
traffic classifier classifier_research operator and
if-match acl 3000
traffic classifier classifier_market operator and
if-match acl 3001
#
traffic behavior behavior_research
mirror-to interface HundredGigE3/0/2
traffic behavior behavior_market
mirror-to interface HundredGigE3/0/2
#
qos policy policy_research
classifier classifier_research behavior behavior_research
qos policy policy_market
classifier classifier_market behavior behavior_market
#
interface HundredGigE3/0/1
port link-mode route
ip address 35.35.35.5 255.255.255.0
qos apply policy policy_research inbound
#
interface HundredGigE3/0/3
port link-mode route
ip address 56.56.56.5 255.255.255.0
qos apply policy policy_market inbound
#
Example: Configuring flow mirroring in a flexible way
Network configuration
As shown in Figure 8, configure flow mirroring to monitor the network traffic by using the data monitoring devices as follows:
· On the data monitoring device connected to Device A:
¡ Monitor the traffic from public servers.
¡ Monitor the traffic from the file server only in the non-working hours (18:00 to 8:30 of the next day) on working days.
¡ Monitor the traffic from the Marketing department to the Internet, except the traffic from the Marketing department manager office to the Internet.
· On the data monitoring device connected to Device B:
¡ Monitor the traffic from the Technical department hosts and the server for external access.
¡ Monitor the outgoing traffic from the server in non-working hours (18:00 to 8:30 of the next day) on working days.
Analysis
To filter data from a specific source, use one of the following methods:
· Apply a QoS policy of denying traffic to the outgoing interface of the mirrored data. The data from the specified source is not received by the data monitoring device.
· Configure a class-behavior association to permit the data from the specified source, and then issue the class-behavior association before the class-behavior association for mirroring. Data from the specified source is not mirrored.
· Use the packet-filter command on the outgoing interface of the mirrored data. The data from the specified source is not received by the data monitoring device.
Software versions used
This configuration example was created and verified on R3606.
Procedures
Configuring Device A to mirror traffic from the public servers
1. Configure a QoS policy to mirror traffic from all public servers:
# Create ACL 2000 to match packets from subnet 14.1.1.0/24.
<DeviceA> system-view
[DeviceA] acl basic 2000
[DeviceA-acl-ipv4-basic-2000] rule permit source 14.1.1.0 0.0.0.255
[DeviceA-acl-ipv4-basic-2000] quit
# Create traffic class classifier_servers, and configure the match criterion as ACL 2000.
[DeviceA] traffic classifier classifier_servers
[DeviceA-classifier-classifier_servers] if-match acl 2000
[DeviceA-classifier-classifier_servers] quit
# Create traffic behavior behavior_servers, and configure the action of mirroring traffic to HundredGigE 3/0/3.
[DeviceA] traffic behavior behavior_servers
[DeviceA-behavior-behavior_servers] mirror-to interface hundredgige 3/0/3
[DeviceA-behavior-behavior_servers] quit
# Create QoS policy policy_servers, and associate traffic class classifier_servers with traffic behavior behavior_servers in the QoS policy.
[DeviceA] qos policy policy_servers
[DeviceA-qospolicy-policy_servers] classifier classifier_servers behavior behavior_servers
[DeviceA-qospolicy-policy_servers] quit
# Apply QoS policy policy_servers to the inbound direction of HundredGigE 3/0/4.
[DeviceA] interface hundredgige 3/0/4
[DeviceA-HundredGigE3/0/4] qos apply policy policy_servers inbound
[DeviceA-HundredGigE3/0/4] quit
2. Configure a QoS policy to filter packets from the file server in working hours:
# Create a periodic time range work-time, setting it to be active between 8:30 and 18:00 during working days.
[DeviceA] time-range work-time 8:30 to 18:00 working-day
# Create ACL 2001, and configure a rule to match packets from 14.1.1.10 in working hours on working days.
[DeviceA] acl basic 2001
[DeviceA-acl-ipv4-basic-2001] rule permit source 14.1.1.10 0.0.0.0 time-range work-time
[DeviceA-acl-ipv4-basic-2001] quit
# Create traffic class classifier_fileserver, and configure the match criterion as ACL 2001.
[DeviceA] traffic classifier classifier_fileserver
[DeviceA-classifier-classifier_fileserver] if-match acl 2001
[DeviceA-classifier-classifier_fileserver] quit
# Create traffic behavior behavior_fileserver, and configure the action of denying traffic.
[DeviceA] traffic behavior behavior_fileserver
[DeviceA-behavior-behavior_fileserver] filter deny
[DeviceA-behavior-behavior_fileserver] quit
# Create QoS policy policy_fileserver, and associate traffic class classifier_fileserver with traffic behavior behavior_fileserver in the QoS policy.
[DeviceA] qos policy policy_fileserver
[DeviceA-qospolicy-policy_fileserver] classifier classifier_fileserver behavior behavior_fileserver
[DeviceA-qospolicy-policy_fileserver] quit
# Apply QoS policy policy_fileserver to the outbound direction of HundredGigE 3/0/3.
[DeviceA] interface hundredgige 3/0/3
[DeviceA-HundredGigE3/0/3] qos apply policy policy_fileserver outbound
[DeviceA-HundredGigE3/0/3] quit
Configuring Device A to mirror the Internet traffic from the Marketing department
1. Create a traffic class and a traffic behavior for the packets:
# Create ACL 3000, and configure a rule to match packets from subnet 12.1.1.0/24.
[DeviceA] acl advanced 3000
[DeviceA-acl-ipv4-adv-3000] rule permit tcp destination-port eq 80 source 12.1.1.0 0.0.0.255
[DeviceA-acl-ipv4-adv-3000] quit
# Create traffic class classifier_market, and configure the match criterion as ACL 3000.
[DeviceA] traffic classifier classifier_market
[DeviceA-classifier-classifier_market] if-match acl 3000
[DeviceA-classifier-classifier_market] quit
# Create traffic behavior behavior_market, and configure the action of mirroring traffic to HundredGigE 3/0/3.
[DeviceA] traffic behavior behavior_market
[DeviceA-behavior-behavior_market] mirror-to interface hundredgige 3/0/3
[DeviceA-behavior-behavior_market] quit
2. Create a traffic class and a traffic behavior for the packets from the manager office:
# Create ACL 3001, and configure a rule to match packets from 12.1.1.100.
[DeviceA] acl advanced 3001
[DeviceA-acl-ipv4-adv-3001] rule permit tcp destination-port eq 80 source 12.1.1.100 0.0.0.0
[DeviceA-acl-ipv4-adv-3001] quit
# Create traffic class classifier_market_mgr, and configure the match criterion as ACL 3001.
[DeviceA] traffic classifier classifier_market_mgr
[DeviceA-classifier-classifier_market_mgr] if-match acl 3001
[DeviceA-classifier-classifier_market_mgr] quit
# Create traffic behavior behavior_market_mgr, and configure the action of permitting traffic to pass through.
[DeviceA] traffic behavior behavior_market_mgr
[DeviceA-behavior-behavior_market_mgr] filter permit
[DeviceA-behavior-behavior_market_mgr] quit
3. Create a QoS policy and associate the traffic classes and traffic behaviors:
# Create QoS policy policy_market.
[DeviceA] qos policy policy_market
# Associate traffic class classifier_market_mgr with traffic behavior behavior_market_mgr in the QoS policy.
[DeviceA-qospolicy-policy_market] classifier classifier_market_mgr behavior behavior_market_mgr
# Associate traffic class classifier_market with traffic behavior behavior_market in the QoS policy.
[DeviceA-qospolicy-policy_market] classifier classifier_market behavior behavior_market
# Display the sequence of issuing the class–behavior associations.
[DeviceA-qospolicy-policy_market] display this
#
qos policy policy_market
classifier classifier_market_mgr behavior behavior_market_mgr
classifier classifier_market behavior behavior_market
#
return
[DeviceA-qospolicy-policy_market] quit
The output shows that the class–behavior association for the manager office are issued first. The packets from the manager office to access the Internet are not mirrored.
4. Apply QoS policy policy_market to the inbound direction of HundredGigE 3/0/2.
[DeviceA] interface hundredgige 3/0/2
[DeviceA-HundredGigE3/0/2] qos apply policy policy_market inbound
[DeviceA-HundredGigE3/0/2] quit
Configuring Device B to mirror traffic from the Technical department
1. Configure local mirroring on Device B:
# Create local mirroring group 1.
<DeviceB> system-view
[DeviceB] mirroring-group 1 local
# Configure HundredGigE 3/0/1 to operate in bridge mode, and assign the port to VLAN 2.
[DeviceB] interface hundredgige3/0/1
[DeviceB-HundredGigE3/0/1] port link-mode bridge
[DeviceB-HundredGigE3/0/1] port access vlan 2
# Configure mirroring group 1 to monitor the incoming traffic of the port HundredGigE 3/0/1.
[DeviceB-HundredGigE3/0/1] mirroring-group 1 mirroring-port inbound
[DeviceB-HundredGigE3/0/1] quit
# Configure HundredGigE 3/0/2 as the monitor port of the mirroring group.
[DeviceB] mirroring-group 1 monitor-port hundredgige 3/0/2
# Configure HundredGigE 3/0/3 to operate in bridge mode, and assign the port to VLAN 2.
[DeviceB] interface hundredgige3/0/3
[DeviceB-HundredGigE3/0/3] port link-mode bridge
[DeviceB-HundredGigE3/0/3] port access vlan 2
[DeviceB-HundredGigE3/0/3] quit
2. Configure an ACL to filter the outgoing traffic from the server (10.1.1.2) in working hours:
# Create a periodic time range work-time, setting it to be active between 8:30 and 18:00 during working days.
[DeviceB] time-range work-time 8:30 to 18:00 working-day
# Create ACL 2000, and configure a rule to deny packets from 10.1.1.2 in working hours on working days.
[DeviceB] acl basic 2000
[DeviceB-acl-ipv4-basic-2000] rule deny source 10.1.1.2 0.0.0.0 time-range work-time
[DeviceB-acl-ipv4-basic-2000] quit
# Apply ACL 2000 to filter the outgoing traffic on HundredGigE 3/0/2.
[DeviceB] interface hundredgige3/0/2
[DeviceB-HundredGigE3/0/2] packet-filter 2000 outbound
[DeviceB-HundredGigE3/0/2] quit
Verifying the configuration
1. Verify flow mirroring configurations on devices:
# Display flow mirroring information on Device A.
[DeviceA] display qos policy interface
Interface: HundredGigE3/0/2
Direction: Inbound
Policy: policy_market
Classifier: classifier_market_mgr
Operator: AND
Rule(s) : If-match acl 3001
Behavior: behavior_market_mgr
Filter enable: Permit
Classifier: classifier_market
Operator: AND
Rule(s) : If-match acl 3000
Behavior: behavior_market
Mirroring:
Mirror to the interface: HundredGigE3/0/3
Interface: HundredGigE3/0/3
Direction: Outbound
Policy: policy_fileserver
Classifier: classifier_fileserver
Operator: AND
Rule(s) : If-match acl 2001
Behavior: behavior_fileserver
Mirroring:
Mirror to the interface: HundredGigE3/0/3
Interface: HundredGigE3/0/4
Direction: Inbound
Policy: policy_servers
Classifier: classifier_servers
Operator: AND
Rule(s) : If-match acl 2000
Behavior: behavior_servers
Mirroring:
Mirror to the interface: HundredGigE3/0/3
# Display information about mirroring group 1 on Device B.
[DeviceB] display mirroring-group 1
Mirroring group 1:
Type: Local
Status: Active
Mirroring port:
HundredGigE3/0/1 Inbound
Monitor port: HundredGigE3/0/2
2. Use Wireshark for packet analysis:
# Use a Marketing department host (12.1.1.2) and the manager's host (12.1.1.100) to access the IP address 57.57.57.7 and port 80 through Telnet. (Details not shown.)
# Use Wireshark on the data monitoring device connected to Device A to capture the packets.
Figure 9 HTTP traffic analysis in Wireshark
The analysis shows that the data monitoring device monitors the traffic only from the Marketing department host (12.1.1.2). The traffic from the manager office is not monitored.
Configuration files
· Device A:
#
time-range work-time 08:30 to 18:00 working-day
#
acl basic 2000
rule 0 permit source 14.1.1.0 0.0.0.255
acl basic 2001
rule 0 permit source 14.1.1.10 0 time-range work-time
#
acl advanced 3000
rule 0 permit tcp source 12.1.1.0 0.0.0.255 destination-port eq www
acl advanced 3001
rule 0 permit tcp source 12.1.1.100 0 destination-port eq www
#
traffic classifier classifier_servers operator and
if-match acl 2000
traffic classifier classifier_fileserver operator and
if-match acl 2001
traffic classifier classifier_market operator and
if-match acl 3000
traffic classifier classifier_market_mgr operator and
if-match acl 3001
#
traffic behavior behavior_servers
mirror-to interface HundredGigE3/0/3
traffic behavior behavior_fileserver
filter deny
traffic behavior behavior_market
mirror-to interface HundredGigE3/0/3
traffic behavior behavior_market_mgr
filter permit
#
qos policy policy_fileserver
classifier classifier_fileserver behavior behavior_fileserver
qos policy policy_market
classifier classifier_market_mgr behavior behavior_market_mgr
classifier classifier_market behavior behavior_market
qos policy policy_servers
classifier classifier_servers behavior behavior_servers
#
interface HundredGigE3/0/1
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 to 2
#
interface HundredGigE3/0/2
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 3
qos apply policy policy_market inbound
#
interface HundredGigE3/0/3
port link-mode route
qos apply policy policy_fileserver outbound
#
interface HundredGigE3/0/4
port link-mode route
ip address 57.57.57.5 255.255.255.0
qos apply policy policy_servers inbound
#
· Device B:
#
mirroring-group 1 local
#
time-range work-time 08:30 to 18:00 working-day
#
acl basic 2000
rule 0 deny source 10.1.1.2 0 time-range work-time
#
interface HundredGigE3/0/1
port link-mode bridge
port access vlan 2
mirroring-group 1 mirroring-port inbound
#
interface HundredGigE3/0/2
port link-mode route
packet-filter 2000 outbound
mirroring-group 1 monitor-port
#
interface HundredGigE3/0/3
port link-mode bridge
port access vlan 2
#
Related documentation
· H3C S12500R Switch Router Series Network Management and Monitoring Command Reference-R3606
· H3C S12500R Switch Router Series Network Management and Monitoring Configuration Guide-R3606