instance-name vpn-instance-name: Displays information about the specified VPN instance. The vpn-instance-name is a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command displays brief information about all VPN instances.

Examples

# Display brief information about all VPN instances.

<Sysname> display ip vpn-instance

Total VPN-Instances configured : 1

VPN-Instance Name RD Create time

abc 1:1 2011/05/18 10:48:17

Table 1 Command output

Field	Description
VPN-Instance Name	Name of the VPN instance.
RD	RD of the VPN instance.
Create Time	Time when the VPN instance was created.

# Display detailed information about VPN instance vpn1.

<Sysname> display ip vpn-instance instance-name vpn1

VPN-Instance Name and Index : vpn1, 2

Route Distinguisher : 100:1

VPN ID : 1:1

Description : vpn1

Interfaces : Vlan-interface2

Address-family IPv4:

Export VPN Targets :

2:2

Import VPN Targets :

3:3

Maximum Routes Limit : 5000

Address-family IPv6:

Export VPN Targets :

2:2

Import VPN Targets :

3:3

Maximum Routes Limit : 5000

domain-id

Use domain-id to configure an OSPF domain ID.

Use undo domain-id to restore the default.

Syntax

domain-id domain-id [ secondary ]

undo domain-id [ domain-id ]

Default

The OSPF domain ID is 0.

Views

OSPF view

Predefined user roles

network-admin

Parameters

domain-id: Specifies an OSPF domain ID, in one of these formats:

· Integer, in the range of 0 to 4294967295. For example, 1.

· Dotted decimal notation. For example, 0.0.0.1.

· Dotted decimal notation:16-bit user-defined number in the range of 0 to 65535. For example, 0.0.0.1:512.

secondary: Specifies a secondary domain ID. If you do not specify this keyword, the command specifies a primary domain ID.

Usage guidelines

When you redistribute OSPF routes into BGP, BGP adds the primary domain ID to the redistributed BGP VPNv4 routes as a BGP extended community attribute. Then, BGP advertises the routes to the peer PE.

When the peer PE receives the routes, it compares the OSPF domain ID in the routes with the locally configured primary and secondary domain IDs. If the primary or secondary domain ID is the same as the received domain ID, and the received routes are intra-area routes, OSPF advertises these routes in Network Summary LSAs (Type 3). Otherwise, OSPF advertises these routes in AS External LSAs (Type 5) or NSSA External LSAs (Type 7).

If you do not specify any parameters, the undo domain-id command deletes all domain IDs.

Examples

# Configure the OSPF domain ID as 234.

<Sysname> system-view

[Sysname] ospf 100

[Sysname-ospf-100] domain-id 234

ext-community-type

Use ext-community-type to configure the type code of an OSPF extended community attribute.

Use undo ext-community-type to restore the default.

Syntax

ext-community-type { domain-id type-code1 | router-id type-code2 | route-type type-code3 }

undo ext-community-type [ domain-id | router-id | route-type ]

Default

The type codes for domain ID, router ID, and route type are hex numbers 0005, 0107, and 0306, respectively.

Views

OSPF view

Predefined user roles

network-admin

Parameters

domain-id type-code1: Specifies the type code for domain ID. Valid values are hex numbers 0005, 0105, 0205, and 8005.

router-id type-code2: Specifies the type code for router ID. Valid values are hex numbers 0107 and 8001.

router-type type-code3: Specifies the type code for route type. Valid values are hex numbers 0306 and 8000.

Examples

# Configure the type codes of domain ID, router ID, and route type as hex numbers 8005, 8001, and 8000, respectively, for OSPF process 100.

<Sysname> system-view

[Sysname] ospf 100

[Sysname-ospf-100] ext-community-type domain-id 8005

[Sysname-ospf-100] ext-community-type router-id 8001

[Sysname-ospf-100] ext-community-type route-type 8000

ip binding vpn-instance

Use ip binding vpn-instance to associate an interface with a VPN instance.

Use undo ip binding vpn-instance to remove the association.

Syntax

ip binding vpn-instance vpn-instance-name

undo ip binding vpn-instance vpn-instance-name

Default

An interface is associated with no VPN instance and belongs to the public network.

Views

Interface view

Predefined user roles

network-admin

Parameters

vpn-instance-name: Specifies a VPN instance by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

