Hello,

I've installed ROS 7.1b2 iso on a Supermicro server with x710 and 82599ES chipset cards, and I saw that all information related to SFP are not displayed on both.

There is any plan to fix this?

Hello,

I've installed ROS 7.1b2 iso on a Supermicro server with x710 and 82599ES chipset cards, and I saw that all information related to SFP are not displayed on both.

There is any plan to fix this?

Code: Select all

[admin@MikroTik] > interface/ethernet/monitor ether9
                   name: ether9
                 status: no-link
  default-cable-setting: standard

[admin@MikroTik] > system/resource/pci/ print
   33  06:00.0  Intel Corporation         82599ES 10-Gigabit SFI/SFP+ Network Connection (rev: 1)         11
   34  06:00.1  Intel Corporation         82599ES 10-Gigabit SFI/SFP+ Network Connection (rev: 1)         10
   35  09:00.0  Intel Corporation         Ethernet Controller X710 for 10GbE SFP+ (rev: 2)         11
   36  09:00.1  Intel Corporation         Ethernet Controller X710 for 10GbE SFP+ (rev: 2)         11
   37  09:00.2  Intel Corporation         Ethernet Controller X710 for 10GbE SFP+ (rev: 2)         11
   38  09:00.3  Intel Corporation         Ethernet Controller X710 for 10GbE SFP+ (rev: 2)         11

4 years later, we're at 7.14.2, and this feature that is really important is missing.
I'm just wondering if, since Mikrotik core business after all is sell hardware, is a conscious choice or just a bug or something left over since it's not a priority.
Any official statement will be appreciated, since my CHR trial is ending, and this part is definitely important to understand if stay with CHR or use other OS.

When running CHR in a virtual machine, all NICs and drivers are managed by the virtual host.

When running CHR in a virtual machine, all NICs and drivers are managed by the virtual host.

No, they can also be PCI Passthought linked devices.

As I wrote in another thread, PCIe passthrough and IO-SRV require specially tailored drivers from the manufacturer, i.e. not something MT is involved with. Additionally, special APIs are needed to manage the driver, and these must be adopted by CHR for each new device to enable ROS management a scenario that probably won’t happen.

Was working ok in ROS v6