Contents

Introduction· 1

Prerequisites· 1

Example: Configuring traffic monitoring and backup· 1

Network configuration· 1

Analysis· 2

Applicable hardware and software versions· 2

Procedures· 2

Verifying the configuration· 3

Configuration files· 4

Example: Configuring traffic monitoring and backup· 5

Network configuration· 5

Analysis· 5

Applicable hardware and software versions· 5

Procedures· 6

Verifying the configuration· 7

Configuration files· 8

Example: Configuring traffic monitoring and backup· 8

Network configuration· 8

Applicable hardware and software versions· 9

Procedures· 10

Verifying the configuration· 11

Configuration files· 12

Example: Configuring traffic monitoring and backup· 13

Network configuration· 13

Applicable hardware and software versions· 13

Procedures· 14

Verifying the configuration· 15

Configuration files· 16

 

Introduction

The test access point (TAP) feature can copy and forward traffic in real time without interrupting the traffic. Specifically, it copies traffic and sends a copy of the traffic to each of multiple monitoring devices for Internet access behavior analysis, abnormal traffic monitoring, and application monitoring

This document provides examples for configuring TAP.

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 TAP.

Example: Configuring traffic monitoring and backup

Network configuration

As shown in Figure 1, configure TAP on the device to meet the following requirements:

·     Add an outer VLAN tag to all traffic.

·     Configure basic M:N copying to send each packet to both Server A (for analysis) and Server B (for backup).

Figure 1 Network diagram

 

Analysis

Configure a TAP policy to add VLAN ID 4094 to all packets and to copy the traffic on the input interfaces to both Server A and Server B.

Applicable hardware and software versions

The following matrix shows the hardware and software versions to which this configuration example is applicable:

 

Hardware	Software version
S9850-G switch series	Not supported
S6850-G switch series S6805-G switch series	Not supported
S6530X switch series	Release 8108P22 and later
S5590-HI switch series	Not supported
S5590-EI switch series S5500V3-HI switch series	Not supported
S6520X-EI-G switch series S6520XP-EI-G switch series	Release 7748 and later
S5590XP-HI-G switch series	Not supported
S5560-EI-G switch series	Release 7748 and later
S5130S-EI-G switch series	Release 7748 and later
S5500-D-G switch series S5100-D-G switch series	Not supported
S5130S-HI-G switch series	Not supported
S5130S-EI-G switch series (except S5130S-30C-EI-G and S5130S-54C-EI-G switches)	Not supported
S5130S-30C-EI-G switch S5130S-54C-EI-G switch	Release 7748 and later

 

Procedures

# Create monitoring group 1, and assign GigabitEthernet 1/0/4 and GigabitEthernet 1/0/5 to the monitoring group.

[DeviceB] monitoring-group 1

[DeviceB-monitoring-group-1] monitoring-port gigabitethernet 1/0/4 to gigabitethernet 1/0/5

[DeviceB-monitoring-group-1] quit

# Create a traffic class named classifier_tap, and configure the traffic class to match all packets.

[DeviceB] traffic classifier classifier_tap

[DeviceB-classifier-classifier_tap] if-match any

[DeviceB-classifier-classifier_tap] quit

# Create a traffic behavior named behavior_tap, and configure an action of adding an outer VLAN tag and an action of redirecting packets to monitoring group 1.

[DeviceB] traffic behavior behavior_tap

[DeviceB-behavior-behavior_tap] nest top-most vlan 4094

[DeviceB-behavior-behavior_tap] redirect monitoring-group 1

[DeviceB-behavior-behavior_tap] quit

# Create a TAP policy named policy_tap, and associate the traffic class with the traffic behavior in the TAP policy.

[DeviceB] qos tap policy policy_tap

[DeviceB-qospolicy-policy_tap] classifier classifier_tap behavior behavior_tap

[DeviceB-qospolicy-policy_tap] quit

# Applying the TAP policy to the inbound direction of GigabitEthernet 1/0/1.

[DeviceB] interface gigabitethernet 1/0/1

[DeviceB-GigabitEthernet1/0/1] qos apply tap policy policy_tap inbound

[DeviceB-GigabitEthernet1/0/1] quit

# Applying the TAP policy to the inbound direction of GigabitEthernet 1/0/2.

[DeviceB] interface gigabitethernet 1/0/2

[DeviceB-GigabitEthernet1/0/2] qos apply tap policy policy_tap inbound

[DeviceB-GigabitEthernet1/0/2] quit

