Expand all | Collapse all
OSPFv3
OSPFv3 routing protocol configuration parameter differences
between legacy and advanced routing engine.
There are parameter setting differences between legacy and advanced routing engines when
configuring OSPFv3 settings.
Route Redistribution
OSPFv3 handles route redistribution to another routing protocol differently in the legacy and
advanced routing engines. When redistributing from OSPFv3, filters are based on a
variety of criteria.
The advanced routing engine does not allow redistribution of
routes based on Link State Advertisement (LSA) type (external-1, external-2,
inter-area, or intra-area) or origin area. You can, however, use prefixes and tags
associated with LSA updates.
CONFIGURED IN (LEGACY ROUTING ENGINE) | | MIGRATED TO (ADVANCED ROUTING ENGINE) | |
| Supports redistribution of routes that match the following criteria: | | Supports Redistribute Route-Map that Match the
following criteria: Address (using Prefix List or Access List ) Next Hop (using Prefix List or Access List )
|
Authentication Profile
In the advanced routing engine, the authentication profile
variables are retained globally for reuse which can cause an issue with the Security
Policy Index (SPI). The advanced routing engine does not allow multiple interface
authentication profiles within a single virtual system (vsys) to share the same SPI
value.
CONFIGURED IN (LEGACY ROUTING ENGINE) | | MIGRATED TO (ADVANCED ROUTING ENGINE) | |
