This is probably you can do. 1. #create interfaces interface eth1 vif eth1 address 10.0.0.1 prefix-length 24.
2. #create protocols vrrp interface eth1 vif eth1 vrid 100 ip 10.0.0.100 3. #create protocols vrrp interface eth1 vif eth1 vrid 100 priority 200 >show vrrp You should see "State Master" + "Master IP 10.0.0.1" Then you can even do the following on a second router: 4. #create interfaces interface eth1 vif eth1 address 10.0.0.2 prefix-length 24. 5. #create protocols vrrp interface eth1 vif eth1 vrid 100 ip 10.0.0.100 6. #create protocols vrrp interface eth1 vif eth1 vrid 100 priority 100 >show vrrp You should see "State Backup" + "Master IP 10.0.0.1" 7. on two routers, use "ip addr add 10.0.0.100 dev eth1" to make kernel IP stack recognize 10.0.0.100 as local address. 8. From a third host to ping 10.0.0.100 Test switchover, you can do the following on the router-1 9. #create interfaces interface eth1 disable true 10.#create interfaces interface eth1 vif eth1 disable true Then ">show vrrp" and "ping 10.0.0.100" should show the switch over. Futher, you can test to use "10.0.0.100" as the endpoint of a ip tunnel to see tunnel protected... etc. Li --- On Fri, 3/19/10, Ben Greear <[email protected]> wrote: > From: Ben Greear <[email protected]> > Subject: Re: [Xorp-hackers] VRRP error > To: "Li Zhao" <[email protected]> > Cc: [email protected] > Date: Friday, March 19, 2010, 11:35 AM > On 03/19/2010 07:16 AM, Li Zhao > wrote: > > I am attaching my fix for vrrp abort. I have done > quite a lot real time testing on my router. > > Thanks, looks good to me. I'll push it to xorp.ct in > a bit. > > Do you have any notes on how to do at least minimal testing > of vrrp using > just xorp? (config-files, disconnect certain cables, etc?) > > Thanks, > Ben > > -- Ben Greear <[email protected]> > Candela Technologies Inc http://www.candelatech.com > _______________________________________________ Xorp-hackers mailing list [email protected] http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
