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 - IP Routing 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - IP Routing
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 the Advertisement of IPv6 NDP Vlink Direct Routes on the Public Network

Configuring the Advertisement of IPv6 NDP Vlink Direct Routes on the Public Network

On an IPv6 public network, advertising IPv6 neighbor discover protocol (NDP) Vlink direct routes allows precise control of data traffic.

Applicable Environment

IP packets are forwarded through a specified physical interface, but cannot be forwarded through a logical interface. If packets reach a logical interface, the device obtains information about the layer-3 interfaces using IPv6 NDP and generates relevant routing entries. The routes recorded by the routing entries are called IPv6 NDP Vlink direct routes.

As shown in Figure 2-8, Device D uses logical interfaces to connect to Devices A, B, and C at three sites. Device E only needs to communicate with Device B, but not with Device A and Device C. You can configure Device D to advertise IPv6 NDP Vlink direct routes and configure a route-policy on Device D to filter out routes to the network segment of the VLAN for which the logical interfaces are configured and filter out routes to Device A and Device C.

Figure 2-8 Networking diagram of advertising IPv6 NDP Vlink direct routes on the public network

Before IPv6 NDP Vlink direct routes are advertised, a route-policy can be used to filter the advertised routes and only routes that pass the filtering can be advertised. In this manner, data traffic can be precisely controlled.

Perform the following steps on the NE on which IPv6 NDP Vlink direct routes need to be advertised.

Pre-configuration Tasks

Before advertising IPv6 NDP Vlink direct routes on the public network, complete the following task:

  • Configuring parameters of a link layer protocol and assigning an IP address to each interface to ensure that the link layer protocol on the interfaces is Up

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ipv6 nd vlink-direct-route advertise [ route-policy route-policy-name | route-filter route-filter-name ]

    Advertising IPv6 NDP Vlink direct routes is enabled.

    By default, IPv6 NDP Vlink direct routes cannot be advertised.

    If IPv6 NDP Vlink direct routes have to be advertised, you can specify the parameter route-policy route-policy-name or route-filter route-filter-name in the ipv6 nd vlink-direct-route advertise command to filter IPv4 ARP Vlink direct routes.
    NOTE:

    At present, apply clauses cannot be used to set routing attributes for the NDP Vlink direct routes that match the filtering rules.

  3. Run commit

    The configuration is committed.

    After advertising IPv6 NDP Vlink direct routes is enabled, IPv6 NDP Vlink direct routes can be advertised only if they are imported to dynamic routing protocols. Perform the following steps on the NE based on the type of the dynamic routing protocol:
    • If RIPng is used, run the import-route direct [ cost cost | route-policy route-policy-name ] * command to import IPv6 NDP Vlink direct routes to RIPng.
    • If OSPFv3 is used, run the import-route direct [ cost cost | inherit-cost | route-policy route-policy-name | tag tag | type type ] * command to import IPv6 NDP Vlink direct routes to OSPFv3.
    • If IS-IS is used, run the import-route direct [ cost-type { external | internal } | cost cost | tag tag | route-policy route-policy-name | [ level-1 | level-2 | level-1-2 ] ] * command to import IPv6 NDP Vlink direct routes to IS-IS.
    • If BGP4+ is used, run the import-route direct [ med med | route-policy route-policy-name ] * command to import IPv6 NDP Vlink direct routes to BGP4+.

Checking the Configurations

Run the display ipv6 routing-table ipv6-address [ prefix-length ] [ longer-match ] [ verbose ] command to check information about advertised IPv6 NDP Vlink direct routes on the public network.

# Run the display ipv6 routing-table ipv6-address [ mask | mask-length ] verbose command to view detailed information about the IPv6 NDP Vlink direct route 2000::4/128.

<HUAWEI> display ipv6 routing-table 2001:db8:2000::4 128 verbose
Routing Table : _Public_
Summary Count : 1

 Destination  : 2001:db8:2000::4                PrefixLength : 128
 NextHop      : 2001:db8:2000::4                Preference   : 0
 Neighbour    : ::                              ProcessID    : 0
 Label        : NULL                            Protocol     : Direct
 State        : Active Adv                     Cost         : 0
 Entry ID     : 266288988                       EntryFlags   : 0xa0010050
 Reference Cnt: 2                               Tag          : 0
 Priority     : high                            Age          : 15sec
 IndirectID   : 0x0
 RelayNextHop : ::                              TunnelID     : 0x0
 Interface    : Vlanif10                        Flags        : D

The command output shows that the route status is Active Adv, indicating that the route is active and can be advertised.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058916

Views: 35105

Downloads: 51

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