nd vlink-direct-route advertise

Function

The nd vlink-direct-route advertise command advertises NDP Vlink direct routes in a VPN instance IPv6 address family.

The undo nd vlink-direct-route advertise command restores the default setting.

By default, NDP Vlink direct routes are not advertised in a VPN instance IPv6 address family.

Format

nd vlink-direct-route advertise [ route-policy route-policy-name | route-filter route-filter-name ]

undo nd vlink-direct-route advertise

Parameters

Parameter Description Value
route-policy route-policy-name

Specifies the name of a route-policy that is used to filter NDP Vlink direct routes in a VPN instance IPv6 address family.

The name is a string of 1 to 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. It must be a unique value.

route-filter route-filter-name

Specifies the name of a route-filter used to filter NDP Vlink direct routes in the VPN instance IPv6 address family.

The value is a string of 1 to 200 case-sensitive characters, spaces not supported. If parameters are included in the referenced route-filter, specify values for them in the format of (var1, var2, ...var8) behind the route-filter name. A maximum of eight parameters can be specified, and each value ranges from 1 to 200 characters.

Views

VPN instance IPv6 address family view

Default Level

2: Configuration level

Task Name and Operations

Task Name Operations
eum write

Usage Guidelines

Usage Scenario

By default, IPv6 NDP Vlink direct routes are only used for packet forwarding in the same VLAN and cannot be imported to dynamic routing protocols. This is because importing Vlink direct routes to dynamic routing protocols will increase the number of routing entries and affect routing table stability. In some cases, some operations need to be performed based on Vlink direct routes of VLAN users. For example, different VLAN users use different route exporting policies to guide traffic from the remote device. In this scenario, IPv6 NDP Vlink direct routes are needed to be imported by a dynamic routing protocol and advertised to the remote device. After advertisement of IPv6 NDP Vlink direct routes is enabled, these direct routes can be imported by a dynamic routing protocol (IGP or BGP) and advertised to the remote device.

In a VPN, a local PE connects to multiple CEs using VLANIF interfaces. Based on NDP, the local PE learns IP addresses of these CEs and advertises NDP Vlink direct routes.

If NDP Vlink direct routes to a few CEs have to be advertised, you can configure the nd vlink-direct-route advertise command with route-policy-name or route-filter-name specified. This configuration allows the device to advertise only the NDP Vlink direct routes that match the route-policy, which controls the routing table size and guarantees the security of users.

Configuration Impact

After route-policy-name or route-filter-name is specified in the nd vlink-direct-route advertise command, the device advertises only the NDP Vlink direct routes that match the route-policy.

Follow-up Procedure

Import NDP Vlink direct routes to the routing table of each dynamic routing protocol on the Router so that they can be advertised by each dynamic routing protocol module.

Precautions

Route-policies and route-filters can filter NDP Vlink direct routes only based on IPv4 or IPv6 route prefixes.

The route-policy route-policy-name parameter must be specified in the nd vlink-direct-route advertise command. If the parameter is not specified, NDP Vlink direct routes cannot be filtered.

The specified route-filter must have been configured; otherwise, it cannot be used to filter NDP Vlink direct routes.

Example

# Advertise NDP Vlink direct routes that match the route-policy named rp1 in the VPN instance named vrf1.
<HUAWEI> system-view
[~HUAWEI] route-policy rp1 permit node 10
[*HUAWEI-route-policy] quit
[*HUAWEI] ip vpn-instance vrf1
[*HUAWEI-vpn-instance-vrf1] ipv6-family
[*HUAWEI-vpn-instance-vrf1-af-ipv6] nd vlink-direct-route advertise route-policy rp1
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >