close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Overview
play_arrow Initial Configuration
- Initial Configuration on NFX150 Devices
- Zero Touch Provisioning on NFX Series Devices
play_arrow Generating YANG Files
- YANG files on NFX150 Devices
play_arrow Configuring Interfaces
play_arrow Configuring USB Pass-Through on NFX Series Devices
- Supporting File Transfer from USB on NFX Series Devices
- Installing Software on NFX Devices Using USB Autoinstallation
play_arrow Configuring Security
play_arrow Configuring VNFs
play_arrow Configuring Mapping of Address and Port with Encapsulation (MAP-E)
- Mapping of Address and Port with Encapsulation on NFX Series Devices
- Configuring MAP-E on NFX Series Devices
play_arrow Configuring High Availability
- Chassis Cluster on NFX150 Devices
- Upgrading or Disabling a Chassis Cluster on NFX150 Devices
play_arrow Configuring Service Chaining
play_arrow Monitoring and Troubleshooting
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

Configuring the LTE Module on NFX Devices

date_range 04-Aug-21

arrow_backward

arrow_forward

The LTE module can be configured in three modes:

Always-on—The LTE module connects to the 3G/4G network after booting. The connection is always maintained, as long as there are no network or connectivity problems.

Note:
The default mode for LTE module is always-on. For the LTE module to be operational, you only need to install one SIM card on the LTE module before powering on the device. There is no additional configuration required.
Dial-on-demand—The LTE module initiates a connection when it receives interesting traffic. You define interesting traffic using the dialer filter. To configure dial-on-demand using a dialer filter, you first configure the dialer filter and then apply the filter to the dialer interface.
Backup—The LTE module connects to the 3G/4G network when the primary connection fails.

You can configure the LTE module either as a primary interface or as a backup interface. When configured as the primary interface, the LTE module supports both the always-on and dial-on-demand modes. When configured as the backup interface, the LTE module connects to the network only when the primary interface fails.

Note:

Starting in Junos OS Release 19.1R1, you can configure LTE modules on both nodes in a chassis cluster to provide backup WAN support.

Profile configuration is not needed in most scenarios, as LTE has a built-in database of many service providers and can automatically select the profile to use. Occasionally, you might need to specify profiles explicitly in the configuration, in which case, the automatic profile selection is disabled.

Before you begin the configuration, insert the Subscriber Identity Module (SIM) in the LTE module. The SIM uses a profile to establish a connection with the network. You can configure up to 16 profiles for each SIM card. The LTE module supports two SIM cards and so you can configure a total of 32 profiles, although only one profile can be active at a time. To configure the SIM profile, you will require the following information from the service provider:

Username and password
Access Point Name (APN)
Authentication (Challenge Handshake Authentication Protocol (CHAP) or Password Authentication Protocol (PAP))

Configuring the LTE Module for Primary Mode

Before you begin the procedure, ensure that the logical interface (dl0.0) is not configured as a backup. If dl0.0 is configured as a backup option for any interface on the device, then this configuration overrides the configuration outlined in this procedure, and the LTE module will function as a backup interface.

Use the show interfaces | display set | match backup-option | match dl0.0 command to check whether any interface uses dl0.0 as a backup interface. If dl0.0 is configured as a backup interface, then delete the configuration by issuing the following command:delete interfaces interface-name unit 0 backup-options interface dl0.0

To configure the LTE module as a primary interface:

Configure the dialer interface:

content_copy zoom_out_map
user@host# set interfaces dl0 unit 0 family inet negotiate-address
user@host# set interfaces dl0 unit 0 family inet6 negotiate-address
user@host# set interfaces dl0 unit 0 dialer-options pool dialer-pool-number
user@host# set interfaces dl0 unit 0 dialer-options dial-string dial-number
user@host# set interfaces dl0 unit 0 dialer-options always-on

Configure the dialer pool for the LTE physical interface:
```
user@host# set interfaces cl-1/1/0 dialer-options pool dialer-pool-number
```
The dialer-pool-number is always 1 as there is only one LTE interface on the NFX150.

