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 VPN 6PE

Configuring VPN 6PE

VPN 6PE connects separated IPv6 networks belonging to different VPN instances through LSPs.

Usage Scenario

Figure 6-4 shows a typical VPN 6PE network where a BGP/MPLS IPv6 VPN (6vPE) is established between PE1 and PE2 and VPN 6PE peer relationships are established between CE1 and PE1 and between CE2 and PE2.

Figure 6-4 VPN 6PE network

Pre-configuration Tasks

Before configuring VPN 6PE, complete the following tasks:

  • Enable IPv6 on PEs and relevant interfaces.

  • Configure an IGP on the MPLS backbone network to ensure IP connectivity.

  • Configure basic MPLS functions on the MPLS backbone network.

  • Establish LSPs or MPLS TE tunnels between PEs.

  • Configure IPv6 addresses on interfaces that connect CEs to PEs.

Configuration Procedures

Figure 6-5 Flowchart for configuring VPN 6PE

Configuring a VPN Instance

An IPv6 VPN instance can be configured to manage IPv6 VPN routes.

Context

A VPN instance, also called a VRF table, is created to comprise the VPN forwarding information for each VPN. This instance is called a VPN instance or a VPN routing and forwarding (VRF) table. In relevant standards, a VPN instance is also called a per-site forwarding table. VPN instances must be created in all BGP/MPLS IPv6 VPN solutions.

In a VPN 6PE scenario, both IPv4 and IPv6 address families must be enabled in a VPN instance. The IPv4 routing table of the VPN instance manages routes used to establish VPN LDP LSPs, whereas the IPv6 routing table of the VPN instance manages received VPN IPv6 routes.

Procedure

  1. Run system-view

    The system view is displayed.

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

    A VPN instance is created, and its view is displayed.

    NOTE:

    A VPN instance name is case sensitive. For example, "vpn1" and "VPN1" are different VPN instances.

    Multiple VPN instances can be created on a PE. By default, no VPN instance exists on a PE.

  3. (Optional) Run description description-information

    A description is configured for the VPN instance.

    Similar to a host name or an interface description, the VPN instance description helps users memorize the VPN instance.

  4. Run ipv4-family

    The IPv4 address family is enabled for the VPN instance, and the VPN instance IPv4 address family view is displayed.

    Configurations in a VPN instance can be performed only after an address family is enabled for the VPN instance based on the advertised route and forwarding data type.

  5. Run route-distinguisher route-distinguisher

    An RD is configured for the VPN instance IPv4 address family.

    A VPN instance IPv4 address family takes effect only after being configured with an RD. The RDs of different VPN instances on a PE must be different.

    NOTE:
    • RDs cannot be modified but can be deleted after being configured. After an RD is deleted, all configurations in the VPN instance IPv4 address family of the corresponding VPN instance will be deleted.

    • If you configure an RD for the VPN instance IPv4 address family in the created VPN instance view, the VPN instance IPv4 address family is enabled and the VPN instance IPv4 address family view is displayed.

  6. Run vpn-target vpn-target &<1-8> [ both | export-extcommunity | import-extcommunity ]

    A VPN target is configured for the VPN instance IPv4 address family.

    A VPN target is a BGP extended community attribute. It is used to control the receiving and advertisement of VPN routing information. A maximum of eight VPN targets can be configured using the vpn-target command. If you want to configure multiple VPN targets in the VPN instance IPv4 address family view, run the vpn-target command multiple times.

  7. Run quit

    Exit from the VPN instance IPv4 address family view.

  8. Run ipv6-family

    The IPv6 address family is enabled for the VPN instance, and the VPN instance IPv6 address family view is displayed.

    VPN instances support both the IPv4 and IPv6 address families. Configurations in a VPN instance can be performed only after an address family is enabled for the VPN instance based on the advertised route and forwarding data type.

  9. Run route-distinguisher route-distinguisher

    An RD is configured for the VPN instance IPv6 address family.

    A VPN instance IPv6 address family takes effect only after being configured with an RD. The RDs of different VPN instances that are enabled with the IPv6 address family on a PE must be different.

    NOTE:

    RDs cannot be modified but can be deleted after being configured. After an RD is deleted, all configurations in the VPN instance IPv6 address family of the corresponding VPN instance will be deleted.

  10. Run vpn-target vpn-target &<1-8> [ both | export-extcommunity | import-extcommunity ]

    A VPN target is configured for the VPN instance IPv6 address family.

    A VPN target is a BGP extended community attribute. It is used to control the receiving and advertisement of VPN-IPv6 routing information. A maximum of eight VPN targets can be configured using the vpn-target command. If you want to configure more VPN targets in the VPN instance IPv6 address family view, run the vpn-target command multiple times.

  11. Run commit

    The configuration is committed.

