No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NE20E-S2 V800R010C10SPC500 Configuration Guide - Security 01

This is NE20E-S2 V800R010C10SPC500 Configuration Guide - Security
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Example for Configuring Static BGP VPN Flow Specification

Example for Configuring Static BGP VPN Flow Specification

In VPNs, if the characteristics of DoS or DDoS attack traffic are known, use the static BGP VPN Flow Specification function by manually configuring BGP VPN Flow Specification routes to ensure network security.

Networking Requirements

As shown in Figure 11-14, in a VPN, CE1 belongs to AS 100, while PE1, and PE2 belong to AS 200. PE1 is an ingress of AS 200. AS 200 communicates with AS 100 through PE1.

The attack source in AS 100 may flow into AS 200 through PE1, severely affecting network performance of AS 200.

In this situation, configure static BGP VPN Flow Specification to address this problem. The operation process is as follows: Configure a BGP VPN Flow Specification route manually and establish a BGP VPN Flow Specification peer relationship between PE1 and PE21. Then the route is sent to PE1 to discard the attack traffic or limit its rate.

Figure 11-14 Configuring static BGP VPN Flow Specification
NOTE:

Interfaces 1 and 2 in this example are GE 0/1/0, GE 0/2/0, respectively.



Configuration Notes

None.

Configuration Roadmap

The configuration roadmap is as follows:

  1. Configure an IP address for each involved interface.

  2. Create a VPN instance on PE1 and PE2 and bind the VPN instance to their interfaces.

  3. On PE2, configure a BGP VPN Flow Specification route (FlowSpec1) to discard the attack traffic whose source port number is 159.

  4. Establish a BGP VPN Flow Specification peer relationship between PE1 and PE2 so that the configured BGP VPN Flow Specification route can be sent to PE1 and be used by PE1 as a traffic filtering policy.

Data Preparation

To complete the configuration, you need the following data:
  • Router ID of CE1 (1.1.1.1), router ID of PE1 (2.2.2.2), and router ID of PE2 (3.3.3.3)

  • AS number of CE1 (100) and AS number of PE1, and PE2 (200)

  • Name of a VPN instance (vpna)

Procedure

  1. Configure an IP address for each interface.

    For detailed configurations, see the configuration files in this example.

  2. Create a VPN instance and bind it to each interface.

    # Configure PE1.

    [~PE1] ip vpn-instance vpna
    [*PE1-vpn-instance-vpna] ipv4-family
    [*PE1-vpn-instance-vpna-af-ipv4] route-distinguisher 100:1
    [*PE1-vpn-instance-vpna-af-ipv4] vpn-target 111:1 export-extcommunity
    [*PE1-vpn-instance-vpna-af-ipv4] vpn-target 111:1 import-extcommunity
    [*PE1-vpn-instance-vpna-af-ipv4] commit
    [~PE1-vpn-instance-vpna-af-ipv4] quit
    [~PE1-vpn-instance-vpna] quit
    [~PE1] interface GigabitEthernet0/1/0
    [~PE1-GigabitEthernet0/1/0] undo shutdown
    [*PE1-GigabitEthernet0/1/0] ip binding vpn-instance vpna
    [*PE1-GigabitEthernet0/1/0] ip address 10.1.1.2 255.255.255.0
    [*PE1-GigabitEthernet0/1/0] commit
    [~PE1-GigabitEthernet0/1/0] quit
    [~PE1] interface GigabitEthernet0/2/0
    [~PE1-GigabitEthernet0/2/0] undo shutdown
    [*PE1-GigabitEthernet0/2/0] ip binding vpn-instance vpna
    [*PE1-GigabitEthernet0/2/0] ip address 10.2.1.1 255.255.255.0
    [*PE1-GigabitEthernet0/2/0] commit
    [~PE1-GigabitEthernet0/2/0] quit

    # Configure PE2.

    [~PE2] ip vpn-instance vpna
    [*PE2-vpn-instance-vpna] ipv4-family
    [*PE2-vpn-instance-vpna-af-ipv4] route-distinguisher 200:1
    [*PE2-vpn-instance-vpna-af-ipv4] vpn-target 111:1 export-extcommunity
    [*PE2-vpn-instance-vpna-af-ipv4] vpn-target 111:1 import-extcommunity
    [*PE2-vpn-instance-vpna-af-ipv4] commit
    [~PE2-vpn-instance-vpna-af-ipv4] quit
    [~PE2-vpn-instance-vpna] quit
    [~PE2] interface GigabitEthernet0/1/0
    [~PE2-GigabitEthernet0/1/0] undo shutdown
    [*PE2-GigabitEthernet0/1/0] ip binding vpn-instance vpna
    [*PE2-GigabitEthernet0/1/0] ip address 10.2.1.2 255.255.255.0
    [*PE2-GigabitEthernet0/1/0] commit
    [~PE2-GigabitEthernet0/1/0] quit

  3. Configure a BGP VPN Flow Specification route.

    # Configure PE2.

    [~PE2] flow-route FlowSpec1 vpn-instance vpna
    [*PE2-flow-route-vpna] if-match source-port equal 159
    [*PE2-flow-route-vpna] apply deny
    [*PE2-flow-route-vpna] commit
    [~PE2-flow-route-vpna] quit

  4. Configure BGP VPN Flow Specification peer relationships.

    # Configure PE1.

    [~PE1]bgp 200
    [*PE1-bgp] router-id 2.2.2.2
    [*PE1-bgp] commit
    [~PE1-bgp] vpn-instance vpna
    [*PE1-bgp-instance-vpna] peer 10.1.1.1 as-number 100
    [*PE1-bgp-instance-vpna] peer 10.2.1.2 as-number 200
    [*PE1-bgp-instance-vpna] quit
    [*PE1-bgp] ipv4-flow vpn-instance vpna
    [*PE1-bgp-flow-vpna] peer 10.1.1.1 enable
    [*PE1-bgp-flow-vpna] peer 10.2.1.2 enable
    [*PE1-bgp-flow-vpna] commit
    [~PE1-bgp-flow-vpna] quit
    [~PE1-bgp] quit

    # Configure PE2.

    [~PE2]bgp 200
    [*PE2-bgp] router-id 3.3.3.3
    [*PE2-bgp] commit
    [~PE2-bgp] vpn-instance vpna
    [*PE2-bgp-instance-vpna] peer 10.2.1.1 as-number 200
    [*PE2-bgp-instance-vpna] quit
    [*PE2-bgp] ipv4-flow vpn-instance vpna
    [*PE2-bgp-flow-vpna] peer 10.2.1.1 enable
    [*PE2-bgp-flow-vpna] commit
    [~PE2-bgp-flow-vpna] quit
    [~PE2-bgp] quit

  5. Verify the configuration.

    # Check whether BGP VPN Flow Specification peer relationships are established on PE1. The command output shows that BGP VPN Flow Specification peer relationships are established.

    <PE1> display bgp flow vpnv4 vpn-instance vpna peer
     
     BGP local router ID : 2.2.2.2
     Local AS number : 200
    
     VPN-Instance vpna, Router ID 2.2.2.2:
     Total number of peers : 2                 Peers in established state : 2
    
      Peer            V          AS  MsgRcvd  MsgSent  OutQ  Up/Down       State  PrefRcv
      10.1.1.1        4         100        3        5     0 00:00:06 Established        0
      10.2.1.2        4         200     9523     9530     0 0138h31m Established        1

    # Check information about the BGP VPN Flow Specification routes received by PE1.

    <PE1> display bgp flow vpnv4 vpn-instance vpna routing-table
     Total Number of Routes: 1
     * >  ReIndex : 1
          Dissemination Rules:
           Src. Port      : eq 159
           MED      : 0                   PrefVal  : 0                   
           LocalPref: 100                       
           Path/Ogn :  i

    # Check the traffic filtering rule carried in the BGP VPN Flow Specification route by specifying ReIndex of the route.

    <PE1> display bgp flow vpnv4 vpn-instance vpna routing-table 1
     ReIndex : 1
     Order   : 0
     Dissemination Rules :
       Src. Port      : eq 159
     
     BGP flow-ipv4 routing table entry information of 1:
     Match action :
       apply deny
     From: 10.2.1.2 (3.3.3.3) 
     Route Duration: 0d15h13m20s
     AS-path Nil, origin igp, MED 0, localpref 100, pref-val 0, valid, internal, best, pre 255
     Advertised to such 1 peers:
        10.1.1.1

