Supports virtual router. | Supports logical router. | Unlike the legacy routing engine, the advanced routing engine does not create a default (logical)
router. |
Routing profiles are unique to the virtual router and are not shared. | Routing profiles are
used
to configure route filters, route redistribution, routing protocol
profiles, and the advanced
routing engine relies extensively on these routing profiles. These routing profiles are shared among the logical routers
within
the same virtual system
as well
as across virtual systems.
This makes it possible to reuse these profiles among logical routers
and protocols
in the
logical routers. A BGP peer in a peer group can inherit routing profiles from that BGP peer group. In addition,
BGP peers can have their own routing profiles, which are not
inherited from their BGP peer group. | Routing profiles may create issues when translating profiles from the legacy routing engine to
the advanced routing engine. In the legacy routing engine, profiles are unique to the virtual router and are not shared. You
may encounter issues with profiles that use the same name in more
than one virtual router. |
Enable you to create filters and policy rules without applying them to an object. For example, the legacy routing engine enables you to create a BGP import or export policy rule
without applying it to any peers or peer groups. | Enable you to create filters and policy rules without applying them to an object, similar to the
legacy routing engine. | To optimize the migration process, these orphan
filters and profiles are not converted during migration. |
Supports route tagging. The legacy routing engine uses a 32-bit dotted decimal value to represent the tag (such as
10.1.7.1). | Supports route tagging more completely and effectively than the legacy routing engine. The advanced routing engine uses 32-bit decimal notation to represent the tag (such as
1234567). | No exceptions; tags are migrated from dotted decimal format to decimal notation successfully. |
