Traffic Sim Instructions Setup
Virtual RN150 Appliance
- Virtual RN150 bootstrapped and assessment started
Required Ports between the RN50 and the RN150
- TCP Ports 2500, 22, 123, 3306 (all bi-directional)
- UDP Port 161
Required Ports between the RN50s
- TCP ports 9000, 22 (bi-directional)
- UDP Ports 17000 – 65535 (bi-directional)
Virtual RN50 Appliances (Requires at least 2)
- Deploy virtual RN50s to desired location
- DHCP or static IP set
- IP of RN150
One of the following Hypervisors for appliance deployment
- VMware ESX or ESXi Server
- VMware Workstation
- VMware Player
- 2 Gigabytes of memory to allocate to the appliance
- 5 Gigabytes of Hard Drive Space
See what the codecs look like:
Detailed Codec Info
- Create the assessment on our portal. (RISC Networks portal)
- Complete setup of the virtual RN150 and select ‘Start Assessment’.
- Log on to https://cs-portal.riscnetworks.com
- Select ‘TrafficSim’ in the ‘Collect Data’ dropdown menu
- Download the virtual RN50 from our portal and unpack the zipped file to a folder
- Deploy on a workstation or laptop with VMware Player (Free) or WMware Workstation
- Deploy to an ESX Server with VMware Vsphere Client or VMware Workstation
- Power on / play the Virtual Machine
- If you wish to continue with DHCP IP address, continue to step 6.
- Select ‘Interfaces’
- For setting static IP address, select static in dropdown box.
- Enter IP information and select ‘Save’
- Select ‘Dashboard’
- Select ‘RN150’
- Enter the IP address of the virtual RN150 appliance
Setting up the calls
- Log on to https://cs-portal.riscnetworks.com and find the tile for the assessment you wish to perform TrafficSim on
- Select “TrafficSim” at the bottom of the assessment
- Select the virtual RN50 nodes to include in the call simulation. Nodes will automatically become enabled as they are added up to your entitlement.
- Purchase additional nodes if needed by selecting ‘Add Nodes’
Schedule the Simulation
- Select “Add New Operation”
- Select the desired time in UTC for the simulation. Current UTC time is displayed for convenience.
- Select “Get Available Devices for Selected Dates”
- Choose the Source and Destination nodes (simlations are run bidirectional)
- Select the “Codec” and “QoS Value”
- Select the “Get Capacity of Selected Devices”
- Select the number of calls and the duration
- Enter a description for the call simulation. This will allow for easy identification of the operation in the final report.
- (Optional) Select the “Advanced Config” to manually set the thresholds and control the auto pause feature. (Default settings will cause Auto-pause feature to pause the simulation if it exceeds 10% packet loss)
- Select “Create Operation” to begin the simulation.
After the call simulation has been created, the assessment will initiate very lightweight test calls between the virtual RN50s to verify communication between the involved devices. Notifications will be sent updating the user on the status of the test including what, if any, required ports were closed, and whether or not DSCP values were maintained.
- TrafficSim operations run on 5 minute intervals for the set duration (30 or 60 seconds.)
- The RN150 appliance is not eligible as a simulation node. All simulations are run bidirectionally between the RN50 appliances. (you will need to deploy an RN50 to each site you wish to simulate to and from.
- TrafficSim simulations run bidirectional. If you set up a call from site A to site B, you will NOT need to set up a 2nd operation from site B back to site A.
- We recommend running simulations 24 – 48 hours. This will provide greater visibility into Jitter, Loss, and Delay at times of the day.
- The Auto-pause feature will pause the simulation if 10% packet loss is exceeded. This value can be manually adjusted in the Advanced Config section.
- It is recommended to place the RN50 on the correct VLAN for Voice, Video, or Data. This will allow you to verify QoS in the environment.
- The RN50 does NOT need internet access to our NOC servers as the RN150 does.
- The RN50s and the RN150 do NOT need to be in scope (included in the subnet ranges at time of setup)