You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Selection Algorithm Scenarios
| Test # | Tag | Procedure | Script | Result |
|---|
| 1 | SRC_SPEC_LOCAL_MR_DST | - MR Node
- MR Peer
- Send a ping
- REPLY for PING should always come on the same interface that PING was sent on.
- Check the TRACE in the logs to verify
|
|
|
| 2 | SRC_SPEC_LOCAL_MR_DST | - MR Node
- MR Peer
- Initiate discovery
- Node → PING → Peer
- Node ← PUSH ← Peer
- Node should respond with an ACK to the same interface as the one it received the PUSH on
- Check the TRACE in the logs to verify
|
|
|
| 3 | SRC_SPEC_ROUTER_MR_DST | - MR Node
- NMR Router
- MR Peer
- Send a ping
- REPLY for PING should always come on the same interface that PING was sent on.
- Check the TRACE in the logs to verify
- Router should be used
|
|
|
| 4 | SRC_SPEC_ROUTER_MR_DST | - MR Node
- NMR Router
- MR Peer
- Initiate discovery
- Node → PING → Peer
- Node ← PUSH ← Peer
- Node should respond with an ACK to the same interface as the one it received the PUSH on
- Check the TRACE in the logs to verify
- Router should be used
|
|
|
| 5 | SRC_SPEC_ROUTER_MR_DST | - MR Node
- MR Router
- MR Peer
- Send a ping
- REPLY for PING should always come on the same interface that PING was sent on.
- Check the TRACE in the logs to verify
- Repeat sending
- Router interfaces should be used in round robin, while the peer destination should remain constant.
|
|
|
| SRC_SPEC_ROUTER_MR_DST | - MR Node
- MR Router
- MR Peer
- Initiate discovery
- Node → PING → Peer
- Node ← PUSH ← Peer
- Node should respond with an ACK to the same interface as the one it received the PUSH on
- Check the TRACE in the logs to verify
- Router interfaces should be used in round robin, while the peer destination should remain constant.
|
|
|
Error Scenarios
Synchronous Errors
Asynchronous Errors
