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/common3.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.000042    0.000006    0.000000  9/100
A          al_loss    false   0.000042    0.000006    0.000000  9/100
A          al_jitter  false   0.000042    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-24 13:12:40.728174                           1        49.86
al_loss    true    2024-06-24 13:12:40.110826                           1        59.55
al_rtt     true    2024-06-24 13:12:41.567997                           1        36.78

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.450312    0.469932    45.000000  100/100  2024-06-24 13:12:41.567997
A          al_loss    true    0.450312    0.469932    45.000000  100/100  2024-06-24 13:12:40.110826
A          al_jitter  true    0.450312    0.469932    45.000000  100/100  2024-06-24 13:12:40.728174

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-24 13:12:48.891017  2024-06-24 13:12:40.728174             2        66.25
al_loss    false   2024-06-24 13:12:49.193261  2024-06-24 13:12:40.110826             2        73.74
al_rtt     false   2024-06-24 13:12:48.138656  2024-06-24 13:12:41.567997             2        53.37

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.000398    0.000065    0.000000  100/100  2024-06-24 13:12:48.138656  2024-06-24 13:12:41.567997
A          al_loss    false   0.000398    0.000065    0.000000  100/100  2024-06-24 13:12:49.193261  2024-06-24 13:12:40.110826
A          al_jitter  false   0.000398    0.000065    0.000000  100/100  2024-06-24 13:12:48.891017  2024-06-24 13:12:40.728174

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-24 13:12:48.891017  2024-06-24 13:12:40.728174             2        44.62
al_loss    false   2024-06-24 13:12:49.193261  2024-06-24 13:12:40.110826             2        49.66
al_rtt     true    2024-06-24 13:12:52.654796  2024-06-24 13:12:48.138656             3        53.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.792430    0.009068    0.000000  100/100  2024-06-24 13:12:52.654796  2024-06-24 13:12:48.138656
A          al_loss    false   0.792430    0.009068    0.000000  100/100  2024-06-24 13:12:49.193261  2024-06-24 13:12:40.110826
A          al_jitter  false   0.792430    0.009068    0.000000  100/100  2024-06-24 13:12:48.891017  2024-06-24 13:12:40.728174

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-24 13:12:48.891017  2024-06-24 13:12:40.728174             2        33.88
al_loss    false   2024-06-24 13:13:01.249747  2024-06-24 13:12:56.747958             4        56.40
al_rtt     false   2024-06-24 13:13:00.750873  2024-06-24 13:12:52.654796             4        60.90

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.000440    0.000058    0.000000  100/100  2024-06-24 13:13:00.750873  2024-06-24 13:12:52.654796
A          al_loss    false   0.000440    0.000058    0.000000  100/100  2024-06-24 13:13:01.249747  2024-06-24 13:12:56.747958
A          al_jitter  false   0.000440    0.000058    0.000000  100/100  2024-06-24 13:12:48.891017  2024-06-24 13:12:40.728174

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-24 13:13:04.809607  2024-06-24 13:12:48.891017             3        36.69
al_loss    false   2024-06-24 13:13:01.249747  2024-06-24 13:12:56.747958             4        44.97
al_rtt     true    2024-06-24 13:13:07.376335  2024-06-24 13:13:00.750873             5        49.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.228698    0.338815    0.000000  100/100  2024-06-24 13:13:07.376335  2024-06-24 13:13:00.750873
A          al_loss    false   0.228698    0.338815    0.000000  100/100  2024-06-24 13:13:01.249747  2024-06-24 13:12:56.747958
A          al_jitter  true    0.228698    0.338815    0.000000  100/100  2024-06-24 13:13:04.809607  2024-06-24 13:12:48.891017

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-24 13:13:12.641085  2024-06-24 13:13:04.809607             4        44.19
al_loss    false   2024-06-24 13:13:13.118597  2024-06-24 13:13:09.414584             6        47.77
al_rtt     false   2024-06-24 13:13:11.430167  2024-06-24 13:13:07.376335             6        51.74

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.000453    0.000071    0.000000  100/100  2024-06-24 13:13:11.430167  2024-06-24 13:13:07.376335
A          al_loss    false   0.000453    0.000071    0.000000  100/100  2024-06-24 13:13:13.118597  2024-06-24 13:13:09.414584
A          al_jitter  false   0.000453    0.000071    0.000000  100/100  2024-06-24 13:13:12.641085  2024-06-24 13:13:04.809607

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.000038    0.000004    0.000000  9/100
A          al_loss    false   0.000038    0.000004    0.000000  9/100
A          al_jitter  false   0.000038    0.000004    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-24 13:13:27.300749                           1        46.40
al_loss    true    2024-06-24 13:13:26.406434                           1        60.27
al_rtt     true    2024-06-24 13:13:27.802419                           1        38.55

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.410241    0.379875    41.000000  100/100  2024-06-24 13:13:27.802419
A          al_loss    true    0.410241    0.379875    41.000000  100/100  2024-06-24 13:13:26.406434
A          al_jitter  true    0.410241    0.379875    41.000000  100/100  2024-06-24 13:13:27.300749

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-24 13:13:35.674821  2024-06-24 13:13:27.300749             2        67.82
al_loss    false   2024-06-24 13:13:35.622555  2024-06-24 13:13:26.406434             2        74.59
al_rtt     false   2024-06-24 13:13:34.920600  2024-06-24 13:13:27.802419             2        57.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.000409    0.000115    0.000000  100/100  2024-06-24 13:13:34.920600  2024-06-24 13:13:27.802419
A          al_loss    false   0.000409    0.000115    0.000000  100/100  2024-06-24 13:13:35.622555  2024-06-24 13:13:26.406434
A          al_jitter  false   0.000409    0.000115    0.000000  100/100  2024-06-24 13:13:35.674821  2024-06-24 13:13:27.300749

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-24 13:13:35.674821  2024-06-24 13:13:27.300749             2        45.46
al_loss    false   2024-06-24 13:13:35.622555  2024-06-24 13:13:26.406434             2        50.01
al_rtt     true    2024-06-24 13:13:39.126181  2024-06-24 13:13:34.920600             3        55.77

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

