09-19-2024 03:06 PM - edited 09-27-2024 10:43 AM
This is a solution unique to Cisco that utilizes an integration between the Cisco IoT Control Center and the SD-WAN Manager to provide secure and automated carrier provisioning and activation at scale.
Today, when customers purchase cellular WAN devices, they must go through a time-consuming and resource-consuming process before the devices are fully set up with the designated carrier and plan at the site destination. In addition to purchasing the cellular WAN device from Cisco, the customer is responsible for acquiring SIM cards for specific carriers and specific plans for all their devices, and then working with the carrier to activate these SIMs.
With the introduction of the Managed Cellular Activation solution, Cisco cuts out the most time- and resource-intensive steps in this process to offer a new, much-simplified customer experience. When the customer purchases a cellular WAN device from Cisco and decides to opt into the Managed Cellular Activation solution, the device will ship with a physical eSIM card pre-loaded on that device. The supported carrier sets up an account for the customer in Control Center, details for this account are entered into SD-WAN Manager by the customer, and upon device boot-up, the device will automatically connect to the internet with a pre-loaded Cisco bootstrap carrier plan on that eSIM card before performing a switchover to the new designated carrier and plan selected by the customer.
Platforms |
First Supported Release |
Module |
Cisco Catalyst Wireless Gateway CG113-4GW6B |
17.12.1a |
N/A |
Catalyst 8200 Series |
17.12.1a |
P-5GS6-GL |
17.13.1a |
P-5GS6-R16SA-GL, P-LTEAP18-GL, P-LTEA-EA, P-LTEA7-NA |
|
Catalyst 8300 Series |
17.12.1a |
P-5GS6-GL |
17.13.1a |
P-5GS6-R16SA-GL, P-LTEAP18-GL, P-LTEA-EA, P-LTEA7-NA |
|
ISR 1000 Series |
17.12.2 |
P-5GS6-GL |
17.13.1a |
P-5GS6-R16SA-GL, P-LTEAP18-GL, P-LTEA-EA, P-LTEA7-NA |
|
Rugged Router IR 1101 Series |
17.15.1a |
P-5GS6-R16SA-GL, P-LTEAP18-GL, P-LTEA-EA, P-LTEA7-NA |
Rugged Router IR 1800 Series |
17.15.1a |
P-5GS6-R16SA-GL, P-LTEAP18-GL, P-LTEA-EA, P-LTEA7-NA, P-LTE-MNA |
North America Arena – AT&T
Note: SD-WAN Manage (formally vManage) used in this guide is running the 20.12 version.
In this section we will enable Cisco eSIM functionalities on SD-WAN Manager.
In this section, we will go over the steps on where to retrieve the (AccountID, Username, API Key) information needed in the next section of this document.
Carrier Name: AT&T Mobility
Account: 121683902
Username: username
API Key: ***********************************
In this section we will add default communication and rate plans to the Service Provider Account. The baseline answer is that the communication plan tells you what a SIM card can do from a technical perspective. In IoT Control Center, the Communication plan defines the connectivity capabilities of a device (e.g. is SMS allowed to communication on 4G or 5G, which APN (access Points) are available). The Rate plans define how the consumed connectivity / data will be billed. e.g., based on individual or pooled consumption within a billing cycle.
In this section we will create a cEdge configuration group using a config group workflow. It is assumed that the device is already onboarded to SD-WAN Manager using Quick Connect workflow for device onboarding. It is an alternative, guided method in Cisco SD-WAN Manager to onboard supported WAN edge devices into the Cisco SD-WAN overlay network. As part of the Quick Connect workflow, basic day-0 configuration profiles are created, which apply to all Cisco IOS XE SD-WAN devices, irrespective of the device model and device family. This workflow adds edge devices to the WAN transport and establishes data plane and control plane connections.
Please refer to this link for more details: https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/sdwan-xe-gs-book/m-quick-connect-workflow.html
In numerous regions globally, an LTE SIM card comes with a data limit that restricts the amount of data that can be transmitted over the LTE connection each month. Once this data limit is used up, the speed of the connection might be significantly reduced, or extra fees could be incurred to access more data.
Hence, in practical scenarios where a remote location is linked to two (WAN) transport, including one utilizing LTE, the preferable approach would typically involve utilizing the LTE connection solely when the other transport becomes unavailable.
For the purpose of this guide, we will configure Cellular tunnel interface as primary WAN transport.
cEdge configuration group is designed to simplify user experience and quickly bring-up the SD-WAN sites. In the real-world deployment, you will have multiple sites configured, multiple Transport and Management Profiles enabled, and service profile (VPNs) configured. To use only Cellular link as Transport VPN, we will delete all WAN interfaces and will configure WWAN or Cellular Tunnel Interface.
VPN 0 —Transport VPN carries control traffic via the configured WAN transport interfaces. Initially, VPN 0 contains all device's interfaces except for the management interface, and all interfaces are disabled. At least one interface must be configured in VPN 0, and at least one interface must connect to a WAN transport network, such as the Internet or an MPLS or a metro Ethernet network. This WAN transport interface is referred to as a tunnel interface. At a minimum, for this interface, you must configure an IP address, enable the interface, and set it to be a tunnel interface.
A tunnel interface allows only DTLS, TLS, and, for Cisco cEdge devices, IPsec traffic to pass through the tunnel. To allow additional traffic to pass without having to create explicit policies or access lists, enable them by including one allow-service command for each service. You can also explicitly disallow services by including the no allow-service command.
Congratulations, you just created your first Cellular Tunnel Interface!
In this section, we will configure the eSIM profile and controller settings. In traditional routing and SD-WAN setups, these actions are distinct. First, we create a profile specifying the Access Point Name (APN) and Packet Data Network (PDN) for SIM connectivity. Then, we link this profile to a controller profile, ensuring alignment with the appropriate interface. Given our PIM's support for multiple packet data networks, accurate profile-to-interface association is crucial.
Give your eSIM Cellular Controller a Feature Name and Description of the configuration.
Configure Cellular ID, it depends on the slot configuration of each and individual device (ex. C8300, C8200, ISR1000). See configuration guide to understand the slot configuration.
Observe the status of every deployed device. Notice Health and Reachability. If some devices are unreachable, it means that the device lost control connection with SD-WAN Manager (ex. Device is powered off)
This configuration example is meant to be interpreted with the aid of the official documentation from the configuration guide located here:
Managed Cellular Activation with Cisco eSIM Datasheet
Managed Cellular Activation Configuration Guide
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: