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.000033 0.000008 0.000000 8/100 A al_loss false 0.000033 0.000008 0.000000 8/100 A al_jitter false 0.000033 0.000008 0.000000 8/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-06-12 21:24:17.449490 1 46.11 al_loss true 2024-06-12 21:24:16.899054 1 54.94 al_rtt true 2024-06-12 21:24:18.453929 1 30.10
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.400228 0.479829 40.000000 100/100 2024-06-12 21:24:18.453929 A al_loss true 0.400228 0.479829 40.000000 100/100 2024-06-12 21:24:16.899054 A al_jitter true 0.400228 0.479829 40.000000 100/100 2024-06-12 21:24:17.449490
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-06-12 21:24:25.414760 2024-06-12 21:24:17.449490 2 65.90 al_loss false 2024-06-12 21:24:25.372401 2024-06-12 21:24:16.899054 2 70.12 al_rtt false 2024-06-12 21:24:24.472223 2024-06-12 21:24:18.453929 2 49.82
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.000369 0.000050 0.000000 100/100 2024-06-12 21:24:24.472223 2024-06-12 21:24:18.453929 A al_loss false 0.000369 0.000050 0.000000 100/100 2024-06-12 21:24:25.372401 2024-06-12 21:24:16.899054 A al_jitter false 0.000369 0.000050 0.000000 100/100 2024-06-12 21:24:25.414760 2024-06-12 21:24:17.449490
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-06-12 21:24:25.414760 2024-06-12 21:24:17.449490 2 43.97 al_loss false 2024-06-12 21:24:25.372401 2024-06-12 21:24:16.899054 2 46.79 al_rtt true 2024-06-12 21:24:29.018375 2024-06-12 21:24:24.472223 3 50.76
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.792410 0.009067 0.000000 100/100 2024-06-12 21:24:29.018375 2024-06-12 21:24:24.472223 A al_loss false 0.792410 0.009067 0.000000 100/100 2024-06-12 21:24:25.372401 2024-06-12 21:24:16.899054 A al_jitter false 0.792410 0.009067 0.000000 100/100 2024-06-12 21:24:25.414760 2024-06-12 21:24:17.449490
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-06-12 21:24:25.414760 2024-06-12 21:24:17.449490 2 33.39 al_loss false 2024-06-12 21:24:37.584746 2024-06-12 21:24:33.079519 4 54.41 al_rtt false 2024-06-12 21:24:37.086210 2024-06-12 21:24:29.018375 4 59.06
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.000356 0.000046 0.000000 100/100 2024-06-12 21:24:37.086210 2024-06-12 21:24:29.018375 A al_loss false 0.000356 0.000046 0.000000 100/100 2024-06-12 21:24:37.584746 2024-06-12 21:24:33.079519 A al_jitter false 0.000356 0.000046 0.000000 100/100 2024-06-12 21:24:25.414760 2024-06-12 21:24:17.449490
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-06-12 21:24:40.898027 2024-06-12 21:24:25.414760 3 36.96 al_loss false 2024-06-12 21:24:37.584746 2024-06-12 21:24:33.079519 4 43.39 al_rtt true 2024-06-12 21:24:43.666868 2024-06-12 21:24:37.086210 5 48.18
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.210513 0.257766 0.000000 100/100 2024-06-12 21:24:43.666868 2024-06-12 21:24:37.086210 A al_loss false 0.210513 0.257766 0.000000 100/100 2024-06-12 21:24:37.584746 2024-06-12 21:24:33.079519 A al_jitter true 0.210513 0.257766 0.000000 100/100 2024-06-12 21:24:40.898027 2024-06-12 21:24:25.414760
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-06-12 21:24:48.956292 2024-06-12 21:24:40.898027 4 44.93 al_loss false 2024-06-12 21:24:37.584746 2024-06-12 21:24:33.079519 4 36.40 al_rtt false 2024-06-12 21:24:45.767932 2024-06-12 21:24:43.666868 6 45.40
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.000371 0.000049 0.000000 100/100 2024-06-12 21:24:45.767932 2024-06-12 21:24:43.666868 A al_loss false 0.000371 0.000049 0.000000 100/100 2024-06-12 21:24:37.584746 2024-06-12 21:24:33.079519 A al_jitter false 0.000371 0.000049 0.000000 100/100 2024-06-12 21:24:48.956292 2024-06-12 21:24:40.898027
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.000036 0.000007 0.000000 9/100 A al_loss false 0.000036 0.000007 0.000000 9/100 A al_jitter false 0.000036 0.000007 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-06-12 21:25:02.264999 1 55.14 al_loss true 2024-06-12 21:25:01.913185 1 60.52 al_rtt true 2024-06-12 21:25:03.365896 1 38.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.470209 0.459829 47.000000 100/100 2024-06-12 21:25:03.365896 A al_loss true 0.470209 0.459829 47.000000 100/100 2024-06-12 21:25:01.913185 A al_jitter true 0.470209 0.459829 47.000000 100/100 2024-06-12 21:25:02.264999
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-06-12 21:25:11.084014 2024-06-12 21:25:02.264999 2 72.16 al_loss false 2024-06-12 21:25:11.034478 2024-06-12 21:25:01.913185 2 74.58 al_rtt false 2024-06-12 21:25:10.124270 2024-06-12 21:25:03.365896 2 55.28
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.000407 0.000058 0.000000 100/100 2024-06-12 21:25:10.124270 2024-06-12 21:25:03.365896 A al_loss false 0.000407 0.000058 0.000000 100/100 2024-06-12 21:25:11.034478 2024-06-12 21:25:01.913185 A al_jitter false 0.000407 0.000058 0.000000 100/100 2024-06-12 21:25:11.084014 2024-06-12 21:25:02.264999
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-06-12 21:25:11.084014 2024-06-12 21:25:02.264999 2 48.40 al_loss false 2024-06-12 21:25:11.034478 2024-06-12 21:25:01.913185 2 50.03 al_rtt true 2024-06-12 21:25:14.436178 2024-06-12 21:25:10.124270 3 54.40
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.792403 0.009053 0.000000 100/100 2024-06-12 21:25:14.436178 2024-06-12 21:25:10.124270 A al_loss false 0.792403 0.009053 0.000000 100/100 2024-06-12 21:25:11.034478 2024-06-12 21:25:01.913185 A al_jitter false 0.792403 0.009053 0.000000 100/100 2024-06-12 21:25:11.084014 2024-06-12 21:25:02.264999
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-06-12 21:25:11.084014 2024-06-12 21:25:02.264999 2 36.74 al_loss false 2024-06-12 21:25:23.048331 2024-06-12 21:25:18.546963 4 56.73 al_rtt false 2024-06-12 21:25:22.550435 2024-06-12 21:25:14.436178 4 61.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.000375 0.000057 0.000000 100/100 2024-06-12 21:25:22.550435 2024-06-12 21:25:14.436178 A al_loss false 0.000375 0.000057 0.000000 100/100 2024-06-12 21:25:23.048331 2024-06-12 21:25:18.546963 A al_jitter false 0.000375 0.000057 0.000000 100/100 2024-06-12 21:25:11.084014 2024-06-12 21:25:02.264999
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-06-12 21:25:26.931312 2024-06-12 21:25:11.084014 3 37.49 al_loss false 2024-06-12 21:25:23.048331 2024-06-12 21:25:18.546963 4 45.43 al_rtt true 2024-06-12 21:25:28.914283 2024-06-12 21:25:22.550435 5 51.06
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.244232 0.284343 0.000000 100/100 2024-06-12 21:25:28.914283 2024-06-12 21:25:22.550435 A al_loss false 0.244232 0.284343 0.000000 100/100 2024-06-12 21:25:23.048331 2024-06-12 21:25:18.546963 A al_jitter true 0.244232 0.284343 0.000000 100/100 2024-06-12 21:25:26.931312 2024-06-12 21:25:11.084014
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-06-12 21:25:34.127254 2024-06-12 21:25:26.931312 4 44.67 al_loss false 2024-06-12 21:25:23.048331 2024-06-12 21:25:18.546963 4 37.99 al_rtt false 2024-06-12 21:25:32.618071 2024-06-12 21:25:28.914283 6 51.81
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.000372 0.000046 0.000000 100/100 2024-06-12 21:25:32.618071 2024-06-12 21:25:28.914283 A al_loss false 0.000372 0.000046 0.000000 100/100 2024-06-12 21:25:23.048331 2024-06-12 21:25:18.546963 A al_jitter false 0.000372 0.000046 0.000000 100/100 2024-06-12 21:25:34.127254 2024-06-12 21:25:26.931312
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-06-12 21:25:50.485652 2024-06-12 21:25:45.267887 2 74.67 al_rtt false 2024-06-12 21:25:50.083817 2024-06-12 21:25:46.017029 2 58.23
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.000839 0.001070 0.000000 100/100 2024-06-12 21:25:50.083817 2024-06-12 21:25:46.017029 A al_loss false 0.000839 0.001070 0.000000 100/100 2024-06-12 21:25:50.485652 2024-06-12 21:25:45.267887 A al_jitter false 0.000839 0.001070 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-06-12 21:25:53.501427 1 26.12 al_loss true 2024-06-12 21:25:53.085268 2024-06-12 21:25:50.485652 3 69.70 al_rtt true 2024-06-12 21:25:54.236523 2024-06-12 21:25:50.083817 3 51.91
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.460205 0.399870 46.000000 100/100 2024-06-12 21:25:54.236523 2024-06-12 21:25:50.083817 A al_loss true 0.460205 0.399870 46.000000 100/100 2024-06-12 21:25:53.085268 2024-06-12 21:25:50.485652 A al_jitter true 0.460205 0.399870 46.000000 100/100 2024-06-12 21:25:53.501427
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-06-12 21:26:01.919376 2024-06-12 21:25:53.501427 2 44.68 al_loss false 2024-06-12 21:26:02.103110 2024-06-12 21:25:53.085268 4 75.58 al_rtt false 2024-06-12 21:26:01.316493 2024-06-12 21:25:54.236523 4 59.19
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.000383 0.000057 0.000000 100/100 2024-06-12 21:26:01.316493 2024-06-12 21:25:54.236523 A al_loss false 0.000383 0.000057 0.000000 100/100 2024-06-12 21:26:02.103110 2024-06-12 21:25:53.085268 A al_jitter false 0.000383 0.000057 0.000000 100/100 2024-06-12 21:26:01.919376 2024-06-12 21:25:53.501427
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-06-12 21:26:01.919376 2024-06-12 21:25:53.501427 2 34.03 al_loss false 2024-06-12 21:26:02.103110 2024-06-12 21:25:53.085268 4 57.56 al_rtt true 2024-06-12 21:26:05.563990 2024-06-12 21:26:01.316493 5 57.68
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.783419 0.009056 0.000000 100/100 2024-06-12 21:26:05.563990 2024-06-12 21:26:01.316493 A al_loss false 0.783419 0.009056 0.000000 100/100 2024-06-12 21:26:02.103110 2024-06-12 21:25:53.085268 A al_jitter false 0.783419 0.009056 0.000000 100/100 2024-06-12 21:26:01.919376 2024-06-12 21:25:53.501427
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-06-12 21:26:01.919376 2024-06-12 21:25:53.501427 2 27.57 al_loss false 2024-06-12 21:26:14.122998 2024-06-12 21:26:09.619307 6 61.38 al_rtt false 2024-06-12 21:26:13.637520 2024-06-12 21:26:05.563990 6 62.97
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.000402 0.000055 0.000000 100/100 2024-06-12 21:26:13.637520 2024-06-12 21:26:05.563990 A al_loss false 0.000402 0.000055 0.000000 100/100 2024-06-12 21:26:14.122998 2024-06-12 21:26:09.619307 A al_jitter false 0.000402 0.000055 0.000000 100/100 2024-06-12 21:26:01.919376 2024-06-12 21:25:53.501427
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-06-12 21:26:17.829536 2024-06-12 21:26:01.919376 3 30.08 al_loss false 2024-06-12 21:26:14.122998 2024-06-12 21:26:09.619307 6 51.46 al_rtt true 2024-06-12 21:26:20.293963 2024-06-12 21:26:13.637520 7 52.98
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.203090 0.277128 0.000000 100/100 2024-06-12 21:26:20.293963 2024-06-12 21:26:13.637520 A al_loss false 0.203090 0.277128 0.000000 100/100 2024-06-12 21:26:14.122998 2024-06-12 21:26:09.619307 A al_jitter true 0.203090 0.277128 0.000000 100/100 2024-06-12 21:26:17.829536 2024-06-12 21:26:01.919376
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-06-12 21:26:24.993816 2024-06-12 21:26:17.829536 4 36.93 al_loss false 2024-06-12 21:26:25.511595 2024-06-12 21:26:21.686173 8 53.48 al_rtt false 2024-06-12 21:26:23.449349 2024-06-12 21:26:20.293963 8 53.04
Step 22: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000396 0.000053 0.000000 100/100 2024-06-12 21:26:23.449349 2024-06-12 21:26:20.293963 A al_loss false 0.000396 0.000053 0.000000 100/100 2024-06-12 21:26:25.511595 2024-06-12 21:26:21.686173 A al_jitter false 0.000396 0.000053 0.000000 100/100 2024-06-12 21:26:24.993816 2024-06-12 21:26:17.829536
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-06-12 21:26:42.186981 2024-06-12 21:26:36.666393 2 77.72 al_rtt false 2024-06-12 21:26:41.691726 2024-06-12 21:26:37.413329 2 60.27
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.000354 0.000048 0.000000 100/100 2024-06-12 21:26:41.691726 2024-06-12 21:26:37.413329 A al_loss false 0.000354 0.000048 0.000000 100/100 2024-06-12 21:26:42.186981 2024-06-12 21:26:36.666393 A al_jitter false 0.000354 0.000048 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-06-12 21:26:45.038441 1 26.32 al_loss true 2024-06-12 21:26:45.031998 2024-06-12 21:26:42.186981 3 68.22 al_rtt true 2024-06-12 21:26:46.185233 2024-06-12 21:26:41.691726 3 50.07
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.370223 0.419868 37.000000 100/100 2024-06-12 21:26:46.185233 2024-06-12 21:26:41.691726 A al_loss true 0.370223 0.419868 37.000000 100/100 2024-06-12 21:26:45.031998 2024-06-12 21:26:42.186981 A al_jitter true 0.370223 0.419868 37.000000 100/100 2024-06-12 21:26:45.038441
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-06-12 21:26:53.797452 2024-06-12 21:26:45.038441 2 46.23 al_loss false 2024-06-12 21:26:53.748260 2024-06-12 21:26:45.031998 4 75.11 al_rtt false 2024-06-12 21:26:52.347222 2024-06-12 21:26:46.185233 4 55.10
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.000348 0.000047 0.000000 100/100 2024-06-12 21:26:52.347222 2024-06-12 21:26:46.185233 A al_loss false 0.000348 0.000047 0.000000 100/100 2024-06-12 21:26:53.748260 2024-06-12 21:26:45.031998 A al_jitter false 0.000348 0.000047 0.000000 100/100 2024-06-12 21:26:53.797452 2024-06-12 21:26:45.038441
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-06-12 21:26:53.797452 2024-06-12 21:26:45.038441 2 34.95 al_loss false 2024-06-12 21:26:53.748260 2024-06-12 21:26:45.031998 4 56.79 al_rtt true 2024-06-12 21:26:57.255620 2024-06-12 21:26:52.347222 5 54.15
Step 13: Run command service nsm operation show
at DUT0
and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.792399 0.009083 0.000000 100/100 2024-06-12 21:26:57.255620 2024-06-12 21:26:52.347222 A al_loss false 0.792399 0.009083 0.000000 100/100 2024-06-12 21:26:53.748260 2024-06-12 21:26:45.031998 A al_jitter false 0.792399 0.009083 0.000000 100/100 2024-06-12 21:26:53.797452 2024-06-12 21:26:45.038441
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-06-12 21:26:53.797452 2024-06-12 21:26:45.038441 2 28.40 al_loss false 2024-06-12 21:27:05.822963 2024-06-12 21:27:01.329763 6 60.70 al_rtt false 2024-06-12 21:27:05.332852 2024-06-12 21:26:57.255620 6 60.02
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.000047 0.000000 100/100 2024-06-12 21:27:05.332852 2024-06-12 21:26:57.255620 A al_loss false 0.000374 0.000047 0.000000 100/100 2024-06-12 21:27:05.822963 2024-06-12 21:27:01.329763 A al_jitter false 0.000374 0.000047 0.000000 100/100 2024-06-12 21:26:53.797452 2024-06-12 21:26:45.038441
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-06-12 21:27:10.581487 2024-06-12 21:26:53.797452 3 28.19 al_loss false 2024-06-12 21:27:05.822963 2024-06-12 21:27:01.329763 6 50.76 al_rtt false 2024-06-12 21:27:05.332852 2024-06-12 21:26:57.255620 6 50.19
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.179104 0.239642 0.000000 100/100 2024-06-12 21:27:05.332852 2024-06-12 21:26:57.255620 A al_loss false 0.179104 0.239642 0.000000 100/100 2024-06-12 21:27:05.822963 2024-06-12 21:27:01.329763 A al_jitter true 0.179104 0.239642 0.000000 100/100 2024-06-12 21:27:10.581487 2024-06-12 21:26:53.797452
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-06-12 21:27:17.444174 2024-06-12 21:27:10.581487 4 36.54 al_loss false 2024-06-12 21:27:17.701437 2024-06-12 21:27:13.735264 8 53.08 al_rtt false 2024-06-12 21:27:15.946924 2024-06-12 21:27:13.441639 8 49.17
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.000345 0.000042 0.000000 100/100 2024-06-12 21:27:15.946924 2024-06-12 21:27:13.441639 A al_loss false 0.000345 0.000042 0.000000 100/100 2024-06-12 21:27:17.701437 2024-06-12 21:27:13.735264 A al_jitter false 0.000345 0.000042 0.000000 100/100 2024-06-12 21:27:17.444174 2024-06-12 21:27:10.581487
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.