Q: 10
A system administrator of a high-performance computing (HPC) cluster that uses an InfiniBand fabric
for high-speed interconnects between nodes received reports from researchers that they are
experiencing unusually slow data transfer rates between two specific compute nodes. The system
administrator needs to ensure the path between these two nodes is optimal.
What command should be used?
Options
Discussion
A
Yeah, for just connectivity testing ibping (C) is quick, but here you need to see the actual path between nodes. ibtracert shows all the hops in the InfiniBand fabric which helps spot if routing or cabling is off. Pretty sure A fits best for troubleshooting slow routes. Correct me if I missed something.
Yeah, for just connectivity testing ibping (C) is quick, but here you need to see the actual path between nodes. ibtracert shows all the hops in the InfiniBand fabric which helps spot if routing or cabling is off. Pretty sure A fits best for troubleshooting slow routes. Correct me if I missed something.
A tbh, ibtracert actually shows the full route packets take between two InfiniBand nodes. Needed here to find any bottlenecks along the path. D (ibnetdiscover) is great for mapping, but doesn't trace actual traffic flow. Anyone see it differently?
Not sure, but I’d pick D here. ibnetdiscover sounds like it’d show how the nodes are connected, so you could spot any weird topology affecting traffic. Maybe not the most direct, but it gives a map at least. Agree?
D , ibnetdiscover only maps the fabric topology, doesn't trace actual data paths like A does.
If the question wanted just a quick connectivity check instead of full path tracing, would C (ibping) be better than A?
Be respectful. No spam.