H3C SecPath F5030 User manual

H3C SecPath Firewalls
Comware 7 Fundamentals Configuration Guide
New H3C Technologies Co., Ltd.
http://www.h3c.com
Software version:
F5030, F5030-6GW, F5060, F5080, F5000-M, F5000-A E9628
F5010, F5020-GM, F5020, F5040, F5000-C, F5000-S E9342
F1020, F1030, F1050, F1060, F1070, F1080, F1020-GM, F1070-GM E9345
F1000-AK130, AK135, AK140, AK145, AK150, AK155, AK160, AK165, AK170,
AK175, AK180, AK185 E9345
F1005, F1010, F1003-L, F1005-L E9536
F1000-AK108, AK109, AK110, AK115, AK120, AK125 E9536
Document version: 6W400-20190620

Copyright © 2019, New H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior written
consent of New H3C Technologies Co., Ltd.
Trademarks
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this
document are the property of their respective owners.
Notice
The information in this document is subject to change without notice. All contents in this document, including
statements, information, and recommendations, are believed to be accurate, but they are presented without
warranty of any kind, express or implied. H3C shall not be liable for technical or editorial errors or omissions
contained herein.

Preface
•This configuration guide describes the fundamentals and configuration procedures for Layer
2—WAN access features, including PPP, 3G modem, and 4G modem.
•CLI.
•RBAC, device login, and device access control.
•Management of the device, file systems, configuration files, and licenses.
•FTP and TFTP.
•Tcl and Python.
•ISSU and common software upgrade.
•MAC address learning through a Layer 3 device.
•Automatic configuration.
This preface includes the following topics about the documentation:
•Audience.
•Conventions.
•Documentation feedback.
Audience
This documentation is intended for:
•Network planners.
•Field technical support and servicing engineers.
•Network administrators.
Conventions
The following information describes the conventions used in the documentation.
Command conventions
Convention Description
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars,
from which you select one or none.

Convention Description
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select a minimum of one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.
&<1-n> The argument or keyword and argument combination before the ampersand (&) sign
can be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Convention Description
Boldface Window names, button names, field names, and menu items are in Boldface. For
example, the New User window opens; click OK.
> Multi-level menus are separated by angle brackets. For example, File > Create >
Folder.
Symbols
Convention Description
WARNING! An alert that calls attention to important information that if not understood or followed
can result in personal injury.
CAUTION: An alert that calls attention to important information that if not understood or followed
can result in data loss, data corruption, or damage to hardware or software.
IMPORTANT: An alert that calls attention to essential information.
NOTE: An alert that contains additional or supplementary information.
TIP: An alert that provides helpful information.
Network topology icons
Convention Description
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that
supports Layer 2 forwarding and other Layer 2 features.
Represents an access controller, a unified wired-WLAN module, or the access
controller engine on a unified wired-WLAN switch.
Represents an access point.
Represents a wireless terminator unit.
T
T

Convention Description
Represents a wireless terminator.
Represents a mesh access point.
Represents omnidirectional signals.
Represents directional signals.
Represents a security product, such as a firewall, UTM, multiservice security
gateway, or load balancing device.
Represents a security module, such as a firewall, load balancing, NetStream, SSL
VPN, IPS, or ACG module.
Examples provided in this document
Examples in this document might use devices that differ from your device in hardware model,
configuration, or software version. It is normal that the port numbers, sample output, screenshots,
and other information in the examples differ from what you have on your device.
Documentation feedback
You can e-mail your comments about product documentation to [e-mail].
We appreciate your comments.
T
T





