Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out

Windows 2003-2008 R2 Fibre Channel HBA Migration Guide

VIEWS: 687 PAGES: 56

									Step-by-step Guide


Windows 2003-2008 R2
S
Fibre Channel HBA
Migration Guide
EMULL




                       Moving to Emulex 8Gb/s
                       HBAs from QLogic 4Gb/s
                       HBAs
Table of contents
Abstract ............................................................................................................................................................3
Introduction ......................................................................................................................................................3
Audience ..........................................................................................................................................................3
Why upgrade to 8Gb/s Fibre Channel ..............................................................................................................3
 New workloads require higher bandwidth ....................................................................................................4
 Reduced Inter-Switch Link (ISL) ports..........................................................................................................4
 All at comparable prices ...............................................................................................................................4
Why migrate to Emulex LightPulse HBAs? ......................................................................................................4
    Reduced management effort .......................................................................................................................5
    Single driver for Fibre Channel HBA and Fibre Channel over Ethernet (FCoE) Converged Network
    Adapter (CNA)..............................................................................................................................................5
    Optional encryption support .........................................................................................................................6
Migration Overview ..........................................................................................................................................7
  Choosing the right HBA................................................................................................................................7
  Intro to Emulex management suite...............................................................................................................8
    Planning the Migration .................................................................................................................................9
    Collect current configuration settings ...........................................................................................................9
The migration process step by step ..............................................................................................................13
  Collecting configuration settings.................................................................................................................13
  Virtual HBA settings (NPIV, including WWNs) ...........................................................................................17
  Installing the Emulex HBA ..........................................................................................................................19
  Removing the QLogic HBA ........................................................................................................................29
  Configuring the HBA ..................................................................................................................................32
    Addressing common problems...................................................................................................................40
    Post migration - Common management tasks ...........................................................................................47
Appendix A – HBA Settings Worksheet .........................................................................................................51
Appendix B –Emulex/QLogic parameter mapping reference..........................................................................54




2       Emulex Step-by-Step Guide | QLogic Migration Guide
Abstract
This guide presents the case for migrating from 2 or 4Gb/s Fibre Channel Storage Area
Networks (SANs) using QLogic Host Bus Adapters (HBAs) to 8Gb/s Fibre Channel using
Emulex HBAs. It then presents the process and best practices for migrating to the Emulex HBAs
on Windows servers.


Introduction
The storage networking industry is in the midst of the transition from the 4Gb/s Fibre Channel
network infrastructure that has been state-of-the-art since 2005 to 8Gb/s technology. The
Dell’Oro Group predicts that 8Gb/s HBAs will make up the majority of Fibre Channel HBA sales
in 2011. As with all superseded technology, it is expected that 4Gb/s Fibre Channel HBAs will
eventually become obsolescent as 8Gb/s Fibre Channel becomes the predominate technology.
User organizations upgrading their Fibre Channel infrastructure from 4 to 8Gb/s have an
excellent opportunity to reassess their HBA vendors, selecting an adapter that better aligns with
their IT initiatives and business objectives, such as better performance for virtualization, better
and more integrated management tools and reduced operating costs. Emulex LightPulse HBAs
have some significant advantages over competitive HBAs from QLogic and others.
This guide is designed to help IT managers and their systems or storage administrators plan
and execute their migration from QLogic 4Gb/s, or even 2Gb/s Fibre Channel, HBAs to Emulex
LightPulse 8Gb/s Fibre Channel HBAs. It will:
• Discuss the advantages of upgrading to 8Gb/s Fibre Channel
• Explore the unique features and other advantages of Emulex LightPulse HBAs
• Describe the process of planning the migration, including selecting the right Emulex HBA(s)
  for your environment
• Walk the reader step-by-step through the process of replacing QLogic HBAs with Emulex
  LightPulse HBAs

Audience
This guide is intended to help system and storage administrators using Fibre Channel SANs. IT
managers will also find the product selection and migration planning sections helpful.

Why upgrade to 8Gb/s Fibre Channel?
New workloads require higher bandwidth
Today’s servers running multi-core Xeon Nehalem and Westmere or Opteron Magny-cour have
many times the compute power and memory capacity of the servers of just a few years ago.
The most popular dual-socket servers like HP’s DL380G7 and Dell’s R710 have 12 multi-
gigahertz processor cores and can support up to 192Gb of memory.



3   Emulex Step-by-Step Guide | QLogic Migration Guide
This combination of compute power and massive memory allows a single physical server to
host 20 or more virtual servers. Organizations are now extending their server virtualization
initiatives from the test and development servers they virtualized in the first wave to include
production servers. A single physical server running multiple disk I/O-intensive production
applications like messaging and database servers can easily generate more disk I/O than a
single 4Gb/s Fibre Channel can satisfy.

Reduced Inter-Switch Link (ISL) ports
In addition to increasing the amount of data servers can transfer to and from the SAN, the
higher data rate of 8Gb/s Fibre Channel also increases the capacity of inter-switch links in the
network. Organizations that have upgraded their switching infrastructure to 8Gb/s Fibre Channel
can frequently reduce the number of parallel connections they maintain between switches,
freeing valuable switch ports for server and storage connections.

All at comparable prices
Even though Emulex LightPulse 8Gb/s Fibre Channel HBAs provide twice the bandwidth of
4Gb/s HBAs, they cost only 10% to 15% more than the older 4Gb/s models.
Since Emulex LightPulse 8Gb/s HBAs can automatically detect the speed of the switch port to
which they are connected from 2Gb/s to 8Gb/s, organizations can start their migration to an
8Gb/s SAN by upgrading HBAs first and upgrading their switches later. Performance
advantages can still be realized when using 8Gb/s HBAs with 4Gb/s infrastructure.

Why migrate to Emulex LightPulse HBAs?
Once you’ve decided to upgrade to 8Gb/s Fibre Channel HBAs, your next decision will be to
choose an HBA vendor. Emulex has been a leader in the Fibre Channel HBA business since
the beginning with over 10 million HBA ports shipped and running reliably in the field. Emulex
HBAs are chosen by customers for:
• Superior Performance - Customers rank Emulex #1 in 8Gb/s HBA performance1
    o Powers the #1 fastest database system 2
    o 37% better dual-port scalability3
    o Highest virtual machine (VM) consolidation – 4x the virtual ports (vPorts)

• Industry-leading Management - Delivers higher availability and reduces costs
    o Twice the management capabilities and spend half the time managing adapters in physical
      and virtualized environments
    o Native VMware management integration for streamlined management with vCenter plug-in

• Unsurpassed Reliability - Customers rank Emulex #1 in Reliability 4

1
  IT BrandPulse Report- 2009
2
  In latest TPC-C reports - advanced CPU utilization for better application and system performance
3
  Highest data throughput on both channels for optimum server performance and power and cooling efficiency

4     Emulex Step-by-Step Guide | QLogic Migration Guide
     o Emulex HBAs run 20°C cooler than their QLogic counterparts
     o Industry-leading, field-proven reliability with 10 million mean time between failures (MTBF)

Emulex HBAs have a 10-million-hour MTBF in the field. One factor contributing to that high
reliability is that Emulex HBAs run 20°C cooler than their QLogic counterparts while running at
lower CPU.
In addition to Emulex-branded products, Emulex HBAs are sold by all of the major storage
OEMs, including Dell, HP, IBM, EMC, Oracle and NetApp.

Reduced management effort
Most HBA vendors have both graphical and command-line management tools to enable system
administrators to perform day-to-day functions like connecting to a storage target and mapping
a logical volume or LUN to a server. While these tools may at first glance seem similar, they can
vary significantly in ease of use.

Simple installs
Emulex’s OneCommand Manager is simpler to install and requires fewer mouse clicks to
perform many common tasks than QLogic’s SANsurfer. For more information on the time
OneCommand can save over SANsurfer, see the OneCommand Manager Report Card at:
http://www.emulex.com/artifacts/ad19cc4e-870a-42e9-a4b2-
bcaa70e2afd6/elx_rc_all_onecommand_efficiency_QLogic.pdf.

No re-boots
While upgrading the firmware on other HBAs may require a system reboot, Emulex HBA
firmware can be updated with the system running. Similarly Emulex’s OneCommand Manager
allows for online configuration of WWNs and boot-from-SAN configurations.

Single driver for Fibre Channel HBA and Fibre Channel over Ethernet (FCoE)
Converged Network Adapter (CNA)
Emulex’s common driver model uses the same driver for all generations of Emulex HBAs. This
means that while users of other vendors’ HBAs may have to install new drivers when upgrading
from a 2 or 4Gb/s HBA to an 8Gb/s HBA, which might in turn require a server reboot, Emulex
users can simply swap out the old hardware and continue to use the same driver.
Since all of the servers in a data center running Emulex HBAs can use the same driver system,
administrators can schedule driver updates without having to track updated driver releases for
different models or track which servers need which driver upgrade. A single driver also means
that the Emulex driver can be installed before the HBA hardware, which allows system
administrators to include the driver in server OS “Golden Images” before those images are
deployed to server hardware.




4
    IT BrandPulse Report- 2009

5       Emulex Step-by-Step Guide | QLogic Migration Guide
A common driver also means users have common management tools, including the
OneCommand Manager graphical HBA manager and HBAnyware CLI that can manage Emulex
HBAs of several generations, and across PCI-X, PCIe and blade architectures.


Migration Overview
Choosing the right HBA
Emulex replacements for QLogic 4Gb/s models
The table below shows the Emulex LightPulse® Fibre Channel HBAs that are the logical
upgrade for QLogic’s 4Gb/s models.
Table 1: QLogic HBAs and Emulex recommended upgrades

QLogic 4Gb/s HBA            Emulex 8Gb/s Upgrade                   Description

QLE2460                     LPe12000                               Single-port, PCIe x4 HBA
QLE2462                     LPe12002                               Dual-port, PCIe x4 HBA
QLE2464                     LPe12004                               Quad-port, PCIe x8 HBA



Emulex LightPulse HBAs are also available as OEM products from the major storage vendors;
for OEM part numbers see: http://www.emulex.com/products/fibre-channel-hbas.html.

Emulex LightPulse HBAs without QLogic direct equivalents
In addition to the enterprise-oriented single-, dual- and quad-port HBAs listed above, Emulex
also makes the LPe1250 single-channel value HBA. The LPe1250 omits some enterprise
features of the LPe12000 such as end-to-end integrity checking and Solaris support, allowing
organizations that don’t need those features, including most Windows shops, to save about
$200 per HBA.

Table 2: Emulex LightPulse HBAs without QLogic direct equivalent

QLogic 4Gb/s HBA            Emulex 8Gb/s Upgrade               Description

No equivalent               LPe12002-X8                        Dual-port, PCIe x4 HBA- with Long-wave optics


Intro to Emulex management suite
Even a fast and feature rich Fibre Channel HBA like an Emulex LightPulse needs management
software so system administrators can connect to storage, configure boot-from- SAN, manage
vPorts via N_Port ID Virtualization (NPIV) and the like. Emulex provides a group of tools that
allow system administrators to complete these tasks in the way that fits their environment and
work process best.




6    Emulex Step-by-Step Guide | QLogic Migration Guide
Emulex OneCommand™ Manager
The core application in the Emulex management suite is OneCommand Manager. This
graphical application for Windows Solaris and Linux environments allows system administrators
that perform HBA management tasks on an occasional basis, or are just more comfortable in a
GUI, with the ability to perform all their management tasks from a simple application. In addition
to managing LightPulse HBAs, OneCommand also manages Emulex OneConnect Universal
CNAs (UCNAs), including managing the Ethernet, iSCSI, DCB and FCoE functions of these
cards.
The OneCommand GUI can be used to manage Emulex adapters in the local system or
remotely, and, unlike many other GUIs, can even perform batch updates to groups of adapters
across the network, including VMware ESX and ESXi servers. Emulex has also released a
vCenter plug-in version of OneCommand, allowing virtual server administrators to manage their
host’s storage adapters from their familiar vCenter console.
For administrators that would rather use scripts to manage their storage adapters, Emulex’s
OneCommand CLI, also known as the HBAnyware CLI, provides a powerful command line
interface to managing Emulex adapters.
The boot-from-SAN function and BIOS interface of Emulex HBAs can be managed from the
server console during the server boot process in addition to management via OneCommand or
the CLI. This can be helpful for the initial setup of servers that boot cloned system disk images
from SAN disk.
How Emulex tools replace SANsurfer and other QLogic tools
For those readers familiar with the QLogic management suite, the table below shows how the
Emulex management suite replaces the QLogic tool set.

