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.000041    0.000019    0.000000  8/100
A          al_loss    false   0.000041    0.000019    0.000000  8/100
A          al_jitter  false   0.000041    0.000019    0.000000  8/100

Note

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

Note

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

Step 5: Set the following configuration in DUT0:

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

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

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------
  Alarm    Status           Toggled            Prev-toggled  Toggle-count  Time up (%)
--------------------------------------------------------------------------------------
al_jitter  true    2024-05-22 08:31:04.075349                           1        52.80
al_loss    true    2024-05-22 08:31:03.770065                           1        57.64
al_rtt     true    2024-05-22 08:31:05.325510                           1        33.18

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.420248    0.459817    42.000000  100/100  2024-05-22 08:31:05.325510
A          al_loss    true    0.420248    0.459817    42.000000  100/100  2024-05-22 08:31:03.770065
A          al_jitter  true    0.420248    0.459817    42.000000  100/100  2024-05-22 08:31:04.075349

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-05-22 08:31:12.544884  2024-05-22 08:31:04.075349             2        69.97
al_loss    false   2024-05-22 08:31:12.485845  2024-05-22 08:31:03.770065             2        72.04
al_rtt     false   2024-05-22 08:31:11.390771  2024-05-22 08:31:05.325510             2        50.15

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.000408    0.000056    0.000000  100/100  2024-05-22 08:31:11.390771  2024-05-22 08:31:05.325510
A          al_loss    false   0.000408    0.000056    0.000000  100/100  2024-05-22 08:31:12.485845  2024-05-22 08:31:03.770065
A          al_jitter  false   0.000408    0.000056    0.000000  100/100  2024-05-22 08:31:12.544884  2024-05-22 08:31:04.075349

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-05-22 08:31:12.544884  2024-05-22 08:31:04.075349             2        47.16
al_loss    false   2024-05-22 08:31:12.485845  2024-05-22 08:31:03.770065             2        48.55
al_rtt     true    2024-05-22 08:31:15.896345  2024-05-22 08:31:11.390771             3        51.25

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.792433    0.009059    0.000000  100/100  2024-05-22 08:31:15.896345  2024-05-22 08:31:11.390771
A          al_loss    false   0.792433    0.009059    0.000000  100/100  2024-05-22 08:31:12.485845  2024-05-22 08:31:03.770065
A          al_jitter  false   0.792433    0.009059    0.000000  100/100  2024-05-22 08:31:12.544884  2024-05-22 08:31:04.075349

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-05-22 08:31:12.544884  2024-05-22 08:31:04.075349             2        35.68
al_loss    false   2024-05-22 08:31:24.461194  2024-05-22 08:31:19.948666             4        55.73
al_rtt     false   2024-05-22 08:31:23.977519  2024-05-22 08:31:15.896345             4        59.61

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.000424    0.000056    0.000000  100/100  2024-05-22 08:31:23.977519  2024-05-22 08:31:15.896345
A          al_loss    false   0.000424    0.000056    0.000000  100/100  2024-05-22 08:31:24.461194  2024-05-22 08:31:19.948666
A          al_jitter  false   0.000424    0.000056    0.000000  100/100  2024-05-22 08:31:12.544884  2024-05-22 08:31:04.075349

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-05-22 08:31:27.777389  2024-05-22 08:31:12.544884             3        38.68
al_loss    false   2024-05-22 08:31:24.461194  2024-05-22 08:31:19.948666             4        44.49
al_rtt     true    2024-05-22 08:31:30.112650  2024-05-22 08:31:23.977519             5        49.93

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