(al_rtt)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.792394    0.009053    0.000000  100/100  2024-06-24 13:13:39.126181  2024-06-24 13:13:34.920600
A          al_loss    false   0.792394    0.009053    0.000000  100/100  2024-06-24 13:13:35.622555  2024-06-24 13:13:26.406434
A          al_jitter  false   0.792394    0.009053    0.000000  100/100  2024-06-24 13:13:35.674821  2024-06-24 13:13:27.300749

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-24 13:13:35.674821  2024-06-24 13:13:27.300749             2        34.48
al_loss    false   2024-06-24 13:13:47.844781  2024-06-24 13:13:43.328330             4        56.53
al_rtt     false   2024-06-24 13:13:47.355510  2024-06-24 13:13:39.126181             4        63.19

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.000403    0.000055    0.000000  100/100  2024-06-24 13:13:47.355510  2024-06-24 13:13:39.126181
A          al_loss    false   0.000403    0.000055    0.000000  100/100  2024-06-24 13:13:47.844781  2024-06-24 13:13:43.328330
A          al_jitter  false   0.000403    0.000055    0.000000  100/100  2024-06-24 13:13:35.674821  2024-06-24 13:13:27.300749

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-24 13:13:52.023140  2024-06-24 13:13:35.674821             3        34.69
al_loss    false   2024-06-24 13:13:47.844781  2024-06-24 13:13:43.328330             4        45.31
al_rtt     false   2024-06-24 13:13:47.355510  2024-06-24 13:13:39.126181             4        50.65

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.188083    0.304818    0.000000  100/100  2024-06-24 13:13:47.355510  2024-06-24 13:13:39.126181
A          al_loss    false   0.188083    0.304818    0.000000  100/100  2024-06-24 13:13:47.844781  2024-06-24 13:13:43.328330
A          al_jitter  true    0.188083    0.304818    0.000000  100/100  2024-06-24 13:13:52.023140  2024-06-24 13:13:35.674821

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-24 13:13:59.232138  2024-06-24 13:13:52.023140             4        43.25
al_loss    false   2024-06-24 13:13:59.361950  2024-06-24 13:13:55.361259             6        49.21
al_rtt     false   2024-06-24 13:13:57.878185  2024-06-24 13:13:54.950630             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.000409    0.000045    0.000000  100/100  2024-06-24 13:13:57.878185  2024-06-24 13:13:54.950630
A          al_loss    false   0.000409    0.000045    0.000000  100/100  2024-06-24 13:13:59.361950  2024-06-24 13:13:55.361259
A          al_jitter  false   0.000409    0.000045    0.000000  100/100  2024-06-24 13:13:59.232138  2024-06-24 13:13:52.023140

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-24 13:14:16.598617  2024-06-24 13:14:11.487901             2        73.04
al_rtt     false   2024-06-24 13:14:16.246740  2024-06-24 13:14:12.245311             2        57.21

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.000434    0.000473    0.000000  100/100  2024-06-24 13:14:16.246740  2024-06-24 13:14:12.245311
A          al_loss    false   0.000434    0.000473    0.000000  100/100  2024-06-24 13:14:16.598617  2024-06-24 13:14:11.487901
A          al_jitter  false   0.000434    0.000473    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-24 13:14:20.002644                                         1        24.49
al_loss    true    2024-06-24 13:14:19.301615  2024-06-24 13:14:16.598617             3        69.12
al_rtt     true    2024-06-24 13:14:21.414402  2024-06-24 13:14:16.246740             3        44.39

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.380277    0.449842    38.000000  100/100  2024-06-24 13:14:21.414402  2024-06-24 13:14:16.246740
A          al_loss    true    0.380277    0.449842    38.000000  100/100  2024-06-24 13:14:19.301615  2024-06-24 13:14:16.598617
A          al_jitter  true    0.380277    0.449842    38.000000  100/100  2024-06-24 13:14:20.002644

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-24 13:14:28.486321  2024-06-24 13:14:20.002644             2        45.20
al_loss    false   2024-06-24 13:14:28.440392  2024-06-24 13:14:19.301615             4        75.93
al_rtt     false   2024-06-24 13:14:27.269450  2024-06-24 13:14:21.414402             4        52.53

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.000427    0.000052    0.000000  100/100  2024-06-24 13:14:27.269450  2024-06-24 13:14:21.414402
A          al_loss    false   0.000427    0.000052    0.000000  100/100  2024-06-24 13:14:28.440392  2024-06-24 13:14:19.301615
A          al_jitter  false   0.000427    0.000052    0.000000  100/100  2024-06-24 13:14:28.486321  2024-06-24 13:14:20.002644

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-24 13:14:28.486321  2024-06-24 13:14:20.002644             2        34.34
al_loss    false   2024-06-24 13:14:28.440392  2024-06-24 13:14:19.301615             4        57.69
al_rtt     true    2024-06-24 13:14:31.731022  2024-06-24 13:14:27.269450             5        52.62

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.792472    0.009053    0.000000  100/100  2024-06-24 13:14:31.731022  2024-06-24 13:14:27.269450
A          al_loss    false   0.792472    0.009053    0.000000  100/100  2024-06-24 13:14:28.440392  2024-06-24 13:14:19.301615
A          al_jitter  false   0.792472    0.009053    0.000000  100/100  2024-06-24 13:14:28.486321  2024-06-24 13:14:20.002644

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-24 13:14:28.486321  2024-06-24 13:14:20.002644             2        27.87
al_loss    false   2024-06-24 13:14:40.301931  2024-06-24 13:14:35.782726             6        61.66
al_rtt     false   2024-06-24 13:14:39.804811  2024-06-24 13:14:31.731022             6        58.92

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.000425    0.000053    0.000000  100/100  2024-06-24 13:14:39.804811  2024-06-24 13:14:31.731022
A          al_loss    false   0.000425    0.000053    0.000000  100/100  2024-06-24 13:14:40.301931  2024-06-24 13:14:35.782726
A          al_jitter  false   0.000425    0.000053    0.000000  100/100  2024-06-24 13:14:28.486321  2024-06-24 13:14:20.002644

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-24 13:14:43.734745  2024-06-24 13:14:28.486321             3        30.92
al_loss    false   2024-06-24 13:14:40.301931  2024-06-24 13:14:35.782726             6        51.69
al_rtt     true    2024-06-24 13:14:45.979224  2024-06-24 13:14:39.804811             7        50.76

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.237269    0.328201    0.000000  100/100  2024-06-24 13:14:45.979224  2024-06-24 13:14:39.804811
A          al_loss    false   0.237269    0.328201    0.000000  100/100  2024-06-24 13:14:40.301931  2024-06-24 13:14:35.782726
A          al_jitter  true    0.237269    0.328201    0.000000  100/100  2024-06-24 13:14:43.734745  2024-06-24 13:14:28.486321

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-24 13:14:51.266738  2024-06-24 13:14:43.734745             4        38.10
al_loss    false   2024-06-24 13:14:51.670571  2024-06-24 13:14:47.856775             8        53.73
al_rtt     false   2024-06-24 13:14:49.470842  2024-06-24 13:14:45.979224             8        50.97

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.000049    0.000000  100/100  2024-06-24 13:14:49.470842  2024-06-24 13:14:45.979224
A          al_loss    false   0.000427    0.000049    0.000000  100/100  2024-06-24 13:14:51.670571  2024-06-24 13:14:47.856775
A          al_jitter  false   0.000427    0.000049    0.000000  100/100  2024-06-24 13:14:51.266738  2024-06-24 13:14:43.734745

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-24 13:15:09.221974  2024-06-24 13:15:03.800740             2        77.53
al_rtt     false   2024-06-24 13:15:08.712012  2024-06-24 13:15:04.562865             2        59.37

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.001789    0.001490    0.000000  100/100  2024-06-24 13:15:08.712012  2024-06-24 13:15:04.562865
A          al_loss    false   0.001789    0.001490    0.000000  100/100  2024-06-24 13:15:09.221974  2024-06-24 13:15:03.800740
A          al_jitter  false   0.001789    0.001490    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-24 13:15:12.065508                                         1        25.41
al_loss    true    2024-06-24 13:15:11.766802  2024-06-24 13:15:09.221974             3        69.79
al_rtt     true    2024-06-24 13:15:13.176068  2024-06-24 13:15:08.712012             3        48.99

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.420258    0.399847    42.000000  100/100  2024-06-24 13:15:13.176068  2024-06-24 13:15:08.712012
A          al_loss    true    0.420258    0.399847    42.000000  100/100  2024-06-24 13:15:11.766802  2024-06-24 13:15:09.221974
A          al_jitter  true    0.420258    0.399847    42.000000  100/100  2024-06-24 13:15:12.065508

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-24 13:15:20.504614  2024-06-24 13:15:12.065508             2        45.24
al_loss    false   2024-06-24 13:15:20.703833  2024-06-24 13:15:11.766802             4        76.95
al_rtt     false   2024-06-24 13:15:19.683012  2024-06-24 13:15:13.176068             4        57.12

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.000420    0.000063    0.000000  100/100  2024-06-24 13:15:19.683012  2024-06-24 13:15:13.176068
A          al_loss    false   0.000420    0.000063    0.000000  100/100  2024-06-24 13:15:20.703833  2024-06-24 13:15:11.766802
A          al_jitter  false   0.000420    0.000063    0.000000  100/100  2024-06-24 13:15:20.504614  2024-06-24 13:15:12.065508

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-24 13:15:20.504614  2024-06-24 13:15:12.065508             2        34.19
al_loss    false   2024-06-24 13:15:20.703833  2024-06-24 13:15:11.766802             4        58.15
al_rtt     true    2024-06-24 13:15:23.940364  2024-06-24 13:15:19.683012             5        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.810561    0.009248    0.000000  100/100  2024-06-24 13:15:23.940364  2024-06-24 13:15:19.683012
A          al_loss    false   0.810561    0.009248    0.000000  100/100  2024-06-24 13:15:20.703833  2024-06-24 13:15:11.766802
A          al_jitter  false   0.810561    0.009248    0.000000  100/100  2024-06-24 13:15:20.504614  2024-06-24 13:15:12.065508

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-24 13:15:20.504614  2024-06-24 13:15:12.065508             2        27.58
al_loss    false   2024-06-24 13:15:32.664967  2024-06-24 13:15:28.156944             6        61.64
al_rtt     false   2024-06-24 13:15:32.175639  2024-06-24 13:15:23.940364             6        61.73

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.000401    0.000077    0.000000  100/100  2024-06-24 13:15:32.175639  2024-06-24 13:15:23.940364
A          al_loss    false   0.000401    0.000077    0.000000  100/100  2024-06-24 13:15:32.664967  2024-06-24 13:15:28.156944
A          al_jitter  false   0.000401    0.000077    0.000000  100/100  2024-06-24 13:15:20.504614  2024-06-24 13:15:12.065508

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-24 13:15:35.941757  2024-06-24 13:15:20.504614             3        31.88
al_loss    false   2024-06-24 13:15:32.664967  2024-06-24 13:15:28.156944             6        51.31
al_rtt     true    2024-06-24 13:15:38.138973  2024-06-24 13:15:32.175639             7        54.33

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.244593    0.339771    0.000000  100/100  2024-06-24 13:15:38.138973  2024-06-24 13:15:32.175639
A          al_loss    false   0.244593    0.339771    0.000000  100/100  2024-06-24 13:15:32.664967  2024-06-24 13:15:28.156944
A          al_jitter  true    0.244593    0.339771    0.000000  100/100  2024-06-24 13:15:35.941757  2024-06-24 13:15:20.504614

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-24 13:15:44.182190  2024-06-24 13:15:35.941757             4        39.18
al_loss    false   2024-06-24 13:15:32.664967  2024-06-24 13:15:28.156944             6        44.31
al_rtt     false   2024-06-24 13:15:41.732088  2024-06-24 13:15:38.138973             8        52.81

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000431    0.000060    0.000000  100/100  2024-06-24 13:15:41.732088  2024-06-24 13:15:38.138973
A          al_loss    false   0.000431    0.000060    0.000000  100/100  2024-06-24 13:15:32.664967  2024-06-24 13:15:28.156944
A          al_jitter  false   0.000431    0.000060    0.000000  100/100  2024-06-24 13:15:44.182190  2024-06-24 13:15:35.941757

Note

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