Table 3: Emulex and QLogic Management Tools

Function                               QLogic Tool                 Emulex Tool

Graphical HBA manager                  SANsurfer HBA Manager       OneCommand Manager
Command Line Utility                   SANsurfer CLI               HBAnyware CLI
HBA driver and software installer      SANsurfer install wizard    AutoPilot Installer
BIOS configuration utility (accessed   FAST!util                   Emulex BIOS Utility
during server bootup)



Planning the Migration
Now that you’ve decided to use Emulex LightPulse HBAs to migrate your servers to 8Gb/ s
Fibre Channel, you should spend a little time planning the migration process to avoid
uncomfortable surprises and the resulting delays once you start the actual migration. Let’s
review the steps you should include in your planning.




7    Emulex Step-by-Step Guide | QLogic Migration Guide
Collect current configuration settings
One key to any successful migration is fully understanding the starting point. Before you start
installing your shiny new HBAs, you should make sure you understand how your servers and
their current QLogic HBAs are configured. Before diving right in and poking around in QLogic
management suite for details, take a minute to review how the server’s storage configuration
should be set up. Answer questions like:
    •   What SAN LUNs does this server use?
    •   What data paths should the SAN support between the server and its disk volumes?
    •   Should the server boot from SAN?
We’ll go through the process of collecting the detailed information from QLogic’s management
tools in the next section as part of the step-by-step migration, so you can transfer the
configuration forward to your new 8Gb/s SAN, but you should also think about the configuration
changes you want to make as you migrate.

Boot from SAN
Fibre Channel HBAs can mount SAN logical volumes as part of the server BIOS load process,
allowing servers to boot from SAN disks rather than local drives. Booting from SAN can
increase data center flexibility by allowing servers to boot from different logical drives and speed
recovery by allowing a new server to mount the boot LUN from a failed volume.
QLogic HBAs manage boot from SAN through the Fast!Util program that’s accessed by
pressing Ctrl-Q at the appropriate time during system boot. If you’re using boot from SAN, make
sure you have KVM or other access to the system console through the boot process.

Managing WWNs
Fibre Channel World Wide Names (WWNs) are used by the Fibre Channel network to identify
devices, similar to Ethernet MAC addresses. While much of the process for assigning and using
WWNs is handled automatically behind the scenes by the Fibre Channel Switching
infrastructure, SAN administrators also use WWNs to limit access to storage systems and their
logical volumes (LUNs) to the servers that should be accessing those devices.
The first method of WWN-based access control is soft zoning. Soft zoning assigns Fibre
Channel connections to zones by their WWN. With soft zoning, only those servers with HBAs
having WWNs assigned to a zone will be able to access the resources in that zone. Zoning is
enforced by the Fibre Channel switching infrastructure.
The other, and frankly, more common, use of WWNs for access control is LUN masking. A
storage array will typically present many logical volumes, or LUNs, to the SAN while individual
servers manage the data within those LUNs. By defining which server “owns” each LUN and
limiting access to the LUN to that server, LUN masking prevents a server from writing to another
server’s LUNs.



8   Emulex Step-by-Step Guide | QLogic Migration Guide
When you replace a QLogic 4Gb/s HBA with an Emulex LightPulse 8Gb/s HBA, you will have
chosen how you want to manage your WWNs. One approach is to use the default WWNs for
the new HBA and change the zoning and LUN masking policies on your SAN switches and/or
array. The other is to assign the WWN from the old HBA to the new one. Each has advantages
and disadvantages.

Using the default WWN
This approach will typically require using at least three different management tools, one each for
the HBA, switch and disk array.
Through the management interface of your Fibre Channel switches, you’ll need to ensure that
the Fibre Channel fabric zoning in your switching infrastructure will place the new HBA ports in
an appropriate zone to access the server’s LUNs. If you’re using port-based hard zoning, you’ll
simply need to verify that fact. If you’re using WWN-based soft zoning, you’ll need to add the
default WWNs to the zone(s) to which the old HBA’s WWNs belonged and should remove the
old HBA’s WWNs from that zone, so if that HBA is reused, the server it’s connected to won’t
have inappropriate access to SAN LUNs.
On the disk array, you’ll need to register the HBA WWNs to a host and to the LUN masks for the
LUNs this server accesses. As with switch zoning, you should plan to remove the WWNs from
the old HBA from the access lists for the servers LUNs once the old HBA is removed from the
server.

Changing the HBA WWN
The second option is to change the WWNs used by the Emulex HBA to those that were used by
the old QLogic HBA. By changing the WWNs and connecting the new HBA to the same switch
ports the old HBA was connected to, you avoid having to change the configurations of either the
Fibre Channel switches or storage array.
The problem is, if the old HBA is ever connected to the SAN, you’ll have two systems both trying
to use the same WWNs, which could wreak havoc on your SAN. If you decide to transfer
WWNs, you should also take appropriate steps to ensure the old HBA isn’t reused without
resetting its WWNs to some new value.

Cables
Many data centers were cabled with 62.5 micron multimode cable, originally used for 100Mb/s
LAN applications, including FDDI. As the transmission rates of data center networks, including
Fibre Channel, have increased several hundred-fold from 100Mb/s to 8 and 10Gb/s, the limited
ability of 62.5 micron cable to carry higher frequency data has lead to the development of newer
multimode cables.
Just as copper twisted pair cable has evolved from the Category 3 cable designed to support
10Base-T Ethernet to Category 7 for 10 gigabit transmissions, Fibre Optic cables have also
evolved. One driver for this evolution has been the development of low-cost semiconductor
lasers to replace the LEDs used for FDDI and Fast Ethernet. New Laser Optimized MultiMode



9   Emulex Step-by-Step Guide | QLogic Migration Guide
Fibre (LOMMF)-designated OM3 and OM4 use 50 micron cores and can support high-speed
networks.

