4. Test Resource Management
If you are new to Xena testers, this section will help you understand the basics of test resource management. Test resources can be the chassis itself, a test module on the chassis or a test port on a module.
This section describes:
Test resource hierarchy.
Test resource management principle.
4.1. Test Resource Hierarchy
4.1.1. Valkyrie Tester (L23 Tester)
Valkyrie is a full-featured stateless Ethernet traffic generator and analysis platform. Valkyrie tester has the following hierarchical structure.
---------------------
| Valkyrie Tester |
---------------------
|
| -----------------------
|---| Valkyrie Module |
| -----------------------
| |
| | -------------------
| |----| Valkyrie Port |
| | -------------------
| | |
| | | *************************
| | |----| Port Statistics |
| | | *************************
| | | *************************
| | |----| Stream |
| | | *************************
| | | |
| | | | **********************
| | | |----| Filter |
| | | | **********************
| | | | **********************
| | | |----| Modifier |
| | | | **********************
| | | | **********************
| | | |----| Histogram |
| | | | **********************
| | | | **********************
| | | |----| Length Term |
| | | | **********************
| | | | **********************
| | | |----| Match Term |
| | | | **********************
| | | | **********************
| | | |----| Test Payload |
| | | | **********************
| | | | **********************
| | | |----| Stream Statistics |
| | | | **********************
| | | |
Valkyrie Tester, Valkyrie Module, and Valkyrie Port are hardware resources that correspond to the hardware configuration. They cannot be created or deleted.
Everything below Valkyrie Port is virtual resources that can be created, deleted, and configured as needed.
4.1.2. Vulcan Tester (L47 Tester)
Vulcan generates stateful traffic over Ethernet. Vulcan Tester has the following hierarchical structure.
------------------
| Vulcan Tester |
------------------
|
| -------------------
|---| Vulcan Module |
| -------------------
| |
| | ------------------
| |----| Vulcan Port |
| | ------------------
| | |
| | | ************************
| | |----| Port Statistics |
| | | ************************
| | | ************************
| | |----| Connection Group |
| | | ************************
| | |
Vulcan Tester, Vulcan Module, and Vulcan Port are physical resources that correspond to the physical configuration. They cannot be created or deleted.
Everything below Vulcan Port is virtual resources that can be created, deleted, and configured as needed.
4.1.3. VulcanVE Tester (L47VE Tester)
VulcanVE is the virtual edition of Vulcan. VulcanVE Tester has the following hierarchical structure, the same as Vulcan Tester.
----------------------
| VulcanVE Tester |
----------------------
|
| ----------------------
|---| VulcanVE Module |
| ----------------------
| |
| | --------------------
| |----| VulcanVE Port |
| | --------------------
| | |
| | | ************************
| | |----| Port Statistics |
| | | ************************
| | | ************************
| | |----| Connection Group |
| | | ************************
| | |
Although VulcanVE Tester, VulcanVE Module, and VulcanVE Port are virtual resources, they cannot be created or deleted.
Everything below VulcanVE Port is virtual resources that can be created, deleted, and configured as needed.
4.1.4. Chimera Network Impairment Emulator (Impairment)
Chimera is a network impairment emulator that makes it easy to introduce consistent, accurate, well-defined and repeatable impairments (e.g. packet manipulation, packet drop, latency and jitter) to traffic between DUT in the lab.
Chimera Emulator has the following hierarchical structure.
------------------------
| Chimera Emulator |
------------------------
|
| ----------------------
|---| Chimera Module |
| ----------------------
| |
| | ----------------------
| |----| Chimera Port |
| | ----------------------
| | |
| | | *************************
| | |----| Port Statistics |
| | | *************************
| | | *************************
| | |----| Flow |
| | | *************************
| | | |
| | | | ****************************
| | | |----| Filter |
| | | | ****************************
| | | | ****************************
| | | |----| Impairment Config |
| | | | ****************************
| | | | ****************************
| | | |----| Impairment Distribution |
| | | | ****************************
| | | | ****************************
| | | |----| Flow Statistics |
| | | | ****************************
| | | |
Chimera Emulator, Chimera Module, and Chimera Port are physical resources that correspond to the physical configuration. They cannot be created or deleted.
Everything below Chimera Port is virtual resources that can be created, deleted, and configured as needed.
Important
Chimera can be seamlessly integrated with Valkyrie by installing Chimera modules in a Valkyrie chassis.
---------------------
| Valkyrie Tester |
---------------------
|
| -----------------------
|---| Valkyrie Module |
| -----------------------
|
| ----------------------
|---| Chimera Module |
| ----------------------
4.2. Management Principle
Xena testers support multiple simultaneous connections from any mixture of Xena clients, such as the ValkyrieManager, scripting clients, etc. As soon as a client has successfully established a connection to the chassis, any test resource can be inspected. But in order to change the test resource configuration, the resource must first be reserved by the client.
To management test resources, i.e., read, write, create, delete, you must follow the principles below:
To do
set(create/update/delete) on a test resource, i.e. tester, module, or port, you must reserve the resource under your username.To do
get(read) on a test resource, you don’t need to reserve.To reserve a tester, you must make sure all the modules and ports are either released or under your ownership.
To reserve a module, you must make sure all the ports are either released or under your ownership.
Important
Starting traffic using C_TRAFFIC of C_TRAFFICSYNC does NOT require chassis reservation but port reservation, although their command prefix is C_ and categorized as chassis-level commands.