i
Contents
Managing a 3G/4G modem ································································1
About managing a 3G/4G modem ·································································································1
Restrictions: Hardware compatibility with 3G/4G modem management··················································1
Restrictions and guidelines: 3G/4G modem management···································································1
3G/4G modem management tasks at a glance·················································································2
Configuring the 3G modem cellular interface····················································································2
Configuring the 4G modem cellular interface····················································································3
Configuring an Eth-channel interface for a 4G modem ·······································································3
Configuring basic parameters for an Eth-channel interface···························································3
Restoring the default settings for an Eth-channel interface ···························································4
Configuring an IP address for an Eth-channel interface of a 4G modem··········································4
Configuring a 3G/4G network ·······································································································5
Configuring parameter profiles······································································································6
About parameter profiles·······································································································6
Creating a parameter profile for a 3G modem············································································6
Creating a parameter profile for a 4G modem············································································6
Specifying the primary and backup profiles ···············································································7
Specifying the primary or secondary SIM card··················································································7
Associating 3G/4G link backup with a track entry··············································································8
Configuring PIN verification··········································································································8
Configuring DM ·························································································································9
Setting the RSSI thresholds ·········································································································9
Issuing a configuration directive to a 3G/4G modem········································································10
Configuring 3G/4G modem reboot·······························································································56H10
24HConfiguring automatic reboot ·······························································································57H10
25HConfiguring manual reboot ··································································································58H11
26HBinding the IMSI of the SIM card to an interface ·············································································59H11
27HDisplay and maintenance commands for 3G/4G modem management ················································60H11
28H3G/4G modem management configuration examples·······································································61H12
29HExample: Configuring 4G modem management·······································································62H12
30HTroubleshooting·······················································································································63H13
31HSymptom·························································································································64H13
32HSolution···························································································································65H13

1
Managing a 3G/4G modem
About managing a 3G/4G modem
A 3G/4G modem connects a device to a 3G/4G network.
USB 3G/4G modems are available for the device.
AUSB 3G/4G modem is hot swappable. The device uses a fixed cellular interface to manage a USB
3G/4G modem. You can enter cellular interface view to perform configurations when the device does
not have a USB 3G/4G modem installed. The configurations remain after the USB 3G/4G modem is
removed from the device.
A cellular interface can be channelized into a serial or an Eth-channel interface. The data link layer
protocols of the serial interface and Eth-channel interface are PPP and Ethernet, respectively. The
two interfaces support IP at the network layer.
The cellular interface of a 3G modem can only be channelized into a serial interface. The cellular
interface of a 4G modem can only be channelized into an Eth-channel interface.
Restrictions: Hardware compatibility with 3G/4G
modem management
Hardware Compatibility with 3G/4G modem
management
F5010, F5020, F5020-GM, F5030, F5030-6GW, F5040, F5060,
F5080, F5000-C, F5000-S, F5000-M, F5000-A No
F1005, F1010 Yes
F1020, F1020-GM, F1030, F1050, F1060, F1070, F1070-GM,
F1080 No
F1003-L, F1005-L Yes
F1000-AK108, AK109, AK110, AK115, AK120, AK125 Yes
F1000-AK130, AK135, AK140, AK145, AK150, AK155, AK160,
AK165, AK170, AK175, AK180, AK185 No
LSU3FWCEA0, LSUM1FWCEAB0, LSX1FWCEA1 No
LSXM1FWDF1, LSUM1FWDEC0, IM-NGFWX-IV,
LSQM1FWDSC0, LSWM1FWD0, LSPM6FWD,
LSQM2FWDSC0 No
Restrictions and guidelines: 3G/4G modem
management
Follow these restrictions and guidelines when you configure 3G/4G modem management:
•Do not remove a USB 3G/4G modem while it is transmitting data. As a best practice, execute
the shutdown command to shut down the USB 3G/4G modem before removing it.

