Between a switch and TrueNAS -
I'd stay away from LAG config, where both link are active at the same time. Instead one link should be active and the other standby for redundancy. Both active never worked well for me (I think they also discourage this somewhere in docs).
I found the original explanation about spanning tree, the one I had mentioned 2 pages before (which did not help you).
STP is off by default with the l3 OS image (off globally and off per vlan), but remains "ON" per port, meaning ports are eligible to participate in an...
Sorry to hear that. It definitely helped in my case, even though the logic behind this had been unclear to me. Furthermore I also tried to find any log relevant to that port blocking and wasn't able to spot anything.
If that helps any, I've been using Mellanox X3 (flashed to ethernet) with both...
I had exactly the same problem as you.
Try to add the line to each physical interface:
interface ethernet 1/2/1
Let me know if that helps.
The explanation is somewhere within this thread. I think it was about spanning tree being active...
That seems pretty hot. Maybe there is not enough room around the switch for proper cooling with all the POE stuff going on?
In any case you could look at that thread:
If you don't care about the noise...
You have old stacking configs still lingering on your switch. You have to delete them and reload.
I don't remember if you can do it from bootloader level too, but the below OS console method works for sure:
over serial (will not work over telnet/ssh)
#at any OS level:
#press ctrl+y, let go...
I did 6610 cooling modification, but less ambitious than all of the above.
I did not care about the PSU noise, so I skipped the whole 'cheat the RPM detection sensor' thing.
Simply cut a 3mm plexiglass sheet to size, drilled and countersunk all mounting screws as well as fan screws.
Where should be a collection point(s) in a typical homelab network, in which you have physical switch(es) with virtual switches (dvSwitches) connected to them?
Export from all switches? Will there be duplicate flows recorded then?
Yes, I meant pasting to terminal (I've been doing that for Cisco switches in the past) or TFTP.
As you noted, some sensitive stuff would need to be recreated manually (passwords, keys).
Quite possibly the SSH key could also be copied back and forth with TFTP.
I haven't tried myself, but looks the config Oxidized saves is ready to be pasted or tftp'd to a switch as-is.
I can see all relevant config there with a correct syntax and irrelevant parts (interrogation) all commented out with "!".
I managed to configure Oxidized to fetch ICX6610 config.
Oxidized SSH library has to be configured to accept older ciphers/kex protocols to be able to connect to the switch.
Ciphers have to be specified in the global section of Oxidized config file, they don't work in groups or models sections...
I have a system with Supermicro XeonD motherboard ( SYS-5019D-FN8TP-2-NC041) running latest ESXi7.03c.
It has one VM for now, TrueNAS SCALE with Intel P4510 passed through.
I experience intermittent PERR followed by CATERR and spontaneous system reboot.
The issue is triggered upon system...
I recently purchased the Supermicro 1U server SYS-5019D-FN8TP with X11SDV-4C-TP8F motherboard inside.
**BIOS is v1.5 (latest)
**JNS1 jumper is moved to position 2-3 to enable NVME-mode for mini-SAS connectors.
I've been trying to connect and use Intel P4510 SSD NVME drive using mini-SAS to U2...