Creating Performance Sessions in Bulk

Performance sessions are ongoing measurements set up between two termination points: a sender (a Provider Connectivity Assurance Sensor Control) and a reflector (any device with the required capabilities). They capture a wide range of metrics that can be used to evaluate the performance of network services.

Performance sessions can be set up one at a time in the Legacy orchestrator web interface. For an introduction to performance sessions and the procedure for setting them up in the Legacy orchestrator web interface, see the Legacy orchestrator User Guide or the online help available in the web interface.

Performance sessions can also be created in bulk from the Legacy orchestrator command line. This section explains two ways to create sessions in bulk:

1. Prepare a script of mgr-commands that creates sender and reflector endpoints, and sessions. Then run the script on the Appliance Monitor command line. For the procedure, see Creating Performance Sessions Using a Script.
2. Use the deployment tool to create reflectors, senders and sessions from CSV files that you prepare in advance. For the procedure, see Creating Performance Sessions Using the Deployment Tool.

About Performance Sessions

This article covers the type of sessions that can be created and how many sessions can be created.

Types of Performance Sessions

The following types of sessions can be created:

• TWAMP Stateful
• TWAMP Stateless
• ETH-DM
• ETH-LB
• ETH-VS
• ICMP Echo
• UDP Echo
• 2xOneWay

Number of Performance Sessions

The number of sessions that can be set up and run simultaneously depends on the collection period used for the sessions. The collection period is the time interval over which packets will be collected and for which performance metrics will be calculated.

Here are some basic guidelines on how many sessions can be set up and running simultaneously:

• 26,000 sessions with a collection period of 30 seconds
• 52,000 sessions with a collection period of 60 seconds.

The system can handle users being logged into 100 sessions simulataneously, as follows:

• The maximum number of concurrent users on the system is 20
• Maximum concurrent sessions per user is five.