ip unr net-route import source vpn-instance destination vpn-instance
Function
The ip unr net-route import source vpn-instance destination vpn-instance command configures a VPN-based import-policy for BAS UNR address pool subnet routes.
The undo ip unr net-route import source vpn-instance destination vpn-instance command cancels the configuration.
By default, the VPN-based import-policy for BAS UNR IPv4 address pool subnet routes is not configured.
This command is supported only on the NetEngine 8000 F1A.
Parameters
| Parameter | Description | Value |
|---|---|---|
| vpn-instance source-vpn-name |
Specifies a source vpn-instance name. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. |
| vpn-instance destination-vpn-name |
Specifies a destination vpn-instance name. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. |
Usage Guidelines
Usage Scenario
When the BAS user side and network side are on different VPNs, you can run this command to configure VPN-based auto-cross-connection policy for IPv4 address pool routes so that the address pool subnet routes in a user-side VPN can be imported to the networks-side VPN through cross-connections. In this case, the interface in the network-side VPN routing table is in the user-side VPN. This configuration remove the inconvenience caused by synchronizing the static route configurations updated in the address pool subnet or VPN.
Configuration Impact
Configuring this policy increases the number of address pool subnet routes on a device. When there are large number of address pools, this may lead to significant increase of the device's memory usage. Therefore, exercise caution when performing this configuration.
Precautions
- This command applies only to address pool subnet routes, instead of other UNRs.
- If the export host-route command has been executed in the IPv4 address pool, subnet routes will be withdrawn and the subnet routes generated during the corresponding cross-connection will also be withdrawn.
- When a route conflict occurs after multiple VPN-based auto-cross-connection policies for IPv4 address pool routes are configured, the routes generated after the conflict do not take effect. After the routes generated before the conflict are revoked, the routes generated after the conflict still fail to take effect. To resolve the preceding route conflict, you can delete the address pool configuration or VPN-based auto-cross-connection policy and then perform reconfiguration.
- In VS mode, this command applies only to admin VS.
Example
<HUAWEI> system-view [~HUAWEI] ip vpn-instance VPN1 [*HUAWEI-vpn-instance-VPN1] ipv4-family [*HUAWEI-vpn-instance-VPN1-af-ipv4] commit [~HUAWEI-vpn-instance-VPN1-af-ipv4] quit [~HUAWEI-vpn-instance-VPN1] quit [~HUAWEI] ip vpn-instance VPN2 [*HUAWEI-vpn-instance-VPN2] ipv4-family [*HUAWEI-vpn-instance-VPN2-af-ipv4] commit [~HUAWEI-vpn-instance-VPN2-af-ipv4] quit [~HUAWEI-vpn-instance-VPN2] quit [~HUAWEI] ip unr net-route import source vpn-instance VPN1 destination vpn-instance VPN2