I've got MSR954 JH299A 4G router which won't bring up the eth-channel after it reboots the system regardless of the configuration. This results in NTP and DNS services unable to serve the clients, also the clients can't access the internet as the interface is down. The only way to bring it up is to ping a random site by its IP-address on which the physical interface is brought up and everything works. The issue has been present since I got the device and it has to be a setup related problem as I have the same issue on another MSR954 JH299A if it runs on 4G.
On technical level everything is sound as the SIM is inserted and functional, subscription is set and when the interface brings itself up everything works flawlessly.
The setup is following:
DIALER-GROUP 1 RULE IP PERMIT
APN STATIC internet // provider specified only required APN parameter
CONTROLLER CELLULAR 1/0
INT ETH-CHANNEL 1/0:0
IP ADDRESS CELLULAR-ALLOC
APN-PROFILE APPLY 0
DIALER CIRCULAR ENABLE
DIALER NUMBER *99#
IP ROUTE-STATIC 0.0.0.0 0 ETH-CHANNEL 1/0:0
DNS SOURCE-INTERFACE ETH-CHANNEL 1/0:0
I tried to resolve the issue by creating a job which pings my own server to get it up but the reality is after rebooting the scheduler is clear from previously scheduled jobs, thus making forcing to find a solution for the root of the problem as the router is deployed at customer's premise and I can't access it physically. To make it accessing the internet the need is to log into the router and ping by an IP-address.
After reboot command "disp ip int eth-channel" shows:
Eth-channel1/0:0 current state: DOWNLine protocol current state: UP(spoofing)
Eth-channel1/0:0 current state: UPLine protocol current state: UP(spoofing)
Also, the eth-channel tends to shut down itself after an idle period on the interface.
Command "disp cellular 1/0" shows:
Hardware Information: Model: MC7304 Manufacturer: Sierra Wireless, Incorporated Modem Firmware Version: SWI9X15C_05.05.58.00 r27038 carmd-fwbuild1 2015/03/04 21:30:23 Modem Boot Version: SWI9X15C_05.05.58.00 r27038 carmd-fwbuild1 2015/03/04 18:38:46 Firmware Unique ID = 005.026_000 Firmware Build ID = 05.05.58.00_GENEU-4G Configuration Unique ID = 005.026_000 Configuration Build ID = 05.05.58.00_GENEU-4G PRI Version: 9904567 05.00 International Mobile Equipment Identity (IMEI): 356853053359255 International Mobile Subscriber Identity (IMSI): 248022139274040 Hardware Version: 1.0 Modem Status: Online Modem Status: IPv4 Active. Modem Status: IPv6 Unkown. Profile Information: Profile index: 1 PDP Type: IPv4v6 Header Compression: Off Data Compression: Off
Access Point Name (APN): internet Authentication: NONE * - Default profile Network Information: Current Service Status: Service Available Registration Status: Registered Current Service: Combined Current Roaming Status: Home Current Data Bearer Technology: LTE Network Selection Mode: Automatic Current IP address Mode: Cellular-alloc Mobile Network Name: a Mobile Country Code (MCC): 248 Mobile Network Code (MNC): 02 Location Area Code (LAC): 65534 Tracking Area Code(TAC): 2021 Cell ID: 256319509 Radio Information: Technology Preference: LTE only Technology Selected: LTE Configured LTE Band = 1,3,7,8,20 Configured GSM Band = GSM 1800,E-GSM 900,P-GSM 900,GSM 850,GSM 1900 Configured WCDMA Band = WCDMA 2100,WCDMA 1900,WCDMA 850,WCDMA 900
LTE related info: Current RSSI: -66 dBm Current RSRQ: -12 dB Current RSRP: -100 dBm Current SNR: 1 dB Tx Power: Invalid Active Band = E-UTRA Operating Band 3 Modem Security Information: PIN Verification: Disabled PIN Status: PIN Requirement Disabled Number of PIN Retries Remaining: 3 Number of PUK Retries Remaining: 10 SIM Status: OK ICCID: 89372021180330050115 Error Information: IPv4 dialing failed: 0x00: No error in the request IPv6 dialing failed: N/A
GPS Information: GPS Info: GPS State: Enabled GPS Mode Configured: Standalone
I can't get the eth-channel interface up by command "undo shutdown" as its status will remain unchanged - Eth-channel1/0:0 current state: DOWN
Firmware is on Comware version 7.1.064, Release 0809P33 but that's is not an issue as the same problem has been present on the firmwares prior that one.
NTP is configured and enabled but that won't change the behavior of the physical interface.
Can someone advice what else configuration has to be applied to get 4G eth-channel up as its unwillingness to get up when the setup is applied is the root of the issue. I've read all the MSR954 configuration manuals and no, I haven't found anything that would help me resolve the issue by myself.
© Copyright 2023 Hewlett Packard Enterprise Development LPAll Rights Reserved.