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.000007    0.000000  10/100
A          al_loss    false   0.000042    0.000007    0.000000  10/100
A          al_jitter  false   0.000042    0.000007    0.000000  10/100

Note

The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.

Note

If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.

Step 5: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out PLOSS
set traffic control PLOSS type network-emulator packet-loss 50

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

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------
  Alarm    Status           Toggled            Prev-toggled  Toggle-count  Time up (%)
--------------------------------------------------------------------------------------
al_jitter  true    2024-04-09 09:27:42.309644                           1        56.06
al_loss    true    2024-04-09 09:27:41.998037                           1        60.99
al_rtt     true    2024-04-09 09:27:43.512292                           1        37.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.400272    0.499796    40.000000  100/100  2024-04-09 09:27:43.512292
A          al_loss    true    0.400272    0.499796    40.000000  100/100  2024-04-09 09:27:41.998037
A          al_jitter  true    0.400272    0.499796    40.000000  100/100  2024-04-09 09:27:42.309644

Note

The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.

Note

If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.

Step 8: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:27:50.778417  2024-04-09 09:27:42.309644             2        69.57
al_loss    false   2024-04-09 09:27:51.167581  2024-04-09 09:27:41.998037             2        75.36
al_rtt     false   2024-04-09 09:27:50.183008  2024-04-09 09:27:43.512292             2        54.84

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.000435    0.000057    0.000000  100/100  2024-04-09 09:27:50.183008  2024-04-09 09:27:43.512292
A          al_loss    false   0.000435    0.000057    0.000000  100/100  2024-04-09 09:27:51.167581  2024-04-09 09:27:41.998037
A          al_jitter  false   0.000435    0.000057    0.000000  100/100  2024-04-09 09:27:50.778417  2024-04-09 09:27:42.309644

Note

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

Note

If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.

Step 11: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out RTT
set traffic control RTT type network-emulator network-delay 900

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

(al_rtt)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:27:50.778417  2024-04-09 09:27:42.309644             2        46.70
al_loss    false   2024-04-09 09:27:51.167581  2024-04-09 09:27:41.998037             2        50.58
al_rtt     true    2024-04-09 09:27:54.523487  2024-04-09 09:27:50.183008             3        53.99

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.009072    0.000000  100/100  2024-04-09 09:27:54.523487  2024-04-09 09:27:50.183008
A          al_loss    false   0.792461    0.009072    0.000000  100/100  2024-04-09 09:27:51.167581  2024-04-09 09:27:41.998037
A          al_jitter  false   0.792461    0.009072    0.000000  100/100  2024-04-09 09:27:50.778417  2024-04-09 09:27:42.309644

Note

The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.

Note

If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.

Step 14: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:27:50.778417  2024-04-09 09:27:42.309644             2        35.38
al_loss    false   2024-04-09 09:28:03.101829  2024-04-09 09:27:58.582509             4        57.19
al_rtt     false   2024-04-09 09:28:02.611504  2024-04-09 09:27:54.523487             4        61.68

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.000442    0.000056    0.000000  100/100  2024-04-09 09:28:02.611504  2024-04-09 09:27:54.523487
A          al_loss    false   0.000442    0.000056    0.000000  100/100  2024-04-09 09:28:03.101829  2024-04-09 09:27:58.582509
A          al_jitter  false   0.000442    0.000056    0.000000  100/100  2024-04-09 09:27:50.778417  2024-04-09 09:27:42.309644

Note

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

Note

If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.

Step 17: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out JITTER
set traffic control JITTER type network-emulator network-delay 1 jitter 1000

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

(al_jitter)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  true    2024-04-09 09:28:07.002943  2024-04-09 09:27:50.778417             3        36.58
al_loss    false   2024-04-09 09:28:03.101829  2024-04-09 09:27:58.582509             4        45.62
al_rtt     false   2024-04-09 09:28:02.611504  2024-04-09 09:27:54.523487             4        49.20

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.164167    0.254660    0.000000  100/100  2024-04-09 09:28:02.611504  2024-04-09 09:27:54.523487
A          al_loss    false   0.164167    0.254660    0.000000  100/100  2024-04-09 09:28:03.101829  2024-04-09 09:27:58.582509
A          al_jitter  true    0.164167    0.254660    0.000000  100/100  2024-04-09 09:28:07.002943  2024-04-09 09:27:50.778417

Note

The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.

Note

If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.

