Refer to the Layer 2 Services and EVPN Guide: VLL, VPLS, PBB, and EVPN and to the Layer 3 Services Guide: Internet Enhanced Services and Virtual Private Routed Network Services for information on command syntax and CLI descriptions.
This command creates a text description stored in the configuration file for a configuration context.
The description command associates a text string with a configuration context to help identify the context in the configuration file.
The no form of this command removes any description string from the context.
No description is associated with the configuration context.
Shutting down a Python script triggers the system to load and compile the script from the configured location(s). Since the system supports three locations, the primary, secondary and tertiary, the system will try to load the Python script in that order.
Shutting down a Python script will disable the Python script and cause the corresponding packet to pass through without any modification.
no shutdown
This command enables the context to configure Python parameters.
This command configures a Python policy which will select Python scripts to modify specific messages of different protocols.
The no form of the command removes the Python policy.
This command enables the context to configure the limits of the caching API inside the Python scripts
This command configures the maximum size of the data structure that can be stored in a single Python cache entry which includes both a value and key.
When requesting to store a data structure the size of the serialized object is compared with the value specified. If larger, the object will not be stored and Python will return exception.
The no form of the command reverts to the default value.
256
This command configures the maximum number of Python cache entries that can be stored in the cache of this Python policy.
If the limit has been reached, a Python exception will be thrown when requested to store another data structure.
128000
This command configures the maximum allowed lifetime for each entry of the Python cache of this Python policy.
When adding data to the Python cache the lifetime of the given object must always be specified. If the specified lifetime is bigger than the configured value, then the value of the max-entry-lifetime will be used instead of the lifetime that was specified.
The no form of the command reverts to the default.
This command specifies the MCS peer’s address and sync-tag for syncing the cached entries of the python-policy. The sync-tag must be match on both chassis.
no mcs-peer
This command enables the context to configure minimum-lifetime of python cache information.
none
This command specifies the minimum lifetime of an entry that it could be synced across CPM.
no high-availability
This command specifies the minimum lifetime for a cache entry to be synchronized with the MCS peer.
no multi-chassis-redundancy
This command configures the minimum lifetime for a cache entry to be made persistent.
no persistence
This command enables persistency support for the cached entries of the python-policy.
no persistence
This command specifies the Python script for the specified DHCPv4 packet type in the specified direction.
Multiple dhcp command configurations are allowed in the same Python policy.
The no form of the command reverts to the default.
none
This command specifies the Python script for the specified DHCPv6 packet type in the specified direction.
Multiple dhcps command configurations are allowed in the same Python policy.
none
This command specifies the Python script to use for the specified Diameter message type in the specified direction.
Multiple diameter command configurations are allowed in the same Python policy.
none
Message type | Application | Direction |
aaa – AA Answer | Nasreq | ingress |
aar – AA Request | Nasreq | egress |
asa – Abort Session Answer | Gx, Gy | egress |
asr – Abort Session Request | Gx, Gy | ingress |
cca – Credit Control Answer | Gx, Gy | ingress |
ccr – Credit Control Request | Gx, Gy | egress |
cea – Capabilities Exchange Answer | Base | ingress |
cer – Capabilities Exchange Request | Base | egress |
dpa – Disconnect Peer Answer | Base | ingress / egress |
dpr – Disconnect Peer Request | Base | ingress / egress |
dwa – Device Watchdog Answer | Base | ingress / egress |
dwr – Device Watchdog Request | Base | ingress / egress |
raa – Re-Authentication Answer | Gx, Gy | egress |
rar – Re-Authentication Request | Gx, Gy | ingress |
This command configures a Python script for the specified GTPv1-C message type in the specified direction.
none
This command configures a Python script for the specified GTPv2-C message type in the specified direction.
none
This command specifies the python-script for the specified PPPoE message type in the specified direction. Multiple pppoe command configuration are allowed in the same Python policy.
The no form of the command reverts to the default.
none
This command specifies the Python script for the specified RADIUS packet type in the specified direction.
Multiple radius command configurations are allowed in the same Python policy.
access-request, access-accept, access-reject, accounting-request, accounting-response, access-challenge, disconnect-request, change-of-authorization-request
This command configures scripts to handle VSD messages.
none
This command enables the context to configure Python scripts to modify messages of different protocols.
The no form of the command removes the Python script name from the configuration.
This command specifies the action taken when Python fails to modify the given message.
The no form of the command reverts to the default.
drop
This command specifies the location of the primary Python script. The system supports three locations for each Python script. Users can store the script file on either a local CF card or an FTP server.
The no form of the command removes the URL.
no primary-url
This command specifies the format of the Python script file(s) in this python-script. Unintentional changing of Python script file could be prevented by using protected format.
The no form of this command equals to protection none.
none
This command specifies the location of secondary Python script. The system supports three locations for each Python-script. Users can store scripts file on either a local CF card or a FTP server.
The no form of the command removes the URL.
no secondary-url
This command specifies the location of tertiary Python script. The system supports three locations for each Python-script. Users can store scripts file on either a local CF card or a FTP server.
The no form of the command removes the URL.
no tertiary-url
This command specified the Python policy for DHCPv4 packets sent/received on the capture SAP.
The no form of the command removes the policy name from the configuration.
none
This command specified the Python policy for DHCPv6 packets sent/received on the capture SAP.
The no form of the command removes the policy name from the configuration.
none
This command specified the Python policy for PPPoE packets sent/received on the capture SAP.
The no form of the command removes the policy name from the configuration.
none
This command specified the python-policy for DHCPv4 packets sent/received on the group interface.
The no form of the command removes the policy name from the configuration.
none
This command specified the python-policy for DHCPv6 packets sent/received on the group interface.
The no form of the command removes the policy name from the configuration.
none
This command specifies the Python policy for PPPoE packets sent/received on the group interface.
The no form of the command removes the policy name from the configuration.
none
This command specified the Python policy for DHCPv4 packets sent/received on the retail subscriber interface.
none
This command specified the python-policy for RADIUS packets to/from the RADIUS servers defined in the specified radius-server-policy.
none
This command specified the python-policy for RADIUS packets sent/received on the client side of the RADIUS proxy server.
none
This command enables the context to configure persistence parameters on the system.
The persistence feature enables state on information learned through DHCP snooping across reboots to be retained. This information includes data such as the IP address and MAC binding information, lease-length information, and ingress sap information (required for VPLS snooping to identify the ingress interface).
If persistence is enabled when there are no DHCP relay or snooping commands enabled, it will simply create an empty file.
no persistence
This command configures Python policy cache persistency parameters.
This command enables syncing of python-policy cached entries to the peer.
Use the mcs-peer command in the python-policy to enable syncing for a specific python-policy.
no python
This command instructs the system where to write the file. The name of the file is: dhcp-persistence.db. On boot the system scans the file systems looking for dhcp-persistence.db, if it finds it starts to load it.
In the subscriber management context, the location specifies the flash device on a CPMCFM card where the data for handling subscriber management persistency is stored.
The no form of this command returns the system to the default. If there is a change in file location while persistence is running, a new file will be written on the new flash, and then the old file will be removed.
no location
This command dumps all cached entries or a specified entry of a specified Python policy.
The DDP key in the output is the python cache persistency record key.
Note:
The DDP Key in the output could be used for the tools>dump>persistence>python command. |
This command set the lifetime of a specified python cache entry.
This command converts a normal (unprotected) Python script file into an SRPY format with specified key.
This command will try to reload/recompile the primary/secondary/tertiary scripts in the specified Python script in order. The system will use the first script that comes up.
Note:
The command outputs in the following section are examples only; actual displays may differ depending on supported functionality and user configuration. |
This command enables the context to display Python information.
This command displays information about the currently configured Python policy.
The system will display a list of currently configured Python policy names if no parameter is specified.
This command displays information about the currently configured Python script.
The system will display a list of currently configured Python script names if no parameter is specified.
This command enters the debug context the specified Python script
This command enables the script-compile-error, script-export-variables, script-output, script-outputon-error, and script-runtime-error functionalities.
This command sends the traceback of the compile error to the logger. The traceback contains detailed information about where and why the compilation fails. The compilation takes place when the CLI user changes the admin state of the Python script from shutdown to no-shutdown.
This command sends the output variables of the Python script to the logger when the script ran successfully.
This command sends the output (such as from 'print' statements) of the Python script to the logger.
This command sends the output (such as traceback data) of the Python script to the logger, but only when the script fails.
This command sends the traceback of the Python script failure to the logger.
This command clears Python policy data.