ibstat shows a port as Initializing. What is likely missing?
Why A is the answer
A working subnet manager
Ports need the SM to go Active.
In detail
- Ports need the SM to go Active.
- Ports need the SM to go Active.
Use case
An illustrative scenario, not a real incident.
A port stays in Initializing, because no working subnet manager can bring it up.
See it in different ways
flowchart LR A["Discover fabric"] --> B["Assign LIDs"] B --> C["Program routing tables"] C --> D["Ports go Active"] D --> E["Standby SM takes over on failure"]
stateDiagram-v2 [*] --> Down Down --> Initializing: link comes up Initializing --> Armed: SM assigns a LID Armed --> Active: SM finishes the configuration Active --> [*]
stateDiagram-v2 state "Down" as s0 state "Initializing" as s1 state "Active" as s2 [*] --> s0 s0 --> s1: link up s1 --> s2: SM configures it s2 --> [*]
Key point: Initializing points to the SM.
Why the other options are wrong
- B. A Slurm controller
- Slurm is unrelated.
- C. A GPU driver
- A GPU driver is unrelated.
- D. An NGC key
- An API key is unrelated.