Route Server Testing

Peer sets (local-info/ ext-info)

This tests the "next hop" function of the IDRP implementation. One of the machines is set up to simulate a route server, and the others peer only to that machine. "route_server" is set on for routes on all machines. The next hop should be the machine a route originates from, not the route server. In this implementation, the route server will also install routes.


	local-node {
		route-server yes;
		local-info {
			  route-server yes/no;
			  }
		ext-info {
			route-server yes/no;
			}
		}	

Test 1: Internal neighbors

For this test, we will set up a totally internal environment.

Expected behavior

   - the "route server" will propogate its routes, but not those
      coming from other machines.
    - each node will install its own static routes, and those from
      the "route server."

  This behavior will occur whether or not the route server option
  is turned on, because route server functions only with external
  RDIs.

Setup

  1. All machines internal peers.
  2. gw on IP routes set to some other node.

Test 2: External neighbors

For this test, we will set up a totally external environment on the same ethernet.

	peer1   peer2  peer3  peer4  peer5  peer6 
	rdi1    rdi2   rdi3   rdi4   rdi5   rdi6
	 |       |      |      |      |      |
	 ========================================= 

Chain connection
	peer1 <->peer 2 <-> peer 3 <-> peer 4 <--> peer 5 <--> peer 6 

Expected behavior

All peers have the route-server set. All routes should have next hop from the original peer1. Set the gw to a unqiue gateway for each peer.

Setup

  1. All machines external peers.
  2. gw on IP routes set to some unqiue address.

    Test 3: External neighbors

    For this test, we will set up a combination of internal and external ethernet.

    	peer1   peer2  peer3  peer4  peer5  peer6 
    	rdi1    rdi1   rdi2   rdi2   rdi3   rdi3
    	 |       |      |      |      |      |
    	 ========================================= 
    
    
    	peer1 <->peer 2 <-> peer 3 <-> peer 4 <--> peer 5 <--> peer 6 
    
    

    Expected behavior

    All peers have the route-server set. All routes should have next hop from either peer 2/3, peer 4/5.