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.000101 0.000082 0.000000 9/100 A al_loss false 0.000101 0.000082 0.000000 9/100 A al_jitter false 0.000101 0.000082 0.000000 9/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0
:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-04-09 09:35:18.763100 1 49.50 al_loss true 2024-04-09 09:35:18.113327 1 59.42 al_rtt true 2024-04-09 09:35:19.558622 1 37.45
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.390229 0.409862 39.000000 100/100 2024-04-09 09:35:19.558622 A al_loss true 0.390229 0.409862 39.000000 100/100 2024-04-09 09:35:18.113327 A al_jitter true 0.390229 0.409862 39.000000 100/100 2024-04-09 09:35:18.763100
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-04-09 09:35:26.750074 2024-04-09 09:35:18.763100 2 64.23 al_loss false 2024-04-09 09:35:27.219947 2024-04-09 09:35:18.113327 2 73.26 al_rtt false 2024-04-09 09:35:26.237798 2024-04-09 09:35:19.558622 2 53.75
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.000452 0.000146 0.000000 100/100 2024-04-09 09:35:26.237798 2024-04-09 09:35:19.558622 A al_loss false 0.000452 0.000146 0.000000 100/100 2024-04-09 09:35:27.219947 2024-04-09 09:35:18.113327 A al_jitter false 0.000452 0.000146 0.000000 100/100 2024-04-09 09:35:26.750074 2024-04-09 09:35:18.763100
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-04-09 09:35:26.750074 2024-04-09 09:35:18.763100 2 42.96 al_loss false 2024-04-09 09:35:27.219947 2024-04-09 09:35:18.113327 2 49.00 al_rtt true 2024-04-09 09:35:30.879863 2024-04-09 09:35:26.237798 3 52.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.792551 0.009290 0.000000 100/100 2024-04-09 09:35:30.879863 2024-04-09 09:35:26.237798 A al_loss false 0.792551 0.009290 0.000000 100/100 2024-04-09 09:35:27.219947 2024-04-09 09:35:18.113327 A al_jitter false 0.792551 0.009290 0.000000 100/100 2024-04-09 09:35:26.750074 2024-04-09 09:35:18.763100
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-04-09 09:35:26.750074 2024-04-09 09:35:18.763100 2 32.60 al_loss false 2024-04-09 09:35:39.605394 2024-04-09 09:35:35.093262 4 55.60 al_rtt false 2024-04-09 09:35:39.097748 2024-04-09 09:35:30.879863 4 60.83
Step 16: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000418 0.000067 0.000000 100/100 2024-04-09 09:35:39.097748 2024-04-09 09:35:30.879863 A al_loss false 0.000418 0.000067 0.000000 100/100 2024-04-09 09:35:39.605394 2024-04-09 09:35:35.093262 A al_jitter false 0.000418 0.000067 0.000000 100/100 2024-04-09 09:35:26.750074 2024-04-09 09:35:18.763100
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-04-09 09:35:42.563274 2024-04-09 09:35:26.750074 3 37.15 al_loss false 2024-04-09 09:35:39.605394 2024-04-09 09:35:35.093262 4 44.74 al_rtt false 2024-04-09 09:35:39.097748 2024-04-09 09:35:30.879863 4 48.95
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.178596 0.300259 0.000000 100/100 2024-04-09 09:35:39.097748 2024-04-09 09:35:30.879863 A al_loss false 0.178596 0.300259 0.000000 100/100 2024-04-09 09:35:39.605394 2024-04-09 09:35:35.093262 A al_jitter true 0.178596 0.300259 0.000000 100/100 2024-04-09 09:35:42.563274 2024-04-09 09:35:26.750074
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-04-09 09:35:50.886876 2024-04-09 09:35:42.563274 4 44.97 al_loss false 2024-04-09 09:35:51.289050 2024-04-09 09:35:47.427313 6 48.20 al_rtt false 2024-04-09 09:35:48.984736 2024-04-09 09:35:46.409486 6 48.18
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.000449 0.000157 0.000000 100/100 2024-04-09 09:35:48.984736 2024-04-09 09:35:46.409486 A al_loss false 0.000449 0.000157 0.000000 100/100 2024-04-09 09:35:51.289050 2024-04-09 09:35:47.427313 A al_jitter false 0.000449 0.000157 0.000000 100/100 2024-04-09 09:35:50.886876 2024-04-09 09:35:42.563274
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.000041 0.000011 0.000000 10/100 A al_loss false 0.000041 0.000011 0.000000 10/100 A al_jitter false 0.000041 0.000011 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-04-09 09:36:06.369528 1 45.86 al_loss true 2024-04-09 09:36:05.725946 1 55.66 al_rtt true 2024-04-09 09:36:06.810906 1 39.06
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.440224 0.479824 44.000000 100/100 2024-04-09 09:36:06.810906 A al_loss true 0.440224 0.479824 44.000000 100/100 2024-04-09 09:36:05.725946 A al_jitter true 0.440224 0.479824 44.000000 100/100 2024-04-09 09:36:06.369528
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-04-09 09:36:14.638919 2024-04-09 09:36:06.369528 2 66.52 al_loss false 2024-04-09 09:36:14.687202 2024-04-09 09:36:05.725946 2 72.03 al_rtt false 2024-04-09 09:36:13.688420 2024-04-09 09:36:06.810906 2 55.31
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.000426 0.000094 0.000000 100/100 2024-04-09 09:36:13.688420 2024-04-09 09:36:06.810906 A al_loss false 0.000426 0.000094 0.000000 100/100 2024-04-09 09:36:14.687202 2024-04-09 09:36:05.725946 A al_jitter false 0.000426 0.000094 0.000000 100/100 2024-04-09 09:36:14.638919 2024-04-09 09:36:06.369528
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-04-09 09:36:14.638919 2024-04-09 09:36:06.369528 2 44.51 al_loss false 2024-04-09 09:36:14.687202 2024-04-09 09:36:05.725946 2 48.21 al_rtt true 2024-04-09 09:36:18.246055 2024-04-09 09:36:13.688420 3 54.09
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.801469 0.009122 0.000000 100/100 2024-04-09 09:36:18.246055 2024-04-09 09:36:13.688420 A al_loss false 0.801469 0.009122 0.000000 100/100 2024-04-09 09:36:14.687202 2024-04-09 09:36:05.725946 A al_jitter false 0.801469 0.009122 0.000000 100/100 2024-04-09 09:36:14.638919 2024-04-09 09:36:06.369528
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-04-09 09:36:14.638919 2024-04-09 09:36:06.369528 2 33.64 al_loss false 2024-04-09 09:36:27.006814 2024-04-09 09:36:22.503755 4 54.75 al_rtt false 2024-04-09 09:36:26.524858 2024-04-09 09:36:18.246055 4 61.64
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.000374 0.000056 0.000000 100/100 2024-04-09 09:36:26.524858 2024-04-09 09:36:18.246055 A al_loss false 0.000374 0.000056 0.000000 100/100 2024-04-09 09:36:27.006814 2024-04-09 09:36:22.503755 A al_jitter false 0.000374 0.000056 0.000000 100/100 2024-04-09 09:36:14.638919 2024-04-09 09:36:06.369528
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-04-09 09:36:30.471489 2024-04-09 09:36:14.638919 3 37.05 al_loss false 2024-04-09 09:36:27.006814 2024-04-09 09:36:22.503755 4 43.76 al_rtt true 2024-04-09 09:36:32.665952 2024-04-09 09:36:26.524858 5 52.30
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.268044 0.356537 0.000000 100/100 2024-04-09 09:36:32.665952 2024-04-09 09:36:26.524858 A al_loss false 0.268044 0.356537 0.000000 100/100 2024-04-09 09:36:27.006814 2024-04-09 09:36:22.503755 A al_jitter true 0.268044 0.356537 0.000000 100/100 2024-04-09 09:36:30.471489 2024-04-09 09:36:14.638919
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-04-09 09:36:38.496891 2024-04-09 09:36:30.471489 4 44.34 al_loss false 2024-04-09 09:36:38.960122 2024-04-09 09:36:35.099527 6 47.13 al_rtt false 2024-04-09 09:36:36.948443 2024-04-09 09:36:32.665952 6 52.89
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.000383 0.000052 0.000000 100/100 2024-04-09 09:36:36.948443 2024-04-09 09:36:32.665952 A al_loss false 0.000383 0.000052 0.000000 100/100 2024-04-09 09:36:38.960122 2024-04-09 09:36:35.099527 A al_jitter false 0.000383 0.000052 0.000000 100/100 2024-04-09 09:36:38.496891 2024-04-09 09:36:30.471489
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-04-09 09:36:57.012319 2024-04-09 09:36:52.113967 2 68.41 al_rtt false 2024-04-09 09:36:56.785169 2024-04-09 09:36:52.846577 2 55.03
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.000396 0.000069 0.000000 100/100 2024-04-09 09:36:56.785169 2024-04-09 09:36:52.846577 A al_loss false 0.000396 0.000069 0.000000 100/100 2024-04-09 09:36:57.012319 2024-04-09 09:36:52.113967 A al_jitter false 0.000396 0.000069 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-04-09 09:37:00.663813 1 25.27 al_loss true 2024-04-09 09:37:00.179332 2024-04-09 09:36:57.012319 3 65.91 al_rtt true 2024-04-09 09:37:02.118793 2024-04-09 09:36:56.785169 3 44.04
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.450244 0.439784 45.000000 100/100 2024-04-09 09:37:02.118793 2024-04-09 09:36:56.785169 A al_loss true 0.450244 0.439784 45.000000 100/100 2024-04-09 09:37:00.179332 2024-04-09 09:36:57.012319 A al_jitter true 0.450244 0.439784 45.000000 100/100 2024-04-09 09:37:00.663813
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-04-09 09:37:09.031048 2024-04-09 09:37:00.663813 2 43.30 al_loss false 2024-04-09 09:37:09.531657 2024-04-09 09:37:00.179332 4 73.77 al_rtt false 2024-04-09 09:37:08.735284 2024-04-09 09:37:02.118793 4 54.65
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.000390 0.000059 0.000000 100/100 2024-04-09 09:37:08.735284 2024-04-09 09:37:02.118793 A al_loss false 0.000390 0.000059 0.000000 100/100 2024-04-09 09:37:09.531657 2024-04-09 09:37:00.179332 A al_jitter false 0.000390 0.000059 0.000000 100/100 2024-04-09 09:37:09.031048 2024-04-09 09:37:00.663813
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-04-09 09:37:09.031048 2024-04-09 09:37:00.663813 2 32.88 al_loss false 2024-04-09 09:37:09.531657 2024-04-09 09:37:00.179332 4 56.02 al_rtt true 2024-04-09 09:37:13.006838 2024-04-09 09:37:08.735284 5 54.07
Step 13: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.819435 0.009150 0.000000 100/100 2024-04-09 09:37:13.006838 2024-04-09 09:37:08.735284 A al_loss false 0.819435 0.009150 0.000000 100/100 2024-04-09 09:37:09.531657 2024-04-09 09:37:00.179332 A al_jitter false 0.819435 0.009150 0.000000 100/100 2024-04-09 09:37:09.031048 2024-04-09 09:37:00.663813
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-04-09 09:37:09.031048 2024-04-09 09:37:00.663813 2 26.50 al_loss false 2024-04-09 09:37:21.965057 2024-04-09 09:37:17.447785 6 59.46 al_rtt false 2024-04-09 09:37:21.464877 2024-04-09 09:37:13.006838 6 60.24
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.000400 0.000061 0.000000 100/100 2024-04-09 09:37:21.464877 2024-04-09 09:37:13.006838 A al_loss false 0.000400 0.000061 0.000000 100/100 2024-04-09 09:37:21.965057 2024-04-09 09:37:17.447785 A al_jitter false 0.000400 0.000061 0.000000 100/100 2024-04-09 09:37:09.031048 2024-04-09 09:37:00.663813
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-04-09 09:37:24.970287 2024-04-09 09:37:09.031048 3 31.36 al_loss false 2024-04-09 09:37:21.965057 2024-04-09 09:37:17.447785 6 49.85 al_rtt true 2024-04-09 09:37:28.075699 2024-04-09 09:37:21.464877 7 51.40
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.202382 0.261276 0.000000 100/100 2024-04-09 09:37:28.075699 2024-04-09 09:37:21.464877 A al_loss false 0.202382 0.261276 0.000000 100/100 2024-04-09 09:37:21.965057 2024-04-09 09:37:17.447785 A al_jitter true 0.202382 0.261276 0.000000 100/100 2024-04-09 09:37:24.970287 2024-04-09 09:37:09.031048
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-04-09 09:37:33.289992 2024-04-09 09:37:24.970287 4 38.31 al_loss false 2024-04-09 09:37:21.965057 2024-04-09 09:37:17.447785 6 43.10 al_rtt false 2024-04-09 09:37:30.731682 2024-04-09 09:37:28.075699 8 49.76
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.000383 0.000060 0.000000 100/100 2024-04-09 09:37:30.731682 2024-04-09 09:37:28.075699 A al_loss false 0.000383 0.000060 0.000000 100/100 2024-04-09 09:37:21.965057 2024-04-09 09:37:17.447785 A al_jitter false 0.000383 0.000060 0.000000 100/100 2024-04-09 09:37:33.289992 2024-04-09 09:37:24.970287
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-04-09 09:37:50.631529 2024-04-09 09:37:46.062810 2 76.65 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.001170 0.010059 0.000000 100/100 A al_loss false 0.001170 0.010059 0.000000 100/100 2024-04-09 09:37:50.631529 2024-04-09 09:37:46.062810 A al_jitter false 0.001170 0.010059 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-04-09 09:37:53.368435 1 27.23 al_loss true 2024-04-09 09:37:52.926325 2024-04-09 09:37:50.631529 3 69.23 al_rtt true 2024-04-09 09:37:54.573863 1 17.11
Step 7: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled -------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.430232 0.419876 43.000000 100/100 2024-04-09 09:37:54.573863 A al_loss true 0.430232 0.419876 43.000000 100/100 2024-04-09 09:37:52.926325 2024-04-09 09:37:50.631529 A al_jitter true 0.430232 0.419876 43.000000 100/100 2024-04-09 09:37:53.368435
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-04-09 09:38:01.634473 2024-04-09 09:37:53.368435 2 46.52 al_loss false 2024-04-09 09:38:02.040461 2024-04-09 09:37:52.926325 4 76.97 al_rtt false 2024-04-09 09:38:01.036224 2024-04-09 09:37:54.573863 2 36.36
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.000417 0.000061 0.000000 100/100 2024-04-09 09:38:01.036224 2024-04-09 09:37:54.573863 A al_loss false 0.000417 0.000061 0.000000 100/100 2024-04-09 09:38:02.040461 2024-04-09 09:37:52.926325 A al_jitter false 0.000417 0.000061 0.000000 100/100 2024-04-09 09:38:01.634473 2024-04-09 09:37:53.368435
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-04-09 09:38:01.634473 2024-04-09 09:37:53.368435 2 34.67 al_loss false 2024-04-09 09:38:02.040461 2024-04-09 09:37:52.926325 4 57.37 al_rtt true 2024-04-09 09:38:05.341386 2024-04-09 09:38:01.036224 3 40.51
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.828443 0.009072 0.000000 100/100 2024-04-09 09:38:05.341386 2024-04-09 09:38:01.036224 A al_loss false 0.828443 0.009072 0.000000 100/100 2024-04-09 09:38:02.040461 2024-04-09 09:37:52.926325 A al_jitter false 0.828443 0.009072 0.000000 100/100 2024-04-09 09:38:01.634473 2024-04-09 09:37:53.368435
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-04-09 09:38:01.634473 2024-04-09 09:37:53.368435 2 27.47 al_loss false 2024-04-09 09:38:14.417402 2024-04-09 09:38:09.897216 6 60.47 al_rtt false 2024-04-09 09:38:13.922966 2024-04-09 09:38:05.341386 4 49.99
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.000392 0.000056 0.000000 100/100 2024-04-09 09:38:13.922966 2024-04-09 09:38:05.341386 A al_loss false 0.000392 0.000056 0.000000 100/100 2024-04-09 09:38:14.417402 2024-04-09 09:38:09.897216 A al_jitter false 0.000392 0.000056 0.000000 100/100 2024-04-09 09:38:01.634473 2024-04-09 09:37:53.368435
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-04-09 09:38:18.063948 2024-04-09 09:38:01.634473 3 30.90 al_loss false 2024-04-09 09:38:14.417402 2024-04-09 09:38:09.897216 6 50.10 al_rtt true 2024-04-09 09:38:20.306187 2024-04-09 09:38:13.922966 5 43.38
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.265712 0.296133 0.000000 100/100 2024-04-09 09:38:20.306187 2024-04-09 09:38:13.922966 A al_loss false 0.265712 0.296133 0.000000 100/100 2024-04-09 09:38:14.417402 2024-04-09 09:38:09.897216 A al_jitter true 0.265712 0.296133 0.000000 100/100 2024-04-09 09:38:18.063948 2024-04-09 09:38:01.634473
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-04-09 09:38:26.141543 2024-04-09 09:38:18.063948 4 38.69 al_loss false 2024-04-09 09:38:26.389149 2024-04-09 09:38:22.421165 8 52.47 al_rtt false 2024-04-09 09:38:24.987819 2024-04-09 09:38:20.306187 6 46.69
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.000386 0.000105 0.000000 100/100 2024-04-09 09:38:24.987819 2024-04-09 09:38:20.306187 A al_loss false 0.000386 0.000105 0.000000 100/100 2024-04-09 09:38:26.389149 2024-04-09 09:38:22.421165 A al_jitter false 0.000386 0.000105 0.000000 100/100 2024-04-09 09:38:26.141543 2024-04-09 09:38:18.063948
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.