Saturday, 24 December 2011

A Brocade Switch CLI Zoning Configuration Walkthrough

Scenario:

A new VMware host server has been purchased with a couple of Fibre Channel (FC) HBAs. You are tasked with patching the fibre cables into a Fibre Channel switch stack pair – one fibre cable per switch – and then need to configure the zoning on the FC switches to support connection to an FC SAN.

Walkthrough:

Note: The output examples below have been truncated to show just the most interesting bits. In the examples we are configuring the zoning for a new host called ESX03, have connected the FC HBA's into ports number 8 on each FC switch. The FC switches are called FCSW01 and FCSW02. The FC switches used were HP 4/16 B-Series (Brocade) running Fabric O/S 6.2.2d. And the SAN is a HP EVA with two controllers (EVA_ContrA and EVA_ContrB.)

Using a tool like Putty (for SSH, Telnet, Serial, ...) or similar, and via a connection to a fibre channel switch using either a serial console connection or ethernet management interface; log in to the CLI and run these commands:

Step 1:> switchshow
Run the switchshow command to find the zoning config name and WWN of newly connected HBA. Copy the WWN for later use.

Example:
The example below shows the config name "Company_Default" and looking on the line for port 8 gives us the WWN of connected FC HBA

FCSW01:admin> switchshow
zoning: ON (Company_Default)

Area Port Media Speed State Proto
=====================================
8 8 id N4 Online F-Port 10:00:00:00:c9:83:63:1d

Step 2:> cfgshow
Run the cfgshow command to display the configuration and see how the zoning is currently configured.

Example:
The example below shows how the ESX02 zone (ESX02z) is configured. The ESX02 zone contains the EVA SAN's controller A port 1 and controller B port 1 (controller ports 2 are plugged into FCSW02,) and the ESX02 hosts FC HBA which is connected into FCSW01.) Also displayed are the aliases used and their associated WWNs.

FCSW01:admin> cfgshow
Defined configuration:
cfg: Company_Default
ESX02z
zone: ESX02z EVA_ContrBP1; EVA_ContrAP1; ESX02
alias: EVA_ContrBP1 50:00:1f:e1:50:0b:81:5c
alias: EVA_ContrAP1 50:00:1f:e1:50:0b:81:58
alias: ESX02_1 10:00:00:00:c9:5e:8d:06

Effective configuration:
cfg: Company_Default
zone: S_ESX02z
50:00:1f:e1:50:0b:81:5c
50:00:1f:e1:50:0b:81:58
10:00:00:00:c9:5e:8d:06

Step 3:> alicreate "NAME", "WWN"
Run the alicreate command with the alias name you want to give to the connected FC HBA, and the WWN number obtained from step 1.

Example:
The example below shows creation of an alias name of ESX03_1 for the new host ESX03's 1st HBA, with WWN 10:00:00:00:c9:83:63:1d

FCSW01:admin> alicreate "ESX03_1", "10:00:00:00:c9:83:63:1d"

Step 4:> zonecreate "NAME", "ALIASofFCHBA"
Run the zonecreate command to create a zone for the VMware host server, and use the alias created in step 3 to add the FC HBA to the zone.

Example:
The example below shows creation of a zone called ESX03z with the alias ESX03_1 added

FCSW01:admin> zonecreate "ESX03z", "ESX03_1"

Step 5:> zoneadd "NAME", "ALIASofSAN(s)"
Run the zoneadd command to add the aliases of the SAN's FC controller ports to the zone

Example:
The example below shows addition of the EVA's controller A port 1 (EVA_ContrAP1) and controller B port 1 (EVA_ContrBP1) to the ESX03z zone.

FCSW01:admin> zoneadd "ESX03z", "EVA_ContrAP1"
FCSW01:admin> zoneadd "ESX03z", "EVA_ContrBP1"

Step 6:> cfgadd "CONFIG_NAME","ZONEtoADD"
Run the cfgadd command to add the newly create zone to the configuration.

Example:
The example below shows the addition of the ESX03z zone to the Company_Default configuration.

FCSW01:admin> cfgadd "Company_Default","ESX03z"

Step 7:> cfgsave
Run the cfgsave command to save the configuration, entering yes to the prompt

Example:

FCSW01:admin> cfgsave
You are about to save the Defined zoning configuration. This action will only save the changes on Defined configuration. Any changes made on the Effective configuration will not take effect until it is re-enabled.
Do you want to save Defined zoning configuration only? (yes, y, no, n): [no] yes
... FCSW01, cfgSave completes successfully. ...

Step 8:> cfgenable CONFIG_NAME
Run the cfgenable command to enable the configuration, entering yes to the prompt.

Example:

FCSW01:admin> cfgenable Company_Default
You are about to enable a new zoning configuration. This action will replace the old zoning configuration with the current configuration selected. If the update includes changes to one or more traffic isolation zones, the update may result in localized disruption to traffic on ports associated with the traffic isolation zone changes.
Do you want to enable 'Company_Default' configuration (yes, y, no, n): [no] yes
... zone config "Company_Default" is in effect ...
Updating flash ...

