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.000032    0.000000  7/100
A          al_loss    false   0.000059    0.000032    0.000000  7/100
A          al_jitter  false   0.000059    0.000032    0.000000  7/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-13 16:01:51.316440                           1        51.63
al_loss    true    2024-02-13 16:01:50.957601                           1        57.39
al_rtt     true    2024-02-13 16:01:52.818669                           1        27.90

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.370267    0.449830    37.000000  100/100  2024-02-13 16:01:52.818669
A          al_loss    true    0.370267    0.449830    37.000000  100/100  2024-02-13 16:01:50.957601
A          al_jitter  true    0.370267    0.449830    37.000000  100/100  2024-02-13 16:01:51.316440

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-13 16:01:59.627111  2024-02-13 16:01:51.316440             2        68.57
al_loss    false   2024-02-13 16:01:59.691949  2024-02-13 16:01:50.957601             2        72.12
al_rtt     false   2024-02-13 16:01:58.725375  2024-02-13 16:01:52.818669             2        48.76

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.000430    0.000081    0.000000  100/100  2024-02-13 16:01:58.725375  2024-02-13 16:01:52.818669
A          al_loss    false   0.000430    0.000081    0.000000  100/100  2024-02-13 16:01:59.691949  2024-02-13 16:01:50.957601
A          al_jitter  false   0.000430    0.000081    0.000000  100/100  2024-02-13 16:01:59.627111  2024-02-13 16:01:51.316440

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-13 16:01:59.627111  2024-02-13 16:01:51.316440             2        46.11
al_loss    false   2024-02-13 16:01:59.691949  2024-02-13 16:01:50.957601             2        48.48
al_rtt     true    2024-02-13 16:02:03.132806  2024-02-13 16:01:58.725375             3        50.26

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.792469    0.009080    0.000000  100/100  2024-02-13 16:02:03.132806  2024-02-13 16:01:58.725375
A          al_loss    false   0.792469    0.009080    0.000000  100/100  2024-02-13 16:01:59.691949  2024-02-13 16:01:50.957601
A          al_jitter  false   0.792469    0.009080    0.000000  100/100  2024-02-13 16:01:59.627111  2024-02-13 16:01:51.316440

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-13 16:01:59.627111  2024-02-13 16:01:51.316440             2        34.92
al_loss    false   2024-02-13 16:02:11.768923  2024-02-13 16:02:07.246034             4        55.73
al_rtt     false   2024-02-13 16:02:11.253061  2024-02-13 16:02:03.132806             4        58.95

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.000410    0.000045    0.000000  100/100  2024-02-13 16:02:11.253061  2024-02-13 16:02:03.132806
A          al_loss    false   0.000410    0.000045    0.000000  100/100  2024-02-13 16:02:11.768923  2024-02-13 16:02:07.246034
A          al_jitter  false   0.000410    0.000045    0.000000  100/100  2024-02-13 16:01:59.627111  2024-02-13 16:01:51.316440

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-13 16:02:15.061824  2024-02-13 16:01:59.627111             3        37.70
al_loss    false   2024-02-13 16:02:11.768923  2024-02-13 16:02:07.246034             4        44.68
al_rtt     false   2024-02-13 16:02:11.253061  2024-02-13 16:02:03.132806             4        47.26

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.197883    0.313113    0.000000  100/100  2024-02-13 16:02:11.253061  2024-02-13 16:02:03.132806
A          al_loss    false   0.197883    0.313113    0.000000  100/100  2024-02-13 16:02:11.768923  2024-02-13 16:02:07.246034
A          al_jitter  true    0.197883    0.313113    0.000000  100/100  2024-02-13 16:02:15.061824  2024-02-13 16:01:59.627111

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-13 16:02:22.783463  2024-02-13 16:02:15.061824             4        45.22
al_loss    false   2024-02-13 16:02:23.186806  2024-02-13 16:02:19.215839             6        48.61
al_rtt     false   2024-02-13 16:02:20.976343  2024-02-13 16:02:18.175636             6        47.47

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.000413    0.000057    0.000000  100/100  2024-02-13 16:02:20.976343  2024-02-13 16:02:18.175636
A          al_loss    false   0.000413    0.000057    0.000000  100/100  2024-02-13 16:02:23.186806  2024-02-13 16:02:19.215839
A          al_jitter  false   0.000413    0.000057    0.000000  100/100  2024-02-13 16:02:22.783463  2024-02-13 16:02:15.061824

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.000067    0.000027    0.000000  9/100
A          al_loss    false   0.000067    0.000027    0.000000  9/100
A          al_jitter  false   0.000067    0.000027    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-13 16:02:37.161656                           1        44.15
al_loss    true    2024-02-13 16:02:36.070517                           1        61.20
al_rtt     true    2024-02-13 16:02:37.507060                           1        38.73

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.550194    0.419829    55.000000  100/100  2024-02-13 16:02:37.507060
A          al_loss    true    0.550194    0.419829    55.000000  100/100  2024-02-13 16:02:36.070517
A          al_jitter  true    0.550194    0.419829    55.000000  100/100  2024-02-13 16:02:37.161656

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-13 16:02:44.725684  2024-02-13 16:02:37.161656             2        61.48
al_loss    false   2024-02-13 16:02:45.173464  2024-02-13 16:02:36.070517             2        74.02
al_rtt     false   2024-02-13 16:02:44.130421  2024-02-13 16:02:37.507060             2        53.81

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.000419    0.000060    0.000000  100/100  2024-02-13 16:02:44.130421  2024-02-13 16:02:37.507060
A          al_loss    false   0.000419    0.000060    0.000000  100/100  2024-02-13 16:02:45.173464  2024-02-13 16:02:36.070517
A          al_jitter  false   0.000419    0.000060    0.000000  100/100  2024-02-13 16:02:44.725684  2024-02-13 16:02:37.161656

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-13 16:02:44.725684  2024-02-13 16:02:37.161656             2        41.32
al_loss    false   2024-02-13 16:02:45.173464  2024-02-13 16:02:36.070517             2        49.74
al_rtt     true    2024-02-13 16:02:48.731974  2024-02-13 16:02:44.130421             3        53.38

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.792446    0.009079    0.000000  100/100  2024-02-13 16:02:48.731974  2024-02-13 16:02:44.130421
A          al_loss    false   0.792446    0.009079    0.000000  100/100  2024-02-13 16:02:45.173464  2024-02-13 16:02:36.070517
A          al_jitter  false   0.792446    0.009079    0.000000  100/100  2024-02-13 16:02:44.725684  2024-02-13 16:02:37.161656

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-13 16:02:44.725684  2024-02-13 16:02:37.161656             2        31.40
al_loss    false   2024-02-13 16:02:57.308950  2024-02-13 16:02:52.809443             4        56.48
al_rtt     false   2024-02-13 16:02:56.807068  2024-02-13 16:02:48.731974             4        61.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.000420    0.000059    0.000000  100/100  2024-02-13 16:02:56.807068  2024-02-13 16:02:48.731974
A          al_loss    false   0.000420    0.000059    0.000000  100/100  2024-02-13 16:02:57.308950  2024-02-13 16:02:52.809443
A          al_jitter  false   0.000420    0.000059    0.000000  100/100  2024-02-13 16:02:44.725684  2024-02-13 16:02:37.161656

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-13 16:03:01.183015  2024-02-13 16:02:44.725684             3        33.01
al_loss    false   2024-02-13 16:02:57.308950  2024-02-13 16:02:52.809443             4        45.47
al_rtt     false   2024-02-13 16:02:56.807068  2024-02-13 16:02:48.731974             4        49.12

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.173406    0.263504    0.000000  100/100  2024-02-13 16:02:56.807068  2024-02-13 16:02:48.731974
A          al_loss    false   0.173406    0.263504    0.000000  100/100  2024-02-13 16:02:57.308950  2024-02-13 16:02:52.809443
A          al_jitter  true    0.173406    0.263504    0.000000  100/100  2024-02-13 16:03:01.183015  2024-02-13 16:02:44.725684

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-13 16:03:08.741925  2024-02-13 16:03:01.183015             4        42.24
al_loss    false   2024-02-13 16:03:08.802616  2024-02-13 16:03:04.870474             6        48.98
al_rtt     false   2024-02-13 16:03:07.333485  2024-02-13 16:03:04.170683             6        49.88

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000457    0.000104    0.000000  100/100  2024-02-13 16:03:07.333485  2024-02-13 16:03:04.170683
A          al_loss    false   0.000457    0.000104    0.000000  100/100  2024-02-13 16:03:08.802616  2024-02-13 16:03:04.870474
A          al_jitter  false   0.000457    0.000104    0.000000  100/100  2024-02-13 16:03:08.741925  2024-02-13 16:03:01.183015

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-13 16:03:25.920123  2024-02-13 16:03:21.281210             2        77.07
al_rtt     false   2024-02-13 16:03:25.393126  2024-02-13 16:03:22.031619             2        55.81

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.000741    0.010129    0.000000  100/100  2024-02-13 16:03:25.393126  2024-02-13 16:03:22.031619
A          al_loss    false   0.000741    0.010129    0.000000  100/100  2024-02-13 16:03:25.920123  2024-02-13 16:03:21.281210
A          al_jitter  false   0.000741    0.010129    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-13 16:03:28.552646                                         1        27.11
al_loss    true    2024-02-13 16:03:28.038551  2024-02-13 16:03:25.920123             3        70.57
al_rtt     true    2024-02-13 16:03:29.901836  2024-02-13 16:03:25.393126             3        44.08

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.410244    0.409860    41.000000  100/100  2024-02-13 16:03:29.901836  2024-02-13 16:03:25.393126
A          al_loss    true    0.410244    0.409860    41.000000  100/100  2024-02-13 16:03:28.038551  2024-02-13 16:03:25.920123
A          al_jitter  true    0.410244    0.409860    41.000000  100/100  2024-02-13 16:03:28.552646

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-13 16:03:36.869985  2024-02-13 16:03:28.552646             2        47.08
al_loss    false   2024-02-13 16:03:37.170147  2024-02-13 16:03:28.038551             4        77.99
al_rtt     false   2024-02-13 16:03:35.812084  2024-02-13 16:03:29.901836             4        52.50

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.000414    0.000069    0.000000  100/100  2024-02-13 16:03:35.812084  2024-02-13 16:03:29.901836
A          al_loss    false   0.000414    0.000069    0.000000  100/100  2024-02-13 16:03:37.170147  2024-02-13 16:03:28.038551
A          al_jitter  false   0.000414    0.000069    0.000000  100/100  2024-02-13 16:03:36.869985  2024-02-13 16:03:28.552646

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-13 16:03:36.869985  2024-02-13 16:03:28.552646             2        35.40
al_loss    false   2024-02-13 16:03:37.170147  2024-02-13 16:03:28.038551             4        58.63
al_rtt     true    2024-02-13 16:03:40.271655  2024-02-13 16:03:35.812084             5        52.77

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

