H3C S5820V2 series Installation manual

H3C S5830V2 & S5820V2 Switch Series
MCE Command Reference
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: Release 22xx
Document version: 6W100-20131105

Copyright © 2013, Hangzhou H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior
written consent of Hangzhou H3C Technologies Co., Ltd.
Trademarks
H3C, , Aolynk, , H3Care, , TOP G, , IRF, NetPilot, Neocean, NeoVTL,
SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V2G, VnG, PSPT,
XGbus, N-Bus, TiGem, InnoVision and HUASAN are trademarks of Hangzhou H3C Technologies Co.,
Ltd.
All other trademarks that may be mentioned in this manual are the property of their respective owners
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Preface
The H3C S5830V2 & S5820V2 documentation set includes 14 command references, which describe the
commands and command syntax options available for the H3C S5830V2 & S5820V2 Switch Series.
The MCE Command Reference describes the MCE configuration commands.
This preface includes:
•Audience
•Added and modified commands
•Conventions
•About the H3C S5830V2 & S5820V2 documentation set
•Obtaining documentation
•Technical support
•Documentation feedback
Audience
This documentation is intended for:
•Network planners
•Field technical support and servicing engineers
•Network administrators working with the S5830V2 & S5820V2 series
Added and modified commands
This documentation set is for Release 22xx. The following describes the command changes between
releases:
•Release 2210 does not have command changes over Release 2208P01.
•Release 2208P01 does not have command changes over Release 2208.
•Release 2208 has the following command changes over Release 2108P02:

Command reference Added and modified commands
MCE
Modified commands:
•display bgp vpnv4 vpn-instance group changed to display bgp group
ipv4 vpn-instance.
•display bgp vpnv4 vpn-instance peer changed to display bgp peer ipv4
vpn-instance.
•refresh bgp vpn-instance changed to refresh bgp ipv4 vpn-instance.
•reset bgp vpn-instance changed to reset bgp ipv4 vpn-instance.
•routing-table limit: The configuration views for this command changed to
VPN instance view, IPv4 VPN view, and IPv6 VPN view. The value range
for the number argument of this command is 1 to 8192 in VPN instance
view, 1 to 16384 in IPv4 VPN view, and 1 to 8192 in IPv6 VPN view.
IPv6 MCE Added commands: IPv6 MCE commands.
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Descri
p
tion
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars, from
which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select at least one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.
&<1-n> The argument or keyword and argument combination before the ampersand (&) sign can
be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Convention Descri
p
tion
Boldface Window names, button names, field names, and menu items are in bold text. For
example, the New User window appears; click OK.
> Multi-level menus are separated by angle brackets. For example, File >Create >Folder.

Symbols
Convention Descri
p
tion
WARNING An alert that calls attention to important information that if not understood or followed can
result in personal injury.
CAUTION An alert that calls attention to important information that if not understood or followed can
result in data loss, data corruption, or damage to hardware or software.
IMPORTANT An alert that calls attention to essential information.
NOTE An alert that contains additional or supplementary information.
TIP An alert that provides helpful information.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your switch.
About the H3C S5830V2 & S5820V2
documentation set
The H3C S5830V2&S5820V2 documentation set includes:
Cate
g
or
y
Documents Pur
p
oses
Hardware specifications
and installation
Compliance and safety
manual
Provides regulatory information and the safety
instructions that must be followed during installation.
Installation quick start Provides basic installation instructions.
Installation guide Provides a complete guide to hardware installation
and hardware specifications.
Fan assemblies
installation manual
Describes the appearance, specifications, and
installation and removal of hot-swappable fan
assemblies.
Power modules user
manual
Describes the appearance, specifications, and
installation and removal of hot-swappable power
modules.
Software configuration
Configuration guides Describe software features and configuration
procedures.
Command references Provide a quick reference to all available
commands.

Obtaining documentation
You can access the most up-to-date H3C product documentation on the World Wide Web
at http://www.h3c.com.
Click the links on the top navigation bar to obtain different categories of product documentation:
[Technical Support & Documents > Technical Documents] – Provides hardware installation, software
upgrading, and software feature configuration and maintenance documentation.
[Products & Solutions] – Provides information about products and technologies.
[Technical Support & Documents > Software Download] – Provides the documentation released with the
software version.
Technical support
servi[email protected]
http://www.h3c.com
Documentation feedback
You can e-mail your comments about product documentation to [e-mail].
We appreciate your comments.

