Using an NQA Test Instance to Detect a 3G Link
Context
When a 3G link is unstable because of weak 3G signals or noises, you may fail to access an external network through a 3G link even if the dial-up succeeds. To solve this problem, configure the device to use an NQA test instance to detect the 3G link status. When the 3G link is unstable, the device triggers an action to recover the 3G link.
Procedure
- Run the system-view command to enter the system view.
- Run the interface cellular interface-number command to enter the 3G cellular interface view.
- Run the modem auto-recovery track { nqa admin-name test-name | nqa-group group-name } [ probe-cycle period | probe-cycle seconds period-s ] command to reference an NQA or NQA group test instance to detect a 3G link.
By default, a device does not use an NQA or NQA group test instance to detect a 3G link.
Only V300R019C10 and later versions support nqa-group group-name parameter.
The NQA test instance used in this step must be an ICMP NQA test instance. For details about how to configure an ICMP NQA test instance, see Configuring an ICMP Test Instance in NetEngine AR Configuration Guide - Network Management Configuration.
- Run the modem auto-recovery track action { plmn-search | modem-reboot | redial } fail-times times command to set the maximum number of 3G link detection failures in an NQA test instance. When the number of consecutive 3G link detection failures in an NQA test instance reaches the maximum value, the device triggers an action to recover the 3G link.
By default, the maximum number of 3G link detection failures in an NQA test instance is not configured. That is, the device does not trigger an action to recover a 3G link when 3G link detection fails for several consecutive times.
