Check Multi Apn Connection

This scenario shows how to configure up to four cellular interfaces on the same cellular module, each associated with a different APN. As a result, more than one data interface can be used to access the network, requiring only one cellular module.

../../../../_images/googlemultiapn.svg

Test ICMP Connectivity

Description

In DUT0, four cellular interfaces are defined, each associated with a different cellular profile and PDP (Packet Data Protocol) context. Once configured, the ‘Ping’ command is used to check the connectivity of all four data interfaces with Google’s public DNS server.

Scenario

Step 1: Set the following configuration in DUT0 :

set cellular profile CELPROFILE1 apn movistar.es
set cellular profile CELPROFILE2 apn telefonica.es
set cellular profile CELPROFILE3 apn internet
set cellular profile CELPROFILE4 apn internet2
set controllers cellular wwan0 sim select socket_1
set controllers cellular wwan0 sim socket socket_1 encrypted-pin U2FsdGVkX1+iITCaJL3ROrm6tdZfaOIuG5p3cMgM9dY=
set controllers cellular wwan0 sim socket socket_1 pdp 1 profile CELPROFILE1
set controllers cellular wwan0 sim socket socket_1 pdp 2 profile CELPROFILE2
set controllers cellular wwan0 sim socket socket_1 pdp 3 profile CELPROFILE3
set controllers cellular wwan0 sim socket socket_1 pdp 4 profile CELPROFILE4
set interfaces cellular cell0 address dhcp
set interfaces cellular cell0 phy wwan0 pdp 1
set interfaces cellular cell1 address dhcp
set interfaces cellular cell1 phy wwan0 pdp 2
set interfaces cellular cell2 address dhcp
set interfaces cellular cell2 phy wwan0 pdp 3
set interfaces cellular cell3 address dhcp
set interfaces cellular cell3 phy wwan0 pdp 4
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Note

Once the cellular module is configured, with the following operational command it can be checked if the SIM and registration states are correct.

Step 2: Run command controllers cellular wwan0 show network-status at DUT0 and check if output matches the following regular expressions:

SIM status\s* = OK
Registration state\s* = registered
Show output
SIM status = OK
Registration state = registered
Public Land Mobile Network code = HOME[21407] ACT[21422]
Public Land Mobile Network name = Movistar
Network technology currently in use = lte(+5gnr)
Current Service Domain registered = cs-ps (capable cs-ps)
Current Roaming status = off
3GPP Cell ID = 72016415
Radio Band = eutran-20
Bandwidth = 10
Channel = 6400
LTE Tracking Area Code (TAC) = 28673
EN-DC Available = yes
DCNR Restriction = no
LTE Carrier Aggregation Info:
   Primary Cell Info:
      Band = E-UTRA Band 20
      Frequency = 6400
      Downlink Bandwidth = 10 MHz
      Physical Cell ID = 195
      Scell State = registered
      RSRP (dBm) = -66
      RSRQ (dB) = -6
      RSSI (dBm) = -43
      SINR (dB) = 14
      Uplink Bandwidth = 10 MHz
   Secondary Cell Info #0:
      Band = E-UTRA Band 3
      Frequency = 1301
      Downlink Bandwidth = 20 MHz
      Physical Cell ID = 216
      Scell State = inactive
      RSRP (dBm) = -102
      RSRQ (dB) = -10
      RSSI (dBm) = -83
      SINR (dB) = 16
      Uplink Frequency = 19301
      Uplink Bandwidth = 20 MHz
RX level (dBm) = -53 or greater
Coverage level = 5 (*****)

Note

On the other hand, with the following commands it can be checked if all four contexts have correctly established the connection to the network.

Step 3: Run command controllers cellular wwan0 pdp 1 show network-data-connection at DUT0 and check if output matches the following regular expressions:

Connection status\s* = connected
Show output
Connection status               = connected
Traffic channel status          = active
Max. TX channel rate (bps)      = 0
Max. RX channel rate (bps)      = 0
IPv4 address                    = 5.205.214.213
IPv4 mask                       = 255.255.255.252
IPv4 gateway                    = 5.205.214.214
IPv4 primary DNS                = 80.58.61.248
IPv4 secondary DNS              = 80.58.61.249

Step 4: Run command controllers cellular wwan0 pdp 2 show network-data-connection at DUT0 and check if output matches the following regular expressions:

Connection status\s* = connected
Show output
Connection status               = connected
Traffic channel status          = active
Max. TX channel rate (bps)      = 0
Max. RX channel rate (bps)      = 0
IPv4 address                    = 10.28.235.177
IPv4 mask                       = 255.255.255.252
IPv4 gateway                    = 10.28.235.178
IPv4 primary DNS                = 80.58.61.248
IPv4 secondary DNS              = 80.58.61.249

