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 and Public Network Instances

Configuring IPv4 Route Import Between VPN and Public Network Instances

IPv4 route import between VPN and public network instances enables IPv4 VPN users to communicate with IPv4 public network users.

Procedure

  • Configure IPv4 route import between VPN and public network 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.

    1. Run system-view

      The system view is displayed.

    2. Configure the device to import different types of IPv4 VPN routes to the public network instance's corresponding routing tables.

      • Run ip import-rib vpn-instance vpn-instance-name protocol direct [ route-policy route-policy-name | route-filter route-filter-name ]

        The device is enabled to import IPv4 VPN direct routes to the public network instance's routing table for direct routes.

      • Run ip import-rib vpn-instance vpn-instance-name protocol vlink-direct-route [ route-policy route-policy-name | route-filter route-filter-name ]

        The device is enabled to import IPv4 VPN VLINK direct routes to the public network instance's routing table for VLINK direct routes.

      • Run ip import-rib vpn-instance vpn-instance-name protocol { static } [ valid-route ] [ route-policy route-policy-name | route-filter route-filter-name ]

        The device is enabled to import IPv4 VPN static routes to the public network instance's routing table.

      • Configure the device to import IPv4 VPN BGP routes to the public network instance's BGP routing table.
        1. Run bgp as-number

          The BGP view is displayed.

        2. Run ipv4-family unicast

          The BGP-IPv4 unicast address family view is displayed.

        3. 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 VPN routes in the VPN instance to a public network routing table.

        4. Run quit

          Return to the BGP view.

        5. Run quit

          Return to the system view.

      • Configure the device to import routes in a VPN instance's BGP-labeled address family to a public BGP routing table:
        1. Run bgp as-number

          The BGP view is displayed.

        2. Run ipv4-family unicast

          The BGP-IPv4 unicast address family view is displayed.

        3. 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 routes in a VPN instance's BGP-labeled address family to a public BGP routing table.

        4. Run quit

          Return to the BGP view.

        5. Run quit

          Return to the system view.

      • Configure the device to import routes in a VPN instance's BGP-labeled address family to the routing table of a public BGP-labeled address family:
        1. Run bgp as-number

          The BGP view is displayed.

        2. Run ipv4-family labeled-unicast

          The BGP-labeled address family view is displayed.

        3. 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 routes in a VPN instance's BGP-labeled address family to the routing table of a public BGP-labeled address family.

        4. Run quit

          Return to the BGP view.

        5. Run quit

          Return to the system view.

    3. Configure the device to import different types of IPv4 public network routes to a VPN instance's corresponding routing tables.

      • Configure the device to import IPv4 public network direct routes, static routes, or IGP routes to a VPN instance's corresponding routing table.
        1. Run ip vpn-instance vpn-instance-name

          The VPN instance view is displayed.

        2. Run ipv4-family

          The VPN instance IPv4 address family view is displayed.

        3. Run import-rib public 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 public network direct routes, VLINK direct routes, static routes to the VPN instance's corresponding routing table.

      • Configure the device to import IPv4 public network BGP routes to a VPN instance's BGP routing table.
        1. Run bgp as-number

          The BGP view is displayed.

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

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

        3. Run import-rib public [ include-label-route ] [ valid-route ] [ route-policy route-policy-name | route-filter route-filter-name ]

          The device is enabled to import IPv4 public network BGP routes to the VPN instance's BGP routing table.

      • Configure the device to import BGP-labeled routes in a public-labeled address family to the routing table of a VPN instance's BGP-labeled address family:
        1. Run bgp as-number

          The BGP view is displayed.

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

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

        3. Run import-rib public 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.

      • Configure the device to import BGP routes in a public routing table to the routing table of a VPN instance's BGP-labeled address family.
        1. Run bgp as-number

          The BGP view is displayed.

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

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

        3. Run import-rib puiblic [ 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 public routing table to the routing table of a VPN instance's BGP-labeled address family.

    4. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 27739

Downloads: 53

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