WS3-14-600-AC arrived yesterday, can't log in

[michaeln416]

I just received a WS3-14-600-AC (arrived March 25th) and I am not able to log into it. No reply from 192.168.1.20 while I'm on the same subnet.
I plugged it into my network and it acquired an IP over DHCP as it booted up. I could see the lease in my router registered to something with a client ID of "estax-71-02-dc" having a MAC address matching the one printed on the bottom of the switch.

I still could not connect to the IP that it leased, nor could I ping it from the router or while plugged into any other port on the switch.

I plugged it into another Netonix switch and tried to use the Discovery tool, but it could not see it either.

I have tried resetting by holding in the DEF button and have gotten the same results.

Is there anything else that I can try (I do not have a console cable around)?

Thanks
Mike

[michaeln416]

Mfg Date: 03/22/2021
v2.0.6rc2 RevD

[Stephen]

Well, first I highly recommend getting a console cable.

Second, are you able to ping it?
If so, ssh is enabled by default, try and connect to it that way and reveal the switches status.

User and password are both "admin" by default.

Post here what you see if that works.

[michaeln416]

More details:

The switch picks up it's DHCP address from my router about 50 seconds after I turn it on. If I am also plugged into the switch with DHCP enabled, my laptop also picks up an IP address at the same time and can browse the web for about 5 to 6 seconds before I lose connectivity.

I have tried browsing to 192.168.1.20 and the DHCP address that it gets from my router during that 5-second window, but still nothing.

Mike

[michaeln416]

Well, first I highly recommend getting a console cable.

Second, are you able to ping it?

I'll order a console cable off of Amazon later today,

No, I am not able to ping it.

[Stephen]

Actually, the fact that it's getting a DHCP address is bizarre, by default it is set to static with:
IP: 192.168.1.20
SUBNET: 255.255.255.0
GATEWAY: 192.168.1.1

So if you are seeing a device being leased an IP at 192.168.1.20 by your DHCP server with the same MAC?

Something here doesn't add up. If you remove the WS3 from the network with the DHCP server and connect to it directly with a laptop that is also on a 192.168.1.0/24 address, are you able to ping it then?

If you are 100% certain there is not a conflict on the network preventing you from seeing the device, or other network mishap and:
- doing a hardware default fails,
- you are unable to access it via web UI,
- you are unable to access it via ssh,
- you are unable to access it via serial console,

Then I don't see how there is a choice other than to RMA it.

[michaeln416]

With the WS3 powered up, not connected to the network, I plug in my laptop with a static IP of 192.168.1.11, I am not able to ping or browse to 192.168.1.20, nor am I able to ping it.

If I then plug the WS3 into the network, after it has already booted up, it will NOT acquire a DHCP address. I still cannot ping it or browse to the UI.

If I reboot the WS3 while it is plugged into the network, it will acquire a DHCP address about 50 seconds after it powers up. The address that it acquired was 192.168.116 as it was on a 192.168.1.x/24 subnet. Looking into the DHCP lease table on my router I could see that address assigned to a device with a Client ID of "estax-71-02-dc" and the exact MAC address of the WS3. However, even during that brief 5 second window mentioned previously, I am not able to ping the device or browse to the UI.

The only thing that I have not tried in your list of suggestions is to access via a serial console cable. One has been ordered and should be here by mid-next week.

[Stephen]

If I reboot the WS3 while it is plugged into the network, it will acquire a DHCP address about 50 seconds after it powers up. The address that it acquired was 192.168.116 as it was on a 192.168.1.x/24 subnet.

Then you have potentially found a bug. I will have to determine if I can replicate it and repair it.

Unfortunately, even if that's so, the tests you've run show that it doesn't explain what's happening to your WS3. Whatever it is might also result in the odd DHCP behavior.

Anyway, when the cable arrives, be sure to connect it and open a session before you power the switch. That way you can capture all of the log messages as it's booting and post them here so we can try and figure out what's going on.

[michaeln416]

Here is the MAC & Client ID of the WS3. Note the unusually formatted Client ID that should instead be 1:ec:12:b2:71:02:ec
https://photos.app.goo.gl/vW3p2AuSxz1Y2Kg28

For comparison, here is MAC address & Client ID on my MikroTik router of two good Netonix switches. They are identical with the addition of a "1:" at the beginning of the Client ID
https://photos.app.goo.gl/7kexWprkB8JE6Knr9

[michaeln416]

We are shipping it back today under an RMA.