ipv6 import-route

Function

The ipv6 import-route command configures IS-IS to import IPv6 routes from other protocols.

The undo ipv6 import-route command disables IS-IS from importing IPv6 routes from other protocols.

By default, IS-IS does not import IPv6 routes from any other protocol.

Format

ipv6 import-route { direct | static | unr | { ospfv3 | ripng | isis } [ process-id ] | bgp [ permit-ibgp ] } [ cost cost | tag tag | route-policy route-policy-name | { level-1 | level-2 | level-1-2 } ] ^*

ipv6 import-route { { ripng | isis | ospfv3 } [ process-id ] | direct | unr | bgp [ permit-ibgp ] } inherit-cost [ tag tag | route-policy route-policy-name | [ level-1 | level-2 | level-1-2 ] ] ^*

undo ipv6 import-route { direct | static | unr | { ospfv3 | ripng | isis } [ process-id ] | bgp [ permit-ibgp ] } [ cost cost | tag tag | route-policy route-policy-name | { level-1 | level-2 | level-1-2 } ] ^*

undo ipv6 import-route { { ripng | isis | ospfv3 } [ process-id ] | direct | unr | bgp [ permit-ibgp ] } inherit-cost [ tag tag | route-policy route-policy-name | [ level-1 | level-2 | level-1-2 ] ] ^*

Parameters

Parameter	Description	Value
direct	Indicates that the imported routes are direct routes.	-
static	Indicates that the imported routes are active static routes.	-
unr	Indicates that the imported routes are UNR routes.	-
ospfv3	Specifies the protocol, from which routes are imported, as OSPFv3.	-
ripng	Specifies the protocol, from which routes are imported, as RIPng.	-
isis	Specifies the protocol, from which routes are imported, as IS-IS.	-
process-id	Specifies the process ID of RIPng, IS-IS, or OSPFv3.	The value is an integer ranging from 1 to 65535. By default, the process ID is 1.
bgp	Specifies the protocol, from which routes are imported, as BGP.	-
permit-ibgp	Specifies the imported source route as an IBGP route. If you do not configure this parameter, only the EBGP routes are imported.	-
cost cost	Specifies the cost value of the imported route.	The value is an integer which varies with the cost type. When the cost type is narrow, narrow-compatible, or compatible, the value ranges from 0 to 63. When the cost type is wide or wide-compatible, the value ranges from 0 to 4261412864. The default value is 0. The cost type can be configured using the cost-style command.
tag tag	Indicates the administrative tag assigned to the imported routes.	The value ranges from 1 to 4294967295.
route-policy route-policy-name	Specifies the name of the routing policy.	The name is a string of 1 to 40 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
level-1	Imports the route into Level-1 routing table.	-
level-2	Imports the route into Level-2 routing table.	-
level-1-2	Imports the route into Level-1 and Level-2 routing table. NOTE: If the level of the imported route is not specified in the command, by default, routes are imported to Level-2 routing table.	-
inherit-cost	Retains the original cost of the imported external route. In this case, the cost type and cost value of the imported route cannot be set, and only OSPFv3, RIPng, IS-IS, or BGP routes can be imported.	-

Views

IS-IS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When IS-IS and other routing protocols are running on a network, you can use either of the following methods to allow the traffic within the IS-IS domain to be transmitted to other routing domains:

Configure a boundary router in the IS-IS domain to advertise default routes to the IS-IS domain.
Configure a boundary router in the IS-IS domain to import routes from the other routing domains to the IS-IS domain.

If multiple boundary devices are deployed, optimal routes to other areas need to be selected. To ensure optimal routes to be selected, all the other devices in the IS-IS areas must learn all or some external routes.

In this scenario, you can configure a boundary router in the IS-IS domain to import routes from the other routing domains to the IS-IS domain. Or you can run the route-policy route-policy-name command to import some routes of other routing domains.

Prerequisites

You have run the isis command to enable IS-IS and enter the IS-IS view. You have run the ipv6 enable command to enable IPv6 in the IS-IS process.

Precautions

If routes of other routing protocols are imported, you can configure cost values and types of the imported routes. If original cost values of the routes imported by IS-IS are retained, the original cost values will be used when the routes are advertised or calculated. In this scenario, you cannot configure the cost values and types for the routes imported by IS-IS. The external routes imported by IS-IS cannot be static routes.

This command is valid only for an IPv6 base topology.

Creating a route-policy before it is referenced is recommended. By default, nonexistent route-policies cannot be referenced using the command. If the route-policy nonexistent-config-check disable command is run in the system view and a nonexistent route-policy is referenced using the current command, all IPv6 routes of the specified routing domain are imported to the IS-IS routing table.

Example

# Configure IS-IS to import an IPv6 static route and set the cost of the route to 15.

<sysname> system-view
[sysname] ipv6
[sysname] isis
[sysname-isis-1] ipv6 enable
[sysname-isis-1] ipv6 import-route static cost 15

# Configure IS-IS to import an OSPFv3 route and retain the original cost of the route.

<sysname> system-view
[sysname] ipv6
[sysname] isis
[sysname-isis-1] ipv6 enable
[sysname-isis-1] ipv6 import-route ospfv3 1 inherit-cost