Table 4: Fibre Optic Cable Types

Cable Type                  Core/Cladding           Typical Jacket Color   Maximum Distance for
                            Diameter                                       8Gb/s Fibre Channel
OM1                         62.5/125µM              Orange                 21M (68.9 feet)
OM2                         50/125µM                Orange                 50M (164 feet)
OM3                         50/125µM                Aqua                   150M (492 feet)
OM4                         50/125µM                Aqua                   190M (623 feet)



Clearly, those looking to the future should use OM4 cable in new work. It not only supports
longer cable lengths with current technologies, but will support emerging technologies, including
16Gb/s Fibre Channel, 40 and 100Gb/s Ethernet with cable lengths of 100 meters or more.
Those organizations with OM1 infrastructure in their data centers and cable runs over 21 meters
may have to invest in new cables to take full advantage of 8Gb/s Fibre Channel.

Allocating time and scheduling downtime
While the PCI Express specification supports hot plugging of cards into PCIe slots, making it
theoretically possible to install an Emulex LightPulse HBA into a running server, most system
administrators will choose to schedule downtime and perform the migration with the server
offline.
A typical migration should take between 15 and 60 minutes. Systems with complex zoning, LUN
Masking and system configurations will, of course, take longer than systems with simple
configurations.

Downloading the Emulex software
It’s always a good idea to use the latest versions of the Emulex drivers and management
software. You can download the driver and enterprise application kit, which includes all of the
components you’ll need to follow the procedures in this guide, from the following link:
http://www.emulex.com/downloads/emulex/firmware-and-boot-code/lpe12002-firmware-and-
bootcode/drivers.html


The migration process step by step
Once you’ve completed the planning process, it’s time to start the actual migration. In this
section, we’ll walk through the process from collecting the current state of your system and HBA
configuration through replacing your old 4Gb/s QLogic HBA with a shiny new Emulex LightPulse
8Gb/s HBA to finally reconnecting the server to its SAN disks.



10    Emulex Step-by-Step Guide | QLogic Migration Guide
Collecting configuration settings
Step one in the migration process is to make sure you know the current configuration so you
can reestablish the server to LUN connections with your new HBA and so you can revert to the
existing configuration should something unexpected cause you to abandon your migration
plans.
The HBA Configuration Worksheet at the end of this guide can help you collect all the
information you’ll need and organize it so you can migrate to your new configuration smoothly.
To start, enter the server’s name and IP address and then the SAN switch ports the HBA is
connected to. Since you’re going to disconnect the SAN cables to swap HBAs, it would be a
good idea to label the cables as you disconnect them so you can reconnect port 1 of the new
HBA to the same switch port.

Using SANsurfer to collect WWNs, mappings, etc.
Once you’ve recorded the basic information about the server, you can fire up QLogic’s
SANsurfer graphical HBA management application to collect more specific information. To start
SANsurfer, select SANsurfer from the QLogic Management Suite submenu of the Windows start
menu.
When SANsurfer starts, click the connect button and enter the name or IP address of the server
whose HBA you’re going to upgrade. Depending on how your SANsurfer is configured, you may
need to log into the application. Note that the default SANsurfer password is config
You can then select each HBA port to see the screenshot below. There, you’ll see the Port and
Node WWNs for this port.




Figure2: SANsurfer Port Information Screen




11    Emulex Step-by-Step Guide | QLogic Migration Guide
Select the Target Persistent Binding tab to identify which of the mapped LUNs on this port are
persistently bound and will be reconnected automatically on server reboot.




Figure 3: SANsurfer Target Persistent Binding Screen

Double-click on an HBA port to see a list of the targets that are connected to that port. Double-
click on a target and you can see the detailed information for that disk that you’ll need to
connect to later.




Figure 5: SANsurfer Target Information




12    Emulex Step-by-Step Guide | QLogic Migration Guide
If you know you haven’t changed any of the detailed Fibre Channel parameters such as
connection speed, you can move on to replacing your HBA. If your system uses customized
parameters, you’ll have to assemble your parameter settings so you can replicate them to the
new HBA.




Figure 5: SANsurfer HBA Parameters

You can find a cross-reference table of QLogic and Emulex parameters in Appendix B of this
guide. It lists all of the commonly customized parameters, their function and how to find them in
both SANsurfer and OneCommand Manager.




13    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 6: SANsurfer Advanced HBA Parameters

You can find the values of these parameters on the various subpages of SANsurfer’s port
parameters tab, as shown in the screenshots above.

Virtual HBA settings (NPIV, including WWNs)
If you’re using Windows servers with Hyper-V, you can configure your host adapters to create
multiple virtual HBAs using N-Port ID Virtualization (NPIV) and assign those virtual adapter
ports to virtual machines (VMs) to assign LUNs directly to VMs to support Windows Clustering,
among other applications.
To manage virtual adapters, click on the Virtual tab as shown below.




14    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 7: NPIV Configuration

Collecting boot from SAN information
While most system administrators configure boot from SAN through the QLogic FAST!Util at
system boot time, it would be inconvenient to reboot the server just to document the LUN from
which the server boots. So we’ll check on the system’s boot drive from the Boot Device
Selection window.




15    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 8: SANsurfer Boot Configuration

Installing the Emulex HBA
After you’ve collected all of your server’s Fibre Channel configuration information on the settings
worksheet, it’s time to swap the physical HBAs and install the Emulex software. If your server
has internal disks to boot from, the order in which you perform the steps doesn’t matter very
much. If your system is configured for boot from SAN, you should install the Emulex software
before removing the QLogic HBA so the driver will be available for Windows when the server
boots from its SAN boot drive using the Emulex HBA.
Let’s proceed through the process in a manner that will work for either case.

Installing the Emulex driver

Note:
Servers running Windows Server 2003 and Windows
Server 2003 R2 should install the updated Storport driver
from Microsoft Knowledge base article 932755 before
installing the Emulex drivers. You can download the
patched Storport driver from the Microsoft site at:
http://support.microsoft.com/kb/932755.




16      Emulex Step-by-Step Guide | QLogic Migration Guide
Since Emulex uses the same driver for all of their Fibre Channel HBAs, we can install the Emulex driver
before installing the physical HBA. To begin, run the self-extracting package you downloaded from the
Emulex Web site. The following splash screen will appear.