(al_rtt)\s+(true)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     true    0.792449    0.009084    0.000000  100/100  2024-02-13 16:03:40.271655  2024-02-13 16:03:35.812084
A          al_loss    false   0.792449    0.009084    0.000000  100/100  2024-02-13 16:03:37.170147  2024-02-13 16:03:28.038551
A          al_jitter  false   0.792449    0.009084    0.000000  100/100  2024-02-13 16:03:36.869985  2024-02-13 16:03:28.552646

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-13 16:03:36.869985  2024-02-13 16:03:28.552646             2        28.41
al_loss    false   2024-02-13 16:03:48.832540  2024-02-13 16:03:44.332818             6        62.42
al_rtt     false   2024-02-13 16:03:48.333043  2024-02-13 16:03:40.271655             6        59.21

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.000436    0.000110    0.000000  100/100  2024-02-13 16:03:48.333043  2024-02-13 16:03:40.271655
A          al_loss    false   0.000436    0.000110    0.000000  100/100  2024-02-13 16:03:48.832540  2024-02-13 16:03:44.332818
A          al_jitter  false   0.000436    0.000110    0.000000  100/100  2024-02-13 16:03:36.869985  2024-02-13 16:03:28.552646

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-13 16:03:52.311403  2024-02-13 16:03:36.869985             3        31.62
al_loss    false   2024-02-13 16:03:48.832540  2024-02-13 16:03:44.332818             6        51.86
al_rtt     true    2024-02-13 16:03:55.047719  2024-02-13 16:03:48.333043             7        49.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.219508    0.322622    0.000000  100/100  2024-02-13 16:03:55.047719  2024-02-13 16:03:48.333043
A          al_loss    false   0.219508    0.322622    0.000000  100/100  2024-02-13 16:03:48.832540  2024-02-13 16:03:44.332818
A          al_jitter  true    0.219508    0.322622    0.000000  100/100  2024-02-13 16:03:52.311403  2024-02-13 16:03:36.869985

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-13 16:04:00.415177  2024-02-13 16:03:52.311403             4        39.92
al_loss    false   2024-02-13 16:04:00.418201  2024-02-13 16:03:56.608013             8        53.69
al_rtt     false   2024-02-13 16:03:58.810807  2024-02-13 16:03:55.047719             8        51.29

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.000445    0.000136    0.000000  100/100  2024-02-13 16:03:58.810807  2024-02-13 16:03:55.047719
A          al_loss    false   0.000445    0.000136    0.000000  100/100  2024-02-13 16:04:00.418201  2024-02-13 16:03:56.608013
A          al_jitter  false   0.000445    0.000136    0.000000  100/100  2024-02-13 16:04:00.415177  2024-02-13 16:03:52.311403

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-13 16:04:18.355224  2024-02-13 16:04:13.460450             2        68.86
al_rtt     false   2024-02-13 16:04:18.110754  2024-02-13 16:04:14.200871             2        54.93

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.000405    0.000520    0.000000  100/100  2024-02-13 16:04:18.110754  2024-02-13 16:04:14.200871
A          al_loss    false   0.000405    0.000520    0.000000  100/100  2024-02-13 16:04:18.355224  2024-02-13 16:04:13.460450
A          al_jitter  false   0.000405    0.000520    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-13 16:04:21.820848                                         1        25.16
al_loss    true    2024-02-13 16:04:21.421880  2024-02-13 16:04:18.355224             3        65.63
al_rtt     true    2024-02-13 16:04:23.221397  2024-02-13 16:04:18.110754             3        44.31

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.400247    0.439830    40.000000  100/100  2024-02-13 16:04:23.221397  2024-02-13 16:04:18.110754
A          al_loss    true    0.400247    0.439830    40.000000  100/100  2024-02-13 16:04:21.421880  2024-02-13 16:04:18.355224
A          al_jitter  true    0.400247    0.439830    40.000000  100/100  2024-02-13 16:04:21.820848

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-13 16:04:30.040140  2024-02-13 16:04:21.820848             2        43.70
al_loss    false   2024-02-13 16:04:30.340310  2024-02-13 16:04:21.421880             4        73.46
al_rtt     false   2024-02-13 16:04:29.503932  2024-02-13 16:04:23.221397             4        54.18

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000439    0.000089    0.000000  100/100  2024-02-13 16:04:29.503932  2024-02-13 16:04:23.221397
A          al_loss    false   0.000439    0.000089    0.000000  100/100  2024-02-13 16:04:30.340310  2024-02-13 16:04:21.421880
A          al_jitter  false   0.000439    0.000089    0.000000  100/100  2024-02-13 16:04:30.040140  2024-02-13 16:04:21.820848

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-13 16:04:30.040140  2024-02-13 16:04:21.820848             2        33.12
al_loss    false   2024-02-13 16:04:30.340310  2024-02-13 16:04:21.421880             4        55.67
al_rtt     true    2024-02-13 16:04:33.697811  2024-02-13 16:04:29.503932             5        53.73

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.801427    0.009075    0.000000  100/100  2024-02-13 16:04:33.697811  2024-02-13 16:04:29.503932
A          al_loss    false   0.801427    0.009075    0.000000  100/100  2024-02-13 16:04:30.340310  2024-02-13 16:04:21.421880
A          al_jitter  false   0.801427    0.009075    0.000000  100/100  2024-02-13 16:04:30.040140  2024-02-13 16:04:21.820848

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-13 16:04:30.040140  2024-02-13 16:04:21.820848             2        26.68
al_loss    false   2024-02-13 16:04:42.467012  2024-02-13 16:04:37.954866             6        59.48
al_rtt     false   2024-02-13 16:04:41.962215  2024-02-13 16:04:33.697811             6        59.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.000467    0.000149    0.000000  100/100  2024-02-13 16:04:41.962215  2024-02-13 16:04:33.697811
A          al_loss    false   0.000467    0.000149    0.000000  100/100  2024-02-13 16:04:42.467012  2024-02-13 16:04:37.954866
A          al_jitter  false   0.000467    0.000149    0.000000  100/100  2024-02-13 16:04:30.040140  2024-02-13 16:04:21.820848

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-13 16:04:45.680058  2024-02-13 16:04:30.040140             3        30.75
al_loss    false   2024-02-13 16:04:42.467012  2024-02-13 16:04:37.954866             6        49.90
al_rtt     true    2024-02-13 16:04:48.706635  2024-02-13 16:04:41.962215             7        50.38

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.217031    0.300973    0.000000  100/100  2024-02-13 16:04:48.706635  2024-02-13 16:04:41.962215
A          al_loss    false   0.217031    0.300973    0.000000  100/100  2024-02-13 16:04:42.467012  2024-02-13 16:04:37.954866
A          al_jitter  true    0.217031    0.300973    0.000000  100/100  2024-02-13 16:04:45.680058  2024-02-13 16:04:30.040140

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-13 16:04:53.453549  2024-02-13 16:04:45.680058             4        37.53
al_loss    false   2024-02-13 16:04:54.189469  2024-02-13 16:04:50.145678             8        52.50
al_rtt     false   2024-02-13 16:04:52.582476  2024-02-13 16:04:48.706635             8        52.41

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

(al_loss)\s+(false)
(al_rtt)\s+(false)
(al_jitter)\s+(false)
Show output
-------------------------------------------------------------------------------------------------------------------------------
Operation    Alarm    Status    RTT(s)    Jitter(s)   Loss(%)   Window            Toggled                   Prev-toggled
-------------------------------------------------------------------------------------------------------------------------------
A          al_rtt     false   0.000429    0.000108    0.000000  100/100  2024-02-13 16:04:52.582476  2024-02-13 16:04:48.706635
A          al_loss    false   0.000429    0.000108    0.000000  100/100  2024-02-13 16:04:54.189469  2024-02-13 16:04:50.145678
A          al_jitter  false   0.000429    0.000108    0.000000  100/100  2024-02-13 16:04:53.453549  2024-02-13 16:04:45.680058

Note

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