These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
VISIT OUR DIFFERENT FORUMS:
Announcements > | |
CloudShell > | TestShell > |
Developers > | BI (Business Inteligence) > |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide > | Configuration Management > |
Getting started with Shells > | Extending CloudShell with Cloud Providers > |
Getting started with Orchestration > | API Guide > |
To share your integration, follow the instructions in this guide >.
The purpose of the document is clarifying the logical structure of the IXN2X Log.
The IXN2X Log Documents the command transportation between the Traffic Generator and our TestShell drivers. The commands are of various origins, could be the Traffic Generator’s, the designer’s or native commands of the OS.
The IXN2X Log is a continuous log constructed of following increments. It will open with a headline which specifies the components of each line in the log (refer to Figure 1)
Figure 1 - IXN2X log headline structure
Head line components:
- Execution of a Traffic Generator command.
- Execution of a TCL command.
- Traffic Generator is loading application program interface package.
Notice that components 5 to 7 are the most important and the meaningful.
An example of the actual structure can be seen in Figure 2.
Figure 2 – Two examples of IXN2X log headline structure, argument and return code
The log consist of two types of lines: The Command line (args) which stands for “arguments” and the response line (rc) which stands for “returncode”. In the log each line can be distinguished by the argument in parentheses (Figure 3)
Figure 3 - Line type identifier
Rarely a command line will not be followed by a return code. These occurrences are not supposed to happen, it will not topple the program or equipment but it can detect something is not quite right.
The title paragraph follows the headline of each increment. It will present details of the directories, paths, drivers, versions, packages etc. An example is presented in Figure 4.
Figure 4 - Title paragraph example
Recommendation:as mentioned before, the log is a collection of following increments. In order to analyze an error which can be reproduced, it would be best to open the log and clear its content (Ctrl A + Del + Save). That way it is easier to observe the log and locate the relevant sessions.
The text which follows the title paragraph. The text inside the red boundary in Figure 5.
Figure 5 - Typical increment of IXN2X log
These log lines are structured as explained in the headline section. In Figure 6, a sample of a return code output is presented.
Figure 6 -ReturnCode sample
This document describes the structure of the IXN2X log file. The main components of the log arethe headline,the title paragraphand the rest isthe registry of data transformation. The document purpose is to direct the log observer to sort the meaningful details the log has to offer.
These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
Announcements | |
CloudShell | TestShell |
Developers | BI (Business Inteligence) |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide | Configuration Management |
Getting started with Shells | Extending CloudShell with Cloud Providers |
Getting started with Orchestration | API Guide |
To share your integration, follow the instructions in this guide.
IxN2X - How to change a field in PDU (Packet Data Unit)
Spirent TestCenter Sample Building Blocks
IxNetwork - How to use the port matrix
IxExplorer : How to view QOS statistics via TestShell Studio
How to automate exit (CTRL + Z) and break (ALT + B) in a Terminal session
Creating a dynamic and rich input form for assets
Changing the fonts of the execution reports in TestShell Studio / Runner
Extract Lines with All Occurrences of a Sub-string using Transformation