Figure 9: AutoPilot Splash Screen

Click Next> to continue




Figure 10: Driver Installation Options

17     Emulex Step-by-Step Guide | QLogic Migration Guide
Since we’re installing the drivers on a single server, check off “Perform installation of Drivers”.
Unpack drivers is used to create an install point for unattended installs. See the Emulex Quick
Installation Manual for Windows Drivers for more details.




Figure 11: Driver kit installation confirmation window

Now that the driver kit is installed on your computer, the actual driver installation will begin.




18     Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 12: Driver Installation Status window

Click Next> on the status window to install drivers and the monitor window below will open.




19     Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 13: The AutoPilot Installation Monitor window

When the driver installation is complete, the window below will open.




20    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 14: Driver Installation Complete window

Installing OneCommand
Once the drivers are installed, we can move on to installing OneCommand Manager. Again, we
start by executing the package we downloaded from the Emulex Web site to see the screen
below:




21    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 15: OneCommand Manager Install Splash Window

Click Next> to start the installation and the following Options window will open.




Figure 16: OCManager Installation Options


22    Emulex Step-by-Step Guide | QLogic Migration Guide
Select both OCManager Enterprise and Supporting Features and click Install to get the
Management Mode Window below.




Figure 16: OneCommand Manager Installation Modes

Since we’re installing our first server, we’ll want Full Management. Select it and click OK to
install.
When the installation is complete, you’ll see the window below.




Figure 17: OneCommand Manager Installation Complete window

23    Emulex Step-by-Step Guide | QLogic Migration Guide
Now that the software is installed, you can install the physical HBA in an available PCIe slot in
your server.

Removing the QLogic HBA
The next step is removing the QLogic HBA and management software. Just remove the QLogic
HBA and run the SANsurfer uninstaller from the start menu or the Windows Control Panel
Programs applet (Add/Remove Programs in Windows 2003).

Uninstalling SANsurfer
When you start the SANsurfer uninstaller, you’ll see the window below.




Figure 18: SANsurfer Uninstaller

You can then choose a complete or selective uninstall from the Window below. We’ll choose
complete.




24    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 19: SANsurfer Uninstall Options

Clicking next will bring up the progress window below after a few seconds’ wait.




25    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 20: SANsurfer Uninstall Progress

When SANsurfer has been successfully uninstalled, you’ll see the window below.




26    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 21: SANsurfer Uninstall Confirmation

Configuring the HBA
To start OneCommand Manager, select Emulex->OCManager from the start menu. If Windows
User Account Control asks permission for this application to change your computer, click yes.
OneCommand Manager will then start and begin attempting to discover servers with Emulex
HBAs on your network. If the system whose HBA you want to manage doesn’t appear in the left-
hand pane, automatically select Add Host from the TCP/IP submenu of the Discovery menu and
enter its name or IP address. You should then see the host and its HBA(s) in the left-hand
navigation pane, as shown below:




27    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 22: OneCommand Manager Port Information

From here, you can set parameters, run diagnostics and manage the HBA.

Changing WWNs
If you’ve decided to transfer your old HBA’s WWNs to your new HBA, you’ll want to change your
HBA’s WWNs before attempting any other configuration to enable access to your LUNs. To
change the LightPulse HBA’s WWNs:

     1. Open OneCommand Manager and select the port to which you want to assign a WWN
     2. Click on the Maintenance tab




28    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 23: OneCommand Manager Maintenance

     3. Click the Change WWN… button. The Warning below will appear:




Figure 24: WWN Change Confirmation

     4. Click yes and the following dialog box will appear:




29     Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 25: OneCommand Manager Change WWN

     5. Enter the WWPN (port name) and WWNN (Node name) from your old HBA
     6. To ensure that the new WWNs remain after a power outage or hard reboot, leave the
        Write changes to volatile memory for temporary use checkbox unchecked
     7. Click the OK button
     8. Reboot the system to have your changes take effect

Verifying connections
Once you’ve configured your HBA to use the old HBA’s WWNs, or configured your Fibre
Channel fabric and disk arrays to allow the new HBA’s WWNs access to your disks, you can
verify that your system can access the disks.
In OneCommand Manager, expand the entry for your HBA and then for an active port. As
shown below, this will show the targets that have been automatically mounted through that port.
Expand the entry for a target and you can view the LUNs on that target your system can access.




30    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 26: OneCommand Manager LUN Information

Once you can see your LUNs in OneCommand Manager, we suggest you run some test
applications to verify that everything is working properly before starting your production
applications.

Configuring Boot from SAN
If your system is going to be booting from SAN, you’ll want to configure it to boot from the right
LUN. You can do this through the OneCommand Manager GUI or the Emulex BIOS utility that is
accessed by pressing CTRL-E when prompted in your server’s boot process.
To configure boot from SAN through OneCommand Manager, select an HBA port in the
navigation pane and then the Maintenance tab to see the screen below.




31   Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 27: OneCommand Manager Maintenance

Click on the Configure Boot button to see the screen below.




32   Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 28: OneCommand Boot from SAN Configuration

On this screen, you can set the Fibre Channel configuration for boot and select up to eight
LUNs as boot devices. For Windows servers, which should use the default Boot Type of x86,
you just have to click on a button for a boot device. The target LUN information will auto-
populate with the first LUN available. If you want to select another LUN for boot, click the Select
From List button to see the dialog box below.




33    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 29: Selecting the LUN for boot

Here you can select any LUN mounted on your system as a boot device.

Mapping common parameters from QLogic SanScreen to Emulex OneCommand
Manager
OneCommand Manager provides access to most of the detailed Fibre Channel configuration
parameters you can tweak, such as the link speed, from the Drive Parameters tab as shown
below.




34    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 30: OneCommand Driver Parameters Screen

Since QLogic and Emulex sometimes use different terminology to refer to parameters that
perform the same function, you should use the parameter cross-reference chart in Appendix II
of this guide to direct you to the Emulex equivalents of QLogic parameters you may have set in
your old configuration.

