Overview… making a script connection
The chassis support multiple concurrent scripting sessions, just like they support multiple concurrent interactive XenaManager sessions. And likewise, scripting sessions interact with the chassis in its current state. Establishing a scripting session does not in itself impact the chassis state.
In order to start a scripting session you establish a TCP/IP connection with the chassis using port 22611, on the same IP address as when using the XenaManager.
You then send lines of ASCII text to the chassis, terminated by CR/LF, and receive lines of ASCII text in response. The first command should be a logon with the valid password for the chassis, or the session will be terminated.
You can use any client platform that is able to establish a TCP/IP connection and send and receive lines of text through it. Typical client platforms include Tcl, Perl, Python, Java, Excel/VBA, and Telnet. You may use client-side functionality to execute script commands conditionally and repetitively.
Note that the notion of a multi-chassis testbed is created by the XenaManager, and is not defined at the scripting level. Each script connection to a chassis is independent of other connections, and any inter-chassis functionality must be implemented in the client environment.
Xena provides a simple interactive scripting client application that runs on Windows. It is similar to telnet and allows you to manually type commands to the chassis and see its responses:
Typing “HELP ?” explains how to get a compact overview of the available commands.