Use the command on an MCE to associate the VPN instance with the interface connected to the site and the interface connected to the PE.

This command or its undo form clears the IP address and routing protocol configuration on the interface. After executing this command or its undo form, use the display this command to view the current configuration and reconfigure the IP address and routing protocol on the interface.

The specified VPN instance must have been created by using the ip vpn-instance command in system view.

To associate a new VPN instance with an interface, you must remove the previous association by using the undo ip binding vpn-instance command and then use the ip binding vpn-instance command to associate the new VPN instance with the interface.

Examples

# Associate interface VLAN-interface 1 with VPN instance vpn1.

<Sysname> system-view

[Sysname] interface vlan-interface 1

[Sysname-Vlan-interface1] ip binding vpn-instance vpn1

Related commands

ip vpn-instance (system view)

Use ip vpn-instance to create a VPN instance and enter VPN instance view.

Use undo ip vpn-instance to delete a VPN instance.

Syntax

ip vpn-instance vpn-instance-name

undo ip vpn-instance vpn-instance-name

Default

No VPN instance is created.

Views

System view

Predefined user roles

network-admin

Parameters

vpn-instance-name: Specifies the name of the VPN instance, a case-sensitive string of 1 to 31 characters.

Examples

# Create a VPN instance named vpn1.

<Sysname> system-view

[Sysname] ip vpn-instance vpn1

[Sysname-vpn-instance-vpn1]

Related commands

route-distinguisher

route-distinguisher (VPN instance view)

Use route-distinguisher to configure an RD for a VPN instance.

Use undo route-distinguisher to remove the RD of a VPN instance.

Syntax

route-distinguisher route-distinguisher

undo route-distinguisher

Default

No RD is specified for a VPN instance.

Views

VPN instance view

Predefined user roles

network-admin

Parameters

route-distinguisher: Specifies an RD for the VPN instance, a string of 3 to 21 characters in one of these formats:

· 16-bit AS number:32-bit user-defined number. For example, 101:3.

· 32-bit IP address:16-bit user-defined number. For example, 192.168.122.15:1.

· 32-bit AS number:16-bit user-defined number, where the minimum value of the AS number is 65536. For example, 65536:1.

Usage guidelines

RDs enable VPNs to use the same address space. An RD and an IPv4 prefix comprise a unique VPN IPv4 prefix. You can use RDs to identify different BGP VPN instances on an MCE.

To change the RD of a VPN instance, you must delete the RD with the undo route-distinguisher command, and then use the route-distinguisher command to configure a new RD.

Examples

# Configure RD 22:1 for VPN instance vpn1.

<Sysname> system-view

[Sysname] ip vpn-instance vpn1

[Sysname-vpn-instance-vpn1] route-distinguisher 22:1

route-tag

Use route-tag to configure an external route tag for redistributed VPN routes.

Use undo route-tag to restore the default.

Syntax

route-tag tag-value

undo route-tag

Default

If BGP runs within an MPLS backbone, and the BGP AS number is not greater than 65535, the first two octets of the external route tag are 0xD000, and the last two octets are the local BGP AS number. For example, if the local BGP AS number is 100, the external route tag value is 3489661028 (100 + the decimal value of 0xD0000000). If the AS number is greater than 65535, the external route tag is 0.

Views

OSPF view

Predefined user roles

network-admin

Parameters

tag-value: Specifies an external route tag for redistributed VPN routes, in the range of 0 to 4294967295.

Usage guidelines

In a dual-homed CE scenario where OSPF runs between the CE and the connected PEs (PE-A and PE-B, for example), you can use external route tags to avoid routing loops.

When PE-A redistributes BGP routes received from the peer PE into OSPF, and advertises these routes in the Type 5 or 7 LSAs to the CE, PE-A adds the locally configured external route tag to Type 5 or 7 LSAs.

When PE-B receives the Type 5 or 7 LSAs advertised by the CE, it compares the external route tag in the LSAs with the locally configured tag. If they are the same, PE-B ignores the LSA in route calculation to avoid routing loops.

The commands used to configure the external route tag (in the descending order of tag priority) are as follows:

· import-route

· route-tag

· default tag

H3C recommends configuring the same external route tag for MCEs in the same area.

