Prefered Method Of Network Redundancy (Server Connectivity)
May 16, 2007
There are several methods of offering network path redundancy. The basic decision for me has come down to:
Do it at Layer 2
Do it at Layer 3
At the moment we have layer 2 redundancy to each server. 2NICs on the server up with one having the IPs for apache/mysql/etc. each nic going into a seperate switch and the switches connected together, with 2 routers running VRRP to handle the gateway.
Everything is Vlaned.
So basicaly the switch redundancy is done by spanning tree and the IP redundancy is done with a process on the router/server to move the IP to the other router/server NIC if there is an issue.
I am thinking about going with 2 fully seperate networks. in differant subnets. where each router would have a gateway. the routers would talk to each other and they would speak OSPF or ISIS with the servers. This way I would move hosting onto loopback IPs on the servers and those loopback IPs would be advertised to the both routers through seperate networks.
Again everything would be Vlanned.
This has the advantage of getting rid of spanning tree which has caused issues from time to time. It would keep redundancy up and we could standardize on the routing daemon ran on the servers allowing all of the various OSs we run to have the same basic config for network redundancy. Where now each OS tends to have its own solution. This would make life easier from a config and troubleshooting point of view.
1) All VPS hosting services emphasize their high level of network connectivity (Tier 1 etc.) but how to learn about this topic and choose the fastest service?
2) What is really the state of the art and fastest network connectivity available?
3) Is there a map/list of the biggest US network hubs and which web hosts are connected to them?
4) Is the old ping response time the best metric to verify a web host speed connectivity?
5) Is there an indipendent and unbiased website that reviews and report web hosts ping response times?
We have a VPS with Media Temple. Their data center is somewhere on the westcoast. From time to time we have severe issues to connect from our Brooklyn/NY locations. We experienced the connectivity issue from 2 physical locations. Doing a tracert gave us a good result.
There are usually 4-8 users using our shop admin for order processing or the shopping cart for manual order entry. While they are having problems connecting from there, I can connect just fine from Calgary/AB, Canada. Most of the time no issues at all.
I am planning to buy a dedicated server and a shared server from a hosting company. Basically I want to have a redundant server so that if one file server goes down, there is no downtime.
Somehow the servers would need to be constantly synchronized so that the files saved to one are immediately saved to the other server as well.
Can somebody told me how to setup the 2 server so that my dedicated server can serve as the main server and if the dedicated server is down, the shared server can automatically be activated and visitors of my website will auto be redirect to the shared server.
Do i need to setup any backup DNS too so that when the dedicated server is down, it will auto redirect the user to the shared server.
I ordered yesterday, and got it today! But I have the box, 100 MB unmetered line, I downloaded utorrent, donloaded a file at 10 MB/per sec, but For some reason the box wont seed, and the tiny little yellow banner on the bottom says there are no incoming connections (this is usually green if your port is open) It wont seed... the DL is great, is there a box setting that is blocking this? there is no installed firewall, and the ports are all open....
I've got a housed server within my customer's datacenter. I consider application runs ok, but it goes very slow.
I consider it's due to their connection (DSL) and installed another provisional server with a simple "Hello World" and no traffic. I'm to install the same server within another datacenter, and would like to find an external tool to certify connectivity times.
Do you know any of these tools? I'm not searching tools like 'Apache AB' or 'HP httperf', but public online services.
I have two questions that hopefully someone will be able to help me out with. The first, is my partner and I want to provide server redundancy for our clients. Our set-up is as follows: two identical servers with multiple virtual machines (about 4) on each. One for SQL, one for IIS, etc. We also have a ServerIron XL to connect the two together and provide replication and load balancing. So the question is, has anyone here used a ServerIron XL and how easy is it to use/how effective is it? The second question is, we would like to provide our clients with hosted Exchange. I have set up and maintained a few Exchange 2007 servers, but only for a single company with a single domain. What would be the best way to go about providing a hosted Exchange solution?
I have dedicated server at GoDaddy and I am hosting very important web service for our company. We have only one HDD on server and no FTP backup. What is the best method to protect data and whole server from HDD crash? Is it enough to add second HDD?
After some experimenting with Linux VPS setups, I'm eager to explore windows VPS software.
Two questions I guess, first off, what is the cheapest method of offering multiple VPS accounts on a windows server? Are there any free or build in Microsoft methods?
Second, what is the easiest way of doing so? (Simple setup, as hands off as possible)
I realize the cheapest may not be the easiest and vice versa. I'm downloading Parrallels Virtuozzo trial right now, but would like to learn what else is out there.
im trying to remotely install WS2003 EE R2 on a dedicated server I have purchased and have an issue. I'm installing it via KVM IP which is cool
however, after installing the network card drivers, I get a "There is no or limited connectivity" etc... so I cannot access the internet or anything on that box.
what do I do from here? how can I make the card work? It is configured to obtain the IP Address automatically as well as using the default DNS. I do have 2 IP Addresses "assigned" to me/my account but dont believe I need to configure them in WS2003?
is anyone else having trouble with burst.net at the moment? from two locations, i'm having problems where anything that will elicit a large response just hangs indefinitely. i can ping my server just fine, i can shell into it... if i do "top" or "dmesg" or anything else that might dump back more than a few lines of response at a time, the ssh session hangs. i can do "ps x" as a regular user, because i only have two processes running. "ps ax" will hang ssh.
none of my websites work, and i can't get on the burst.net website from either location. i tried calling but no matter what sequence i try for (even tried reboots) i can't get ahold of a live person, but then again it is almost midnight.
I have tested so many compagny I can't even remember and with all of thoses compagny my customers had lagg pikes or this kind of things.
I am hosting a gameserver service which required a top connectivity , most of my customers are in europe and I looked for the best dedicated provider in europe.
I tested OVH , ngz-server , bestserver.eu and much more but it was the same problem.
If someone know a good dedicated server provider in europe using premium bandwidth with good carier and not only with peerings .
I have looked a bit at serverboost.nl they seems serious but I have no feedback about them.
If you have any provider with a top connectivity it would help me a lot to choose what deserve my customers.
A DDos protection is a must also (not for bigg ddos but littles one ).
someone that can provide pricing for multiple providers (Level3, Global Crossing, and Cogent at a minimum) that I know are available in a building we have service in.
Is anyone else having issues with Layered Technologies. For the past 18+ hours they've been 'down' from the Global Crossing network. Does anyone know anyone at Savvis and/or Global Crossing that can check and see what's wrong with their routing?
what happens when I have 2 DNS servers on my domain and 1 fails? around 50% of the access fails... or they detect DNS timeout and try the other one, so 50% of the access would just take more time?
after months of disruption moving servers into a new data centre, our once reliable colocation company has now had nearly 6 hours downtime in the last 16 hours. So much for network redundancy.
Basically have 2 hosting accounts at different providers...each set-up for the same domain name...and then somehow wtih DNS make it so if host #1 goes down traffic goes to host #2 (which would basically be a splash screen explaining that host #1 is down and will be back soon).
DNS isn't my strong point, but I do know you can do this with MX records...so if the first server fails it tries the next until it gets a working one or reaches the end of the list. I'd just like to do it is A records.
It wouldn't be as simple as setting the nameservers like this would it?
Would it use the host1 nameservers as long as they're online, and if not failover to the host2 nameservers? If so, great, but what if the host1 nameservers are online but the server itself is not.
What are the smaller shops doing for switch redundancy? We have all our machines on dual Com Ed feeds but most switches in the $1k-$3k range only have one power supply. We recently had a power strip go flakey and of course the switch was plugged into it.
Is the best solution getting two switches and hooking each machine up to both? How hard is that to setup in Linux? I've used keepalived for whole machine failover but not for network failover.
I host several web clients that were recently impacted by the crap at ThePlanet. As I think about how to be more redundant (and repetitive) I'm not sure of my options.
What's the best practice to ensure that if you have a server at a data center that goes out, that you can (somewhat) easily switch over to a different server? I suppose one solution is to have 2 servers at 2 physical locations, and then you could just change the DNS record in the event of failure, but is there another solution I'm not aware of? Is there a good resource I can goto to read up on this info?
Is anyone having a problem with Intermedia's Hosted Sharepoint (WSS 3.0) Service? For the past couple days I've had sporadic service. Finally today, None of my pc's can get to my hosted sharepoint site. I even tried my site from 3 other locations, all with different ISP's, networks, and even geographic locations. (2 Corporate spots in OKC, Tulsa, Dallas).
Anyways their tech support says they can log in fine, and it's just a problem with my ISP. (I tried to emphasis the fact that it's 4 different ISP's all having the same issue).
Ping's good, I even get an authentication window. Just when I put in credentials I get The connection was interrupted.
Anyways phone support could only offer to open a ticket for me. Can anyone else using Intermedia Hosted Sharepoint let me know if they too are having problems? I realize Hosted Email is probably working fine.
for a linux VPS package provider that can provide both IPv4 and IPv6 (not tunneled) connectivity. IRC client/bots are not a priority but would be a bonus.
I am working on setting up a few servers that run cPanel and the usual software, minus any sort of DNS server. These servers are setup to sync all DNS records over to a cPanel "Dns Only" (ns1.domain.com), which in turn syncs all its records to a backup DNS server (ns2.domain.com).
In other words: [Domain registrar] | | [NS1]--Sync-->[NS2] | (Sync to NS1) | Cpanel Web Server
Now, say something happens to NS1 and the sever goes completely offline (i.e. power supply dies, CPU goes bad, etc.), which of the following scenarios would actually happen:
1) Because the registrar lists both NS1 and NS2 as NS records, NS1 would time out and the DNS lookup would look to the secondary DNS (NS2) for the record.
2) The registrar would randomly give out NS1 OR NS2 because of round robin, and if NS1 is given to a client as the result of a DNS lookup, the site will appear down, however if the client happens to be referred to NS2, the site would appear online.
3) The site would be down no matter what.
So, if someone with knowledge on the subject wouldn't mind enlightening me as to which of those would actually take place in the event of a failure on NS1, and maybe some suggestions as to keeping the DNS truely "redundant", then I would greatly appreciate it.
And Im aware that there are many 3rd party services that will take care of the DNS records and make them redundant (DYNDNS, DNSMadeEasy, etc) But I would prefer to keep the DNS in our full control.
I am interested in finding out any experiences people have had in the last year or so with Savvis or Net2EZ.
I'm primarily interested in experience with the IP connectivity they provide, as well as their co-location, reliability, etc.
I have experience with Savvis from quite a while ago, but presumably that experience may no longer apply.
It's likely we will end up buying transit from multiple carriers and deal with BGP, etc.
But I am also interested in hearing about Savvis's Diverse Internet availability product.
As for Net2EZ, I'd be primarily interested in hearing about their colo services and if anyone has had experience connecting to Carriers in the next door Equinix facility.
