How do I set the APN and bring a device online with a Hologram SIM (LTE-M or NB-IoT)?

Most LTE-M and NB-IoT projects stall at the same place: the SIM is inserted, the device powers up, but it never actually comes online. In almost every case I’ve debugged, it comes down to two things—APN settings and network registration. The good news: with a Hologram SIM, you only need a handful of parameters and a repeatable checklist to bring devices online reliably.

Quick Answer: To bring an LTE-M or NB-IoT device online with a Hologram SIM, set the APN to hologram (no username/password), confirm your modem is in LTE-only mode with LTE-M or NB-IoT bands enabled, and then initiate a data session (PDP context). You can verify connectivity by checking for an IP address on the modem and confirming active session logs in the Hologram Dashboard.

Why This Matters

If APN and radio settings are wrong, your fleet doesn’t just fail to connect—it silently sits in the field burning engineering time, truck rolls, and customer trust. For LTE-M and NB-IoT especially, registration quirks and band support can turn into multi-week escalations unless you treat connectivity as a controlled, testable workflow.

Dialing in a standard “bring-up” process for Hologram SIMs—APN, radio mode, bands, attach, data session—gives you:

Key Benefits:

• Outage-resistant deployments: Start from a clean, known-good configuration so you can layer in Hologram’s multi-carrier redundancy and Outage Protection without guesswork.
• Faster, cheaper rollouts: Use the same scripts from factory Test Mode through field deployment, avoiding “it works on my bench” surprises and idle SIM spend.
• Observable connectivity: Tie modem states, IP assignment, and Dashboard logs together so your team can see exactly why a device is or isn’t online.

Core Concepts & Key Points

Concept	Definition	Why it's important
APN (hologram)	The Access Point Name tells the network which packet data network to connect your SIM to. For Hologram, use hologram with no username/password.	If the APN is wrong or missing, your device may register to the network but never get an IP address or pass data.
PDP Context / Data Session	A logical data connection (bearer) between the device and the cellular network, usually configured with APN, IP type, and QoS.	LTE-M/NB-IoT devices can appear “attached” yet offline until a PDP context is activated with the correct APN.
LTE-M vs NB-IoT Radio Mode	Narrowband LTE technologies optimized for low-power, low-bandwidth IoT. LTE-M supports mobility and voice; NB-IoT focuses on deep coverage and very low data rates.	Your modem must support and be configured for the right mode and bands available on local Hologram partner networks, or it will never fully register.

How It Works (Step-by-Step)

Here’s the high-level process I recommend for any LTE-M or NB-IoT deployment with Hologram SIMs—whether you’re bringing up a single dev kit or a factory line.

1. Confirm SIM & Plan Support

   • Use genuine Hologram global IoT SIMs (including Hyper SIMs when you want eUICC flexibility) that are activated and assigned to a plan that supports LTE-M or NB-IoT in your target country.
   • In the Hologram Dashboard:
     • Check that the SIM status is Active (not Inactive, Hibernating, or Preflight).
     • Verify there are no data caps or plan restrictions blocking usage.
   • If you’re in Test Mode, remember test data limits are small; for extended testing, upgrade to a production plan.

2. Set the APN to hologram

   • Regardless of LTE-M or NB-IoT, the APN is:

     APN: hologram
     Username: (leave blank)
     Password: (leave blank)
     Auth: None / CHAP disabled (if configurable)
     

   • Common AT-command patterns (consult your modem’s manual for exact syntax):

     # Example (Quectel-style)
     AT+QICSGP=1,1,"hologram","","",1
     
     # Example (Sierra/Fibocom-style PDP context)
     AT+CGDCONT=1,"IP","hologram"
     

   • For modules that store profiles, make sure you save the APN configuration to non-volatile memory so it persists across reboots.

3. Configure LTE-M or NB-IoT Radio Mode & Bands

   This is where most LTE-M/NB-IoT failures hide. You need three things to line up:

   • The module supports LTE-M and/or NB-IoT on bands available in your region.
   • The firmware revision enables LTE-M/NB-IoT (some modules need a specific firmware).
   • The device is configured to use the right mode and bands.

   Typical checks:

   # Check supported radio access technologies (vendor-specific)
   AT+QNWINFO          # Quectel
   AT+CESQ / AT+CSQ    # Signal quality
   AT+QCFG="nwscanmode",3,1   # Example: LTE only (no 2G/3G)
   AT+QCFG="iotopmode",1      # Example: LTE-M only
   AT+QCFG="iotopmode",2      # NB-IoT only
   AT+QCFG="iotopmode",0      # LTE-M + NB-IoT both enabled
   

   Practical guidance:

   • Start with LTE-only (no 2G/3G) to reduce registration confusion.
   • For a new region, begin with LTE-M first, then try NB-IoT if LTE-M coverage is limited.
   • If your module supports manual band selection, initially enable all LTE bands or at least the primary local LTE-M/NB-IoT bands, then narrow once you know what’s actually being used.

