This article discusses the data collection required for troubleshooting connection problems through LTE modem on NFX150.
To troubleshoot LTE problems, first verify if settings are correct. Confirm the following parameters:
root@bj340a> request modem wireless create-profile ? Possible completions: <interface-name> Name of physical interface cl-1/0/0 access-point-name Access Point Name (APN) <-- must be correct authentication-method Authentication method <-- if authentication required by ISP ip-version IP Version <-- optional, if ISP doesn't support IPv6, must set it to IPv4-only profile-id Profile Id (1..16) sip-password SIP Password <-- Must be matching, if authentication required sip-user-id SIP User ID <-- Must be matching, if authentication required slot SIM slot number (1..2)
All events regarding the LTE connection, like creation attempt, success, failure with call end, and network states are logged to syslog as info level. It is advisable to re-configure your syslog to record info level logs to the messages file.
set system syslog file messages pfe info
If you cannot determine reason for the connection problem based on the LTE logs in messages file, then further debugging will be needed from the PFE on FPC1.
To collect LTE debugs, go to the shell prompt and issue the command, vty fpc1 .
vty fpc1
root@t01-40:~ # vty fpc1 TOR platform (2199 Mhz Intel(R) Xeon(R) processor, 232MB memory, 8192KB flash) FLOWD_NFX_3(t01-40 vty)#
From here, run the command, debug mlte 1 get_log
debug mlte 1 get_log
This will collect LTE debugging information, and it will write it to hypervisor, /var/tmp/mlte_debug.tgz file. To extract this file, copy it from /var/tmp to /var/public
root@t01-40-node:/var/tmp# cp mlte_debug.tgz /var/public root@t01-40-node:/var/tmp#
Now scp or sftp from /var/public/mlte_debug.tgz to your local desktop. Then upload this file to JTAC for further analysis.
scp
sftp