Cool- glad it all works. Odd about the fail-over not working properly. Unfortunately, I¹ve only used the NLB in production, so I can¹t help much with the failover stuff. That being said, I will say that you should ensure that you¹ve got the latest firmware on those guys. Netgear has a later version posted than what shipped on them. t On 7/22/06 4:25 PM, "Glenn P. JOHNSTON" <glenn.johnston@xxxxxxxxxxx> spoketh to all: > I put it in at the customer site yesterday. Works fine. > > But there seems to some minor issue with this setup, but the redundancy > portion works fine. > > When first powered up, traffic is routed over all 3 links, and the speed of > internet access is fantastic. The router that manages ISP1 and ISP2, when it > detects that either of ISP1 or ISP2 have gone down, and will route traffic to > the link that's still up, which is exactly what one would expect. We tested > this by unplugging the Telephone line from the router, and it sends traffic > across the other link just fine. So far so good. > > But, even after an hour, it does not recognise that the ADSL line that had > 'failed', is back up and operational, even attempting to tweak it back to > life, by attaching to the web interface of NetGear box1 from the internet, it > does not start routing traffic down the link that had failed, the logs still > show all traffic as routing down the ISP that had not 'FAILED'. But it only > switches to the 'failed line', if we unplug the line that had not failed, and > will then hold that configuration, but will happily switch back and forth > between ADSL1 and ADSL 2, by 'failing' the other ADSL line. > > So it only seems to be able to use all 3 lines from a power off cold start up, > once up and running, and 1 line has failed, it's then effectively a 2 line > setup. But given the reliability of the ADSL lines these days, you are going > to have 3 lines most of the time. > > Maybe not 100% ideal, but at least there is a fairly high level of redundancy > in this setup, so the customer is very happy, with the setup. > > > > From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On > Behalf Of Thor (Hammer of God) > Sent: Tuesday, 18 July 2006 12:14 > To: isalist@xxxxxxxxxxxxx > Subject: [isalist] Re: Proxy problems > > Yes, you could do something like this: > > ISP1 ISP2 > WAN1 WAN2 > | | > [NetGear FVX 538 Box1] > | > LanFromBox1 ISP3 > WAN1 WAN2 > | | > [NetGear FVX 538 Box 2] > | > Int LAN > > > > ISP1 and ISP2 go into NetGear Box 1. You would want that guy to be in > ³Fail-Over² mode. Use DDNS just on 2 providers for inbound. LAN from NetGear > Box 1 goes into WAN1 on Netgear Box 2, with ISP3 going into WAN2. This guy > would be in ³Load-Balancing² mode. All published services come from WAN1 on > Box 2, which are already redundant because of Netgear Box 1. Multiple HTTP > requests would be LB between the combo of ISP1+ISP2 as ³one leg² with ISP3. > All internal users go to NetGear Box 2 for access. > > Only drawback (if it really is a ³drawback²) is that there is no LB on the > ISP1+ISP2 leg coming into WAN1 on the Netgear Box 2. But that¹s OK- you just > set the ³main² connection on Netgear Box 1 to the fastest ISP. > > The boxes are only $350 a piece and you can get the model one under the 538 > (338?) even cheaper if you don¹t need P2P VPN capabilities in-box. That¹s > actually a pretty cool topology for under $700 in hardware. You know, I¹ve > got an extra FVX538- I think I¹ll order another DSL and do just that. ;) > > T > > > > > On 7/17/06 6:38 PM, "Glenn P. JOHNSTON" <glenn.johnston@xxxxxxxxxxx> spoketh > to all: > >> Ok, I know what the first question the customer is going to ask, can they be >> cascaded ? combining 3 lines in 2 steps ? >> >> I suppose they can, but are there any draw backs that jump to mind ? >> >> >> >> From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On >> Behalf Of Thor (Hammer of God) >> Sent: Tuesday, 18 July 2006 11:35 >> To: isalist@xxxxxxxxxxxxx >> Subject: [isalist] Re: Proxy problems >> >> Right- should have said that... The Netgear FVX538 provides 2 WAN >> connections, not 3. >> >> t >> >> >> On 7/17/06 6:25 PM, "Greg Mulholland" <gmulholland@xxxxxxxxxxxx> spoketh to >> all: >> >> >>> Havent seen a 3-way (maybe before i die! ) but there is a nice little >>> netgear floating around that apparantly does a good job. I'll wait for >>> thor to chime in with the details, I looked at it and it seemed to do most >>> of what i wanted. Might be a start >>> >>> Greg >>> >>> >>>> >>>> ----- Original Message ----- >>>> >>>> From: Glenn P. JOHNSTON <mailto:glenn.johnston@xxxxxxxxxxx> >>>> >>>> To: isalist@xxxxxxxxxxxxx >>>> >>>> Sent: Tuesday, July 18, 2006 11:15 AM >>>> >>>> Subject: [isalist] Re: Proxy problems >>>> >>>> >>>> >>>> A little off topic, but I'm sure that someone on this list will have >>>> done this before. >>>> >>>> >>>> >>>> A customer wants to combine 2 or preferably 3 ADSL2 lines together for >>>> the added bandwidth & more importantly the reliability factor. >>>> >>>> >>>> >>>> They can get 3 ADSL services from 3 different telco's, which supposedly >>>> use different equipment at the local exchange. >>>> >>>> >>>> >>>> What's the best way to bind them together. >>>> >>>> >>>> >>>> There will be inbound VPN & SMTP so the public DNS entries will have to >>>> cater for the multiple public IP's, but that easy stuff. >>>> >>>> >>>> >>>> I found multiple hardware & software solutions on the WEB, but nobody I >>>> know who has actually used any and can tell me the un documented holes, >>>> or the one that just work, and those that really work well. >>>> >>>> >>>> >>>> Has anyone done this ? >>>> >>>> >>>> >>>> Any suggestions ? >>>> >>>> >>>> >>>> >>>> >>>> >>>> From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] >>>> On Behalf Of Greg Mulholland >>>> Sent: Tuesday, 18 July 2006 09:19 >>>> To: isalist@xxxxxxxxxxxxx >>>> Subject: [isalist] Re: Proxy problems >>>> >>>> >>>> >>>> Please let us know! in fact email John he will be excited to know. >>>> >>>> >>>> >>>> Greg >>>> >>>> >>>> >>>>> >>>>> ----- Original Message ----- >>>>> >>>>> From: D PIETRUSZKA USWRN INTERLINK INFRA ASST MGR >>>>> <mailto:DPietruszka@xxxxxx> >>>>> >>>>> To: isalist@xxxxxxxxxxxxx >>>>> >>>>> Sent: Tuesday, July 18, 2006 6:01 AM >>>>> >>>>> Subject: [isalist] Re: Proxy problems >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Ok, ok don¹t cry, you can finish with that poor customer. >>>>> >>>>> Anyway, my proxy starts working without any apparent reason. I >>>>> restarted the firewall as Jim told me and nothing, and about an hour >>>>> latter I discover it was working again. >>>>> >>>>> I¹ll see if this happen again. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Regards >>>>> >>>>> Diego R. Pietruszka >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> From: isalist-bounce@xxxxxxxxxxxxx >>>>> [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of John T (Lists) >>>>> Sent: Monday, July 17, 2006 3:01 PM >>>>> To: isalist@xxxxxxxxxxxxx >>>>> Subject: [isalist] Re: Proxy problems >>>>> >>>>> >>>>> >>>>> Oh, excuse me sir. Let me drop everything including the work I am doing >>>>> for a client that was robbed and I am trying to get them back all up >>>>> and running to attend to your problem that you expect free instant >>>>> help on. >>>>> >>>>> >>>>> >>>>> Gees, what did you do take lessons from Andrew? >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> John T >>>>> >>>>> eServices For You >>>>> >>>>> >>>>> >>>>> "Seek, and ye shall find!" >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -----Original Message----- >>>>> From: isalist-bounce@xxxxxxxxxxxxx >>>>> [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of D PIETRUSZKA USWRN >>>>> INTERLINK INFRA ASST MGR >>>>> Sent: Monday, July 17, 2006 11:19 AM >>>>> To: isalist@xxxxxxxxxxxxx >>>>> Subject: [isalist] Re: Proxy problems >>>>> >>>>> >>>>> >>>>> Helloooooo is anybody at home! >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Regards >>>>> >>>>> Diego R. Pietruszka >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> From: isalist-bounce@xxxxxxxxxxxxx >>>>> [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of D PIETRUSZKA USWRN >>>>> INTERLINK INFRA ASST MGR >>>>> Sent: Monday, July 17, 2006 12:50 PM >>>>> To: isalist@xxxxxxxxxxxxx >>>>> Subject: [isalist] Proxy problems >>>>> >>>>> >>>>> >>>>> Hi ISAList >>>>> >>>>> >>>>> >>>>> I¹m having this issue and I have no idea why, I will appreciate if >>>>> somebody knows what is going on. >>>>> >>>>> We have a website https://vwa.msc.us <https://vwa.msc.us/> that is >>>>> published on 12.32.217.149. >>>>> >>>>> From outside everything work fine, but from inside I¹m receiving the >>>>> following error: >>>>> >>>>> >>>>> >>>>> Network Access Message: The page cannot be displayed >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Technical Information (for Support personnel) >>>>> >>>>> >>>>> * Error Code: 504 Proxy Timeout. The connection timed out. (10060) >>>>> * IP Address: 204.251.15.190 >>>>> * Date: 7/17/2006 4:42:49 PM >>>>> * Server: njisa17.interlink-intranet.net >>>>> * Source: proxy >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> If I ping the website, its resolving fine to 12.32.x.x but the error is >>>>> showing another IP. >>>>> >>>>> If from my proxy server (njisa17) I ping the website, the address >>>>> returned it is also correct. >>>>> >>>>> So, where is ISA keeping that wrong IP????? >>>>> >>>>> >>>>> >>>>> Thanks for all your answers. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Regards >>>>> >>>>> Diego R. Pietruszka >>>>> >>>>> MIS - Assistant Manager >>>>> >>>>> MSC (USA) - Interlink Transport Technologies >>>>> >>>>> >>> >> >> > >