Configure the profile.

content_copy zoom_out_map
user@host# run request modem wireless create-profile profile-id profile-id cl-1/1/0 slot sim-slot-number access-point-name apn-name authentication-method none

Note:

sim-slot-number is the slot on the module in which the SIM card is inserted.

Verify that the profile is configured successfully:
```
user@host# run show modem wireless profiles cl-1/1/0 slot 1
```

Activate the SIM card:

content_copy zoom_out_map
user@host# set interfaces cl-1/1/0 act-sim sim-slot-number

Select the profile and configure the radio access type for the SIM card:
```
user@host# set interfaces cl-1/1/0 cellular-options sim sim-slot-number select-profile profile-id profile-id
user@host# set interfaces cl-1/1/0 cellular-options sim sim-slot-number radio-access automatic
```
Note:
If a SIM card is installed in the second slot, then select the profile and configure the radio access type for the SIM card in the second slot as well.
Verify the status of the wireless network and dialer interface:
```
user@host#  run show modem wireless network
user@host#  run show interfaces dl0.0
```

Configuring the LTE Module for Dial-on-Demand Mode

When the LTE module is configured as a primary interface, it can function either in always-on mode or in dial-on-demand mode. In always-on mode, the interface remains connected to the network whereas In dial-on-demand mode, the connection is established only when needed.

In dial-on-demand mode, the dialer interface is enabled only when network traffic configured as an “interesting traffic” arrives on the network. Interesting traffic triggers or activates the wireless WAN connection. You define an interesting packet by using the dialer filter. To configure dial-on-demand by using a dialer filter, you first configure the dialer filter and then apply the filter to the dialer interface.

Once the traffic is sent over the network, an inactivity timer is triggered and the connection is closed after the timer expires.

Note:

The dial-on-demand mode is supported only if the LTE module is configured as a primary interface.

To configure the LTE module as a dial-on-demand interface:

Configure the dialer interface:

content_copy zoom_out_map
user@host# set interfaces dl0 unit 0 family inet negotiate-address
user@host# set interfaces dl0 unit 0 family inet6 negotiate-address
user@host# set interfaces dl0 unit 0 family inet filter dialer dialer-filter-name
user@host# set interfaces dl0 unit 0 dialer-options pool dialer-pool-number
user@host# set interfaces dl0 unit 0 dialer-options dial-string dial-number

(Optional) Configure the idle-timeout value, which determines the duration for which the connection will remain enabled in the absence of interesting traffic.
```
user@host# set interfaces dl0 unit 0 dialer-options idle-timeout idle-timeout-value
```
Configure the dialer pool for the LTE physical interface:
```
user@host# set interfaces cl-1/1/0 dialer-options pool dialer-pool-number
```
The dialer-pool-number is always 1 as there is only one LTE interface on the NFX150.

Create the dialer filter rule:

content_copy zoom_out_map
user@host# set firewall family inet dialer-filter dialer-filter-name term term1 from destination-address ip-address then note

Set the default route:

content_copy zoom_out_map
user@host# set routing-options static route ip-address next-hop dl0.0

Configure the profile.

content_copy zoom_out_map
user@host# run request modem wireless create-profile profile-id profile-id cl-1/1/0 slot sim-slot-number access-point-name apn-name authentication-method none

Note:

sim-slot-number is the slot on the module in which the SIM card is inserted.

Verify that the profile is configured successfully:
```
user@host# run show modem wireless profiles cl-1/1/0 slot 1
```

Activate the SIM card:

content_copy zoom_out_map
user@host# set interfaces cl-1/1/0 act-sim sim-slot-number

Select the profile and configure the radio access type for the SIM card:
```
user@host# set interfaces cl-1/1/0 cellular-options sim sim-slot-number select-profile profile-id profile-id
user@host# set interfaces cl-1/1/0 cellular-options sim sim-slot-number radio-access automatic
```
Note:
If a SIM card is installed in the second slot, then select the profile and configure the radio access type for the SIM card in the second slot as well.
Verify the configuration by sending traffic to the destination address. The traffic is routed to the dl0 interface and if it matches the dialer filter rule, then the dl0 is triggered to dial.
Verify the status of the wireless network and dialer interface:
```
user@host#  run show modem wireless network
user@host#  run show interfaces dl0.0
```

Configuring the LTE Module for Backup Mode

You can configure the LTE module as a backup interface. If the primary interface fails, the LTE module connects to the network and remains online only until the primary interface becomes functional. The dialer interface is enabled only when the primary interface fails.

To configure the LTE module as a backup interface:

Configure the dialer interface:

content_copy zoom_out_map
user@host# set interfaces dl0 unit 0 family inet negotiate-address
user@host# set interfaces dl0 unit 0 family inet6 negotiate-address
user@host# set interfaces dl0 unit 0 dialer-options pool dialer-pool-number
user@host# set interfaces dl0 unit 0 dialer-options dial-string dial-number

Configure the dialer pool for the LTE physical interface:
```
user@host# set interfaces cl-1/1/0 dialer-options pool dialer-pool-number
```
The dialer-pool-number is always 1 as there is only one LTE interface on the NFX150.

Configure the profile.

content_copy zoom_out_map
user@host# run request modem wireless create-profile profile-id profile-id cl-1/1/0 slot sim-slot-number access-point-name l3vpn.corp authentication-method none

Note:

sim-slot-number is the slot on the LTE module in which the SIM card is inserted.

Verify that the profile is configured successfully:
```
user@host# run show modem wireless profiles cl-1/1/0 slot 1
```

Activate the SIM card:

content_copy zoom_out_map
user@host# set interfaces cl-1/1/0 act-sim sim-slot-number

Select the profile and configure the radio access type for the SIM card:
```
user@host# set interfaces cl-1/1/0 cellular-options sim sim-slot-number select-profile profile-id profile-id
user@host# set interfaces cl-1/1/0 cellular-options sim sim-slot-number radio-access automatic
```
Note:
If a SIM card is installed in the second slot, then select the profile and configure the radio access type for the SIM card in the second slot as well.
Configure the Ethernet interface as the primary interface, which connects to the wireless network. Configure the dl0 interface as the backup interface.
```
user@host# set interfaces ge-1/0/2 unit 0 family inet address 192.168.2.1/24
user@host# set interfaces ge-1/0/2 unit 0 backup-options interface dl0.0
```
Verify the status of the wireless network and dialer interface:
```
user@host#  run show modem wireless network
user@host#  run show interfaces dl0.0
```

Configuring the LTE Interface Module in an NFX Chassis Cluster

An NFX150 chassis cluster supports two cl interfaces, cl-1/1/0 (primary node) and cl-8/1/0 (secondary node).

To configure the LTE modules in a chassis cluster:

Configure the dialer interface (dl0):

content_copy zoom_out_map
{primary:node0}[edit]
user@host# set interfaces dl0 unit 0 family inet negotiate-address
user@host# set interfaces dl0 unit 0 family inet6 negotiate-address
user@host# set interfaces dl0 unit 0 dialer-options pool dialer-pool-number
user@host# set interfaces dl0 unit 0 dialer-options dial-string dial-number
user@host# set interfaces dl0 unit 0 dialer-options always-on

Sample configuration for the dl0 interface:

content_copy zoom_out_map
set interfaces dl0 unit 0 family inet negotiate-address
set interfaces dl0 unit 0 dialer-options pool 1
set interfaces dl0 unit 0 dialer-options always-on
set interfaces dl0 unit 0 dialer-options dial-string 1234

Configure the LTE interface (cl-1/1/0) on the primary node:

Configure the dialer pool for the LTE physical interface:

content_copy zoom_out_map
{primary:node0}[edit]
user@host# set interfaces cl-1/1/0 dialer-options pool dialer-pool-number

Specify the priority for the interface. The interface with the higher priority becomes the active interface.
```
{primary:node0}[edit]
user@host# set interfaces cl-1/1/0 dialer-options pool dialer-pool-number priority priority
```

Configure the profile:

content_copy zoom_out_map
{primary:node0}[edit]
user@host# run request modem wireless create-profile profile-id profile-id cl-1/1/0 slot sim-slot-number access-point-name apn-name 

Verify that the profile is configured successfully:

content_copy zoom_out_map
{primary:node0}[edit]
user@host# run show modem wireless profiles cl-1/1/0 slot 1
Profile details
  Max profiles: 16
  Default profile Id: 1

Profile 1: ACTIVE
  Valid: TRUE
  Username: user1
  Password: ********
  Access point name (APN): 3gnet
  Authentication: CHAP
  IP Version: IPV4V6
Profile 2: Invalid
Profile 3: Invalid
Profile 4: Invalid
Profile 5: Invalid
Profile 6: Invalid
Profile 7: Invalid
Profile 8: Invalid
Profile 9: Invalid
Profile 10: Invalid
Profile 11: Invalid
Profile 12: Invalid
Profile 13: Invalid
Profile 14: Invalid
Profile 15: Invalid
Profile 16: Inactive
  Valid: TRUE
  Access point name (APN): 3gnet
  Authentication: None
  IP Version: IPV4V6

Activate the SIM card:

content_copy zoom_out_map
{primary:node0}[edit]
user@host# set interfaces cl-1/1/0 act-sim sim-slot-number

Select the profile and configure the radio access type for the SIM card:
```
{primary:node0}[edit]
user@host# set interfaces cl-1/1/0 cellular-options sim sim-slot-number select-profile profile-id profile-id
user@host# set interfaces cl-1/1/0 cellular-options sim sim-slot-number radio-access automatic
```
Note:
If a SIM card is installed in the second slot, then select the profile and configure the radio access type for the SIM card in the second slot as well.

Sample configuration for the cl-1/1/0 interface:

content_copy zoom_out_map
set interfaces cl-1/1/0 act-sim 1
set interfaces cl-1/1/0 cellular-options sim 1 select-profile profile-id 1
set interfaces cl-1/1/0 cellular-options sim 1 radio-access automatic
set interfaces cl-1/1/0 cellular-options sim 2 select-profile profile-id 1
set interfaces cl-1/1/0 cellular-options sim 2 radio-access automatic
set interfaces cl-1/1/0 dialer-options pool 1 priority 1

Repeat Step 2 to configure the LTE interface (cl-8/1/0) for the secondary node.

If you assign the same priority to both interfaces, then the interface that is listed first in the configuration becomes the active interface.

To verify which interface is the active interface:

content_copy zoom_out_map
root@host> show dialer pools 
Pool: 1                               
  Dialer interfaces:      Name            State
                          dl0.0           Active               
  Subordinate interfaces: Name            Flags         Priority
                          cl-1/1/0        Active        100     
                          cl-8/1/0        Inactive      1       
 

Sample configuration for the cl-8/1/0 interface:

content_copy zoom_out_map
set interfaces cl-8/1/0 act-sim 1
set interfaces cl-8/1/0 cellular-options sim 1 select-profile profile-id 1
set interfaces cl-8/1/0 cellular-options sim 1 radio-access automatic
set interfaces cl-8/1/0 cellular-options sim 2 select-profile profile-id 1
set interfaces cl-8/1/0 cellular-options sim 2 radio-access automatic
set interfaces cl-8/1/0 dialer-options pool 1 priority 254

Verify the status of the wireless network and dialer interface:

content_copy zoom_out_map
{primary:node0}[edit]
user@host# run show modem wireless network 
LTE Connection details 
  Connected time: 210
  IP: 10.90.51.234
  Gateway: 10.90.51.233
  DNS: 123.123.123.123
  IPv6: ::
  Gatewayv6: ::
  DNSv6: ::
  Input bps: 0
  Output bps: 14
  Bytes Received: 7236
  Bytes Transferred: 25468
  Packets Received: 89
  Packets Transferred: 316