i
Contents
MCE configuration commands···································································································································· 1
description·································································································································································1
display bgp group ipv4 vpn-instance·····················································································································1
display bgp peer ipv4 vpn-instance ·······················································································································3
display ip vpn-instance ············································································································································5
domain-id ··································································································································································6
export route-policy····················································································································································7
ext-community-type ···················································································································································8
import route-policy····················································································································································9
ip binding vpn-instance········································································································································· 10
ip vpn-instance······················································································································································· 11
ipv4-family······························································································································································ 11
route-distinguisher·················································································································································· 12
route-tag ································································································································································· 13
routing-table limit ··················································································································································· 14
vpn-instance-capability simple······························································································································ 15
vpn-target································································································································································ 15
IPv6 MCE configuration commands ·························································································································18
display bgp group ipv6 vpn-instance·················································································································· 18
display bgp peer ipv6 vpn-instance ···················································································································· 20
ipv6-family······························································································································································ 22
Index ···········································································································································································24

1
MCE configuration commands
description
Use description to configure a description for a VPN instance.
Use undo description to delete the description.
Syntax
description text
undo description
Default
No description for a VPN instance is configured.
Views
VPN instance view
Predefined user roles
network-admin
Parameters
text: Description for the VPN instance, a string of 1 to 79 case-sensitive characters.
Usage guidelines
If you perform this command multiple times, the last configuration takes effect.
Examples
# Configure a description of This is vpn1 for VPN instance vpn1.
<Sysname> system-view
[Sysname] ip vpn-instance vpn1
[Sysname-vpn-instance-vpn1] description This is vpn1
display bgp group ipv4 vpn-instance
Use display bgp group ipv4 vpn-instance to display BGP VPNv4 peer group information.
Syntax
display bgp group ipv4 vpn-instance vpn-instance-name [ group-name ]
Views
Any view
Predefined user roles
network-admin
network-operator

2
Views
Any view
Parameters
vpn-instance vpn-instance-name: Specifies the name of a VPN instance, a string of 1 to 31 case-sensitive
characters.
group-name: Specifies the name of a BGP peer group, a string of 1 to 47 case-sensitive characters. If no
peer group is specified, this command displays information about all peer groups.
Examples
# Display information about all BGP peer groups for VPN instance vpn1.
<Sysname> display bgp group ipv4 vpn-instance vpn1
BGP peer group: grp1
Remote AS number: Not specified
Type: external
Members:
10.1.1.1
BGP peer group: grp2
Remote AS: 100
Type: internal
Members:
1.1.1.1
# Display information about the BGP VPNv4 peer group grp1 for VPN instance vpn1.
<Sysname> display bgp group ipv4 vpn-instance vpn1 grp1
BGP peer group: grp1
Remote AS number: Not specified
Type: external
Maximum allowed prefix number: 4294967295
Threshold: 75%
Configured hold timer value: 180 seconds
Keepalive timer value: 60 seconds
Minimum time between advertisements: 30 seconds
Peer preferred value: 0
Routing policy configured:
No routing policy is configured
Members:
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
10.1.1.1 10 0 0 0 0 00:01:02 Connect
Table 1 Output description
Field Descri
p
tion
BGP peer-group Name of the BGP VPNv4 peer group.
remote AS number Number of the remote AS.