# Applying the TAP policy to the inbound direction of GigabitEthernet 1/0/3.

[DeviceB] interface gigabitethernet 1/0/3

[DeviceB-GigabitEthernet1/0/3] qos apply tap policy policy_tap inbound

[DeviceB-GigabitEthernet1/0/3] quit

Verifying the configuration

# Display TAP policies applied to interfaces.

[DeviceB] display qos tap policy interface

Interface: GigabitEthernet1/0/1

  Direction: Inbound

  Tap policy: policy_tap

 

   Classifier: classifier_tap

     Operator: AND

     Rule(s) :

      If-match any

     Behavior: behavior_tap

      Nesting:

        Nest top-most vlan-id 4094

      Redirecting:

        Redirect to the monitoring group: 1

 

Interface: GigabitEthernet1/0/2

  Direction: Inbound

  Tap policy: policy_tap

 

   Classifier: classifier_tap

     Operator: AND

     Rule(s) :

      If-match any

     Behavior: behavior_tap

      Nesting:

        Nest top-most vlan-id 4094

      Redirecting:

        Redirect to the monitoring group: 1

 

Interface: GigabitEthernet1/0/3

  Direction: Inbound

  Tap policy: policy_tap

 

   Classifier: classifier_tap

     Operator: AND

     Rule(s) :

      If-match any

     Behavior: behavior_tap

      Nesting:

        Nest top-most vlan-id 4094

      Redirecting:

        Redirect to the monitoring group: 1

Configuration files

#

monitoring-group 1

monitoring-port GigabitEthernet1/0/4

monitoring-port GigabitEthernet1/0/5

#

traffic classifier classifier_tap operator and

if-match any

#

traffic behavior behavior_tap

nest top-most vlan 4094

redirect monitoring-group 1

#

qos tap policy policy_tap

classifier classifier_tap behavior behavior_tap

#

interface GigabitEthernet1/0/1

qos apply tap policy policy_tap inbound

#

interface GigabitEthernet1/0/2

qos apply tap policy policy_tap inbound

#

interface GigabitEthernet1/0/3

qos apply tap policy policy_tap inbound

#

Example: Configuring traffic monitoring and backup

Network configuration

As shown in Figure 2, configure TAP on the device to meet the following requirements:

·     Add an outer VLAN tag to all traffic.

·     Configure basic M:N copying to send each packet to both Server A (for analysis) and Server B (for backup).

Figure 2 Network diagram

 

Analysis

Configure a TAP policy to add VLAN ID 4094 to all packets and to copy the traffic on the input interfaces to both Server A and Server B.

Applicable hardware and software versions

The following matrix shows the hardware and software versions to which this configuration example is applicable:

 

Hardware	Software version
S9850-G switch series	Not supported
S6850-G switch series S6805-G switch series	Not supported
S6530X switch series	Release 8108P22 and later
S5590-HI switch series	Not supported
S5590-EI switch series S5500V3-HI switch series	Not supported
S6520X-EI-G switch series S6520XP-EI-G switch series	Release 7748 and later
S5590XP-HI-G switch series	Not supported
S5560-EI-G switch series	Release 7748 and later
S5130S-EI-G switch series	Release 7748 and later
S5500-D-G switch series S5100-D-G switch series	Not supported
S5130S-HI-G switch series	Not supported
S5130S-EI-G switch series (except S5130S-30C-EI-G and S5130S-54C-EI-G switches)	Not supported
S5130S-30C-EI-G switch S5130S-54C-EI-G switch	Release 7748 and later

 

Procedures

# Create monitoring group 1, and assign Ten-GigabitEthernet 1/0/4 and Ten-GigabitEthernet 1/0/5 to the monitoring group.

[DeviceB] monitoring-group 1

[DeviceB-monitoring-group-1] monitoring-port ten-gigabitethernet 1/0/4 to ten-gigabitethernet 1/0/5

[DeviceB-monitoring-group-1] quit

# Create a traffic class named classifier_tap, and configure the traffic class to match all packets.

[DeviceB] traffic classifier classifier_tap

[DeviceB-classifier-classifier_tap] if-match any

[DeviceB-classifier-classifier_tap] quit

# Create a traffic behavior named behavior_tap, and configure an action of adding an outer VLAN tag and an action of redirecting packets to monitoring group 1.

[DeviceB] traffic behavior behavior_tap

[DeviceB-behavior-behavior_tap] nest top-most vlan 4094

