Bug 435503
Summary: | openmpi gets confused with multiple HCAs | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Gurhan Ozen <gozen> |
Component: | openmpi | Assignee: | Doug Ledford <dledford> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.2 | CC: | jburke |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-03-03 18:03:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Gurhan Ozen
2008-02-29 19:05:40 UTC
This isn't a bug. The warning is correct. The common IB setup method doesn't use link aggregation on the same subnet, it usually involves links to redundant fabrics. That means that port 1 and port 2 are usually on different networks. If they both have the same GID prefix, but are on two networks, then openmpi will fail to run. So, whenever openmpi detects what looks like the uncommon "dual links on single subnet" configuration, it prints the warning above in case the machine really is on two subnets but the admins simply forgot to configure opensm to have a different GID prefix on the different subnets (it's impossible for openmpi to know if the links are *actually* on the same subnet). If the person checks things out and determines that this is in fact all correct and good and the machine is on the same subnet with both ports, then the user can add the option listed in the warning in order to shut the warning up. |