Step 5: Run command controllers cellular wwan0 pdp 3 show network-data-connection at DUT0 and check if output matches the following regular expressions:

Connection status\s* = connected
Show output
Connection status               = connected
Traffic channel status          = active
Max. TX channel rate (bps)      = 0
Max. RX channel rate (bps)      = 0
IPv4 address                    = 10.18.135.98
IPv4 mask                       = 255.255.255.252
IPv4 gateway                    = 10.18.135.97
IPv4 primary DNS                = 80.58.61.248
IPv4 secondary DNS              = 80.58.61.249

Step 6: Run command controllers cellular wwan0 pdp 4 show network-data-connection at DUT0 and check if output matches the following regular expressions:

Connection status\s* = connected
Show output
Connection status               = connected
Traffic channel status          = active
Max. TX channel rate (bps)      = 0
Max. RX channel rate (bps)      = 0
IPv4 address                    = 10.180.77.48
IPv4 mask                       = 255.255.255.224
IPv4 gateway                    = 10.180.77.49
IPv4 primary DNS                = 80.58.61.248
IPv4 secondary DNS              = 80.58.61.249

Note

Additionally, with the previous operational commands, the IP addresses that have been provided by the operator to be used by each cellular interface are displayed. So, with the following commands, it can be checked if all four cellular interfaces have been correctly configured by the DHCP client.

Step 7: Run command interfaces cellular cell0 show at DUT0 and check if output matches the following regular expressions:

cell0\s+\d+.\d+.\d+.\d+\/\d+\s+up\s+up
Show output
------------------------------------------------------------------
Name            IP Address           Admin  Oper  Vrf  Description
------------------------------------------------------------------
cell0  5.205.214.213/30              up     up
       fe80::5081:86ff:fe12:c6eb/64

Step 8: Run command interfaces cellular cell1 show at DUT0 and check if output matches the following regular expressions:

cell1\s+\d+.\d+.\d+.\d+\/\d+\s+up\s+up
Show output
------------------------------------------------------------------
Name            IP Address           Admin  Oper  Vrf  Description
------------------------------------------------------------------
cell1  10.28.235.177/30              up     up
       fe80::5081:86ff:fe12:c6eb/64

Step 9: Run command interfaces cellular cell2 show at DUT0 and check if output matches the following regular expressions:

cell2\s+\d+.\d+.\d+.\d+\/\d+\s+up\s+up
Show output
------------------------------------------------------------------
Name            IP Address           Admin  Oper  Vrf  Description
------------------------------------------------------------------
cell2  10.18.135.98/30               up     up
       fe80::5081:86ff:fe12:c6eb/64

Step 10: Run command interfaces cellular cell3 show at DUT0 and check if output matches the following regular expressions:

cell3\s+\d+.\d+.\d+.\d+\/\d+\s+up\s+up
Show output
------------------------------------------------------------------
Name            IP Address           Admin  Oper  Vrf  Description
------------------------------------------------------------------
cell3  10.180.77.48/27               up     up
       fe80::5081:86ff:fe12:c6eb/64

Note

Once everything above has been verified, we can be sure that all four cellular interfaces have been configured correctly and that there must be connectivity with the network from each of them. The latter can be verified, for example, by pinging Google's DNS public server.

Step 11: Ping IP address 8.8.8.8 from DUT0:

admin@DUT0$ ping 8.8.8.8 local-address cell0 count 1 size 56 timeout 1
Show output
PING 8.8.8.8 (8.8.8.8) from 5.205.214.213 cell0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=25.9 ms

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

Step 12: Ping IP address 8.8.8.8 from DUT0:

admin@DUT0$ ping 8.8.8.8 local-address cell1 count 1 size 56 timeout 1
Show output
PING 8.8.8.8 (8.8.8.8) from 10.28.235.177 cell1: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=114 time=101 ms

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

Step 13: Ping IP address 8.8.8.8 from DUT0:

admin@DUT0$ ping 8.8.8.8 local-address cell2 count 1 size 56 timeout 1
Show output
PING 8.8.8.8 (8.8.8.8) from 10.18.135.98 cell2: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=113 time=166 ms

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

Step 14: Ping IP address 8.8.8.8 from DUT0:

admin@DUT0$ ping 8.8.8.8 local-address cell3 count 1 size 56 timeout 1
Show output
PING 8.8.8.8 (8.8.8.8) from 10.180.77.48 cell3: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=114 time=141 ms

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