Addressing common problems
WWN-based zoning
If your SAN uses WWN-based soft zoning, you can either change the Emulex LightPulse HBA’s
WWNs to those used by your previous HBA, as described in the section titled “Changing
WWNs” above, or change the zone information in your Fibre Channel switches to allow the
WWNs of the new HBA to access the resources. While the process you’ll use to modify your
SAN’s zoning will depend on which Fibre Channel switches and management tools you use,
we’ll step through the process using Brocade’s Web Tools as an example.




35    Emulex Step-by-Step Guide | QLogic Migration Guide
First, open the zone administration window in Web Tools as shown below by selecting a switch
and clicking on Zone Admin from the Manage section of the Tasks menu.




Figure 31: Brocade Web Tools Zone Administration

Once the zone administration window opens, select the zone tab and select the zone you want
to administer from the Name pull down. You’ll see a screen like the one below.




36    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 32: Managing a zone with Web Tools

Here you can see the members of the group in the right-hand pane and the devices that have
logged into the Fibre Channel fabric in the right-hand pane. If you’ve installed and configured
your Emulex HBA it should appear in the right pane. Select the HBA in the right-hand pane and
click on the Add Member button. For multiport HBAs, repeat the process for each port of your
HBA that is connected to this switch.
If you haven’t yet had the HBA log into the Fibre Channel fabric, you can enter the HBA’s
WWNs manually by clicking on the Add Other button. See the following screen.




37    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 33: Manually enter HBAs with the Add Other button

Brocade switches hold changes made through the Web Tools zone administration window in a
buffer until they are saved. In order to have the changes you made take effect, you have to save
them to the switch’s zoning database by selecting Save Config from the Zoning Actions menu.

LUN Masking by WWN
While the details of how to manage LUN masking are different for each disk array vendor, the
basic process of limiting access to LUNs to the servers that should be accessing those LUNs by
Fibre Channel WWN is pretty simple.
On EMC Clariion systems, you place host servers in Storage Groups that you then grant access
to the LUNs. Before a server can access the LUN, you have to register its WWNs with the
system. To start, right-click on the storage system you want to manage and select Connectivity
Status from the menu as shown below.




38    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 34: Navisphere Storage Array

Selecting connectivity status will cause the following dialog box to appear.




39    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 35: Navisphere Host Connectivity

In this scenario, the server DL160-G6-03a has had a new HBA installed. Since that server is
running EMC’s Navisphere agent, the new HBA’s WWNs were automatically registered in the
Clariion. If they hadn’t auto-registered, we could enter the WWNs manually and assign them to
the server by clicking the New button to open the dialog box below.




40    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 36: Navisphere Create Initiator

Enter the WWNN (Node Name) followed by the WWPN (Port Name) in the initiator field and
select the existing host whose HBA you’ve replaced. Repeat for each port on the HBA.
Once you’ve registered the WWNs for the new HBA, you should have access to the LUNs, as
the server is still part of the Storage Group that has access to the LUN as shown below.




41     Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 37: Navisphere Storage Group Management

Post migration - Common management tasks
Of course, once your system is up and running, you’ll still have to maintain it. In addition to
mapping new LUNs and troubleshooting Fibre Channel link problems, most SAN administrators
periodically update the drivers and firmware for their HBAs. For Emulex LightPulse HBAs, this
couldn’t be simpler. In fact, administering Emulex adapters takes approximately half the time
compared to other vendors’ adapters.

Updating drivers
The easiest way to update a single server’s drivers is to just run the installer interactively. The
process runs exactly as for a new installation, but it preserves any custom settings you may
have selected.
To update the drivers on many servers, it’s easier to use the command line option. Once you’ve
downloaded the driver kit, you can enter:

        Elxdrv-fc-fcoe<version>.exe /q2




42    Emulex Step-by-Step Guide | QLogic Migration Guide
Where <version> is the version of the driver you downloaded. You can run the installer from the
command line with the quiet switch from a script as well.

Updating firmware
The first step in updating HBA firmware is to stage the latest firmware version somewhere it is
accessible to the systems to be updated. A software distribution share would be a good place.
Download the latest firmware from the Emulex Web site and extract the .ALL file from the .ZIP
file you downloaded to a location the system can access.
Then in OneCommand Manager, select the port whose firmware you want to update and press
the Update Firmware… button on the Maintenance tab.




Figure 38: OneCommand Manager Maintenance

Click on the Update Firmware… button to see the dialog box below.




43   Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 39: Firmware Download dialog box

Click Browse to select the .ALL file you extracted earlier and click Start Download. The warning
below will appear.




Figure 40: Download Firmware warning

After you click the Yes button on the warning, the firmware download dialog will reappear and
display a progress bar. When the download completes, it will reset the port and look like this.




44    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 41: Firmware Update Complete

Batch-mode firmware updates
You can also use OneCommand Manager to update HBA firmware in batches or use the
command line interface in scripts. See the OneCommand Manager manual for more information
on these options.


After the Install Is Over (Living with LightPulse Adapters)
Congratulations, you’ve successfully migrated your servers to Emulex’s market leading
LightPulse technology. Whether you’ve acquired your HBAs from a leading server or storage
system vendor like HP, IBM, EMC, NetApp or Dell, or from your favorite reseller as an Emulex-
branded product, you’ll get the same combination of superior performance, reliability and
management.
As you’ve already discovered, installing OneCommand Manager was faster and required less
work than installing SANsurfer. You’ve also seen how simple it is to perform the day-to-day
tasks of SAN management, like updating drivers and firmware or configuring boot from SAN
with OneCommand Manager. For more information on the time OneCommand can save over
SANsurfer, see the OneCommand Manager Report Card at:
http://www.emulex.com/artifacts/ad19cc4e-870a-42e9-a4b2-
bcaa70e2afd6/elx_rc_all_onecommand_efficiency_QLogic.pdf.

Perhaps even more importantly, configuration changes and firmware updates of your LightPulse
HBAs can be performed while your servers are in production without rebooting the server. This
means you can perform these tasks during the normal working day without scheduling
downtime and/or working late into the night or on weekends.

.

