Check Udp Operation

This scenario shows how to configure Network Service Monitor (NSM) operations to measure network quality using active traffic probes and the UDP SLA protocol. In addition, the UDP NSM responder service is configured.

../../../_images/common2.svg

Test IPv4 Destination

Description

In this scenario, UDP NSM operations are configured in DUT0 (using an IPv4 destination address) and the UDP NSM responder service is configured in DUT1.

Scenario

Step 1: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.215.200.100/24
set service nsm responder type udp port 60000

Step 2: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.215.200.50/24
set service nsm operation A destination-address 10.215.200.100
set service nsm operation A type udp
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A window 100
set service nsm operation A alarm al_loss activate loss 5
set service nsm operation A alarm al_rtt activate rtt 0.2
set service nsm operation A alarm al_jitter activate jitter 0.1
set system alarm al_loss
set system alarm al_rtt
set system alarm al_jitter
set service nsm operation A destination-port 60000

Step 3: Run command system alarm show at DUT0 and check if output matches the following regular expressions:

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------
  Alarm    Status  Toggled  Prev-toggled  Toggle-count  Time up (%)
-------------------------------------------------------------------
al_jitter  false                                     0         0.00
al_loss    false                                     0         0.00
al_rtt     false                                     0         0.00

Step 4: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
---------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window  Toggled  Prev-toggled
---------------------------------------------------------------------------------------------
A          al_rtt     false   0.000039    0.000009    0.000000  9/100
A          al_loss    false   0.000039    0.000009    0.000000  9/100
A          al_jitter  false   0.000039    0.000009    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:21:00.418945                           1        47.21
al_loss    true    2024-06-12 21:20:59.764592                           1        57.61
al_rtt     true    2024-06-12 21:21:01.014572                           1        37.84

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.400254    0.429835    40.000000  100/100  2024-06-12 21:21:01.014572
A          al_loss    true    0.400254    0.429835    40.000000  100/100  2024-06-12 21:20:59.764592
A          al_jitter  true    0.400254    0.429835    40.000000  100/100  2024-06-12 21:21:00.418945

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:21:08.590646  2024-06-12 21:21:00.418945             2        67.23
al_loss    false   2024-06-12 21:21:08.648186  2024-06-12 21:20:59.764592             2        73.11
al_rtt     false   2024-06-12 21:21:07.629457  2024-06-12 21:21:01.014572             2        54.46

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.000429    0.000059    0.000000  100/100  2024-06-12 21:21:07.629457  2024-06-12 21:21:01.014572
A          al_loss    false   0.000429    0.000059    0.000000  100/100  2024-06-12 21:21:08.648186  2024-06-12 21:20:59.764592
A          al_jitter  false   0.000429    0.000059    0.000000  100/100  2024-06-12 21:21:08.590646  2024-06-12 21:21:00.418945

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:21:08.590646  2024-06-12 21:21:00.418945             2        45.31
al_loss    false   2024-06-12 21:21:08.648186  2024-06-12 21:20:59.764592             2        49.27
al_rtt     true    2024-06-12 21:21:12.005316  2024-06-12 21:21:07.629457             3        53.96

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.792452    0.009071    0.000000  100/100  2024-06-12 21:21:12.005316  2024-06-12 21:21:07.629457
A          al_loss    false   0.792452    0.009071    0.000000  100/100  2024-06-12 21:21:08.648186  2024-06-12 21:20:59.764592
A          al_jitter  false   0.792452    0.009071    0.000000  100/100  2024-06-12 21:21:08.590646  2024-06-12 21:21:00.418945

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:21:08.590646  2024-06-12 21:21:00.418945             2        34.13
al_loss    false   2024-06-12 21:21:20.666192  2024-06-12 21:21:16.144372             4        56.00
al_rtt     false   2024-06-12 21:21:20.158846  2024-06-12 21:21:12.005316             4        61.71

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.000398    0.000055    0.000000  100/100  2024-06-12 21:21:20.158846  2024-06-12 21:21:12.005316
A          al_loss    false   0.000398    0.000055    0.000000  100/100  2024-06-12 21:21:20.666192  2024-06-12 21:21:16.144372
A          al_jitter  false   0.000398    0.000055    0.000000  100/100  2024-06-12 21:21:08.590646  2024-06-12 21:21:00.418945

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:21:24.087560  2024-06-12 21:21:08.590646             3        36.99
al_loss    false   2024-06-12 21:21:20.666192  2024-06-12 21:21:16.144372             4        44.86
al_rtt     true    2024-06-12 21:21:26.027934  2024-06-12 21:21:20.158846             5        52.59

