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.000012 0.000000 8/100 A al_loss false 0.000036 0.000012 0.000000 8/100 A al_jitter false 0.000036 0.000012 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-10-10 08:04:54.839631 1 45.13 al_loss true 2024-10-10 08:04:53.884698 1 60.36 al_rtt true 2024-10-10 08:04:55.179910 1 39.76
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.490221 0.419827 49.000000 100/100 2024-10-10 08:04:55.179910 A al_loss true 0.490221 0.419827 49.000000 100/100 2024-10-10 08:04:53.884698 A al_jitter true 0.490221 0.419827 49.000000 100/100 2024-10-10 08:04:54.839631
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-10-10 08:05:02.801808 2024-10-10 08:04:54.839631 2 65.48 al_loss false 2024-10-10 08:05:02.748759 2024-10-10 08:04:53.884698 2 72.92 al_rtt false 2024-10-10 08:05:02.091987 2024-10-10 08:04:55.179910 2 56.88
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.000398 0.000060 0.000000 100/100 2024-10-10 08:05:02.091987 2024-10-10 08:04:55.179910 A al_loss false 0.000398 0.000060 0.000000 100/100 2024-10-10 08:05:02.748759 2024-10-10 08:04:53.884698 A al_jitter false 0.000398 0.000060 0.000000 100/100 2024-10-10 08:05:02.801808 2024-10-10 08:04:54.839631
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-10-10 08:05:02.801808 2024-10-10 08:04:54.839631 2 43.58 al_loss false 2024-10-10 08:05:02.748759 2024-10-10 08:04:53.884698 2 48.53 al_rtt true 2024-10-10 08:05:06.499367 2024-10-10 08:05:02.091987 3 55.16
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.792465 0.009069 0.000000 100/100 2024-10-10 08:05:06.499367 2024-10-10 08:05:02.091987 A al_loss false 0.792465 0.009069 0.000000 100/100 2024-10-10 08:05:02.748759 2024-10-10 08:04:53.884698 A al_jitter false 0.792465 0.009069 0.000000 100/100 2024-10-10 08:05:02.801808 2024-10-10 08:04:54.839631
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-10-10 08:05:02.801808 2024-10-10 08:04:54.839631 2 33.09 al_loss false 2024-10-10 08:05:15.066548 2024-10-10 08:05:10.560546 4 55.58 al_rtt false 2024-10-10 08:05:14.566762 2024-10-10 08:05:06.499367 4 62.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.000459 0.000062 0.000000 100/100 2024-10-10 08:05:14.566762 2024-10-10 08:05:06.499367 A al_loss false 0.000459 0.000062 0.000000 100/100 2024-10-10 08:05:15.066548 2024-10-10 08:05:10.560546 A al_jitter false 0.000459 0.000062 0.000000 100/100 2024-10-10 08:05:02.801808 2024-10-10 08:04:54.839631
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-10-10 08:05:18.738441 2024-10-10 08:05:02.801808 3 35.30 al_loss false 2024-10-10 08:05:15.066548 2024-10-10 08:05:10.560546 4 44.63 al_rtt false 2024-10-10 08:05:14.566762 2024-10-10 08:05:06.499367 4 50.01
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.182712 0.243346 0.000000 100/100 2024-10-10 08:05:14.566762 2024-10-10 08:05:06.499367 A al_loss false 0.182712 0.243346 0.000000 100/100 2024-10-10 08:05:15.066548 2024-10-10 08:05:10.560546 A al_jitter true 0.182712 0.243346 0.000000 100/100 2024-10-10 08:05:18.738441 2024-10-10 08:05:02.801808
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-10-10 08:05:26.341839 2024-10-10 08:05:18.738441 4 43.57 al_loss false 2024-10-10 08:05:26.503387 2024-10-10 08:05:22.829371 6 47.72 al_rtt false 2024-10-10 08:05:23.885519 2024-10-10 08:05:21.873605 6 47.57
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.000417 0.000061 0.000000 100/100 2024-10-10 08:05:23.885519 2024-10-10 08:05:21.873605 A al_loss false 0.000417 0.000061 0.000000 100/100 2024-10-10 08:05:26.503387 2024-10-10 08:05:22.829371 A al_jitter false 0.000417 0.000061 0.000000 100/100 2024-10-10 08:05:26.341839 2024-10-10 08:05:18.738441
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.000045 0.000012 0.000000 9/100 A al_loss false 0.000045 0.000012 0.000000 9/100 A al_jitter false 0.000045 0.000012 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-10-10 08:05:40.635654 1 40.02 al_loss true 2024-10-10 08:05:39.578660 1 56.61 al_rtt true 2024-10-10 08:05:41.831223 1 21.17
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.350255 0.399871 35.000000 100/100 2024-10-10 08:05:41.831223 A al_loss true 0.350255 0.399871 35.000000 100/100 2024-10-10 08:05:39.578660 A al_jitter true 0.350255 0.399871 35.000000 100/100 2024-10-10 08:05:40.635654
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-10-10 08:05:48.024887 2024-10-10 08:05:40.635654 2 60.95 al_loss false 2024-10-10 08:05:48.344372 2024-10-10 08:05:39.578660 2 72.26 al_rtt false 2024-10-10 08:05:47.391653 2024-10-10 08:05:41.831223 2 45.85
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.000380 0.000053 0.000000 100/100 2024-10-10 08:05:47.391653 2024-10-10 08:05:41.831223 A al_loss false 0.000380 0.000053 0.000000 100/100 2024-10-10 08:05:48.344372 2024-10-10 08:05:39.578660 A al_jitter false 0.000380 0.000053 0.000000 100/100 2024-10-10 08:05:48.024887 2024-10-10 08:05:40.635654
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-10-10 08:05:48.024887 2024-10-10 08:05:40.635654 2 40.96 al_loss false 2024-10-10 08:05:48.344372 2024-10-10 08:05:39.578660 2 48.57 al_rtt true 2024-10-10 08:05:51.758371 2024-10-10 08:05:47.391653 3 48.07
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.783451 0.009064 0.000000 100/100 2024-10-10 08:05:51.758371 2024-10-10 08:05:47.391653 A al_loss false 0.783451 0.009064 0.000000 100/100 2024-10-10 08:05:48.344372 2024-10-10 08:05:39.578660 A al_jitter false 0.783451 0.009064 0.000000 100/100 2024-10-10 08:05:48.024887 2024-10-10 08:05:40.635654
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-10-10 08:05:48.024887 2024-10-10 08:05:40.635654 2 31.00 al_loss false 2024-10-10 08:06:00.316747 2024-10-10 08:05:55.806837 4 55.68 al_rtt false 2024-10-10 08:05:59.823737 2024-10-10 08:05:51.758371 4 57.16
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.000381 0.000048 0.000000 100/100 2024-10-10 08:05:59.823737 2024-10-10 08:05:51.758371 A al_loss false 0.000381 0.000048 0.000000 100/100 2024-10-10 08:06:00.316747 2024-10-10 08:05:55.806837 A al_jitter false 0.000381 0.000048 0.000000 100/100 2024-10-10 08:05:48.024887 2024-10-10 08:05:40.635654
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-10-10 08:06:03.705333 2024-10-10 08:05:48.024887 3 34.67 al_loss false 2024-10-10 08:06:00.316747 2024-10-10 08:05:55.806837 4 44.50 al_rtt true 2024-10-10 08:06:05.191751 2024-10-10 08:05:59.823737 5 50.59
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.245905 0.293741 0.000000 100/100 2024-10-10 08:06:05.191751 2024-10-10 08:05:59.823737 A al_loss false 0.245905 0.293741 0.000000 100/100 2024-10-10 08:06:00.316747 2024-10-10 08:05:55.806837 A al_jitter true 0.245905 0.293741 0.000000 100/100 2024-10-10 08:06:03.705333 2024-10-10 08:05:48.024887
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-10-10 08:06:12.051411 2024-10-10 08:06:03.705333 4 44.07 al_loss false 2024-10-10 08:06:12.009463 2024-10-10 08:06:08.347431 6 47.43 al_rtt false 2024-10-10 08:06:10.308015 2024-10-10 08:06:05.191751 6 52.48
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.000484 0.000184 0.000000 100/100 2024-10-10 08:06:10.308015 2024-10-10 08:06:05.191751 A al_loss false 0.000484 0.000184 0.000000 100/100 2024-10-10 08:06:12.009463 2024-10-10 08:06:08.347431 A al_jitter false 0.000484 0.000184 0.000000 100/100 2024-10-10 08:06:12.051411 2024-10-10 08:06:03.705333
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-10-10 08:06:28.140551 2024-10-10 08:06:23.339357 2 68.35 al_rtt false 2024-10-10 08:06:27.990383 2024-10-10 08:06:24.085078 2 55.63
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.000406 0.000314 0.000000 100/100 2024-10-10 08:06:27.990383 2024-10-10 08:06:24.085078 A al_loss false 0.000406 0.000314 0.000000 100/100 2024-10-10 08:06:28.140551 2024-10-10 08:06:23.339357 A al_jitter false 0.000406 0.000314 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-10-10 08:06:31.748428 1 24.77 al_loss true 2024-10-10 08:06:30.994032 2024-10-10 08:06:28.140551 3 67.66 al_rtt true 2024-10-10 08:06:32.241286 2024-10-10 08:06:27.990383 3 51.13
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.490228 0.419828 49.000000 100/100 2024-10-10 08:06:32.241286 2024-10-10 08:06:27.990383 A al_loss true 0.490228 0.419828 49.000000 100/100 2024-10-10 08:06:30.994032 2024-10-10 08:06:28.140551 A al_jitter true 0.490228 0.419828 49.000000 100/100 2024-10-10 08:06:31.748428
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-10-10 08:06:40.008942 2024-10-10 08:06:31.748428 2 44.06 al_loss false 2024-10-10 08:06:40.209782 2024-10-10 08:06:30.994032 4 74.78 al_rtt false 2024-10-10 08:06:39.027669 2024-10-10 08:06:32.241286 4 57.05
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.000445 0.000054 0.000000 100/100 2024-10-10 08:06:39.027669 2024-10-10 08:06:32.241286 A al_loss false 0.000445 0.000054 0.000000 100/100 2024-10-10 08:06:40.209782 2024-10-10 08:06:30.994032 A al_jitter false 0.000445 0.000054 0.000000 100/100 2024-10-10 08:06:40.008942 2024-10-10 08:06:31.748428
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-10-10 08:06:40.008942 2024-10-10 08:06:31.748428 2 33.46 al_loss false 2024-10-10 08:06:40.209782 2024-10-10 08:06:30.994032 4 56.79 al_rtt true 2024-10-10 08:06:43.532226 2024-10-10 08:06:39.027669 5 56.10
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.792492 0.009075 0.000000 100/100 2024-10-10 08:06:43.532226 2024-10-10 08:06:39.027669 A al_loss false 0.792492 0.009075 0.000000 100/100 2024-10-10 08:06:40.209782 2024-10-10 08:06:30.994032 A al_jitter false 0.792492 0.009075 0.000000 100/100 2024-10-10 08:06:40.008942 2024-10-10 08:06:31.748428
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-10-10 08:06:40.008942 2024-10-10 08:06:31.748428 2 27.05 al_loss false 2024-10-10 08:06:52.191893 2024-10-10 08:06:47.677306 6 60.68 al_rtt false 2024-10-10 08:06:51.687490 2024-10-10 08:06:43.532226 6 61.73
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.000465 0.000068 0.000000 100/100 2024-10-10 08:06:51.687490 2024-10-10 08:06:43.532226 A al_loss false 0.000465 0.000068 0.000000 100/100 2024-10-10 08:06:52.191893 2024-10-10 08:06:47.677306 A al_jitter false 0.000465 0.000068 0.000000 100/100 2024-10-10 08:06:40.008942 2024-10-10 08:06:31.748428
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-10-10 08:06:55.601961 2024-10-10 08:06:40.008942 3 30.68 al_loss false 2024-10-10 08:06:52.191893 2024-10-10 08:06:47.677306 6 50.69 al_rtt true 2024-10-10 08:06:57.974075 2024-10-10 08:06:51.687490 7 53.16
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.259654 0.278227 0.000000 100/100 2024-10-10 08:06:57.974075 2024-10-10 08:06:51.687490 A al_loss false 0.259654 0.278227 0.000000 100/100 2024-10-10 08:06:52.191893 2024-10-10 08:06:47.677306 A al_jitter true 0.259654 0.278227 0.000000 100/100 2024-10-10 08:06:55.601961 2024-10-10 08:06:40.008942
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-10-10 08:07:03.359026 2024-10-10 08:06:55.601961 4 37.85 al_loss false 2024-10-10 08:07:03.857790 2024-10-10 08:06:59.855238 8 53.26 al_rtt false 2024-10-10 08:07:02.559623 2024-10-10 08:06:57.974075 8 55.39
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.000453 0.000083 0.000000 100/100 2024-10-10 08:07:02.559623 2024-10-10 08:06:57.974075 A al_loss false 0.000453 0.000083 0.000000 100/100 2024-10-10 08:07:03.857790 2024-10-10 08:06:59.855238 A al_jitter false 0.000453 0.000083 0.000000 100/100 2024-10-10 08:07:03.359026 2024-10-10 08:06:55.601961
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-10-10 08:07:22.307828 2024-10-10 08:07:17.205377 2 72.21 al_rtt false 2024-10-10 08:07:21.975059 2024-10-10 08:07:17.955493 2 56.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.000796 0.000954 0.000000 100/100 2024-10-10 08:07:21.975059 2024-10-10 08:07:17.955493 A al_loss false 0.000796 0.000954 0.000000 100/100 2024-10-10 08:07:22.307828 2024-10-10 08:07:17.205377 A al_jitter false 0.000796 0.000954 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-10-10 08:07:25.662272 1 24.54 al_loss true 2024-10-10 08:07:25.262926 2024-10-10 08:07:22.307828 3 66.74 al_rtt true 2024-10-10 08:07:26.871011 2024-10-10 08:07:21.975059 3 46.11
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.410248 0.439836 41.000000 100/100 2024-10-10 08:07:26.871011 2024-10-10 08:07:21.975059 A al_loss true 0.410248 0.439836 41.000000 100/100 2024-10-10 08:07:25.262926 2024-10-10 08:07:22.307828 A al_jitter true 0.410248 0.439836 41.000000 100/100 2024-10-10 08:07:25.662272
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-10-10 08:07:33.695954 2024-10-10 08:07:25.662272 2 42.80 al_loss false 2024-10-10 08:07:33.938494 2024-10-10 08:07:25.262926 4 73.37 al_rtt false 2024-10-10 08:07:32.930769 2024-10-10 08:07:26.871011 4 53.69
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.000398 0.000055 0.000000 100/100 2024-10-10 08:07:32.930769 2024-10-10 08:07:26.871011 A al_loss false 0.000398 0.000055 0.000000 100/100 2024-10-10 08:07:33.938494 2024-10-10 08:07:25.262926 A al_jitter false 0.000398 0.000055 0.000000 100/100 2024-10-10 08:07:33.695954 2024-10-10 08:07:25.662272
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-10-10 08:07:33.695954 2024-10-10 08:07:25.662272 2 32.55 al_loss false 2024-10-10 08:07:33.938494 2024-10-10 08:07:25.262926 4 55.80 al_rtt true 2024-10-10 08:07:37.391169 2024-10-10 08:07:32.930769 5 53.49
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.792454 0.009055 0.000000 100/100 2024-10-10 08:07:37.391169 2024-10-10 08:07:32.930769 A al_loss false 0.792454 0.009055 0.000000 100/100 2024-10-10 08:07:33.938494 2024-10-10 08:07:25.262926 A al_jitter false 0.792454 0.009055 0.000000 100/100 2024-10-10 08:07:33.695954 2024-10-10 08:07:25.662272
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-10-10 08:07:33.695954 2024-10-10 08:07:25.662272 2 26.28 al_loss false 2024-10-10 08:07:46.015494 2024-10-10 08:07:41.493339 6 59.85 al_rtt false 2024-10-10 08:07:45.511702 2024-10-10 08:07:37.391169 6 59.53
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.000402 0.000080 0.000000 100/100 2024-10-10 08:07:45.511702 2024-10-10 08:07:37.391169 A al_loss false 0.000402 0.000080 0.000000 100/100 2024-10-10 08:07:46.015494 2024-10-10 08:07:41.493339 A al_jitter false 0.000402 0.000080 0.000000 100/100 2024-10-10 08:07:33.695954 2024-10-10 08:07:25.662272
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-10-10 08:07:49.589367 2024-10-10 08:07:33.695954 3 29.45 al_loss false 2024-10-10 08:07:46.015494 2024-10-10 08:07:41.493339 6 50.18 al_rtt true 2024-10-10 08:07:52.100097 2024-10-10 08:07:45.511702 7 50.44
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.206596 0.255997 0.000000 100/100 2024-10-10 08:07:52.100097 2024-10-10 08:07:45.511702 A al_loss false 0.206596 0.255997 0.000000 100/100 2024-10-10 08:07:46.015494 2024-10-10 08:07:41.493339 A al_jitter true 0.206596 0.255997 0.000000 100/100 2024-10-10 08:07:49.589367 2024-10-10 08:07:33.695954
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-10-10 08:07:57.535206 2024-10-10 08:07:49.589367 4 37.76 al_loss false 2024-10-10 08:07:57.481508 2024-10-10 08:07:53.933626 8 51.61 al_rtt false 2024-10-10 08:07:55.281012 2024-10-10 08:07:52.100097 8 50.51
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.000423 0.000059 0.000000 100/100 2024-10-10 08:07:55.281012 2024-10-10 08:07:52.100097 A al_loss false 0.000423 0.000059 0.000000 100/100 2024-10-10 08:07:57.481508 2024-10-10 08:07:53.933626 A al_jitter false 0.000423 0.000059 0.000000 100/100 2024-10-10 08:07:57.535206 2024-10-10 08:07:49.589367
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.