H3C S6800 Series Installation manual

H3C S6800 Switch Series
MCE Command Reference
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: Release 2407
Document version: 6W100-20131205

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, , H3CS, H3CIE, H3CNE, Aolynk, , H3Care, , IRF, NetPilot, Netflow,
SecEngine, SecPath, SecCenter, SecBlade, Comware, ITCMM 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 S6800 documentation set includes 9 command references, which describe the commands and
command syntax options available for the H3C S6800 Switch Series.
The MCE Command Reference describes the MCE configuration commands.
This preface includes:
•Audience
•Conventions
•About the H3C S6800 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 S6800 series
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.

Convention Descri
p
tion
# 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 Boldface. 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.
Network topology icons
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports
Layer 2 forwarding and other Layer 2 features.
Represents an access controller, a unified wired-WLAN module, or the switching engine
on a unified wired-WLAN switch.
Represents an access point.
Represents a security product, such as a firewall, a UTM, or a load-balancing or security
card that is installed in a device.
Represents a security card, such as a firewall card, a load-balancing card, or a
NetStream card.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your device.


About the H3C S6800 documentation set
The H3C S6800 documentation set includes:
Cate
g
or
y
Documents Pur
p
oses
Product description and
specifications Marketing brochures Describe product specifications and benefits.
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.
H3C LSWM1HFANSC &
LSWM1HFANSCB Fan
Assemblies Installtion
Describes the appearance, specifications, and
installation and removal of hot-swappable fan
assemblies.
H3C SFP/SFP+/XFP
Transceiver Modules
Installation Guide
Describe the installation, and replacement of
SFP/SFP+/XFP transceiver modules.
H3C LSVM1AC650 &
LSVM1DC650 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.
Operations and
maintenance
MIB Companion Describes the MIBs for the software release.
Release notes Provide information about the product release and
software upgrading.
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, as well as solutions.
[Technical Support & Documents > Software Download]—Provides the documentation released with the
software version.