Step 19: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:

(al_jitter)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.229054    0.283994    1.000000  100/100  2024-06-12 21:21:26.027934  2024-06-12 21:21:20.158846
A          al_loss    false   0.229054    0.283994    1.000000  100/100  2024-06-12 21:21:20.666192  2024-06-12 21:21:16.144372
A          al_jitter  true    0.229054    0.283994    1.000000  100/100  2024-06-12 21:21:24.087560  2024-06-12 21:21:08.590646

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:21:31.490121  2024-06-12 21:21:24.087560             4        43.66
al_loss    false   2024-06-12 21:21:20.666192  2024-06-12 21:21:16.144372             4        37.58
al_rtt     false   2024-06-12 21:21:29.029440  2024-06-12 21:21:26.027934             6        49.83

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.000416    0.000052    0.000000  100/100  2024-06-12 21:21:29.029440  2024-06-12 21:21:26.027934
A          al_loss    false   0.000416    0.000052    0.000000  100/100  2024-06-12 21:21:20.666192  2024-06-12 21:21:16.144372
A          al_jitter  false   0.000416    0.000052    0.000000  100/100  2024-06-12 21:21:31.490121  2024-06-12 21:21:24.087560

Note

The previous command output should show that the alarms are desactivated, since the network quality is good.


Test IPv4 FQDN Destination

Description

In this scenario, UDP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv4 destination address) and the UDP NSM responder service is configured in DUT1.

Scenario

Step 1: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.215.200.100/24
set service nsm responder type udp port 60000

Step 2: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.215.200.50/24
set service nsm operation A destination-address test.nsm.fqdn
set service nsm operation A type udp
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A window 100
set service nsm operation A alarm al_loss activate loss 5
set service nsm operation A alarm al_rtt activate rtt 0.2
set service nsm operation A alarm al_jitter activate jitter 0.1
set system alarm al_loss
set system alarm al_rtt
set system alarm al_jitter
set service nsm operation A destination-port 60000
set service dns static host-name testnsm alias test.nsm.fqdn
set service dns static host-name testnsm inet 10.215.200.100

Step 3: Run command system alarm show at DUT0 and check if output matches the following regular expressions:

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------
  Alarm    Status  Toggled  Prev-toggled  Toggle-count  Time up (%)
-------------------------------------------------------------------
al_jitter  false                                     0         0.00
al_loss    false                                     0         0.00
al_rtt     false                                     0         0.00

