HPE FlexFabric 5950 Series Configuration Manual page 313

Step
5. (Optional.) Configure the
type code of an OSPFv3
extended community
attribute.
6. (Optional.) Configure an
external route tag for
redistributed VPN routes.
7. (Optional.) Disable setting
the DN bit in OSPFv3 LSAs.
8. (Optional.) Ignore the DN bit
in OSPFv3 LSAs.
9. (Optional.) Enable the
external route check feature
for OSPFv3 LSAs.
Command
ext-community-type
{ domain-id type-code1 |
route-type type-code2 | router-id
type-code3 }
route-tag tag-value
disable-dn-bit-set
disable-dn-bit-check
route-tag-check enable
305
Remarks
attribute.
You can configure the same
domain ID for different OSPFv3
processes.
You must configure the same
domain ID for all OSPFv3
processes of the same VPN to
ensure correct route
advertisement.
By default, the type codes for
domain ID, route type, and router
ID are hexadecimal numbers
0005, 0306, and 0107,
respectively.
Perform this configuration on the
PE.
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 the local BGP AS
number. If the AS number is
greater than 65535, the external
route tag is 0.
Perform this configuration on the
PE.
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.
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.
By default, the PE does not check
the external route tag but checks
the DN bit in OSPFv3 LSAs to
avoid routing loops.
This command is only for
backward compatibility with the
old protocol (RFC 4577). If the
device supports the DN bit, use
the DN bit to avoid routing loops.
Perform this configuration on the
PE.