The SFP+ port might need to have the speed manually forced to 1gbps to match the module. I had to contact support for one of my Mikrotik switches because I was having modules that didn’t know how to tell the switch what speed they could use. Use case was the same, 10gbps SFP+ port with 1gbps copper module installed.
After that, I have no experience with your switch, but maybe the above helps. Also after inserting the modules, power cycle the switch. All my old Cisco gear requires a power cycle before they see the modules (2960s and 3560 switches).
Ok, just needed to put an empty enable3px file in /mnt/flash, and power cycle the switch to make the transceivers work (this trick seems to only work on old Arista switches like mine).
You pointed me to the right direction, thank you very much.
Now I need to Everything solved:
clear a “Cpu” port in my VLAN (what’s that?) Solved: whenever I create a vlan interface, the switch shows a “cpu” port among the vlan ports.
see if I can connect the eth management port to the eth port on VLAN 100. I have actually two ports on vlan 100 with the transceivers, I can see my LAN if I connect a port to the LAN and the other to the PC, the PC receives its IP and gets to the internet (actually writing here through the switch’s transceivers). The management port, though, doesn’t seem to get connected to the transceiver. If I change the LAN cable with the management port cable, and put the PC on the same network, it doesn’t ping the switch. The management port is flawlessly connected to VLAN 100, probably just needed some time to get in the network.