Step 20: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:28:14.438040  2024-04-09 09:28:07.002943             4        44.33
al_loss    false   2024-04-09 09:28:14.871000  2024-04-09 09:28:11.121060             6        48.62
al_rtt     false   2024-04-09 09:28:02.611504  2024-04-09 09:27:54.523487             4        41.15

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.000429    0.000045    0.000000  100/100  2024-04-09 09:28:02.611504  2024-04-09 09:27:54.523487
A          al_loss    false   0.000429    0.000045    0.000000  100/100  2024-04-09 09:28:14.871000  2024-04-09 09:28:11.121060
A          al_jitter  false   0.000429    0.000045    0.000000  100/100  2024-04-09 09:28:14.438040  2024-04-09 09:28:07.002943

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.000059    0.000027    0.000000  11/100
A          al_loss    false   0.000059    0.000027    0.000000  11/100
A          al_jitter  false   0.000059    0.000027    0.000000  11/100

Note

The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.

Note

If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.

Step 5: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out PLOSS
set traffic control PLOSS type network-emulator packet-loss 50

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

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------
  Alarm    Status           Toggled            Prev-toggled  Toggle-count  Time up (%)
--------------------------------------------------------------------------------------
al_jitter  true    2024-04-09 09:28:38.842864                           1        43.07
al_loss    true    2024-04-09 09:28:38.283522                           1        51.64
al_rtt     true    2024-04-09 09:28:39.685586                           1        30.00

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.380264    0.389854    38.000000  100/100  2024-04-09 09:28:39.685586
A          al_loss    true    0.380264    0.389854    38.000000  100/100  2024-04-09 09:28:38.283522
A          al_jitter  true    0.380264    0.389854    38.000000  100/100  2024-04-09 09:28:38.842864

Note

The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.

Note

If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.

Step 8: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:28:46.594936  2024-04-09 09:28:38.842864             2        62.47
al_loss    false   2024-04-09 09:28:46.799423  2024-04-09 09:28:38.283522             2        68.57
al_rtt     false   2024-04-09 09:28:45.790298  2024-04-09 09:28:39.685586             2        49.18

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.000444    0.000053    0.000000  100/100  2024-04-09 09:28:45.790298  2024-04-09 09:28:39.685586
A          al_loss    false   0.000444    0.000053    0.000000  100/100  2024-04-09 09:28:46.799423  2024-04-09 09:28:38.283522
A          al_jitter  false   0.000444    0.000053    0.000000  100/100  2024-04-09 09:28:46.594936  2024-04-09 09:28:38.842864

Note

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

Note

If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.

Step 11: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out RTT
set traffic control RTT type network-emulator network-delay 900

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

(al_rtt)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:28:46.594936  2024-04-09 09:28:38.842864             2        41.63
al_loss    false   2024-04-09 09:28:46.799423  2024-04-09 09:28:38.283522             2        45.71
al_rtt     true    2024-04-09 09:28:50.513486  2024-04-09 09:28:45.790298             3        50.34

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.819513    0.009151    0.000000  100/100  2024-04-09 09:28:50.513486  2024-04-09 09:28:45.790298
A          al_loss    false   0.819513    0.009151    0.000000  100/100  2024-04-09 09:28:46.799423  2024-04-09 09:28:38.283522
A          al_jitter  false   0.819513    0.009151    0.000000  100/100  2024-04-09 09:28:46.594936  2024-04-09 09:28:38.842864

Note

The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.

Note

If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.

Step 14: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:28:46.594936  2024-04-09 09:28:38.842864             2        31.57
al_loss    false   2024-04-09 09:28:59.320887  2024-04-09 09:28:54.817257             4        53.00
al_rtt     false   2024-04-09 09:28:58.816958  2024-04-09 09:28:50.513486             4        58.66

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.000492    0.000114    0.000000  100/100  2024-04-09 09:28:58.816958  2024-04-09 09:28:50.513486
A          al_loss    false   0.000492    0.000114    0.000000  100/100  2024-04-09 09:28:59.320887  2024-04-09 09:28:54.817257
A          al_jitter  false   0.000492    0.000114    0.000000  100/100  2024-04-09 09:28:46.594936  2024-04-09 09:28:38.842864

Note

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

Note

If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.

Step 17: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out JITTER
set traffic control JITTER type network-emulator network-delay 1 jitter 1000

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

(al_jitter)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  true    2024-04-09 09:29:03.327511  2024-04-09 09:28:46.594936             3        34.03
al_loss    false   2024-04-09 09:28:59.320887  2024-04-09 09:28:54.817257             4        42.06
al_rtt     true    2024-04-09 09:29:06.024029  2024-04-09 09:28:58.816958             5        46.82

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.209751    0.302371    0.000000  100/100  2024-04-09 09:29:06.024029  2024-04-09 09:28:58.816958
A          al_loss    false   0.209751    0.302371    0.000000  100/100  2024-04-09 09:28:59.320887  2024-04-09 09:28:54.817257
A          al_jitter  true    0.209751    0.302371    0.000000  100/100  2024-04-09 09:29:03.327511  2024-04-09 09:28:46.594936