Technical support
servic[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 commands··························································································································································· 1
address-family ipv4 (VPN instance view) ··············································································································1
description (VPN instance view) ·····························································································································1
display bgp group ipv4 vpn-instance·····················································································································2
display bgp peer ipv4 vpn-instance ·······················································································································4
display ip vpn-instance ············································································································································6
domain-id ··································································································································································7
export route-policy····················································································································································8
ext-community-type ···················································································································································9
import route-policy················································································································································· 10
ip binding vpn-instance········································································································································· 11
ip vpn-instance (system view) ······························································································································· 12
route-distinguisher (VPN instance view) ·············································································································· 12
route-tag ································································································································································· 13
routing-table limit ··················································································································································· 14
vpn-id ······································································································································································ 15
vpn-instance-capability simple······························································································································ 16
vpn-target (VPN instance view/IPv4 VPN view/IPv6 VPN view)····································································· 17
IPv6 MCE commands·················································································································································19
address-family ipv6 (VPN instance view) ··········································································································· 19
display bgp group ipv6 vpn-instance·················································································································· 19
display bgp peer ipv6 vpn-instance ···················································································································· 21
Index ···········································································································································································25

1
MCE commands
address-family ipv4 (VPN instance view)
Use address-family ipv4 in VPN instance view to enter IPv4 VPN view.
Use undo address-family ipv4 to remove all configurations from IPv4 VPN view.
Syntax
address-family ipv4
undo address-family ipv4
Views
VPN instance view
Predefined user roles
network-admin
Usage guidelines
In IPv4 VPN view, you can configure IPv4 VPN parameters such as inbound and outbound routing
policies.
Examples
# Enter IPv4 VPN view.
<Sysname> system-view
[Sysname] ip vpn-instance vpn1
[Sysname-vpn-instance-vpn1] address-family ipv4
[Sysname-vpn-ipv4-vpn1]
Related commands
address-family ipv6 (VPN instance view)
description (VPN instance view)
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 is configured for a VPN instance.
Views
VPN instance view

2
Predefined user roles
network-admin
Parameters
text: Specifies a description for the VPN instance, a case-sensitive string of 1 to 79 characters.
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
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 brief information about all peer groups.
Examples
# Display brief 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 detailed 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

3
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 Command output
Field Descri
p
tion
Type
Peer group type:
•external—EBGP peer group.
•internal—IBGP peer group.
Maximum allowed prefix number Maximum number of routes allowed to learn from a peer in the
group.
Threshold
Percentage of received routes from a peer to maximum routes
allowed to learn from the peer. If the percentage is reached, the
system generates alarm messages.
Configured hold time value Configured Hold Interval in seconds.
Keepalive timer value Keepalive interval in seconds.
Minimum time between advertisements Minimum route advertisement interval in seconds.
Peer preferred value Preferred value specified for the routes from a peer.
Routing policy configured Routing policy configured for the peer group.
Members Information about the peers included in the peer group.
Peer IP address of the peer.
AS AS number of the peer.
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.
State Current state of the BGP session between the local switch and the
peer.

4
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 brief 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
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
10.1.1.1 200 24 29 0 1 00:18:47 Established
Table 2 Command output
Field Descri
p
tion
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 Lasting time of the current BGP session state.

5
Field Descri
p
tion
State Current state of the BGP session between the local device and 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
Table 3 Command output
Field Description
Peer IP address of the peer.
Local Local router ID.
Type
BGP connection type between the local device and the peer:
•IBGP link—IBGP connection.
•EBGP link—EBGP connection.
remote router ID Router ID of the peer.
BGP current state Current state of the BGP session between the local device and the peer.
BGP current event Current event of the BGP session between the local device and the peer.
BGP last state Previous state of the BGP session.
Received Total numbers of received messages and updates.
Sent Total numbers of sent messages and updates.
Maximum allowed prefix number Maximum number of routes allowed to learn from the peer.
Threshold
Percentage of received routes from the peer to maximum routes allowed
to learn from the peer. If the percentage is reached, the system
generates alarm messages.
Minimum time between
advertisements Minimum route advertisement interval in seconds.
Optional capabilities Optional capabilities supported by the local end.

6
Field Description
Peer Preferred Value Preferred value specified for the routes from the peer.
# 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
27-Mar-2011 15:36:12 Down Receive notification with error 6/4
Cease/Administrative Reset
27-Mar-2011 15:34:29 Up
Table 4 Command output
Field Description
Peer IP address of the peer.
Date Date on which the notification was sent or received.
Time Time at which the notification was sent or received.
State BGP session state.
Notification
Error/SubError
Error code of the notification, indicating the cause of why the BGP session is down.
•Error—Refers to the error code, which identifies the type of the notification.
•SubError—Refers to the error subcode of the notification, which identifies specific
information about the reported error.
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: Displays information about the specified VPN instance. The
vpn-instance-name is a case-sensitive string of 1 to 31 characters. If no VPN instance is specified, the
command displays brief information about all VPN instances.
Examples
# Display brief information about all VPN instances.

7
<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 5 Command output
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 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
Export Route Policy : outpolicy
Import Route Policy : inpolicy
Maximum Routes Limit : 5000
Address-family IPv6:
Export VPN Targets :
2:2
Import VPN Targets :
3:3
Export Route Policy : outpolicy
Import Route Policy : inpolicy
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.

8
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. Without this keyword, the command specifies a primary
domain ID.
Usage guidelines
When you redistribute OSPF routes into BGP, 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 they do and they are
intra-area routes, OSPF advertises these routes in Summary LSAs (Type 3). If they do but they are not
intra-area routes, OSPF advertises these routes in AS External LSAs (Type 5) or NSSA External LSAs (Type
7). If the routes do not belong to the same OSPF routing domain, OSPF advertises them in Type 5 or Type
7 LSAs.
With no parameter specified, the undo domain-id command deletes all domain IDs.
Examples
# Configure an OSPF domain ID.
<Sysname> system-view
[Sysname] ospf 100
[Sysname-ospf-100] domain-id 234
export route-policy
Use export route-policy to apply an export routing policy for a VPN instance.
Use undo export route-policy to remove the application.
Syntax
export route-policy route-policy
undo export route-policy
Default
No export routing policy is applied for a VPN instance.
Views
VPN instance view, IPv4 VPN view, IPv6 VPN view
Predefined user roles
network-admin

9
Parameters
route-policy: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
You can specify an export routing policy to filter advertised routes or modify their route attributes for the
VPN instance.
An export routing policy specified in VPN instance view applies to both IPv4 VPN and IPv6 VPN.
An export routing policy specified in IPv4 VPN view or IPv6 VPN view applies to only IPv4 VPN or IPv6
VPN.
IPv4/IPv6 VPN prefers the export routing policy specified in IPv4/IPv6 VPN view over the one specified
in VPN instance view.
Examples
# Apply export routing policy poly-1 for 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 for IPv4 VPN vpn2.
<Sysname> system-view
[Sysname] ip vpn-instance vpn2
[Sysname-vpn-instance-vpn2] address-family ipv4
[Sysname-vpn-ipv4-vpn2] export route-policy poly-2
# Apply export routing policy poly-3 for IPv6 VPN vpn3.
<Sysname> system-view
[Sysname] ip vpn-instance vpn3
[Sysname-vpn-instance-vpn3] address-family ipv6
[Sysname-vpn-ipv6-vpn3] export route-policy poly-3
Related commands
•import route-policy
•route-policy (Layer 3—IP Routing Configuration Guide)
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 0x0005, 0x0107, and 0x0306.
Views
OSPF view

10
Predefined user roles
network-admin
Parameters
domain-id type-code1: Specifies the type code for domain ID. Valid values are 0x0005, 0x0105,
0x0205, and 0x8005.
router-id type-code2: Specifies the type code for router ID. Valid values are 0x0107 and 0x8001.
router-type type-code3: Specifies the type code for route type. Valid values are 0x0306 and 0x8000.
Examples
# Configure the type codes of domain ID, router ID, and route type as 0x8005, 0x8001, and 0x8000,
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 an import routing policy for a VPN instance.
Use undo import route-policy to remove the application.
Syntax
import route-policy route-policy
undo import route-policy
Default
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 a routing policy by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
You can specify an import routing policy to filter received routes or modify their route attributes for the
VPN instance.
An import routing policy specified in VPN instance view applies to both IPv4 VPN and IPv6 VPN.
An import routing policy specified in IPv4 VPN view or IPv6 VPN view applies to only the IPv4 VPN or
IPv6 VPN.
IPv4/IPv6 VPN prefers the import routing policy specified in IPv4/IPv6 VPN view over the one specified
in VPN instance view.

11
Examples
# Apply import routing policy poly-1 for VPN instance vpn1.
<Sysname> system-view
[Sysname] ip vpn-instance vpn1
[Sysname-vpn-instance-vpn1] import route-policy poly-1
# Apply import routing policy poly-2 for IPv4 VPN vpn2.
<Sysname> system-view
[Sysname] ip vpn-instance vpn2
[Sysname-vpn-instance-vpn2] address-family ipv4
[Sysname-vpn-ipv4-vpn2] import route-policy poly-2
# Apply import routing policy poly-3 for IPv6 VPN vpn3.
<Sysname> system-view
[Sysname] ip vpn-instance vpn3
[Sysname-vpn-instance-vpn3] address-family ipv6
[Sysname-vpn-ipv6-vpn3] import route-policy poly-3
Related commands
•export route-policy
•route-policy (Layer 3—IP Routing Configuration Guide)
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.

12
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)
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.

13
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 these
formats:
•16 - b i t AS 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 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 the AS number is not greater than 65535, the first two octets of the default external route tag are
0xD000 and the last two octets are the local AS number. For example, if the local BGP AS number is 100,
the default value of the external route tag is 3489661028. If the AS number is greater than 65535, the
default external route tag is 0.