An external route tag is not transferred in any BGP extended community attribute. It takes effect only on the MCEs that receive BGP routes and generate OSPF Type 5 or 7 LSAs.

You can configure the same external route tag for different OSPF processes.

Examples

# In OSPF process 100, set the external route tag for redistributed VPN routes to 100.

<Sysname> system-view

[Sysname] ospf 100

[Sysname-ospf-100] route-tag 100

Related commands

· default (Layer 3—IP Routing Command Reference)

· import-route (Layer 3—IP Routing Command Reference)

routing-table limit

Use routing-table limit to set the maximum number of active routes in a VPN instance.

Use undo routing-table limit to restore the default.

Syntax

routing-table limit number { warn-threshold | simply-alert }

undo routing-table limit

Default

The number of active routes in a VPN instance is not limited.

Views

VPN instance view, IPv4 VPN view, IPv6 VPN view

Predefined user roles

network-admin

Parameters

number: Specifies the maximum number of active routes, in the range of 1 to 1024.

warn-threshold: Specifies a warning threshold in the range of 1 to 100 in percentage. When the percentage of the number of existing active routes to the maximum number of active routes exceeds the specified threshold, the system gives an alarm message but still allows new active routes. If active routes in the VPN instance reach the maximum, no more active routes are added.

simply-alert: Specifies that when active routes exceed the maximum number, the system still accepts active routes but generates a system log message.

Usage guidelines

A limit configured in VPN instance view applies to both the IPv4 VPN and the IPv6 VPN.

A limit configured in IPv4 VPN view or IPv6 VPN view applies to only the IPv4 VPN or the IPv6 VPN.

If you have specified limits in both IPv4 VPN view and VPN instance view, IPv4 VPN uses the limit specified in IPv4 VPN view.

If you have specified limits in both IPv6 VPN view and VPN instance view, IPv6 VPN uses the limit specified in IPv6 VPN view.

Examples

# Specify that VPN instance vpn1 supports up to 1000 active routes, and when active routes exceed the upper limit, can receive new active routes but generates a system log message.

<Sysname> system-view

[Sysname] ip vpn-instance vpn1

[Sysname-vpn-instance-vpn1] route-distinguisher 100:1

[Sysname-vpn-instance-vpn1] routing-table limit 1000 simply-alert

# Specify that the IPv4 VPN vpn2 supports up to 1000 active routes, and when active routes exceed the upper limit, can receive new active routes but generates a system log message.

<Sysname> system-view

[Sysname] ip vpn-instance vpn2

[Sysname-vpn-instance-vpn2] route-distinguisher 100:2

[Sysname-vpn-instance-vpn2] address-family ipv4

[Sysname-vpn-ipv4-vpn2] routing-table limit 1000 simply-alert

# Specify that the IPv6 VPN vpn3 supports up to 1000 active routes, and when active routes exceed the upper limit, can receive new active routes but generates a system log message.

<Sysname> system-view

[Sysname] ip vpn-instance vpn3

[Sysname-vpn-instance-vpn3] route-distinguisher 100:3

[Sysname-vpn-instance-vpn3] address-family ipv6

[Sysname-vpn-ipv4-vpn3] routing-table limit 1000 simply-alert

vpn-id

Use vpn-id to configure a VPN ID for a VPN instance.

Use undo vpn-id to remove the VPN ID of a VPN instance.

Syntax

vpn-id

undo vpn-id

Default

No VPN ID is configured for a VPN instance.

Views

VPN instance view

Predefined user roles

network-admin

Parameters

vpn-id: Specifies a VPN ID for the VPN instance, in the form of OUI:Index. Both OUI and Index are hex numbers. The OUI is in the range of 0 to FFFFFF, and the index is in the range of 0 to FFFFFFFF.

Usage guidelines

The VPN ID uniquely identifies the VPN instance. Different VPN instances must have different VPN IDs.

The VPN ID cannot be 0:0.

Examples

# Configure VPN ID 20:1 for VPN instance vpn1.

<Sysname> system-view

[Sysname] ip vpn-instance vpn1

[Sysname-vpn-instance-vpn1] vpn-id 20:1

Related commands

display ip vpn-instance

vpn-instance-capability simple

Use vpn-instance-capability simple to disable routing loop detection for an OSPF VRF process.

Use undo vpn-instance-capability to restore the default.