[DeviceB-behavior-behavior_tap] redirect monitoring-group 1

[DeviceB-behavior-behavior_tap] quit

# Create a TAP policy named policy_tap, and associate the traffic class with the traffic behavior in the TAP policy.

[DeviceB] qos tap policy policy_tap

[DeviceB-qospolicy-policy_tap] classifier classifier_tap behavior behavior_tap

[DeviceB-qospolicy-policy_tap] quit

# Applying the TAP policy to the inbound direction of Ten-GigabitEthernet 1/0/1.

[DeviceB] interface ten-gigabitethernet 1/0/1

[DeviceB-Ten-GigabitEthernet1/0/1] qos apply tap policy policy_tap inbound

[DeviceB-Ten-GigabitEthernet1/0/1] quit

# Applying the TAP policy to the inbound direction of Ten-GigabitEthernet 1/0/2.

[DeviceB] interface ten-gigabitethernet 1/0/2

[DeviceB-Ten-GigabitEthernet1/0/2] qos apply tap policy policy_tap inbound

[DeviceB-Ten-GigabitEthernet1/0/2] quit

# Applying the TAP policy to the inbound direction of Ten-GigabitEthernet 1/0/3.

[DeviceB] interface ten-gigabitethernet 1/0/3

[DeviceB-Ten-GigabitEthernet1/0/3] qos apply tap policy policy_tap inbound

[DeviceB-Ten-GigabitEthernet1/0/3] quit

 

Verifying the configuration

# Display TAP policies applied to interfaces.

[DeviceB] display qos tap policy interface

Interface: Ten-GigabitEthernet1/0/1

  Direction: Inbound

  Tap policy: policy_tap

 

   Classifier: classifier_tap

     Operator: AND

     Rule(s) :

      If-match any

     Behavior: behavior_tap

      Nesting:

        Nest top-most vlan-id 4094

      Redirecting:

        Redirect to the monitoring group: 1

 

Interface: Ten-GigabitEthernet1/0/2

  Direction: Inbound

  Tap policy: policy_tap

 

   Classifier: classifier_tap

     Operator: AND

     Rule(s) :

      If-match any

     Behavior: behavior_tap

      Nesting:

        Nest top-most vlan-id 4094

      Redirecting:

        Redirect to the monitoring group: 1

 

Interface: Ten-GigabitEthernet1/0/3

  Direction: Inbound

  Tap policy: policy_tap

 

   Classifier: classifier_tap

     Operator: AND

     Rule(s) :

      If-match any

     Behavior: behavior_tap

      Nesting:

        Nest top-most vlan-id 4094

      Redirecting:

        Redirect to the monitoring group: 1

Configuration files

#

monitoring-group 1

monitoring-port Ten-GigabitEthernet1/0/4

monitoring-port Ten-GigabitEthernet1/0/5

#

traffic classifier classifier_tap operator and

if-match any

#

traffic behavior behavior_tap

nest top-most vlan 4094

redirect monitoring-group 1

#

qos tap policy policy_tap

classifier classifier_tap behavior behavior_tap

#

interface Ten-GigabitEthernet1/0/1

qos apply tap policy policy_tap inbound

#

interface Ten-GigabitEthernet1/0/2

qos apply tap policy policy_tap inbound

#

interface Ten-GigabitEthernet1/0/3

qos apply tap policy policy_tap inbound

#

Example: Configuring traffic monitoring and backup

Network configuration

As shown in Figure 3, configure M:N copying and link aggregation load sharing on Device B to meet the following requirements:

·     Incoming packets on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 are redirected to the aggregate interface.

·     The aggregate interface load shares packets based on source IP addresses and destination IP addresses.

·     The aggregate interface sends incoming packets on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to Device D over the same link by using algorithm 1 as the link aggregation load sharing algorithm.

Figure 3 Network diagram

 

Applicable hardware and software versions

The following matrix shows the hardware and software versions to which this configuration example is applicable:

 

Hardware	Software version
S9850-G switch series	Not supported
S6850-G switch series S6805-G switch series	Not supported
S6530X switch series	Release 8108P22 and later
S5590-HI switch series	Not supported
S5590-EI switch series S5500V3-HI switch series	Not supported
S6520X-EI-G switch series S6520XP-EI-G switch series	Release 7748 and later
S5590XP-HI-G switch series	Not supported
S5560-EI-G switch series	Release 7748 and later
S5130S-EI-G switch series	Release 7748 and later
S5500-D-G switch series S5100-D-G switch series	Not supported
S5130S-HI-G switch series	Not supported
S5130S-EI-G switch series (except S5130S-30C-EI-G and S5130S-54C-EI-G switches)	Not supported
S5130S-30C-EI-G switch S5130S-54C-EI-G switch	Release 7748 and later

 