Wireless Modem Network Info 
  Current Modem Status: Connected
  Current Service Status: Normal
  Current Service Type: CS
  Current Service Mode: LTE
  Network: CHN-UNICOM
  Mobile Country Code (MCC): 0
  Mobile Network Code (MNC): 0
  Location Area Code (LAC): 0
  Routing Area Code (RAC): 0
  Cell Identification: 0
  Access Point Name (APN): ctnet
  Public Land Mobile Network (PLMN): CHN-UNICOM
  Physical Cell ID (PCI): N/A
  International Mobile Subscriber Identification (IMSI): ****************
  International Mobile Equipment Identification (IMEI/MEID): ****************
  Integrate Circuit Card Identity (ICCID): 89860118802425942389
  Reference Signal Receiving Power (RSRP): N/A
  Reference Signal Receiving Quality (RSRQ): N/A
  Signal to Interference-plus-Noise Ratio (SiNR): N/A
  Signal Noise Ratio (SNR): N/A
  Energy per Chip to Interference (ECIO): 0

content_copy zoom_out_map
{primary:node0}[edit]
user@host#  run show interfaces dl0.0 
Physical interface: dl0, Enabled, Physical link is Up
  Interface index: 522, SNMP ifIndex: 0
  Type: 27, Link-level type: Ethernet, MTU: 1504
  Device flags   : Present Running
  Interface flags: SNMP-Traps
  Link type      : Full-Duplex
  Link flags     : None
  Current address: 00:00:5e:00:53:82, Hardware address: 00:00:5e:00:53:82
  Last flapped   : Never
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)

  Logical interface dl0.0 (Index 101) (SNMP ifIndex 0)
    Flags: Up SNMP-Traps 0x4004000 Encapsulation: ENET2
    Dialer:  
      State: Active, Dial pool: 1
      Dial strings: 1234
      Subordinate interfaces: cl-8/1/0 (Index 519)
      Activation delay: 0, Deactivation delay: 0
      Initial route check delay: 120
      Redial delay: 255
      Callback wait period: 5
      Load threshold: 0, Load interval: 60
    Bandwidth: 300mbps
    Input packets : 1
    Output packets: 4
    Protocol inet, MTU: 1490
    Max nh cache: 0, New hold nh limit: 0, Curr nh cnt: 0, Curr new hold cnt: 0, NH drop cnt: 0
      Flags: Sendbcast-pkt-to-re, Negotiate-Address
      Addresses, Flags: Is-Preferred Is-Primary
        Destination: 10.34.163.0/26, Local: 10.34.163.31, Broadcast: 10.34.163.63

By default, the time interval taken to switch to the secondary cl interface when the active cl interface times out is 120 seconds. You can change the time interval by configuring the redial-delay option:

content_copy zoom_out_map
{primary:node0}[edit]
user@host# user@host# set interfaces dl0 unit 0 dialer-options redial-delay time-in-seconds

arrow_backward PREVIOUS VDSL2 Interfaces on NFX150 Devices

NEXT arrow_forward Upgrading the Modem Firmware on NFX Devices Through Over-the-Air (OTA)

How to Configure the NFX150

ON THIS PAGE

Configuring the LTE Module on NFX Devices

Configuring the LTE Module for Primary Mode

Configuring the LTE Module for Dial-on-Demand Mode

Configuring the LTE Module for Backup Mode

Configuring the LTE Interface Module in an NFX Chassis Cluster

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

How to Configure the NFX150

ON THIS PAGE

Configuring the LTE Module on NFX Devices

Configuring the LTE Module for Primary Mode

Configuring the LTE Module for Dial-on-Demand Mode

Configuring the LTE Module for Backup Mode

Configuring the LTE Interface Module in an NFX Chassis Cluster

Related Documentation

Stay in touch