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.000017 0.000004 0.000000 6/100 A al_loss false 0.000017 0.000004 0.000000 6/100 A al_jitter false 0.000017 0.000004 0.000000 6/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-10-09 08:36:54.633724 1 47.29 al_loss true 2024-10-09 08:36:53.530174 1 66.01 al_rtt true 2024-10-09 08:36:54.731687 1 45.68
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.450247 0.429788 45.000000 97/100 2024-10-09 08:36:54.731687 A al_loss true 0.450247 0.429788 45.000000 97/100 2024-10-09 08:36:53.530174 A al_jitter true 0.450247 0.429788 45.000000 97/100 2024-10-09 08:36:54.633724
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:37:02.456164 2024-10-09 08:36:54.633724 2 68.18 al_loss false 2024-10-09 08:37:02.407453 2024-10-09 08:36:53.530174 2 77.39 al_rtt false 2024-10-09 08:37:01.111980 2024-10-09 08:36:54.731687 2 55.63
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.000468 0.000132 0.000000 100/100 2024-10-09 08:37:01.111980 2024-10-09 08:36:54.731687 A al_loss false 0.000468 0.000132 0.000000 100/100 2024-10-09 08:37:02.407453 2024-10-09 08:36:53.530174 A al_jitter false 0.000468 0.000132 0.000000 100/100 2024-10-09 08:37:02.456164 2024-10-09 08:36:54.633724
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:37:02.456164 2024-10-09 08:36:54.633724 2 45.73 al_loss false 2024-10-09 08:37:02.407453 2024-10-09 08:36:53.530174 2 51.91 al_rtt true 2024-10-09 08:37:05.511257 2024-10-09 08:37:01.111980 3 55.53
Step 13: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt true 0.774578 0.009120 0.000000 100/100 2024-10-09 08:37:05.511257 2024-10-09 08:37:01.111980 A al_loss false 0.774578 0.009120 0.000000 100/100 2024-10-09 08:37:02.407453 2024-10-09 08:36:53.530174 A al_jitter false 0.774578 0.009120 0.000000 100/100 2024-10-09 08:37:02.456164 2024-10-09 08:36:54.633724
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:37:02.456164 2024-10-09 08:36:54.633724 2 34.52 al_loss false 2024-10-09 08:37:13.894244 2024-10-09 08:37:09.370317 4 59.14 al_rtt false 2024-10-09 08:37:13.384192 2024-10-09 08:37:05.511257 4 62.91
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.000566 0.000129 0.000000 100/100 2024-10-09 08:37:13.384192 2024-10-09 08:37:05.511257 A al_loss false 0.000566 0.000129 0.000000 100/100 2024-10-09 08:37:13.894244 2024-10-09 08:37:09.370317 A al_jitter false 0.000566 0.000129 0.000000 100/100 2024-10-09 08:37:02.456164 2024-10-09 08:36:54.633724
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-10-09 08:37:16.649257 2024-10-09 08:37:02.456164 3 38.72 al_loss false 2024-10-09 08:37:13.894244 2024-10-09 08:37:09.370317 4 47.46 al_rtt true 2024-10-09 08:37:18.753126 2024-10-09 08:37:13.384192 5 54.05
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.236759 0.281616 0.000000 100/100 2024-10-09 08:37:18.753126 2024-10-09 08:37:13.384192 A al_loss false 0.236759 0.281616 0.000000 100/100 2024-10-09 08:37:13.894244 2024-10-09 08:37:09.370317 A al_jitter true 0.236759 0.281616 0.000000 100/100 2024-10-09 08:37:16.649257 2024-10-09 08:37:02.456164
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:37:24.519308 2024-10-09 08:37:16.649257 4 46.45 al_loss false 2024-10-09 08:37:13.894244 2024-10-09 08:37:09.370317 4 39.67 al_rtt false 2024-10-09 08:37:21.908133 2024-10-09 08:37:18.753126 6 51.54
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.000611 0.000142 0.000000 100/100 2024-10-09 08:37:21.908133 2024-10-09 08:37:18.753126 A al_loss false 0.000611 0.000142 0.000000 100/100 2024-10-09 08:37:13.894244 2024-10-09 08:37:09.370317 A al_jitter false 0.000611 0.000142 0.000000 100/100 2024-10-09 08:37:24.519308 2024-10-09 08:37:16.649257
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.000024 0.000007 0.000000 6/100 A al_loss false 0.000024 0.000007 0.000000 6/100 A al_jitter false 0.000024 0.000007 0.000000 6/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
-------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) -------------------------------------------------------------------------------------- al_jitter true 2024-10-09 08:37:33.704151 1 50.21 al_loss true 2024-10-09 08:37:32.902769 1 63.59 al_rtt true 2024-10-09 08:37:34.506299 1 36.74
Step 7: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
------------------------------------------------------------------------------------------------------------------ Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------ A al_rtt true 0.390330 0.399804 39.000000 100/100 2024-10-09 08:37:34.506299 A al_loss true 0.390330 0.399804 39.000000 100/100 2024-10-09 08:37:32.902769 A al_jitter true 0.390330 0.399804 39.000000 100/100 2024-10-09 08:37:33.704151
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:37:41.626039 2024-10-09 08:37:33.704151 2 68.95 al_loss false 2024-10-09 08:37:41.881334 2024-10-09 08:37:32.902769 2 78.10 al_rtt false 2024-10-09 08:37:40.675148 2024-10-09 08:37:34.506299 2 53.68
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.000630 0.000141 0.000000 100/100 2024-10-09 08:37:40.675148 2024-10-09 08:37:34.506299 A al_loss false 0.000630 0.000141 0.000000 100/100 2024-10-09 08:37:41.881334 2024-10-09 08:37:32.902769 A al_jitter false 0.000630 0.000141 0.000000 100/100 2024-10-09 08:37:41.626039 2024-10-09 08:37:33.704151
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:37:41.626039 2024-10-09 08:37:33.704151 2 46.40 al_loss false 2024-10-09 08:37:41.881334 2024-10-09 08:37:32.902769 2 52.58 al_rtt true 2024-10-09 08:37:44.686959 2024-10-09 08:37:40.675148 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.774754 0.009155 0.000000 100/100 2024-10-09 08:37:44.686959 2024-10-09 08:37:40.675148 A al_loss false 0.774754 0.009155 0.000000 100/100 2024-10-09 08:37:41.881334 2024-10-09 08:37:32.902769 A al_jitter false 0.774754 0.009155 0.000000 100/100 2024-10-09 08:37:41.626039 2024-10-09 08:37:33.704151
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:37:41.626039 2024-10-09 08:37:33.704151 2 35.00 al_loss false 2024-10-09 08:37:53.059963 2024-10-09 08:37:48.601503 4 59.35 al_rtt false 2024-10-09 08:37:52.567558 2024-10-09 08:37:44.686959 4 62.07
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.000537 0.000138 0.000000 100/100 2024-10-09 08:37:52.567558 2024-10-09 08:37:44.686959 A al_loss false 0.000537 0.000138 0.000000 100/100 2024-10-09 08:37:53.059963 2024-10-09 08:37:48.601503 A al_jitter false 0.000537 0.000138 0.000000 100/100 2024-10-09 08:37:41.626039 2024-10-09 08:37:33.704151
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-10-09 08:37:56.239182 2024-10-09 08:37:41.626039 3 37.77 al_loss false 2024-10-09 08:37:53.059963 2024-10-09 08:37:48.601503 4 47.55 al_rtt true 2024-10-09 08:37:58.701384 2024-10-09 08:37:52.567558 5 50.74
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.216834 0.258250 0.000000 100/100 2024-10-09 08:37:58.701384 2024-10-09 08:37:52.567558 A al_loss false 0.216834 0.258250 0.000000 100/100 2024-10-09 08:37:53.059963 2024-10-09 08:37:48.601503 A al_jitter true 0.216834 0.258250 0.000000 100/100 2024-10-09 08:37:56.239182 2024-10-09 08:37:41.626039
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:38:03.887460 2024-10-09 08:37:56.239182 4 46.10 al_loss false 2024-10-09 08:38:04.150545 2024-10-09 08:38:00.379289 6 50.94 al_rtt false 2024-10-09 08:38:01.782781 2024-10-09 08:37:58.701384 6 50.72
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.000427 0.000156 0.000000 100/100 2024-10-09 08:38:01.782781 2024-10-09 08:37:58.701384 A al_loss false 0.000427 0.000156 0.000000 100/100 2024-10-09 08:38:04.150545 2024-10-09 08:38:00.379289 A al_jitter false 0.000427 0.000156 0.000000 100/100 2024-10-09 08:38:03.887460 2024-10-09 08:37:56.239182
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-10-09 08:38:16.794258 2024-10-09 08:38:11.883940 2 73.99 al_rtt false 2024-10-09 08:38:16.543639 2024-10-09 08:38:12.632000 2 58.96
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.021166 0.004927 0.000000 100/100 2024-10-09 08:38:16.543639 2024-10-09 08:38:12.632000 A al_loss false 0.021166 0.004927 0.000000 100/100 2024-10-09 08:38:16.794258 2024-10-09 08:38:11.883940 A al_jitter false 0.021166 0.004927 0.000000 100/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-10-09 08:38:19.300073 1 28.74 al_loss true 2024-10-09 08:38:19.105247 2024-10-09 08:38:16.794258 3 70.47 al_rtt true 2024-10-09 08:38:20.602535 2024-10-09 08:38:16.543639 3 50.08
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.430294 0.509752 43.000000 100/100 2024-10-09 08:38:20.602535 2024-10-09 08:38:16.543639 A al_loss true 0.430294 0.509752 43.000000 100/100 2024-10-09 08:38:19.105247 2024-10-09 08:38:16.794258 A al_jitter true 0.430294 0.509752 43.000000 100/100 2024-10-09 08:38:19.300073
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:38:27.378092 2024-10-09 08:38:19.300073 2 45.43 al_loss false 2024-10-09 08:38:27.425323 2024-10-09 08:38:19.105247 4 74.42 al_rtt false 2024-10-09 08:38:26.220556 2024-10-09 08:38:20.602535 4 53.61
Step 10: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
------------------------------------------------------------------------------------------------------------------------------- Operation Alarm Status RTT(s) Jitter(s) Loss(%) Window Toggled Prev-toggled ------------------------------------------------------------------------------------------------------------------------------- A al_rtt false 0.000708 0.000118 0.000000 100/100 2024-10-09 08:38:26.220556 2024-10-09 08:38:20.602535 A al_loss false 0.000708 0.000118 0.000000 100/100 2024-10-09 08:38:27.425323 2024-10-09 08:38:19.105247 A al_jitter false 0.000708 0.000118 0.000000 100/100 2024-10-09 08:38:27.378092 2024-10-09 08:38:19.300073
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:38:27.378092 2024-10-09 08:38:19.300073 2 34.50 al_loss false 2024-10-09 08:38:27.425323 2024-10-09 08:38:19.105247 4 56.52 al_rtt true 2024-10-09 08:38:30.881195 2024-10-09 08:38:26.220556 5 54.01
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.774566 0.009149 0.000000 100/100 2024-10-09 08:38:30.881195 2024-10-09 08:38:26.220556 A al_loss false 0.774566 0.009149 0.000000 100/100 2024-10-09 08:38:27.425323 2024-10-09 08:38:19.105247 A al_jitter false 0.774566 0.009149 0.000000 100/100 2024-10-09 08:38:27.378092 2024-10-09 08:38:19.300073
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:38:27.378092 2024-10-09 08:38:19.300073 2 27.92 al_loss false 2024-10-09 08:38:39.204857 2024-10-09 08:38:34.687301 6 61.35 al_rtt false 2024-10-09 08:38:38.706053 2024-10-09 08:38:30.881195 6 60.00
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.000638 0.000153 0.000000 100/100 2024-10-09 08:38:38.706053 2024-10-09 08:38:30.881195 A al_loss false 0.000638 0.000153 0.000000 100/100 2024-10-09 08:38:39.204857 2024-10-09 08:38:34.687301 A al_jitter false 0.000638 0.000153 0.000000 100/100 2024-10-09 08:38:27.378092 2024-10-09 08:38:19.300073
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-10-09 08:38:42.313927 2024-10-09 08:38:27.378092 3 31.52 al_loss false 2024-10-09 08:38:39.204857 2024-10-09 08:38:34.687301 6 51.38 al_rtt false 2024-10-09 08:38:38.706053 2024-10-09 08:38:30.881195 6 50.25
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.159253 0.234290 0.000000 100/100 2024-10-09 08:38:38.706053 2024-10-09 08:38:30.881195 A al_loss false 0.159253 0.234290 0.000000 100/100 2024-10-09 08:38:39.204857 2024-10-09 08:38:34.687301 A al_jitter true 0.159253 0.234290 0.000000 100/100 2024-10-09 08:38:42.313927 2024-10-09 08:38:27.378092
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:38:49.232562 2024-10-09 08:38:42.313927 4 37.40 al_loss false 2024-10-09 08:38:39.204857 2024-10-09 08:38:34.687301 6 44.27 al_rtt false 2024-10-09 08:38:38.706053 2024-10-09 08:38:30.881195 6 43.29
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.000555 0.000141 0.000000 100/100 2024-10-09 08:38:38.706053 2024-10-09 08:38:30.881195 A al_loss false 0.000555 0.000141 0.000000 100/100 2024-10-09 08:38:39.204857 2024-10-09 08:38:34.687301 A al_jitter false 0.000555 0.000141 0.000000 100/100 2024-10-09 08:38:49.232562 2024-10-09 08:38:42.313927
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-10-09 08:39:02.867950 2024-10-09 08:38:57.998362 2 71.98 al_rtt false 2024-10-09 08:39:02.662370 2024-10-09 08:38:58.742504 2 57.97
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.012696 0.003884 0.000000 100/100 2024-10-09 08:39:02.662370 2024-10-09 08:38:58.742504 A al_loss false 0.012696 0.003884 0.000000 100/100 2024-10-09 08:39:02.867950 2024-10-09 08:38:57.998362 A al_jitter false 0.012696 0.003884 0.000000 100/100
Note
The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.
Note
If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.
Step 5: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out PLOSS set traffic control PLOSS type network-emulator packet-loss 50
Step 6: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-10-09 08:39:05.915748 1 25.07 al_loss true 2024-10-09 08:39:05.265071 2024-10-09 08:39:02.867950 3 69.75 al_rtt true 2024-10-09 08:39:06.566943 2024-10-09 08:39:02.662370 3 51.53
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.410280 0.439808 41.000000 100/100 2024-10-09 08:39:06.566943 2024-10-09 08:39:02.662370 A al_loss true 0.410280 0.439808 41.000000 100/100 2024-10-09 08:39:05.265071 2024-10-09 08:39:02.867950 A al_jitter true 0.410280 0.439808 41.000000 100/100 2024-10-09 08:39:05.915748
Note
The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.
Note
If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.
Step 8: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 9: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:39:13.839425 2024-10-09 08:39:05.915748 2 44.34 al_loss false 2024-10-09 08:39:14.239083 2024-10-09 08:39:05.265071 4 77.45 al_rtt false 2024-10-09 08:39:13.248231 2024-10-09 08:39:06.566943 4 59.32
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.000599 0.000133 0.000000 100/100 2024-10-09 08:39:13.248231 2024-10-09 08:39:06.566943 A al_loss false 0.000599 0.000133 0.000000 100/100 2024-10-09 08:39:14.239083 2024-10-09 08:39:05.265071 A al_jitter false 0.000599 0.000133 0.000000 100/100 2024-10-09 08:39:13.839425 2024-10-09 08:39:05.915748
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.
Step 11: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out RTT set traffic control RTT type network-emulator network-delay 900
Step 12: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_rtt)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:39:13.839425 2024-10-09 08:39:05.915748 2 33.78 al_loss false 2024-10-09 08:39:14.239083 2024-10-09 08:39:05.265071 4 59.01 al_rtt true 2024-10-09 08:39:17.065918 2024-10-09 08:39:13.248231 5 58.21
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.765665 0.009178 0.000000 100/100 2024-10-09 08:39:17.065918 2024-10-09 08:39:13.248231 A al_loss false 0.765665 0.009178 0.000000 100/100 2024-10-09 08:39:14.239083 2024-10-09 08:39:05.265071 A al_jitter false 0.765665 0.009178 0.000000 100/100 2024-10-09 08:39:13.839425 2024-10-09 08:39:05.915748
Note
The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.
Note
If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.
Step 14: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 15: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:39:13.839425 2024-10-09 08:39:05.915748 2 27.32 al_loss false 2024-10-09 08:39:25.379840 2024-10-09 08:39:20.861078 6 63.31 al_rtt false 2024-10-09 08:39:24.868302 2024-10-09 08:39:17.065918 6 63.46
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.000533 0.000153 0.000000 100/100 2024-10-09 08:39:24.868302 2024-10-09 08:39:17.065918 A al_loss false 0.000533 0.000153 0.000000 100/100 2024-10-09 08:39:25.379840 2024-10-09 08:39:20.861078 A al_jitter false 0.000533 0.000153 0.000000 100/100 2024-10-09 08:39:13.839425 2024-10-09 08:39:05.915748
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.
Note
If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.
Step 17: Set the following configuration in DUT0:
set interfaces ethernet eth0 traffic control out JITTER set traffic control JITTER type network-emulator network-delay 1 jitter 1000
Step 18: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_jitter)\s+(true)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter true 2024-10-09 08:39:28.268589 2024-10-09 08:39:13.839425 3 31.53 al_loss false 2024-10-09 08:39:25.379840 2024-10-09 08:39:20.861078 6 53.08 al_rtt true 2024-10-09 08:39:30.473591 2024-10-09 08:39:24.868302 7 55.45
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.245276 0.343176 0.000000 100/100 2024-10-09 08:39:30.473591 2024-10-09 08:39:24.868302 A al_loss false 0.245276 0.343176 0.000000 100/100 2024-10-09 08:39:25.379840 2024-10-09 08:39:20.861078 A al_jitter true 0.245276 0.343176 0.000000 100/100 2024-10-09 08:39:28.268589 2024-10-09 08:39:13.839425
Note
The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.
Note
If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.
Step 20: Set the following configuration in DUT0:
delete interfaces ethernet eth0 traffic control
Step 21: Run command system alarm show at DUT0 and check if output matches the following regular expressions:
(al_loss)\s+(false) (al_rtt)\s+(false) (al_jitter)\s+(false)Show output
---------------------------------------------------------------------------------------------------- Alarm Status Toggled Prev-toggled Toggle-count Time up (%) ---------------------------------------------------------------------------------------------------- al_jitter false 2024-10-09 08:39:36.203807 2024-10-09 08:39:28.268589 4 39.53 al_loss false 2024-10-09 08:39:36.459048 2024-10-09 08:39:32.445511 8 55.78 al_rtt false 2024-10-09 08:39:34.960773 2024-10-09 08:39:30.473591 8 57.06
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.000560 0.000159 0.000000 100/100 2024-10-09 08:39:34.960773 2024-10-09 08:39:30.473591 A al_loss false 0.000560 0.000159 0.000000 100/100 2024-10-09 08:39:36.459048 2024-10-09 08:39:32.445511 A al_jitter false 0.000560 0.000159 0.000000 100/100 2024-10-09 08:39:36.203807 2024-10-09 08:39:28.268589
Note
The previous command output should show that the alarms are desactivated, since the network quality is good.