45    Emulex Step-by-Step Guide | QLogic Migration Guide
Running Diagnostics
While Emulex LightPulse HBAs are highly reliable in the real world, things do sometimes go
wrong, and as a system administrator, your job is to figure out what it was and fix it ASAP. To
aid you in that quest, OneCommand Manager includes a powerful set of diagnostics that will not
only test the state of the HBA, but will also allow you to perform end-to-end connectivity testing,
an Emulex exclusive.
To run diagnostics, select an HBA and port in the left-hand pane of the OneCommand Manager
Application and click on the diagnostics tab in the right-hand pane. You’ll see a screenshot like
the one below.




Figure 42: OneCommand Manager Diagnostics

You can run a quick test of the HBA by clicking the Quick Test button. As the message below
shows, this takes the port offline, so make sure your server has multipath support, or is idle,
before clicking OK.




46    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 43: Quick Test

The quick test runs PCI and local loopback tests to ensure the HBA itself is working properly. If
the quick test succeeds but you suspect you may have a connectivity problem, you can run
more extensive diagnostics by clicking the Advanced Diagnostic Tests button. The most
powerful of these is the Echo test, which, like an IP Ping, will send data to another device on the
Fibre Channel network and request a response.




47    Emulex Step-by-Step Guide | QLogic Migration Guide
Figure 44: Echo Test

In the figure above, we’ve selected the Echo test and used the Select from list button to
automatically enter the WWN of our disk array. We then clicked on the Start Test button and
sent 100 “ping” requests, all of which were answered successfully. This test is good for locating
bad cables, optics and switch ports in your Fibre Channel fabric.


Conclusion
As you expand your computing environment to include server virtualization, you’ll find that
Emulex has blazed the trail for you, providing high-performance adapters to support more VMs
as well as simplified management with a vCenter management plug-in .
When the time comes to upgrade from 8Gb/s Fibre Channel to 16Gb/s Fibre Channel HBAs or
even Fibre Channel over Ethernet CNAs, you’ll be glad that you chose to install Emulex HBAs,
because the common driver model uses the same driver for all generations of Emulex HBAs
and CNAs. Emulex users can simply swap out the old hardware and continue to use the same
driver.
Since all of the servers in a data center running Emulex HBAs can use the same driver system,
administrators can schedule driver updates without having to track updated driver releases for

48    Emulex Step-by-Step Guide | QLogic Migration Guide
different models or track which servers need which driver upgrade. A single driver also means
that the Emulex driver can be installed before the HBA hardware, which allows system
administrators to include the driver in server OS “Golden Images” before those images are
deployed to server hardware.
A common driver also means users have common management tools, including the
OneCommand Manager graphical HBA manager and HBAnyware CLI that can manage Emulex
HBAs of several generations, and across PCI-X, PCIe and blade architectures.
Furthermore, at Emulex, we understand the critical nature our connectivity products play in your
data center. That is why Emulex’s technical support organization is dedicated to providing you
with the world-class support you deserve to ensure maximum availability for your mission-critical
networks. All products are backed with telephone, e-mail and Web support with after-hours
support available, providing 24x7 coverage. The three-year limited warranty also features
unlimited firmware, driver updates, boot code and management application updates. For more
information on Emulex support, visit the support site.
Lastly, by purchasing Emulex adapters, you are eligible to join the EmulexExtras program,
which gives you exclusive access to training, priority notification of new driver releases and
priority access to support, as well as the chance to win tickets to Emulex events and more. Join
the Emulex family today.




49   Emulex Step-by-Step Guide | QLogic Migration Guide
Appendix A – HBA Settings Worksheet
Server Name:                                              Primary IP Address:
HBA Model:                                                Number of Ports:



Port 1                                                    Port 2
Switch connected to:                                      Switch connected to:
Port connected to:                                        Port connected to:
Port WWN:                                                 Port WWN:
Node WWN:                                                 Node WWN:



Target 1
Vendor ID
Product ID
Node WWN
Port WWN
LUN ID
Capacity
Boot From SAN?
Persistently Bound?



Target 2
Vendor ID
Product ID
Node WWN
Port WWN
LUN ID
Capacity
Boot From SAN?
Persistently Bound?




50       Emulex Step-by-Step Guide | QLogic Migration Guide
Target 3
Vendor ID
Product ID
Node WWN
Port WWN
LUN ID
Capacity
Boot From SAN?
Persistently Bound?



Target 4
Vendor ID
Product ID
Node WWN
Port WWN
LUN ID
Capacity
Boot From SAN?
Persistently Bound?



Target 5
Vendor ID
Product ID
Node WWN
Port WWN
LUN ID
Capacity
Boot From SAN?
Persistently Bound?




51    Emulex Step-by-Step Guide | QLogic Migration Guide
Target 6
Vendor ID
Product ID
Node WWN
Port WWN
LUN ID
Capacity
Boot From SAN?
Persistently Bound?



Target 7
Vendor ID
Product ID
Node WWN
Port WWN
LUN ID
Capacity
Boot From SAN?
Persistently Bound?




52    Emulex Step-by-Step Guide | QLogic Migration Guide
Appendix B –Emulex/QLogic parameter mapping reference
QLogic              Values and         SANsurfer         Emulex             Values and         OneCommand        Description
Parameter           default            location          Parameter          default            Location

Connection          0=Loop Only        Port Parameters   Topology           0=Loop             Driver            Determines the
Options             1=Point-to-point   tab, HBA                             1=Point-to-point   Parameters tab    Fibre Channel
                    only               Parameters                                                                topology to use.
                                                                            2=Loop                               For switched
                    2=Loop                                                  Preferred                            fabric select
                    preferred                                               3=Point-to-point                     point-to-point.
                    3=Point-to-point                                        preferred
                    preferred 5

Data Rate           1=Auto-            Port Parameters   Link Speed         0=Auto-            Driver            Data Rate
                    negotiate          tab, HBA                             negotiate          Parameters tab
                    2=1Gb/s            Parameters                           1=1Gb/s
                    3=2Gb/s                                                 2=2Gb/s
                    4=4Gb/s                                                 3=4Gb/s

Frame Size          512                Port Parameters   Frame Size SB      1-8 (256byte       Driver            Maximum frame
                    1024               tab, HBA          C                  units)             Parameters tab    size
                                       Parameters                           1=256
                    2048
                                                                            0=2048
                                                               6
