VMGuru.nl – I choose (a virtual) life!

During the last month I have been very busy building a new infrastructure at a client site. I’m responsible for the overall technical solution and the basis, a VMware vSphere infrastructure build on five Dell PowerEdge R805’s, Dell EqualLogic PS5000 and 6000 storage and Cisco switches for LAN, DMZ and IP storage networking.

Just before the customer initiated their functional test period we discovered that the overall Windows network  performance was slow. We did several test like copying an 8 GB file from local vmdk to local vmdk and VM to VM and found that the storage performance was no issue but the network performance was very slow.

In the last few years that I have been working with virtualization I have always been a fan of a static network configuration. Meaning, when I configure ESX networking I like my network interfaces and physical switch ports to be configured at 1000MB full duplex if the switch/network interface combination allows it. The idea is that if you purchase gigabit network interfaces and switches you know the maximum speeds. So you configure it to run at it’s maximum capacity, eliminating overhead and using as much bandwidth as possible purely for data transfer.

So when we experienced slow network performance I had a colleague check the Cisco LAN switches for errors, drops, packet loss or any other flaw which might indicate a speed or duplex mismatch. None were found so I assumed that the network configuration was not the issue. But as we know by now, ‘Assumption is the mother of all fuck-ups!‘.

(more…)

When using a Cisco 3750 stack connected through stackwise technology you can add or remove a Cisco switch while the stack stays on. If you are adding or removing a switch from the stack, it is very important that the switch is turned OFF. The rest of the stack can keep doing its business.

For adding a switch to the stack follow these steps:

Step 1) On the new switch give the global command: switch stack-member-number provision type

Type is the type of switch you are adding to the stack.

When adding for example a third Cisco switch to the Cisco stack, use the following command:

switch 3 provision ws3750g-24t

Step 2) Power off the new stack member

Step 3) Connect the new member to the Cisco stack using the stacking cables, 1 loop at a time.

Step 4) Power on the new stack member. The switch will come alive and will receive the Cisco IOS version from the master, when that is completed it will be ready to service network requests.

(more…)

While I was updating the Determining VMware vCenter and ESX Build Numbers post I thought I would semi-automate the updating of the post with new build numbers for new releases, while working on it I started too fill an excel sheet and ended up with an excel sheet with the following products and build numbers for easy reference:

VMware vSphere 4 Suite (combines several products)
VMware Infrastructure 3 Suite (combines several products)
Cisco Nexus v1000 (1.0)
VMware ESXi (4.0, 3.5, 3.0)
VMware ESX  (4.0, 3.5, 3.0, 2.5, 2.0, 1.5, 1.0)
VMware Server (2.0, 1.0)
VMware vCenter Server (4.0, 2.5, 2.0)
VMware vCenter Converter Standalone (4.0, 3.0)
VMware vCenter Lab Manager (4.0, 3.0, 2.5, 2.4)
VMware vCenter Site Recovery Manager (4.0, 1.0)
VMware vCenter Server Heartbeat (5.5)
VMware vCenter Lifecycle Manager (1.0)
VMware vCenter CapacityIQ (1.0)
VMware vCenter AppSpeed (1.0)
VMware vCenter Chargeback (1.0)
(more…)

The Cisco Nexus 1000V is the first switch that can be placed in your vSphere virtual infrastructure, giving back network control back to the people that know the most about networking: The network admins. The Nexus 1000V is built on the distributed vSwitch technology in vSphere and can be managed by the same tools that network admins already use for manging their physical switches.

Cisco is organizing a series of free seminars aimed at sales professionals as well as admins.

(more…)

Last night I received an e-mail from Cisco thanking me for my work in the Nexus 1000V beta program and announcing the availability of the final product.

For those of you that don’t know the Cisco Nexus 1000V, it is a pure software implementation of a Cisco Nexus switch which can be used in vSphere 4. It resides on a server and integrates with the hypervisor to deliver VN-Link virtual machine-aware network services.