Follow-up Procedure

You can configure a routing policy in a VPN instance to implement functions, such as filtering routes and limiting the number of routes. For configuration details, see Configuring a VPN Instance and Configuring a VPN Instance.

Binding Interfaces to a VPN Instance

After an interface is bound to a VPN instance, the interface becomes a part of the VPN. Packets entering the interface will be forwarded based on the VRF table of the VPN.

Context

After a VPN instance is configured on a PE, an interface that belongs to the VPN must be bound to the VPN instance. Otherwise, the interface functions as a public network interface and cannot forward VPN data.

Perform the following steps on the PEs that are connected to CEs:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Run ip binding vpn-instance vpn-instance-name

    The interface is bound to the VPN instance.

    NOTE:

    Using the ip binding vpn-instance command will delete Layer 3 (including IPv4 and IPv6) configurations, such as the IP address and routing protocol, on the interface. Reconfigure them after using the ip binding vpn-instance command if needed.

  4. Run ip address ip-address { mask | mask-length }

    An IP address is configured for the interface.

  5. Run commit

    The configuration is committed.

(Optional) Configuring a Router ID for a BGP VPN Instance

To distinguish a BGP VPN instance from the other BGP VPN instances on the same device, specify a unique router ID for the BGP VPN instance.

Context

By default, all BGP VPN instances on a device use the BGP router ID as their router IDs. Using the same router ID for all BGP VPN instances sometimes creates inconveniences. For example, it is impossible to establish a BGP peer relationship between two BGP VPN instances that use the same router ID on a PE.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run vpn-instance vpn-instance-name

    A BGP VPN instance is created, and the BGP VPN instance view is displayed.

  4. Run router-id { ipv4-address | auto-select }

    A router ID is manually configured or automatically selected for the BGP VPN instance.

  5. Run commit

    The configuration is committed.

Establishing MP-IBGP Peer Relationships Between PEs

MP-IBGP uses extended community attributes to advertise VPNv6 routes between PEs.

Context

If VPN sites in a basic BGP/MPLS IPv6 VPN need to communicate, PEs must use MP-IBGP to advertise VPNv4 routes with the RD information to each other. Since all the PEs reside in the same AS, MP-IBGP peer relationships can be set up between them. In the current implementation, IPv4 BGP peer relationships are set up between PEs.

Perform the following steps on each PE.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run peer ipv4-address as-number as-number

    The peer PE is configured as a BGP peer.

  4. Run peer ipv4-address connect-interface loopback interface-number

    An interface is used to set up a TCP connection with the BGP peer.

    NOTE:

    A PE must use a loopback interface address with a 32-bit mask to set up an MP-IBGP peer relationship with the peer PE so that VPN routes can be iterated to tunnels. The route to the local loopback interface is advertised to the peer PE using an IGP on the MPLS backbone network.

  5. Run ipv6-family vpnv6

    The BGP-VPNv6 address family view is displayed.

  6. Run peer ipv4-address enable

    The function to exchange VPN-IPv6 routes with the BGP peer is enabled.

  7. Run commit

    The configuration is committed.

Configuring BGP VPN 6PE Peer Relationships Between PEs and CEs

In a VPN 6PE, VPN 6PE peer relationships must be configured between PEs and CEs to allow them to communicate.

Context

If you want to use IP forwarding between PEs and CEs, be sure to configure IPv4 and IPv6 addresses on link interfaces between PEs and CEs.

The routing protocol configurations on CEs and PEs are different:
  • A CE is located at the client side and unaware of the VPN. Therefore, you do not need to configure VPN parameters when configuring a routing protocol on the CE.
  • A PE is located at the edge of the carrier's network. It connects to a CE and exchanges VPN routing information with other PEs. If the CEs that access a PE belong to different VPNs, the PE must maintain different VRF tables. When configuring a routing protocol on the PE, specify the name of the VPN instance to which the routing protocol applies and configure the routing protocol and MP-BGP to import routes from each other.