Step 9: Repeat
Repeat Steps 1 to 8 on the other FC Switch, for the VMware hosts 2nd FC HBA, and FC SANs other controller ports.

THE END

Note: Instead of adding WWNs to zones, can also designate specific ports to be a member of a zone (a default configuration may have one zone with all ports designated.)

Example:
In the example below, instead of defining a WWN for ESX01 (as is done for ESX02), a port number is designated instead:
alias: ESX01_SP3 1,3
alias: ESX02 10:00:00:00:c9:5e:8d:06

For Search Engine: How to configure / setup additional zoning - using CLI - on a Brocade switch.

Thursday, 22 December 2011

Windows 7 XP Mode User Experience (or How Easy it is to Run Native XP Apps from Windows 7)

Windows XP Mode is a preconfigured Windows XP Mode environment, and this quick walkthrough will show how easy it is to get a native XP application running from Windows 7. With Christmas and the New Year coming, might be fun to crack out some old XP games and have a go at running them again alongside Windows 7 games to reminisce on times gone by and compare old to new.

1: Download Windows XP Mode and Windows Virtual PC from

2: Install WindowsXPMode
Note: The WindowsXPMode virtual PC is a 1.13GB base disk, and configured with 512MB RAM by default

3: Install Windows Virtual PC and reboot system

4: i: All Programs -> Windows Virtual PC -> Click Windows XP Mode
ii: Accept License Agreement -> Next
iii: Choose installation folder and credentials -> Next
iv: Choose Automatic Updates settings -> Next
v: Start Setup (the drives on the computer will be shared with Windows XP Mode)

5: After the Windows XP Mode Virtual PC has loaded; install the native Windows XP application and copy a shortcut for the application to C:\Documents and Settings\All Users\Start Menu\Programs

Note that you can place any shortcut into the above folder to use later from the Windows 7 PC. In the below image, the shortcut to Internet Explorer 6 is placed in the folder

6: Log off and then click the X in the top right corner of the Windows XP Mode window and the XP Mode Virtual PC will hibernate.

7: From the Windows 7 Machine:
All Programs -> Windows Virtual PC -> Windows XP Mode Applications
Click on the XP Mode Application to run (can also copy the shortcut to desktop)
Example below showing Internet Explorer 6 and Internet Explorer 8 running side-by-side on Windows 7

THE END

Afternote

Windows XP Mode is included in the Microsoft Exam 70-669 syllabus. The 70-669 Exam is one of three exams required for the 'MCITP: Virtualization Administrator on Windows Server 2008 R2' qualification - full list of exams below:

Exam 70-659: TS: Windows Server 2008 R2, Server Virtualization
Exam 70-669: TS: Windows Server 2008 R2, Desktop Virtualization
Exam 70-693: Pro: Windows Server 2008 R2, Virtualization Administrator

Links to useful resources for Exam 70-669

An excellent list of video links:

Free e-book:

Microsoft links:

Thursday, 15 December 2011

Citrix Udadmin Delete Script & Event 1163

Scenario:

Users are unable to logon to their Citrix XenDesktop 5 desktops, and the following error is seen in the Windows Application log on the XenDesktop 5 Controller:
Event 1163, Citrix Broker Service : No connection license available. To resolve, free licenses by closing sessions that are not needed, or add more licenses.”

Solution to free one license at a time:

i: Logon to the Citrix Licensing server and open up a command prompt.
ii: Run the command below to 'list all licensed users and devices organized by feature and version':

udadmin -list -a

