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.000036 0.000008 0.000000 8/100 A al_loss false 0.000036 0.000008 0.000000 8/100 A al_jitter false 0.000036 0.000008 0.000000 8/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-13 16:05:07.921148 1 47.07 al_loss true 2024-02-13 16:05:07.170248 1 58.84 al_rtt true 2024-02-13 16:05:09.025390 1 29.93
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.410254 0.319898 41.000000 100/100 2024-02-13 16:05:09.025390 A al_loss true 0.410254 0.319898 41.000000 100/100 2024-02-13 16:05:07.170248 A al_jitter true 0.410254 0.319898 41.000000 100/100 2024-02-13 16:05:07.921148
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-13 16:05:16.046653 2024-02-13 16:05:07.921148 2 66.71 al_loss false 2024-02-13 16:05:16.198739 2024-02-13 16:05:07.170248 2 74.19 al_rtt false 2024-02-13 16:05:15.448984 2024-02-13 16:05:09.025390 2 52.76
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.000464 0.000114 0.000000 100/100 2024-02-13 16:05:15.448984 2024-02-13 16:05:09.025390 A al_loss false 0.000464 0.000114 0.000000 100/100 2024-02-13 16:05:16.198739 2024-02-13 16:05:07.170248 A al_jitter false 0.000464 0.000114 0.000000 100/100 2024-02-13 16:05:16.046653 2024-02-13 16:05:07.921148
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-13 16:05:16.046653 2024-02-13 16:05:07.921148 2 44.51 al_loss false 2024-02-13 16:05:16.198739 2024-02-13 16:05:07.170248 2 49.49 al_rtt true 2024-02-13 16:05:19.593787 2024-02-13 16:05:15.448984 3 52.62
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.801457 0.009061 0.000000 100/100 2024-02-13 16:05:19.593787 2024-02-13 16:05:15.448984 A al_loss false 0.801457 0.009061 0.000000 100/100 2024-02-13 16:05:16.198739 2024-02-13 16:05:07.170248 A al_jitter false 0.801457 0.009061 0.000000 100/100 2024-02-13 16:05:16.046653 2024-02-13 16:05:07.921148
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-13 16:05:16.046653 2024-02-13 16:05:07.921148 2 33.69 al_loss false 2024-02-13 16:05:28.315424 2024-02-13 16:05:23.814477 4 56.11 al_rtt false 2024-02-13 16:05:27.824551 2024-02-13 16:05:19.593787 4 60.77
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.000419 0.000050 0.000000 100/100 2024-02-13 16:05:27.824551 2024-02-13 16:05:19.593787 A al_loss false 0.000419 0.000050 0.000000 100/100 2024-02-13 16:05:28.315424 2024-02-13 16:05:23.814477 A al_jitter false 0.000419 0.000050 0.000000 100/100 2024-02-13 16:05:16.046653 2024-02-13 16:05:07.921148
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-13 16:05:31.679034 2024-02-13 16:05:16.046653 3 36.57 al_loss false 2024-02-13 16:05:28.315424 2024-02-13 16:05:23.814477 4 45.09 al_rtt true 2024-02-13 16:05:33.970849 2024-02-13 16:05:27.824551 5 50.70
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.217081 0.302384 0.000000 100/100 2024-02-13 16:05:33.970849 2024-02-13 16:05:27.824551 A al_loss false 0.217081 0.302384 0.000000 100/100 2024-02-13 16:05:28.315424 2024-02-13 16:05:23.814477 A al_jitter true 0.217081 0.302384 0.000000 100/100 2024-02-13 16:05:31.679034 2024-02-13 16:05:16.046653
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-13 16:05:39.698994 2024-02-13 16:05:31.679034 4 45.16 al_loss false 2024-02-13 16:05:39.845305 2024-02-13 16:05:35.974721 6 48.68 al_rtt false 2024-02-13 16:05:38.039015 2024-02-13 16:05:33.970849 6 52.37
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.000445 0.000125 0.000000 100/100 2024-02-13 16:05:38.039015 2024-02-13 16:05:33.970849 A al_loss false 0.000445 0.000125 0.000000 100/100 2024-02-13 16:05:39.845305 2024-02-13 16:05:35.974721 A al_jitter false 0.000445 0.000125 0.000000 100/100 2024-02-13 16:05:39.698994 2024-02-13 16:05:31.679034
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.000028 0.000005 0.000000 7/100 A al_loss false 0.000028 0.000005 0.000000 7/100 A al_jitter false 0.000028 0.000005 0.000000 7/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-13 16:05:54.054107 1 39.78 al_loss true 2024-02-13 16:05:53.061639 1 55.64 al_rtt true 2024-02-13 16:05:54.605448 1 30.97
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.420239 0.419844 42.000000 100/100 2024-02-13 16:05:54.605448 A al_loss true 0.420239 0.419844 42.000000 100/100 2024-02-13 16:05:53.061639 A al_jitter true 0.420239 0.419844 42.000000 100/100 2024-02-13 16:05:54.054107
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-13 16:06:01.324962 2024-02-13 16:05:54.054107 2 60.06 al_loss false 2024-02-13 16:06:01.416800 2024-02-13 16:05:53.061639 2 69.05 al_rtt false 2024-02-13 16:06:00.518235 2024-02-13 16:05:54.605448 2 48.82
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.000406 0.000050 0.000000 100/100 2024-02-13 16:06:00.518235 2024-02-13 16:05:54.605448 A al_loss false 0.000406 0.000050 0.000000 100/100 2024-02-13 16:06:01.416800 2024-02-13 16:05:53.061639 A al_jitter false 0.000406 0.000050 0.000000 100/100 2024-02-13 16:06:01.324962 2024-02-13 16:05:54.054107
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-13 16:06:01.324962 2024-02-13 16:05:54.054107 2 40.47 al_loss false 2024-02-13 16:06:01.416800 2024-02-13 16:05:53.061639 2 46.51 al_rtt true 2024-02-13 16:06:05.071074 2024-02-13 16:06:00.518235 3 50.54
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.792432 0.009058 0.000000 100/100 2024-02-13 16:06:05.071074 2024-02-13 16:06:00.518235 A al_loss false 0.792432 0.009058 0.000000 100/100 2024-02-13 16:06:01.416800 2024-02-13 16:05:53.061639 A al_jitter false 0.792432 0.009058 0.000000 100/100 2024-02-13 16:06:01.324962 2024-02-13 16:05:54.054107
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-13 16:06:01.324962 2024-02-13 16:05:54.054107 2 30.68 al_loss false 2024-02-13 16:06:13.638325 2024-02-13 16:06:09.135442 4 54.26 al_rtt false 2024-02-13 16:06:13.143720 2024-02-13 16:06:05.071074 4 58.99
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.000401 0.000048 0.000000 100/100 2024-02-13 16:06:13.143720 2024-02-13 16:06:05.071074 A al_loss false 0.000401 0.000048 0.000000 100/100 2024-02-13 16:06:13.638325 2024-02-13 16:06:09.135442 A al_jitter false 0.000401 0.000048 0.000000 100/100 2024-02-13 16:06:01.324962 2024-02-13 16:05:54.054107
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-13 16:06:17.179223 2024-02-13 16:06:01.324962 3 33.73 al_loss false 2024-02-13 16:06:13.638325 2024-02-13 16:06:09.135442 4 43.41 al_rtt false 2024-02-13 16:06:13.143720 2024-02-13 16:06:05.071074 4 47.20
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.159572 0.223615 0.000000 100/100 2024-02-13 16:06:13.143720 2024-02-13 16:06:05.071074 A al_loss false 0.159572 0.223615 0.000000 100/100 2024-02-13 16:06:13.638325 2024-02-13 16:06:09.135442 A al_jitter true 0.159572 0.223615 0.000000 100/100 2024-02-13 16:06:17.179223 2024-02-13 16:06:01.324962
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-13 16:06:25.129960 2024-02-13 16:06:17.179223 4 42.90 al_loss false 2024-02-13 16:06:25.213051 2024-02-13 16:06:21.421302 6 46.94 al_rtt false 2024-02-13 16:06:13.143720 2024-02-13 16:06:05.071074 4 39.41
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.000435 0.000057 0.000000 100/100 2024-02-13 16:06:13.143720 2024-02-13 16:06:05.071074 A al_loss false 0.000435 0.000057 0.000000 100/100 2024-02-13 16:06:25.213051 2024-02-13 16:06:21.421302 A al_jitter false 0.000435 0.000057 0.000000 100/100 2024-02-13 16:06:25.129960 2024-02-13 16:06:17.179223
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-13 16:06:41.454359 2024-02-13 16:06:36.765528 2 66.32 al_rtt false 2024-02-13 16:06:41.404307 2024-02-13 16:06:37.514234 2 55.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.000414 0.000569 0.000000 100/100 2024-02-13 16:06:41.404307 2024-02-13 16:06:37.514234 A al_loss false 0.000414 0.000569 0.000000 100/100 2024-02-13 16:06:41.454359 2024-02-13 16:06:36.765528 A al_jitter false 0.000414 0.000569 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-13 16:06:45.167262 1 25.16 al_loss true 2024-02-13 16:06:44.772280 2024-02-13 16:06:41.454359 3 64.00 al_rtt true 2024-02-13 16:06:46.478785 2024-02-13 16:06:41.404307 3 44.85
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.400241 0.499820 40.000000 100/100 2024-02-13 16:06:46.478785 2024-02-13 16:06:41.404307 A al_loss true 0.400241 0.499820 40.000000 100/100 2024-02-13 16:06:44.772280 2024-02-13 16:06:41.454359 A al_jitter true 0.400241 0.499820 40.000000 100/100 2024-02-13 16:06:45.167262
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-13 16:06:53.385239 2024-02-13 16:06:45.167262 2 43.43 al_loss false 2024-02-13 16:06:53.741857 2024-02-13 16:06:44.772280 4 72.21 al_rtt false 2024-02-13 16:06:52.485952 2024-02-13 16:06:46.478785 4 52.31
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.000419 0.000069 0.000000 100/100 2024-02-13 16:06:52.485952 2024-02-13 16:06:46.478785 A al_loss false 0.000419 0.000069 0.000000 100/100 2024-02-13 16:06:53.741857 2024-02-13 16:06:44.772280 A al_jitter false 0.000419 0.000069 0.000000 100/100 2024-02-13 16:06:53.385239 2024-02-13 16:06:45.167262
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-13 16:06:53.385239 2024-02-13 16:06:45.167262 2 32.90 al_loss false 2024-02-13 16:06:53.741857 2024-02-13 16:06:44.772280 4 54.69 al_rtt true 2024-02-13 16:06:57.244338 2024-02-13 16:06:52.485952 5 52.03
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.783457 0.009101 0.000000 100/100 2024-02-13 16:06:57.244338 2024-02-13 16:06:52.485952 A al_loss false 0.783457 0.009101 0.000000 100/100 2024-02-13 16:06:53.741857 2024-02-13 16:06:44.772280 A al_jitter false 0.783457 0.009101 0.000000 100/100 2024-02-13 16:06:53.385239 2024-02-13 16:06:45.167262
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-13 16:06:53.385239 2024-02-13 16:06:45.167262 2 26.73 al_loss false 2024-02-13 16:07:05.764203 2024-02-13 16:07:01.250480 6 59.12 al_rtt false 2024-02-13 16:07:05.265883 2024-02-13 16:06:57.244338 6 58.28
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.000442 0.000096 0.000000 100/100 2024-02-13 16:07:05.265883 2024-02-13 16:06:57.244338 A al_loss false 0.000442 0.000096 0.000000 100/100 2024-02-13 16:07:05.764203 2024-02-13 16:07:01.250480 A al_jitter false 0.000442 0.000096 0.000000 100/100 2024-02-13 16:06:53.385239 2024-02-13 16:06:45.167262
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-13 16:07:09.612313 2024-02-13 16:06:53.385239 3 29.10 al_loss false 2024-02-13 16:07:05.764203 2024-02-13 16:07:01.250480 6 49.50 al_rtt false 2024-02-13 16:07:05.265883 2024-02-13 16:06:57.244338 6 48.81
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.211914 0.273784 0.000000 100/100 2024-02-13 16:07:12.126778 2024-02-13 16:07:05.265883 A al_loss false 0.211914 0.273784 0.000000 100/100 2024-02-13 16:07:05.764203 2024-02-13 16:07:01.250480 A al_jitter true 0.211914 0.273784 0.000000 100/100 2024-02-13 16:07:09.612313 2024-02-13 16:06:53.385239
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-13 16:07:17.249333 2024-02-13 16:07:09.612313 4 37.30 al_loss false 2024-02-13 16:07:17.215423 2024-02-13 16:07:13.527107 8 51.44 al_rtt false 2024-02-13 16:07:15.589390 2024-02-13 16:07:12.126778 8 50.31
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.000442 0.000056 0.000000 100/100 2024-02-13 16:07:15.589390 2024-02-13 16:07:12.126778 A al_loss false 0.000442 0.000056 0.000000 100/100 2024-02-13 16:07:17.215423 2024-02-13 16:07:13.527107 A al_jitter false 0.000442 0.000056 0.000000 100/100 2024-02-13 16:07:17.249333 2024-02-13 16:07:09.612313
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-13 16:07:35.728613 2024-02-13 16:07:30.709275 2 71.06 al_rtt false 2024-02-13 16:07:35.408951 2024-02-13 16:07:31.455553 2 55.90
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.000785 0.000962 0.000000 100/100 2024-02-13 16:07:35.408951 2024-02-13 16:07:31.455553 A al_loss false 0.000785 0.000962 0.000000 100/100 2024-02-13 16:07:35.728613 2024-02-13 16:07:30.709275 A al_jitter false 0.000785 0.000962 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-13 16:07:38.870721 1 26.64 al_loss true 2024-02-13 16:07:38.516418 2024-02-13 16:07:35.728613 3 67.78 al_rtt true 2024-02-13 16:07:39.823942 2024-02-13 16:07:35.408951 3 49.58
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.430229 0.439839 43.000000 100/100 2024-02-13 16:07:39.823942 2024-02-13 16:07:35.408951 A al_loss true 0.430229 0.439839 43.000000 100/100 2024-02-13 16:07:38.516418 2024-02-13 16:07:35.728613 A al_jitter true 0.430229 0.439839 43.000000 100/100 2024-02-13 16:07:38.870721
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-13 16:07:47.516021 2024-02-13 16:07:38.870721 2 45.86 al_loss false 2024-02-13 16:07:47.455388 2024-02-13 16:07:38.516418 4 74.07 al_rtt false 2024-02-13 16:07:46.294047 2024-02-13 16:07:39.823942 4 55.29
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.000420 0.000054 0.000000 100/100 2024-02-13 16:07:46.294047 2024-02-13 16:07:39.823942 A al_loss false 0.000420 0.000054 0.000000 100/100 2024-02-13 16:07:47.455388 2024-02-13 16:07:38.516418 A al_jitter false 0.000420 0.000054 0.000000 100/100 2024-02-13 16:07:47.516021 2024-02-13 16:07:38.870721
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-13 16:07:47.516021 2024-02-13 16:07:38.870721 2 34.94 al_loss false 2024-02-13 16:07:47.455388 2024-02-13 16:07:38.516418 4 56.43 al_rtt true 2024-02-13 16:07:50.903198 2024-02-13 16:07:46.294047 5 54.74
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.792425 0.009069 0.000000 100/100 2024-02-13 16:07:50.903198 2024-02-13 16:07:46.294047 A al_loss false 0.792425 0.009069 0.000000 100/100 2024-02-13 16:07:47.455388 2024-02-13 16:07:38.516418 A al_jitter false 0.792425 0.009069 0.000000 100/100 2024-02-13 16:07:47.516021 2024-02-13 16:07:38.870721
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-13 16:07:47.516021 2024-02-13 16:07:38.870721 2 28.20 al_loss false 2024-02-13 16:07:59.573694 2024-02-13 16:07:55.071034 6 60.22 al_rtt false 2024-02-13 16:07:59.077785 2024-02-13 16:07:50.903198 6 60.65
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.000407 0.000051 0.000000 100/100 2024-02-13 16:07:59.077785 2024-02-13 16:07:50.903198 A al_loss false 0.000407 0.000051 0.000000 100/100 2024-02-13 16:07:59.573694 2024-02-13 16:07:55.071034 A al_jitter false 0.000407 0.000051 0.000000 100/100 2024-02-13 16:07:47.516021 2024-02-13 16:07:38.870721
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-13 16:08:02.893368 2024-02-13 16:07:47.516021 3 31.86 al_loss false 2024-02-13 16:07:59.573694 2024-02-13 16:07:55.071034 6 50.40 al_rtt false 2024-02-13 16:07:59.077785 2024-02-13 16:07:50.903198 6 50.76
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.186616 0.293109 0.000000 100/100 2024-02-13 16:07:59.077785 2024-02-13 16:07:50.903198 A al_loss false 0.186616 0.293109 0.000000 100/100 2024-02-13 16:07:59.573694 2024-02-13 16:07:55.071034 A al_jitter true 0.186616 0.293109 0.000000 100/100 2024-02-13 16:08:02.893368 2024-02-13 16:07:47.516021
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-13 16:08:10.749945 2024-02-13 16:08:02.893368 4 38.96 al_loss false 2024-02-13 16:07:59.573694 2024-02-13 16:07:55.071034 6 43.59 al_rtt false 2024-02-13 16:08:07.588823 2024-02-13 16:08:06.934815 8 45.45
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.000402 0.000052 0.000000 100/100 2024-02-13 16:08:07.588823 2024-02-13 16:08:06.934815 A al_loss false 0.000402 0.000052 0.000000 100/100 2024-02-13 16:07:59.573694 2024-02-13 16:07:55.071034 A al_jitter false 0.000402 0.000052 0.000000 100/100 2024-02-13 16:08:10.749945 2024-02-13 16:08:02.893368
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.