If you’re directly connecting linux hosts, I recommend you look at creating a Bonding Adaptor. I understand that you may wish to be connecting linux hosts directly.
#Juniper s task lamp free
In my environment, I’m using the free version of ESXi 4.1. The only thing you have to watch out for, is that on at least one switch, you set the lacp mode to be active. Obviously with gigabit Ethernet right through the network this isn’t much bandwidth, so the idea is to keep as little data traveling that link as possible (network broadcasts only hopefully!)įirst, the following configuration configures the aggregate Ethernet link between the switches: I’ve opted to use 4 physical ports in my 24 port switches (ge-0/0/20 to ge-0/0/23) to give me a 4Gbit/s backbone between them. In my switch design with the EX2200’s, I’m using aggregate Ethernet 802.3ad Etherchannel between my two switches. Ok, so this heading is a lie, but let me explain. If however, you’re going to be pumping some more bandwidth intensive applications through your network (thus require more then gigabit Ethernet connections to the hosts) or have the need for more then a single VLAN and intra-VLAN routing is required (that’s all outside the scope of this tutorial.) I can strongly recommend you start looking at the EX4200 model switches (set up in a virtual chassis), which can do all your highly available layer 3 IP routing and support multi gigabit Ethernet to your hosts by spanning Ethernet channel across both physical switches. If you’re in the same boat I was, I can suggest a pair of Juniper EX2200’s. Because our bandwidth requirements in this site wasn’t terribly demanding (simple database server, few web, mail servers and the like), a single gigabit Ethernet link to all hosts was all that we required. We’ll be replacing the single switch (in my case, unmanaged old gigabit switch) with a pair of managed switches. We will eliminate every single point of failure such that in the event of a system outage/failure, the system can self recover with at most a minute of unscheduled down time. The goal with this tutorial is to attempt to help your administrators sleep at night. In the event of a system failure, your system administrator (me in this case) will have to hop in a cab and rush to the server room to fix the problem. You have a single internet connection, single router/firewall, single switch and a bunch of hosts hanging from that switch. If you’re reading this, I’m guessing your current network topology looks something like
#Juniper s task lamp software
This blog post is split up in two parts, this first post in the series talks about setting up the network infrastructure, the second talks about setting up the software stack. Instead, please consider this post as an overview to help enlighten you and link you to more specific information to help you set this up in your own environment. However what I won’t be doing is providing complete configuration examples.
The first part is talking about setting up the physical hosts and topology (using Juniper EX2200 switches, SRX100 border firewall’s and ESXi (free) hypervisors for the software stack.) The second part is talking about setting up the software stack to deliver our LAMP stack in a highly redundant fashion. During the course of this tutorial, I’ll run you through it in two parts. While I’ve chosen WordPress to be the demonstration of this post, the concepts will work with any apache/mysql LAMP stack software. After you’ve finished reading this blog post, you should have the knowledge to be able to eliminate the single point of failures in hosting a WordPress website. I’ve wanted to write this blog post for a while. During the process of ensuring high availability (HA), I realized that many small companies might have similar need, but with more pressing tasks and limited man hours, without a post that talks about all the issues and solutions in one place, many companies and organisations tend to leave single points of failure living with the chance that they’re not going to fail any time soon. In one of my last little tasks at work, I was asked to eliminate single points of failure in the software and hardware stack without spending a fortune on hardware or software licenses.
0 kommentar(er)
