Check Twamp Operation
This scenario shows how to configure Network Service Monitor (NSM) operations to measure network quality using active traffic probes and the TWAMP protocol. In addition, the TWAMP NSM responder service is configured.
Test IPv4 Destination
Description
In this scenario, TWAMP NSM operations are configured in DUT0 (using an IPv4 destination address) and the TWAMP NSM responder service is configured in DUT1.
Scenario
Step 1: Set the following configuration in DUT1:
set interfaces ethernet eth0 address 10.215.200.100/24 set service nsm responder type twamp port 12345
Step 2: Set the following configuration in DUT0:
set interfaces ethernet eth0 address 10.215.200.50/24 set service nsm operation A destination-address 10.215.200.100 set service nsm operation A type twamp set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A window 100 set service nsm operation A alarm al_loss activate loss 5 set service nsm operation A alarm al_rtt activate rtt 0.2 set service nsm operation A alarm al_jitter activate jitter 0.1 set system alarm al_loss set system alarm al_rtt set system alarm al_jitter set service nsm operation A destination-port 12345
Step 3: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ------------------------------------------------------------------- al_jitter false 0 0.00 al_loss false 0 0.00 al_rtt false 0 0.00
Step 4: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
--------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled --------------------------------------------------------------------------------------------- A al_rtt false 0.000056 0.000013 0.000000 9/100 A al_loss false 0.000056 0.000013 0.000000 9/100 A al_jitter false 0.000056 0.000013 0.000000 9/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:29:12.199100 1 46.29 al_loss true 2024-02-26 19:29:11.401400 1 58.71 al_rtt true 2024-02-26 19:29:12.955454 1 34.63
Step 7: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------ Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------ A al_rtt true 0.430397 0.419716 43.000000 100/100 2024-02-26 19:29:12.955454 A al_loss true 0.430397 0.419716 43.000000 100/100 2024-02-26 19:29:11.401400 A al_jitter true 0.430397 0.419716 43.000000 100/100 2024-02-26 19:29:12.199100
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:29:20.075653 2024-02-26 19:29:12.199100 2 63.45 al_loss false 2024-02-26 19:29:20.272875 2024-02-26 19:29:11.401400 2 71.52 al_rtt false 2024-02-26 19:29:18.870995 2024-02-26 19:29:12.955454 2 47.67
Step 10: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000705 0.000047 0.000000 100/100 2024-02-26 19:29:18.870995 2024-02-26 19:29:12.955454 A al_loss false 0.000705 0.000047 0.000000 100/100 2024-02-26 19:29:20.272875 2024-02-26 19:29:11.401400 A al_jitter false 0.000705 0.000047 0.000000 100/100 2024-02-26 19:29:20.075653 2024-02-26 19:29:12.199100
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:29:20.075653 2024-02-26 19:29:12.199100 2 42.76 al_loss false 2024-02-26 19:29:20.272875 2024-02-26 19:29:11.401400 2 48.19 al_rtt true 2024-02-26 19:29:23.983239 2024-02-26 19:29:18.870995 3 49.29
Step 13: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.801732 0.009053 0.000000 100/100 2024-02-26 19:29:23.983239 2024-02-26 19:29:18.870995 A al_loss false 0.801732 0.009053 0.000000 100/100 2024-02-26 19:29:20.272875 2024-02-26 19:29:11.401400 A al_jitter false 0.801732 0.009053 0.000000 100/100 2024-02-26 19:29:20.075653 2024-02-26 19:29:12.199100
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:29:20.075653 2024-02-26 19:29:12.199100 2 32.40 al_loss false 2024-02-26 19:29:32.658597 2024-02-26 19:29:28.193292 4 54.89 al_rtt false 2024-02-26 19:29:32.157862 2024-02-26 19:29:23.983239 4 57.98
Step 16: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000709 0.000038 0.000000 100/100 2024-02-26 19:29:32.157862 2024-02-26 19:29:23.983239 A al_loss false 0.000709 0.000038 0.000000 100/100 2024-02-26 19:29:32.658597 2024-02-26 19:29:28.193292 A al_jitter false 0.000709 0.000038 0.000000 100/100 2024-02-26 19:29:20.075653 2024-02-26 19:29:12.199100
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:29:36.162781 2024-02-26 19:29:20.075653 3 35.43 al_loss false 2024-02-26 19:29:32.658597 2024-02-26 19:29:28.193292 4 44.04 al_rtt true 2024-02-26 19:29:38.939043 2024-02-26 19:29:32.157862 5 46.78
Step 19: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.211820 0.295131 0.000000 100/100 2024-02-26 19:29:38.939043 2024-02-26 19:29:32.157862 A al_loss false 0.211820 0.295131 0.000000 100/100 2024-02-26 19:29:32.658597 2024-02-26 19:29:28.193292 A al_jitter true 0.211820 0.295131 0.000000 100/100 2024-02-26 19:29:36.162781 2024-02-26 19:29:20.075653
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:29:44.036091 2024-02-26 19:29:36.162781 4 43.56 al_loss false 2024-02-26 19:29:44.185128 2024-02-26 19:29:40.620957 6 46.76 al_rtt false 2024-02-26 19:29:42.079514 2024-02-26 19:29:38.939043 6 47.67
Step 22: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000754 0.000189 0.000000 100/100 2024-02-26 19:29:42.079514 2024-02-26 19:29:38.939043 A al_loss false 0.000754 0.000189 0.000000 100/100 2024-02-26 19:29:44.185128 2024-02-26 19:29:40.620957 A al_jitter false 0.000754 0.000189 0.000000 100/100 2024-02-26 19:29:44.036091 2024-02-26 19:29:36.162781
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Test IPv4 FQDN Destination
Description
In this scenario, TWAMP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv4 destination address) and the TWAMP NSM responder service is configured in DUT1.
Scenario
Step 1: Set the following configuration in DUT1:
set interfaces ethernet eth0 address 10.215.200.100/24 set service nsm responder type twamp port 12345
Step 2: Set the following configuration in DUT0:
set interfaces ethernet eth0 address 10.215.200.50/24 set service nsm operation A destination-address test.nsm.fqdn set service nsm operation A type twamp set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A window 100 set service nsm operation A alarm al_loss activate loss 5 set service nsm operation A alarm al_rtt activate rtt 0.2 set service nsm operation A alarm al_jitter activate jitter 0.1 set system alarm al_loss set system alarm al_rtt set system alarm al_jitter set service nsm operation A destination-port 12345 set service dns static host-name testnsm alias test.nsm.fqdn set service dns static host-name testnsm inet 10.215.200.100
Step 3: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ------------------------------------------------------------------- al_jitter false 0 0.00 al_loss false 0 0.00 al_rtt false 0 0.00
Step 4: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
--------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled --------------------------------------------------------------------------------------------- A al_rtt false 0.000058 0.000014 0.000000 9/100 A al_loss false 0.000058 0.000014 0.000000 9/100 A al_jitter false 0.000058 0.000014 0.000000 9/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:29:59.490172 1 46.34 al_loss true 2024-02-26 19:29:58.989011 1 54.06 al_rtt true 2024-02-26 19:30:00.342592 1 33.27
Step 7: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------ Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------ A al_rtt true 0.440460 0.439865 44.000000 100/100 2024-02-26 19:30:00.342592 A al_loss true 0.440460 0.439865 44.000000 100/100 2024-02-26 19:29:58.989011 A al_jitter true 0.440460 0.439865 44.000000 100/100 2024-02-26 19:29:59.490172
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:30:07.760788 2024-02-26 19:29:59.490172 2 66.64 al_loss false 2024-02-26 19:30:07.825107 2024-02-26 19:29:58.989011 2 71.22 al_rtt false 2024-02-26 19:30:06.860851 2024-02-26 19:30:00.342592 2 52.49
Step 10: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000705 0.000037 0.000000 100/100 2024-02-26 19:30:06.860851 2024-02-26 19:30:00.342592 A al_loss false 0.000705 0.000037 0.000000 100/100 2024-02-26 19:30:07.825107 2024-02-26 19:29:58.989011 A al_jitter false 0.000705 0.000037 0.000000 100/100 2024-02-26 19:30:07.760788 2024-02-26 19:29:59.490172
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:30:07.760788 2024-02-26 19:29:59.490172 2 44.89 al_loss false 2024-02-26 19:30:07.825107 2024-02-26 19:29:58.989011 2 47.98 al_rtt true 2024-02-26 19:30:11.269218 2024-02-26 19:30:06.860851 3 52.40
Step 13: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.792727 0.009060 0.000000 100/100 2024-02-26 19:30:11.269218 2024-02-26 19:30:06.860851 A al_loss false 0.792727 0.009060 0.000000 100/100 2024-02-26 19:30:07.825107 2024-02-26 19:29:58.989011 A al_jitter false 0.792727 0.009060 0.000000 100/100 2024-02-26 19:30:07.760788 2024-02-26 19:29:59.490172
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:30:07.760788 2024-02-26 19:29:59.490172 2 34.05 al_loss false 2024-02-26 19:30:19.944733 2024-02-26 19:30:15.427890 4 54.99 al_rtt false 2024-02-26 19:30:19.439820 2024-02-26 19:30:11.269218 4 60.47
Step 16: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000711 0.000055 0.000000 100/100 2024-02-26 19:30:19.439820 2024-02-26 19:30:11.269218 A al_loss false 0.000711 0.000055 0.000000 100/100 2024-02-26 19:30:19.944733 2024-02-26 19:30:15.427890 A al_jitter false 0.000711 0.000055 0.000000 100/100 2024-02-26 19:30:07.760788 2024-02-26 19:29:59.490172
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:30:23.702228 2024-02-26 19:30:07.760788 3 35.82 al_loss false 2024-02-26 19:30:19.944733 2024-02-26 19:30:15.427890 4 44.07 al_rtt true 2024-02-26 19:30:25.523170 2024-02-26 19:30:19.439820 5 50.99
Step 19: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.232749 0.273310 0.000000 100/100 2024-02-26 19:30:25.523170 2024-02-26 19:30:19.439820 A al_loss false 0.232749 0.273310 0.000000 100/100 2024-02-26 19:30:19.944733 2024-02-26 19:30:15.427890 A al_jitter true 0.232749 0.273310 0.000000 100/100 2024-02-26 19:30:23.702228 2024-02-26 19:30:07.760788
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:30:31.377354 2024-02-26 19:30:23.702228 4 44.09 al_loss false 2024-02-26 19:30:31.526224 2024-02-26 19:30:27.911627 6 46.93 al_rtt false 2024-02-26 19:30:29.666673 2024-02-26 19:30:25.523170 6 52.07
Step 22: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000711 0.000046 0.000000 100/100 2024-02-26 19:30:29.666673 2024-02-26 19:30:25.523170 A al_loss false 0.000711 0.000046 0.000000 100/100 2024-02-26 19:30:31.526224 2024-02-26 19:30:27.911627 A al_jitter false 0.000711 0.000046 0.000000 100/100 2024-02-26 19:30:31.377354 2024-02-26 19:30:23.702228
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Test IPv6 Destination
Description
In this scenario, TWAMP NSM operations are configured in DUT0 (using an IPv6 destination address) and the TWAMP NSM responder service is configured in DUT1.
Scenario
Step 1: Set the following configuration in DUT1:
set interfaces ethernet eth0 address 10::3/64 set service nsm responder type twamp port 12345
Step 2: Set the following configuration in DUT0:
set interfaces ethernet eth0 address 10::2/64 set service nsm operation A destination-address 10::3 set service nsm operation A type twamp set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A window 100 set service nsm operation A alarm al_loss activate loss 5 set service nsm operation A alarm al_rtt activate rtt 0.2 set service nsm operation A alarm al_jitter activate jitter 0.1 set system alarm al_loss set system alarm al_rtt set system alarm al_jitter set service nsm operation A destination-port 12345
Step 3: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 0 0.00 al_loss false 2024-02-26 19:30:49.038806 2024-02-26 19:30:44.176222 2 67.64 al_rtt false 2024-02-26 19:30:48.872941 2024-02-26 19:30:44.921698 2 54.93
Step 4: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000667 0.000045 0.000000 100/100 2024-02-26 19:30:48.872941 2024-02-26 19:30:44.921698 A al_loss false 0.000667 0.000045 0.000000 100/100 2024-02-26 19:30:49.038806 2024-02-26 19:30:44.176222 A al_jitter false 0.000667 0.000045 0.000000 100/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:30:53.294680 1 20.26 al_loss true 2024-02-26 19:30:52.139953 2024-02-26 19:30:49.038806 3 65.84 al_rtt true 2024-02-26 19:30:53.293462 2024-02-26 19:30:48.872941 3 50.19
Step 7: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled -------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.530318 0.379731 53.000000 100/100 2024-02-26 19:30:53.293462 2024-02-26 19:30:48.872941 A al_loss true 0.530318 0.379731 53.000000 100/100 2024-02-26 19:30:52.139953 2024-02-26 19:30:49.038806 A al_jitter true 0.530318 0.379731 53.000000 100/100 2024-02-26 19:30:53.294680
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:31:01.065678 2024-02-26 19:30:53.294680 2 40.75 al_loss false 2024-02-26 19:31:01.367406 2024-02-26 19:30:52.139953 4 73.92 al_rtt false 2024-02-26 19:31:00.462680 2024-02-26 19:30:53.293462 4 58.33
Step 10: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000696 0.000046 0.000000 100/100 2024-02-26 19:31:00.462680 2024-02-26 19:30:53.293462 A al_loss false 0.000696 0.000046 0.000000 100/100 2024-02-26 19:31:01.367406 2024-02-26 19:30:52.139953 A al_jitter false 0.000696 0.000046 0.000000 100/100 2024-02-26 19:31:01.065678 2024-02-26 19:30:53.294680
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:31:01.065678 2024-02-26 19:30:53.294680 2 30.99 al_loss false 2024-02-26 19:31:01.367406 2024-02-26 19:30:52.139953 4 56.21 al_rtt true 2024-02-26 19:31:04.676058 2024-02-26 19:31:00.462680 5 56.94
Step 13: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.801701 0.009051 0.000000 100/100 2024-02-26 19:31:04.676058 2024-02-26 19:31:00.462680 A al_loss false 0.801701 0.009051 0.000000 100/100 2024-02-26 19:31:01.367406 2024-02-26 19:30:52.139953 A al_jitter false 0.801701 0.009051 0.000000 100/100 2024-02-26 19:31:01.065678 2024-02-26 19:30:53.294680
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:31:01.065678 2024-02-26 19:30:53.294680 2 25.12 al_loss false 2024-02-26 19:31:13.348142 2024-02-26 19:31:08.834663 6 60.15 al_rtt false 2024-02-26 19:31:12.848905 2024-02-26 19:31:04.676058 6 62.37
Step 16: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000700 0.000049 0.000000 100/100 2024-02-26 19:31:12.848905 2024-02-26 19:31:04.676058 A al_loss false 0.000700 0.000049 0.000000 100/100 2024-02-26 19:31:13.348142 2024-02-26 19:31:08.834663 A al_jitter false 0.000700 0.000049 0.000000 100/100 2024-02-26 19:31:01.065678 2024-02-26 19:30:53.294680
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:31:16.387341 2024-02-26 19:31:01.065678 3 30.00 al_loss false 2024-02-26 19:31:13.348142 2024-02-26 19:31:08.834663 6 50.37 al_rtt false 2024-02-26 19:31:12.848905 2024-02-26 19:31:04.676058 6 52.23
Step 19: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.194185 0.287516 0.000000 100/100 2024-02-26 19:31:12.848905 2024-02-26 19:31:04.676058 A al_loss false 0.194185 0.287516 0.000000 100/100 2024-02-26 19:31:13.348142 2024-02-26 19:31:08.834663 A al_jitter true 0.194185 0.287516 0.000000 100/100 2024-02-26 19:31:16.387341 2024-02-26 19:31:01.065678
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:31:24.728963 2024-02-26 19:31:16.387341 4 37.62 al_loss false 2024-02-26 19:31:24.827692 2024-02-26 19:31:21.367013 8 51.53 al_rtt false 2024-02-26 19:31:22.672748 2024-02-26 19:31:20.444595 8 50.25
Step 22: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000736 0.000124 0.000000 100/100 2024-02-26 19:31:22.672748 2024-02-26 19:31:20.444595 A al_loss false 0.000736 0.000124 0.000000 100/100 2024-02-26 19:31:24.827692 2024-02-26 19:31:21.367013 A al_jitter false 0.000736 0.000124 0.000000 100/100 2024-02-26 19:31:24.728963 2024-02-26 19:31:16.387341
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Test IPv6 FQDN Destination
Description
In this scenario, TWAMP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv6 destination address) and the TWAMP NSM responder service is configured in DUT1.
Scenario
Step 1: Set the following configuration in DUT1:
set interfaces ethernet eth0 address 10::3/64 set service nsm responder type twamp port 12345
Step 2: Set the following configuration in DUT0:
set interfaces ethernet eth0 address 10::2/64 set service nsm operation A destination-address test.nsm.fqdn set service nsm operation A type twamp set service nsm operation A interval 0.05 set service nsm operation A local-interface eth0 set service nsm operation A window 100 set service nsm operation A alarm al_loss activate loss 5 set service nsm operation A alarm al_rtt activate rtt 0.2 set service nsm operation A alarm al_jitter activate jitter 0.1 set system alarm al_loss set system alarm al_rtt set system alarm al_jitter set service nsm operation A destination-port 12345 set service dns static host-name testnsm alias test.nsm.fqdn set service dns static host-name testnsm inet 10::3
Step 3: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 0 0.00 al_loss false 2024-02-26 19:31:43.087486 2024-02-26 19:31:38.314735 2 65.36 al_rtt false 2024-02-26 19:31:43.008109 2024-02-26 19:31:39.061597 2 53.97
Step 4: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000650 0.000061 0.000000 100/100 2024-02-26 19:31:43.008109 2024-02-26 19:31:39.061597 A al_loss false 0.000650 0.000061 0.000000 100/100 2024-02-26 19:31:43.087486 2024-02-26 19:31:38.314735 A al_jitter false 0.000650 0.000061 0.000000 100/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:31:47.279070 1 21.82 al_loss true 2024-02-26 19:31:46.429676 2024-02-26 19:31:43.087486 3 64.05 al_rtt true 2024-02-26 19:31:47.782496 2024-02-26 19:31:43.008109 3 47.65
Step 7: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled -------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.410391 0.419730 41.000000 100/100 2024-02-26 19:31:47.782496 2024-02-26 19:31:43.008109 A al_loss true 0.410391 0.419730 41.000000 100/100 2024-02-26 19:31:46.429676 2024-02-26 19:31:43.087486 A al_jitter true 0.410391 0.419730 41.000000 100/100 2024-02-26 19:31:47.279070
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:31:55.456079 2024-02-26 19:31:47.279070 2 42.64 al_loss false 2024-02-26 19:31:55.607295 2024-02-26 19:31:46.429676 4 72.77 al_rtt false 2024-02-26 19:31:54.557579 2024-02-26 19:31:47.782496 4 55.90
Step 10: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000697 0.000050 0.000000 100/100 2024-02-26 19:31:54.557579 2024-02-26 19:31:47.782496 A al_loss false 0.000697 0.000050 0.000000 100/100 2024-02-26 19:31:55.607295 2024-02-26 19:31:46.429676 A al_jitter false 0.000697 0.000050 0.000000 100/100 2024-02-26 19:31:55.456079 2024-02-26 19:31:47.279070
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:31:55.456079 2024-02-26 19:31:47.279070 2 32.48 al_loss false 2024-02-26 19:31:55.607295 2024-02-26 19:31:46.429676 4 55.42 al_rtt true 2024-02-26 19:31:58.916618 2024-02-26 19:31:54.557579 5 54.99
Step 13: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.792705 0.009060 0.000000 100/100 2024-02-26 19:31:58.916618 2024-02-26 19:31:54.557579 A al_loss false 0.792705 0.009060 0.000000 100/100 2024-02-26 19:31:55.607295 2024-02-26 19:31:46.429676 A al_jitter false 0.792705 0.009060 0.000000 100/100 2024-02-26 19:31:55.456079 2024-02-26 19:31:47.279070
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:31:55.456079 2024-02-26 19:31:47.279070 2 26.35 al_loss false 2024-02-26 19:32:07.538219 2024-02-26 19:32:03.024724 6 59.51 al_rtt false 2024-02-26 19:32:07.037913 2024-02-26 19:31:58.916618 6 60.71
Step 16: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000695 0.000039 0.000000 100/100 2024-02-26 19:32:07.037913 2024-02-26 19:31:58.916618 A al_loss false 0.000695 0.000039 0.000000 100/100 2024-02-26 19:32:07.538219 2024-02-26 19:32:03.024724 A al_jitter false 0.000695 0.000039 0.000000 100/100 2024-02-26 19:31:55.456079 2024-02-26 19:31:47.279070
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-26 19:32:11.660229 2024-02-26 19:31:55.456079 3 28.17 al_loss false 2024-02-26 19:32:07.538219 2024-02-26 19:32:03.024724 6 49.83 al_rtt true 2024-02-26 19:32:13.454331 2024-02-26 19:32:07.037913 7 52.11
Step 19: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.240470 0.284184 0.000000 100/100 2024-02-26 19:32:13.454331 2024-02-26 19:32:07.037913 A al_loss false 0.240470 0.284184 0.000000 100/100 2024-02-26 19:32:07.538219 2024-02-26 19:32:03.024724 A al_jitter true 0.240470 0.284184 0.000000 100/100 2024-02-26 19:32:11.660229 2024-02-26 19:31:55.456079
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-26 19:32:18.669997 2024-02-26 19:32:11.660229 4 35.39 al_loss false 2024-02-26 19:32:19.272931 2024-02-26 19:32:15.559725 8 51.68 al_rtt false 2024-02-26 19:32:17.466877 2024-02-26 19:32:13.454331 8 53.25
Step 22: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000737 0.000123 0.000000 100/100 2024-02-26 19:32:17.466877 2024-02-26 19:32:13.454331 A al_loss false 0.000737 0.000123 0.000000 100/100 2024-02-26 19:32:19.272931 2024-02-26 19:32:15.559725 A al_jitter false 0.000737 0.000123 0.000000 100/100 2024-02-26 19:32:18.669997 2024-02-26 19:32:11.660229
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.