Automation Knowledge Base

The scripting environment provides you with optional default values for the module index and port index, allowing you to change and query parameters without providing the module and port index explicitly.

Default indices are enabled and disabled using the following short commands:

module/port Set default module and port to the specified values.

port Set default port to the specified value, retaining the default module.

-/- Disable the default module and port.

– Disable the default port, retaining the default module.

module/- Set the default module and disable the default port.

? Show the current default module and port.

When a default module and port is provided, parameters that would otherwise require explicit module and port index values can be written without them, e.g.:

PS_RATEPPS [3] 500
^---
#Index error in column 1
0/5
PS_RATEPPS [3] 500

Replies from the chassis will also use the current default values to suppress the explicit module and port indices when possible.

The scripting environment also provides wild-carding across modules and ports. Using an asterisk as a module or port index effectively makes the chassis execute the command for each value, e.g.:

0/* P_INTERFRAMEGAP 30

This sets the inter-frame gap for every port on module 0. It will generate an individual status response for each operation, and indeed some may succeed while others fail, for instance, due to lack of reservation.

Wild-cards also work for queries. This will give you the inter-frame gap for each port of module 0:

0/* P_INTERFRAMEGAP ?

Wild-cards cannot be used as default values, but the default and wild-card mechanisms can be combined, for instance, to use a default module together with a wild-carded port:

0/-
* P_INTERFRAMEGAP 30

Indeed, for chassis with a single module, you will typically set it as the default module and then use only port indices.