Check Icmp Operation
This scenario shows how to configure Network Service Monitor (NSM) operations to measure network quality using active traffic probes and the ICMP protocol.
Test IPv4 Destination
Description
In this scenario, ICMP NSM operations are configured in DUT0 (using an IPv4 destination address).
Scenario
Step 1: Set the following configuration in DUT1:
set interfaces ethernet eth0 address 10.215.200.100/24
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 icmp 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
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.000060 0.000034 0.000000 12/100 A al_loss false 0.000060 0.000034 0.000000 12/100 A al_jitter false 0.000060 0.000034 0.000000 12/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-02-13 15:58:31.684782 1 50.46 al_loss true 2024-02-13 15:58:31.182193 1 58.18 al_rtt true 2024-02-13 15:58:32.982943 1 30.83
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.480208 0.399872 48.000000 100/100 2024-02-13 15:58:32.982943 A al_loss true 0.480208 0.399872 48.000000 100/100 2024-02-13 15:58:31.182193 A al_jitter true 0.480208 0.399872 48.000000 100/100 2024-02-13 15:58:31.684782
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 15:58:40.416339 2024-02-13 15:58:31.684782 2 69.50 al_loss false 2024-02-13 15:58:40.474005 2024-02-13 15:58:31.182193 2 74.03 al_rtt false 2024-02-13 15:58:39.653995 2024-02-13 15:58:32.982943 2 53.13
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.000375 0.000046 0.000000 100/100 2024-02-13 15:58:39.653995 2024-02-13 15:58:32.982943 A al_loss false 0.000375 0.000046 0.000000 100/100 2024-02-13 15:58:40.474005 2024-02-13 15:58:31.182193 A al_jitter false 0.000375 0.000046 0.000000 100/100 2024-02-13 15:58:40.416339 2024-02-13 15:58:31.684782
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 15:58:40.416339 2024-02-13 15:58:31.684782 2 47.01 al_loss false 2024-02-13 15:58:40.474005 2024-02-13 15:58:31.182193 2 50.06 al_rtt true 2024-02-13 15:58:43.861610 2024-02-13 15:58:39.653995 3 52.77
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.792408 0.009068 0.000000 100/100 2024-02-13 15:58:43.861610 2024-02-13 15:58:39.653995 A al_loss false 0.792408 0.009068 0.000000 100/100 2024-02-13 15:58:40.474005 2024-02-13 15:58:31.182193 A al_jitter false 0.792408 0.009068 0.000000 100/100 2024-02-13 15:58:40.416339 2024-02-13 15:58:31.684782
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 15:58:40.416339 2024-02-13 15:58:31.684782 2 35.76 al_loss false 2024-02-13 15:58:52.483555 2024-02-13 15:58:47.974494 4 56.55 al_rtt false 2024-02-13 15:58:51.983010 2024-02-13 15:58:43.861610 4 60.60
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.000379 0.000049 0.000000 100/100 2024-02-13 15:58:51.983010 2024-02-13 15:58:43.861610 A al_loss false 0.000379 0.000049 0.000000 100/100 2024-02-13 15:58:52.483555 2024-02-13 15:58:47.974494 A al_jitter false 0.000379 0.000049 0.000000 100/100 2024-02-13 15:58:40.416339 2024-02-13 15:58:31.684782
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-13 15:58:56.227832 2024-02-13 15:58:40.416339 3 37.33 al_loss false 2024-02-13 15:58:52.483555 2024-02-13 15:58:47.974494 4 45.34 al_rtt false 2024-02-13 15:58:51.983010 2024-02-13 15:58:43.861610 4 48.59
Step 19: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.136505 0.246720 0.000000 100/100 2024-02-13 15:58:51.983010 2024-02-13 15:58:43.861610 A al_loss false 0.136505 0.246720 0.000000 100/100 2024-02-13 15:58:52.483555 2024-02-13 15:58:47.974494 A al_jitter true 0.136505 0.246720 0.000000 100/100 2024-02-13 15:58:56.227832 2024-02-13 15:58:40.416339
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 15:59:02.822642 2024-02-13 15:58:56.227832 4 42.06 al_loss false 2024-02-13 15:58:52.483555 2024-02-13 15:58:47.974494 4 37.88 al_rtt false 2024-02-13 15:58:51.983010 2024-02-13 15:58:43.861610 4 40.60
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.000384 0.000056 0.000000 100/100 2024-02-13 15:58:51.983010 2024-02-13 15:58:43.861610 A al_loss false 0.000384 0.000056 0.000000 100/100 2024-02-13 15:58:52.483555 2024-02-13 15:58:47.974494 A al_jitter false 0.000384 0.000056 0.000000 100/100 2024-02-13 15:59:02.822642 2024-02-13 15:58:56.227832
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, ICMP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv4 destination address).
Scenario
Step 1: Set the following configuration in DUT1:
set interfaces ethernet eth0 address 10.215.200.100/24
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 icmp 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 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.000065 0.000063 0.000000 10/100 A al_loss false 0.000065 0.000063 0.000000 10/100 A al_jitter false 0.000065 0.000063 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-02-13 15:59:19.211422 1 52.11 al_loss true 2024-02-13 15:59:19.206123 1 52.22 al_rtt true 2024-02-13 15:59:20.527738 1 32.21
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.420227 0.409874 42.000000 100/100 2024-02-13 15:59:20.527738 A al_loss true 0.420227 0.409874 42.000000 100/100 2024-02-13 15:59:19.206123 A al_jitter true 0.420227 0.409874 42.000000 100/100 2024-02-13 15:59:19.211422
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 15:59:27.746319 2024-02-13 15:59:19.211422 2 68.01 al_loss false 2024-02-13 15:59:27.697347 2024-02-13 15:59:19.206123 2 67.68 al_rtt false 2024-02-13 15:59:26.986651 2024-02-13 15:59:20.527738 2 51.45
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.000382 0.000049 0.000000 100/100 2024-02-13 15:59:26.986651 2024-02-13 15:59:20.527738 A al_loss false 0.000382 0.000049 0.000000 100/100 2024-02-13 15:59:27.697347 2024-02-13 15:59:19.206123 A al_jitter false 0.000382 0.000049 0.000000 100/100 2024-02-13 15:59:27.746319 2024-02-13 15:59:19.211422
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 15:59:27.746319 2024-02-13 15:59:19.211422 2 46.11 al_loss false 2024-02-13 15:59:27.697347 2024-02-13 15:59:19.206123 2 45.88 al_rtt true 2024-02-13 15:59:31.399196 2024-02-13 15:59:26.986651 3 51.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.801433 0.009102 0.000000 100/100 2024-02-13 15:59:31.399196 2024-02-13 15:59:26.986651 A al_loss false 0.801433 0.009102 0.000000 100/100 2024-02-13 15:59:27.697347 2024-02-13 15:59:19.206123 A al_jitter false 0.801433 0.009102 0.000000 100/100 2024-02-13 15:59:27.746319 2024-02-13 15:59:19.211422
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 15:59:27.746319 2024-02-13 15:59:19.211422 2 34.98 al_loss false 2024-02-13 15:59:40.077616 2024-02-13 15:59:35.565241 4 53.30 al_rtt false 2024-02-13 15:59:39.567580 2024-02-13 15:59:31.399196 4 59.94
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.000409 0.000097 0.000000 100/100 2024-02-13 15:59:39.567580 2024-02-13 15:59:31.399196 A al_loss false 0.000409 0.000097 0.000000 100/100 2024-02-13 15:59:40.077616 2024-02-13 15:59:35.565241 A al_jitter false 0.000409 0.000097 0.000000 100/100 2024-02-13 15:59:27.746319 2024-02-13 15:59:19.211422
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-13 15:59:43.630660 2024-02-13 15:59:27.746319 3 37.22 al_loss false 2024-02-13 15:59:40.077616 2024-02-13 15:59:35.565241 4 42.85 al_rtt true 2024-02-13 15:59:45.842188 2024-02-13 15:59:39.567580 5 50.00
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.248378 0.254155 0.000000 100/100 2024-02-13 15:59:45.842188 2024-02-13 15:59:39.567580 A al_loss false 0.248378 0.254155 0.000000 100/100 2024-02-13 15:59:40.077616 2024-02-13 15:59:35.565241 A al_jitter true 0.248378 0.254155 0.000000 100/100 2024-02-13 15:59:43.630660 2024-02-13 15:59:27.746319
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 15:59:51.304658 2024-02-13 15:59:43.630660 4 44.88 al_loss false 2024-02-13 15:59:51.397607 2024-02-13 15:59:47.985211 6 45.46 al_rtt false 2024-02-13 15:59:49.750628 2024-02-13 15:59:45.842188 6 51.32
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.000377 0.000058 0.000000 100/100 2024-02-13 15:59:49.750628 2024-02-13 15:59:45.842188 A al_loss false 0.000377 0.000058 0.000000 100/100 2024-02-13 15:59:51.397607 2024-02-13 15:59:47.985211 A al_jitter false 0.000377 0.000058 0.000000 100/100 2024-02-13 15:59:51.304658 2024-02-13 15:59:43.630660
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, ICMP NSM operations are configured in DUT0 (using an IPv6 destination address).
Scenario
Step 1: Set the following configuration in DUT1:
set interfaces ethernet eth0 address 10::3/64
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 icmp 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
Step 3: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 0 0.00 al_loss false 2024-02-13 16:00:08.419157 2024-02-13 16:00:03.645591 2 65.64 al_rtt false 2024-02-13 16:00:08.389198 2024-02-13 16:00:04.386821 2 55.00
Step 4: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000441 0.000190 0.000000 100/100 2024-02-13 16:00:08.389198 2024-02-13 16:00:04.386821 A al_loss false 0.000441 0.000190 0.000000 100/100 2024-02-13 16:00:08.419157 2024-02-13 16:00:03.645591 A al_jitter false 0.000441 0.000190 0.000000 100/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-13 16:00:12.217063 1 24.99 al_loss true 2024-02-13 16:00:11.957795 2024-02-13 16:00:08.419157 3 62.75 al_rtt true 2024-02-13 16:00:13.811259 2024-02-13 16:00:08.389198 3 43.05
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.400235 0.459846 40.000000 100/100 2024-02-13 16:00:13.811259 2024-02-13 16:00:08.389198 A al_loss true 0.400235 0.459846 40.000000 100/100 2024-02-13 16:00:11.957795 2024-02-13 16:00:08.419157 A al_jitter true 0.400235 0.459846 40.000000 100/100 2024-02-13 16:00:12.217063
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 16:00:20.587688 2024-02-13 16:00:12.217063 2 43.70 al_loss false 2024-02-13 16:00:20.927637 2024-02-13 16:00:11.957795 4 71.78 al_rtt false 2024-02-13 16:00:19.947847 2024-02-13 16:00:13.811259 4 52.95
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.000375 0.000047 0.000000 100/100 2024-02-13 16:00:19.947847 2024-02-13 16:00:13.811259 A al_loss false 0.000375 0.000047 0.000000 100/100 2024-02-13 16:00:20.927637 2024-02-13 16:00:11.957795 A al_jitter false 0.000375 0.000047 0.000000 100/100 2024-02-13 16:00:20.587688 2024-02-13 16:00:12.217063
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 16:00:20.587688 2024-02-13 16:00:12.217063 2 33.19 al_loss false 2024-02-13 16:00:20.927637 2024-02-13 16:00:11.957795 4 54.51 al_rtt true 2024-02-13 16:00:24.294446 2024-02-13 16:00:19.947847 5 52.64
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.792393 0.009082 0.000000 100/100 2024-02-13 16:00:24.294446 2024-02-13 16:00:19.947847 A al_loss false 0.792393 0.009082 0.000000 100/100 2024-02-13 16:00:20.927637 2024-02-13 16:00:11.957795 A al_jitter false 0.792393 0.009082 0.000000 100/100 2024-02-13 16:00:20.587688 2024-02-13 16:00:12.217063
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 16:00:20.587688 2024-02-13 16:00:12.217063 2 26.95 al_loss false 2024-02-13 16:00:32.900244 2024-02-13 16:00:28.448990 6 58.60 al_rtt false 2024-02-13 16:00:32.405263 2024-02-13 16:00:24.294446 6 58.77
Step 16: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000376 0.000056 0.000000 100/100 2024-02-13 16:00:32.405263 2024-02-13 16:00:24.294446 A al_loss false 0.000376 0.000056 0.000000 100/100 2024-02-13 16:00:32.900244 2024-02-13 16:00:28.448990 A al_jitter false 0.000376 0.000056 0.000000 100/100 2024-02-13 16:00:20.587688 2024-02-13 16:00:12.217063
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-13 16:00:36.627045 2024-02-13 16:00:20.587688 3 29.88 al_loss false 2024-02-13 16:00:32.900244 2024-02-13 16:00:28.448990 6 48.99 al_rtt false 2024-02-13 16:00:32.405263 2024-02-13 16:00:24.294446 6 49.13
Step 19: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.168408 0.259807 0.000000 100/100 2024-02-13 16:00:32.405263 2024-02-13 16:00:24.294446 A al_loss false 0.168408 0.259807 0.000000 100/100 2024-02-13 16:00:32.900244 2024-02-13 16:00:28.448990 A al_jitter true 0.168408 0.259807 0.000000 100/100 2024-02-13 16:00:36.627045 2024-02-13 16:00:20.587688
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 16:00:44.191911 2024-02-13 16:00:36.627045 4 37.04 al_loss false 2024-02-13 16:00:44.581144 2024-02-13 16:00:40.927749 8 50.80 al_rtt false 2024-02-13 16:00:42.589578 2024-02-13 16:00:40.413446 8 47.48
Step 22: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000390 0.000085 0.000000 100/100 2024-02-13 16:00:42.589578 2024-02-13 16:00:40.413446 A al_loss false 0.000390 0.000085 0.000000 100/100 2024-02-13 16:00:44.581144 2024-02-13 16:00:40.927749 A al_jitter false 0.000390 0.000085 0.000000 100/100 2024-02-13 16:00:44.191911 2024-02-13 16:00:36.627045
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, ICMP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv6 destination address).
Scenario
Step 1: Set the following configuration in DUT1:
set interfaces ethernet eth0 address 10::3/64
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 icmp 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 dns static host-name testnsm alias test.nsm.fqdn set service dns static host-name testnsm inet 10::3
Step 3: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 0 0.00 al_loss false 2024-02-13 16:01:01.629720 2024-02-13 16:00:57.030657 2 75.59 al_rtt false 2024-02-13 16:01:01.119562 2024-02-13 16:00:57.765440 2 55.02
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.000566 0.010112 0.000000 100/100 2024-02-13 16:01:01.119562 2024-02-13 16:00:57.765440 A al_loss false 0.000566 0.010112 0.000000 100/100 2024-02-13 16:01:01.629720 2024-02-13 16:00:57.030657 A al_jitter false 0.000566 0.010112 0.000000 100/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-13 16:01:04.226852 1 29.16 al_loss true 2024-02-13 16:01:03.978195 2024-02-13 16:01:01.629720 3 68.95 al_rtt true 2024-02-13 16:01:05.431594 2024-02-13 16:01:01.119562 3 46.76
Step 7: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled -------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.490204 0.459854 49.000000 100/100 2024-02-13 16:01:05.431594 2024-02-13 16:01:01.119562 A al_loss true 0.490204 0.459854 49.000000 100/100 2024-02-13 16:01:03.978195 2024-02-13 16:01:01.629720 A al_jitter true 0.490204 0.459854 49.000000 100/100 2024-02-13 16:01:04.226852
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 16:01:12.914477 2024-02-13 16:01:04.226852 2 47.80 al_loss false 2024-02-13 16:01:12.987109 2024-02-13 16:01:03.978195 4 74.90 al_rtt false 2024-02-13 16:01:11.650868 2024-02-13 16:01:05.431594 4 52.66
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.000373 0.000071 0.000000 100/100 2024-02-13 16:01:11.650868 2024-02-13 16:01:05.431594 A al_loss false 0.000373 0.000071 0.000000 100/100 2024-02-13 16:01:12.987109 2024-02-13 16:01:03.978195 A al_jitter false 0.000373 0.000071 0.000000 100/100 2024-02-13 16:01:12.914477 2024-02-13 16:01:04.226852
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 16:01:12.914477 2024-02-13 16:01:04.226852 2 35.91 al_loss false 2024-02-13 16:01:12.987109 2024-02-13 16:01:03.978195 4 56.27 al_rtt true 2024-02-13 16:01:16.609178 2024-02-13 16:01:11.650868 5 52.66
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.801412 0.009088 0.000000 100/100 2024-02-13 16:01:16.609178 2024-02-13 16:01:11.650868 A al_loss false 0.801412 0.009088 0.000000 100/100 2024-02-13 16:01:12.987109 2024-02-13 16:01:03.978195 A al_jitter false 0.801412 0.009088 0.000000 100/100 2024-02-13 16:01:12.914477 2024-02-13 16:01:04.226852
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 16:01:12.914477 2024-02-13 16:01:04.226852 2 28.86 al_loss false 2024-02-13 16:01:25.325709 2024-02-13 16:01:20.823938 6 60.18 al_rtt false 2024-02-13 16:01:24.840947 2024-02-13 16:01:16.609178 6 59.15
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.000369 0.000057 0.000000 100/100 2024-02-13 16:01:24.840947 2024-02-13 16:01:16.609178 A al_loss false 0.000369 0.000057 0.000000 100/100 2024-02-13 16:01:25.325709 2024-02-13 16:01:20.823938 A al_jitter false 0.000369 0.000057 0.000000 100/100 2024-02-13 16:01:12.914477 2024-02-13 16:01:04.226852
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-02-13 16:01:28.697051 2024-02-13 16:01:12.914477 3 32.21 al_loss false 2024-02-13 16:01:25.325709 2024-02-13 16:01:20.823938 6 50.28 al_rtt true 2024-02-13 16:01:30.642888 2024-02-13 16:01:24.840947 7 52.11
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.243424 0.320545 0.000000 100/100 2024-02-13 16:01:30.642888 2024-02-13 16:01:24.840947 A al_loss false 0.243424 0.320545 0.000000 100/100 2024-02-13 16:01:25.325709 2024-02-13 16:01:20.823938 A al_jitter true 0.243424 0.320545 0.000000 100/100 2024-02-13 16:01:28.697051 2024-02-13 16:01:12.914477
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-02-13 16:01:36.899309 2024-02-13 16:01:28.697051 4 40.30 al_loss false 2024-02-13 16:01:37.002699 2024-02-13 16:01:33.151472 8 52.40 al_rtt false 2024-02-13 16:01:34.810641 2024-02-13 16:01:30.642888 8 52.42
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.000401 0.000118 0.000000 100/100 2024-02-13 16:01:34.810641 2024-02-13 16:01:30.642888 A al_loss false 0.000401 0.000118 0.000000 100/100 2024-02-13 16:01:37.002699 2024-02-13 16:01:33.151472 A al_jitter false 0.000401 0.000118 0.000000 100/100 2024-02-13 16:01:36.899309 2024-02-13 16:01:28.697051
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.