3com MSR 20-20 참조 매뉴얼
1713
■
32-bit IP address: 16-bit user-defined number. For example, 192.168.122.15:1.
Description
Use the route-distinguisher command to configure a route distinguisher (RD)
for a VPN instance.
for a VPN instance.
An RD is used to create the routing and forwarding table of a VPN. By prefixing an
RD to an IPv4 prefix, you get a VPN IPv4 prefix unique globally.
RD to an IPv4 prefix, you get a VPN IPv4 prefix unique globally.
n
■
No RD is configured by default; you must configure an RD for each VPN
instance.
instance.
■
A VPN instance takes effect only after you configure an RD for it.
■
Once you configure an RD for a VPN, you cannot remove the association.
■
You cannot change an RD directly; you can only delete the VPN instance, and
then re-create the VPN instance and re-configure a new RD.
then re-create the VPN instance and re-configure a new RD.
Example
# Configure the RD of VPN instance vpn1.
<Sysname> system-view
[Sysname] ip vpn-instance vpn1
[Sysname-vpn-instance-vpn1] route-distinguisher 22:1
route-tag
Syntax
route-tag tag-value
undo route-tag
View
OSPF view
Parameter
tag-value: Tag for identifying injected VPN routes, in the range 0 to 4294967295.
Description
Use the route-tag command to configure the tag for identifying injected VPN
routes.
routes.
Use the undo route-tag command to restore the default.
The first two octets of the default tag is always 0xD000, while the last two octets
is the AS number of the local BGP. For example, if the local BGP AS number is 100,
the default tag is 3489661028 in decimal.
is the AS number of the local BGP. For example, if the local BGP AS number is 100,
the default tag is 3489661028 in decimal.
An OSPF instance-related VPN instance on a PE is usually configured with a VPN
route tag, which must be included in Type 5/7 LSAs. PEs in the same AS are
recommended to have the same route tag. The route tag is local significant and
can be configured and take effect on only PEs receiving BGP routes and
generating OSPF LSAs; it is not transferred in any BGP extended community
attribute. Different OSPF processes can have the same route tag.
route tag, which must be included in Type 5/7 LSAs. PEs in the same AS are
recommended to have the same route tag. The route tag is local significant and
can be configured and take effect on only PEs receiving BGP routes and
generating OSPF LSAs; it is not transferred in any BGP extended community
attribute. Different OSPF processes can have the same route tag.
Tags configured with different commands have different priorities:
■
A tag configured with the import-route command has the highest priority.