Check Accessibility Control

This scenario shows how to configure a cellular interface, enabling the accessibility control mechanism that triggers reconnections when network connectivity is lost.

Test Reconnection By Accessibility Control

Description

In DUT0, the cell0 cellular interface is configured with a cellular profile for which accessibility control is enabled. Once connectivity with Google’s DNS public server has been verified, a situation where 100% of the packets received by the network are lost is emulated to verify that the accessibility control mechanism triggers a reconnection.

Scenario

Step 1: Set the following configuration in DUT0 :

set cellular logging level info
set cellular profile CELPROFILE accessibility-control ping address 8.8.8.8
set cellular profile CELPROFILE accessibility-control ping interval 10
set cellular profile CELPROFILE apn movistar.es
set interfaces cellular cell0 address dhcp
set interfaces cellular cell0 encrypted-pin U2FsdGVkX1/F2/P/+OFnGMKMspVNtv6anz3/2UF8j28=
set interfaces cellular cell0 profile CELPROFILE
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Note

Once the cellular interface is configured, it can be verified that there is network connectivity by pinging Google’s DNS public server.

Step 2: Ping IP address 8.8.8.8 from DUT0:

admin@DUT0$ ping 8.8.8.8 count 1 size 56 timeout 1

Note

The accessibility control is a mechanism where pings are sent at an interval, and to the IP address, configured by the user. The mechanism then waits for a response within this interval. If no response is received before it times out, a second ping is sent and a response is expected within 10 seconds. If there is still no response, two more pings are sent at 5-second intervals. Finally, if there is still no response, the device reconnects to the network.

Note

As a result, you can verify that no reconnection has been recorded in the system logs if you wait long enough.

Step 3: Run command system journal clear at DUT0.

Step 4: Run command system journal show | cat at DUT0 and check if output does not contain the following tokens:

[Core/cell0] Info: Signal '12' received to reconnect device
[Device/cell0] Info: Stopping network connection
[Device/cell0] Info: Establishing network connection

Note

However, when traffic control is applied, it is possible to prove the ‘ping’ command is failing because ICMP packets are being dropped.

Step 5: Modify the following configuration lines in DUT0 :

set interfaces cellular cell0 traffic control in PLOSS
set traffic control PLOSS type network-emulator packet-loss 100

Step 6: Expect a failure in the following command: Ping IP address 8.8.8.8 from DUT0:

admin@DUT0$ ping 8.8.8.8 count 1 size 56 timeout 1

Note

You can verify that a reconnection has been recorded in the system logs if you wait long enough.

Step 7: Run command system journal clear at DUT0.

Step 8: Run command system journal show | cat at DUT0 and check if output does not contain the following tokens:

[Core/cell0] Info: Signal '12' received to reconnect device
[Device/cell0] Info: Stopping network connection
[Device/cell0] Info: Establishing network connection

Step 9: Run command system journal show | cat at DUT0 and check if output contains the following tokens:

[Core/cell0] Info: Signal '12' received to reconnect device
[Device/cell0] Info: Stopping network connection
[Device/cell0] Info: Establishing network connection

Show output