iii: Then run either the first command below to 'delete a licensed user from the feature specified' or the second command below to 'delete a licensed device from the feature specified' (Note that … -device … -delete did not work until Citrix License Server Version 11.9 Build #11011.)

udadmin -f featurename -user username -delete
udadmin -f featurename -device devicename -delete

Solution to free multiple licenses at a time:

i: From a command prompt run the command

udadmin -list -a > users.txt

ii: Edit the users.txt file to contain just the user strings (users or devices) as desired (don't worry about preceding spaces,) remembering to note the feature name from the output.
iii: (If required) Edit strFeature string in udadmindelete.vbs script if different from XDT_ENT_UD.
iv: (If required) Change strUserDev string in udadmindelete.vbs script from user to device if running against a list of devices.
v: Double-click on the udadmindelete.vbs script to run (the users.txt file needs to be in the same location as the udadmindelete.vbs script.)

And we're done!

udadmindelete.vbs script:

Copy all the contents below into a text document and save as udadmindelete.vbs.
Remember to change the string contents for strFeature and strUserDev (user or device) as per requirements.
Apologies if this is not the most elegant script, was a mash up of bits and pieces from around the net!

Option Explicit
Dim objFSO, strTextFile, strData, strLine, arrLines, objShell, strTmp, strFeature, strUserDev
CONST ForReading = 1
set objShell = wscript.createObject("wscript.shell")

'Name of the text file to be read
strTextFile = "users.txt"

'ADJUST strFeature AS PER REQUIREMENTS
strFeature = "XDT_ENT_UD"

'ADJUST strUserDev AS PER REQUIREMENTS
strUserDev = "user"

'Create a File System Object
Set objFSO = CreateObject("Scripting.FileSystemObject")

'Open the text file - strData now contains the whole file
strData = objFSO.OpenTextFile(strTextFile,ForReading).ReadAll

'Split the text file into lines
arrLines = Split(strData,vbCrLf)

'Step through the lines
For Each strLine in arrLines
strTmp = "udadmin -f " & strFeature & " -" & strUserDev & " " & strLine & " -delete"
'To see the command being, run add a line below with wscript.echo strtmp
objShell.Run strTmp
Next

'Cleanup
Set objFSO = Nothing

Tuesday, 13 December 2011

Veeam Backup and Replication v6 Pre-Install Checklist

1: Does Veeam Backup and Replication 6 (VBR6) Support your infrastructure?

VBR6 supports VMware ESX(i) 3.5, ESX(i) 4.x, ESXi 5.0 Hosts
VBR6 does not need to use a Virtual Center, but supports Virtual Center 2.5, vCenter Server 4.x, vCenter 5.0
VBR6 supports Windows Server Hyper-V 2008 R2 SP1, and Microsoft Hyper-V Server 2008 R2 SP1 Hosts
VBR6 does not need to use Microsoft System Center Virtual Machine Manager, but supports the 2008 R2 SP1 version

2: Physical or Virtual Veeam Backup Server?

Advantages of physical:

Veeam server's resources are separate from the Virtual Environment
Unconstrained by hypervisor limits for such things as Virtual SMP

Advantages of virtual:

Can backup/replicate the Veeam server with Veeam
Reduced hardware footprint in the datacenter

Comment:

Some of the advantages which existed in Veeam Backup and Replication 5 no longer apply in Veeam Backup and Replication 6 because of the Backup Proxy and Backup Repository functionality; these include but are not limited to:

Physical server able to backup using dedicated HBA (Host Bus Adapter) for say Fibre Channel (can now have a physical backup proxy with HBA)
Virtual server able to backup using virtual appliance mode (can now have a virtual backup proxy)


Really comes down to personal preference or available resources

3: Available Operating System for Veeam Backup & Replication Server Installation?

VBR6 installs on a wide variety of Microsoft Windows operating systems - XP SP3, Server 2003 SP2, Vista SP2, Server 2008 SP2, Server 2008 R2 SP1, 7 SP1
VBR6 does not install on any version of Windows Storage Server
VBR6 will install on a member server or workgroup server (highly recommended to install with a local administrator account which rules out installing on a DC)

Comment:

Personal preference here is to use the latest Windows Server version (currently 2008 R2 SP1)

4: Available Hardware Resources for Veeam Backup & Replication Server?

CPU: Minimum 2 cores, mores cores will improve data processing performance, and allows for more concurrent jobs
Memory: Minimum 2GB RAM (with remote SQL server,) Minimum 4GB RAM (using local SQL server.) Using faster memory (DDR3) improves data processing performance.
Disk Space: 300MB product installation. Minimum 1 GB per 500 VM for guest file system catalog folder. Minimum 10GB for Instant VM Recovery cache.
Network: 1 Gbps LAN for on-site backup, 1 Mbps or faster WAN for off-site backup and replication
Note: high latency links are supported but TCP/IP connection must not drop

Comment:

i: If installing Veeam Backup onto a physical backup server; in order to use the recommended 'Direct SAN access' Processing Mode – and when not using a Backup Proxy with direct access to the SAN – then the physical server will need a FibreChannel HBA to connect to a FibreChannel SAN or spare ethernet ports to connect to an iSCSI SAN.
ii: A suggestion to partition the VBR6 server is for: system disk partition, application disk partition, vPower NFS disk partition (could put on SSD for faster write cache performance of Instant Recovery VMs,) and backup data partition.

5: Available Software?

The binaries for Veeam Backup 6 need to be available (the download of Veeam Backup & Replication v6 includes Setup, Search_Setup, Enterprise_Manager_Setup)
Microsoft SQL Server 2005/2008 (SQL 2005 SP4 Express is included in the setup)
(Optional) SearchServerExpress (if intend to install Backup Search)
(Optional) Microsoft PowerShell 2.0 or later
(Optional) System Center Virtual Machine Manager 2008 R2 Admin UI (to be able to register SCVMM servers)

Comment:

Using Microsoft SQL Server 2008 R2 Express as opposed to the bundled SQL 2005 SP4 Express, allows for greater database size and enhanced database functionality.

6: Backup Target?

There needs to be enough available free disk space to hold the required number of roll-backs before optional archival to other media is performed. Backups targets can be:
- Direct Attached Storage (DAS) connected to the backup repository server (includes USB drives)
- Network Attached Storage (NAS) able to present itself as CIFS (SMB) share (direct operation), or NFS share (must be mounted on Linux backup repository server)
- Storage Area Network (SAN) – the backup repository server must be connected directly into SAN fabric via hardware HBA or software iSCSI initiator, and the corresponding volumes must be seen in the Microsoft Windows Disk Management snap in.

Comment:

Backup storage should typically be on Tier-2 or Tier-3 deduplicated storage, separate from Tier-1 storage used by critical production servers. Depending on compliance requirements, this backup storage will either need to be replicated to another site or archived off to removeable media. In the absense of a hot-DR solution, it is essential the backup is off the main production SAN so that in the event of a SAN failure the latest backups are still safe.

The following components are all optional, and add performance, useability, and management benefits:

7: (Optional) Additional Backup Proxy Server(s)
Note: The Veeam Backup and Replication Server is itself a Backup Proxy


OS: Windows – XP SP3, Server 2003 SP2, Vista SP2, Server 2008 SP2, Server 2008 R2 SP1, 7 SP1
Note: for Hyper-V Proxy, only Server 2008 R2 SP1 with Hyper-V role enabled is supported
CPU: Minimum 2 cores, mores cores will improve data processing performance, and allows for more concurrent jobs
Memory: 2 GB RAM. Using faster memory (DDR3) improves data processing performance.
Disk Space: 300MB
Network: 1 Gbps LAN for on-site backup, 1 Mbps or faster WAN for off-site backup and replication
Note: high latency links are supported but TCP/IP connection must not drop

8: (Optional) Additional Backup Respository Server(s)
Note: The Veeam Backup and Replication Server is in itself a Backup Repository


OS: Linux (with SSH and Perl) / Windows – XP SP3, Server 2003 SP2, Vista SP2, Server 2008 SP2, Server 2008 R2 SP1, 7 SP1
CPU: x86/x64 processor
Memory: 1 GB RAM
Network: 1 Gbps LAN for on-site backup, 1 Mbps or faster WAN for off-site backup and replication
Note: high latency links are supported but TCP/IP connection must not drop

9: (Optional) Veeam Backup & Replication Enterprise Manager

OS: Windows – XP SP3, Server 2003 SP2, Vista SP2, Server 2008 SP2, Server 2008 R2 SP1, 7 SP1
CPU: x86/x64 processor
Memory: 2 GB RAM
Disk Space: 100MB for product installation and sufficient disk space to store guest file system catalog from connected backup servers (according to data retention policy)
Network: 1 Mbps or faster connection to Veeam Backup & Replication servers

Server Software:
- IIS 5.1 or later ("IIS6.0 Metabase Compatibility", and "Windows Authentication" components are required for IIS 7.0)
- Microsoft SQL Server 2005/2008 (SQL 2005 SP4 Express included in the setup)
- Microsoft .NET Framework 2.0 SP1 (included in the setup)

Client Software:
- Internet Explorer 7 or later, and Mozilla Firefox 3 or later
- (to view Excel reports) Microsoft Excel 2003 or later

10: (Optional) Veeam Backup Search Server

Software: Microsoft Search Server 2008/2010 (including Express Edition)

Requirement for Microsoft Search Server 2010:
- OS: Windows Server 2008, Windows Server 2008 R2
- CPU: 64-bit, four core
- Memory: 4 GB for development, 8 GB for evaluation or single-server production use, 16GB for multiple-server production use
- Disk Space: 80 GB for system drive and the computer should have twice as much free disk space as it has RAM

Comment:

It is recommended to install Microsoft Search Server on a separate computer

Credit: Much of this information comes from Veeam's Veeam Backup & Replication 6.0 Release Notes

Saturday, 10 December 2011

Veeam Backup and Replication v6 Install Complete Walkthrough

*This is an update of the v5 Walkthrough from http://cosonok.blogspot.com/2011/10/veeam-backup-and-replication-v5-install.html and installing into Windows 2008 R2 with Veeam Backup and Replication 6.0.0 Enterprise with all components installed, and using the pre-packaged SQL Server 2005 Express

Pre-installation: step 1 (Diskpart)
CMD:\>
DISKPART
automount disable
*to check in future use automount command
exit

Pre-installation: step 2 (Specify a local user to be granted logon as service permissions)
Run secpol.msc (Local Security Policy) → Local Policies → User Rights Assignments → Find 'Log on as a service' policy and double-click → Add User or Group → Add the user account to be used to install Veeam Backup
*Note that a local administrator user account should be used to install Veeam Backup

Pre-installation: step 3 (required for Veeam Backup Enterprise Manager)
Server Manager → Roles → Add Roles → Check 'Web Server (IIS)' → Accept the default selections, check IIS 6 Management Compatibility and sub components, and check Windows Authentication component → Install

Installation
Download the following ZIP files from Veeam: veeam_backup_6, veeam_backup_ad_air_6, veeam_backup_ex_air_6, veeam_backup_sql_air_6, veeam_backup_un_air_6

Veeam Backup Server Installation
Login with the local administrator account to be used to install Veeam Backup → Open the Zip file containing Veeam Backup → Double-click the Veeam Backup Setup executable file → Click Run → Next → Accept terms → Next → Browse for License File → Next → Accept default feature selections for 'Veeam Backup and Replication' and 'Veeam Backup Catalog' (optionally can add in 'PowerShell Snap-in') → Change the default installation paths if desired → Next →
Specify SQL Server Instance (either new SQL 2005 Express or existing) → Next → Specify service account and password → Next → Customize/accept default file locations for 'Guest file system catalog' and 'vPower NFS' → Next → Ready to Install and check 'Create shortcut on desktop' → Install → Finish

Enterprise Manager setup step 1
Open the Zip file containing Veeam Backup → Double-click the Veeam Backup Enterprise Manager executable file → Click Run → Next → Accept license agreement → Next → Browse for License File → Next → Accept default feature selections for 'Enterprise Manager Server' and 'Enterprise Manager Web Site' → Next →
Specify SQL Server Instance → Next → Specify service account and password → Next → Accept Web Site Configuration defaults → Next → Ready to Install → Install → Finish

Enterprise Manager setup step 2
Logon to the Enterprise Manager https://servername:9443 → Configuration → Backup Servers → Add → In the Backup Server settings dialog enter the computer name or IP address of the backup server and provide user credentials → OK

Install Microsoft Search Server: step 1
Download Microsoft Search Server 2010 Express (suitable for small to medium environments) → Run the searchserverexpress executable → Install software prerequisites → Restart → Installation will continue when log in after restart → Finish → Run the searchserverexpress executable again →
Install Search Server Express → Accept the license → Standalone → Check 'Run the SharePoint Products Configuration Wizard now' → Close → SharePoint Products Configuration Wizard → Next → Finish

Install Microsoft Search Server: step 2
SharePoint 2010 Central Administration → Application Management → Service Applications: Manage service applications → Search Service Application → Click Default content access account and change to either your Veeam backup service account / or an account with Read access rights to the catalog share, and NTFS permissions to the folder backing the share

Backup Search Installation
Open the Zip file containing Veeam Backup → Double-click the Veeam Backup Search Setup executable file → Click Run → Next → Accept the license agreement → Next → Next → Provide Service Settings → Next → Install → Finish
Open the Enterprise Manager console → Logon → Configuration → Search Servers → Add → Provide DNS name / IP address of Search server, credentials → Choose Server type (Search Server and SQL Version) → OK

U-AIR Installations
1) Open the Zip file containing Veeam Backup AD AIR Setup → Double-click the executable file → Click Run → Next → Accept the license agreement → Next → Feature install: Active Directory Restore → Next → Accept connect parameter defaults → Next → Install → Finish
2) Open the Zip file containing Veeam Backup EX AIR Setup → Double-click the executable file → Click Run → Next → Accept the license agreement → Next → Feature install: Microsoft Exchange Restore → Next → Accept connect parameter defaults → Next → Install → Finish
3) Open the Zip file containing Veeam Backup SQL AIR Setup → Double-click the executable file → Click Run → Next → Accept the license agreement → Next → Feature install: Microsoft SQL Restore → Next → Accept connect parameter defaults → Next → Install → Finish
4) Open the Zip file containing Veeam Backup UN AIR Setup → Double-click the executable file → Click Run → Next → Accept the license agreement → Next → Feature install: Universal Restore → Next → Accept connect parameter defaults → Next → Install → Finish

Conclusion
The Veeam Backup and Replication v5 and v6 complete installs are pretty much identical procedures!

Thursday, 8 December 2011

Flow Control Best Practice for a VMware vSphere ESXi and iSCSI SAN Environment

Setup the storage network with each end point (ESXi hosts and iSCSI storage modules) with flow control send (tx) only, and the data switches in between with flow control receive (rx) only.

ESXi hosts have flow control enabled by default (or more accurately - the vmnics are set to autonegotiate.) If you want to check or change the flow control settings on an ESXi host, use the ethtool via the command line as below:

To check the flow control settings (pause parameters) for a vmnic:

ethtool -a VMNICName

To disable auto-negotiation of flow control:

ethtool --pause VMNICName autoneg off

To enable flow control for send only

ethtool --pause VMNICName tx on rx off

Finally, to the save the configuration change on the ESXi host

/sbin/auto-backup.sh

The example output below is from a vSphere 5 ESXi host

Example Output (text):

~ # ethtool -a vmnic6
Pause parameters for vmnic6:
Autonegotiate: on
RX: off
TX: off
~ # ethtool --pause vmnic6 autoneg off
~ # ethtool --pause vmnic6 tx on rx off
rx unmodified, ignoring
~ # ethtool -a vmnic6
Pause parameters for vmnic6:
Autonegotiate: off
RX: off
TX: on
~ # /sbin/auto-backup.sh
Binary files /etc/vmware/dvsdata.db and /tmp/auto-backup.3629787//etc/vmware/dvsdata.db differ
Saving current state in /bootbank
Clock updated.
Time: 13:24:48 Date: 12/08/2011 UTC
~ #