2
•AUSB 3G/4G modem is not usable when the USB interface to which the modem is attached is
shut down. For more information about shutting down a USB interface, see Fundamentals
Configuration Guide.
•Unless otherwise noted, the 3G/4G modem configuration in this document is saved in the NVM
of the 3G/4G modem. To verify the configuration, use the display cellular command.
3G/4G modem management tasks at a glance
To management a 3G/4G modem, perform the following tasks:
1. Configuring the 3G/4G modem cellular interface
{Configuring the 3G modem cellular interface
{Configuring the 4G modem cellular interface
2. Configuring an Eth-channel interface for a 4G modem
3. Configuring a 3G/4G network
4. Configuring parameter profiles
5. (Optional.) Specifying the primary or secondary SIM card
6. (Optional.) Associating 3G/4G link backup with a track entry
7. (Optional.) Configuring PIN verification
8. (Optional.) Configuring DM
9. (Optional.) Setting the RSSI thresholds
10. (Optional.) Issuing a configuration directive to a 3G/4G modem
11. (Optional.) Configuring 3G/4G modem reboot
{Configuring automatic reboot
{Configuring manual reboot
12. Binding the IMSI of the SIM card to an interface
Configuring the 3G modem cellular interface
1. Enter system view.
system-view
2. Enter cellular interface view.
controller cellular cellular-number
3. (Optional.) Configure a description for the cellular interface.
description text
By default, the description for a cellular interface is interface name Interface, for example,
Cellular 2/4/0 Interface.
4. Channelize the cellular interface into a synchronous/asynchronous serial interface.
serial-set set-number
This command names the serial interface as serial cellular-number:set-number.
Configure PPP and DDR, and specify an IP address for the serial interface channelized from
the cellular interface of a 3G modem as needed.
5. Bring up the cellular interface.
undo shutdown
By default, a cellular interface is up.

3
Configuring the 4G modem cellular interface
1. Enter system view.
system-view
2. Enter cellular interface view.
controller cellular cellular-number
3. Configure a description for the cellular interface.
description text
By default, the description for a cellular interface is interface name Interface, for example,
Cellular 2/4/0 Interface.
4. Channelize the cellular interface into an Eth-channel interface.
eth-channel channel-number
This command names the Eth-channel interface as eth-channel
cellular-number:channel-number.
Configure DDR and specify an IP address for the Eth-channel interface channelized from the
cellular interface of a 4G modem as needed.
5. Bring up the cellular interface.
undo shutdown
By default, a cellular interface is up.
Configuring an Eth-channel interface for a 4G
modem
Configuring basic parameters for an Eth-channel interface
1. Enter system view.
system-view
2. Enter Eth-channel interface view.
interface eth-channel interface-number
3. Configure a description of the Eth-channel interface.
description text
By default, the description for an Eth-channel interface is interface name Interface, for example,
Echannel 2/4/0:0 Interface.
4. Set the MTU for the Eth-channel interface.
mtu size
By default, the MTU for an Eth-channel interface is 1500 bytes.
5. Set the expected bandwidth of the Eth-channel interface.
bandwidth bandwidth-value
By default, the expected bandwidth (in kbps) of an Eth-channel is the interface baud rate
divided by 1000.
The baud rate of an Eth-channel interface is 100 Mbps.
6. Bring up the Eth-channel interface.
undo shutdown
By default, the Eth-channel interface is up.

4
Restoring the default settings for an Eth-channel interface
Restrictions and guidelines
CAUTION:
Restoring the default interface settings might interrupt ongoing network services. Make sure you are
fully aware of the impact of this command when you use it on a live network.
The default command might fail to restore the default settings for some commands for reasons
such as command dependencies and system restrictions. Use the display this command in
interface view to identify these commands. Then use their undo forms or follow the command
reference to individually restore their default settings. If your restoration attempt still fails, follow the
error message instructions to resolve the problem.
Procedure
1. Enter system view.
system-view
2. Enter Eth-channel interface view.
interface eth-channel interface-number
3. Restore the default configurations.
default
Configuring an IP address for an Eth-channel interface of a
4G modem
About obtaining an IP address for an Eth-channel interface
An Eth-channel interface can communicate with other devices only after it obtains an IP address.
You can configure an IP address for an Eth-channel interface in the following ways:
•DHCP—The Eth-channel interface obtains the modem's IP address as its own IP address
through DHCP. The modem's IP address is automatically allocated by the service provider.
•Modem manufacturer's proprietary protocol—The Eth-channel interface obtains the
modem's IP address as its own IP address through the modem manufacturer's proprietary
protocol. The modem's IP address is automatically allocated by the service provider.
•Manual configuration.
The ways for the Eth-channel interface to obtain an IP address are mutually exclusive. The most
recent configuration overrides the previous one.
Restrictions and guidelines
Changing the IP address will result in dialup interruption. Immediate re-dialup upon interruption
might not be supported by service providers.
Procedure
1. Enter system view.
system-view
2. Enter Eth-channel interface view.
interface eth-channel interface-number
3. Configure an IP address for the Eth-channel interface in one of the three ways.
{Obtain an IP address by using DHCP.
ip address dhcp-alloc

5
For more information about the command, see DHCP commands in Layer 3–IP Service
Command Reference.
{Obtain an IP address by using the modem-manufacturer's proprietary protocol.
IPv4:
ip address cellular-alloc
IPv6:
ipv6 address cellular-alloc
{Configure an IP address manually.
ip address ip-address {mask-length |mask }[sub ]
By default, no IP address is configured for an Eth-channel interface.
Configuring a 3G/4G network
Restrictions and guidelines
Both 3G and 4G modems can access GSM, CDMA2000, TD-SCDMA, and WCDMAnetworks. Only
4G modems can access LTE networks.
A 3G/4G modem is used to search a public land mobile network (PLMN) for accessible mobile
networks. A PLMN is uniquely identified by the mobile country code (MCC) and the mobile network
code (MNC). Some 3G/4G modems can automaticallyaccess a mobile network. To manually specify
a mobile network for a 3G modem, first search for available mobile networks.
Procedure
1. Enter system view.
system-view
2. Enter cellular interface view.
controller cellular interface-number
3. (Optional.) Search for PLMNs.
plmn search
4. Configure a PLMN searching mode.
plmn select {auto |manual mcc mnc }
The default setting depends on the modem model.
5. Specify the network service to which the modem connects.
mode {1xrtt |auto |evdo |gsm |gsm-precedence |hybrid |lte |td |
td-precedence |wcdma |wcdma-precedence }
The default setting for this command and support for the arguments depend on the modem
model.
6. (Optional.) Specify a GSM frequency band.
gsm band {egsm900 |gsm450 |gsm480 |gsm750 |gsm850 |gsm1800 |gsm1900
|pgsm900 |rsgm900 }
By default, no GSM frequency band is specified.
This command is supported only by Sierra MC7354 (ATT version) and MC7304 4G modules.
7. (Optional.) Specify a WCDMA frequency band.
wcdma band {wcdma800 |wcdma850 |wcdma900 |wcdma1700ip |wcdma1700us
|wcdma1800 |wcdma1900 |wcdma2100 |wcdma2600 }
By default, no WCDMA frequency band is specified.
This command is supported only by Sierra MC7354 (ATT version) and MC7304 4G modules.

6
8. (Optional.) Specify an LTE frequency band.
lte band band-number
The default setting for this commandand support for the band-number argument depend on the
4G modem model.
Configuring parameter profiles
About parameter profiles
A parameter profile defines the following items:
•The access point with which a 3G/4G modem is associated.
•The authentication mode in which the service provider authenticates the 3G/4G modem.
Creating a parameter profile for a 3G modem
1. Enter system view.
system-view
2. Enter cellular interface view.
controller cellular interface-number
3. Create a parameter profile.
profile create profile-number {dynamic |static apn }
authentication-mode {none |{chap |pap }user username [password
password ]}
The default setting depends on the modem model.
Creating a parameter profile for a 4G modem
1. Enter system view.
system-view
2. Create a parameter profile and enter its view.
apn-profile profile-name
3. Specify the PDP data carrying protocol.
pdp-type {ipv4 |ipv6 |ipv4v6 }
By default, the data carrying protocol is IPv4 and IPv6.
4. Specify an APN.
apn {dynamic |static apn }
By default, no APN is specified.
5. Specify an authentication mode for accessing a 4G network.
authentication-mode {pap |chap |pap-chap }user user-name password
{cipher |simple }string
By default, no authentication is performed for accessing a 4G network.
6. Specify a separator for the IMSI/SN binding authentication information.
attach-format imsi-sn split splitchart
By default, no separator is specified for the IMSI/SN binding authentication information.

7
Specifying the primary and backup profiles
About the primary and backup profiles
By default, profile 1 is used for 3G/4G modem dialup. The dialup fails if profile 1 does not exist.
You can also specify the primary and backup profiles for 3G/4G modem dialup. The primary profile
always has priority over the backup profile. For each dialup connection establishment, the 3G or 4G
modem uses the backup profile only when it has failed to dial up using the primary profile.
Restrictions and guidelines
You must configure the same username and password for the primary and backup profiles.
Specifying the primary and backup profiles for a 3G modem
1. Enter system view.
system-view
2. Enter cellular interface view.
controller cellular interface-number
3. Specify the primary and backup profiles for the 3G modem.
profile main main-profile-number backup backup-profile-number
By default, profile 1 is used for 3G modem dialup.
Specifying the primary and backup profiles for a 4G modem
1. Enter system view.
system-view
2. Enter Eth-channel interface view.
interface eth-channel interface-number
3. Specify the primary and backup profiles for the 4G modem.
apn-profile apply profile-name [backup profile-name ]
By default, no profiles are specified for 4G modem dialup.
Specifying the primary or secondary SIM card
About specifying the primary or secondary SIM card
On a device that uses dual SIM card, youcan specify the use of the secondary SIM card when one of
the following problems occurs:
•The 3G/4G link signals of the primary SIM card are weak.
•The service provider network that the primary SIM card connects to is unavailable.
•The primary SIM card has failed.
If the problems of the primary SIM card are resolved, you can specify the use of the primary SIM card
or enable the 3G/4G modem to automatically switch back to the primary SIM card.
Procedure
1. Enter system view.
system-view
2. Enter cellular interface view.
controller cellular interface-number
3. Specify the primary or secondary SIM card.

8
sim switch-to card-number
By default, a 3G/4G modem uses the primary SIM card.
4. Enable the 3G/4G modem to automatically switch back to the primary SIM card.
sim switch-back enable [wait-time time ]
By default, automatic switchback to the primary SIM card is disabled.
Associating 3G/4G link backup with a track entry
About associating 3G/4G link backup with a track entry
This configuration allows the system to use a track entry to monitor the status of the primary 3G/4G
link. When the track entry state changes from Positive to Negative, the secondary 3G/4G link takes
over.
Procedure
1. Enter system view.
system-view
2. Enter cellular interface view.
controller cellular interface-number
3. Associate 3G/4G link backup with a track entry
sim backup enable track entry-number
By default, 3G/4G link backup is not associated with a track entry.
Configuring PIN verification
About PIN verification
A UIM card is used in the CDMA network and a SIM card is used in other mobile networks. Each
SIM/UIM card has a Personal Identification Number (PIN). PIN verification prevents unauthorized
access to the SIM/UIM card.
To perform PIN verification, you need to save the PIN of the SIM/UIM card on the device by using the
pin verify command and enable PIN verification. The pin verify command can be executed before
and after you enable PIN verification. After the PIN is saved on the device, the PIN is used for
verification automatically when required.
When PIN verification is enabled, PIN verification is performed after you perform any of the following
tasks:
•Install a 3G/4G modem.
•Reboot the device where a USB 3G/4G modem is attached.
•Execute the modem reboot command to reboot a 3G/4G modem.
•Hot swap a USB 3G/4G modem.
•Cold boot the device where a SIC-3G/4G modem is installed.
If PIN verification fails after a maximum number of attempts, the SIM/UIM card is locked, and a PIN
Unlocking Key (PUK) is required to unlock the card. The maximum number of attempts depends on
the 3G/4G modem model.
Procedure
1. Enter system view.
system-view
2. Enter cellular interface view.

9
controller cellular interface-number
3. Enable PIN verification.
pin verification enable [pin ]
The default setting depends on the modem model.
Whether you are required to enter the PIN when enabling PIN verification depends on the
modem model.
4. Specify the PIN for verification.
pin verify {cipher |simple }string
By default, no PIN is configured on a device for 3G/4G modem verification.
This command saves the PIN on the device.
5. (Optional.) Specify a PUK to unlock the SIM/UIM card.
pin unlock puk new-pin
After the SIM/UIM card is unlocked, execute the pin verify command to save the new PIN
on the device.
6. (Optional.) Modify the PIN of the SIM/UIM card.
pin modify current-pin new-pin
The new PIN is saved in the SIM/UIM card.
After the PIN is modified, execute the pin verify command to save the new PIN on the
device.
Configuring DM
NOTE:
Support for DM depends on the modem model.
About DM
Diagnostic and monitoring (DM) allows third-party debugging tools to diagnose and monitor the
3G/4G modem through cellular interface debugging output. For more information about DM, see
related 3G/4G modem user manuals.
Procedure
1. Enter system view.
system-view
2. Enter cellular interface view.
controller cellular interface-number
3. Enable DM.
dm-port open
The default setting for this command depends on the modem model.
Setting the RSSI thresholds
About setting the RSSI thresholds
After setting the RSSI thresholds, you will stay informed about the RSSI changes.
Procedure
1. Enter system view.

10
system-view
2. Enter cellular interface view.
controller cellular interface-number
3. Set the RSSI thresholds.
rssi {gsm |1xrtt |evdo |lte }{low lowthreshold |medium
mediumthreshold }
By default, the lower and upper RSSI thresholds for a 3G/4G modem are–150 dBm and 0 dBm,
respectively.
The value of lowthreshold cannot be smaller than the value of mediumthreshold
because the system automatically adds a negative sign to the RSSI thresholds.
Issuing a configuration directive to a 3G/4G
modem
Restrictions and guidelines
Configuration directives might cause malfunction of a 3G/4G modem. When you issue a
configuration directive to the modem, make sure you understand the impact on the 3G/4G modem.
Procedure
1. Enter system view.
system-view
2. Enter cellular interface view.
controller cellular interface-number
3. Issue a configuration directive to the 3G/4G modem.
sendat at-string
Configuring 3G/4G modem reboot
Configuring automatic reboot
About automatic reboot
The 3G modem might malfunction in an unstable 3G network or when the application environment
changes. During a malfunction, the modem cannot respond to the device's requests or configuration
commands. If the device does not receive any responses from the 3G modem within the timeout
interval, a response failure occurs. When the number of consecutive response failures reaches the
threshold, the device restarts the 3G modem automatically.
The device does not restart the 3G modem when the 3G modem has not made a successful dialup
since the last restart. This restriction avoids repeated restarts of the 3G modem when there are
configuration errors.
Procedure
1. Enter system view.
system-view
2. Enter cellular interface view.
controller cellular interface-number
3. Configure the response timeout and the threshold for the number of consecutive timeouts to
enable automatic reboot of the 3G/4G modem.

11
modem response timer time auto-recovery threshold
By default, the response timeout is 10 seconds and the consecutive timeout threshold is 3.
The configuration is saved on the device rather than the 3G/4G modem.
Configuring manual reboot
About manual reboot
A 3G/4G modem can automatically detect running errors and reboot. If the 3G/4G modem fails to
reboot by itself, you can use this command to manually reboot it.
Procedure
1. Enter system view.
system-view
2. Enter cellular interface view.
controller cellular interface-number
3. Manually reboot the 3G/4G modem.
modem reboot
Binding the IMSI of the SIM card to an interface
About binding the IMSI of the SIM card to an interface
The device must support PPP LCP negotiation of the IMSI/SI when it acts as a LAC to access the
LNS in LAC-auto-initiated mode. After you bind the IMSI on the SIM card to a virtual PPP interface,
the packets sent by the device carry the IMSI.
Restrictions and guidelines
This feature is not available for distributed devices or devices operating in IRF mode.
Procedure
1. Enter system view.
system-view
2. Enter cellular interface view.
controller cellular interface-number
3. Bind the IMSI on the SIM card to an interface.
imsi bind interface-type interface-number
By default, the IMSI on the SIM card is not bound to any interface.
Display and maintenance commands for 3G/4G
modem management
Execute display commands in any view and the reset command in user view.
Task Command
Display the call connection information
for the 3G/4G modem. display cellular [interface-number ]
Display information about a cellular display controller [cellular

12
Task Command
interface. [interface-number ]]
Display information about an
Eth-channel interface. display interface [eth-channel
[channel-id ]][brief [description |down ]]
Clear the statistics for a cellular
interface. reset counters controller [cellular
[interface-number ]]
Clear the statistics for an Eth-channel
interface. reset counters interface [eth-channel
[channel-id ]]
3G/4G modem management configuration
examples
Example: Configuring 4G modem management
Network configuration
As shown in Figure 1:
•The router provides a USB 4G or SIC-4G modem.
•The PC dials up to access an LTE network through Dial-on-Demand Routing (DDR).
For more information about DDR dialup, see "Configuring DDR."
Figure 1 Network diagram
Procedure
# Configure dialer group 1 and configure DDR to place calls for IP packets.
<Router> system-view
[Router] dialer-group 1 rule ip permit
# Channelize the cellular interface into an Eth-channel interface.
[Router] controller cellular 2/4/0
[Router-Cellular2/4/0] eth-channel 0
[Router-Cellular2/4/0] quit
# Configure an IP address for Eth-channel 2/4/0:0.
[Router] interface eth-channel 2/4/0:0
[Router-Eth-channel2/4/0:0] ip address cellular-alloc
# Enable traditional DDR on Eth-channel 2/4/0:0.
[Router-Eth-channel2/4/0:0] dialer circular enable
# Associate Eth-channel 2/4/0:0 with dialer group 1.
[Router-Eth-channel2/4/0:0] dialer-group 1
# Set the interval for DDR to make the next call attempt to 5 seconds.
[Router-Eth-channel2/4/0:0] dialer timer autodial 5
LTE network
Router
PC

13
# Configure the dial string for placing calls as 666666.
[Router-Eth-channel2/4/0:0] dialer number 666666
Troubleshooting
Symptom
A 3G/4G modem fails to function correctly. For example, the 3G/4G modem receives no signals or
fails to connect to service providers' networks.
Solution
To resolve the issue:
1. Execute the shutdown command and the undo shutdown command on the cellular
interface.
2. If the 3G/4G modem still fails to function,execute the modem reboot command on the cellular
interface.
3. If the issue persists, contact H3C Support.

i
Contents
Configuring PPP ··············································································1
About PPP ·······························································································································1
PPP protocols·····················································································································1
PPP link establishment process······························································································1
PPP authentication··············································································································2
PPP for IPv4 ······················································································································2
PPP for IPv6 ······················································································································3
PPP tasks at a glance·················································································································4
Configuring PPP authentication·····································································································4
About PPP authentication ·····································································································4
Configuring PAP authentication······························································································5
Configuring CHAP authentication (authenticator name is configured)··············································5
Configuring CHAP authentication (authenticator name is not configured)·········································7
Configuring MS-CHAP or MS-CHAP-V2 authentication ·······························································7
Configuring the polling feature ······································································································8
Configuring PPP negotiation·········································································································9
Configuring the PPP negotiation timeout time············································································9
Configuring IP address negotiation on the client·········································································9
Enabling IP segment match·································································································10
Configuring DNS server IP address negotiation on the client ······················································10
Configuring ACFC negotiation······························································································11
Configuring PFC negotiation································································································11
Enabling IP header compression·································································································12
Enabling PPP link quality monitoring····························································································13
Configuring the NAS-Port-Type attribute·······················································································14
Enabling PPP accounting ··········································································································63H14
26HDisplay and maintenance commands for PPP················································································64H15
27HConfiguring PPPoE·········································································65H16
28HAbout PPPoE··························································································································66H16
29HPPPoE network structure····································································································67H16
30HConfiguring a PPPoE client········································································································68H17
31HOperation mode················································································································69H17
32HPPPoE client tasks at a glance·····························································································70H17
33HConfiguring a dialer interface ·······························································································71H18
34HConfiguring a PPPoE session ······························································································72H19
35HResetting a PPPoE session·································································································73H19
36HDisplay and maintenance commands for PPPoE ············································································74H19
37HDisplay and maintenance commands for PPPoE client······························································75H19