Enable hard loop    0=Disable          Port Parameters   N/A                N/A                N/A               Loop IDs used
ID                  1=Enable           tab, HBA                                                                  for FC-AL not
                                       Parameters                                                                fabric
                    2 = Disable

Hard loop ID        0x00-0xEF          Port Parameters   N/A                N/A                N/A               N/A
                    0x00               tab, HBA
                                       Parameters
Enable HBA Port     0=Disable          Port Parameters   Enable Adapter     Default=Disabled   Port              BIOS must be
BIOS                1=Enable           tab, HBA          Boot                                  Maintenance tab   enabled for boot
                                       Parameters                                                                from SAN.
                                                                                                                 Disabling frees
                                                                                                                 some memory.
Loop reset delay    0-255              Port Parameters   No Equivalent                                           Time HBA waits
                    5                  tab, HBA                                                                  after loop reset
                                       Parameters                                                                before
                                                                                                                 sending/requesti
                                                                                                                 ng data
Enable FC Tape      0=Disable          Port Parameters   Not Required                                            Enables FCP-2
Support             1=Enable           tab, HBA                                                                  recovery for tape
                                       Parameters                                                                applications


Operation Mode      0=Interrupt        Port Parameters   Coalesce           0-63               Driver Options    Controls reduced
                    every I/O          tab, advanced     Response           Milliseconds                         interrupt mode
                    5 = Interrupt on   HBA Parameters    Feature                                                 with Interrupt
                                                                            Default is 0                         delay timer
                    delay timeout
                                                                            Default of 0 is
                    6 = Interrupt on                                        adaptive based
                    delay timeout or                                        on load
                    no active I/Os




5
    Some models only
6
    Emulex HBAs will disable this function if the hard loop address (ALPA) is set to 0.
Emulex Technical Documentation Style Guide



QLogic              Values and         SANsurfer         Emulex           Values and         OneCommand       Description
Parameter           default            location          Parameter        default            Location

Interrupt delay     0-255 (200µsec     Port Parameters   Coalesce         0-255              Driver Options   Controls reduced
timer               units)             tab, advanced     Response         Default = 8                         interrupt mode
                    Default 0          HBA Parameters    Count                                                with Operation
                                                                          Number of IOs to                    Mode. Multiple
                                                                          wait before                         I/O will generate
                                                                          sending an                          1 interrupt,
                                                                          interrupt                           rather than on
                                                                                                              interrupt per I/O
                                                                                                              if received this
                                                                                                              many 200µsec
                                                                                                              units of each
                                                                                                              other.
Enable LIP Full     0=Disabled         Port Parameters   Does Not Apply                                       Used with
Login               1=Enabled          tab, advanced                                                          Enable LIP
                                       HBA Parameters                                                         Reset and
                                                                                                              Enable Target
                                                                                                              reset to manage
                                                                                                              how the HBA
                                                                                                              performs SCSI
                                                                                                              bus resets
Enable Target       0=Disabled         Port Parameters   No Equivalent                                        Delivers target
Reset               1=Enabled          tab, advanced                                                          reset to all
                                       HBA Parameters                                                         devices on SCSI
                                                                                                              bus reset
Enable out of       0=Disabled         Port Parameters   No Equivalent                                        Reassembles
order frame         1=Enabled          tab, advanced                                                          out of order
reassembly                             HBA Parameters                                                         packets received
                                                                                                              if enabled.
Execution           1-655535           Port Parameters   Queue Depth      1-128              Driver           Maximum
Throttle            Default=16         tab, advanced                      Default=32         Parameters tab   outstanding I/O
                                       HBA Parameters                                                         requests
                                       Port Parameters   Queue Target     0=queue per        Driver
                                       tab, advanced                      LUN                Parameters tab
                                       HBA Parameters                     1=Queue per
                                                                          target
Login retry count   0-255              Port Parameters   Node Timeout                                         The number of
                    Default=8          tab, advanced                                                          times the HBA
                                       HBA Parameters                                                         will attempt to
                                                                                                              login
Link Down           0-240 (seconds)    Port Parameters   LinkTimeOut      0-255 seconds      Driver           Seconds the
Timeout             Default=30         tab, advanced                      Default=30         Parameters tab   HBA will wait for
                                       HBA Parameters                                                         a link to come
                                                                                                              back
LUNs per Target     0,8,166,32,64,12   Port Parameters   No Equivalent                                        Maximum LUNs
                    8,256              tab, advanced                                                          per target
                                       HBA Parameters
Enable LIP          0=Enable           Port Parameters   No Equivalent                                        Used with
Reset               1=Disable          tab, advanced                                                          Enable LIP Full
                                       HBA Parameters                                                         Login and
                    Default=0                                                                                 Enable Target
                                                                                                              reset to manage
                                                                                                              how the HBA
                                                                                                              performs SCSI
                                                                                                              bus resets.




54      Emulex White Paper | QLogic Migration Guide
Emulex Technical Documentation Style Guide



QLogic            Values and      SANsurfer          Emulex        Values and        OneCommand       Description
Parameter         default         location           Parameter     default           Location

Spin up delay     0-2 (seconds)   Port Parameters    InitTimeOut   5-60 (seconds)                     Time to wait for
                  Default=0       tab, advanced                    Default=15                         response from
                                  HBA Parameters                                                      target at startup
Enable Extended   0=Disable       Port Parameters    Log Errors    0=All Errors      Driver           Sets the data
Logging           1=Enable        tab, advanced                    1= Severe,        Parameters tab   that Should be
                                  HBA Parameters                   malfunction and                    logged
                  Default=0
                                                                   Command
                                                                   2=Severe and
                                                                   malfunction
                                                                   3=Only Severe




55     Emulex White Paper | QLogic Migration Guide
World Headquarters 3333 Susan Street, Costa Mesa, California 92626 +1 714 662 5600
Bangalore, India +91 80 40156789 | Beijing, China +86 10 68499547
Dublin, Ireland+35 3 (0)1 652 1700 | Munich, Germany +49 (0) 89 97007 177
Paris, France +33 (0) 158 580 022 | Tokyo, Japan +81 3 5322 1348
Wokingham, United Kingdom +44 (0) 118 977 2929

								
To top