Gliffy Diagram |
---|
name | LocalLayout1 Copy |
---|
pagePin | 1 |
---|
|
Overview
...
Primary Requirement ID | Secondary Requirement ID | Unit Test ID | Unit Test Description |
---|
cfg-095 | cfg-160 |
| - Setup: configure single network, 3 NIDs on the network
- Execute UDSP "Show" command
- Verify that the resulting YAML file doesn't contain any policy description
|
cfg-125, cfg-100 | cfg-115, cfg-125 |
| - 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
| cfg-125 | - 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
- Add UDSP rule that lowers the priority of one of the NIDs with highest priority back to default
- Execute UDSP "Show" command
- Verify that the resulting YAML file contains policy description as expected
|
cfg-110 |
|
| - Setup: configure two networks, two NIDs on each network
- Add UDSP rule that gives one of the networks highest priority
- Add UDSP rule that gives the highest priority to one of the NIDs on the network with the highest priority
- Execute UDSP "Show" command
- Verify that the resulting YAML file contains policy description as expected (for network and NID)
- Delete UDSP rule that gives the highest priority to one of the NIDs
- Execute UDSP "Show" command
- Verify that the resulting YAML file contains policy description as expected (for network)
- Delete UDSP rule that gives the highest priority to one of the networks
- Execute UDSP "Show" command
- Verify that the resulting YAML file doesn't contain any policy description
|
cfg-115 |
|
| - Setup: configure single network, 3 NIDs on the network locally, 3 NIDs on the remote peer
- Add UDSP rule that gives priority to one of the remote peer's NIDs
- Execute UDSP "Show" command
- Verify that the resulting YAML file contains policy description as expected
- Delete UDSP rule that gives the highest priority to the remote peer's NID
- Execute UDSP "Show" command
- Verify that the resulting YAML file doesn't contain any policy description
|
cfg-120 |
|
| - Setup: configure single network, 3 NIDs on the network locally, 3 NIDs on the local peer
- Add UDSP rule that gives priority to a pair of the local NID and peer's NID
- Execute UDSP "Show" command
- Verify that the resulting YAML file contains policy description as expected
- Delete UDSP rule that gives the highest priority to the NID pair
- Execute UDSP "Show" command
- Verify that the resulting YAML file doesn't contain any policy description
|
|
|
| - 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 remote peer NID as preferred
- Execute UDSP "Show" command
- Verify that the resulting YAML file contains policy description as expected
- Delete UDSP rule that gives the highest priority to the router/remote NID pair
- Execute UDSP "Show" command
- Verify that the resulting YAML file doesn't contain any policy description
| - 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
- Execute UDSP "Show" command
- Verify that the resulting YAML file contains policy description as expected
- Delete UDSP rule that gives the highest priority to the router/local network pair
- Execute UDSP "Show" command
- Verify that the resulting YAML file doesn't contain any policy description
|
TODOTODO: add N:1, 1:N, N:N mapping tests |
|
|
|
TODO: update requirements to cover router-related rules |
|
|
|
...
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 one of the local interfaces highest priority
- Start traffic TODO: need to specify direction?
- Stop traffic
- Verify that the NID with the highest priority was used
|
|
|
| - Setup: configure single network, 3 NIDs on the network
- Add UDSP rule that gives two of the local interfaces highest priority
- Start traffic
- Stop traffic
- Verify that two NIDs with the highest priority were used
|
|
|
| - Setup: configure single network, 3 NIDs on the network
- Add UDSP rule that gives two of the interfaces highest priority
- Start traffic
- Stop traffic
- Verify that two NIDs with the highest priority were used
- Add UDSP that lowers the priority of one of the NIDs with highest priority back to default
- Start traffic
- Stop traffic
- Verify that the remaining highest-priority NID was used
|
|
|
| - Setup: configure single network, 3 NIDs on the network
- Add UDSP rule that gives two of the interfaces highest priority
- Start traffic
- Stop traffic
- Verify that two NIDs with the highest priority were used
- Add UDSP that lowers the priority of both of the NIDs with the highest priority back to default
- Start traffic
- Stop traffic
- Verify that all NIDs were used
|
|
|
| - Setup: configure single network, 3 NIDs on the network, 3 NIDs on the local peer
- Add UDSP rule that gives the highest priority to one of the local peer NIDs
- Start traffic
- Stop traffic
- Verify that local peer NID with the highest priority was used
| singlenet-006 | - Setup: configure single network, 3 NIDs on the network, 3 NIDs on the local peer
- Add UDSP rule that creates 3 NID pairs such that one of the peer NIDs is not in any pairrule that gives the highest priority to one of the local peer NIDs
- Start traffic
- Stop traffic
- Verify that the local peer NID that is not part of any pair was not used (less used?)
- Delete UDSP rule
- Start traffic
- Stop traffic
- Verify that all NIDs are used
- with the highest priority was used
|
|
|
| - Setup: configure single network, 3 NIDs on the network, 3 NIDs on the
network Start trafficVerify that all NIDs were used- local peer
- Add UDSP rule that gives one of the
interfaces - local NIDs highest priority
Verify - Add UDSP rule that pairs the highest priority local NID with
the highest priority - a certain peer NID
- Start traffic
- Stop traffic
- Verify that the paired peer NID was used
Stop traffic |
|
| singlenet-006 | - Setup: configure single network, 3 NIDs on the network, 3 NIDs on the
| network | UDSP rule that gives one of the interfaces highest priorityOn the peer, add UDSP rule that gives - UDSP rule that creates 3 NID pairs such that one of the peer
| interfaces highest priority- NIDs is not in any pair
- Start traffic
- Stop traffic
- Verify that the
| NIDs with the highest priority were used on both sides, except for responses TODO: can this be verified?- peer NID that is not part of any pair was not used (less used?)
- Delete UDSP rule
- Start traffic
- Stop traffic
- Verify that all NIDs are used
|
Out-of-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
|
Issues
...
Unit Test ID | Description | Status |
---|
LU-13193 | "Oops" when adding a destination nid UDSP | pending commit |
Routed Network Configuration
Remote layout 1:
Gliffy Diagram |
---|
| |
---|
name | RemoteLayout1 |
---|
pagePin | 1 |
---|
|
Remote layout 2:
Gliffy Diagram |
---|
| |
---|
name | RemoteLayout2 |
---|
pagePin | 1 |
---|
|
Remote layout 3:
...
Expected Behavior
In-Range UT
Primary Requirement ID | Secondary Requirement ID | Unit Test ID | Unit Test Description |
---|
|
|
| - Configure single local network with two NIDs on the network (RemoteLayout1)
- 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 remote peer NIDs as preferred
- Add UDSP rule that gives the same remote peer NID highest priority
- Start traffic
- Stop traffic
- Verify that the preferred remote peer NID and router NID were used
|
|
|
| - Configure single local network with two NIDs on the network network (RemoteLayout1)
- Configure two routers/gateways each providing access to a remote network
- Configure remote peer to have access to the remote network with two NIDs
- Assign higher route priority to the route using gateway 1
- Add UDSP rule that designates a pair of a router and local network (gateway 2) and remote peer NIDs as preferred
- Start traffic
- Stop traffic
- Verify that the preferred router higher priority route was used (gateway 1)
|
|
|
| - Configure two local networks (net1, net2) with two NIDs on each network Configure two routers/gateways per local networknetwork (RemoteLayout2)
- Configure remote peer to have access to the remote network with two NIDs
- Add On peerA add UDSP rule that designates a pair of a router and local network (net1) as preferredgateway 1 as preferred for all NIDs on peerB
- Start traffic (peerA to peerB)
- Stop traffic
- Verify that if net1 was used then the paired router was used
|
...
Primary Requirement ID | Secondary Requirement ID | Unit Test ID | Unit Test Description |
---|
|
|
| - 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 that doesn't exist and a local network as preferred
- Start traffic
- Stop traffic
- Verify that both routers were used
|
|
|
| - 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 a local network that doesn't exist as preferred
- Start traffic
- Stop traffic
- Verify that both routers were used
|
|
|
| - 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 that doesn't exist and a remote peer NID as preferred
- Add UDSP rule that gives the same remote peer NID highest priority
- Start traffic
- Stop traffic
- Verify that the all peer NIDs and both routers were used
|
|
|
| - 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 a peerB NID as preferred
- Start traffic
- Verify that the preferred router was used
- Bring down the preferred router
- Verify that the remaining router was used
- Stop traffic
|
...
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 for all remote peer NIDs
- 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.
|
...