Configuration Files

  • CE1 configuration file

    #
    sysname CE1  
    #               
    interface GigabitEthernet0/1/0
     undo shutdown  
     ip address 10.1.1.1 255.255.255.0  
    #               
    interface LoopBack1
     ip address 1.1.1.1 255.255.255.255
    #               
    bgp 100         
     router-id 1.1.1.1
     peer 10.1.1.2 as-number 200
     #              
     ipv4-family unicast
      undo synchronization
      peer 10.1.1.2 enable
     #              
     ipv4-family flow
      peer 10.1.1.2 enable
    #               
    return
  • PE1 configuration file

    #
    sysname PE1
    #
    ip vpn-instance vpna
     ipv4-family
      route-distinguisher 100:1
      vpn-target 111:1 export-extcommunity
      vpn-target 111:1 import-extcommunity
    #               
    interface GigabitEthernet0/1/0
     undo shutdown  
     ip binding vpn-instance vpna
     ip address 10.1.1.2 255.255.255.0
    #               
    interface GigabitEthernet0/2/0
     undo shutdown  
     ip binding vpn-instance vpna
     ip address 10.2.1.1 255.255.255.0
    #               
    interface LoopBack1
     ip address 2.2.2.2 255.255.255.255
    #               
    bgp 200         
     router-id 2.2.2.2
     #              
     ipv4-family unicast
      undo synchronization
    
     #              
     vpn-instance vpna
      peer 10.1.1.1 as-number 100
      peer 10.2.1.2 as-number 200
     #              
     ipv4-flow vpn-instance vpna
      peer 10.1.1.1 enable
      peer 10.2.1.2 enable
    #               
    return
  • PE2 configuration file

    #
    sysname PE2
    #
    ip vpn-instance vpna
     ipv4-family
      route-distinguisher 200:1
      vpn-target 111:1 export-extcommunity
      vpn-target 111:1 import-extcommunity
    #               
    interface GigabitEthernet0/1/0
     undo shutdown  
     ip binding vpn-instance vpna
     ip address 10.2.1.2 255.255.255.0
    #               
    interface LoopBack1
     ip address 3.3.3.3 255.255.255.255
    #               
    bgp 200         
     router-id 3.3.3.3
     #              
     ipv4-family unicast
      undo synchronization
     #              
     vpn-instance vpna
      peer 10.2.1.1 as-number 200
     #              
     ipv4-flow vpn-instance vpna
      peer 10.2.1.1 enable
    #               
    flow-route FlowSpec1 vpn-instance vpna
     if-match source-port equal 159
     apply deny     
    #               
    return          
Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055397

Views: 19562

Downloads: 39

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next