3
Field Descri
p
tion
Type Peer group type, external or internal.
Maximum allowed prefix number Maximum number of routes that the VPN instance supports.
Threshold Threshold value.
If the threshold is reached, the device generates prompt information.
MsgRcvd Number of messages received.
MsgSent Number of messages sent.
OutQ Number of messages waiting to be sent to the peer.
PrefRcv Number of prefixes received.
Up/Down Duration of the BGP session in the current state.
display bgp peer ipv4 vpn-instance
Use display bgp peer ipv4 vpn-instance to display information about BGP peers.
Syntax
display bgp peer ipv4 vpn-instance vpn-instance-name [ group-name log-info | ip-address { log-info |
verbose } | verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
vpn-instance vpn-instance-name: Specifies the name of a VPN instance, a string of 1 to 31 case-sensitive
characters.
ip-address: Specifies the IP address of a peer. If no peer is specified, this command displays all peers.
verbose: Displays detailed information.
group-name: Specifies the name of a peer group, a string of 1 to 47 case-sensitive characters.
log-info: Displays log information for the specified peer or peer group.
Usage guidelines
If no parameters are specified, this command displays brief information about all BGP peers in the
specified VPN.
Examples
# Display information about the BGP peers for the VPN instance vpn1.
<Sysname> display bgp peer ipv4 vpn-instance vpn1
BGP local router ID : 2.2.2.2
Local AS number : 100
Total number of peers : 1 Peers in established state : 1

4
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
10.1.1.1 200 24 29 0 1 00:18:47 Established
Table 2 Output description
Field Descri
p
tion
BGP Local router ID Router ID of the local BGP router
local AS number Local AS number
Total number of peers Total number of peers
Peers in established state Number of peers in Established state
Peer IP address of the peer
AS AS number of the peer group
MsgRcvd Number of messages received
MsgSent Number of messages sent
OutQ Number of messages waiting to be sent to the peer
PrefRcv Number of received prefixes
Up/Down Duration of the BGP session in the current state
State Status of the peer
# Display detailed information about BGP peers for VPN instance vpn1.
<Sysname> display bgp peer ipv4 vpn-instance vpn1 verbose
Peer: 10.1.1.1 Local: 10.1.1.2
Type: EBGP link
BGP version 4, remote router ID 0.0.0.0
BGP current state: Connect
BGP current event: CRTimerExpired
BGP last state: Connect
Received: Total 0 messages, Update messages 0
Sent: Total 0 messages, Update messages 0
Maximum allowed prefix number: 12345
Threshold: 23%
Minimum time between advertisements is 30 seconds
Optional capabilities:
Multi-protocol extended capability has been enabled
Route refresh capability has been enabled
Peer preferred value: 0
# D i s p l a y l o g i n f o r m a t i o n f o r B G P p e e r 10 .1.1.1 i n V P N i n s t a n c e vpn1.
<Sysname> display bgp peer ipv4 vpn-instance vpn1 10.1.1.1 log-info
Peer : 10.1.1.1
Date Time State Notification
Error/SubError

5
27-Mar-2011 15:36:12 Down Receive notification with error 6/4
Cease/Administrative Reset
27-Mar-2011 15:34:29 Up
display ip vpn-instance
Use display ip vpn-instance to display information about VPN instances.
Syntax
display ip vpn-instance [ instance-name vpn-instance-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
instance-name vpn-instance-name: Specifies the name of a VPN instance, a string of 1 to 31
case-sensitive characters. If no VPN is specified, the command displays brief information about all VPN
instances.
Examples
# Display 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 3 Output description
Field Descri
p
tion
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 ID : vpn1, 1
Route Distinguisher : 100:1
Description : vpn for rd
Interfaces : Vlan-interface2
Ipv4-family:
Export VPN Targets :
3:3
Import VPN Targets :
3:3
Maximum Routes Limit : 4000
Threshold Value(%): 20

6
Ipv6-family:
Export VPN Targets :
2:2
Import VPN Targets :
2:2
Maximum Routes Limit : 2000
Threshold Value(%): 50
Table 4 Output description
Field Descri
p
tion
Interfaces Interface to which the VPN instance is bound.
Ipv4-family IPv4 VPN information.
Ipv6-family IPv6 VPN information.
Export VPN Targets Export route target attribute of the VPN.
Import VPN Targets Import route target attribute of the VPN.
Threshold Value(%)
Threshold for warning. When the percentage of the number of the received
route prefixes to the maximum number of routes supported reaches this
value, the device generates a prompt.
If no threshold is configured, this field is not displayed.
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 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 the domain ID as secondary. Without this keyword, the domain ID is primary.

7
Usage guidelines
When you redistribute OSPF routes into BGP on the MCE, BGP adds the configured OSPF domain ID to
the redistributed BGP VPN routes as a BGP extended community attribute and advertises the routes to the
BGP peer. When you redistribute the BGP VPN routes into OSPF on the BGP peer, OSPF uses the domain
ID to determine whether the routes belong to the same OSPF routing domain. If the domain ID is the same
and the routes are intra-area or inter-area routes, OSPF advertises these routes in Type-3 LSAs. If the
domain ID is the same but the routes are not intra-area or inter-area routes, OSPF advertises these routes
in Type-5 or Type-7 LSAs. If the domain ID is different, OSPF advertises the routes in Type-5 or Type-7
LSAs.
With no parameter specified, the undo domain-id command deletes all domain IDs.
Examples
# Configure the OSPF domain ID as 234 for VPN instance vpn1.
<Sysname> system-view
[Sysname] ospf 100 vpn-instance vpn1
[Sysname-ospf-100] domain-id 234
export route-policy
Use export route-policy to apply a routing policy to filter outgoing routes for the VPN instance. Such a
routing policy is referred to as an export routing policy.
Use undo export route-policy to remove the application.
Syntax
export route-policy route-policy
undo export route-policy
Default
No routing policy is applied to filter the routes to be advertised.
Views
VPN instance view, IPv4 VPN view, IPv6 VPN view
Predefined user roles
network-admin
Parameters
route-policy: Specifies the name of a routing policy, a case-sensitive string of 1 to 63 characters.
Usage guidelines
Use this command to apply a routing policy to a VPN instance for more precise and flexible route
advertisement of the VPN instance. When the device advertises routes of the VPN instance, it filters the
advertised routes and modifies attributes for the advertised routes according to the specified routing
policy.
Note the following guidelines when you use this command:
•If you execute this command multiple times, the most recent configuration takes effect.
•A routing policy specified in VPN instance view applies to both the IPv4 VPN and IPv6 VPN. A
routing policy specified in IPv4 VPN view applies only to the IPv4 VPN. A routing policy specified
in IPv6 VPN view applies only to the IPv6 VPN.

8
•A routing policy specified in IPv4 VPN view or IPv6 view takes precedence over that specified in
VPN instance view. If you specify a routing policy in both IPv4 VPN view (or IPv6 VPN view) and
VPN instance view, the IPv4 VPN (IPv6 VPN) uses the policy specified in IPv4 VPN view (IPv6 VPN
view).
Examples
# Apply export routing policy poly-1 to VPN instance vpn1.
<Sysname> system-view
[Sysname] ip vpn-instance vpn1
[Sysname-vpn-instance-vpn1] export route-policy poly-1
# Apply export routing policy poly-2 to the IPv4 VPN of VPN instance vpn2.
<Sysname> system-view
[Sysname] ip vpn-instance vpn2
[Sysname-vpn-instance-vpn2] ipv4-family
[Sysname-vpn-ipv4-vpn2] export route-policy poly-2
# Apply export routing policy poly-3 to the IPv6 VPN of VPN instance vpn3.
<Sysname> system-view
[Sysname] ip vpn-instance vpn3
[Sysname-vpn-instance-vpn3] ipv6-family
[Sysname-vpn-ipv6-vpn3] export route-policy poly-3
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 the OSPF extended community attributes of Domain ID, Router ID, and Route Type are
0x0005, 0x0107, and 0x0306, respectively.
Views
OSPF view
Predefined user roles
network-admin
Parameters
domain-id type-code1: Specifies the type code for the OSPF extended community attribute of Domain ID.
Valid values are 0x0005, 0x0105, 0x0205, and 0x8005.
router-id type-code2: Specifies the type code for the OSPF extended community attribute of Router ID.
Valid values are 0x0107 and 0x8001.
router-type type-code3: Specifies the type code for the OSPF extended community attribute of Route
Type. Valid values are 0x0306 and 0x8000.

9
Examples
# Configure the type codes of OSPF extended community attributes Domain ID, Router ID, and Route
Type as 0x8005, 0x8001, and 0x8000, 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
import route-policy
Use import route-policy to apply a routing policy to filter incoming routes for the VPN instance. Such a
routing policy is referred to as an import routing policy.
Use undo import route-policy to remove the application.
Syntax
import route-policy route-policy
undo import route-policy
Default
No import routing policy is applied to a VPN instance. All routes matching the import target attribute are
accepted.
Views
VPN instance view, IPv4 VPN view, IPv6 VPN view
Predefined user roles
network-admin
Parameters
route-policy: Specifies the name of a routing policy, a case-sensitive string of 1 to 63 characters.
Usage guidelines
Use this command to apply a routing policy to a VPN instance for more precise and flexible route
reception of the VPN instance. When the device receives routes of the VPN instance, it filters the received
routes and modifies attributes for the received routes according to the specified routing policy.
Note the following guidelines when you use this command:
•If you execute this command multiple times, the most recent configuration takes effect.
•A routing policy specified in VPN instance view applies to both the IPv4 VPN and IPv6 VPN. A
routing policy specified in IPv4 VPN view applies only to the IPv4 VPN. A routing policy specified
in IPv6 VPN view applies only to the IPv6 VPN.
•A routing policy specified in IPv4 VPN view or IPv6 view takes precedence over that specified in
VPN instance view. If you specify a routing policy in both IPv4 VPN view (or IPv6 VPN view) and
VPN instance view, the IPv4 VPN (IPv6 VPN) uses the policy specified in IPv4 VPN view (IPv6 VPN
view).
Examples
# Apply import routing policy poly-1 to VPN instance vpn1.
<Sysname> system-view

10
[Sysname] ip vpn-instance vpn1
[Sysname-vpn-instance-vpn1] import route-policy poly-1
# Apply import routing policy poly-2 to the IPv4 VPN of VPN instance vpn2.
<Sysname> system-view
[Sysname] ip vpn-instance vpn2
[Sysname-vpn-instance-vpn2] ipv4-family
[Sysname-vpn-ipv4-vpn2] import route-policy poly-2
# Apply import routing policy poly-3 to the IPv6 VPN of VPN instance vpn3.
<Sysname> system-view
[Sysname] ip vpn-instance vpn3
[Sysname-vpn-instance-vpn3] ipv6-family
[Sysname-vpn-ipv6-vpn3] import route-policy poly-3
Related commands
•export route-policy
•route-policy (Layer 3—IP Routing Command Reference)
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
Default
No VPN instance is associated with an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
vpn-instance-name: Specifies the name of a VPN instance, a string of 1 to 31 case-sensitive characters.
Usage guidelines
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.

11
Examples
# Associate VLAN-interface 2 with the VPN instance vpn1.
<Sysname> system-view
[Sysname] interface vlan-interface 2
[Sysname-Vlan-interface2] ip binding vpn-instance vpn1
Related commands
ip vpn-instance (system view)
ip vpn-instance
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 a VPN instance, a string of 1 to 31 case-sensitive characters.
Examples
# Create a VPN instance named vpn1.
<Sysname> system-view
[Sysname] ip vpn-instance vpn1
[Sysname-vpn-instance-vpn1]
Related command
route-distinguisher
ipv4-family
Use ipv4-family to enter IPv4 VPN view.
Use undo ipv4-family to remove all the configurations in IPv4 VPN view.
Syntax
ipv4-family
undo ipv4-family

12
Views
VPN instance view
Predefined user roles
network-admin
Usage guidelines
In IPv4 VPN view, you can configure parameters such as inbound and outbound routing policies for the
VPN.
Examples
# Enter IPv4 VPN view.
<Sysname> system-view
[Sysname] ip vpn-instance vpn1
[Sysname-vpn-instance-vpn1] ipv4-family
[Sysname-vpn-ipv4-vpn1]
route-distinguisher
Use route-distinguisher to configure a route distinguisher (RD) for a VPN instance.
Use undo route-distinguisher to delete the RD for 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 the RD for the VPN instance, a string of 3 to 21 characters in one of the
following formats:
•16 - b i t A S n u m b e r :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 overlapping address space. By prefixing an RD to an IPv4 prefix for a VPN, you
make the VPN IPv4 prefix globally unique. On an MCE device, when multiple BGP VPN instances are
configured, you can configure RDs for the VPN instances to distinguish them.

13
NOTE:
To change the RD for a VPN instance, you must first delete the RD with the undo route-distinguisher
command, and then configure a new RD for the VPN instance with the route-distinguisher command.
Examples
# Configure an RD 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 a 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 AS number is not greater than 65535, the first two octets of the default route tag is always
0xD000 and the last two octets are the AS number of the local BGP. For example, if the local BGP AS
number is 100, the default VPN route tag is 3489661028 in decimal. If the BGP AS number is greater
than 65535, the default route tag is 0.
Views
OSPF view
Predefined user roles
network-admin
Parameters
tag-value: Specifies the VPN route tag in the range of 0 to 4294967295.
Usage guidelines
On an MCE device, you can configure a VPN route tag for a VPN instance bound to an OSPF process.
The VPN route tag must be included in Type-5 or Type-7 LSAs. H3C recommends configuring the same
VPN route tag for MCEs in the same area.
The VPN route tag is not transferred in any BGP extended community attribute. It is locally significant and
needs to be configured and takes effect only on the MCEs that receive BGP routes and generate OSPF
Type-5 or Type-7 LSAs.
You can configure the same VPN route tag for different OSPF processes.
A route tag can be configured by different commands and has different priorities. 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