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

Note

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

Note

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

Step 5: Set the following configuration in DUT0:

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

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

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------
  Alarm    Status           Toggled            Prev-toggled  Toggle-count  Time up (%)
--------------------------------------------------------------------------------------
al_jitter  true    2024-02-26 19:32:33.952282                           1        50.20
al_loss    true    2024-02-26 19:32:33.452070                           1        58.02
al_rtt     true    2024-02-26 19:32:34.755282                           1        37.81

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.420393    0.479679    42.000000  100/100  2024-02-26 19:32:34.755282
A          al_loss    true    0.420393    0.479679    42.000000  100/100  2024-02-26 19:32:33.452070
A          al_jitter  true    0.420393    0.479679    42.000000  100/100  2024-02-26 19:32:33.952282

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-02-26 19:32:42.424557  2024-02-26 19:32:33.952282             2        68.64
al_loss    false   2024-02-26 19:32:42.626275  2024-02-26 19:32:33.452070             2        74.39
al_rtt     false   2024-02-26 19:32:41.474784  2024-02-26 19:32:34.755282             2        54.46

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000714    0.000110    0.000000  100/100  2024-02-26 19:32:41.474784  2024-02-26 19:32:34.755282
A          al_loss    false   0.000714    0.000110    0.000000  100/100  2024-02-26 19:32:42.626275  2024-02-26 19:32:33.452070
A          al_jitter  false   0.000714    0.000110    0.000000  100/100  2024-02-26 19:32:42.424557  2024-02-26 19:32:33.952282

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-02-26 19:32:42.424557  2024-02-26 19:32:33.952282             2        46.21
al_loss    false   2024-02-26 19:32:42.626275  2024-02-26 19:32:33.452070             2        50.07
al_rtt     true    2024-02-26 19:32:45.933150  2024-02-26 19:32:41.474784             3        53.75

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.792727    0.009085    0.000000  100/100  2024-02-26 19:32:45.933150  2024-02-26 19:32:41.474784
A          al_loss    false   0.792727    0.009085    0.000000  100/100  2024-02-26 19:32:42.626275  2024-02-26 19:32:33.452070
A          al_jitter  false   0.792727    0.009085    0.000000  100/100  2024-02-26 19:32:42.424557  2024-02-26 19:32:33.952282

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-02-26 19:32:42.424557  2024-02-26 19:32:33.952282             2        35.03
al_loss    false   2024-02-26 19:32:54.555755  2024-02-26 19:32:50.043272             4        56.61
al_rtt     false   2024-02-26 19:32:54.055997  2024-02-26 19:32:45.933150             4        61.38

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.000709    0.000036    0.000000  100/100  2024-02-26 19:32:54.055997  2024-02-26 19:32:45.933150
A          al_loss    false   0.000709    0.000036    0.000000  100/100  2024-02-26 19:32:54.555755  2024-02-26 19:32:50.043272
A          al_jitter  false   0.000709    0.000036    0.000000  100/100  2024-02-26 19:32:42.424557  2024-02-26 19:32:33.952282

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-02-26 19:32:57.942638  2024-02-26 19:32:42.424557             3        37.93
al_loss    false   2024-02-26 19:32:54.555755  2024-02-26 19:32:50.043272             4        45.35
al_rtt     true    2024-02-26 19:33:00.652120  2024-02-26 19:32:54.055997             5        50.07

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.217270    0.286389    0.000000  100/100  2024-02-26 19:33:00.652120  2024-02-26 19:32:54.055997
A          al_loss    false   0.217270    0.286389    0.000000  100/100  2024-02-26 19:32:54.555755  2024-02-26 19:32:50.043272
A          al_jitter  true    0.217270    0.286389    0.000000  100/100  2024-02-26 19:32:57.942638  2024-02-26 19:32:42.424557

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-02-26 19:33:06.241423  2024-02-26 19:32:57.942638             4        46.53
al_loss    false   2024-02-26 19:33:06.390857  2024-02-26 19:33:02.526317             6        48.71
al_rtt     false   2024-02-26 19:33:04.081586  2024-02-26 19:33:00.652120             6        50.70

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.000720    0.000059    0.000000  100/100  2024-02-26 19:33:04.081586  2024-02-26 19:33:00.652120
A          al_loss    false   0.000720    0.000059    0.000000  100/100  2024-02-26 19:33:06.390857  2024-02-26 19:33:02.526317
A          al_jitter  false   0.000720    0.000059    0.000000  100/100  2024-02-26 19:33:06.241423  2024-02-26 19:32:57.942638

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.000063    0.000022    0.000000  9/100
A          al_loss    false   0.000063    0.000022    0.000000  9/100
A          al_jitter  false   0.000063    0.000022    0.000000  9/100