4. Register to the Network (Attach)

   Once radio mode is correct, you need the module to attach to a network that accepts Hologram SIMs (Hologram connects to 550+ networks across 190+ countries via roaming and direct partners).

   Key steps:

   # Enable registration URCs
   AT+CREG=2
   AT+CEREG=2
   
   # Check registration status
   AT+CREG?    # Circuit-switched (legacy, often not used on IoT)
   AT+CEREG?   # EPS / LTE attach status
   

   Typical +CEREG responses:

   • 0,1 — Registered, home network.
   • 0,5 — Registered, roaming (expected for many Hologram deployments).
   • 0,2 — Searching for network (not yet attached).
   • 0,3 — Registration denied (often provisioning, coverage, or band issues).

   If registration is denied:

   • Confirm the SIM is Active in the Dashboard.
   • Verify you’re in a location with known LTE-M/NB-IoT coverage.
   • Try a different antenna or location (window, outdoors) to rule out RF issues.
   • Check that the device is not network-locked to a single carrier.

5. Start a Data Session (PDP Context Activation)

   This is where the APN actually gets used. Until the PDP context is active, you won’t get an IP address and your device won’t be “online” in practice.

   Typical procedure:

   # Define the PDP context (if not already saved)
   AT+CGDCONT=1,"IP","hologram"
   
   # Attach to packet domain
   AT+CGATT=1
   
   # Activate PDP context
   AT+CGACT=1,1
   
   # Some modules combine attach + data session in one command:
   AT+QIACT=1      # Quectel
   AT+NETOPEN      # Others
   

   Then confirm:

   # Check if you got an IP address
   AT+CGPADDR=1
   # or
   AT+QIACT?       # Module-specific
   

   You should see a non-0.0.0.0 IP address. That means the network has accepted your APN and you have an active data bearer.

6. Send a Simple Data Test

   With the PDP context active, verify end-to-end connectivity:

   # DNS resolution test (where supported)
   AT+QIDNSGIP="hologram.io"
   
   # Simple TCP test (Hologram Cloud or your own server)
   AT+QIOPEN=1,0,"TCP","cloudsocket.hologram.io",9999,0,0
   # or for generic ping
   AT+QPING=1,"8.8.8.8"
   

   Confirm:

   • DNS resolves.
   • TCP socket opens without errors.
   • Pings return with reasonable latency (LTE-M/NB-IoT are slower than LTE Cat 4, but typical single/low hundreds of ms are normal for LTE-M; NB-IoT can be higher due to power-saving and coverage enhancements).

7. Verify in the Hologram Dashboard

   Finally, tie the modem view to your fleet view:

   • In the Hologram Dashboard:
     • Locate your SIM by ICCID or device name/label.
     • Confirm it shows Online or recently active.
     • Check session logs and data usage to confirm packets are flowing.
   • If you’ve integrated the Dashboard via API, surface:
     • Last seen timestamp.
     • Last IP address.
     • Current state (active, hibernating, paused).

   This single pane of glass is what lets you debug issues in minutes instead of days once devices are in the field.

Common Mistakes to Avoid

• Using the wrong APN or adding credentials:
  Many modules ship from the factory with a carrier-specific APN (e.g., internet, web.vodafone.com, etc.) or a default username/password.
  How to avoid it: Always explicitly set hologram as the APN and clear any stored username/password or auth type. Save the configuration and verify after a reboot.

• Assuming “registered” means “online”:
  Seeing +CEREG: 0,5 (roaming registered) can give a false sense of success even when no PDP context exists.
  How to avoid it: Always check for an IP address (AT+CGPADDR or equivalent) and complete a data test (DNS, ping, or HTTP/TCP request) before considering a device “online.”

• Ignoring LTE-M / NB-IoT band and firmware constraints:
  I’ve seen fleets shipped with modules that technically support LTE-M but on bands not deployed in the target country—or with firmware that doesn’t enable NB-IoT yet.
  How to avoid it: Before hardware lock-in, confirm with your module vendor and Hologram which LTE-M/NB-IoT bands and firmware versions are verified in your deployment regions. Run on-bench tests with Hologram SIMs early in your lifecycle.

Real-World Example

A team rolling out remote monitoring devices for rooftop solar wanted to use NB-IoT for deep coverage and long battery life. They’d wired Hologram SIMs into their design, but field pilots in rural sites kept failing: the devices would show good signal strength yet never send data back.

When we walked their bring-up sequence, we found:

• The module was in auto mode with LTE, LTE-M, NB-IoT, and 2G all enabled.
• The APN was still set to the module vendor’s demo profile, not hologram.
• They were checking only +CEREG and assumed that meant the device was online.

We reworked their scripts to:

1. Force LTE-only + NB-IoT (iotopmode set appropriately).
2. Explicitly configure APN="hologram" with no credentials and store it to NVRAM.
3. Require a successful PDP context activation and DNS resolution before marking the device as commissioned.
4. Use Hologram’s Dashboard to confirm first traffic and tag devices as “Healthy” once a full handshake completed.

After that change:

• Factory bring-up time dropped to under 2 minutes per device.
• NB-IoT devices in deep-coverage locations came online reliably.
• The ops team could see, from the Hologram Dashboard, exactly which sites were attached but offline versus fully online.

Pro Tip: Build your APN and PDP context configuration as an idempotent script you can run at every boot—don’t assume the modem’s non-volatile storage is always in a good state. On unexpected resets, this saves hours of remote debugging.

Summary

To bring an LTE-M or NB-IoT device online with a Hologram SIM, you only need a few critical settings—but they have to be exact and verified. Use hologram as the APN with no credentials, ensure your modem is configured for LTE-M or NB-IoT on the right bands, and always confirm both network registration and an active data session with an IP address. Close the loop by validating traffic in the Hologram Dashboard so your team has a single, reliable view of device health as your fleet scales across 190+ countries and 550+ carriers.

Next Step

Get Started