MTCDTIP-L4E1-279L-868 (GW3) unable to access (no network, no reset)
Home › Forums › Conduit: mLinux Model › MTCDTIP-L4E1-279L-868 (GW3) unable to access (no network, no reset)
Tagged: conduit unresponsive, factory, Reset
- This topic has 10 replies, 3 voices, and was last updated 2 years, 8 months ago by
Steve Kovarik.
-
AuthorPosts
-
May 3, 2022 at 9:35 am #32688
sebastian barillaro
ParticipantDear Support team,
After reading all the topics on the forum, documentation, and spending the whole day trying to access the device, I decided to create this post.
I have a brand new LoRaWAN Gateway MTCDTIP-L4E1-279L-868 DOM:2020.01.21, that I bought a year ago. I could not have the time for using this specific device until now.
To my surprise, the device is unresponsive. My computer has IP 192.168.2.20. However, I receive nothing when I ping 192.168.2.1
I also cannot ssh the device.The device has a solid green PR light on. The ST light is solid red with a hearth-bit blinking on green (without affecting the red light).
I tried many many times to reset to factory defaults. 3, 5, 30, 45, 60, 120 seconds… no way. On all the trials over the 30 seconds, it happens that the ST red light turns off, while the green heart beating remains blinking for a couple of seconds. Then, all the three lights (PR green + ST green and red) go on solid for about 30 seconds. after that, the heartbeat starts again. I monitor the network with a constant ping that is never responded.
I have a TFTP server running on my computer publishing a folder with two identical files in it: https://webfiles.multitech.com/wireless/mLinux/mLinux%205.3.31/MTCDT/mlinux-commissioning-image-mtcdt-upgrade.bin
The same file is also published with the name oe_uImage.binI also copied the file oe_uImage.bin into a USB-Memory that I connected to the USB port of the Gateway with the hope it could be read and flash the new firmware image after a reboot.
I connected a double USB-A cable to my computer. I also connected a phone with OTG cable. None of those devices detected anything on the USB port.
On one of the resetting tries, the device started to respond to the pings. I was able to log in using ssh. The connection was super laggy at that time. The ping-response took almost a second, while there were many pings lost. Anyway, I was able to execute a couple of commands before the device kicked me out. Unfortunately, this happened only once.
See below the log of that ocassion:mtcdt:/etc$ cat ./version 20191018234646 mtcdt:/etc$ top top - 23:21:34 up 14 min, 1 user, load average: 1.02, 1.01, 0.71 Tasks: 86 total, 1 running, 85 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.3 us, 3.2 sy, 0.0 ni, 95.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 252568 total, 219528 free, 17940 used, 15100 buff/cache KiB Swap: 0 total, 0 free, 0 used. 227956 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1219 mtadm 20 0 3044 1464 1124 R 4.1 0.6 0:00.78 top 1 root 20 0 1744 704 636 S 0.0 0.3 0:07.46 init 2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd 3 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0 5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H 7 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_preempt 8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_sched 9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh 10 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 lru-add-drain 11 root rt 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/0 12 root 20 0 0 0 0 S 0.0 0.0 0:00.07 kdevtmpfs 13 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns 14 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khungtaskd 15 root 20 0 0 0 0 S 0.0 0.0 0:00.00 oom_reaper 16 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 writeback 17 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kcompactd0 18 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 crypto 19 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset 20 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd 21 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 watchdogd 22 root 20 0 0 0 0 D 0.0 0.0 0:00.41 kworker/0:1 23 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kswapd0 47 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset 48 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset 49 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset 50 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset 51 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset 52 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset 53 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset 54 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset 55 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset 56 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset 57 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset 58 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset 59 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset mtcdt:/etc$ ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.8 0.2 1744 704 ? Ss 23:07 0:07 init [5] root 2 0.0 0.0 0 0 ? S 23:07 0:00 [kthreadd] root 3 0.0 0.0 0 0 ? S 23:07 0:00 [ksoftirqd/0] root 5 0.0 0.0 0 0 ? S< 23:07 0:00 [kworker/0:0H] root 7 0.0 0.0 0 0 ? S 23:07 0:00 [rcu_preempt] root 8 0.0 0.0 0 0 ? S 23:07 0:00 [rcu_sched] root 9 0.0 0.0 0 0 ? S 23:07 0:00 [rcu_bh] root 10 0.0 0.0 0 0 ? S< 23:07 0:00 [lru-add-drain] root 11 0.0 0.0 0 0 ? S 23:07 0:00 [watchdog/0] root 12 0.0 0.0 0 0 ? S 23:07 0:00 [kdevtmpfs] root 13 0.0 0.0 0 0 ? S< 23:07 0:00 [netns] root 14 0.0 0.0 0 0 ? S 23:07 0:00 [khungtaskd] root 15 0.0 0.0 0 0 ? S 23:07 0:00 [oom_reaper] root 16 0.0 0.0 0 0 ? S< 23:07 0:00 [writeback] root 17 0.0 0.0 0 0 ? S 23:07 0:00 [kcompactd0] root 18 0.0 0.0 0 0 ? S< 23:07 0:00 [crypto] root 19 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 20 0.0 0.0 0 0 ? S< 23:07 0:00 [kblockd] root 21 0.0 0.0 0 0 ? S< 23:07 0:00 [watchdogd] root 22 0.0 0.0 0 0 ? S 23:07 0:00 [kworker/0:1] root 23 0.0 0.0 0 0 ? S 23:07 0:00 [kswapd0] root 47 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 48 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 49 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 50 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 51 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 52 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 53 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 54 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 55 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 56 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 57 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 58 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 59 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 60 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 61 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 62 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 63 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 64 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 65 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 66 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 67 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 68 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 69 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 70 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 71 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 72 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 73 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 74 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 75 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 76 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 77 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 78 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 79 0.0 0.0 0 0 ? S< 23:07 0:00 [bioset] root 80 0.0 0.0 0 0 ? S 23:07 0:00 [kworker/u2:1] root 82 0.0 0.0 0 0 ? S< 23:07 0:00 [ipv6_addrconf] root 83 0.0 0.0 0 0 ? D 23:07 0:00 [kworker/0:2] root 98 0.0 0.0 0 0 ? SN 23:07 0:00 [jffs2_gcd_mtd6] root 108 0.1 0.5 3360 1264 ? Ss 23:07 0:01 /sbin/udevd -d root 134 0.0 0.0 0 0 ? S 23:07 0:00 [spi32766] root 135 0.0 0.0 0 0 ? S 23:07 0:00 [spi32765] root 157 0.0 0.0 0 0 ? S< 23:07 0:00 [kworker/0:1H] root 219 0.0 0.0 0 0 ? S 23:07 0:00 [kworker/u2:2] root 459 0.0 0.0 0 0 ? S< 23:07 0:00 [cfg80211] root 600 0.0 0.0 0 0 ? S< 23:07 0:00 [krfcommd] root 864 1.0 0.0 0 0 ? SN 23:07 0:09 [jffs2_gcd_mtd8] message+ 1070 0.0 0.4 2984 1096 ? Ss 23:07 0:00 /usr/bin/dbus-daemon --system root 1076 0.0 0.3 3088 932 ? Ss 23:07 0:00 /usr/sbin/ifplugd -fI -i eth0 -u 0 -d 10 -r /etc/if root 1092 0.0 0.6 4856 1684 ? Ss 23:08 0:00 /usr/sbin/sshd ntp 1113 0.0 1.0 7084 2640 ? S<sl 23:08 0:00 /usr/sbin/ntpd -u ntp:ntp -p /var/run/ntpd.pid -c / root 1118 0.0 0.3 3088 996 ? S 23:08 0:00 /sbin/syslogd -n -O /var/log/messages -s 512 -b 4 root 1121 0.0 0.4 3088 1084 ? S 23:08 0:00 /sbin/klogd -n root 1135 0.1 0.5 4844 1436 ? Ss 23:08 0:01 /usr/sbin/mosquitto -d -c /etc/mosquitto/mosquitto. root 1164 0.0 0.5 3076 1428 ? Ss 23:08 0:00 /usr/sbin/crond root 1170 0.0 0.5 2684 1456 ? S 23:08 0:00 /bin/bash /usr/sbin/reset-handler root 1182 0.0 0.5 2680 1468 ? Ss 23:08 0:00 /bin/sh /bin/start_getty 115200 ttyS0 root 1183 0.0 0.5 2680 1444 ? Ss 23:08 0:00 /bin/sh /bin/start_getty 115200 ttyGS0 root 1185 0.0 0.4 3088 1040 ttyS0 Ss+ 23:08 0:00 /sbin/getty -L 115200 ttyS0 root 1186 0.0 0.3 3088 996 ttyGS0 Ss+ 23:08 0:00 /sbin/getty -L 115200 ttyGS0 root 1197 0.0 0.0 0 0 ? S 23:12 0:00 [kworker/0:0] root 1206 0.0 0.0 0 0 ? S 23:17 0:00 [kworker/0:3] root 1207 0.1 1.0 5684 2644 ? Ss 23:18 0:00 sshd: mtadm [priv] mtadm 1209 0.0 0.9 5684 2384 ? S 23:18 0:00 sshd: mtadm@pts/0 mtadm 1210 0.0 0.7 3000 1940 pts/0 Ss 23:18 0:00 -bash root 1220 0.0 0.0 0 0 ? S 23:21 0:00 [kworker/u2:0] mtadm 1221 0.0 0.4 2828 1160 pts/0 R+ 23:22 0:00 ps auxI have no more ideas on how to proceed. It is also very strange that the device seems to be blocked from the factory since it has never been used before today.
THank you for taking the time reading this long report. And thank you in advance for helping me to solve this issue.
With best regards
Sebastian
May 4, 2022 at 2:44 am #32696ParticipantBefore you ask, the serial number of this Gateway is 20695006.
Thank you for your help.
With best regards
Sebastian
May 4, 2022 at 9:57 am #32698Steve Kovarik
ModeratorHi Sebastian
Can you provide the make/model of the POE Injector you are using to power the MTCDTIP-L4E1-270-868 Gateway.
May 4, 2022 at 10:56 am #32700ParticipantHi Steve,
Thank you for your response. The following are the details of the PoE injector that I am using with the Gateways.
Microsemi
Power over Ethernet Midspan
Model: PD-9501GC/AC
INPUT: 100-240 VAC – 50/60 Hz, 1.5A
OUTPUT: 55V – 1.1ABy the way, I have two of these PoE’s. However, it seems to me that one of these does not work (always blinking in Orange). Thus, I am using the same PoE for all my three GW. One at a time, of course.
With best regards
Sebastian
May 4, 2022 at 3:06 pm #32717ModeratorSebastian
Just a note….for most all of our POE powered Conduit Gateways a 30 Watt POE Injector is recommended.
However you do have the V2.1 Geolocation model that consumes more power than any of our other Gateways.
For the V2.1 model MTCDT-L4E1-270L-868 a 75 Watt POE Injector is recommended.
I notice that the PD-9501GC/AC is rated at 60 Watts.May 5, 2022 at 8:42 am #32722ParticipantDear Steve,
I understand that the PoE injector that I am using could not be delivering the recommended power for this model of devices. However, I find curious that I am using the very same PoE injector to powerise others V2.1 devices. Those devices are able to answer PING on 192.168.2.1
Do you really think that the PoE injector could be the cause of not being able to answer ping? I doubt it, considering that the other devices are working. I would like to explore other solutions while I order a 75W PoE.
Thank you for working together.
With best regards
Sebastian Barillaro
May 5, 2022 at 12:19 pm #32725ModeratorHi Sebastian
Based on LED and device behavior I also doubt that the POE Injector is the cause for the no Ping response.
Since the behavior of this device is not consistent with other working units, sounds like a Support Ticket should be created to have this Gateway looked at.-Best Regards
May 13, 2022 at 3:48 am #32753Nick
ParticipantHi Sebastian
Did you get a resolution / fix for this problem?
I received a MTCDTIP-L4E1-266A-868 yesterday and have exactly the same issue. I’m unable to connect to the web management interface on https://192.168.2.1 via a browser when directly connected via ethernet and setting my PC to 192.168.2.2/24 Gateway 192.168.2.1.
I have managed to connect via the micro USB on the main board and using Putty via a serial connection get onto the Linux OS, I changed the /etc/network/interfaces to DHCP and rebooted, I can now see the Multitech on my home network and it has an address from my DHCP of 192.168.5.101/24 but I still can’t connect to the web management interface.
It’s like the port isn’t open, or the management interface web server isn’t running or something.
Also tried factory reset, still nothing.
Serial number 21874725
May 13, 2022 at 4:15 am #32756ParticipantHi Nick,
I am sorry to hear that you are facing similar problems. However, your case seems to be different. I cannot even ping the device. I have been suggested to fill a Technical Support ticket. That I will do soon.
Your descriptions suit better the issues I have with a second device. It is described on http://www.multitech.net/developer/forums/topic/mtcdtip-l4e1-279l-868-gw1-unable-to-factory-reset/#post-32721 . I am still waiting for an answer on this.
By the way, how did you manage to connect the micro-USB port? I guess you opened the device’s case, right?
With best regards
Sebastian
May 13, 2022 at 5:02 am #32759ParticipantHi Sebastian,
Thanks for the reply, yes I can ping the device and SSH onto it using the mtadm / root credentials that Steve detailed in your other thread.
I still can’t get to the web management interface, think I will get a ticket logged.
Yes, to connect to the micro-USB I opened the case.
Kind regards,
NickMay 13, 2022 at 1:32 pm #32763ModeratorStrange that you have a login issue with these new Gateways.
The Gateway as a DHCP Server out of the box, it should be as easy as browsing to https://192.168.2.1
Alternatively configuring your NIC to be on the same subnet works equally as well.
When ready, you may create a support ticket to have MultiTech further analyze.-Best Regards
-
AuthorPosts
- You must be logged in to reply to this topic.