Procedure

  • Configure BGP VPN 6PE peer relationships between PEs and CEs (IP forwarding).

    NOTE:

    Before configuring BGP VPN 6PE peer relationships between PEs and CEs, configure IPv6 addresses for interfaces connecting PEs to CEs.

    Perform the following steps on a PE:

    1. Run system-view

      The system view is displayed.

    2. Run route-policy route-policy-name { permit | deny } node node

      A route-policy node is created, and the route-policy view is displayed.

    3. (Optional) Configure if-match clauses to filter routes transmitted between sites. For configuration details, see (Optional) Configuring an if-match Clause.
    4. Run apply ipv6 next-hop ipv6-address

      The next hop of the route is changed and ipv6-address is configured as the IPv6 address of the CE interface that connects to a PE.

    5. Run quit

      Return to the previous view.

    6. Run bgp as-number

      The BGP view is displayed.

    7. Run vpn-instance vpn-instance-name

      A BGP VPN instance is created, and the BGP VPN instance view is displayed.

    8. Run peer ipv4-address as-number as-number

      The CE is configured as a VPN 6PE peer.

      NOTE:
      Before configuring a VPN 6PE peer group, run the group group-name internal command to create a peer group and run the peer ipv4-address group group-name command to add peers to the group.

    9. (Optional) Run peer ipv4-address connect-interface interface-type interface-number [ ipv4-source-address ]

      The source interface and source address are specified for establishing a TCP connection.

    10. Run quit

      Return to the previous view.

    11. Run ipv6-family vpn-instance vpn-instance-name

      The BGP VPN instance IPv6 address family view is displayed.

    12. Run peer { ipv4-address | group-name } enable

      The ability to exchange BGP route information with a specified BGP IPv4 peer (group) is enabled.

      NOTE:
      To enable the ability to add a peer to a peer group in a BGP VPN instance, run the peer ipv4-address group group-name enable command.

    13. Run peer { ipv4-address | group-name } route-policy route-policy-name export

      An export routing policy is applied.

    14. Run quit

      Return to the previous view.

    15. Run commit

      The configuration is committed.

    Perform the following steps on the CE:

    1. Run system-view

      The system view is displayed.

    2. Run route-policy route-policy-name { permit | deny } node node

      A route-policy node is created, and the route-policy view is displayed.

    3. (Optional) Configure if-match clauses to filter routes transmitted between sites. For configuration details, see (Optional) Configuring an if-match Clause.
    4. Run apply ipv6 next-hop ipv6-address

      The next hop of the route is changed and ipv6-address is configured as the IPv6 address of the CE interface that connects to a PE.

    5. Run quit

      Return to the previous view.

    6. Run bgp as-number

      The BGP view is displayed.

    7. Run peer { ipv4-address | group-name } as-number as-number

      A BGP peer is configured.

    8. (Optional) Run peer ipv4-address connect-interface interface-type interface-number [ ipv4-source-address ]

      The source interface and source address are specified for establishing a TCP connection.

    9. Run ipv6-family unicast

      The BGP-IPv6 unicast address family view is displayed.

    10. Run peer { ipv4-address | group-name } enable

      The BGP IPv4 peer (group) is enabled.

    11. Run peer { ipv4-address | group-name } route-policy route-policy-name export

      An export routing policy is applied.

    12. Run commit

      The configuration is committed.

  • Configure IBGP VPN 6PE peer relationships between PEs and CEs (tunnel forwarding).

    NOTE:

    Before configuring IBGP VPN 6PE peer relationships between PEs and CEs (tunnel forwarding), configure a VPN IGP or VPN static routes on PEs and CEs. To implement communication between PEs and CEs, see Configuring Route Exchange Between PEs and CEs.

    Perform the following steps on a PE:

    1. Run system-view

      The system view is displayed.

    2. Run mpls lsr-id lsr-id

      The LSR ID of the local node is configured.

      When configuring an LSR ID, note the following:
      • Configuring an LSR ID is the prerequisite of all MPLS configurations.

      • An LSR ID must be manually configured because no default LSR ID is available.

      • Use the IP address of a loopback interface on an LSR as an LSR ID.

    3. Run mpls

      MPLS is enabled globally.

    4. Run quit

      Return to the previous view.

    5. Run mpls ldp vpn-instance vpn-instance-name

      LDP is enabled for a specified VPN instance, and the MPLS LDP VPN instance view is displayed.

    6. Run quit

      Return to the previous view.

    7. Run interface interface-type interface-number

      The view of the PE interface connecting to the CE is displayed.

    8. Run mpls

      MPLS is enabled.

    9. Run mpls ldp

      MPLS LDP is enabled.

    10. Run quit

      Return to the previous view.

    11. Run bgp as-number

      The BGP view is displayed.

    12. Run vpn-instance vpn-instance-name

      A BGP VPN instance is created, and the BGP VPN instance view is displayed.

    13. Run peer ipv4-address as-number as-number

      The CE is configured as a VPN peer.

      NOTE:
      Before configuring a VPN 6PE peer group, run the group group-name internal command to create a peer group and run the peer ipv4-address group group-name command to add peers to the group.

    14. Run peer ipv4-address connect-interface interface-type interface-number [ ipv4-source-address ]

      The source interface and source address are specified for establishing a TCP connection.

    15. Run quit

      Return to the previous view.

    16. Run ipv6-family vpn-instance vpn-instance-name

      The BGP VPN instance IPv6 address family view is displayed.

    17. Run peer { ipv4-address | group-name } enable

      The ability to exchange BGP route information with a specified BGP IPv4 peer (group) is enabled.

      NOTE:
      To enable the ability to add a peer to a peer group in a BGP VPN instance, run the peer ipv4-address group group-name enable command.

    18. Run peer { ipv4-address | group-name } label-route-capability

      The capability to exchange labeled IPv4 routes with CEs is configured.

    19. Run quit

      Return to the previous view.

    20. Run commit

      The configuration is committed.

    Perform the following steps on the CE:

    1. Run system-view

      The system view is displayed.

    2. Run mpls lsr-id lsr-id

      The LSR ID of the local node is configured.

      When configuring an LSR ID, note the following:
      • Configuring an LSR ID is the prerequisite of all MPLS configurations.

      • An LSR ID must be manually configured because no default LSR ID is available.

      • Use the IP address of a loopback interface on an LSR as an LSR ID.

    3. Run mpls

      MPLS is enabled globally.

    4. Run quit

      Return to the previous view.

    5. Run mpls ldp

      MPLS LDP is enabled globally.

    6. Run quit

      Return to the previous view.

    7. Run interface interface-type interface-number

      The view of the CE interface connecting to the PE is displayed.

    8. Run mpls

      MPLS is enabled.

    9. Run mpls ldp

      MPLS LDP is enabled.

    10. Run quit

      Return to the previous view.

    11. Run bgp as-number

      The BGP view is displayed.

    12. Run peer { ipv4-address | group-name } as-number as-number

      A BGP peer is configured.

    13. Run peer ipv4-address connect-interface interface-type interface-number [ ipv4-source-address ]

      The source interface and source address are specified for establishing a TCP connection.

    14. Run ipv6-family unicast

      The BGP-IPv6 unicast address family view is displayed.

    15. Run peer { ipv4-address | group-name } enable

      The ability to exchange BGP route information with a specified BGP IPv4 peer (group) is enabled.

    16. Run peer { ipv4-address | group-name } label-route-capability

      The capability to exchange labeled IPv4 routes with PEs is configured.

    17. Run commit

      The configuration is committed.

  • Configure direct EBGP VPN 6PE peer relationships between PEs and CEs (tunnel forwarding).

    Perform the following steps on a PE:

    1. Run system-view

      The system view is displayed.

    2. Run mpls lsr-id lsr-id

      The LSR ID of the local node is configured.

      When configuring an LSR ID, note the following:
      • Configuring an LSR ID is the prerequisite of all MPLS configurations.

      • An LSR ID must be manually configured because no default LSR ID is available.

      • Use the IP address of a loopback interface on an LSR as an LSR ID.

    3. Run mpls

      MPLS is enabled globally.

    4. Run quit

      Return to the previous view.

    5. Run interface interface-type interface-number

      The view of the PE interface connecting to the CE is displayed.

    6. Run mpls

      MPLS is enabled.

    7. Run quit

      Return to the previous view.

    8. Run bgp as-number

      The BGP view is displayed.

    9. Run vpn-instance vpn-instance-name

      A BGP VPN instance is created, and the BGP VPN instance view is displayed.

    10. Run peer { ipv4-address | group-name } as-number as-number

      The CE is configured as a VPN peer (group).

      NOTE:
      Before configuring a VPN 6PE peer group, run the group group-name external command to create a peer group and run the peer ipv4-address group group-name command to add peers to the group.

    11. Run peer { ipv4-address | group-name } ebgp-max-hop [ hop-count ]

      The maximum number of hops allowed for the EBGP connection is set.

    12. Run quit

      Return to the previous view.

    13. Run ipv6-family vpn-instance vpn-instance-name

      The BGP VPN instance IPv6 address family view is displayed.

    14. Run peer { ipv4-address | group-name } enable

      The ability to exchange BGP route information with a specified BGP IPv4 peer (group) is enabled.

      NOTE:
      To enable the ability to add a peer to a peer group in a BGP VPN instance, run the peer ipv4-address group group-name enable command.

    15. Run peer { ipv4-address | group-name } label-route-capability

      The capability to exchange labeled IPv4 routes with CEs is configured.

    16. Run quit

      Return to the previous view.

    17. Run commit

      The configuration is committed.

    Perform the following steps on the CE:

    1. Run system-view

      The system view is displayed.

    2. Run mpls lsr-id lsr-id

      The LSR ID of the local node is configured.

      When configuring an LSR ID, note the following:
      • Configuring an LSR ID is the prerequisite of all MPLS configurations.

      • An LSR ID must be manually configured because no default LSR ID is available.

      • Use the IP address of a loopback interface on an LSR as an LSR ID.

    3. Run mpls

      MPLS is enabled globally.

    4. Run quit

      Return to the previous view.

    5. Run interface interface-type interface-number

      The view of the CE interface connecting to the PE is displayed.

    6. Run mpls

      MPLS is enabled.

    7. Run quit

      Return to the previous view.

    8. Run bgp as-number

      The BGP view is displayed.

    9. Run peer { ipv4-address | group-name } as-number as-number

      A BGP peer is configured.

    10. Run ipv6-family unicast

      The BGP-IPv6 unicast address family view is displayed.

    11. Run peer { ipv4-address | group-name } enable

      The ability to exchange BGP route information with a specified BGP IPv4 peer (group) is enabled.

    12. Run peer { ipv4-address | group-name } ebgp-max-hop [ hop-count ]

      The maximum number of hops allowed for the EBGP connection is set.

    13. Run peer { ipv4-address | group-name } label-route-capability

      The capability to exchange labeled IPv4 routes with PEs is configured.

    14. Run commit

      The configuration is committed.

  • Configure indirect EBGP VPN 6PE peer relationships between PEs and CEs (tunnel forwarding).

    NOTE:

    Before configuring IBGP VPN 6PE peer relationships between PEs and CEs (tunnel forwarding), configure PEs and CEs to implement route reachability. For example, configure static routes on PEs and CEs.

    Perform the following steps on a PE:

    1. Run system-view

      The system view is displayed.

    2. Run mpls lsr-id lsr-id

      The LSR ID of the local node is configured.

      When configuring an LSR ID, note the following:
      • Configuring an LSR ID is the prerequisite of all MPLS configurations.

      • An LSR ID must be manually configured because no default LSR ID is available.

      • Use the IP address of a loopback interface on an LSR as an LSR ID.

    3. Run mpls

      MPLS is enabled globally.

    4. Run quit

      Return to the previous view.

    5. Run mpls ldp vpn-instance vpn-instance-name

      LDP is enabled for a specified VPN instance, and the MPLS LDP VPN instance view is displayed.

    6. Run quit

      Return to the previous view.

    7. Run interface interface-type interface-number

      The view of the PE interface connecting to the CE is displayed.

    8. Run mpls

      MPLS is enabled.

    9. Run mpls ldp

      MPLS LDP is enabled.

    10. Run quit

      Return to the previous view.

    11. Run bgp as-number

      The BGP view is displayed.

    12. Run vpn-instance vpn-instance-name

      A BGP VPN instance is created, and the BGP VPN instance view is displayed.

    13. Run peer { ipv4-address | group-name } as-number as-number

      The CE is configured as a VPN peer (group).

      NOTE:
      Before configuring a VPN 6PE peer group, run the group group-name external command to create a peer group and run the peer ipv4-address group group-name command to add peers to the group.

    14. Run peer { ipv4-address | group-name } ebgp-max-hop [ hop-count ]

      The maximum number of hops allowed for the EBGP connection is set.

    15. Run quit

      Return to the previous view.

    16. Run ipv6-family vpn-instance vpn-instance-name

      The BGP VPN instance IPv6 address family view is displayed.

    17. Run peer { ipv4-address | group-name } enable

      The ability to exchange BGP route information with a specified BGP IPv4 peer (group) is enabled.

      NOTE:
      To enable the ability to add a peer to a peer group in a BGP VPN instance, run the peer ipv4-address group group-name enable command.

    18. Run peer { ipv4-address | group-name } label-route-capability

      The capability to exchange labeled IPv4 routes with CEs is configured.

    19. Run quit

      Return to the previous view.

    20. Run commit

      The configuration is committed.

    Perform the following steps on the CE:

    1. Run system-view

      The system view is displayed.

    2. Run mpls lsr-id lsr-id

      The LSR ID of the local node is configured.

      When configuring an LSR ID, note the following:
      • Configuring an LSR ID is the prerequisite of all MPLS configurations.

      • An LSR ID must be manually configured because no default LSR ID is available.

      • Use the IP address of a loopback interface on an LSR as an LSR ID.

    3. Run mpls

      MPLS is enabled globally.

    4. Run quit

      Return to the previous view.

    5. Run mpls ldp

      MPLS LDP is enabled globally.

    6. Run quit

      Return to the previous view.

    7. Run interface interface-type interface-number

      The view of the CE interface connecting to the PE is displayed.

    8. Run mpls

      MPLS is enabled.

    9. Run mpls ldp

      MPLS LDP is enabled.

    10. Run quit

      Return to the previous view.

    11. Run bgp as-number

      The BGP view is displayed.

    12. Run peer { ipv4-address | group-name } as-number as-number

      A BGP peer is configured.

    13. Run peer { ipv4-address | group-name } ebgp-max-hop [ hop-count ]

      The maximum number of hops allowed for the EBGP connection is set.

    14. Run ipv6-family unicast

      The BGP-IPv6 unicast address family view is displayed.

    15. Run peer { ipv4-address | group-name } enable

      The ability to exchange BGP route information with a specified BGP IPv4 peer (group) is enabled.

    16. Run peer { ipv4-address | group-name } label-route-capability

      The capability to exchange labeled IPv4 routes with PEs is configured.

    17. Run commit

      The configuration is committed.

Verifying the VPN 6PE Configuration

After VPN 6PE is configured on a PE, a BGP IPv4 peer relationship with the CE can be found in the VPN instance IPv6 address family on the PE.

Prerequisites

VPN 6PE has been configured.

Procedure

  • Run the following commands on the PE to check information about the created VPN instance IPv6 address family, including the RD and other attributes.

    • Run the display ip vpn-instance vpn-instance-name command to check summary information about the specified VPN instance.

    • Run the display ip vpn-instance verbose vpn-instance-name command to check detailed information about the specified VPN instance, including information in the IPv4 and IPv6 address families enabled for the VPN instance.

    • Run the display ip vpn-instance import-vt ivt-value command to check information about the VPN instances with the specified import VPN target.

    • Run the display ip vpn-instance [ vpn-instance-name ] interface command to check information about the interface bound to the specified VPN instance.

  • Run the following commands on the PE to check the BGP IPv4 peer relationship established with the CE in the VPN instance IPv6 address family.

    • Run the display bgp vpnv6 vpn-instance vpn-instance-name peer ipv4-address verbose command to check the BGP IPv4 peer relationship established with the CE in the VPN instance IPv6 address family.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 36203

Downloads: 61

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