# Number of days to generate, default = 365
$NumDays 		= 365
$AccessGroup 	= "Gasten"
$ExpiryTime 	= "20:00"
$StartTime 		= "07:00"
$OutputCSV		= "C:\TEMP\wireless.csv"

$SshHost 		= "127.0.0.1"
$SshUser		= "someuser"

$access_codes = @()

# Start SSH session
New-SshSession $SshUser $SshHost
Invoke-Ssh "z"
Invoke-Ssh "conf t"
Invoke-Ssh "wireless F"
Invoke-Ssh "conf t"
Invoke-Ssh "radius-server local"

$i = 0;
do {
	# WSEM format: mm/dd/yyyy hh:mm
	$date = (Get-Date).AddDays($i)
	$date2 = Get-Date $date -Format "dd-MM-yyyy"
	$date = Get-Date $date -format "MM:dd:yyyy"
	$pass = RandomPassword 4
	$user = RandomPassword 4
	$output = "rad-user $user password 0 $pass group $AccessGroup guest expiry-time $ExpiryTime expiry-date $date start-time $StartTime start-date $date"

	# add user through SSH
	Invoke-ssh $output

	$Response = New-Object PSObject
	Add-Member -InputObject $Response -MemberType NoteProperty -Name "Datum" -Value $date2
	Add-Member -InputObject $Response -MemberType NoteProperty -Name "Gebruikersnaam" -Value $user
	Add-Member -InputObject $Response -MemberType NoteProperty -Name "Wachtwoord" -Value $pass
	$access_codes += $Response

	$i++;
} while ( $i -le $NumDays )

# Save and disconnect SSH
Invoke-ssh "write mem"
Remove-SshSession

# Export to CSV
$access_codes | Export-Csv $OutputCSV

# Helper functions
function RandomPassword ([int]$intPasswordLength)
{
   $strNumbers = "1234567890"
   $strCapitalLetters = "ABCDEFGHIJKLMNOPQRSTUVWXYZ"
   $strLowerLetters = "abcdefghijklmnopqrstuvwxyz"
   $rand = new-object random

   for ($a=1; $a -le $intPasswordLength; $a++)
      {
         if ($a -gt 3)
           {
      	      $b = $rand.next(0,3) + $a
      	      $b = $b % 3 + 1
      	   } else { $b = $a }
      	 switch ($b)
      	   {
      	      "1" {$b = "$strNumbers"}
      	      "2" {$b = "$strCapitalLetters"}
      	      "3" {$b = "$strLowerLetters"}
      	   }
         $charset = $($b)
         $number = $rand.next(0,$charset.Length)
         $RandomPassword += $charset[$number]
      }
   return $RandomPassword
}

Special thanks to Joel Bennett’s SharpSSH wrapper for PowerShell (located here: http://huddledmasses.org/scriptable-ssh-from-powershell/) which I used to automate the command line commands for the HP WSEM.
This shows the great power of PowerShell for automating virtually anything!

To find out the vmnic number, simple click the error, the vmnic number is shown on that page:

To resolve this you simple have to put the nics into the “Down” state using “ifconfig”:

ifconfig vmnic3 down

To make this change more permanent (surviving reboots) you have to put the command in the file /etc/rc.local (this file is called once the host has been started)
Here is an example rc.local disabling 2 nics:


#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

touch /var/lock/subsys/local
ifconfig vmnic3 down
ifconfig vmnic7 down


• First you have to fix up the physical cabling;
• next, you have to setup up the zoning;
• up next you have to present the virtual disks to the VMware hosts.

Last but not least you need to take care of pathing for your presented virtual disks. For our HP EVA SAN, vSphere defaults to the “Most Recently Used (VMware)” policy.
In the past we used to manually load balance using fixed paths. This was mainly because the round robin policy mechanism was still in an EXPERIMENTAL status.
The round robin policy offers great advantages over the default MRU policy:

• The HP EVA offers ALUA (Asymmetrical Logical Unit Access). ALUA allows a LUN to be accessed via its primary path (via the owning Storage Processor) and via an asymmetrical path (via the not-owning Storage Processor) I/O to the not-owning Storage Processor or not-optimized path  comes with a performance penalty because the I/O has to be transmitted over the internal connection between the storage processors which does not have much bandwidth;
• using ALUA in combination with Round Robin will load balance the I/O’s over the most optimized paths for that LUN;
• the load is balanced between the two optimized paths rather then the most recently used path (as with the MRU policy).

Setting the pathing policy for each individual LUN can become quite a job. Good thing there is a way to set the default pathing policy for new discovered LUN’s using “esxcli”

esxcli nmp satp setdefaultpsp -–psp VMW_PSP_RR –-satp <Storage Array Type>

To figure out the storage array type for your virtual disk, right click a LUN and select “Manage Paths” (the screenshot highlights the Storage Array Type.