Release 1.0 known bugs and limitations.

[Ilya Baldin]

We’ve outlined some of the known limitations for the current release of FABRIC software (v1.0).

(see https://learn.fabric-testbed.net/knowledge-base/fabric-testbed-release-1-0/)

In addition to those as we go we are discovering bugs – this is the place to discuss these. Here is the summary of bugs we discovered so far:

1. It is not possible to request more than one Shared NIC for a VM.

Resolution: it has been fixed in the next release, not deployed yet

Work-arounds: None

2. Sometimes when requesting a VM with multiple NICs (Shared or Smart) one of them will not pass traffic regardless of the type of network service used.

Resolution: TBD – we are actively investigating the cause We have identified the cause and are working on a fix.

Work-arounds: None

3. Requested slice topology isn’t updated with new information after first query (includes not being able to see updated sliver lifetimes after extending the slice)

Resolution: We are actively investigating

Work-arounds: Wait for a period of time after creating the slice to make sure the topology is populated with all needed information.

4. This limitation is mentioned in the document above, more specifically – connecting multiple Shared NICs that are on VMs on the same physical node to an L2STS service will make it impossible for them to communicate with each other, although they can communicate with other VMs on other worker nodes/sites.

Resolution: This is a limitation of our dataplane and will not be resolved (it is part of the ASIC hardware). Our dataplane switches lack the ability to perform the ‘hair-pin’ that is required in this case (send traffic down one VLAN and receive on a different VLAN on the same physical port).

Work-arounds: Newer versions of user libraries will disallow these scenarios to avoid confusion.

5. Giving multiple NICs the same name within a slice results in some of their ports not being connected. This bug manifests similar to 2, however is separate and, more importantly, there is a workaround. This will be fixed in newer versions of user libraries.

Work-arounds: Make sure your NICs all have unique names within a slice

• This topic was modified 3 years ago by Ilya Baldin.
• This topic was modified 3 years ago by Ilya Baldin.
• This topic was modified 2 years, 12 months ago by Ilya Baldin.
• This topic was modified 2 years, 12 months ago by Ilya Baldin.

[Author]

Posts