That is not an easy answer. In the world of UCS, there are several factors that can affect this:
1) Type of IOM (I/O Module) 2) Port config of the IOM (single link or port-channel) 3) Number of inks from the Fabric Interconnect to said IOM 4) Model of adapter in the blade. Depending on the combination of these things, it can be a 10, 20, or 40 GB link. On Wed, Jun 3, 2020, 9:40 PM Lee Trager <1881...@bugs.launchpad.net> wrote: > MAAS 2.7 introduced network testing. As part of network testing we added > the following features which require accurate interface and link speed > information. > > 1. The interface and uplink speeds are now shown in the API and over the > UI. > 2. MAAS now warns when an interface is connected to an uplink which is > slower than its maximum supported speed. > 3. Users may now acquire machines based on its uplink speed. > > I could stop verifying that link speed >= max interface speed however > that will mean 1 is incorrect and 2 is broken. I understand that some > interfaces achieve higher speeds by using more physical ports but > neither ethtool nor LXD give any information on this. > > Does anyone know the proper way to calculate the maximum supported > interface speed on a device like this? > > ** Summary changed: > > - Kernel does not report interface speed correctly for Cisco UCS B200 M5 > blade > + MAAS does not properly detect max interface speed for interfaces which > use multiple phyiscal ports(Cisco UCS B200 M5 blade) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1881821 > > Title: > MAAS does not properly detect max interface speed for interfaces which > use multiple phyiscal ports(Cisco UCS B200 M5 blade) > > Status in MAAS: > Triaged > Status in MAAS 2.7 series: > Triaged > Status in MAAS 2.8 series: > Triaged > Status in linux package in Ubuntu: > Confirmed > > Bug description: > MAAS 2.7.1 > Ubuntu 18.04.4 > > When attempting to commission a Cisco UCS B200 M5 blade, the > commissioning finishes (if smartctl-validate is disabled), however on > the machine in question in the Networking tab, it only shows 2 nics, > eth0 and eth1. and shows no storage. > > Going to SSH in the middle of commissioning, running lshw shows all 10 > NICs, and the disk of the proper size. > > This is causing the buckets.yaml for FCE to be inaccurate, and thus > cannot write a bucketsconfig.yaml since the actual devices don't show > up. > > This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for > commissioning, all have the same behavior. > > I was previously hitting this bug > https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from > comment #10, and am no longer getting any commissioning errors. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881821 Title: MAAS does not properly detect max interface speed for interfaces which use multiple phyiscal ports(Cisco UCS B200 M5 blade) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
