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

Configuration Guide - VPN 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - VPN
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).
Configuring IPv4 Route Import Between VPN Instances

Configuring IPv4 Route Import Between VPN Instances

IPv4 route import between VPN instances enables users in different VPNs to communicate.

Context

Perform the following steps for target VPN instances.
NOTE:

If you do not want a VPN instance to change the next hops of imported routes when advertising these routes to its IBGP peers, run the import-rib route next-hop-invariable command for the VPN instance.

Procedure

  • Configure the device to import IPv4 direct routes, static routes, or IGP routes from one VPN instance to another VPN instance.
    1. Run system-view

      The system view is displayed.

    2. Run ip vpn-instance vpn-instance-name

      The VPN instance view is displayed.

    3. Run ipv4-family

      The VPN instance IPv4 address family view is displayed.

    4. Run import-rib vpn-instance vpn-instance-name protocol { direct | vlink-direct-route | { static } [ valid-route ] } [ route-policy route-policy-name | route-filter route-filter-name ]

      The device is enabled to import IPv4 direct routes, Vlink direct routes or static routes from the specified VPN instance to the current VPN instance's corresponding routing table.

    5. Run commit

      The configuration is committed.

  • Configure the device to import IPv4 BGP routes from one VPN instance to another VPN instance's BGP routing table.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run ipv4-family vpn-instance vpn-instance-name

      The BGP-VPN instance IPv4 address family view is displayed.

    4. Run import-rib { public | vpn-instance vpn-instance-name } [ include-label-route ] [ valid-route ] [ route-policy route-policy-name | route-filter route-filter-name ]

      The device is enabled to import IPv4 BGP routes from the specified VPN instance to the current VPN instance's BGP routing table.

    5. Run commit

      The configuration is committed.

  • Configure the device to import BGP-labeled routes in a VPN instance's labeled address family to a specified VPN instance's BGP routing table.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run ipv4-family vpn-instance vpn-instance-name

      The BGP-VPN instance IPv4 address family view is displayed.

    4. Run import-rib vpn-instance vpn-instance-name labeled-unicast [ valid-route ] { route-policy route-policy-name | route-filter route-filter-name }

      The device is enabled to import BGP-labeled routes in a VPN instance's labeled address family to another VPN instance's BGP routing table.

    5. Run commit

      The configuration is committed.

  • Configure the device to import BGP-labeled routes in a VPN instance's labeled address family to the routing table of a specified VPN instance's BGP-labeled address family.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run ipv4-labeled-unicast vpn-instance vpn-instance-name

      The BGP-labeled-VPN instance IPv4 address family view is displayed.

    4. Run import-rib vpn-instance vpn-instance-name labeled-unicast [ valid-route ] { route-policy route-policy-name | route-filter route-filter-name }

      The device is enabled to import BGP-labeled routes in a public-labeled address family to the routing table of a VPN instance's BGP-labeled address family.

    5. Run commit

      The configuration is committed.

  • Configure the device to import BGP routes in a VPN instance to the routing table of a specified VPN instance's BGP-labeled address family:
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run ipv4-labeled-unicast vpn-instance vpn-instance-name

      The BGP-labeled-VPN instance IPv4 address family view is displayed.

    4. Run import-rib vpn-instance vpn-instance-name [ include-label-route ] [ valid-route ] [ route-policy route-policy-name | route-filter route-filter-name ]

      The device is enabled to import BGP routes in a VPN instance to the routing table of a specified VPN instance's BGP-labeled address family.

    5. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 27549

Downloads: 53

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