LI management using the MD-CLI engine

The MD-CLI engine for mixed and model-driven configuration modes only allows names for filters, router instances, and services; IDs are not supported.

Table: Key differences between classic CLI and MD-CLI lists key differences between classic CLI and MD-CLI.

Table: Key differences between classic CLI and MD-CLI
Classic CLI engine for mixed mode MD-CLI engine for mixed and model-driven mode

li>li-source (ID with name)

/li/li-source (name only)

li>li-source>nat>classic-lsn-sub>router

li>li-source>nat>dslite-lsn-sub>router

li>li-source>nat>nat64-lsn-sub>router

(router ID or name)

/li/li-source/nat/nat44

/li/li-source/nat/dslite

/li/li-source/nat/nat64

(router name only)

li>mirror-dest-template>layer-3-encap>router

(router ID or name)

/li/mirror-dest-template/layer-3-encap

(router name only)

Compared to classic configuration mode, mixed and model-driven configuration modes primarily use loose references, where the object referenced does not have to exist in the system before it is referenced. For example, subscriber-1 is referenced in li-source but does not need to be created on the system beforehand.

In classic configuration mode, when an LI filter (li-ip-filter, li-ipv6-filter, and li-mac-filter) is configured:

In mixed configuration mode: