Monday, 31 October 2011

Preparing the ESXi Hypervisor for multiple NIC Usage

0 comments



Step 1:

  • Open the vSphere Client and proceed to ConfigurationNetworking and click Add Networking
ISCSI-mountVmware-01.png

Step 2:

  • Select VMKernel and click Next
ISCSI-mountVmware-02.png

Step 3:

  • Create a new network switch and select a NIC located on another subnet
ISCSI-mountVmware-03.png

Step 4:

  • Enter a new name for this new network and click next
ISCSI-mountVmware-04.png

Step 5:

  • Enter an IP Address and Subnet address for this secondary NIC and click next
ISCSI-mountVmware-05.png

Step 6:

  • Final Confirmation Settings
ISCSI-mountVmware-06.png

Step 7:

  • The second network has been added to this Hypervisor
ISCSI-mountVmware-07.png

Step 8:

  • Repeat this process for each additional network to be added to the Hypervisor

Step 9:



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
ISCSI-mountVmware-08.png

Step 2:

  • In this example, the iSCSI Initiator is disabled, click Configure to configure the settings of the iSCSI Initiator
ISCSI-mountVmware-09.png

Step 3:

  • Enable the iSCSI Initiator
ISCSI-mountVmware-10.png

Step 4:

  • Once the iSCSI Initiator is enabled, click on Dynamic Discovery
ISCSI-mountVmware-11.png

Step 5:

  • Enter the primary IP Address of the Synology DiskStation
ISCSI-mountVmware-12.png

Step 6:

  • If mounting for MPIO, enter the secondary IP address of the Synology DiskStation, located within the secondary subnet of the ESXi Hypervisor
    • The preceding direction may skipped for non-MPIO Environments
ISCSI-mountVmware-13.png

Step 7:

  • Rescan the Host Bus Adapter
ISCSI-mountVmware-14.png

Step 8:

  • The iSCSI Initiator has detected the target on the Synology DiskStation.
ISCSI-mountVmware-15.png

Step 9:

  • Right Click on the Target and click Manage Paths
    • The preceding direction may skipped for non-MPIO Environments
ISCSI-mountVmware-16.png

Step 10:

  • Select Round Robin (VMWare)
    • The preceding direction may skipped for non-MPIO Environments
  • Note that within the Path Management, that the ESXi Hypervisor is using two paths (via two subnets) to mount the same iSCSI Target.
ISCSI-mountVmware-17.png

Step 11:


Formatting the iSCSI Target for usage within the ESXi Hypervisor

Overview: This section of the article will guide the administrator in formatting the iSCSI Target for usage within ESXi Hypervisor

Step 1:

  • Within the Configuration tab, click on Storage, and click Add Storage
ISCSI-mountVmware-19.png

Step 2:

  • Select Disk/LUN and click Next
ISCSI-mountVmware-20.png

Step 3:

  • Find the iSCSI Target, and click Next
ISCSI-mountVmware-21.png

Step 4:

  • Review the current disk layout and click Next
ISCSI-mountVmware-22.png

Step 5:

  • Enter a new datastore name for this new storage.
ISCSI-mountVmware-23.png

Step 6:

  • Select a block size to use for this new storage
    • Using default settings is recommended
ISCSI-mountVmware-24.png

Step 7:

  • Final Confirmation Settings
ISCSI-mountVmware-25.png

Step 8:

  • The new datastore has been added...
ISCSI-mountVmware-26.png

Step 9:

  • ...and is ready for use
ISCSI-mountVmware-27.png

Sunday, 30 October 2011

vicfg-mpath35 - configure multipath settings for Fibre Channel or iSCSI LUNs