Example Output (screenshot):
Note that the vmnic must be patched into a live switch port before it will display any of the pause parameters as being on.

Credits:

Wednesday, 7 December 2011

NetApp Simulator 8.1 7-Mode Walkthrough Setup Guide

UPDATE: Also see NetApp Simulator 8.1.2 Cluster Mode Installation Walkthrough

This walkthrough guide is specifically using the current latest version of the NetApp Simulator ONTAP – version 8.1, and running the lab inside VMware Workstation 8 (*see Appendix B for Simulate ONTAP 8.1 Hardware and Software Requirements.) The NetApp Simulator is an excellent tool to learn about NetApp filers in a virtual lab environment.

Step 1: Download or Obtain the Binaries

Go to http://now.netapp.com/NOW/cgi-bin/simulator and login with your NetApp NOW account.

Select the Simulator 8.x link, and choose the links to download the Simulate ONTAP 8.1 7-mode and C-mode simulators for VMware Workstation or ESX as required (*see Appendix C for Differences Between ONTAP 7-Mode and C-Mode,) and the 8.1 licenses
Extract the downloaded zip files – vsim-7m.zip and vsim-cm1.zip – to their respective folders.

Note: Whilst we are downloading software, go to https://now.netapp.com/NOW/cgi-bin/software/ and download the OnCommand System Manager (latest version at 7th December 2012 is 2.0R1 which supports ONTAP 7.3.2 and above.) The OnCommand System Manager provides a GUI to manage NetApp Filers. The file name for the Windows version is sysmgr-setup-2-0R1-win.exe .

