Hey Garnet, I know you've had to wait awhile for me to get back to this I apologize but it was unavoidable.
Fortunately, I can finally start working on this again. I've spent the whole day testing this and here is what I've found so far:
My network setup is simple, the WS3 is passing through another WS switch connected to a netgear router acting as the DHCP server.
You can see the results in the logs here:
I tried this many many times using the provided config along with a few variations I setup and I was still unable to replicate the issue's you are showing (that is to say, dhcp provided a lease successfully 100% of the time for me). So I figured what we must be seeing (such as the weird hang times on boot and random reboots etc) must be occurring as a result of something going wrong at this early stage.
Eventually I was able to find out what could cause this.
If I disconnect the network cable to my switch and change from static to DHCP from the console port directly then I was finally able to replicate the issue's you've been mentioning.
The first thing that happened when dhcp inevitably failed to obtain a lease is that the results from
- Code: Select all
show status
Would sometimes show the IP address as "Unknown"
Other times it would catch it when the system reverts to the 169 default IP.
And using the system command:
- Code: Select all
ip addr show
or
- Code: Select all
ifconfig
Showed the ip address to be 169.254.195.50/24 for the vtss.vlan.1 interface.
Which is a default private IP built into the network driver.
Here are the logs of the event:
Here are the results from the above commands (by the time I captured it, it was on an instance where it caught the default ip):
As I started using the switch after this I also started noticing some strange issue's creep up. Reboots might hang for awhile and I've seen a few random reboots during normal operation.
After looking closer this makes sense, parts of the config and status for the switches firmware are not in sync with the underline OS which means null pointers are just waiting to be stepped on depending on events in the system.
So this is definitely a bug, if the dhcp lease acquisition fails I would prefer it to take on the default IP address for the switch and not the one built into the firmware.
However, even if I fix this it won't solve your original problem. I cannot see any reason why dhcp itself would fail without there being some sort of connectivity issue between the WS3 and the DHCP Server provider. Or possibly a compatibility issue if it's maybe a new version for the dhcp server itself and they've changed the protocol? I really doubt that though.
It is still possible there is something wrong with that unit, if you want you can RMA the switch and I will have the factory redirect it too me personally and I will run it through the exact same series of tests I've done on the one I'm currently using.