Check Udp Operation
This scenario shows how to configure Network Service Monitor (NSM) operations to measure network quality using active traffic probes and the UDP SLA protocol. In addition, the UDP NSM responder service is configured.
Test IPv4 Destination
Description
In this scenario, UDP NSM operations are configured in DUT0 (using an IPv4 destination address) and the UDP 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 udp port 60000
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 udp 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 60000
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.000244 0.000298 0.000000 10/100 A al_loss false 0.000244 0.000298 0.000000 10/100 A al_jitter false 0.000244 0.000298 0.000000 10/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-12-02 21:33:40.703627 1 47.83 al_loss true 2024-12-02 21:33:40.259633 1 54.46 al_rtt true 2024-12-02 21:33:41.925486 1 29.74
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.440354 0.469879 44.000000 100/100 2024-12-02 21:33:41.925486 A al_loss true 0.440354 0.469879 44.000000 100/100 2024-12-02 21:33:40.259633 A al_jitter true 0.440354 0.469879 44.000000 100/100 2024-12-02 21:33:40.703627
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-12-02 21:33:48.979787 2024-12-02 21:33:40.703627 2 65.21 al_loss false 2024-12-02 21:33:49.405147 2024-12-02 21:33:40.259633 2 72.09 al_rtt false 2024-12-02 21:33:48.457654 2024-12-02 21:33:41.925486 2 51.51
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.000482 0.000177 0.000000 100/100 2024-12-02 21:33:48.457654 2024-12-02 21:33:41.925486 A al_loss false 0.000482 0.000177 0.000000 100/100 2024-12-02 21:33:49.405147 2024-12-02 21:33:40.259633 A al_jitter false 0.000482 0.000177 0.000000 100/100 2024-12-02 21:33:48.979787 2024-12-02 21:33:40.703627
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-12-02 21:33:48.979787 2024-12-02 21:33:40.703627 2 43.79 al_loss false 2024-12-02 21:33:49.405147 2024-12-02 21:33:40.259633 2 48.40 al_rtt true 2024-12-02 21:33:52.884877 2024-12-02 21:33:48.457654 3 51.53
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.810492 0.009143 0.000000 100/100 2024-12-02 21:33:52.884877 2024-12-02 21:33:48.457654 A al_loss false 0.810492 0.009143 0.000000 100/100 2024-12-02 21:33:49.405147 2024-12-02 21:33:40.259633 A al_jitter false 0.810492 0.009143 0.000000 100/100 2024-12-02 21:33:48.979787 2024-12-02 21:33:40.703627
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-12-02 21:33:48.979787 2024-12-02 21:33:40.703627 2 33.04 al_loss false 2024-12-02 21:34:01.816819 2024-12-02 21:33:57.330893 4 54.43 al_rtt false 2024-12-02 21:34:01.312004 2024-12-02 21:33:52.884877 4 59.75
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.000421 0.000077 0.000000 100/100 2024-12-02 21:34:01.312004 2024-12-02 21:33:52.884877 A al_loss false 0.000421 0.000077 0.000000 100/100 2024-12-02 21:34:01.816819 2024-12-02 21:33:57.330893 A al_jitter false 0.000421 0.000077 0.000000 100/100 2024-12-02 21:33:48.979787 2024-12-02 21:33:40.703627
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-12-02 21:34:05.463339 2024-12-02 21:33:48.979787 3 36.07 al_loss false 2024-12-02 21:34:01.816819 2024-12-02 21:33:57.330893 4 43.58 al_rtt true 2024-12-02 21:34:08.078531 2024-12-02 21:34:01.312004 5 49.09
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.237167 0.327294 0.000000 100/100 2024-12-02 21:34:08.078531 2024-12-02 21:34:01.312004 A al_loss false 0.237167 0.327294 0.000000 100/100 2024-12-02 21:34:01.816819 2024-12-02 21:33:57.330893 A al_jitter true 0.237167 0.327294 0.000000 100/100 2024-12-02 21:34:05.463339 2024-12-02 21:33:48.979787
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-12-02 21:34:13.895967 2024-12-02 21:34:05.463339 4 44.78 al_loss false 2024-12-02 21:34:13.950146 2024-12-02 21:34:10.225860 6 46.52 al_rtt false 2024-12-02 21:34:12.331127 2024-12-02 21:34:08.078531 6 51.50
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.000421 0.000042 0.000000 100/100 2024-12-02 21:34:12.331127 2024-12-02 21:34:08.078531 A al_loss false 0.000421 0.000042 0.000000 100/100 2024-12-02 21:34:13.950146 2024-12-02 21:34:10.225860 A al_jitter false 0.000421 0.000042 0.000000 100/100 2024-12-02 21:34:13.895967 2024-12-02 21:34:05.463339
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, UDP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv4 destination address) and the UDP 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 udp port 60000
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 udp 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 60000 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.000041 0.000008 0.000000 9/100 A al_loss false 0.000041 0.000008 0.000000 9/100 A al_jitter false 0.000041 0.000008 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-12-02 21:34:31.031783 1 44.32 al_loss true 2024-12-02 21:34:30.645718 1 50.06 al_rtt true 2024-12-02 21:34:32.247807 1 25.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.340407 0.400106 34.000000 100/100 2024-12-02 21:34:32.247807 A al_loss true 0.340407 0.400106 34.000000 100/100 2024-12-02 21:34:30.645718 A al_jitter true 0.340407 0.400106 34.000000 100/100 2024-12-02 21:34:31.031783
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-12-02 21:34:39.268462 2024-12-02 21:34:31.031783 2 65.08 al_loss false 2024-12-02 21:34:39.658211 2024-12-02 21:34:30.645718 2 71.15 al_rtt false 2024-12-02 21:34:38.566405 2024-12-02 21:34:32.247807 2 49.91
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.000473 0.000139 0.000000 100/100 2024-12-02 21:34:38.566405 2024-12-02 21:34:32.247807 A al_loss false 0.000473 0.000139 0.000000 100/100 2024-12-02 21:34:39.658211 2024-12-02 21:34:30.645718 A al_jitter false 0.000473 0.000139 0.000000 100/100 2024-12-02 21:34:39.268462 2024-12-02 21:34:31.031783
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-12-02 21:34:39.268462 2024-12-02 21:34:31.031783 2 43.92 al_loss false 2024-12-02 21:34:39.658211 2024-12-02 21:34:30.645718 2 48.04 al_rtt true 2024-12-02 21:34:42.866131 2024-12-02 21:34:38.566405 3 50.86
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.810451 0.009047 0.000000 100/100 2024-12-02 21:34:42.866131 2024-12-02 21:34:38.566405 A al_loss false 0.810451 0.009047 0.000000 100/100 2024-12-02 21:34:39.658211 2024-12-02 21:34:30.645718 A al_jitter false 0.810451 0.009047 0.000000 100/100 2024-12-02 21:34:39.268462 2024-12-02 21:34:31.031783
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-12-02 21:34:39.268462 2024-12-02 21:34:31.031783 2 33.28 al_loss false 2024-12-02 21:34:51.744265 2024-12-02 21:34:47.236115 4 54.61 al_rtt false 2024-12-02 21:34:51.245901 2024-12-02 21:34:42.866131 4 59.38
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.000418 0.000057 0.000000 100/100 2024-12-02 21:34:51.245901 2024-12-02 21:34:42.866131 A al_loss false 0.000418 0.000057 0.000000 100/100 2024-12-02 21:34:51.744265 2024-12-02 21:34:47.236115 A al_jitter false 0.000418 0.000057 0.000000 100/100 2024-12-02 21:34:39.268462 2024-12-02 21:34:31.031783
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-12-02 21:34:55.521279 2024-12-02 21:34:39.268462 3 35.66 al_loss false 2024-12-02 21:34:51.744265 2024-12-02 21:34:47.236115 4 43.59 al_rtt true 2024-12-02 21:34:57.470044 2024-12-02 21:34:51.245901 5 50.21
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.261077 0.308175 0.000000 100/100 2024-12-02 21:34:57.470044 2024-12-02 21:34:51.245901 A al_loss false 0.261077 0.308175 0.000000 100/100 2024-12-02 21:34:51.744265 2024-12-02 21:34:47.236115 A al_jitter true 0.261077 0.308175 0.000000 100/100 2024-12-02 21:34:55.521279 2024-12-02 21:34:39.268462
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-12-02 21:35:03.544418 2024-12-02 21:34:55.521279 4 43.90 al_loss false 2024-12-02 21:35:03.852741 2024-12-02 21:34:59.948581 6 47.03 al_rtt false 2024-12-02 21:35:02.095315 2024-12-02 21:34:57.470044 6 52.16
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.000751 0.000451 0.000000 100/100 2024-12-02 21:35:02.095315 2024-12-02 21:34:57.470044 A al_loss false 0.000751 0.000451 0.000000 100/100 2024-12-02 21:35:03.852741 2024-12-02 21:34:59.948581 A al_jitter false 0.000751 0.000451 0.000000 100/100 2024-12-02 21:35:03.544418 2024-12-02 21:34:55.521279
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, UDP NSM operations are configured in DUT0 (using an IPv6 destination address) and the UDP 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 udp port 60000
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 udp 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 60000
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-12-02 21:35:22.097391 2024-12-02 21:35:17.437863 2 75.21 al_rtt false 2024-12-02 21:35:22.103179 2024-12-02 21:35:18.190174 2 63.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.082784 0.009921 0.000000 100/100 2024-12-02 21:35:22.103179 2024-12-02 21:35:18.190174 A al_loss false 0.082784 0.009921 0.000000 100/100 2024-12-02 21:35:22.097391 2024-12-02 21:35:17.437863 A al_jitter false 0.082784 0.009921 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-12-02 21:35:24.798632 1 28.31 al_loss true 2024-12-02 21:35:24.501251 2024-12-02 21:35:22.097391 3 68.83 al_rtt true 2024-12-02 21:35:25.964855 2024-12-02 21:35:22.103179 3 50.79
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.440300 0.459932 44.000000 100/100 2024-12-02 21:35:25.964855 2024-12-02 21:35:22.103179 A al_loss true 0.440300 0.459932 44.000000 100/100 2024-12-02 21:35:24.501251 2024-12-02 21:35:22.097391 A al_jitter true 0.440300 0.459932 44.000000 100/100 2024-12-02 21:35:24.798632
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-12-02 21:35:33.265738 2024-12-02 21:35:24.798632 2 46.54 al_loss false 2024-12-02 21:35:33.641654 2024-12-02 21:35:24.501251 4 75.88 al_rtt false 2024-12-02 21:35:32.868183 2024-12-02 21:35:25.964855 4 59.49
Step 10: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000504 0.000205 0.000000 100/100 2024-12-02 21:35:32.868183 2024-12-02 21:35:25.964855 A al_loss false 0.000504 0.000205 0.000000 100/100 2024-12-02 21:35:33.641654 2024-12-02 21:35:24.501251 A al_jitter false 0.000504 0.000205 0.000000 100/100 2024-12-02 21:35:33.265738 2024-12-02 21:35:24.798632
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-12-02 21:35:33.265738 2024-12-02 21:35:24.798632 2 34.88 al_loss false 2024-12-02 21:35:33.641654 2024-12-02 21:35:24.501251 4 56.87 al_rtt true 2024-12-02 21:35:37.118008 2024-12-02 21:35:32.868183 5 57.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.801518 0.009124 0.000000 100/100 2024-12-02 21:35:37.118008 2024-12-02 21:35:32.868183 A al_loss false 0.801518 0.009124 0.000000 100/100 2024-12-02 21:35:33.641654 2024-12-02 21:35:24.501251 A al_jitter false 0.801518 0.009124 0.000000 100/100 2024-12-02 21:35:33.265738 2024-12-02 21:35:24.798632
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-12-02 21:35:33.265738 2024-12-02 21:35:24.798632 2 27.99 al_loss false 2024-12-02 21:35:45.912346 2024-12-02 21:35:41.401385 6 60.54 al_rtt false 2024-12-02 21:35:45.414880 2024-12-02 21:35:37.118008 6 63.20
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.000513 0.000213 0.000000 100/100 2024-12-02 21:35:45.414880 2024-12-02 21:35:37.118008 A al_loss false 0.000513 0.000213 0.000000 100/100 2024-12-02 21:35:45.912346 2024-12-02 21:35:41.401385 A al_jitter false 0.000513 0.000213 0.000000 100/100 2024-12-02 21:35:33.265738 2024-12-02 21:35:24.798632
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-12-02 21:35:50.876514 2024-12-02 21:35:33.265738 3 27.64 al_loss false 2024-12-02 21:35:45.912346 2024-12-02 21:35:41.401385 6 50.22 al_rtt false 2024-12-02 21:35:45.414880 2024-12-02 21:35:37.118008 6 52.43
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.151784 0.205536 0.000000 100/100 2024-12-02 21:35:45.414880 2024-12-02 21:35:37.118008 A al_loss false 0.151784 0.205536 0.000000 100/100 2024-12-02 21:35:45.912346 2024-12-02 21:35:41.401385 A al_jitter true 0.151784 0.205536 0.000000 100/100 2024-12-02 21:35:50.876514 2024-12-02 21:35:33.265738
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-12-02 21:35:57.335705 2024-12-02 21:35:50.876514 4 35.12 al_loss false 2024-12-02 21:35:45.912346 2024-12-02 21:35:41.401385 6 43.10 al_rtt false 2024-12-02 21:35:45.414880 2024-12-02 21:35:37.118008 6 44.99
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.000436 0.000070 0.000000 100/100 2024-12-02 21:35:45.414880 2024-12-02 21:35:37.118008 A al_loss false 0.000436 0.000070 0.000000 100/100 2024-12-02 21:35:45.912346 2024-12-02 21:35:41.401385 A al_jitter false 0.000436 0.000070 0.000000 100/100 2024-12-02 21:35:57.335705 2024-12-02 21:35:50.876514
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, UDP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv6 destination address) and the UDP 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 udp port 60000
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 udp 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 60000 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-12-02 21:36:16.039553 2024-12-02 21:36:11.436217 2 75.45 al_rtt false 2024-12-02 21:36:15.546852 2024-12-02 21:36:12.171790 2 55.36
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.000407 0.000293 0.000000 100/100 2024-12-02 21:36:15.546852 2024-12-02 21:36:12.171790 A al_loss false 0.000407 0.000293 0.000000 100/100 2024-12-02 21:36:16.039553 2024-12-02 21:36:11.436217 A al_jitter false 0.000407 0.000293 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-12-02 21:36:18.794315 1 27.57 al_loss true 2024-12-02 21:36:18.784574 2024-12-02 21:36:16.039553 3 65.60 al_rtt true 2024-12-02 21:36:20.801351 2024-12-02 21:36:15.546852 3 38.85
Step 7: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled -------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.340267 0.499826 34.000000 100/100 2024-12-02 21:36:20.801351 2024-12-02 21:36:15.546852 A al_loss true 0.340267 0.499826 34.000000 100/100 2024-12-02 21:36:18.784574 2024-12-02 21:36:16.039553 A al_jitter true 0.340267 0.499826 34.000000 100/100 2024-12-02 21:36:18.794315
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-12-02 21:36:27.560041 2024-12-02 21:36:18.794315 2 48.51 al_loss false 2024-12-02 21:36:27.569540 2024-12-02 21:36:18.784574 4 74.05 al_rtt false 2024-12-02 21:36:26.608040 2024-12-02 21:36:20.801351 4 50.80
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.000400 0.000053 0.000000 100/100 2024-12-02 21:36:26.608040 2024-12-02 21:36:20.801351 A al_loss false 0.000400 0.000053 0.000000 100/100 2024-12-02 21:36:27.569540 2024-12-02 21:36:18.784574 A al_jitter false 0.000400 0.000053 0.000000 100/100 2024-12-02 21:36:27.560041 2024-12-02 21:36:18.794315
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-12-02 21:36:27.560041 2024-12-02 21:36:18.794315 2 36.19 al_loss false 2024-12-02 21:36:27.569540 2024-12-02 21:36:18.784574 4 55.25 al_rtt true 2024-12-02 21:36:31.118182 2024-12-02 21:36:26.608040 5 50.79
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.792535 0.009200 0.000000 100/100 2024-12-02 21:36:31.118182 2024-12-02 21:36:26.608040 A al_loss false 0.792535 0.009200 0.000000 100/100 2024-12-02 21:36:27.569540 2024-12-02 21:36:18.784574 A al_jitter false 0.792535 0.009200 0.000000 100/100 2024-12-02 21:36:27.560041 2024-12-02 21:36:18.794315
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-12-02 21:36:27.560041 2024-12-02 21:36:18.794315 2 29.05 al_loss false 2024-12-02 21:36:39.833377 2024-12-02 21:36:35.329877 6 59.28 al_rtt false 2024-12-02 21:36:39.348451 2024-12-02 21:36:31.118182 6 57.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.000475 0.000181 0.000000 100/100 2024-12-02 21:36:39.348451 2024-12-02 21:36:31.118182 A al_loss false 0.000475 0.000181 0.000000 100/100 2024-12-02 21:36:39.833377 2024-12-02 21:36:35.329877 A al_jitter false 0.000475 0.000181 0.000000 100/100 2024-12-02 21:36:27.560041 2024-12-02 21:36:18.794315
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-12-02 21:36:43.592070 2024-12-02 21:36:27.560041 3 31.54 al_loss false 2024-12-02 21:36:39.833377 2024-12-02 21:36:35.329877 6 49.36 al_rtt true 2024-12-02 21:36:45.210299 2024-12-02 21:36:39.348451 7 50.93
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.244837 0.298379 0.000000 100/100 2024-12-02 21:36:45.210299 2024-12-02 21:36:39.348451 A al_loss false 0.244837 0.298379 0.000000 100/100 2024-12-02 21:36:39.833377 2024-12-02 21:36:35.329877 A al_jitter true 0.244837 0.298379 0.000000 100/100 2024-12-02 21:36:43.592070 2024-12-02 21:36:27.560041
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-12-02 21:36:51.153435 2024-12-02 21:36:43.592070 4 38.64 al_loss false 2024-12-02 21:36:39.833377 2024-12-02 21:36:35.329877 6 42.34 al_rtt false 2024-12-02 21:36:49.451229 2024-12-02 21:36:45.210299 8 51.24
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.000382 0.000046 0.000000 100/100 2024-12-02 21:36:49.451229 2024-12-02 21:36:45.210299 A al_loss false 0.000382 0.000046 0.000000 100/100 2024-12-02 21:36:39.833377 2024-12-02 21:36:35.329877 A al_jitter false 0.000382 0.000046 0.000000 100/100 2024-12-02 21:36:51.153435 2024-12-02 21:36:43.592070
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.