Avaya M770 Manuel D’Utilisation
Avaya M770 ATM Switch User’s Guide
259
Chapter 21
Command Line Interface Scripts
This chapter describes how to create and to run Command Line Interface (CLI)
scripts. For common information related to the CLI see Chapter 3, “How to Use the
Command-line Interface”.
scripts. For common information related to the CLI see Chapter 3, “How to Use the
Command-line Interface”.
What CLI Scripts Are
Until version 2.1 of the Avaya M770 ATM Switch, there were several ways to access
the Command-line interface of the M770 ATM Switch. These methods include:
•
the Command-line interface of the M770 ATM Switch. These methods include:
•
Direct connection via serial port of the module
•
Telnet connection combined with the
access
command
•
The MSP-X menu.
CLI scripts now allow yet another way to access CLI commands. A CLI script is a
plain ASCII file, which contains set of almost any usual CLI commands, and may be
prepared using any text editor that is capable to store its output files in ASCII-only
format - Windows' Word, Notepad or WordPad, or UNIX's vi or emacs are
examples of such editors. The scripts are downloaded to the M770 ATM switch
using usual tftp download procedure, and run using special command (see below).
During the script running, the switch executes commands consecutively as they
appear in the script. Output of the commands is stored in temporary log, or,
alternatively, displayed on the console terminal. The script may be run on a single
module, or on multiple modules simultaneously, if started from the Master Agent
module.
plain ASCII file, which contains set of almost any usual CLI commands, and may be
prepared using any text editor that is capable to store its output files in ASCII-only
format - Windows' Word, Notepad or WordPad, or UNIX's vi or emacs are
examples of such editors. The scripts are downloaded to the M770 ATM switch
using usual tftp download procedure, and run using special command (see below).
During the script running, the switch executes commands consecutively as they
appear in the script. Output of the commands is stored in temporary log, or,
alternatively, displayed on the console terminal. The script may be run on a single
module, or on multiple modules simultaneously, if started from the Master Agent
module.