Syntax

vpn-instance-capability simple

undo vpn-instance-capability

Default

Routing loop detection is enabled for an OSPF VRF process.

Views

OSPF view

Predefined user roles

network-admin

Usage guidelines

For the MCE to receive OSPF routes from the PE, you must disable routing loop detection for an OSPF VRF process on the MCE.

This command is applicable only to an OSPF VRF process.

Examples

# Disable routing loop detection for OSPF VRF process 100.

<Sysname> system-view

[Sysname] ospf 100 vpn-instance vpna

[Sysname-ospf-100] vpn-instance-capability simple

vpn-target (VPN instance view/IPv4 VPN view/IPv6 VPN view)

Use vpn-target to configure route targets for a VPN instance.

Use undo vpn-target to remove the specified or all route targets of a VPN instance.

Syntax

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

undo vpn-target { all | vpn-target&<1-8> [ both | export-extcommunity | import-extcommunity ] }

Default

No route targets are configured for a VPN instance.

Views

VPN instance view, IPv4 VPN view, IPv6 VPN view

Predefined user roles

network-admin

Parameters

vpn-target&<1-8>: Specifies a space-separated list of up to eight route targets.

A route target is a string of 3 to 21 characters in one of these formats:

· 16-bit AS number:32-bit user-defined number. For example, 101:3.

· 32-bit IP address:16-bit user-defined number. For example, 192.168.122.15:1.

· 32-bit AS number:16-bit user-defined number, where the AS number must not be less than 65536. For example, 65536:1.

both: Uses the specified route targets as both import targets and export targets. The both keyword is also used when you do not specify any of the following keywords: both, export-extcommunity, and import-extcommunity.

export-extcommunity: Uses the specified route targets as export targets.

import-extcommunity: Uses the specified route targets as import targets.

all: Removes all route targets.

Usage guidelines

MPLS L3VPN uses route targets to control the advertisement of VPN routing information. A PE adds the configured export targets into the route target attribute of routes advertised to a peer. The peer uses the local import targets to match the route targets of received routes. If a match is found, the peer adds the routes to the routing table of the VPN instance.

Route targets configured in VPN instance view are applicable to both the IPv4 VPN and the IPv6 VPN.

Route targets configured in IPv4 VPN view or IPv6 VPN view are applicable to only the IPv4 VPN or IPv6 VPN.

Route targets configured in IPv4 VPN view or IPv6 VPN view take precedence over those configured in VPN instance view. If you configure route targets in both IPv4 VPN view (or IPv6 VPN view) and VPN instance view, the IPv4 VPN or IPv6 VPN uses the route targets configured in IPv4 VPN view or IPv6 VPN view.

Examples

# Configure route targets for VPN instance vpn1.

<Sysname> system-view

[Sysname] ip vpn-instance vpn1

[Sysname-vpn-instance-vpn1] vpn-target 3:3 export-extcommunity

[Sysname-vpn-instance-vpn1] vpn-target 4:4 import-extcommunity

[Sysname-vpn-instance-vpn1] vpn-target 5:5 both

# Configure route targets for the IPv4 VPN vpn2.

<Sysname> system-view

[Sysname] ip vpn-instance vpn2

[Sysname-vpn-instance-vpn2] address-family ipv4

[Sysname-vpn-ipv4-vpn2] vpn-target 3:3 export-extcommunity

[Sysname-vpn-ipv4-vpn2] vpn-target 4:4 import-extcommunity

[Sysname-vpn-ipv4-vpn2] vpn-target 5:5 both

# Configure route targets for the IPv6 VPN vpn3.

<Sysname> system-view

[Sysname] ip vpn-instance vpn3

[Sysname-vpn-instance-vpn3] address-family ipv6

[Sysname-vpn-ipv6-vpn3] vpn-target 3:3 export-extcommunity

[Sysname-vpn-ipv6-vpn3] vpn-target 4:4 import-extcommunity

[Sysname-vpn-ipv6-vpn3] vpn-target 5:5 both

IPv6 MCE commands

For information about the commands available for both MCE and IPv6 MCE, see "MCE commands."

address-family ipv6 (VPN instance view)

Use address-family ipv6 to enter IPv6 VPN view.

Use undo address-family ipv6 to remove all configurations from IPv6 VPN view.