Step 4: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
---------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window  Toggled  Prev-toggled
---------------------------------------------------------------------------------------------
A          al_rtt     false   0.000040    0.000006    0.000000  9/100
A          al_loss    false   0.000040    0.000006    0.000000  9/100
A          al_jitter  false   0.000040    0.000006    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:21:46.451547                           1        42.69
al_loss    true    2024-06-12 21:21:45.499251                           1        57.60
al_rtt     true    2024-06-12 21:21:46.611302                           1        40.15

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.450262    0.399867    45.000000  100/100  2024-06-12 21:21:46.611302
A          al_loss    true    0.450262    0.399867    45.000000  100/100  2024-06-12 21:21:45.499251
A          al_jitter  true    0.450262    0.399867    45.000000  100/100  2024-06-12 21:21:46.451547

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:21:54.225660  2024-06-12 21:21:46.451547             2        63.82
al_loss    false   2024-06-12 21:21:54.584698  2024-06-12 21:21:45.499251             2        74.55
al_rtt     false   2024-06-12 21:21:53.717316  2024-06-12 21:21:46.611302             2        58.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.000432    0.000053    0.000000  100/100  2024-06-12 21:21:53.717316  2024-06-12 21:21:46.611302
A          al_loss    false   0.000432    0.000053    0.000000  100/100  2024-06-12 21:21:54.584698  2024-06-12 21:21:45.499251
A          al_jitter  false   0.000432    0.000053    0.000000  100/100  2024-06-12 21:21:54.225660  2024-06-12 21:21:46.451547

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:21:54.225660  2024-06-12 21:21:46.451547             2        42.47
al_loss    false   2024-06-12 21:21:54.584698  2024-06-12 21:21:45.499251             2        49.62
al_rtt     true    2024-06-12 21:21:57.938453  2024-06-12 21:21:53.717316             3        56.14

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.792603    0.009332    0.000000  100/100  2024-06-12 21:21:57.938453  2024-06-12 21:21:53.717316
A          al_loss    false   0.792603    0.009332    0.000000  100/100  2024-06-12 21:21:54.584698  2024-06-12 21:21:45.499251
A          al_jitter  false   0.792603    0.009332    0.000000  100/100  2024-06-12 21:21:54.225660  2024-06-12 21:21:46.451547

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:21:54.225660  2024-06-12 21:21:46.451547             2        32.27
al_loss    false   2024-06-12 21:22:06.556983  2024-06-12 21:22:02.035409             4        56.47
al_rtt     false   2024-06-12 21:22:06.068395  2024-06-12 21:21:57.938453             4        63.24

Step 16: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000449    0.000060    0.000000  100/100  2024-06-12 21:22:06.068395  2024-06-12 21:21:57.938453
A          al_loss    false   0.000449    0.000060    0.000000  100/100  2024-06-12 21:22:06.556983  2024-06-12 21:22:02.035409
A          al_jitter  false   0.000449    0.000060    0.000000  100/100  2024-06-12 21:21:54.225660  2024-06-12 21:21:46.451547

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:22:09.557791  2024-06-12 21:21:54.225660             3        36.81
al_loss    false   2024-06-12 21:22:06.556983  2024-06-12 21:22:02.035409             4        45.29
al_rtt     true    2024-06-12 21:22:12.039324  2024-06-12 21:22:06.068395             5        53.39

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.257085    0.338948    0.000000  100/100  2024-06-12 21:22:12.039324  2024-06-12 21:22:06.068395
A          al_loss    false   0.257085    0.338948    0.000000  100/100  2024-06-12 21:22:06.556983  2024-06-12 21:22:02.035409
A          al_jitter  true    0.257085    0.338948    0.000000  100/100  2024-06-12 21:22:09.557791  2024-06-12 21:21:54.225660

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:22:17.879718  2024-06-12 21:22:09.557791             4        44.88
al_loss    false   2024-06-12 21:22:06.556983  2024-06-12 21:22:02.035409             4        37.93
al_rtt     false   2024-06-12 21:22:15.921359  2024-06-12 21:22:12.039324             6        53.30

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.000439    0.000053    0.000000  100/100  2024-06-12 21:22:15.921359  2024-06-12 21:22:12.039324
A          al_loss    false   0.000439    0.000053    0.000000  100/100  2024-06-12 21:22:06.556983  2024-06-12 21:22:02.035409
A          al_jitter  false   0.000439    0.000053    0.000000  100/100  2024-06-12 21:22:17.879718  2024-06-12 21:22:09.557791

Note

The previous command output should show that the alarms are desactivated, since the network quality is good.


Test IPv6 Destination

Description

In this scenario, UDP NSM operations are configured in DUT0 (using an IPv6 destination address) and the UDP NSM responder service is configured in DUT1.

Scenario