Note

The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.

Note

If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.

Step 20: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:29:10.715463  2024-04-09 09:29:03.327511             4        40.78
al_loss    false   2024-04-09 09:29:11.655024  2024-04-09 09:29:07.654127             6        45.83
al_rtt     false   2024-04-09 09:29:10.464387  2024-04-09 09:29:06.024029             6        50.76

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000442    0.000078    0.000000  100/100  2024-04-09 09:29:10.464387  2024-04-09 09:29:06.024029
A          al_loss    false   0.000442    0.000078    0.000000  100/100  2024-04-09 09:29:11.655024  2024-04-09 09:29:07.654127
A          al_jitter  false   0.000442    0.000078    0.000000  100/100  2024-04-09 09:29:10.715463  2024-04-09 09:29:03.327511

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-04-09 09:29:30.163640  2024-04-09 09:29:25.268800             2        66.88
al_rtt     false   2024-04-09 09:29:29.913811  2024-04-09 09:29:26.017275             2        53.27

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000408    0.000065    0.000000  100/100  2024-04-09 09:29:29.913811  2024-04-09 09:29:26.017275
A          al_loss    false   0.000408    0.000065    0.000000  100/100  2024-04-09 09:29:30.163640  2024-04-09 09:29:25.268800
A          al_jitter  false   0.000408    0.000065    0.000000  100/100

Note

The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.

Note

If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.

Step 5: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out PLOSS
set traffic control PLOSS type network-emulator packet-loss 50

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

(al_loss)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  true    2024-04-09 09:29:34.388320                                         1        22.23
al_loss    true    2024-04-09 09:29:33.546203  2024-04-09 09:29:30.163640             3        64.87
al_rtt     true    2024-04-09 09:29:35.399866  2024-04-09 09:29:29.913811             3        43.69

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.420212    0.399869    42.000000  100/100  2024-04-09 09:29:35.399866  2024-04-09 09:29:29.913811
A          al_loss    true    0.420212    0.399869    42.000000  100/100  2024-04-09 09:29:33.546203  2024-04-09 09:29:30.163640
A          al_jitter  true    0.420212    0.399869    42.000000  100/100  2024-04-09 09:29:34.388320

Note

The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.

Note

If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.

Step 8: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:29:42.098958  2024-04-09 09:29:34.388320             2        39.62
al_loss    false   2024-04-09 09:29:42.792688  2024-04-09 09:29:33.546203             4        72.67
al_rtt     false   2024-04-09 09:29:42.322909  2024-04-09 09:29:35.399866             4        55.61

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.001342    0.001926    0.000000  100/100  2024-04-09 09:29:42.322909  2024-04-09 09:29:35.399866
A          al_loss    false   0.001342    0.001926    0.000000  100/100  2024-04-09 09:29:42.792688  2024-04-09 09:29:33.546203
A          al_jitter  false   0.001342    0.001926    0.000000  100/100  2024-04-09 09:29:42.098958  2024-04-09 09:29:34.388320

Note

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

Note

If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.

Step 11: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out RTT
set traffic control RTT type network-emulator network-delay 900

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

(al_rtt)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:29:42.098958  2024-04-09 09:29:34.388320             2        29.91
al_loss    false   2024-04-09 09:29:42.792688  2024-04-09 09:29:33.546203             4        54.86
al_rtt     true    2024-04-09 09:29:46.501329  2024-04-09 09:29:42.322909             5        54.41

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.819588    0.009363    0.000000  100/100  2024-04-09 09:29:46.501329  2024-04-09 09:29:42.322909
A          al_loss    false   0.819588    0.009363    0.000000  100/100  2024-04-09 09:29:42.792688  2024-04-09 09:29:33.546203
A          al_jitter  false   0.819588    0.009363    0.000000  100/100  2024-04-09 09:29:42.098958  2024-04-09 09:29:34.388320

Note

The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.

Note

If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.

Step 14: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:29:42.098958  2024-04-09 09:29:34.388320             2        23.87
al_loss    false   2024-04-09 09:29:55.726443  2024-04-09 09:29:51.267515             6        57.60
al_rtt     false   2024-04-09 09:29:55.266225  2024-04-09 09:29:46.501329             6        60.66

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.000589    0.000207    0.000000  100/100  2024-04-09 09:29:55.266225  2024-04-09 09:29:46.501329
A          al_loss    false   0.000589    0.000207    0.000000  100/100  2024-04-09 09:29:55.726443  2024-04-09 09:29:51.267515
A          al_jitter  false   0.000589    0.000207    0.000000  100/100  2024-04-09 09:29:42.098958  2024-04-09 09:29:34.388320