Syntax

address-family ipv6

undo address-family ipv6

Views

VPN instance view

Predefined user roles

network-admin

Usage guidelines

In IPv6 VPN view, you can configure IPv6 VPN parameters.

Examples

# Enter IPv6 VPN view.

<Sysname> system-view

[Sysname] ip vpn-instance vpn1

[Sysname-vpn-instance-vpn1] address-family ipv6

[Sysname-vpn-ipv6-vpn1]

Related commands

address-family ipv4 (VPN instance view)

domain-id

Use domain-id to configure an OSPFv3 domain ID.

Use undo domain-id to restore the default.

Syntax

domain-id { domain-id [ secondary ] | null }

undo domain-id [ domain-id | null ]

Default

The OSPFv3 domain ID is 0.

Views

OSPFv3 view

Predefined user roles

network-admin

Parameters

domain-id: Specifies an OSPFv3 domain ID, in one of the following formats:

· Integer, in the range of 0 to 4294967295. For example, 1.

· Dotted decimal notation. For example, 0.0.0.1.

· Dotted decimal notation:16-bit user-defined number in the range of 0 to 65535. For example, 0.0.0.1:512.

secondary: Specifies a secondary domain ID. If you do not specify this keyword, the command specifies a primary domain ID.

null: Carries no domain ID in the community attribute.

Usage guidelines

When you redistribute OSPFv3 routes into BGP, BGP adds the primary domain ID to the redistributed BGP VPNv6 routes as a BGP extended community attribute. Then, BGP advertises the routes to the peer PE.

When the peer PE receives the routes, it compares the OSPFv3 domain ID in the routes with the locally configured primary and secondary domain IDs. If the primary or secondary domain ID is the same as the received domain ID, and the received routes are intra-area or inter-area routes, OSPFv3 advertises these routes in Inter-Area-Prefix LSAs (Type 3 LSAs). Otherwise, OSPFv3 advertises these routes in AS External LSAs (Type 5 LSAs) or NSSA External LSAs (Type 7 LSAs).

A null domain ID and a domain ID of 0 are considered the same in domain ID comparison.

You cannot configure a secondary domain ID when the primary domain ID is configured as 0.

With no parameters specified, the undo domain-id command deletes all domain IDs.

This command takes effect only for an OSPFv3 VRF process that is not configured with the vpn-instance-capability simple command.

Examples

# Configure the primary domain ID for OSPFv3 VRF process 100 as 1.1.1.1.

<Sysname> system-view

[Sysname] ospfv3 100 vpn-instance vpn1

[Sysname-ospfv3-100] domain-id 1.1.1.1

Related commands

display ospfv3 (Layer 3—IP Routing Command Reference)

vpn-instance-capability simple

Use vpn-instance-capability simple to disable routing loop detection for an OSPFv3 VRF process.

Use undo vpn-instance-capability to restore the default.

Syntax

vpn-instance-capability simple

undo vpn-instance-capability

Default

Routing loop detection is enabled for an OSPFv3 VRF process.

Views

OSPFv3 view

Predefined user roles

network-admin

Usage guidelines

For the MCE to receive OSPFv3 routes from the PE, you must disable routing loop detection for an OSPFv3 VRF process on the MCE.

This command is applicable only to an OSPFv3 VRF process.

Examples

# Disable routing loop detection for OSPFv3 VRF process 100.

<Sysname> system-view

[Sysname] ospfv3 100 vpn-instance vpn1

[Sysname-ospfv3-100] vpn-instance-capability simple

07-MCE Command Reference

MCE commands

address-family ipv4 (VPN instance view)

description (VPN instance view)

display ip vpn-instance

domain-id

ext-community-type

ip binding vpn-instance

ip vpn-instance (system view)

route-distinguisher (VPN instance view)

route-tag

routing-table limit

vpn-id

vpn-instance-capability simple

vpn-target (VPN instance view/IPv4 VPN view/IPv6 VPN view)

IPv6 MCE commands

address-family ipv6 (VPN instance view)

domain-id

vpn-instance-capability simple

Cloud & AI

InterConnect

Intelligent Computing

Security

SMB Products

Intelligent Terminal Products

Industry Solutions

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Training & Certification

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Online Exhibition Center

Contact Us