Preparing for a new installation
19
Introduction
Required hardware
You must have a laptop, desktop, PC, or similar device with a keyboard and
graphical interface for connecting to the VPLEX management server and configuring
your VPLEX cluster(s). For convenience, this guide uses the term laptop to describe
the device.
Before starting the installation and configuration procedures described in this guide,
confirm that your laptop has the following:
◆ USB port.
◆ CD-ROM drive.
◆ Fully charged batteries — For mobility between the lab environment and a
quieter location from which you can perform most of the configuration tasks.
Generally, access to power outlets will not be a problem. Just in case, however,
fully charged batteries could be useful.
◆ Laptop power supply or laptop-to-rack power cord — For assurance of power.
Required software
Confirm that you have the following on your laptop:
◆ Windows OS
◆ PuTTY, version 0.60 or later (download from www.putty.org) or similar SSH
client
◆ FTP client (download from SourceForge.net) and/or PSCP client
◆ If you want to use the VPLEX GUI:
• Web browser (Firefox v3.5.5 or v3.5.7, or Internet Explorer 7)
• Adobe Flash Player 10.0.0 or higher
Required tools
You will need the following tools when unpacking and installing a VPLEX cluster:
◆ Screwdrivers (#2 Phillips and medium flat-head)
◆ Adjustable or 3/4-inch wrench (to remove shipping plates)
◆ 7/16-inch socket wrench (to remove shipping plates)
◆ 8 mm Allen wrench or cabinet door key (to open and secure the doors)
◆ Knife or wire cutters (to cut strapping)
Reference: VPLEX
requirements
Use redundant physical Fibre Channel links to connect:
◆ Each host to the VPLEX directors
◆ Each director to the back-end storage
To prevent data unavailability:
◆ Ensure that each host in a storage view has paths to at least two directors in each
cluster.
◆ Ensure that multi-pathing is configured in such a way that the paths are
distributed evenly between directors A and B in each engine.
◆ Use redundant SAN fabrics.
As Figure 8 on page 24 shows, each director should connect to both fabrics with
both the front-end and back-end ports. Connecting the ports as shown prevents
data unavailability if a single I/O module fails.
To Next Page
Loading...
Need help?
General