Mar 21 16:59:31.921404 osdx systemd-journald[1693]: Runtime Journal (/run/log/journal/3ed46040748047a0a8333e44e1894bf3) is 1.0M, max 8.5M, 7.4M free.
Mar 21 16:59:31.923591 osdx systemd-journald[1693]: Received client request to rotate journal, rotating.
Mar 21 16:59:31.923793 osdx systemd-journald[1693]: Vacuuming done, freed 0B of archived journals from /run/log/journal/3ed46040748047a0a8333e44e1894bf3.
Mar 21 16:59:32.009942 osdx OSDxCLI[36805]: User 'admin' executed a new command: 'system journal clear'.
Mar 21 16:59:40.513740 osdx cfgd[1361]: Could not parse bandwidth for traffic-control network-emulator 'PLOSS'
Mar 21 16:59:50.579098 osdx cfgd[1361]: Could not parse bandwidth for traffic-control network-emulator 'PLOSS'
Mar 21 16:59:52.292166 osdx OSDxCLI[36805]: User 'admin' executed a new command: 'system journal show | cat'.
Mar 21 16:59:52.532029 osdx OSDxCLI[36805]: User 'admin' executed a new command: 'system journal show | cat'.
Mar 21 16:59:53.808039 osdx OSDxCLI[36805]: User 'admin' executed a new command: 'system journal show | cat'.
Mar 21 16:59:55.084030 osdx OSDxCLI[36805]: User 'admin' executed a new command: 'system journal show | cat'.
Mar 21 16:59:56.376029 osdx OSDxCLI[36805]: User 'admin' executed a new command: 'system journal show | cat'.
Mar 21 16:59:57.652154 osdx OSDxCLI[36805]: User 'admin' executed a new command: 'system journal show | cat'.
Mar 21 16:59:58.940044 osdx OSDxCLI[36805]: User 'admin' executed a new command: 'system journal show | cat'.
Mar 21 17:00:00.244039 osdx OSDxCLI[36805]: User 'admin' executed a new command: 'system journal show | cat'.
Mar 21 17:00:00.644495 osdx cfgd[1361]: Could not parse bandwidth for traffic-control network-emulator 'PLOSS'
Mar 21 17:00:00.946788 osdx wwan-module[46568]: [Core/cell0] Info: Signal '12' received to reconnect device.
Mar 21 17:00:00.946842 osdx wwan-module[46568]: [Device/cell0] Info: Stopping network connection...
Mar 21 17:00:00.964907 osdx wwan-module[46924]: Network cancelled... releasing resources
Mar 21 17:00:00.999915 osdx wwan-module[46924]: [/dev/cdc-wdm0] Network stopped
Mar 21 17:00:00.999915 osdx wwan-module[46924]: [/dev/cdc-wdm0] Client ID not released:
Mar 21 17:00:00.999915 osdx wwan-module[46924]:         Service: 'wds'
Mar 21 17:00:00.999915 osdx wwan-module[46924]:             CID: '21'
Mar 21 17:00:01.001661 osdx wwan-module[46568]: [Device/cell0] Info: Network connection was stopped!
Mar 21 17:00:01.003740 osdx wwan-module[46568]: [Network/cell0] Info: Stopping accessibility control...
Mar 21 17:00:01.003941 osdx wwan-module[46568]: [Device/cell0] Info: Accessibility control was stopped!
Mar 21 17:00:01.006911 osdx kernel: net cell0: link_state 0x1 -> 0x0
Mar 21 17:00:01.016993 osdx modulelauncher[46931]: stop DHCP client for cell0
Mar 21 17:00:01.017582 osdx dhclient[46652]: receive_packet failed on cell0: Network is down
Mar 21 17:00:01.021123 osdx wwan-module[46568]: [Device/cell0] Info: Establishing network connection...
Mar 21 17:00:01.027978 osdx dhclient[46936]: Killed old client process
Mar 21 17:00:01.132589 osdx wwan-module[46568]: [Device/cell0] Info: Network connection was successfully started: PDH=[2175581616]
Mar 21 17:00:01.134759 osdx kernel: net cell0: link_state 0x0 -> 0x1
Mar 21 17:00:01.136033 osdx wwan-module[46568]: [Network/cell0] Info: Starting accessibility control...
Mar 21 17:00:01.136338 osdx wwan-module[46568]: [Network/cell0] Info: Accessibility control was started!
Mar 21 17:00:01.151181 osdx dhclient[46936]: DHCPRELEASE of 37.12.28.167 on cell0 to 37.12.28.168 port 67
Mar 21 17:00:01.151209 osdx dhclient[46936]: send_packet: Network is down
Mar 21 17:00:01.151221 osdx dhclient[46936]: dhclient.c:3146: Failed to send 300 byte long packet over cell0 interface.