270
When
routes into BGP, BGP adds the
redistributed BGP VPNv6 routes
as a BGP extended community
attribute.
You can configure the same
domain ID for different OSPFv3
processes.
All OSPF processes of the same
VPN must be configured with the
same OSPF domain ID to ensure
correct route advertisement.
5. (Optional.) C
onfigure the
type code of an OSPFv3
extended community
attribute.
ext-community-type
{
domain-id
type-code1 |
route-type
type-code2 |
router-id
type-code3 }
By default
domain ID, route type, and router
ID are hexadecimal numbers
respectively.
Perform this configuration on the
PE.
6. (Optional.) Configure an
external route
redistributed VPN routes.
route-tag
tag-value
By 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. The last two
octets are
number.
greater than 65535, the external
route tag is 0.
Perform this configuration on the
PE.
7. (Optional.) D
the DN bit in OSPFv3 LSAs.
disable-dn-bit-set
By default, when a PE
redistributes BGP routes into
OSPFv3 and creates OSPFv3
LSAs, it sets the DN bit for the
LSAs.
Before using this command, make
sure it does not cause any routing
loops.
Perform this configuration on the
PE.
8. (Optional.) Ignore the DN bit
in OSPFv3 LSAs.
disable-dn-bit-check
By default, the PE checks the DN
bit in OSPFv3 LSAs.
Before using this command, make
sure it does not cause any routing
loops.
Perform this configuration on the
PE.
9. (Optional.) E
external route check function
for OSPFv3 LSAs.
route-tag-check enable
By default, the PE checks the DN
bit in OSPFv3 LSAs to avoid
routing loops.
This command is compatible with
the old protocol (RFC 4577). As a
best practice, do not use this
command in the current software