Step 1: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10::3/64
set service nsm responder type udp port 60000

Step 2: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10::2/64
set service nsm operation A destination-address 10::3
set service nsm operation A type udp
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A window 100
set service nsm operation A alarm al_loss activate loss 5
set service nsm operation A alarm al_rtt activate rtt 0.2
set service nsm operation A alarm al_jitter activate jitter 0.1
set system alarm al_loss
set system alarm al_rtt
set system alarm al_jitter
set service nsm operation A destination-port 60000

Step 3: Run command system alarm show at DUT0 and check if output matches the following regular expressions:

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false                                                                      0         0.00
al_loss    false   2024-06-12 21:22:35.538274  2024-06-12 21:22:30.593006             2        70.38
al_rtt     false   2024-06-12 21:22:35.287624  2024-06-12 21:22:31.334817             2        56.29

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.000383    0.000529    0.000000  100/100  2024-06-12 21:22:35.287624  2024-06-12 21:22:31.334817
A          al_loss    false   0.000383    0.000529    0.000000  100/100  2024-06-12 21:22:35.538274  2024-06-12 21:22:30.593006
A          al_jitter  false   0.000383    0.000529    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:22:38.751174                                         1        26.74
al_loss    true    2024-06-12 21:22:38.697177  2024-06-12 21:22:35.538274             3        65.32
al_rtt     true    2024-06-12 21:22:40.973842  2024-06-12 21:22:35.287624             3        40.11

Step 7: Run command service nsm operation show at DUT0 and check if output matches the following regular expressions:

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)    Loss(%)   Window            Toggled                   Prev-toggled
--------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.350248    0.419858    35.000000  100/100  2024-06-12 21:22:40.973842  2024-06-12 21:22:35.287624
A          al_loss    true    0.350248    0.419858    35.000000  100/100  2024-06-12 21:22:38.697177  2024-06-12 21:22:35.538274
A          al_jitter  true    0.350248    0.419858    35.000000  100/100  2024-06-12 21:22:38.751174

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:22:47.169591  2024-06-12 21:22:38.751174             2        44.96
al_loss    false   2024-06-12 21:22:47.210982  2024-06-12 21:22:38.697177             4        71.89
al_rtt     false   2024-06-12 21:22:45.906540  2024-06-12 21:22:40.973842             4        47.47

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.000062    0.000000  100/100  2024-06-12 21:22:45.906540  2024-06-12 21:22:40.973842
A          al_loss    false   0.000383    0.000062    0.000000  100/100  2024-06-12 21:22:47.210982  2024-06-12 21:22:38.697177
A          al_jitter  false   0.000383    0.000062    0.000000  100/100  2024-06-12 21:22:47.169591  2024-06-12 21:22:38.751174

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:22:47.169591  2024-06-12 21:22:38.751174             2        33.99
al_loss    false   2024-06-12 21:22:47.210982  2024-06-12 21:22:38.697177             4        54.36
al_rtt     true    2024-06-12 21:22:50.873323  2024-06-12 21:22:45.906540             5        48.59

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.792461    0.009063    0.000000  100/100  2024-06-12 21:22:50.873323  2024-06-12 21:22:45.906540
A          al_loss    false   0.792461    0.009063    0.000000  100/100  2024-06-12 21:22:47.210982  2024-06-12 21:22:38.697177
A          al_jitter  false   0.792461    0.009063    0.000000  100/100  2024-06-12 21:22:47.169591  2024-06-12 21:22:38.751174

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:22:47.169591  2024-06-12 21:22:38.751174             2        27.58
al_loss    false   2024-06-12 21:22:59.432690  2024-06-12 21:22:54.929037             6        58.85
al_rtt     false   2024-06-12 21:22:58.935205  2024-06-12 21:22:50.873323             6        55.53

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.000391    0.000073    0.000000  100/100  2024-06-12 21:22:58.935205  2024-06-12 21:22:50.873323
A          al_loss    false   0.000391    0.000073    0.000000  100/100  2024-06-12 21:22:59.432690  2024-06-12 21:22:54.929037
A          al_jitter  false   0.000391    0.000073    0.000000  100/100  2024-06-12 21:22:47.169591  2024-06-12 21:22:38.751174

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:23:02.719979  2024-06-12 21:22:47.169591             3        31.71
al_loss    false   2024-06-12 21:22:59.432690  2024-06-12 21:22:54.929037             6        48.98
al_rtt     true    2024-06-12 21:23:05.694667  2024-06-12 21:22:58.935205             7        46.86

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.212719    0.298393    0.000000  100/100  2024-06-12 21:23:05.694667  2024-06-12 21:22:58.935205
A          al_loss    false   0.212719    0.298393    0.000000  100/100  2024-06-12 21:22:59.432690  2024-06-12 21:22:54.929037
A          al_jitter  true    0.212719    0.298393    0.000000  100/100  2024-06-12 21:23:02.719979  2024-06-12 21:22:47.169591

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:23:10.858278  2024-06-12 21:23:02.719979             4        38.78
al_loss    false   2024-06-12 21:23:11.254712  2024-06-12 21:23:07.656556             8        50.51
al_rtt     false   2024-06-12 21:23:09.353229  2024-06-12 21:23:05.694667             8        48.28

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.000422    0.000050    0.000000  100/100  2024-06-12 21:23:09.353229  2024-06-12 21:23:05.694667
A          al_loss    false   0.000422    0.000050    0.000000  100/100  2024-06-12 21:23:11.254712  2024-06-12 21:23:07.656556
A          al_jitter  false   0.000422    0.000050    0.000000  100/100  2024-06-12 21:23:10.858278  2024-06-12 21:23:02.719979

