LI management using the classic CLI engine

With the advent of support for both classic and mixed configuration modes for LI management, the classic engine supports the following additional features in classic configuration mode.

Classic CLI mode features for LI management are as follows:

Table: Classic CLI engine properties for classic and mixed configuration mode lists the classic CLI engine properties for classic and mixed configuration mode.

Table: Classic CLI engine properties for classic and mixed configuration mode
Config CLI tree Classic mode Mixed mode

li>li-filter-lock-state

  • locked

  • unlocked-for-li-users

  • unlocked-for-all-users

  • locked

  • unlocked-for-all-users

See Configurable filter lock for Lawful Intercept for more information

li>li-source

ID with name

ID with name

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

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

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

ID or name (router and router-name are mutually exclusive)

ID or name (router and router-name are mutually exclusive)

li>mirror-dest-template>router

ID or name (router and router-name are mutually exclusive)

ID or name (router and router-name are mutually exclusive)

li>li-filter-associations>li-ip-filter>ip-filter

li>li-filter-associations>li-ipv6-filter>ipv6-filter

li>li-filter-associations>li-mac-filter>mac-filter

ID or name (ID and name are mutually exclusive)

name only

li>li-filter-block-reservation>li-reserved-block>ip-filter

li>li-filter-block-reservation>li-reserved-block>ipv6-filter

li>li-filter-block-reservation>li-reserved-block>mac-filter

ID or name (ID and name are mutually exclusive)

name only

Table: Reference types for classic and mixed configuration mode lists the reference types for classic and mixed configuration mode.

Table: Reference types for classic and mixed configuration mode
Config CLI tree Classic mode Mixed mode

li>li-source>sap

loose reference1

loose reference

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

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

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

  • hard reference for router2
  • loose reference for router-name

(router and router-name are mutually exclusive)

  • hard reference for router

  • loose reference for router-name

(router and router-name are mutually exclusive)

li>li-source>subscriber

li>li-source>nat l2-aware-sub

li>li-source>wlan-gw>dsm-subscriber

loose reference

loose reference

li>li-filter-associations>li-ip-filter>ip-filter

li>li-filter-associations>li-ipv6-filter>ipv6-filter

li>li-filter-associations>li-mac-filter>mac-filter

hard reference

hard reference

li>li-filter-block-reservation>li-reserved-block>ip-filter

li>li-filter-block-reservation>li-reserved-block>ipv6-filter

li>li-filter-block-reservation>li-reserved-block>mac-filter

  • loose reference for filter

  • hard reference for entries (entries cannot overlap)

  • loose reference for filter

  • hard reference for entries (entries cannot overlap)

li>li-source>ip-filter

li>li-source>ipv6-filter

li>li-source>mac-filter

hard reference

not supported

li>li-source>li-ip-filter

li>li-source>li-ipv6-filter

li>li-source>li-mac-filter

hard reference

hard reference

1 Loose reference means that the referenced object does not have to exist before it can be referenced. In addition, the referenced object can be deleted at any time. For example, li-source references subscriber-1 even if subscriber-1 is not created on the system. With loose reference, an LI administrator can become completely independent from regular administrators. An LI administrator can provision a list of targets for LI without having to wait for the regular administrator to create them (such as SAP and subscribers). In reverse order, when the regular administrator wants to remove SAPs, there is no need to wait for the LI administrator to remove the reference beforehand. Loose reference allows LI independence and is the recommended model for LI provisioning.
2 Hard reference means that the object must first be created in the system before it can be referenced. In addition, after an object is referenced by LI, the object must be unreferenced before it can be removed. For example, ip-filter 10 must first exist in the system before it can be referenced using the li>li-source>ip-filter command.