Step 2: Import the Simulator Into VMware Workstation

In this post we are just going to focus the ONTAP 8.1 7-mode simulator (the procedure for the C-mode simulator is pretty similar)
Create a copy of the vsim-7m folder and within VMware Workstation -> File Menu -> Open
- and point to the DataONTAP.vmx file and select Open
- rename the imported machine as desired and power on

Step 3: Booting the Simulator and Initial Configuration
On first boot, wait for the simulator to reach "Press Ctrl-C for Boot Menu" and press Ctrl-C
- this brings up the boot menu, and choose option 4 for 'Clean configuration and initialize all disks'
- Selection (1-8)? 4
- Zero disks, reset config and install a new file system?: Yes
- This will erase all the data on the disks, are you sure?: Yes

The virtual filer will reboot, re-initialize and run through the wipe procedure
- Please enter the new hostname []: VFILER01
- Do you want to enable IPv6? [n]:
- Do you want to configure interface groups? [n]:
- Please enter the IP address for Network Interface e0a []: 192.168.0.111
- Please enter the netmask for Network Interface e0a [255.255.255.0]:
- Please enter media type for e0a {100tx-fd, tp-fd, 100tx, tp, auto (10/100/1000)} [auto]:
- Please enter flow control for e0a {none, receive, send, full} [full]:
- Do you want e0a to support jumbo frames? [n]:
- Please enter the IP address for Network Interface e0b []:
- Please enter the IP address for Network Interface e0b []:
- Please enter the IP address for Network Interface e0b []:
Note: Here I leave configuring the 3 interfaces e0b, e0c, e0d for later
- Would you like to continue setup through the web interface? [n]:
Note: Default answer is no to the above question, and my preference is to continue via the console (also the Filer's interfaces do not come up until after the setup is completed!) For reference, the link given is https://IPADDRESSofFILER/api
- Please enter the name or IP address of the Ipv4 default gateway: 192.168.0.2
Screen Ouput: The administration host is given root access to the filer's /etc files for system administration. To allow /etc root access to all NFS clients enter RETURN below.
- Please enter the name or IP address of the administration host: 192.168.0.11
- Please enter timezone [GMT]:
- Where is the filer located? []:
- Enter the root directory for HTTP files [/home/http]:
- Do you want to run DNS resolver? [n]:
- Do you want to run NIS client? [n]:
Screen Output: This system will send event messages and weekly reports to NetApp Technical Support. To disable this feature, enter "options autosupport.support.enable off" within 24 hours. Enabling AutoSupport can significantly speed problem determination and resolution should a problem occur on your system. For further information on AutoSupport, please see: http://now.netapp.com/autosupport/
- Do you want to configure the Shelf Alternate Control Path Management interface for SAS shelves [n]:
- Setting the administration (root) password for VFILER01 ... New password: XXXXXXXX
- Retype new password: XXXXXXXX

Then wait for the network interface to become pingable and the system to complete its initialization.

*Continuing from here, see these later tutorials (time permitting - this list will grow):
NetApp Basic NFS Configuration Walkthrough with VMware
NetApp Basic iSCSI Configuration
Installing the NetApp Virtual Storage Console (VSC) for VMware vSphere and Using it to Optimize NFS Settings
NetApp Data ONTAP 8.1 Enabling SFTP Access to /etc

Step 4: Managing Your NetApp Virtual Filer

After the NetApp virtual Filer has initialized, it can be managed using the root credentials via:

1: Direct Console (*see Appendix D: CLI commands)
2: SSH connection (*see Appendix D: CLI commands)
3: NetApp OnCommand System Manager (installable on Linux and Windows platforms)
Feel free to play around with the simulator to your heart's content!

Appendix A: Useful links and Credits

http://now.netapp.com/NOW/knowledge/docs/docs.cgi – NetApp product documentation

Appendix B: Simulate ONTAP 8.1 Hardware and Software Requirements

Hardware requirements
Dual core 64-bit Intel or AMD system
2 GB RAM for one instance of simulator
3 GB RAM for two instances of simulator (4 GB recommended)
20 GB free disk space for each instance of the simulator
VT support for Intel system
Software requirements
Microsoft Windows XP, Windows 7, or Windows Vista
VMware Workstation, VMware Player, or VMware vSphere Client (if running on a VMware ESX/ESXi host server)

Appendix C: Difference Between ONTAP 7-Mode and C-Mode


FAS arrays run Data Ontap, which is available in two modes:

Data Ontap 7-mode (or classic mode) allows FAS arrays to be deployed as a local two-node cluster, a geographically spanned MetroCluster, and as a remote distributed FlexCache, which enables capabilities like LDVM for VMware.

Data Ontap C-Mode (or cluster mode) expands a NetApp storage cluster from 2 nodes to 24 nodes, increases the features found in 7-mode to include endless scaling, global name spaces, and the complete separation of data and data access from the hardware layer in the form of next generation vFilers (known as vServers).

Appendix D: CLI Commands

VFILER01> ?
acpadmin / aggr / arp / autosupport / backup / bmc / cdpd / cf / charmap / cifs / clone / config / date / dcb / df / disk / disk_fw_update / dns / download / du / dump / echo / ems / environment / exportfs / fcadmin / fcnic / fcp / fcstat / file / flexcache / fpolicy / fsecurity / ftp / halt / help / hostname / httpstat / ic / ifconfig / ifgrp / ifstat / igroup / ipsec / ipspace / iscsi / key_manager / keymgr / license / lock / logger / logout / lun / man / maxfiles / mt / nbtstat / ndmpcopy / ndmpd / ndp / netdiag / netstat / nfs / nfsstat / nis / options / orouted / partner / passwd / ping / ping6 / pktt / portset / priority / priv / qtree / quota / radius / rdate / rdfile / reallocate / reboot / restore / revert_to / rlm / route / routed / rshstat / sasadmin / sasstat / savecore / sectrace / secureadmin / setup / sftp / shelfchk / sis / smtape / snap / snaplock / snapmirror / snapvault / snmp / software / source / sp / stats / storage / sysconfig / sysstat / system / timezone / traceroute / traceroute6 / ups / uptime / useradmin / version / vfiler / vlan / vmservices / vol / vscan / wcc / wrfile / ypcat / ypgroup / ypmatch / ypwhich


SEO: NetApp Simulator 8.1 Step by Step Install Guide

Saturday, 3 December 2011

Installing APC UPS PowerChute Network Shutdown Software on VMware vSphere Management Assistant for use with VMware ESXi Hosts Walkthrough Guide

The examples in this walkthrough use the current latest versions (01 Dec 2011) of PowerChute Network Shutdown v3.0.0 and vMA 5.0.0.0

Part 1: Download PowerChute Software

Select a Product Name = PowerChute Network Shutdown
Filter by Operating System = VMware ESXi
Download PowerChute Network Shutdown


The downloaded file will be named something like pcns300ESXi.tar.gz
*Note: Requires a login account for www.apc.com

Part 2: Download and deploy VMware vSphere Management Assistant (vMA)

*Note: If already have a vMA, please ignore this part
Select VMware vSphere → Select Drivers & Tools → Download VMware vSphere Management Assistant (vMA)
*Note: vMA version 5 will work fine in a vSphere 4.X environment


The downloaded file will be named something like vMA-5.0.0.0-472630.zip
Extract the files from the zip file


Deploy the vMA via a vSphere Client → File menu → Deploy OVF Template... and follow the prompts to complete, deploying from the .ovf file extracted previously.


Power on the vMA on a suitable virtual network, follow the prompts to apply a network configuration, provide a password for the vi-admin user, and this part is done!

Example configuration:


*Note: vMA 5 uses virtual hardware version 4, so will run on old ESX 3.X hosts.
*Note: the vMA can be managed via https://IP_of_vMA:5480

Part 3: Uploading and installing PowerChute Network Shutdown into vMA

Use a tool lke WinSCP to copy the PowerChute Network Shutdown software (pcns300ESXi.tar.gz) to the tmp directory on the vMA


Using the vMA command line via the console or a remote SSH session, and logged in as vi-admin, run the following commands in turn:

sudo chmod 777 /etc/rc.d
sudo mkdir /etc/rc.d/init.d
cd /tmp
sudo gunzip pcns300ESXi.tar.gz
sudo tar -xvf pcns3000ESXi.tar
cd ESXi
sudo ./install_en.sh

Press any key to display and scroll through the End User License Agreement
Type yes to the question 'Do you agree to the above license terms? [yes or no]'
Press enter to accept the default installation directory (/opc/APC/PowerChute)
Type yes to the question 'Are you sure you want to install PCNS to /opt/APC/PowerChute [Yes|No]?'
Type /usr/java/jre-vmware/bin to the question 'Please enter java directory if you want to use your system java or press enter to install the bundled Java:'
*Note: vMA 5.0.0.0 comes with Java pre-installed and this is suitable for PCNS
Type q to skip entering an ESXi host IP for now
Installation complete!

*Note: See Output in Appendix below

Part 4: Adding the ESXi Hosts

From the vMA command line, use the following command to add ESXi Hosts

vifp addserver IPADDRESSofESXiHOST

Part 5: Configuration via the PCNS Web UI

Connect to: https://vMA_IP_Address:6547 to access the Configuration Wizard, and follow through the Wizard to complete the configuration of PCNS.


Configuration Wizard: Welcome
Click Next

Configuration Wizard: Security
Enter User Name (This must be the username used to log on to the Network Management Card (NMC) Web UI. It is used both to communicate with the NMC, and log into PCNS)
Enter Password (This password will be used to log into PCNS)
Enter Authentication Phrase (This must match the PowerChute authentication phrase configured on the NMC)
Click Next

Configuration Wizard: UPS Electrical Configuration
Select how the UPS's are configured
Options are:
Using power from a single UPS
Redundant: Two or more UPS providing redundancy, with multiple power cables from the computer
Parallel: Two or more UPS combined in parallel as a single power supply
Click Next

Configuration Wizard: UPS Details
Enter NMC Protocol
Enter NMC Port
Enter NMC IP address(es)
Click Next

Configuration Wizard: Miscellaneous
Choose whether PCNS will automatically check for updates
Choose whether the UPS should turn off after shutdown finishes
Click Next

Configuration Wizard: Confirm
Click Apply

Appendix: vMA Command Line Output

login as: vi-admin
Welcome to vSphere Management Assistant
vi-admin@10.122.130.130's password:
vi-admin@localhost:~> sudo chmod 777 /etc/rc.d

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.

vi-admin's password:
vi-admin@localhost:~> sudo mkdir /etc/rc.d/init.d
vi-admin@localhost:~> cd /tmp
vi-admin@localhost:/tmp> sudo gunzip pcns300ESXi.tar.gz
vi-admin@localhost:/tmp> sudo tar -xvf pcns300ESXi.tar
ESXi/
ESXi/Installation.pdf
ESXi/install_en.sh
ESXi/jre1.6.0_24_linux64.tar.gz
ESXi/pcns300.tar.gz
ESXi/relnotes.htm
ESXi/silentInstall.sample
vi-admin@localhost:/tmp> cd ESXi
vi-admin@localhost:/tmp/ESXi> sudo ./install_en.sh

...

Do you agree to the above license terms? [yes or no]
yes

Please enter the installation directory or press enter to install to the default directory (/opt/APC/PowerChute):

Are you sure you want to install PCNS to /opt/APC/PowerChute [Yes|No]?
yes
Creating /opt/APC directory ...
PCNS will be installed to /opt/APC/PowerChute

Please enter java directory if you want to use your system java (example:/usr/local/bin/jre/jre1.6.0_24) or press enter to install the bundled Java:
/usr/java/jre-vmware/bin
Checking version of Java ...
Detected Java Version: 1.6.0.20
Acceptable version

java version "1.6.0_20"
Java(TM) Platform, Standard Edition for Business (build 1.6.0_20-b02)
Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)

JAVA_DIR=/usr/java/jre-vmware/bin/

Copying the installation files ...
Extracting PCNS files ...
PCNS is extracted to /opt/APC/PowerChute
Configuring startup files ...
Startup script=/etc/rc.d/init.d/PowerChute
Updating Linux symbolic link ...
PowerChute: unknown service
PowerChute: unknown service

In order for PCNS to shutdown the ESXi host, it must be added as a target server.
Please enter ESXi host IP (XXX.XXX.XXX.XXX) or (q) to skip:
q

Skipping configuration of ESXi Host Shutdown.
Configuring uninstall script ...
Setup the m11.cfg file

PowerChute Network Shutdown, v3.0.0
Copyright (c) 1999-2011, Schneider Electric. All Rights Reserved.
Startup completed.

Installation has completed.
PowerChute Network Shutdown can be accessed through your browser at https://:6547
Please complete the configuration wizard so that PowerChute Network Shutdown can protect your server.

vi-admin@localhost:/tmp/ESXi> vifp addserver 10.122.130.51
root@10.122.130.51's password:
vi-admin@localhost:/tmp/ESXi>