...
Primary Requirement ID | Secondary Requirement ID | Unit Test ID | Unit Test Description |
|---|
|
|
| - Setup: configure single network, 3 NIDs on the network
- Add UDSP rule that gives two of the interfaces highest priority
- Execute UDSP "Show" command
- Verify that the resulting YAML file contains policy description as expected
- Execute UDSP "Delete" command providing policy index that doesn't exist
- Verify that the command failed with an error
|
|
|
|
|
Single Network Configuration
Expected Behavior
In-Range UT
...
Primary Requirement ID | Secondary Requirement ID | Unit Test ID | Unit Test Description |
|---|
|
|
| - Setup: configure single network, 3 NIDs on the network
- Add UDSP rule that gives highest priority to a NID that doesn't exist
- Execute UDSP "Show" command
- Verify that the resulting YAML file contains policy description as expected
|
|
|
| - Setup: configure single network, 3 NIDs on the network
- Add UDSP rule that gives one of the interfaces highest priority
- Start traffic
- Verify that the NID with the highest priority was used
- Bring the highest priority NID down
- Verify that remaining NIDs are used
- Stop traffic
|
Multiple Network Configuration
Expected Behavior
In-Range UT
...
Primary Requirement ID | Secondary Requirement ID | Unit Test ID | Unit Test Description |
|---|
|
|
| - Setup: configure two networks, two NIDs on each network
- Add UDSP rule that gives highest priority to a network that doesn't exist
- Execute UDSP "Show" command
- Verify that the resulting YAML file contains policy description as expected
|
|
|
| - Setup: configure two networks, two NIDs on each network
- Add UDSP rule that gives one of the networks highest priority
- Start traffic
- Verify that the network with the highest priority was used
- Bring the highest priority network down
- Verify that the remaining network is used
- Stop traffic
|
Routed Network Configuration
Expected Behavior
In-Range UT
...
Tests cases listed in this section are intended to verify that UDSP and LNet Health features work properly when both are enabled. The expected behaviour is that UDSP decisions come second to the health-based decisions, such that, for example, given healthier alternatives, NID with a lower health score won't be chosen even if it is preferred according to a UDSP rule. More detail on how to simulate events that affect the health score can be found here: LNet Health Test Plan [3].
Primary Requirement ID | Secondary Requirement ID | Unit Test ID | Unit Test Description |
|---|
|
|
| - MR Node with Multiple interfaces
- Add UDSP rule that gives one of the local interfaces highest priority
- Send a PING
- Verify that the NID with the highest priority was used
- Send a PING
- Simulate an <error>
- PING msg should be queued on resend queue
- PING msg will be resent on a different interface
- Failed interface's health value will be decremented
- Failed interface will be placed on the recovery queue
- Eventually health score should recover so then only the preferred interface will be used (sensitivity > 0)
|
|
|
| - MR Node with Multiple interfaces: configure two networks, two NIDs on each network
- Add UDSP rule that gives one of the networks highest priority
- Start traffic
- Stop traffic
- Verify that NIDs on the network with the highest priority were used
- Start traffic
- Simulate an <error> (drop on one of the NIDs on the highest priority network)
- Failed interface's health value will be decremented
- Failed interface will be placed on the recovery queue
- Verify that the remaining interface on the failed network is used
- Eventually health score should recover so then only both interface on the preferred network will be used (sensitivity > 0)
|
|
|
| - Configure single local network with two NIDs on the network
- Configure two routers/gateways each providing access to a remote network
- Configure remote peer to have access to the remote network with two NIDs
- Add UDSP rule that designates a pair of a router and local network as preferred
- Start traffic
- Stop traffic
- Verify that the preferred router was used
- Add a PUT drop rule on the router to drop traffic on one of the interfaces.
- Verify that traffic goes to the other interfaces of the preferred router. There shouldn't be any drop in traffic.
- Add a PUT drop rule on the router to drop traffic on all interfaces.
- Verify that traffic goes through the non-preferred router until one of the interfaces of the preferred router recovers.
|
Functional Requirements
Performance Requirements
...
