James Mackinnon wrote on Friday, May 29, 2009 6:25 PM > Hi All > > Thanks for your feedback. > > The guy regarding the cisco is a CCIE so I tend to accept his > statements > quick enough.. > > In VPN, I am referencing it in general terms in the creation of a > private > network over a public network of course. I would go with MPLS or > another > technology, however again, not 100% failsafe. > > Their application is a thick app which has allowances for network > drops, > however, the data is a real-time life and death type of solution in > that > they are a security monitoring company with multiple sites to which > access > data in 1 location. This is what I must ensure stays up because staff > must > be able to handle the alarms.. > > Roughly 1 million alarms a day go through this network, thus, any > outage can > result in dropped alarms.. Our solutions in both facilities also offer > some > allowances for drops by caching an alarm until network return, however > applications failures are also bad in this case. > > At first, I was looking at BGP, and in the past have used it, but with > convergence time on a net down situation, it doesn't come close to the > time > required. > > Personally, I think any solution that can rebuild in 10-30 seconds is a > very > solid solution. If they are not happy with that, I could recommend a > very > expensive alternative but that won't fly. > > Stuart, do you know of some sources I should review on your mentioned > idea. > > I am also looking at multi-segmenting the locations systems and having > their > applications account for loss to failover to the second IP. > > fun little project, very small to almost nil budget is the challange. > > Cheers
If it absolutely has to be up, OpenVMS