Procedures

# Create a Layer 2 aggregate interface named Bridge-Aggregation 1.

<DeviceB> system-view

[DeviceB] interface Bridge-Aggregation 1

[DeviceB-Bridge-Aggregation1] quit

# Assign GigabitEthernet 1/0/4, GigabitEthernet 1/0/5, and GigabitEthernet 1/0/6 to the aggregation group.

[DeviceB] interface gigabitethernet1/0/4

[DeviceB-GigabitEthernet1/0/4] port link-aggregation group 1

[DeviceB-GigabitEthernet1/0/4] quit

[DeviceB] interface gigabitethernet1/0/5

[DeviceB-GigabitEthernet1/0/5] port link-aggregation group 1

[DeviceB-GigabitEthernet1/0/5] quit

[DeviceB] interface gigabitethernet1/0/6

[DeviceB-GigabitEthernet1/0/6] port link-aggregation group 1

[DeviceB-GigabitEthernet1/0/6] quit

# Create monitoring group 1, and assign the Layer 2 aggregate interface to the monitoring group.

[DeviceB] monitoring-group 1

[DeviceB-monitoring-group-1] monitoring-port bridge-aggregation 1

[DeviceB-monitoring-group-1] quit

# Create a traffic class named classifier_tap, and configure the traffic class to match all packets.

[DeviceB] traffic classifier classifier_tap

[DeviceB-classifier-classifier_tap] if-match any

[DeviceB-classifier-classifier_tap] quit

# Create a traffic behavior named behavior_tap, and configure an action of redirecting packets to monitoring group 1.

[DeviceB] traffic behavior behavior_tap

[DeviceB-behavior-behavior_tap] redirect monitoring-group 1

[DeviceB-behavior-behavior_tap] quit

# Create a TAP policy named policy_tap, and associate the traffic class with the traffic behavior in the TAP policy.

[DeviceB] qos tap policy policy_tap

[DeviceB-qospolicy-policy_tap] classifier classifier_tap behavior behavior_tap

[DeviceB-qospolicy-policy_tap] quit

# Applying the TAP policy to the inbound direction of GigabitEthernet 1/0/1.

[DeviceB] interface gigabitethernet 1/0/1

[DeviceB-GigabitEthernet1/0/1] qos apply tap policy policy_tap inbound

[DeviceB-GigabitEthernet1/0/1] quit

# Applying the TAP policy to the inbound direction of GigabitEthernet 1/0/2.

[DeviceB] interface gigabitethernet 1/0/2

[DeviceB-GigabitEthernet1/0/2] qos apply tap policy policy_tap inbound

[DeviceB-GigabitEthernet1/0/2] quit

# Applying the TAP policy to the inbound direction of GigabitEthernet 1/0/3.

[DeviceB] interface gigabitethernet 1/0/3

[DeviceB-GigabitEthernet1/0/3] qos apply tap policy policy_tap inbound

[DeviceB-GigabitEthernet1/0/3] quit

# Set the global load sharing mode to load share packets based on source IP addresses and destination IP addresses.

[DeviceB] link-aggregation global load-sharing mode source-ip destination-ip

# Specify algorithm 1 as the link aggregation load sharing algorithm.

[DeviceB] link-aggregation global load-sharing algorithm 1

Verifying the configuration

# Display TAP policies applied to interfaces.

[DeviceB] display qos tap policy interface

Interface: GigabitEthernet1/0/1

  Direction: Inbound

  Tap policy: policy_tap

 

   Classifier: classifier_tap

     Operator: AND

     Rule(s) :

      If-match any

     Behavior: behavior_tap

      Redirecting:

        Redirect to the monitoring group: 1

Interface: GigabitEthernet1/0/2

  Direction: Inbound

  Tap policy: policy_tap

 

   Classifier: classifier_tap

     Operator: AND

     Rule(s) :

      If-match any

     Behavior: behavior_tap

      Redirecting:

        Redirect to the monitoring group: 1

Interface: GigabitEthernet1/0/3

  Direction: Inbound

  Tap policy: policy_tap

 

   Classifier: classifier_tap

     Operator: AND

     Rule(s) :

      If-match any

     Behavior: behavior_tap

      Redirecting:

        Redirect to the monitoring group: 1

# Display monitoring groups.

[DeviceB] display monitoring-group all

Monitoring group 1:

  Monitoring ports: Bridge-Aggregation1

# Display the load sharing mode.

[DeviceB] display link-aggregation load-sharing mode

Link-aggregation load-sharing algorithm:1

Link-aggregation load-sharing mode:

destination-ip address, source-ip address

Configuration files

#

 link-aggregation global load-sharing mode destination-ip source-ip

 link-aggregation global load-sharing algorithm 1

#

monitoring-group 1

 monitoring-port Bridge-Aggregation1

#

traffic behavior behavior_tap

 redirect monitoring-group 1

#

traffic classifier classifier_tap operator and

 if-match any

#

qos tap policy policy_tap

 classifier classifier_tap behavior behavior_tap

#

interface Bridge-Aggregation1

#

interface GigabitEthernet1/0/1

 qos apply tap policy policy_tap inbound

#

interface GigabitEthernet1/0/2

 qos apply tap policy policy_tap inbound

#

interface GigabitEthernet1/0/3

 qos apply tap policy policy_tap inbound 

#

interface GigabitEthernet1/0/4

 port link-aggregation group 1

#

interface GigabitEthernet1/0/5

 port link-aggregation group 1

#

interface GigabitEthernet1/0/6

port link-aggregation group 1

Example: Configuring traffic monitoring and backup

Network configuration

As shown in Figure 4, configure M:N copying and link aggregation load sharing on Device B to meet the following requirements:

·     Incoming packets on Ten-GigabitEthernet 1/0/1 and Ten-GigabitEthernet 1/0/2 are redirected to the aggregate interface.

·     The aggregate interface load shares packets based on source IP addresses and destination IP addresses.

·     The aggregate interface sends incoming packets on Ten-GigabitEthernet 1/0/1 and Ten-GigabitEthernet 1/0/2 to Device D over the same link by using algorithm 1 as the link aggregation load sharing algorithm.

Figure 4 Network diagram

 

Applicable hardware and software versions

The following matrix shows the hardware and software versions to which this configuration example is applicable:

 

Hardware	Software version
S9850-G switch series	Not supported
S6850-G switch series S6805-G switch series	Not supported
S6530X switch series	Release 8108P22 and later
S5590-HI switch series	Not supported
S5590-EI switch series S5500V3-HI switch series	Not supported
S6520X-EI-G switch series S6520XP-EI-G switch series	Release 7748 and later
S5590XP-HI-G switch series	Not supported
S5560-EI-G switch series	Release 7748 and later
S5130S-EI-G switch series	Release 7748 and later
S5500-D-G switch series S5100-D-G switch series	Not supported
S5130S-HI-G switch series	Not supported
S5130S-EI-G switch series (except S5130S-30C-EI-G and S5130S-54C-EI-G switches)	Not supported
S5130S-30C-EI-G switch S5130S-54C-EI-G switch	Release 7748 and later

 

Procedures

# Create a Layer 2 aggregate interface named Bridge-Aggregation 1.

<DeviceB> system-view

[DeviceB] interface Bridge-Aggregation 1

[DeviceB-Bridge-Aggregation1] quit

# Assign Ten-GigabitEthernet 1/0/4, Ten-GigabitEthernet 1/0/5, and Ten-GigabitEthernet 1/0/6 to the aggregation group.

[DeviceB] interface ten-gigabitethernet1/0/4

[DeviceB-Ten-GigabitEthernet1/0/4] port link-aggregation group 1

[DeviceB-Ten-GigabitEthernet1/0/4] quit

[DeviceB] interface ten-gigabitethernet1/0/5

[DeviceB-Ten-GigabitEthernet1/0/5] port link-aggregation group 1

[DeviceB-Ten-GigabitEthernet1/0/5] quit

[DeviceB] interface ten-gigabitethernet1/0/6

[DeviceB-Ten-GigabitEthernet1/0/6] port link-aggregation group 1

[DeviceB-Ten-GigabitEthernet1/0/6] quit

# Create monitoring group 1, and assign the Layer 2 aggregate interface to the monitoring group.

[DeviceB] monitoring-group 1

[DeviceB-monitoring-group-1] monitoring-port bridge-aggregation 1

[DeviceB-monitoring-group-1] quit

# Create a traffic class named classifier_tap, and configure the traffic class to match all packets.