(al_jitter)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.200025    0.284625    0.000000  100/100  2024-05-22 08:31:30.112650  2024-05-22 08:31:23.977519
A          al_loss    false   0.200025    0.284625    0.000000  100/100  2024-05-22 08:31:24.461194  2024-05-22 08:31:19.948666
A          al_jitter  true    0.200025    0.284625    0.000000  100/100  2024-05-22 08:31:27.777389  2024-05-22 08:31:12.544884

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-05-22 08:31:35.668043  2024-05-22 08:31:27.777389             4        45.83
al_loss    false   2024-05-22 08:31:36.214213  2024-05-22 08:31:32.486947             6        47.50
al_rtt     false   2024-05-22 08:31:33.692873  2024-05-22 08:31:30.112650             6        49.66

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.000564    0.000376    0.000000  100/100  2024-05-22 08:31:33.692873  2024-05-22 08:31:30.112650
A          al_loss    false   0.000564    0.000376    0.000000  100/100  2024-05-22 08:31:36.214213  2024-05-22 08:31:32.486947
A          al_jitter  false   0.000564    0.000376    0.000000  100/100  2024-05-22 08:31:35.668043  2024-05-22 08:31:27.777389

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.000089    0.000054    0.000000  13/100
A          al_loss    false   0.000089    0.000054    0.000000  13/100
A          al_jitter  false   0.000089    0.000054    0.000000  13/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-05-22 08:31:52.751671                           1        50.81
al_loss    true    2024-05-22 08:31:52.383800                           1        56.23
al_rtt     true    2024-05-22 08:31:53.786189                           1        35.09

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.440249    0.459802    44.000000  100/100  2024-05-22 08:31:53.786189
A          al_loss    true    0.440249    0.459802    44.000000  100/100  2024-05-22 08:31:52.383800
A          al_jitter  true    0.440249    0.459802    44.000000  100/100  2024-05-22 08:31:52.751671

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-05-22 08:32:01.155118  2024-05-22 08:31:52.751671             2        67.74
al_loss    false   2024-05-22 08:32:01.505091  2024-05-22 08:31:52.383800             2        73.43
al_rtt     false   2024-05-22 08:32:00.661481  2024-05-22 08:31:53.786189             2        55.38

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.000438    0.000067    0.000000  100/100  2024-05-22 08:32:00.661481  2024-05-22 08:31:53.786189
A          al_loss    false   0.000438    0.000067    0.000000  100/100  2024-05-22 08:32:01.505091  2024-05-22 08:31:52.383800
A          al_jitter  false   0.000438    0.000067    0.000000  100/100  2024-05-22 08:32:01.155118  2024-05-22 08:31:52.751671

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-05-22 08:32:01.155118  2024-05-22 08:31:52.751671             2        45.30
al_loss    false   2024-05-22 08:32:01.505091  2024-05-22 08:31:52.383800             2        49.13
al_rtt     true    2024-05-22 08:32:04.866090  2024-05-22 08:32:00.661481             3        54.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.801486    0.009090    0.000000  100/100  2024-05-22 08:32:04.866090  2024-05-22 08:32:00.661481
A          al_loss    false   0.801486    0.009090    0.000000  100/100  2024-05-22 08:32:01.505091  2024-05-22 08:31:52.383800
A          al_jitter  false   0.801486    0.009090    0.000000  100/100  2024-05-22 08:32:01.155118  2024-05-22 08:31:52.751671

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-05-22 08:32:01.155118  2024-05-22 08:31:52.751671             2        34.15
al_loss    false   2024-05-22 08:32:13.729392  2024-05-22 08:32:09.226600             4        55.33
al_rtt     false   2024-05-22 08:32:13.224317  2024-05-22 08:32:04.866090             4        61.89

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.000456    0.000054    0.000000  100/100  2024-05-22 08:32:13.224317  2024-05-22 08:32:04.866090
A          al_loss    false   0.000456    0.000054    0.000000  100/100  2024-05-22 08:32:13.729392  2024-05-22 08:32:09.226600
A          al_jitter  false   0.000456    0.000054    0.000000  100/100  2024-05-22 08:32:01.155118  2024-05-22 08:31:52.751671

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-05-22 08:32:17.547368  2024-05-22 08:32:01.155118             3        35.72
al_loss    false   2024-05-22 08:32:13.729392  2024-05-22 08:32:09.226600             4        44.57
al_rtt     false   2024-05-22 08:32:13.224317  2024-05-22 08:32:04.866090             4        49.84

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.192699    0.275703    0.000000  100/100  2024-05-22 08:32:13.224317  2024-05-22 08:32:04.866090
A          al_loss    false   0.192699    0.275703    0.000000  100/100  2024-05-22 08:32:13.729392  2024-05-22 08:32:09.226600
A          al_jitter  true    0.192699    0.275703    0.000000  100/100  2024-05-22 08:32:17.547368  2024-05-22 08:32:01.155118

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-05-22 08:32:25.052720  2024-05-22 08:32:17.547368             4        43.85
al_loss    false   2024-05-22 08:32:25.251469  2024-05-22 08:32:21.338806             6        48.31
al_rtt     false   2024-05-22 08:32:23.542394  2024-05-22 08:32:20.453953             6        50.49

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.000433    0.000056    0.000000  100/100  2024-05-22 08:32:23.542394  2024-05-22 08:32:20.453953
A          al_loss    false   0.000433    0.000056    0.000000  100/100  2024-05-22 08:32:25.251469  2024-05-22 08:32:21.338806
A          al_jitter  false   0.000433    0.000056    0.000000  100/100  2024-05-22 08:32:25.052720  2024-05-22 08:32:17.547368

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-05-22 08:32:41.982757  2024-05-22 08:32:36.576085             2        77.86
al_rtt     false   2024-05-22 08:32:41.491150  2024-05-22 08:32:37.332895             2        59.91

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.002010    0.001617    0.000000  100/100  2024-05-22 08:32:41.491150  2024-05-22 08:32:37.332895
A          al_loss    false   0.002010    0.001617    0.000000  100/100  2024-05-22 08:32:41.982757  2024-05-22 08:32:36.576085
A          al_jitter  false   0.002010    0.001617    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-05-22 08:32:45.437808                                         1        20.83
al_loss    true    2024-05-22 08:32:44.236021  2024-05-22 08:32:41.982757             3        72.17
al_rtt     true    2024-05-22 08:32:46.246277  2024-05-22 08:32:41.491150             3        46.87

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.370302    0.419877    37.000000  100/100  2024-05-22 08:32:46.246277  2024-05-22 08:32:41.491150
A          al_loss    true    0.370302    0.419877    37.000000  100/100  2024-05-22 08:32:44.236021  2024-05-22 08:32:41.982757
A          al_jitter  true    0.370302    0.419877    37.000000  100/100  2024-05-22 08:32:45.437808

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-05-22 08:32:53.169694  2024-05-22 08:32:45.437808             2        41.42
al_loss    false   2024-05-22 08:32:53.356699  2024-05-22 08:32:44.236021             4        77.85
al_rtt     false   2024-05-22 08:32:51.802185  2024-05-22 08:32:46.246277             4        52.07

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.000438    0.000051    0.000000  100/100  2024-05-22 08:32:51.802185  2024-05-22 08:32:46.246277
A          al_loss    false   0.000438    0.000051    0.000000  100/100  2024-05-22 08:32:53.356699  2024-05-22 08:32:44.236021
A          al_jitter  false   0.000438    0.000051    0.000000  100/100  2024-05-22 08:32:53.169694  2024-05-22 08:32:45.437808

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-05-22 08:32:53.169694  2024-05-22 08:32:45.437808             2        31.42
al_loss    false   2024-05-22 08:32:53.356699  2024-05-22 08:32:44.236021             4        59.06
al_rtt     true    2024-05-22 08:32:56.710635  2024-05-22 08:32:51.802185             5        52.24

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.783464    0.009067    0.000000  100/100  2024-05-22 08:32:56.710635  2024-05-22 08:32:51.802185
A          al_loss    false   0.783464    0.009067    0.000000  100/100  2024-05-22 08:32:53.356699  2024-05-22 08:32:44.236021
A          al_jitter  false   0.783464    0.009067    0.000000  100/100  2024-05-22 08:32:53.169694  2024-05-22 08:32:45.437808

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-05-22 08:32:53.169694  2024-05-22 08:32:45.437808             2        25.41
al_loss    false   2024-05-22 08:33:05.277704  2024-05-22 08:33:00.768876             6        62.58
al_rtt     false   2024-05-22 08:33:04.787422  2024-05-22 08:32:56.710635             6        58.49

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.000415    0.000068    0.000000  100/100  2024-05-22 08:33:04.787422  2024-05-22 08:32:56.710635
A          al_loss    false   0.000415    0.000068    0.000000  100/100  2024-05-22 08:33:05.277704  2024-05-22 08:33:00.768876
A          al_jitter  false   0.000415    0.000068    0.000000  100/100  2024-05-22 08:32:53.169694  2024-05-22 08:32:45.437808

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-05-22 08:33:08.512847  2024-05-22 08:32:53.169694             3        29.80
al_loss    false   2024-05-22 08:33:05.277704  2024-05-22 08:33:00.768876             6        52.33
al_rtt     false   2024-05-22 08:33:04.787422  2024-05-22 08:32:56.710635             6        48.91

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.199286    0.305147    0.000000  100/100  2024-05-22 08:33:04.787422  2024-05-22 08:32:56.710635
A          al_loss    false   0.199286    0.305147    0.000000  100/100  2024-05-22 08:33:05.277704  2024-05-22 08:33:00.768876
A          al_jitter  true    0.199286    0.305147    0.000000  100/100  2024-05-22 08:33:08.512847  2024-05-22 08:32:53.169694

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-05-22 08:33:16.448583  2024-05-22 08:33:08.512847             4        37.14
al_loss    false   2024-05-22 08:33:05.277704  2024-05-22 08:33:00.768876             6        45.13
al_rtt     false   2024-05-22 08:33:13.962878  2024-05-22 08:33:12.790886             8        44.96

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000407    0.000053    0.000000  100/100  2024-05-22 08:33:13.962878  2024-05-22 08:33:12.790886
A          al_loss    false   0.000407    0.000053    0.000000  100/100  2024-05-22 08:33:05.277704  2024-05-22 08:33:00.768876
A          al_jitter  false   0.000407    0.000053    0.000000  100/100  2024-05-22 08:33:16.448583  2024-05-22 08:33:08.512847

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-05-22 08:33:34.218394  2024-05-22 08:33:28.778444             2        76.76
al_rtt     false   2024-05-22 08:33:33.723799  2024-05-22 08:33:29.514340             2        59.44

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.000477    0.000121    0.000000  100/100  2024-05-22 08:33:33.723799  2024-05-22 08:33:29.514340
A          al_loss    false   0.000477    0.000121    0.000000  100/100  2024-05-22 08:33:34.218394  2024-05-22 08:33:28.778444
A          al_jitter  false   0.000477    0.000121    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-05-22 08:33:37.021032                                         1        26.80
al_loss    true    2024-05-22 08:33:36.921274  2024-05-22 08:33:34.218394             3        68.96
al_rtt     true    2024-05-22 08:33:38.474197  2024-05-22 08:33:33.723799             3        47.79

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.440254    0.519775    44.000000  100/100  2024-05-22 08:33:38.474197  2024-05-22 08:33:33.723799
A          al_loss    true    0.440254    0.519775    44.000000  100/100  2024-05-22 08:33:36.921274  2024-05-22 08:33:34.218394
A          al_jitter  true    0.440254    0.519775    44.000000  100/100  2024-05-22 08:33:37.021032

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-05-22 08:33:45.890286  2024-05-22 08:33:37.021032             2        46.86
al_loss    false   2024-05-22 08:33:45.842082  2024-05-22 08:33:36.921274             4        75.85
al_rtt     false   2024-05-22 08:33:44.987940  2024-05-22 08:33:38.474197             4        56.65

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.000440    0.000053    0.000000  100/100  2024-05-22 08:33:44.987940  2024-05-22 08:33:38.474197
A          al_loss    false   0.000440    0.000053    0.000000  100/100  2024-05-22 08:33:45.842082  2024-05-22 08:33:36.921274
A          al_jitter  false   0.000440    0.000053    0.000000  100/100  2024-05-22 08:33:45.890286  2024-05-22 08:33:37.021032

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-05-22 08:33:45.890286  2024-05-22 08:33:37.021032             2        35.72
al_loss    false   2024-05-22 08:33:45.842082  2024-05-22 08:33:36.921274             4        57.82
al_rtt     true    2024-05-22 08:33:49.095327  2024-05-22 08:33:44.987940             5        55.85

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.792455    0.009056    0.000000  100/100  2024-05-22 08:33:49.095327  2024-05-22 08:33:44.987940
A          al_loss    false   0.792455    0.009056    0.000000  100/100  2024-05-22 08:33:45.842082  2024-05-22 08:33:36.921274
A          al_jitter  false   0.792455    0.009056    0.000000  100/100  2024-05-22 08:33:45.890286  2024-05-22 08:33:37.021032

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-05-22 08:33:45.890286  2024-05-22 08:33:37.021032             2        28.98
al_loss    false   2024-05-22 08:33:57.665394  2024-05-22 08:33:53.152660             6        61.65
al_rtt     false   2024-05-22 08:33:57.183721  2024-05-22 08:33:49.095327             6        61.46

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000440    0.000064    0.000000  100/100  2024-05-22 08:33:57.183721  2024-05-22 08:33:49.095327
A          al_loss    false   0.000440    0.000064    0.000000  100/100  2024-05-22 08:33:57.665394  2024-05-22 08:33:53.152660
A          al_jitter  false   0.000440    0.000064    0.000000  100/100  2024-05-22 08:33:45.890286  2024-05-22 08:33:37.021032

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-05-22 08:34:01.100991  2024-05-22 08:33:45.890286             3        31.97
al_loss    false   2024-05-22 08:33:57.665394  2024-05-22 08:33:53.152660             6        51.72
al_rtt     true    2024-05-22 08:34:03.570109  2024-05-22 08:33:57.183721             7        52.45

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

(al_jitter)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.227270    0.320942    0.000000  100/100  2024-05-22 08:34:03.570109  2024-05-22 08:33:57.183721
A          al_loss    false   0.227270    0.320942    0.000000  100/100  2024-05-22 08:33:57.665394  2024-05-22 08:33:53.152660
A          al_jitter  true    0.227270    0.320942    0.000000  100/100  2024-05-22 08:34:01.100991  2024-05-22 08:33:45.890286

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-05-22 08:34:08.644312  2024-05-22 08:34:01.100991             4        38.84
al_loss    false   2024-05-22 08:34:09.244360  2024-05-22 08:34:05.383799             8        53.79
al_rtt     false   2024-05-22 08:34:06.832723  2024-05-22 08:34:03.570109             8        52.24

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.000438    0.000057    0.000000  100/100  2024-05-22 08:34:06.832723  2024-05-22 08:34:03.570109
A          al_loss    false   0.000438    0.000057    0.000000  100/100  2024-05-22 08:34:09.244360  2024-05-22 08:34:05.383799
A          al_jitter  false   0.000438    0.000057    0.000000  100/100  2024-05-22 08:34:08.644312  2024-05-22 08:34:01.100991

Note

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