Page History

• 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 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

pass - manually run

add UDSP rule to interface A

simulate the error by "lctl net_drop_add -s A -d B -i 2"

do lctl ping B from A

check lnetctl net show -v 3 and found send_count is increased on A as well as other interfaces,  the same time, health stats dropped number increased too

delete the rule by "lctl net_drop_del" and do lctl ping again

send_count shows only A increased by 1

• 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 router 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.