Courts batch-inference InfiniBand fabric finishes initial provisioning. What should operators confirm next?
Select an answer to reveal the explanation.
Short Explanation
Config saved is not the same as links up. After initial InfiniBand provisioning, confirm the courts fabric’s IB ports actually come up cleanly.
Full Explanation
After courts batch-inference InfiniBand finishes initial provisioning, operators should confirm InfiniBand ports come up cleanly. Saved configuration is incomplete until physical and logical IB links reach expected Up/active states on the switches and HCAs that will carry RDMA for municipal inference. Port-state validation catches cabling errors, bad optics, wrong speed/width negotiation, and admin-down leftovers before GPU jobs depend on the fabric. Leaving all ports administratively down until the next budget cycle fails by concept: an intentionally down fabric cannot serve courts workloads and treats budget timing as a substitute for bring-up validation. Checking only Ethernet management ports while ignoring IB data ports fails because management reachability does not prove InfiniBand data-plane readiness for batch inference. Starting GPU jobs before any port-state validation fails because jobs will hit link-down or flapping paths, wasting court compute windows and obscuring whether the fault is model software or the unvalidated IB underlay. Exam caveat: NCP-AIN initial-configuration flows include post-config link verification, not configuration-file save alone. Operational check: after applying initial IB config, walk switch and HCA port states, confirm expected ports are Up with correct link width/speed, clear unexpected down ports, then allow courts inference jobs only after the port report is clean.