[DeviceB] traffic classifier classifier_tap

[DeviceB-classifier-classifier_tap] if-match any

[DeviceB-classifier-classifier_tap] quit

# Create a traffic behavior named behavior_tap, and configure an action of redirecting packets to monitoring group 1.

[DeviceB] traffic behavior behavior_tap

[DeviceB-behavior-behavior_tap] redirect monitoring-group 1

[DeviceB-behavior-behavior_tap] quit

# Create a TAP policy named policy_tap, and associate the traffic class with the traffic behavior in the TAP policy.

[DeviceB] qos tap policy policy_tap

[DeviceB-qospolicy-policy_tap] classifier classifier_tap behavior behavior_tap

[DeviceB-qospolicy-policy_tap] quit

# Applying the TAP policy to the inbound direction of Ten-GigabitEthernet 1/0/1.

[DeviceB] interface ten-gigabitethernet 1/0/1

[DeviceB-Ten-GigabitEthernet1/0/1] qos apply tap policy policy_tap inbound

[DeviceB-Ten-GigabitEthernet1/0/1] quit

# Applying the TAP policy to the inbound direction of Ten-GigabitEthernet 1/0/2.

[DeviceB] interface ten-gigabitethernet 1/0/2

[DeviceB-Ten-GigabitEthernet1/0/2] qos apply tap policy policy_tap inbound

[DeviceB-Ten-GigabitEthernet1/0/2] quit

# Applying the TAP policy to the inbound direction of Ten-GigabitEthernet 1/0/3.

[DeviceB] interface ten-gigabitethernet 1/0/3

[DeviceB-Ten-GigabitEthernet1/0/3] qos apply tap policy policy_tap inbound

[DeviceB-Ten-GigabitEthernet1/0/3] quit

# Set the global load sharing mode to load share packets based on source IP addresses and destination IP addresses.

[DeviceB] link-aggregation global load-sharing mode source-ip destination-ip

# Specify algorithm 1 as the link aggregation load sharing algorithm.

[DeviceB] link-aggregation global load-sharing algorithm 1

Verifying the configuration

# Display TAP policies applied to interfaces.

[DeviceB] display qos tap policy interface

Interface: Ten-GigabitEthernet1/0/1

  Direction: Inbound

  Tap policy: policy_tap

 

   Classifier: classifier_tap

     Operator: AND

     Rule(s) :

      If-match any

     Behavior: behavior_tap

      Redirecting:

        Redirect to the monitoring group: 1

Interface: Ten-GigabitEthernet1/0/2

  Direction: Inbound

  Tap policy: policy_tap

 

   Classifier: classifier_tap

     Operator: AND

     Rule(s) :

      If-match any

     Behavior: behavior_tap

      Redirecting:

        Redirect to the monitoring group: 1

Interface: Ten-GigabitEthernet1/0/3

  Direction: Inbound

  Tap policy: policy_tap

 

   Classifier: classifier_tap

     Operator: AND

     Rule(s) :

      If-match any

     Behavior: behavior_tap

      Redirecting:

        Redirect to the monitoring group: 1

# Display monitoring groups.

[DeviceB] display monitoring-group all

Monitoring group 1:

  Monitoring ports: Bridge-Aggregation1

# Display the load sharing mode.

[DeviceB] display link-aggregation load-sharing mode

Link-aggregation load-sharing algorithm:1

Link-aggregation load-sharing mode:

destination-ip address, source-ip address

Configuration files

#

 link-aggregation global load-sharing mode destination-ip source-ip

 link-aggregation global load-sharing algorithm 1

#

monitoring-group 1

 monitoring-port Bridge-Aggregation1

#

traffic behavior behavior_tap

 redirect monitoring-group 1

#

traffic classifier classifier_tap operator and

 if-match any

#

qos tap policy policy_tap

 classifier classifier_tap behavior behavior_tap

#

interface Bridge-Aggregation1

#

interface Ten-GigabitEthernet1/0/1

 qos apply tap policy policy_tap inbound

#

interface Ten-GigabitEthernet1/0/2

 qos apply tap policy policy_tap inbound

#

interface Ten-GigabitEthernet1/0/3

 qos apply tap policy policy_tap inbound 

#

interface Ten-GigabitEthernet1/0/4

 port link-aggregation group 1

#

interface Ten-GigabitEthernet1/0/5

 port link-aggregation group 1

#

interface Ten-GigabitEthernet1/0/6

port link-aggregation group 1