Internal Reference Number | Issues |
- | Description: On multi PKEY environment, UCX in SHARP can use only the default PKEY (PKEY at index 0). |
Workaround: Use sockets for communication over non-default PKEY. | |
Keywords: Configuration, SMX, UCX, PKEY | |
Discovered in Release: 2.4.3 | |
1307124 | Description: Begin Job requests with virtual ports might be rejected until fabric virtualization info file is parsed. |
Workaround: Wait for AM to discover virtual ports before sending Begin Job requests. | |
Keywords: Aggregation Manager, Socket Direct, Virtual Ports | |
Discovered in Release: 1.5.3 | |
1193629 | Description: Configuring sharpd/sharp_am as daemons is not possible when installing from RPM into non-default location. |
Workaround: Configure daemon manually. | |
Keywords: Configuration | |
Discovered in Release: 1.5.3 | |
1307108 | Description: Discovering a new Aggregation Node (AN) found on the shortest path between two ANs might invalidate the existing path. |
Workaround: Restart Aggregation Manager after the Subnet Manager completes fabric reconfiguration followed by the fabric changes. | |
Keywords: Aggregation Manager, Aggregation Node | |
Discovered in Release: 1.5.3 | |
- | Description: Adding new switches or switch replacement are currently not supported by the Aggregation Manager for Hypercube and Dragonfly+ topologies. |
Workaround: Restart Aggregation Manager after the Subnet Manager completes fabric reconfiguration followed by the fabric changes. | |
Keywords: Fabric extension, Aggregation Manager | |
Discovered in Release: 1.5.3 | |
- | Description: Adding new non-root switches or non-root switch replacement are currently not supported by the Aggregation Manager for tree topologies. (Fat-Tree, Quasi-Fat-Tree) |
Workaround: Restart Aggregation Manager after the Subnet Manager completes fabric reconfiguration followed by the fabric changes. | |
Keywords: Fabric extension, Aggregation Manager | |
- | Description: Aggregation Manager High Availability is currently not supported in HPCX/MLNX OFED packages. Therefore, only a single instance of Aggregation Manager can run in the IB fabric. |
Workaround: Use Aggregation Manager in UFM. | |
Keywords: Aggregation Manager | |
- | Description: Aggregation manager should run on the same Host where the Master Subnet Manager (SM) is running. |
Workaround: N/A | |
Keywords: Aggregation Manager | |
- | Description: In case of HPCX/MLNX OFED packages, upon Subnet Manager handover/failover, another instance of Aggregation Manager should be started on the Host where the new Master SM is running |
Workaround: Use Aggregation Manager in UFM. | |
Keywords: Aggregation Manager | |
- | Description: Aggregation Manager should be started after completion of fabric configuration by the Subnet Manager. |
Workaround: N/A | |
Keywords: Aggregation Manager | |
- | Description: Only Fat-Tree, Quasi-Fat-Tree, Hypercube and Dragonfly+ topologies are supported by the Aggregation Manager. |
Workaround: N/A | |
Keywords: Fabric Topology | |
- | Description: Only IB fabrics where all compute nodes are connected to Mellanox SHARP capable switches (Switch-IB 2) are supported by the Aggregation Manager. |
Workaround: Manually configure mapping between the compute port and the Aggregation Node. | |
Keywords: Fabric Topology | |
- | Description: Upon changes in configuration file beyond parameters in 3.3, Aggregation Manager should be restarted to deploy new configuration. |
Workaround: N/A | |
Keywords: Configuration |