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.000026 0.000005 0.000000 7/100 A al_loss false 0.000026 0.000005 0.000000 7/100 A al_jitter false 0.000026 0.000005 0.000000 7/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-10-09 08:34:00.459564 1 54.71 al_loss true 2024-10-09 08:34:00.257029 1 58.09 al_rtt true 2024-10-09 08:34:01.562732 1 36.56
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.390293 0.419829 39.000000 100/100 2024-10-09 08:34:01.562732 A al_loss true 0.390293 0.419829 39.000000 100/100 2024-10-09 08:34:00.257029 A al_jitter true 0.390293 0.419829 39.000000 100/100 2024-10-09 08:34:00.459564
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:34:08.730332 2024-10-09 08:34:00.459564 2 71.45 al_loss false 2024-10-09 08:34:08.942914 2024-10-09 08:34:00.257029 2 75.05 al_rtt false 2024-10-09 08:34:08.080450 2024-10-09 08:34:01.562732 2 56.38
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.000460 0.000128 0.000000 100/100 2024-10-09 08:34:08.080450 2024-10-09 08:34:01.562732 A al_loss false 0.000460 0.000128 0.000000 100/100 2024-10-09 08:34:08.942914 2024-10-09 08:34:00.257029 A al_jitter false 0.000460 0.000128 0.000000 100/100 2024-10-09 08:34:08.730332 2024-10-09 08:34:00.459564
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:34:08.730332 2024-10-09 08:34:00.459564 2 48.17 al_loss false 2024-10-09 08:34:08.942914 2024-10-09 08:34:00.257029 2 50.59 al_rtt true 2024-10-09 08:34:11.790305 2024-10-09 08:34:08.080450 3 56.08
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.774607 0.009151 0.000000 100/100 2024-10-09 08:34:11.790305 2024-10-09 08:34:08.080450 A al_loss false 0.774607 0.009151 0.000000 100/100 2024-10-09 08:34:08.942914 2024-10-09 08:34:00.257029 A al_jitter false 0.774607 0.009151 0.000000 100/100 2024-10-09 08:34:08.730332 2024-10-09 08:34:00.459564
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:34:08.730332 2024-10-09 08:34:00.459564 2 36.34 al_loss false 2024-10-09 08:34:20.159127 2024-10-09 08:34:15.711503 4 57.71 al_rtt false 2024-10-09 08:34:19.658721 2024-10-09 08:34:11.790305 4 63.25
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.000534 0.000093 0.000000 100/100 2024-10-09 08:34:19.658721 2024-10-09 08:34:11.790305 A al_loss false 0.000534 0.000093 0.000000 100/100 2024-10-09 08:34:20.159127 2024-10-09 08:34:15.711503 A al_jitter false 0.000534 0.000093 0.000000 100/100 2024-10-09 08:34:08.730332 2024-10-09 08:34:00.459564
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:34:23.314713 2024-10-09 08:34:08.730332 3 38.97 al_loss false 2024-10-09 08:34:20.159127 2024-10-09 08:34:15.711503 4 46.27 al_rtt false 2024-10-09 08:34:19.658721 2024-10-09 08:34:11.790305 4 50.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.163046 0.266660 0.000000 100/100 2024-10-09 08:34:19.658721 2024-10-09 08:34:11.790305 A al_loss false 0.163046 0.266660 0.000000 100/100 2024-10-09 08:34:20.159127 2024-10-09 08:34:15.711503 A al_jitter true 0.163046 0.266660 0.000000 100/100 2024-10-09 08:34:23.314713 2024-10-09 08:34:08.730332
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:34:30.544323 2024-10-09 08:34:23.314713 4 45.64 al_loss false 2024-10-09 08:34:20.159127 2024-10-09 08:34:15.711503 4 38.67 al_rtt false 2024-10-09 08:34:19.658721 2024-10-09 08:34:11.790305 4 42.38
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.000622 0.000133 0.000000 100/100 2024-10-09 08:34:19.658721 2024-10-09 08:34:11.790305 A al_loss false 0.000622 0.000133 0.000000 100/100 2024-10-09 08:34:20.159127 2024-10-09 08:34:15.711503 A al_jitter false 0.000622 0.000133 0.000000 100/100 2024-10-09 08:34:30.544323 2024-10-09 08:34:23.314713
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.000027 0.000008 0.000000 6/100 A al_loss false 0.000027 0.000008 0.000000 6/100 A al_jitter false 0.000027 0.000008 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:34:40.792014 1 49.25 al_loss true 2024-10-09 08:34:39.838131 1 65.21 al_rtt true 2024-10-09 08:34:41.089166 1 44.25
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.470281 0.429809 47.000000 98/100 2024-10-09 08:34:41.089166 A al_loss true 0.470281 0.429809 47.000000 98/100 2024-10-09 08:34:39.838131 A al_jitter true 0.470281 0.429809 47.000000 98/100 2024-10-09 08:34:40.792014
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:34:48.363804 2024-10-09 08:34:40.792014 2 65.83 al_loss false 2024-10-09 08:34:48.671696 2024-10-09 08:34:39.838131 2 76.77 al_rtt false 2024-10-09 08:34:47.865117 2024-10-09 08:34:41.089166 2 58.90
Step 10: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000523 0.000129 0.000000 100/100 2024-10-09 08:34:47.865117 2024-10-09 08:34:41.089166 A al_loss false 0.000523 0.000129 0.000000 100/100 2024-10-09 08:34:48.671696 2024-10-09 08:34:39.838131 A al_jitter false 0.000523 0.000129 0.000000 100/100 2024-10-09 08:34:48.363804 2024-10-09 08:34:40.792014
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:34:48.363804 2024-10-09 08:34:40.792014 2 44.27 al_loss false 2024-10-09 08:34:48.671696 2024-10-09 08:34:39.838131 2 51.64 al_rtt true 2024-10-09 08:34:51.777629 2024-10-09 08:34:47.865117 3 57.70
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.774695 0.009146 0.000000 100/100 2024-10-09 08:34:51.777629 2024-10-09 08:34:47.865117 A al_loss false 0.774695 0.009146 0.000000 100/100 2024-10-09 08:34:48.671696 2024-10-09 08:34:39.838131 A al_jitter false 0.774695 0.009146 0.000000 100/100 2024-10-09 08:34:48.363804 2024-10-09 08:34:40.792014
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:34:48.363804 2024-10-09 08:34:40.792014 2 33.40 al_loss false 2024-10-09 08:35:00.159502 2024-10-09 08:34:55.638855 4 58.90 al_rtt false 2024-10-09 08:34:59.644211 2024-10-09 08:34:51.777629 4 64.59
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.000543 0.000150 0.000000 100/100 2024-10-09 08:34:59.644211 2024-10-09 08:34:51.777629 A al_loss false 0.000543 0.000150 0.000000 100/100 2024-10-09 08:35:00.159502 2024-10-09 08:34:55.638855 A al_jitter false 0.000543 0.000150 0.000000 100/100 2024-10-09 08:34:48.363804 2024-10-09 08:34:40.792014
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:35:03.621626 2024-10-09 08:34:48.363804 3 35.49 al_loss false 2024-10-09 08:35:00.159502 2024-10-09 08:34:55.638855 4 47.12 al_rtt false 2024-10-09 08:34:59.644211 2024-10-09 08:34:51.777629 4 51.67
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.174880 0.260747 0.000000 100/100 2024-10-09 08:34:59.644211 2024-10-09 08:34:51.777629 A al_loss false 0.174880 0.260747 0.000000 100/100 2024-10-09 08:35:00.159502 2024-10-09 08:34:55.638855 A al_jitter true 0.174880 0.260747 0.000000 100/100 2024-10-09 08:35:03.621626 2024-10-09 08:34:48.363804
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:35:11.024227 2024-10-09 08:35:03.621626 4 44.11 al_loss false 2024-10-09 08:35:11.381417 2024-10-09 08:35:07.517519 6 50.71 al_rtt false 2024-10-09 08:35:09.217679 2024-10-09 08:35:07.217208 6 49.02
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.000489 0.000141 0.000000 100/100 2024-10-09 08:35:09.217679 2024-10-09 08:35:07.217208 A al_loss false 0.000489 0.000141 0.000000 100/100 2024-10-09 08:35:11.381417 2024-10-09 08:35:07.517519 A al_jitter false 0.000489 0.000141 0.000000 100/100 2024-10-09 08:35:11.024227 2024-10-09 08:35:03.621626
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-10-09 08:35:23.861702 2024-10-09 08:35:18.945729 2 73.75 al_rtt false 2024-10-09 08:35:23.616488 2024-10-09 08:35:19.697825 2 58.81
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.016975 0.004433 0.000000 100/100 2024-10-09 08:35:23.616488 2024-10-09 08:35:19.697825 A al_loss false 0.016975 0.004433 0.000000 100/100 2024-10-09 08:35:23.861702 2024-10-09 08:35:18.945729 A al_jitter false 0.016975 0.004433 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:35:26.565100 1 27.33 al_loss true 2024-10-09 08:35:26.169697 2024-10-09 08:35:23.861702 3 70.61 al_rtt true 2024-10-09 08:35:27.771434 2024-10-09 08:35:23.616488 3 49.44
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.540260 0.369827 54.000000 100/100 2024-10-09 08:35:27.771434 2024-10-09 08:35:23.616488 A al_loss true 0.540260 0.369827 54.000000 100/100 2024-10-09 08:35:26.169697 2024-10-09 08:35:23.861702 A al_jitter true 0.540260 0.369827 54.000000 100/100 2024-10-09 08:35:26.565100
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:35:32.294882 2024-10-09 08:35:26.565100 2 30.30 al_loss false 2024-10-09 08:35:35.997561 2024-10-09 08:35:26.169697 4 77.97 al_rtt false 2024-10-09 08:35:35.501936 2024-10-09 08:35:27.771434 4 61.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.000675 0.000141 0.000000 100/100 2024-10-09 08:35:35.501936 2024-10-09 08:35:27.771434 A al_loss false 0.000675 0.000141 0.000000 100/100 2024-10-09 08:35:35.997561 2024-10-09 08:35:26.169697 A al_jitter false 0.000675 0.000141 0.000000 100/100 2024-10-09 08:35:32.294882 2024-10-09 08:35:26.565100
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:35:32.294882 2024-10-09 08:35:26.565100 2 23.40 al_loss false 2024-10-09 08:35:35.997561 2024-10-09 08:35:26.169697 4 60.22 al_rtt true 2024-10-09 08:35:39.054423 2024-10-09 08:35:35.501936 5 60.15
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.765574 0.009140 0.000000 100/100 2024-10-09 08:35:39.054423 2024-10-09 08:35:35.501936 A al_loss false 0.765574 0.009140 0.000000 100/100 2024-10-09 08:35:35.997561 2024-10-09 08:35:26.169697 A al_jitter false 0.765574 0.009140 0.000000 100/100 2024-10-09 08:35:32.294882 2024-10-09 08:35:26.565100
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:35:32.294882 2024-10-09 08:35:26.565100 2 19.08 al_loss false 2024-10-09 08:35:47.382030 2024-10-09 08:35:42.862332 6 64.14 al_rtt false 2024-10-09 08:35:46.876651 2024-10-09 08:35:39.054423 6 64.84
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.000487 0.000115 0.000000 100/100 2024-10-09 08:35:46.876651 2024-10-09 08:35:39.054423 A al_loss false 0.000487 0.000115 0.000000 100/100 2024-10-09 08:35:47.382030 2024-10-09 08:35:42.862332 A al_jitter false 0.000487 0.000115 0.000000 100/100 2024-10-09 08:35:32.294882 2024-10-09 08:35:26.565100
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:35:51.043164 2024-10-09 08:35:32.294882 3 22.36 al_loss false 2024-10-09 08:35:47.382030 2024-10-09 08:35:42.862332 6 54.06 al_rtt false 2024-10-09 08:35:46.876651 2024-10-09 08:35:39.054423 6 54.65
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.187597 0.258541 0.000000 100/100 2024-10-09 08:35:46.876651 2024-10-09 08:35:39.054423 A al_loss false 0.187597 0.258541 0.000000 100/100 2024-10-09 08:35:47.382030 2024-10-09 08:35:42.862332 A al_jitter true 0.187597 0.258541 0.000000 100/100 2024-10-09 08:35:51.043164 2024-10-09 08:35:32.294882
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:35:57.250231 2024-10-09 08:35:51.043164 4 29.00 al_loss false 2024-10-09 08:35:47.382030 2024-10-09 08:35:42.862332 6 46.81 al_rtt false 2024-10-09 08:35:46.876651 2024-10-09 08:35:39.054423 6 47.31
Step 22: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000460 0.000119 0.000000 100/100 2024-10-09 08:35:46.876651 2024-10-09 08:35:39.054423 A al_loss false 0.000460 0.000119 0.000000 100/100 2024-10-09 08:35:47.382030 2024-10-09 08:35:42.862332 A al_jitter false 0.000460 0.000119 0.000000 100/100 2024-10-09 08:35:57.250231 2024-10-09 08:35:51.043164
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-10-09 08:36:10.971444 2024-10-09 08:36:06.248894 2 70.42 al_rtt false 2024-10-09 08:36:10.911984 2024-10-09 08:36:07.000166 2 58.35
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.012672 0.003873 0.000000 100/100 2024-10-09 08:36:10.911984 2024-10-09 08:36:07.000166 A al_loss false 0.012672 0.003873 0.000000 100/100 2024-10-09 08:36:10.971444 2024-10-09 08:36:06.248894 A al_jitter false 0.012672 0.003873 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:36:14.065674 1 26.41 al_loss true 2024-10-09 08:36:13.667666 2024-10-09 08:36:10.971444 3 67.65 al_rtt true 2024-10-09 08:36:15.268885 2024-10-09 08:36:10.911984 3 48.23
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.410298 0.429847 41.000000 100/100 2024-10-09 08:36:15.268885 2024-10-09 08:36:10.911984 A al_loss true 0.410298 0.429847 41.000000 100/100 2024-10-09 08:36:13.667666 2024-10-09 08:36:10.971444 A al_jitter true 0.410298 0.429847 41.000000 100/100 2024-10-09 08:36:14.065674
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:36:21.938299 2024-10-09 08:36:14.065674 2 43.92 al_loss false 2024-10-09 08:36:22.590612 2024-10-09 08:36:13.667666 4 76.12 al_rtt false 2024-10-09 08:36:21.643839 2024-10-09 08:36:15.268885 4 57.39
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.000496 0.000122 0.000000 100/100 2024-10-09 08:36:21.643839 2024-10-09 08:36:15.268885 A al_loss false 0.000496 0.000122 0.000000 100/100 2024-10-09 08:36:22.590612 2024-10-09 08:36:13.667666 A al_jitter false 0.000496 0.000122 0.000000 100/100 2024-10-09 08:36:21.938299 2024-10-09 08:36:14.065674
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:36:21.938299 2024-10-09 08:36:14.065674 2 33.51 al_loss false 2024-10-09 08:36:22.590612 2024-10-09 08:36:13.667666 4 58.07 al_rtt true 2024-10-09 08:36:25.344086 2024-10-09 08:36:21.643839 5 56.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.765465 0.009143 0.000000 100/100 2024-10-09 08:36:25.344086 2024-10-09 08:36:21.643839 A al_loss false 0.765465 0.009143 0.000000 100/100 2024-10-09 08:36:22.590612 2024-10-09 08:36:13.667666 A al_jitter false 0.765465 0.009143 0.000000 100/100 2024-10-09 08:36:21.938299 2024-10-09 08:36:14.065674
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:36:21.938299 2024-10-09 08:36:14.065674 2 27.11 al_loss false 2024-10-09 08:36:33.664992 2024-10-09 08:36:29.152411 6 62.53 al_rtt false 2024-10-09 08:36:33.163589 2024-10-09 08:36:25.344086 6 62.36
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.000523 0.000124 0.000000 100/100 2024-10-09 08:36:33.163589 2024-10-09 08:36:25.344086 A al_loss false 0.000523 0.000124 0.000000 100/100 2024-10-09 08:36:33.664992 2024-10-09 08:36:29.152411 A al_jitter false 0.000523 0.000124 0.000000 100/100 2024-10-09 08:36:21.938299 2024-10-09 08:36:14.065674
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:36:36.529843 2024-10-09 08:36:21.938299 3 31.49 al_loss false 2024-10-09 08:36:33.664992 2024-10-09 08:36:29.152411 6 52.43 al_rtt false 2024-10-09 08:36:33.163589 2024-10-09 08:36:25.344086 6 52.28
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.184116 0.296617 0.000000 100/100 2024-10-09 08:36:33.163589 2024-10-09 08:36:25.344086 A al_loss false 0.184116 0.296617 0.000000 100/100 2024-10-09 08:36:33.664992 2024-10-09 08:36:29.152411 A al_jitter true 0.184116 0.296617 0.000000 100/100 2024-10-09 08:36:36.529843 2024-10-09 08:36:21.938299
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:36:44.095878 2024-10-09 08:36:36.529843 4 38.41 al_loss false 2024-10-09 08:36:33.664992 2024-10-09 08:36:29.152411 6 45.17 al_rtt false 2024-10-09 08:36:33.163589 2024-10-09 08:36:25.344086 6 45.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.000528 0.000144 0.000000 100/100 2024-10-09 08:36:33.163589 2024-10-09 08:36:25.344086 A al_loss false 0.000528 0.000144 0.000000 100/100 2024-10-09 08:36:33.664992 2024-10-09 08:36:29.152411 A al_jitter false 0.000528 0.000144 0.000000 100/100 2024-10-09 08:36:44.095878 2024-10-09 08:36:36.529843
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.