Abstract: A verification mechanism monitors incoming and outgoing traffic between a channel adapter and a switch fabric in an InfiniBandSM system in order to verify that the InfiniBandSM protocol is correctly followed by the channel adapter. The verification mechanism uses a simple hardware-independent interface to query the channel adapter hardware for specific values and completion queue, queue pair and work queue element attributes that are required for verification. The verification mechanism creates a plurality of verification components that monitor incoming and outgoing messages and verify that each of the channel adapter elements correctly follows the protocol. The verification mechanism is controlled by a verification application programming interface (API) that allows different test benches and tests to incorporate InfiniBandSM protocol verification in any test system for use with any hardware.

Abstract: A verification mechanism monitors incoming and outgoing traffic between a channel adapter and a switch fabric in an InfiniBandSM system in order to verify that the InfiniBandSM protocol is correctly followed by the channel adapter. The verification mechanism uses a simple hardware-independent interface to query the channel adapter hardware for specific values and completion queue, queue pair and work queue element attributes that are required for verification. The verification mechanism creates a plurality of verification components that monitor incoming and outgoing messages and verify that each of the channel adapter elements correctly follows the protocol. The verification mechanism is controlled by a verification application programming interface (API) that allows different test benches and tests to incorporate InfiniBandSM protocol verification in any test system for use with any hardware.

Abstract: A network layer verification mechanism (NLVM) is inserted between DUTs or between a DUT and the test bench components in order to simulate conditions that can occur in a packetized network connection, such as dropped packets, duplicate packets, corrupted packets out-of-order packets and delayed packets. The NLVM has internal storage and an application programmer interface (API) which can be driven by the test bench and comprises a plurality of methods that allow packets received by the NLVM to be selectively forwarded through the object, temporarily stored in the object or the packet data to be corrupted. The NLVM is implemented as an object with an interface that is independent of the simulation configuration so that verification test benches and tests can be written with no reliance on bus functional models and environment-specific details.