Note

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

Note

If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.

Step 17: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out JITTER
set traffic control JITTER type network-emulator network-delay 1 jitter 1000

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

(al_jitter)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  true    2024-04-09 09:29:59.840419  2024-04-09 09:29:42.098958             3        27.05
al_loss    false   2024-04-09 09:29:55.726443  2024-04-09 09:29:51.267515             6        48.11
al_rtt     false   2024-04-09 09:29:55.266225  2024-04-09 09:29:46.501329             6        50.66

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.196947    0.327012    0.000000  100/100  2024-04-09 09:29:55.266225  2024-04-09 09:29:46.501329
A          al_loss    false   0.196947    0.327012    0.000000  100/100  2024-04-09 09:29:55.726443  2024-04-09 09:29:51.267515
A          al_jitter  true    0.196947    0.327012    0.000000  100/100  2024-04-09 09:29:59.840419  2024-04-09 09:29:42.098958

Note

The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.

Note

If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.

Step 20: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:30:07.726885  2024-04-09 09:29:59.840419             4        35.06
al_loss    false   2024-04-09 09:30:07.682795  2024-04-09 09:30:04.062128             8        49.96
al_rtt     false   2024-04-09 09:30:06.216831  2024-04-09 09:30:02.981950             8        51.31

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.027292    0.009946    0.000000  100/100  2024-04-09 09:30:06.216831  2024-04-09 09:30:02.981950
A          al_loss    false   0.027292    0.009946    0.000000  100/100  2024-04-09 09:30:07.682795  2024-04-09 09:30:04.062128
A          al_jitter  false   0.027292    0.009946    0.000000  100/100  2024-04-09 09:30:07.726885  2024-04-09 09:29:59.840419

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-04-09 09:30:50.641865  2024-04-09 09:30:45.682670             2        68.93
al_rtt     false   2024-04-09 09:30:50.398989  2024-04-09 09:30:46.451577             2        54.90

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.000465    0.000153    0.000000  100/100  2024-04-09 09:30:50.398989  2024-04-09 09:30:46.451577
A          al_loss    false   0.000465    0.000153    0.000000  100/100  2024-04-09 09:30:50.641865  2024-04-09 09:30:45.682670
A          al_jitter  false   0.000465    0.000153    0.000000  100/100

Note

The previous command output should show that the NSM operations have been created successfully and that the alarms are desactivated, since the network quality is good.

Note

If a packet loss rate of 50% is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said packet loss in the network and will proceed to activate the ‘al_loss’ alarm.

Step 5: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out PLOSS
set traffic control PLOSS type network-emulator packet-loss 50

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

(al_loss)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  true    2024-04-09 09:30:54.247471                                         1        23.89
al_loss    true    2024-04-09 09:30:53.800463  2024-04-09 09:30:50.641865             3        65.15
al_rtt     true    2024-04-09 09:30:55.096451  2024-04-09 09:30:50.398989             3        47.54

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.430248    0.379862    43.000000  100/100  2024-04-09 09:30:55.096451  2024-04-09 09:30:50.398989
A          al_loss    true    0.430248    0.379862    43.000000  100/100  2024-04-09 09:30:53.800463  2024-04-09 09:30:50.641865
A          al_jitter  true    0.430248    0.379862    43.000000  100/100  2024-04-09 09:30:54.247471

Note

The previous command output should show that the ‘al_loss’ alarm is activated, since there are packet losses on the network greater than the configured threshold. As there are packet losses in the network, the delay and jitter are also affected, so ‘al_rtt’ and ‘al_jitter’ alarms are also activated since the threshold configured for them is exceeded.

Note

If the packet loss emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there is no longer packet loss and will deactivate the ‘al_loss’ alarm.

Step 8: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:31:02.475662  2024-04-09 09:30:54.247471             2        43.50
al_loss    false   2024-04-09 09:31:02.823572  2024-04-09 09:30:53.800463             4        73.89
al_rtt     false   2024-04-09 09:31:01.967574  2024-04-09 09:30:55.096451             4        57.19

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000468    0.000103    0.000000  100/100  2024-04-09 09:31:01.967574  2024-04-09 09:30:55.096451
A          al_loss    false   0.000468    0.000103    0.000000  100/100  2024-04-09 09:31:02.823572  2024-04-09 09:30:53.800463
A          al_jitter  false   0.000468    0.000103    0.000000  100/100  2024-04-09 09:31:02.475662  2024-04-09 09:30:54.247471

