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.

../../../../_images/google2.svg

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/O9CEbIzgZVN1pePwZqtwNNsG91qC6hjs=
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
Show output
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=35.8 ms

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 35.752/35.752/35.752/0.000 ms

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
Show output
Jun 20 12:17:17.375861 osdx systemd-journald[1704]: Runtime Journal (/run/log/journal/1289a908a316477eb5dc4f18a9a27da9) is 1.1M, max 8.5M, 7.4M free.
Jun 20 12:17:17.377942 osdx systemd-journald[1704]: Received client request to rotate journal, rotating.
Jun 20 12:17:17.378143 osdx systemd-journald[1704]: Vacuuming done, freed 0B of archived journals from /run/log/journal/1289a908a316477eb5dc4f18a9a27da9.
Jun 20 12:17:17.479264 osdx OSDxCLI[10111]: User 'admin' executed a new command: 'system journal clear'.

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
Show output
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

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
Show output
Jun 20 12:18:02.088121 osdx systemd-journald[1704]: Runtime Journal (/run/log/journal/1289a908a316477eb5dc4f18a9a27da9) is 1.0M, max 8.5M, 7.5M free.
Jun 20 12:18:02.092074 osdx systemd-journald[1704]: Received client request to rotate journal, rotating.
Jun 20 12:18:02.092479 osdx systemd-journald[1704]: Vacuuming done, freed 0B of archived journals from /run/log/journal/1289a908a316477eb5dc4f18a9a27da9.
Jun 20 12:18:02.187943 osdx OSDxCLI[10111]: User 'admin' executed a new command: 'system journal clear'.

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
Jun 20 12:18:02.088121 osdx systemd-journald[1704]: Runtime Journal (/run/log/journal/1289a908a316477eb5dc4f18a9a27da9) is 1.0M, max 8.5M, 7.5M free.
Jun 20 12:18:02.092074 osdx systemd-journald[1704]: Received client request to rotate journal, rotating.
Jun 20 12:18:02.092479 osdx systemd-journald[1704]: Vacuuming done, freed 0B of archived journals from /run/log/journal/1289a908a316477eb5dc4f18a9a27da9.
Jun 20 12:18:02.187943 osdx OSDxCLI[10111]: User 'admin' executed a new command: 'system journal clear'.
Jun 20 12:18:22.361340 osdx OSDxCLI[10111]: User 'admin' executed a new command: 'system journal show | cat'.
Jun 20 12:18:22.573372 osdx OSDxCLI[10111]: User 'admin' executed a new command: 'system journal show | cat'.
Jun 20 12:18:23.781358 osdx OSDxCLI[10111]: User 'admin' executed a new command: 'system journal show | cat'.
Jun 20 12:18:24.993354 osdx OSDxCLI[10111]: User 'admin' executed a new command: 'system journal show | cat'.
Jun 20 12:18:26.213354 osdx OSDxCLI[10111]: User 'admin' executed a new command: 'system journal show | cat'.
Jun 20 12:18:27.437368 osdx OSDxCLI[10111]: User 'admin' executed a new command: 'system journal show | cat'.
Jun 20 12:18:28.685365 osdx OSDxCLI[10111]: User 'admin' executed a new command: 'system journal show | cat'.
Jun 20 12:18:29.937357 osdx OSDxCLI[10111]: User 'admin' executed a new command: 'system journal show | cat'.
Jun 20 12:18:31.185365 osdx OSDxCLI[10111]: User 'admin' executed a new command: 'system journal show | cat'.
Jun 20 12:18:32.445424 osdx OSDxCLI[10111]: User 'admin' executed a new command: 'system journal show | cat'.
Jun 20 12:18:32.519225 osdx wwan-module[41549]: [Core/cell0] Info: Signal '12' received to reconnect device.
Jun 20 12:18:32.519275 osdx wwan-module[41549]: [Device/cell0] Info: Stopping network connection...
Jun 20 12:18:32.537303 osdx wwan-module[41969]: Network cancelled... releasing resources
Jun 20 12:18:32.673431 osdx wwan-module[41969]: [/dev/cdc-wdm0] Network stopped
Jun 20 12:18:32.673431 osdx wwan-module[41969]: [/dev/cdc-wdm0] Client ID not released:
Jun 20 12:18:32.673431 osdx wwan-module[41969]:         Service: 'wds'
Jun 20 12:18:32.673431 osdx wwan-module[41969]:             CID: '21'
Jun 20 12:18:32.675268 osdx wwan-module[41549]: [Device/cell0] Info: Network connection was stopped!
Jun 20 12:18:32.677329 osdx wwan-module[41549]: [Network/cell0] Info: Stopping accessibility control...
Jun 20 12:18:32.677835 osdx wwan-module[41549]: [Network/cell0] Info: Accessibility control was stopped!
Jun 20 12:18:32.680078 osdx kernel: net cell0: link_state 0x1 -> 0x0
Jun 20 12:18:32.690932 osdx modulelauncher[41976]: stop DHCP client for cell0
Jun 20 12:18:32.692985 osdx dhclient[41668]: receive_packet failed on cell0: Network is down
Jun 20 12:18:32.694924 osdx wwan-module[41549]: [Device/cell0] Info: Checking registration state...
Jun 20 12:18:32.700987 osdx dhclient[41980]: Killed old client process
Jun 20 12:18:32.801489 osdx wwan-module[41549]: [Device/cell0] Info: Device registered and PS attached successfully
Jun 20 12:18:32.801513 osdx wwan-module[41549]: [Device/cell0] Info: Establishing network connection...
Jun 20 12:18:32.828514 osdx dhclient[41980]: DHCPRELEASE of 5.205.196.109 on cell0 to 5.205.196.110 port 67
Jun 20 12:18:32.828542 osdx dhclient[41980]: send_packet: Network is down
Jun 20 12:18:32.828553 osdx dhclient[41980]: dhclient.c:3146: Failed to send 300 byte long packet over cell0 interface.
Jun 20 12:18:33.094122 osdx wwan-module[41549]: [Device/cell0] Info: Network connection was successfully started: PDH=[2175585376]
Jun 20 12:18:33.220077 osdx kernel: net cell0: link_state 0x0 -> 0x1
Jun 20 12:18:33.222878 osdx wwan-module[41549]: [Network/cell0] Info: Starting accessibility control...
Jun 20 12:18:33.223259 osdx wwan-module[41549]: [Network/cell0] Info: Accessibility control was started!
Jun 20 12:18:33.406631 osdx modulelauncher[42029]: start DHCP client for cell0