0 comments

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 of a given LUN path to either "on" or "off". This option requires that you also specify the --lun and --path options.
--preferred | -f
Sets the given path to be the "preferred" path for a given LUN. This option requires that you also specify the --lun and --path options.
--query | -q
Queries a specific LUN for its information and print it. This option requires that you also specify the --lun option.
--path | -P
Specifies the path to use in other operations. You cannot use this option by itself.
--lun | -L
Specifies the LUN to use in other operations. You cannot use this option by itself.
--detailed | -d
Displays all information about a LUN and its paths including the vml name of the LUN.
--bulk | -b
Shows all LUNs and paths in a format easily parsed by scripts.
--hbas | -a
Prints the list of HBAs that can be identified by a unique ID. This option lists Fibre Channel and iSCSI devices. Parallel and Block devices do not appear in the list.
--vihost | -h
When you execute this command with --server pointing to a vCenter Server system, you can use --vihost to specify the ESX/ESXi host to run the command against.

EXAMPLES

List all LUNs and the paths to these LUNs through adapters on the system:
 vicfg-mpath35 --server <servername> --username <user name> 
    --password <password> -l
Set the policy for a specific LUN. Requires --lun is also specified to indicate the LUN to operate on:
 vicfg-mpath35 --server <server name> --username <user name>
    --password <password> --policy mru --lun vmhba0:8:0
Set the state for a specific LUN path. Requires both --lun and --path are specified. This operation may appear to fail if there is active I/O on a path that is set to "off":
 vicfg-mpath35 --server <server name> --username <user name>
    --password <password> --state <on|off> --path <path flag> --lun <lunname>
Set the given path to be the preferred path for the given LUN. Requires both --path and --lun are specified:
 vicfg-mpath35 --server <server name> --username <user name> 
    --password <password> --preferred --path vmhba0:8:0 --lun vmhba0:8:0
Query the information on a specific LUN:
 vicfg-mpath35 --server <server name> --username <user name>
    --password <password> --query --lun vmhba0:8:0
Indicate which LUN to operate on. You can specify the LUN either with its internal VMkernel vmhba name (vmhbaX:X:X) or with its vml name as found in /vmfs/devices/disks:
 vicfg-mpath35 --server <server name> --username <user name> 
    --password <pasword> --policy mru --lun vmhba0:8:0
Return a bulk path listing suitable for parsing:
 vicfg-mpath35 --server <server name> --username <user name>
    --password <password> -b

Saturday, 29 October 2011

Which ESX log file

4 comments

Log FileNameDetails
/var/log/vmkernelVmkernelRecords activities related to the virtual machines and ESX host
/var/log/vmkwarningVmkernel WarningsA copy of everything marked as a warning or higher severity from vmkernel log. Easier to look through than vmkernel log
/var/log/vmksummaryVmkernel SummaryUsed for avaialability and uptime statistics. Human-readable summary in vmksummary.txt
/var/log/vmware/hostd.logHost Agent LogContains information on the agent that manages and configures the ESX host and its virtual machines
/var/log/vmware/vpxVirtualCenter AgentContains information on the agent that communicates with VirtualCenter
/var/log/messagesService ConsoleLog 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.logESX Boot LogESX Boot log, logs all ESX boot events
/var/log/vmware/webAccessWeb AccessRecords information on Web-based access to ESX Server
/var/log/secureAuthentication LogContains records of connections that require authentication, such as VMware daemons and actions initiated by the xinetd daemon
/var/log/vmware/esxcfg-firewall.logESX Firewall LogContains all firewall rule events
/var/log/vmware/aamHigh Availability LogContains information related to the High Availability (HA) service
/var/log/vmware/esxupdate.logESX Update LogLogs all updates completed using the esxupdate tool

Friday, 28 October 2011

Which ESX log file

0 comments

• 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 3rd party app acting up. This log has NOTHING to do with virtual machines. The SERVICE CONSOLE (red hat kernel) has NO awareness of the VMs (worlds) running on the VMKERNEL.
• Web Access – /var/log/vmware/webAccess – Records information on Web-based access to ESX Server.
• Authentication log – /var/log/secure – Contains records of connections that require authentication, such as VMware daemons and actions initiated by the xinetd daemon.
• VirtualCenter agent – /var/log/vmware/vpx – Contains information on the agent that communicates with VirtualCenter.
• Virtual Machines – The same directory as the affected virtual machine’s configuration files; named vmware.log – Contain information when a virtual machine crashes or ends abnormally.