Re: [Vyatta-users] WAN Load Balancing
-BEGIN PGP SIGNED MESSAGE- On Tue, 5 Feb 2008, Dave Roberts wrote: > One thing you could do is use the WAN load balancing feature and change > the weight factors between the links as you approach the maximum. There is > currently no way to do this automatically, though coupled with QoS you > might be able to work something out. Personally, I would go this route > with WAN LB weight adjustment rather than OSPF. Having not yet played with Glendale, the answer to this may be obvious, but... is there a way to execute Vyatta commands via cron? Being able to schedule the insertion/removal of a higher priority static route would solve Abhilash's problem and be a very cool feature. In the current version I guess you could probably do scheduled config changes using expect. Has anyone tried doing so? - -- Dave Pifke, [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQCVAwUBR6pJjTuW2fOIQC3pAQF9jgQAmV/z++gL5CA0PuWhdsfJ8tYewsCncSfN y8clYip2s4TjMVKEiVY3hA2B3oRyVZAhhmKyPAF3c5mhSuVIV5b05V7B+1Q5QWqr JRTJjfSW7sHPfIYIIEV4NOQzYqVmubBu/A8/pJbWUP5aU4+2Yo1fC4eTZxM/VB9G j3ltmAeybxU= =PoHn -END PGP SIGNATURE- ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Emergency Config paste? How do you prepare?
-BEGIN PGP SIGNED MESSAGE- On Fri, 18 Jan 2008, Justin Fletcher wrote: > There are a couple of choices. You can copy your configuration using > scp (it's /opt/vyatta/etc/config/config.boot) to another server. From a > blank slate/system, all you need to do is to configure an interface and > a default gateway, scp the configuration back, and load the restored > configuration. One caveat to anyone thinking about scp'ing config.boot files around: you need to make sure to change the interface hw-id parameters to represent the MAC address of the box it's running on, not the box from which it was copied. I once spent most of a day troubleshooting what I thought was a buggy NIC in my backup router after copying the config from my primary box. Couldn't for the life of me figure out why the interfaces kept disappearing on reboot. :) - -- Dave Pifke, [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQCVAwUBR5FLKjuW2fOIQC3pAQET8QP/c8OvLK37T4j6PM/NlIopQpLxJgc8lsju X11B0ZpvYfZBo2FlE06tW53L7pviQaMDpKR3XNZnLrK+szl6VOXUJSLbcop+WN2H tHf7a0PyvH/DA44ud8F2JuU5U2G2ZzPpTCBXzqnn4beV4mlaMJcMvvKjTeHZgeMS BDeCLcc1Ngo= =mjeT -END PGP SIGNATURE- ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] GLBP
-BEGIN PGP SIGNED MESSAGE- On Thu, 10 Jan 2008, Max wrote: > Can canyone comment more on load balaning vrrp? Active/active style > configuration? Perhaps even noting bgp? I was not aware with vrrp one > could have two routers handling packets :/ This may have changed, but I believe Vyatta only supports one VRRP address per interface. Consider what I'm describing here a feature request, although perhaps someone else can comment on how to make this work with the current functionality. :) If Vyatta supported multiple VRRP addresses (and the equipment behind it supports ECMP), you could do active/active by configuring two default gateway addresses and using the VRRP priority/preempt parameters to give one address an affinity for one router and one for the other. For instance: Router A, x.x.x.3, VRRP addresses x.x.x.1 priority 100 and x.x.x.2 priority 50 Router B, x.x.x.4, VRRP addresses x.x.x.1 priority 50 and x.x.x.2 priority 100 Device C, x.x.x.5, default gateway configured as x.x.x.1 and x.x.x.2 with equal metrics In normal operation, half the packets will be processed by either router (depending on how device C implements equal cost multipath). If one router fails, both the .1 and .2 addresses end up on the surviving box. N.B. this breaks stateful packet inspection. I believe the original reason for the one-addres-per-interface restriction was due to the virtual MAC address. Now that we have the disable-vmac option, perhaps this limitation could be removed? - -- Dave Pifke, [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQCVAwUBR4aPSTuW2fOIQC3pAQFKmgP/U6kbweEz+HR0Tbrq5aeoXOZu2JXpav4y fVjBzG8wR7mL/2b1whiVjUq/hj55uiMcXPWQ4+dxWvbRoJgZZx1o1kpjfASW3z+J aCJ4fbcv0O2fmWqxVGuEc8gPohW3BrBuWOipj1y7vFofmfV7dkEtyOdLLFbaLE9I Jt7AFqzoFCM= =ASQ2 -END PGP SIGNATURE- ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Vyatta BGP Router
-BEGIN PGP SIGNED MESSAGE- On Wed, 14 Nov 2007, Tony Raboza wrote: > 1. Has anybody deployed something like the above in a *production* > network and has been running it for some time (e.g. 6 months or more) > with no serious problem? The reason I ask this is because I just came > across this web site: We've been running Vyatta on our two border routers (rack-mount mini-ITX systems with mobile Core Duo and 2GB RAM) with BGP since June with no problems. We have three 100Mbps upstream connections providing us full routes, two into border01 and one into border02. The routers exchange routing information via iBGP and use VRRP to provide failover in the event we lose one of them. No major problems. A few months back we had rtrmgr crash on one of them, but VRRP worked as advertised and a simple reboot solved the problem. There were a few issues during the initial deployment, all of which turned out to be completely on one of our provider's side. Mark in the TAC went out of his way to help me diagnose these and get them solved. My only complaints were the lack of MD5 authentication and no easy to use equivalent to the IOS "show ip bgp " command - both of which I understand are fixed in the latest version (haven't upgraded yet). For the cost in both in dollars and watts, this solution blows away anything else I've seen or used in my nearly 15 years of doing this. It's been as solid (if not more so) than the Cisco 2828s and 6509s I used at my previous job. - -- Dave Pifke, [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQCVAwUBRzsyYjuW2fOIQC3pAQEuIAP+IiGc+gwexVjABuGV3QfVjOlOqqzlHFty jVEPTAdkHwp7o/xIJLlXTJE1mSO4w47xdUHjW25esiwbJ0b1VAlZoAvnV+kSyquB rLpvcLdo/HusUuEEO4OORw3uFZdclUfdMELZpnueCL9CX7ehVyNew6Ti9DAgUbMK f6NS7OFk9xo= =IPD5 -END PGP SIGNATURE- ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
