No, this was not happening before flashing the module.
We are powering the board at 24V and 0.02A.
What hardware did you use to flash the board? How was the board powered during the flashing process?
We used the ST-Link hardware for flashing the board, as given in the documentation. The board was powered with the same voltage and current as mentioned above.
It appears that the board is damaged. The port lights stuck on, along with the very low power draw (0.48W) implies this.
If this happened after the flashing, then something during the flashing has damaged the board.
Firmware itself would not be capable of doing that, so I suspect there has been some hardware issue here. We’ll need to approve an RMA so you can send the board back to us for inspection. We will follow up on email.
We are under a tight deadline and need multiple switches for our project. If we purchase another UbiSwitch, would you be able to send it to us already flashed with the CLI software? In the meantime, we can work on sending the current switch back for inspection.
Yes. We can do that. To help further, can you provide the specific VLAN configuration, and Aaron will help you with the specific CLI commands to run to achieve that.
What are the next steps we should take to purchase another switch that is flashed?
The configuration that we need was mentioned above:
vlan add port 1 vid 1 pvid untagged
vlan add port 2 vid 1 pvid untagged
vlan add port 3 vid 2 pvid untagged
vlan add port 4 vid 2 pvid untagged
All modules we ship are now flashed with the latest firmware by default.
1 Like
If you send over the VLAN topology you want, I’d be happy to help you with the commands you’ll need to set but based on what I think you’re trying to achieve this is what you need.
For clarification on what the above commands do:
VLAN 1 members: port 1, 2
VLAN 2 members: port 3, 4
Ports 1-4 are treated as access ports with default VLANs, not trunk ports, and no VLAN tag is required to be added to ingress packets on those ports.
2 Likes