Translate this

    Translate to:

The back catalog

Simulating a more interesting environment with Vyatta and VMware ESXi

[Part 2 of this series which involves the actual configuration of the Vyatta routers is now up here -crt]

At work we’ve recently made the decision to migrate to Exchange 2010 from Exchange 2003. While we do have an environment that we can use for some testing of the migration it doesn’t mimic our production environment closely enough for me to be comfortable using it as the sole test area. Given the changes in how Exchange 2010 (E2KX) works vs 2003 I wanted to be able to simulate multiple (2) Active Directory sites (i.e. subnets), a DMZ, and the “Internet” including some really simple firewalls.

I wanted to use virtual machines to go through this exercise so that I could take snapshots and repeat the various steps and/or variations of them if necessary. In order to do this I utilized the Vyatta Community Edition based routers to help create my virtual “enterprise” environment. I’ve talked about Vyatta before in this article. In this post I’ll talk a little about the process I went through to get to my final configuration (shown below).  In subsequent articles I’ll go  through the actual router and VMware configuration process.

Final Environment

The final environment as laid out on two interconnected servers

My lab environment at home consists of two Dell PowerEdge servers (one a PE2850, the other a 2950 each with 8Gigs of RAM). Both servers are running ESXi 4.0. Since the 2850 can’t run 64 bit VMs I was going to install the Exchange 2003 servers and Windows 2003 DCs on it. Then I’d install VMs running Server 2008R2 on the 2950 with Exchange 2010. Both servers are connected to my home network and since I was going to be using both I wanted to have some way for VMs on each host to be able to communicate with others without necessarily having all the traffic come across my home network. Since both Dells have multiple NICs I connected them with a crossover cable ending up with something like this:

Physical view of the network

In initially penciling out a plan for what I wanted to do I had nine VMs scattered across four subnets.

Isolated environment with multiple gateways per subnet

Considering my limited resources and my need to keep some other unrelated VMs up and running while I’m testing, I trimmed this down to 7 by combining the Domain Controllers and Exchange 2003 servers together in the HQ and Remote subnets.

Consolidating functions to reduce # of VMs

In further looking at this from a networking perspective, I was hit with the realization the initial configuration with two routers attached to the HQ and DMZ subnets would require me to manage routing on each individual VM in each of those subnets as well as on each of the routers. As an example one can look at the Exchange 2010 server in the HQ site/subnet.

Continue reading Simulating a more interesting environment with Vyatta and VMware ESXi

Updated ESX 3i scripts for Nagios

I had a little time today and needed to mentally switch gears so I took a look again at the 3i storage script for Nagios and made some changes to it to clean it up a little bit. I also made clones…er …versions rather…. for monitoring CPU status, memory status, and sensor data (i.e. [...]

Checking storage on a dell poweredge 2900 running ESX 3i

As I mentioned in an earlier post one of the issues we’ve had with the idea of deploying ESX 3i vs 3.5 is the ability to monitor the hardware since neither the DRAC card nor the BMC via IPMI seem to be able to give us all the info we need. I had looked briefly at the VI-Perl toolkit and the VI SDK but not spent a lot of time on it.

I installed 3i on a new PE 2900 today to take a look at this again. I had previously pulled one of the disks in the server so that I could be certain something was “wrong” so I had something to test against. Below is the “Health Status” as shown via the VI client. As you can see “Storage” shows up as being in a warning state since RAID 6 Virtual Disk shows as being in a “Warning” state. It’s worth noting that since I pulled a hard drive Physical Disk 7 does not show in the list of items under Storage. I’m assuming that if the drive was actually bad it’d show up as failed. But I don’t know that I want to damage a perfectly good drive to find out.


Continue reading Checking storage on a dell poweredge 2900 running ESX 3i

IPMI and the Dell PowerEdge – Part the Third

Okay now that we have a user that’s set up for access to IPMI what can we find out about our server from a monitoring perspective?

If run ipmitool -h we get a list of commands we can run.

Several of these “commands” have sub commands. For example the ‘chassis’ command

Has sub-commands of: status, power, identify, policy, restart_cause, poh, bootdev, selftest.

Continue reading IPMI and the Dell PowerEdge – Part the Third

IPMI and the Dell PowerEdge – Part the Second

Setting up IPMI via the DRAC

We’ll walk through the steps to set up the server for monitoring via IPMI using the DRAC. It is supposedly possible to do this without the DRAC, but I haven’t had a reason to try to do that yet.  

  1. Log in the DRAC (ex: https://<RAC IP Address>/ )
  2. Once logged in (see below) choose the “Remote Access” option
    Continue reading IPMI and the Dell PowerEdge – Part the Second

IPMI and the Dell PowerEdge

In one of my projects at work, we’ve been debating whether to use ESX 3i (installable) or ESX 3.5 on a large number of Dell servers we’re getting ready to deploy. The advantage of 3i is we can treat the host as more of an appliance (i.e. hopefully fewer patches/maintenance). Downside is monitoring. [...]