My IT Blog

Step 1: Open the vSphere Client and proceed to  Configuration ,  Networking  and click  Add Networking Step 2: Select  VMKernel  and click  Next Step 3: Create a new network switch  and select a NIC located on another subnet Step 4: Enter a new name for this new network and click  next Step 5: Enter an IP Address and Subnet address for this secondary NIC and click  next Step 6: Final Confirmation Settings Step 7: The second network has been added to this Hypervisor Step 8: Repeat this process for each additional network to be added to the Hypervisor Step 9: Proceed with  Mounting the iSCSI Target on the ESXi Hypervisor Mounting the iSCSI Target on the ESXi Hypervisor Overview: This section will guide the administrator in mounting iSCSI Targets on the Synology DiskStation to the ESXi Hypervisor. Step 1: Within the  Configuration  tab, click on  Storage Adapters , select the  iSCSI Software Adapter  and click  Properties Step 2: In this example, the iSCSI In

SYNOPSIS vicfg-mpath35 [OPTIONS] DESCRIPTION vicfg-mpath35 provides an interface to configure multipath settings for Fibre Channel or iSCSI LUNs on ESX/ESXi version 3.5 hosts. Use vicfg-mpath for ESX/ESXi 4.0 and later hosts. OPTIONS --help Prints a help message for each command-specific and each connection option. Calling the command with no arguments or with  --help  has the same effect. --list | -l Lists all LUNs and the paths to these LUNs through adapters on the system. For each LUN, the command displays the type, internal name, console name, size, and paths, and the policy used for path selection. --policy | -p Sets the policy for a given LUN to one of "mru", "rr", or "fixed". Most Recently Used (mru) selects the path most recently used to send I/O to a device. Round Robin (rr) rotates through all available paths. Fixed (fixed) uses only the active path. This option requires that you also specify the --lun option. --state | -s Sets the state

Log File Name Details /var/log/vmkernel Vmkernel Records activities related to the virtual machines and ESX host /var/log/vmkwarning Vmkernel Warnings A copy of everything marked as a warning or higher severity from vmkernel log. Easier to look through than vmkernel log /var/log/vmksummary Vmkernel Summary Used for avaialability and uptime statistics. Human-readable summary in vmksummary.txt /var/log/vmware/hostd.log Host Agent Log Contains information on the agent that manages and configures the ESX host and its virtual machines /var/log/vmware/vpx VirtualCenter Agent Contains information on the agent that communicates with VirtualCenter /var/log/messages Service Console Log from the Linux kernel. Useful for underlying Linux issues. The kernel has no awareness of VMs running on the VMkernel /var/log/vmware/esxcfg-boot.log ESX Boot Log ESX Boot log, logs all ESX boot events /var/log/vmware/webAccess Web Access Records information on Web-based access to ESX Server /var/log/se

• Vmkernel – /var/log/vmkernel – records activities related to the virtual machines and ESX server. • Vmkernel Warnings – /var/log/vmkwarning – This log is a copy of everything marked as a warning or higher severity from vmkernel log. It is much easier to look through this for warnings and  errors , instead of filtering through the full information in the vmkernel logs. • Vmkernel Summary – /var/log/vmksummary – Used to determine uptime and availability statistics for ESX Server; human-readable summary found in /var/log/vmksummary.txt • ESX Server host agent log – /var/log/vmware/hostd.log – Contains information on the agent that manages and configures the ESX Server host and its virtual machines (Search the file date/time stamps to find the log file it is currently outputting to). • Service Console – /var/log/messages – This log is the log from the Linux kernel (service console), which is generally only potentially useful in the case of a host hang, crash, authentication  issue, or 3

We get an enormous amount of questions about VMware’s HA (High Availability), especially when users see a message stating there are Insufficient resources to satisfy HA failover. We have already discussed the mechanism that HA uses to provide high availability here . Now we need to understand capacity calculations. In current versions of ESX (3.02) and earlier the following calculation applies for failover capacity. HA Failover Capacity Failover Capacity is determined using a slot size value that is calculated on the cluster. Slots are calculated by a combination of the total CPU and Memory that are in the physical hosts. The calculation for failover capacity works as follows: Let’s say you have 4 ESX servers in your VMware HA cluster and Configured Failover capacity on the cluster is set to 1. Physical memory in the hosts is as follows: ESX1 = 16 GB ESX2 = 24 GB ESX3 = 32 GB ESX4 = 32 GB In the cluster you have 24 VM’s each configured and running. Of the 24 VM’s run

Linux - Ubuntu 8.04 Server I am not going to go through each and every step of the Ubuntu installation as that is really straight forward. I downloaded the 8.04 Server version from http://www.ubuntu.com/getubuntu/download and started the installation one on of the nodes. During disk partitioning, select manual mode and delete any existing partitions (if there are any). Create one partition for your main system and make it 5GB. This partition will be used for your Dom0 and 5GB should be more than enough. Create a second partition for your swap for Dom0. Make this 512MB as we later will configure Dom0 to use 512MB of RAM. Create a third partition with all your remaining space. At the packages selection step do not select any packages. Leave everything deselected. A few minutes later you should have a basic installation of Ubuntu 8.04 Server running. Ubuntu - Base configuration A few things need to be done to the freshly installed Ubuntu Server before we start installing

Assigning a virtual IP to a NIC is a very easy task either you use the system-config-networktool or just do some text file editing. The script ifconfig can also be used to create a virtual network interface, but this would not be permanent since the changes ifconfig makes do not survive a reboot. In this post I’ll stick with the “manual” way… In Fedora, all information about the network interfaces is kept in the following directories: /etc/sysconfig/network-scripts/ /etc/sysconfig/networking/ I assume that the default NIC configuration script is: /etc/sysconfig/network-scripts/ifcfg-eth0. Mine looks like this:DEVICE=eth0 BOOTPROTO=static BROADCAST=192.168.0.255 HWADDR=00:00:00:00:00:00 IPADDR=192.168.0.1 NETMASK=255.255.255.0 NETWORK=192.168.0.0 ONBOOT=yes TYPE=Ethernet GATEWAY=192.168.0.254 BOOTPROTO: sets the protocol that is used when the device is initialized. Since we use static IPs we set it to static. HWADDR: is the MAC address of your network card. Do not change it

An Overview on Folder Redirection Folder Redirection is a Group Policy feature that enables users to redirect the system folders containing the profile of a user on the network, through the use of the Folder Redirection node in the Group Policy Object Editor console. This basically makes folder redirection a user configuration option. Through the use of the Folder Redirection feature, users can configure that the system folders’ contents on the user remains the same, irrespective of the particular computer used to log onto the system. The system folders that users can configure for folder redirection are listed below: Application Data: This folder contains user configuration files, user specific data that applications utilize, and Public Key Infrastructure files. Desktop: This folder holds the shortcuts and files that appear on the user’s desktop. My Documents: This folder holds the user’s files and pictures. Start Menu: This folder holds the shortcuts and files that appear on