Note

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

Note

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

Step 5: Set the following configuration in DUT0:

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

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

(al_loss)\s+(true)
Show output
--------------------------------------------------------------------------------------
  Alarm    Status           Toggled            Prev-toggled  Toggle-count  Time up (%)
--------------------------------------------------------------------------------------
al_jitter  true    2024-02-26 19:33:22.198946                           1        49.18
al_loss    true    2024-02-26 19:33:21.648298                           1        57.68
al_rtt     true    2024-02-26 19:33:22.896567                           1        38.43

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.480363    0.419726    48.000000  100/100  2024-02-26 19:33:22.896567
A          al_loss    true    0.480363    0.419726    48.000000  100/100  2024-02-26 19:33:21.648298
A          al_jitter  true    0.480363    0.419726    48.000000  100/100  2024-02-26 19:33:22.198946

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-02-26 19:33:30.372164  2024-02-26 19:33:22.198946             2        66.02
al_loss    false   2024-02-26 19:33:30.770292  2024-02-26 19:33:21.648298             2        73.71
al_rtt     false   2024-02-26 19:33:29.769473  2024-02-26 19:33:22.896567             2        55.49

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.000707    0.000037    0.000000  100/100  2024-02-26 19:33:29.769473  2024-02-26 19:33:22.896567
A          al_loss    false   0.000707    0.000037    0.000000  100/100  2024-02-26 19:33:30.770292  2024-02-26 19:33:21.648298
A          al_jitter  false   0.000707    0.000037    0.000000  100/100  2024-02-26 19:33:30.372164  2024-02-26 19:33:22.198946

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-02-26 19:33:30.372164  2024-02-26 19:33:22.198946             2        44.48
al_loss    false   2024-02-26 19:33:30.770292  2024-02-26 19:33:21.648298             2        49.66
al_rtt     true    2024-02-26 19:33:34.127921  2024-02-26 19:33:29.769473             3        54.46

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.792729    0.009085    0.000000  100/100  2024-02-26 19:33:34.127921  2024-02-26 19:33:29.769473
A          al_loss    false   0.792729    0.009085    0.000000  100/100  2024-02-26 19:33:30.770292  2024-02-26 19:33:21.648298
A          al_jitter  false   0.792729    0.009085    0.000000  100/100  2024-02-26 19:33:30.372164  2024-02-26 19:33:22.198946

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-02-26 19:33:30.372164  2024-02-26 19:33:22.198946             2        33.73
al_loss    false   2024-02-26 19:33:42.751046  2024-02-26 19:33:38.238051             4        56.29
al_rtt     false   2024-02-26 19:33:42.250722  2024-02-26 19:33:34.127921             4        61.88

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.000689    0.000045    0.000000  100/100  2024-02-26 19:33:42.250722  2024-02-26 19:33:34.127921
A          al_loss    false   0.000689    0.000045    0.000000  100/100  2024-02-26 19:33:42.751046  2024-02-26 19:33:38.238051
A          al_jitter  false   0.000689    0.000045    0.000000  100/100  2024-02-26 19:33:30.372164  2024-02-26 19:33:22.198946

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-02-26 19:33:46.159280  2024-02-26 19:33:30.372164             3        36.76
al_loss    false   2024-02-26 19:33:42.751046  2024-02-26 19:33:38.238051             4        45.16
al_rtt     true    2024-02-26 19:33:48.909629  2024-02-26 19:33:42.250722             5        50.24

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.226611    0.317461    0.000000  100/100  2024-02-26 19:33:48.909629  2024-02-26 19:33:42.250722
A          al_loss    false   0.226611    0.317461    0.000000  100/100  2024-02-26 19:33:42.751046  2024-02-26 19:33:38.238051
A          al_jitter  true    0.226611    0.317461    0.000000  100/100  2024-02-26 19:33:46.159280  2024-02-26 19:33:30.372164

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-02-26 19:33:53.930756  2024-02-26 19:33:46.159280             4        44.23
al_loss    false   2024-02-26 19:33:54.477781  2024-02-26 19:33:50.616629             6        48.53
al_rtt     false   2024-02-26 19:33:52.272559  2024-02-26 19:33:48.909629             6        50.91

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.000703    0.000051    0.000000  100/100  2024-02-26 19:33:52.272559  2024-02-26 19:33:48.909629
A          al_loss    false   0.000703    0.000051    0.000000  100/100  2024-02-26 19:33:54.477781  2024-02-26 19:33:50.616629
A          al_jitter  false   0.000703    0.000051    0.000000  100/100  2024-02-26 19:33:53.930756  2024-02-26 19:33:46.159280

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-02-26 19:34:12.251534  2024-02-26 19:34:07.197653             2        70.43
al_rtt     false   2024-02-26 19:34:11.903728  2024-02-26 19:34:07.945301             2        55.12

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.000673    0.000070    0.000000  100/100  2024-02-26 19:34:11.903728  2024-02-26 19:34:07.945301
A          al_loss    false   0.000673    0.000070    0.000000  100/100  2024-02-26 19:34:12.251534  2024-02-26 19:34:07.197653
A          al_jitter  false   0.000673    0.000070    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-02-26 19:34:15.614009                                         1        25.49
al_loss    true    2024-02-26 19:34:15.012445  2024-02-26 19:34:12.251534             3        68.36
al_rtt     true    2024-02-26 19:34:16.463523  2024-02-26 19:34:11.903728             3        49.05

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.500332    0.589586    50.000000  100/100  2024-02-26 19:34:16.463523  2024-02-26 19:34:11.903728
A          al_loss    true    0.500332    0.589586    50.000000  100/100  2024-02-26 19:34:15.012445  2024-02-26 19:34:12.251534
A          al_jitter  true    0.500332    0.589586    50.000000  100/100  2024-02-26 19:34:15.614009

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-02-26 19:34:24.184558  2024-02-26 19:34:15.614009             2        44.95
al_loss    false   2024-02-26 19:34:24.286687  2024-02-26 19:34:15.012445             4        75.18
al_rtt     false   2024-02-26 19:34:22.886645  2024-02-26 19:34:16.463523             4        54.46

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000728    0.000083    0.000000  100/100  2024-02-26 19:34:22.886645  2024-02-26 19:34:16.463523
A          al_loss    false   0.000728    0.000083    0.000000  100/100  2024-02-26 19:34:24.286687  2024-02-26 19:34:15.012445
A          al_jitter  false   0.000728    0.000083    0.000000  100/100  2024-02-26 19:34:24.184558  2024-02-26 19:34:15.614009

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-02-26 19:34:24.184558  2024-02-26 19:34:15.614009             2        34.19
al_loss    false   2024-02-26 19:34:24.286687  2024-02-26 19:34:15.012445             4        57.18
al_rtt     true    2024-02-26 19:34:27.694871  2024-02-26 19:34:22.886645             5        53.97

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.792732    0.009095    0.000000  100/100  2024-02-26 19:34:27.694871  2024-02-26 19:34:22.886645
A          al_loss    false   0.792732    0.009095    0.000000  100/100  2024-02-26 19:34:24.286687  2024-02-26 19:34:15.012445
A          al_jitter  false   0.792732    0.009095    0.000000  100/100  2024-02-26 19:34:24.184558  2024-02-26 19:34:15.614009

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-02-26 19:34:24.184558  2024-02-26 19:34:15.614009             2        27.71
al_loss    false   2024-02-26 19:34:36.371007  2024-02-26 19:34:31.853576             6        60.94
al_rtt     false   2024-02-26 19:34:35.868669  2024-02-26 19:34:27.694871             6        60.00

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000698    0.000045    0.000000  100/100  2024-02-26 19:34:35.868669  2024-02-26 19:34:27.694871
A          al_loss    false   0.000698    0.000045    0.000000  100/100  2024-02-26 19:34:36.371007  2024-02-26 19:34:31.853576
A          al_jitter  false   0.000698    0.000045    0.000000  100/100  2024-02-26 19:34:24.184558  2024-02-26 19:34:15.614009

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-02-26 19:34:40.758203  2024-02-26 19:34:24.184558             3        28.48
al_loss    false   2024-02-26 19:34:36.371007  2024-02-26 19:34:31.853576             6        51.04
al_rtt     false   2024-02-26 19:34:35.868669  2024-02-26 19:34:27.694871             6        50.24

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.179215    0.257852    0.000000  100/100  2024-02-26 19:34:35.868669  2024-02-26 19:34:27.694871
A          al_loss    false   0.179215    0.257852    0.000000  100/100  2024-02-26 19:34:36.371007  2024-02-26 19:34:31.853576
A          al_jitter  true    0.179215    0.257852    0.000000  100/100  2024-02-26 19:34:40.758203  2024-02-26 19:34:24.184558

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-02-26 19:34:47.748136  2024-02-26 19:34:40.758203             4        36.36
al_loss    false   2024-02-26 19:34:47.898780  2024-02-26 19:34:44.337448             8        52.37
al_rtt     false   2024-02-26 19:34:45.992124  2024-02-26 19:34:42.956868             8        50.46

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.000739    0.000116    0.000000  100/100  2024-02-26 19:34:45.992124  2024-02-26 19:34:42.956868
A          al_loss    false   0.000739    0.000116    0.000000  100/100  2024-02-26 19:34:47.898780  2024-02-26 19:34:44.337448
A          al_jitter  false   0.000739    0.000116    0.000000  100/100  2024-02-26 19:34:47.748136  2024-02-26 19:34:40.758203

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-02-26 19:35:05.352346  2024-02-26 19:35:00.436761             2        68.22
al_rtt     false   2024-02-26 19:35:05.119716  2024-02-26 19:35:01.186639             2        54.50

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.000718    0.000146    0.000000  100/100  2024-02-26 19:35:05.119716  2024-02-26 19:35:01.186639
A          al_loss    false   0.000718    0.000146    0.000000  100/100  2024-02-26 19:35:05.352346  2024-02-26 19:35:00.436761
A          al_jitter  false   0.000718    0.000146    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-02-26 19:35:09.074823                                         1        23.68
al_loss    true    2024-02-26 19:35:09.012225  2024-02-26 19:35:05.352346             3        61.35
al_rtt     true    2024-02-26 19:35:10.163665  2024-02-26 19:35:05.119716             3        45.17

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.390401    0.429721    39.000000  100/100  2024-02-26 19:35:10.163665  2024-02-26 19:35:05.119716
A          al_loss    true    0.390401    0.429721    39.000000  100/100  2024-02-26 19:35:09.012225  2024-02-26 19:35:05.352346
A          al_jitter  true    0.390401    0.429721    39.000000  100/100  2024-02-26 19:35:09.074823

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-02-26 19:35:17.431900  2024-02-26 19:35:09.074823             2        43.80
al_loss    false   2024-02-26 19:35:17.683382  2024-02-26 19:35:09.012225             4        71.22
al_rtt     false   2024-02-26 19:35:16.832279  2024-02-26 19:35:10.163665             4        55.54

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.000738    0.000096    0.000000  100/100  2024-02-26 19:35:16.832279  2024-02-26 19:35:10.163665
A          al_loss    false   0.000738    0.000096    0.000000  100/100  2024-02-26 19:35:17.683382  2024-02-26 19:35:09.012225
A          al_jitter  false   0.000738    0.000096    0.000000  100/100  2024-02-26 19:35:17.431900  2024-02-26 19:35:09.074823

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-02-26 19:35:17.431900  2024-02-26 19:35:09.074823             2        33.31
al_loss    false   2024-02-26 19:35:17.683382  2024-02-26 19:35:09.012225             4        54.17
al_rtt     true    2024-02-26 19:35:20.941397  2024-02-26 19:35:16.832279             5        54.72

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.792699    0.009081    0.000000  100/100  2024-02-26 19:35:20.941397  2024-02-26 19:35:16.832279
A          al_loss    false   0.792699    0.009081    0.000000  100/100  2024-02-26 19:35:17.683382  2024-02-26 19:35:09.012225
A          al_jitter  false   0.792699    0.009081    0.000000  100/100  2024-02-26 19:35:17.431900  2024-02-26 19:35:09.074823

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-02-26 19:35:17.431900  2024-02-26 19:35:09.074823             2        27.00
al_loss    false   2024-02-26 19:35:29.563275  2024-02-26 19:35:25.049579             6        58.50
al_rtt     false   2024-02-26 19:35:29.061480  2024-02-26 19:35:20.941397             6        60.48

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.000705    0.000043    0.000000  100/100  2024-02-26 19:35:29.061480  2024-02-26 19:35:20.941397
A          al_loss    false   0.000705    0.000043    0.000000  100/100  2024-02-26 19:35:29.563275  2024-02-26 19:35:25.049579
A          al_jitter  false   0.000705    0.000043    0.000000  100/100  2024-02-26 19:35:17.431900  2024-02-26 19:35:09.074823

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-02-26 19:35:32.993434  2024-02-26 19:35:17.431900             3        30.61
al_loss    false   2024-02-26 19:35:29.563275  2024-02-26 19:35:25.049579             6        48.97
al_rtt     true    2024-02-26 19:35:35.463681  2024-02-26 19:35:29.061480             7        51.96

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.212890    0.275017    0.000000  100/100  2024-02-26 19:35:35.463681  2024-02-26 19:35:29.061480
A          al_loss    false   0.212890    0.275017    0.000000  100/100  2024-02-26 19:35:29.563275  2024-02-26 19:35:25.049579
A          al_jitter  true    0.212890    0.275017    0.000000  100/100  2024-02-26 19:35:32.993434  2024-02-26 19:35:17.431900

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-02-26 19:35:40.594492  2024-02-26 19:35:32.993434             4        37.26
al_loss    false   2024-02-26 19:35:41.392238  2024-02-26 19:35:37.434406             8        51.51
al_rtt     false   2024-02-26 19:35:38.739070  2024-02-26 19:35:35.463681             8        51.35

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.000676    0.000057    0.000000  100/100  2024-02-26 19:35:38.739070  2024-02-26 19:35:35.463681
A          al_loss    false   0.000676    0.000057    0.000000  100/100  2024-02-26 19:35:41.392238  2024-02-26 19:35:37.434406
A          al_jitter  false   0.000676    0.000057    0.000000  100/100  2024-02-26 19:35:40.594492  2024-02-26 19:35:32.993434

Note

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