Note

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

Note

If an additional delay of 900 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said delay in the network and will proceed to activate the ‘al_rtt’ alarm.

Step 11: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out RTT
set traffic control RTT type network-emulator network-delay 900

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

(al_rtt)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:31:02.475662  2024-04-09 09:30:54.247471             2        32.80
al_loss    false   2024-04-09 09:31:02.823572  2024-04-09 09:30:53.800463             4        55.72
al_rtt     true    2024-04-09 09:31:06.168140  2024-04-09 09:31:01.967574             5        55.88

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.810477    0.009102    0.000000  100/100  2024-04-09 09:31:06.168140  2024-04-09 09:31:01.967574
A          al_loss    false   0.810477    0.009102    0.000000  100/100  2024-04-09 09:31:02.823572  2024-04-09 09:30:53.800463
A          al_jitter  false   0.810477    0.009102    0.000000  100/100  2024-04-09 09:31:02.475662  2024-04-09 09:30:54.247471

Note

The previous command output should show that the ‘al_rtt’ alarm is activated, since there are delays on the network greater than the configured threshold.

Note

If the additional delay emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high delays and will deactivate the ‘al_rtt’ alarm.

Step 14: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:31:02.475662  2024-04-09 09:30:54.247471             2        26.46
al_loss    false   2024-04-09 09:31:14.995639  2024-04-09 09:31:10.487392             6        59.45
al_rtt     false   2024-04-09 09:31:14.492256  2024-04-09 09:31:06.168140             6        61.56

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.000076    0.000000  100/100  2024-04-09 09:31:14.492256  2024-04-09 09:31:06.168140
A          al_loss    false   0.000425    0.000076    0.000000  100/100  2024-04-09 09:31:14.995639  2024-04-09 09:31:10.487392
A          al_jitter  false   0.000425    0.000076    0.000000  100/100  2024-04-09 09:31:02.475662  2024-04-09 09:30:54.247471

Note

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

Note

If an additional jitter of 1000 ms is emulated in the network and we wait a reasonable amount of time, the NSM operation will detect said jitter in the network and will proceed to activate the ‘al_jitter’ alarm.

Step 17: Set the following configuration in DUT0:

set interfaces ethernet eth0 traffic control out JITTER
set traffic control JITTER type network-emulator network-delay 1 jitter 1000

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

(al_jitter)\s+(true)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  true    2024-04-09 09:31:18.820042  2024-04-09 09:31:02.475662             3        29.34
al_loss    false   2024-04-09 09:31:14.995639  2024-04-09 09:31:10.487392             6        49.65
al_rtt     true    2024-04-09 09:31:21.058240  2024-04-09 09:31:14.492256             7        52.64

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.242852    0.313716    0.000000  100/100  2024-04-09 09:31:21.058240  2024-04-09 09:31:14.492256
A          al_loss    false   0.242852    0.313716    0.000000  100/100  2024-04-09 09:31:14.995639  2024-04-09 09:31:10.487392
A          al_jitter  true    0.242852    0.313716    0.000000  100/100  2024-04-09 09:31:18.820042  2024-04-09 09:31:02.475662

Note

The previous command output should show that the ‘al_jitter’ alarm is activated, since there is a jitter on the network greater than the configured threshold.

Note

If the additional jitter emulated in the network is removed and we wait a reasonable amount of time, the NSM operation will detect that there are no longer high jitter and will deactivate the ‘al_jitter’ alarm.

Step 20: Set the following configuration in DUT0:

delete interfaces ethernet eth0 traffic control

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
----------------------------------------------------------------------------------------------------
  Alarm    Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
----------------------------------------------------------------------------------------------------
al_jitter  false   2024-04-09 09:31:26.529071  2024-04-09 09:31:18.820042             4        36.88
al_loss    false   2024-04-09 09:31:27.036606  2024-04-09 09:31:23.264505             8        51.51
al_rtt     false   2024-04-09 09:31:24.765244  2024-04-09 09:31:21.058240             8        52.88

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.000060    0.000000  100/100  2024-04-09 09:31:24.765244  2024-04-09 09:31:21.058240
A          al_loss    false   0.000427    0.000060    0.000000  100/100  2024-04-09 09:31:27.036606  2024-04-09 09:31:23.264505
A          al_jitter  false   0.000427    0.000060    0.000000  100/100  2024-04-09 09:31:26.529071  2024-04-09 09:31:18.820042

Note

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