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.000026 0.000009 0.000000 6/100 A al_loss false 0.000026 0.000009 0.000000 6/100 A al_jitter false 0.000026 0.000009 0.000000 6/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-09 08:31:08.748333 1 48.84 al_loss true 2024-10-09 08:31:08.053818 1 60.67 al_rtt true 2024-10-09 08:31:09.698274 1 32.71
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.300402 0.379795 30.000000 98/100 2024-10-09 08:31:09.698274 A al_loss true 0.300402 0.379795 30.000000 98/100 2024-10-09 08:31:08.053818 A al_jitter true 0.300402 0.379795 30.000000 98/100 2024-10-09 08:31:08.748333
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-09 08:31:16.268320 2024-10-09 08:31:08.748333 2 65.82 al_loss false 2024-10-09 08:31:16.785567 2024-10-09 08:31:08.053818 2 76.44 al_rtt false 2024-10-09 08:31:15.775084 2024-10-09 08:31:09.698274 2 53.20
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.000580 0.000132 0.000000 100/100 2024-10-09 08:31:15.775084 2024-10-09 08:31:09.698274 A al_loss false 0.000580 0.000132 0.000000 100/100 2024-10-09 08:31:16.785567 2024-10-09 08:31:08.053818 A al_jitter false 0.000580 0.000132 0.000000 100/100 2024-10-09 08:31:16.268320 2024-10-09 08:31:08.748333
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-09 08:31:16.268320 2024-10-09 08:31:08.748333 2 44.09 al_loss false 2024-10-09 08:31:16.785567 2024-10-09 08:31:08.053818 2 51.20 al_rtt true 2024-10-09 08:31:19.678857 2024-10-09 08:31:15.775084 3 53.91
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.774509 0.009139 0.000000 100/100 2024-10-09 08:31:19.678857 2024-10-09 08:31:15.775084 A al_loss false 0.774509 0.009139 0.000000 100/100 2024-10-09 08:31:16.785567 2024-10-09 08:31:08.053818 A al_jitter false 0.774509 0.009139 0.000000 100/100 2024-10-09 08:31:16.268320 2024-10-09 08:31:08.748333
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-09 08:31:16.268320 2024-10-09 08:31:08.748333 2 33.32 al_loss false 2024-10-09 08:31:28.046734 2024-10-09 08:31:23.531889 4 58.69 al_rtt false 2024-10-09 08:31:27.544358 2024-10-09 08:31:19.678857 4 61.78
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.000598 0.000142 0.000000 100/100 2024-10-09 08:31:27.544358 2024-10-09 08:31:19.678857 A al_loss false 0.000598 0.000142 0.000000 100/100 2024-10-09 08:31:28.046734 2024-10-09 08:31:23.531889 A al_jitter false 0.000598 0.000142 0.000000 100/100 2024-10-09 08:31:16.268320 2024-10-09 08:31:08.748333
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-09 08:31:30.903575 2024-10-09 08:31:16.268320 3 37.36 al_loss false 2024-10-09 08:31:28.046734 2024-10-09 08:31:23.531889 4 47.03 al_rtt false 2024-10-09 08:31:27.544358 2024-10-09 08:31:19.678857 4 49.50
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.182768 0.234273 0.000000 100/100 2024-10-09 08:31:27.544358 2024-10-09 08:31:19.678857 A al_loss false 0.182768 0.234273 0.000000 100/100 2024-10-09 08:31:28.046734 2024-10-09 08:31:23.531889 A al_jitter true 0.182768 0.234273 0.000000 100/100 2024-10-09 08:31:30.903575 2024-10-09 08:31:16.268320
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-09 08:31:38.737314 2024-10-09 08:31:30.903575 4 45.58 al_loss false 2024-10-09 08:31:39.027212 2024-10-09 08:31:35.013894 6 51.25 al_rtt false 2024-10-09 08:31:37.370913 2024-10-09 08:31:34.462056 6 50.04
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.000487 0.000146 0.000000 100/100 2024-10-09 08:31:37.370913 2024-10-09 08:31:34.462056 A al_loss false 0.000487 0.000146 0.000000 100/100 2024-10-09 08:31:39.027212 2024-10-09 08:31:35.013894 A al_jitter false 0.000487 0.000146 0.000000 100/100 2024-10-09 08:31:38.737314 2024-10-09 08:31:30.903575
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.000006 0.000000 6/100 A al_loss false 0.000028 0.000006 0.000000 6/100 A al_jitter false 0.000028 0.000006 0.000000 6/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-09 08:31:48.784252 1 51.64 al_loss true 2024-10-09 08:31:48.072842 1 63.55 al_rtt true 2024-10-09 08:31:49.536035 1 38.98
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.420314 0.419760 42.000000 98/100 2024-10-09 08:31:49.536035 A al_loss true 0.420314 0.419760 42.000000 98/100 2024-10-09 08:31:48.072842 A al_jitter true 0.420314 0.419760 42.000000 98/100 2024-10-09 08:31:48.784252
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-09 08:31:56.549254 2024-10-09 08:31:48.784252 2 67.81 al_loss false 2024-10-09 08:31:56.946380 2024-10-09 08:31:48.072842 2 77.46 al_rtt false 2024-10-09 08:31:55.447409 2024-10-09 08:31:49.536035 2 51.61
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.000533 0.000120 0.000000 100/100 2024-10-09 08:31:55.447409 2024-10-09 08:31:49.536035 A al_loss false 0.000533 0.000120 0.000000 100/100 2024-10-09 08:31:56.946380 2024-10-09 08:31:48.072842 A al_jitter false 0.000533 0.000120 0.000000 100/100 2024-10-09 08:31:56.549254 2024-10-09 08:31:48.784252
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-09 08:31:56.549254 2024-10-09 08:31:48.784252 2 45.48 al_loss false 2024-10-09 08:31:56.946380 2024-10-09 08:31:48.072842 2 51.95 al_rtt true 2024-10-09 08:31:59.900587 2024-10-09 08:31:55.447409 3 52.67
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.765578 0.009154 0.000000 100/100 2024-10-09 08:31:59.900587 2024-10-09 08:31:55.447409 A al_loss false 0.765578 0.009154 0.000000 100/100 2024-10-09 08:31:56.946380 2024-10-09 08:31:48.072842 A al_jitter false 0.765578 0.009154 0.000000 100/100 2024-10-09 08:31:56.549254 2024-10-09 08:31:48.784252
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-09 08:31:56.549254 2024-10-09 08:31:48.784252 2 34.32 al_loss false 2024-10-09 08:32:08.228206 2024-10-09 08:32:03.709619 4 59.18 al_rtt false 2024-10-09 08:32:07.724521 2024-10-09 08:31:59.900587 4 60.70
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.000674 0.000144 0.000000 100/100 2024-10-09 08:32:07.724521 2024-10-09 08:31:59.900587 A al_loss false 0.000674 0.000144 0.000000 100/100 2024-10-09 08:32:08.228206 2024-10-09 08:32:03.709619 A al_jitter false 0.000674 0.000144 0.000000 100/100 2024-10-09 08:31:56.549254 2024-10-09 08:31:48.784252
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-09 08:32:11.813716 2024-10-09 08:31:56.549254 3 35.66 al_loss false 2024-10-09 08:32:08.228206 2024-10-09 08:32:03.709619 4 47.49 al_rtt false 2024-10-09 08:32:07.724521 2024-10-09 08:31:59.900587 4 48.71
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.163672 0.243184 0.000000 100/100 2024-10-09 08:32:07.724521 2024-10-09 08:31:59.900587 A al_loss false 0.163672 0.243184 0.000000 100/100 2024-10-09 08:32:08.228206 2024-10-09 08:32:03.709619 A al_jitter true 0.163672 0.243184 0.000000 100/100 2024-10-09 08:32:11.813716 2024-10-09 08:31:56.549254
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-09 08:32:19.107265 2024-10-09 08:32:11.813716 4 44.68 al_loss false 2024-10-09 08:32:19.107368 2024-10-09 08:32:15.342951 6 50.90 al_rtt false 2024-10-09 08:32:16.952555 2024-10-09 08:32:14.895906 6 46.85
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.000573 0.000130 0.000000 100/100 2024-10-09 08:32:16.952555 2024-10-09 08:32:14.895906 A al_loss false 0.000573 0.000130 0.000000 100/100 2024-10-09 08:32:19.107368 2024-10-09 08:32:15.342951 A al_jitter false 0.000573 0.000130 0.000000 100/100 2024-10-09 08:32:19.107265 2024-10-09 08:32:11.813716
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-09 08:32:30.698535 2024-10-09 08:32:25.931368 2 72.01 al_rtt false 2024-10-09 08:32:30.598987 2024-10-09 08:32:26.695492 2 58.99
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.021275 0.004977 0.000000 100/100 2024-10-09 08:32:30.598987 2024-10-09 08:32:26.695492 A al_loss false 0.021275 0.004977 0.000000 100/100 2024-10-09 08:32:30.698535 2024-10-09 08:32:25.931368 A al_jitter false 0.021275 0.004977 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-09 08:32:33.605872 1 26.57 al_loss true 2024-10-09 08:32:33.112609 2024-10-09 08:32:30.698535 3 69.62 al_rtt true 2024-10-09 08:32:34.255473 2024-10-09 08:32:30.598987 3 53.22
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.480279 0.399815 48.000000 100/100 2024-10-09 08:32:34.255473 2024-10-09 08:32:30.598987 A al_loss true 0.480279 0.399815 48.000000 100/100 2024-10-09 08:32:33.112609 2024-10-09 08:32:30.698535 A al_jitter true 0.480279 0.399815 48.000000 100/100 2024-10-09 08:32:33.605872
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-09 08:32:41.987099 2024-10-09 08:32:33.605872 2 47.08 al_loss false 2024-10-09 08:32:41.927498 2024-10-09 08:32:33.112609 4 76.30 al_rtt false 2024-10-09 08:32:40.428476 2024-10-09 08:32:34.255473 4 56.61
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.000580 0.000153 0.000000 100/100 2024-10-09 08:32:40.428476 2024-10-09 08:32:34.255473 A al_loss false 0.000580 0.000153 0.000000 100/100 2024-10-09 08:32:41.927498 2024-10-09 08:32:33.112609 A al_jitter false 0.000580 0.000153 0.000000 100/100 2024-10-09 08:32:41.987099 2024-10-09 08:32:33.605872
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-09 08:32:41.987099 2024-10-09 08:32:33.605872 2 35.83 al_loss false 2024-10-09 08:32:41.927498 2024-10-09 08:32:33.112609 4 58.07 al_rtt true 2024-10-09 08:32:44.934573 2024-10-09 08:32:40.428476 5 56.29
Step 13: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.774562 0.009168 0.000000 100/100 2024-10-09 08:32:44.934573 2024-10-09 08:32:40.428476 A al_loss false 0.774562 0.009168 0.000000 100/100 2024-10-09 08:32:41.927498 2024-10-09 08:32:33.112609 A al_jitter false 0.774562 0.009168 0.000000 100/100 2024-10-09 08:32:41.987099 2024-10-09 08:32:33.605872
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-09 08:32:41.987099 2024-10-09 08:32:33.605872 2 28.92 al_loss false 2024-10-09 08:32:53.305878 2024-10-09 08:32:48.841134 6 62.27 al_rtt false 2024-10-09 08:32:52.810366 2024-10-09 08:32:44.934573 6 61.95
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.000467 0.000128 0.000000 100/100 2024-10-09 08:32:52.810366 2024-10-09 08:32:44.934573 A al_loss false 0.000467 0.000128 0.000000 100/100 2024-10-09 08:32:53.305878 2024-10-09 08:32:48.841134 A al_jitter false 0.000467 0.000128 0.000000 100/100 2024-10-09 08:32:41.987099 2024-10-09 08:32:33.605872
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-09 08:32:56.152350 2024-10-09 08:32:41.987099 3 33.07 al_loss false 2024-10-09 08:32:53.305878 2024-10-09 08:32:48.841134 6 52.20 al_rtt true 2024-10-09 08:32:58.577748 2024-10-09 08:32:52.810366 7 53.75
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.220576 0.296962 0.000000 100/100 2024-10-09 08:32:58.577748 2024-10-09 08:32:52.810366 A al_loss false 0.220576 0.296962 0.000000 100/100 2024-10-09 08:32:53.305878 2024-10-09 08:32:48.841134 A al_jitter true 0.220576 0.296962 0.000000 100/100 2024-10-09 08:32:56.152350 2024-10-09 08:32:41.987099
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-09 08:33:04.036214 2024-10-09 08:32:56.152350 4 40.53 al_loss false 2024-10-09 08:33:04.239291 2024-10-09 08:33:00.436647 8 54.44 al_rtt false 2024-10-09 08:33:02.229895 2024-10-09 08:32:58.577748 8 53.84
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.000625 0.000113 0.000000 100/100 2024-10-09 08:33:02.229895 2024-10-09 08:32:58.577748 A al_loss false 0.000625 0.000113 0.000000 100/100 2024-10-09 08:33:04.239291 2024-10-09 08:33:00.436647 A al_jitter false 0.000625 0.000113 0.000000 100/100 2024-10-09 08:33:04.036214 2024-10-09 08:32:56.152350
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-09 08:33:16.780281 2024-10-09 08:33:12.174354 2 68.70 al_rtt false 2024-10-09 08:33:16.279496 2024-10-09 08:33:12.914844 2 50.21
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.000612 0.000168 0.000000 100/100 2024-10-09 08:33:16.279496 2024-10-09 08:33:12.914844 A al_loss false 0.000612 0.000168 0.000000 100/100 2024-10-09 08:33:16.780281 2024-10-09 08:33:12.174354 A al_jitter false 0.000612 0.000168 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-09 08:33:19.983696 1 26.03 al_loss true 2024-10-09 08:33:19.533801 2024-10-09 08:33:16.780281 3 66.98 al_rtt true 2024-10-09 08:33:20.688281 2024-10-09 08:33:16.279496 3 47.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.430339 0.399807 43.000000 100/100 2024-10-09 08:33:20.688281 2024-10-09 08:33:16.279496 A al_loss true 0.430339 0.399807 43.000000 100/100 2024-10-09 08:33:19.533801 2024-10-09 08:33:16.780281 A al_jitter true 0.430339 0.399807 43.000000 100/100 2024-10-09 08:33:19.983696
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-09 08:33:28.314834 2024-10-09 08:33:19.983696 2 46.50 al_loss false 2024-10-09 08:33:28.266898 2024-10-09 08:33:19.533801 4 74.43 al_rtt false 2024-10-09 08:33:27.113409 2024-10-09 08:33:20.688281 4 54.64
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.000716 0.000156 0.000000 100/100 2024-10-09 08:33:27.113409 2024-10-09 08:33:20.688281 A al_loss false 0.000716 0.000156 0.000000 100/100 2024-10-09 08:33:28.266898 2024-10-09 08:33:19.533801 A al_jitter false 0.000716 0.000156 0.000000 100/100 2024-10-09 08:33:28.314834 2024-10-09 08:33:19.983696
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-09 08:33:28.314834 2024-10-09 08:33:19.983696 2 35.36 al_loss false 2024-10-09 08:33:28.266898 2024-10-09 08:33:19.533801 4 56.60 al_rtt true 2024-10-09 08:33:31.321142 2024-10-09 08:33:27.113409 5 54.69
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.774658 0.009168 0.000000 100/100 2024-10-09 08:33:31.321142 2024-10-09 08:33:27.113409 A al_loss false 0.774658 0.009168 0.000000 100/100 2024-10-09 08:33:28.266898 2024-10-09 08:33:19.533801 A al_jitter false 0.774658 0.009168 0.000000 100/100 2024-10-09 08:33:28.314834 2024-10-09 08:33:19.983696
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-09 08:33:28.314834 2024-10-09 08:33:19.983696 2 28.61 al_loss false 2024-10-09 08:33:39.693315 2024-10-09 08:33:35.183328 6 61.29 al_rtt false 2024-10-09 08:33:39.191164 2024-10-09 08:33:31.321142 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.000592 0.000155 0.000000 100/100 2024-10-09 08:33:39.191164 2024-10-09 08:33:31.321142 A al_loss false 0.000592 0.000155 0.000000 100/100 2024-10-09 08:33:39.693315 2024-10-09 08:33:35.183328 A al_jitter false 0.000592 0.000155 0.000000 100/100 2024-10-09 08:33:28.314834 2024-10-09 08:33:19.983696
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-09 08:33:42.677461 2024-10-09 08:33:28.314834 3 32.41 al_loss false 2024-10-09 08:33:39.693315 2024-10-09 08:33:35.183328 6 51.35 al_rtt true 2024-10-09 08:33:45.150017 2024-10-09 08:33:39.191164 7 52.13
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.231515 0.318642 0.000000 100/100 2024-10-09 08:33:45.150017 2024-10-09 08:33:39.191164 A al_loss false 0.231515 0.318642 0.000000 100/100 2024-10-09 08:33:39.693315 2024-10-09 08:33:35.183328 A al_jitter true 0.231515 0.318642 0.000000 100/100 2024-10-09 08:33:42.677461 2024-10-09 08:33:28.314834
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-09 08:33:50.182180 2024-10-09 08:33:42.677461 4 39.29 al_loss false 2024-10-09 08:33:50.475789 2024-10-09 08:33:47.009279 8 52.87 al_rtt false 2024-10-09 08:33:48.566100 2024-10-09 08:33:45.150017 8 52.28
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.000593 0.000125 0.000000 100/100 2024-10-09 08:33:48.566100 2024-10-09 08:33:45.150017 A al_loss false 0.000593 0.000125 0.000000 100/100 2024-10-09 08:33:50.475789 2024-10-09 08:33:47.009279 A al_jitter false 0.000593 0.000125 0.000000 100/100 2024-10-09 08:33:50.182180 2024-10-09 08:33:42.677461
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.