Note

The previous command output should show that the alarms are desactivated, since the network quality is good.


Test IPv6 FQDN Destination

Description

In this scenario, UDP NSM operations are configured in DUT0 (using a Fully Qualified Domain Name as the IPv6 destination address) and the UDP NSM responder service is configured in DUT1.

Scenario

Step 1: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10::3/64
set service nsm responder type udp port 60000

Step 2: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10::2/64
set service nsm operation A destination-address test.nsm.fqdn
set service nsm operation A type udp
set service nsm operation A interval 0.05
set service nsm operation A local-interface eth0
set service nsm operation A window 100
set service nsm operation A alarm al_loss activate loss 5
set service nsm operation A alarm al_rtt activate rtt 0.2
set service nsm operation A alarm al_jitter activate jitter 0.1
set system alarm al_loss
set system alarm al_rtt
set system alarm al_jitter
set service nsm operation A destination-port 60000
set service dns static host-name testnsm alias test.nsm.fqdn
set service dns static host-name testnsm inet 10::3

Step 3: Run command system alarm show at DUT0 and check if output matches the following regular expressions:

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false                                                                      0         0.00
al_loss    false   2024-06-12 21:23:27.883803  2024-06-12 21:23:23.014756             2        69.40
al_rtt     false   2024-06-12 21:23:27.675510  2024-06-12 21:23:23.764148             2        55.78

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.000970    0.001074    0.000000  100/100  2024-06-12 21:23:27.675510  2024-06-12 21:23:23.764148
A          al_loss    false   0.000970    0.001074    0.000000  100/100  2024-06-12 21:23:27.883803  2024-06-12 21:23:23.014756
A          al_jitter  false   0.000970    0.001074    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:23:32.292890                                         1        18.32
al_loss    true    2024-06-12 21:23:30.792585  2024-06-12 21:23:27.883803             3        67.30
al_rtt     true    2024-06-12 21:23:31.787995  2024-06-12 21:23:27.675510             3        52.29

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.530195    0.359862    53.000000  100/100  2024-06-12 21:23:31.787995  2024-06-12 21:23:27.675510
A          al_loss    true    0.530195    0.359862    53.000000  100/100  2024-06-12 21:23:30.792585  2024-06-12 21:23:27.883803
A          al_jitter  true    0.530195    0.359862    53.000000  100/100  2024-06-12 21:23:32.292890

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:23:39.696762  2024-06-12 21:23:32.292890             2        39.37
al_loss    false   2024-06-12 21:23:39.797047  2024-06-12 21:23:30.792585             4        73.73
al_rtt     false   2024-06-12 21:23:38.906074  2024-06-12 21:23:31.787995             4        58.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.000433    0.000060    0.000000  100/100  2024-06-12 21:23:38.906074  2024-06-12 21:23:31.787995
A          al_loss    false   0.000433    0.000060    0.000000  100/100  2024-06-12 21:23:39.797047  2024-06-12 21:23:30.792585
A          al_jitter  false   0.000433    0.000060    0.000000  100/100  2024-06-12 21:23:39.696762  2024-06-12 21:23:32.292890

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:23:39.696762  2024-06-12 21:23:32.292890             2        29.97
al_loss    false   2024-06-12 21:23:39.797047  2024-06-12 21:23:30.792585             4        56.14
al_rtt     true    2024-06-12 21:23:43.260581  2024-06-12 21:23:38.906074             5        57.27

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.783456    0.009068    0.000000  100/100  2024-06-12 21:23:43.260581  2024-06-12 21:23:38.906074
A          al_loss    false   0.783456    0.009068    0.000000  100/100  2024-06-12 21:23:39.797047  2024-06-12 21:23:30.792585
A          al_jitter  false   0.783456    0.009068    0.000000  100/100  2024-06-12 21:23:39.696762  2024-06-12 21:23:32.292890

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:23:39.696762  2024-06-12 21:23:32.292890             2        24.25
al_loss    false   2024-06-12 21:23:51.818263  2024-06-12 21:23:47.313413             6        60.19
al_rtt     false   2024-06-12 21:23:51.326321  2024-06-12 21:23:43.260581             6        62.55

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.000412    0.000053    0.000000  100/100  2024-06-12 21:23:51.326321  2024-06-12 21:23:43.260581
A          al_loss    false   0.000412    0.000053    0.000000  100/100  2024-06-12 21:23:51.818263  2024-06-12 21:23:47.313413
A          al_jitter  false   0.000412    0.000053    0.000000  100/100  2024-06-12 21:23:39.696762  2024-06-12 21:23:32.292890

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:23:54.674294  2024-06-12 21:23:39.696762             3        29.70
al_loss    false   2024-06-12 21:23:51.818263  2024-06-12 21:23:47.313413             6        50.48
al_rtt     true    2024-06-12 21:23:56.812521  2024-06-12 21:23:51.326321             7        55.93

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.240837    0.321448    0.000000  100/100  2024-06-12 21:23:56.812521  2024-06-12 21:23:51.326321
A          al_loss    false   0.240837    0.321448    0.000000  100/100  2024-06-12 21:23:51.818263  2024-06-12 21:23:47.313413
A          al_jitter  true    0.240837    0.321448    0.000000  100/100  2024-06-12 21:23:54.674294  2024-06-12 21:23:39.696762

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:02.793161  2024-06-12 21:23:54.674294             4        36.70
al_loss    false   2024-06-12 21:24:03.496082  2024-06-12 21:23:59.643194             8        52.55
al_rtt     false   2024-06-12 21:24:00.895840  2024-06-12 21:23:56.812521             8        54.79

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.000407    0.000066    0.000000  100/100  2024-06-12 21:24:00.895840  2024-06-12 21:23:56.812521
A          al_loss    false   0.000407    0.000066    0.000000  100/100  2024-06-12 21:24:03.496082  2024-06-12 21:23:59.643194
A          al_jitter  false   0.000407    0.000066    0.000000  100/100  2024-06-12 21:24:02.793161  2024-06-12 21:23:54.674294

Note

The previous command output should show that the alarms are desactivated, since the network quality is good.