Upload
marcosvr77
View
261
Download
6
Tags:
Embed Size (px)
DESCRIPTION
best practices for VCA installation
Citation preview
EIS Installation Checklist for the
ORACLE Virtual Compute Appliance (OVCA) X4-2
Customer:
Task Number:
Technician:
Date:
It is recommend that the EIS web pages are checked for the latest version of this
checklist prior to commencing the installation.
The idea behind this checklist is to help the installer achieve a "good" installation.
It is assumed that the installer has attended the appropriate training classes.
Use of a laptop (preferably with Solaris or Linux available) is recommended during
the installation.
It is not intended that this checklist be handed over to the customer.
Feedback is welcome refer to the last page of this checklist.
System Type Rack Master Serial Number
OVCA X4-2
The OVCA is intended to be a customer installable appliance so please keep in mind
that customer install documents may not be identical to EIS checklists. You will
notice that the customer installation documents call for attaching a workstation to port
24 of the ES1-24 switch or port 19 if slower speed is needed. Field personnel should
always use Port 19. All installation activity could be done from either port, but the
field should use port 19 as its not an upward facing port to the customer's network.
If there are any compute nodes to be added to the rack its recommended to install
them after you have installed the OVCA base rack. Always install compute nodes
from the lowest empty slot in the rack progressing upwards to the top. Do not skip
any slots.
For reference the following terminology could be interchanged from document to
document.
Xsigo = F1-15 Switch or F1-15 Director
OPUS = ES1-24
NM2 = 36 port IB switch
Management Node = X4-2 server
Compute Node = X4-2 server
Oracle Internal and Approved Partners Only Page 1 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
Task Check
ENGINEERED SYSTEMS ENTERPRISE SUPPORT TEAM
EEST
If a Field Support Engineer (FSE) requires assistance while installing an
Engineered system, a streamlined method of engaging an Engineered Systems
Enterprise Support Team (EEST) engineer when the SR owner is not
available is described below.
The SR referred to is the installation SR.
An FSE would use this option if they are onsite and require immediate
assistance from EEST. This process is specifically for FSE Callbacks for
hardware, installation and Field Change Order (FCOs) support and should
NOT be used by ACS or partners.
The complete process is described in this Oracle-internal link under the
Tasks tab. Ensure that you understand the contents before going onsite.
Oracle Internal and Approved Partners Only Page 2 of 42 Vn 1.0a Created: 28. Aug. 2014
Task Comment Check
PREPARATIONReference the Oracle Virtual Compute Appliance X4-2 documentation set.
Review Oracle Virtual Compute
Appliance X4-2 Installation Guide.
Refer to the Quick Start Guide part 1 (Part number 7076466) and part 2 (Part number 7079091) that ships with the OVCA for a quick review of the steps to install the OVCA.
Review the safety precautions,
guidelines, site requirements and site
checklists.
Section 4.2.2, Review Safety Guidelines
Chapter 2: Site Requirements
Site Checklists
Ensure that the site is prepared for the
installation of the system.
Section 4.2.3, Prepare the Installation Site.
Review steps for unpacking the system. Section 4.2.5, Unpack Oracle Virtual Compute Appliance X4-2.
Review steps to install the system in its
allocated place.
Section 4.3, "Install Oracle Virtual Compute Appliance X4-2 in Its Allocated Space.
Review the OVCA Administration
Guide.
For complete details about the software configuration process and for advanced configuration and update options, refer to the Oracle Virtual Compute Appliance X4-2Administrator's Guide.
Review all Release Notes.
AUTOMATIC SERVICE REQUEST (ASR) ACTIVITIES
The monitoring capabilities of ASR are necessary for Service and Technical
Support for the OVCA. Therefore, the steps to install ASR on OVCA are
customized and must be done manually. Currently, ASR installation on the
OVCA X4-2 is meant to be FE installed only until it can be automated.
Decide on what ASRM mode you plan
to use.
Some customers work with an ASR
Manager host on a separate system in
their datacenter.
You will need this information when
performing the actions in the ASR
Installation and Configuration section
on page 24.
A standalone ASRM would be necessary ifthere is no other ASR manager at the Customers site. This install would communicate directly to the Oracle backendsystems and is a more standard installation. This method can be used even if the Customer has an ASRM already in use provided they are OK with a second (or third) connection.
A relay ASRM could be used if the Customer already has an established ASRMwhich is already in use by other systems in their facility. Since the other systems CAN NOT be routed through the OVCAs internal ASRM, you must route the OVCA ASRM through the existing one.
The instructions for setting the ASRM in relay mode are in the ASR installation manual, but in short you will be registering the OVCA ASRM to the web address generated by the other ASRM when the
command show_http_receiver is entered.
Oracle Internal and Approved Partners Only Page 3 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
Task Comment Check
DOWNLOAD CURRENT OVCA SOFTWARE
As of the date of this checklist, the latest image for OVCA is 1.1.3 (MOS
patch number 18499286). Currently one cannot search MOS under Product
or Family (Advanced) for OVCA.
Download the OVCA software update from My Oracle Support (MOS) site
(do this before going onsite due to size of file):
1. Go to https://support.oracle.com/ & sign in,
2. Click on the Patches & Updates tab (on the top),
3. In the Patch Name or Number box enter the required patch e.g. 18499286.
4. Click Search.
5. A new screen will appear with the Patch Search Results.
6. Click on the entry in the Patch Name column; there should only be one.
7. Click on the Download button on the right section of the page to
download the files currently 4.4 GB in size.
8. The patch consists of two files that must be unzipped to obtain the two
files within that need to be concatenated/joined in to a single zip file.
The result will be two files of the form: pxxxxxxx_.zip.
This will be required for the actions on page 18 of this checklist.
Copy the software update to a USB
flash drive with adequate space.
You will be bringing this with you to the customer site.
Oracle Internal and Approved Partners Only Page 4 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
The table below references the hostnames in OVCA X4-2.
Refer to pages 35 to 38 for compute node cabling and connections in OVCA X4-2
with regard to the switches.
Rack Unit # Component Hostname SP Hostname
22 F1-15 Xsigo Switch ovcasw22r1 ILOM-ovcasw22r1
21 OPUS Switch A | B
20 NM2-36P IB Switch ovcasw20r1 ILOM-ovcasw20r1
19 NM2-36P IB Switch ovcasw19r1 ILOM-ovcasw19r1
15 F1-15 Xsigo Switch ovcasw15r1 ILOM-ovcasw15r1
14 Compute node
6 Management node ovcamn06r1 ILOM-ovcamn06r1
5 Management node ovcamn05r1 ILOM-ovcamn05r1
2 ZFS-appliance head ovcasn02r1 ILOM-ovcasn02r1
1 ZFS-appliance head ovcasn01r1 ILOM-ovcasn01r1
PDU-A -PDUA
PDU-B -PDUB
Oracle Internal and Approved Partners Only Page 5 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
Task Comment Check
ADDITIONAL INFORMATION
Compute nodes will also have host
names for the server and its ILOM that
would follow the same convention of
using the slot numbering scheme.
Convention for hostnames is:ovca
Abbr. Node type
cn Compute Node
sn Storage Node
sw Switch
mn Management Node
rx Rack Number
Example:
ovcacn07r1 this is a compute node in slot 07 in rack1.
ovcasn14r1 this is a storage node in slot 14 in rack1.
The PDU name field will be a
combination of the rack serial number
- .
If the rack serial number is 1039AK2070 then the PDU A name would be 1039AK2070-PDUA.
The PDUs are configured by default
with the IP addresses and host names.
See tables below for default IP addresses for base unit and expansion unit(s).
PDUs only need to be configured upon replacement, not during an install.
If you must replace a defective PDU,
the initial PDU vendor default is for a
static IP address of 192.168.0.1.
To avoid creating an IP conflict, each PDUwill have to be setup individually and changed to the 192.168.4.xxx address and name as noted below.
Firmware on a new PDU must be
checked and upgraded if required.
Refer to: How to Update Firmware for thePDU in Your Engineered System (MOS Document ID 1543240.1).
Oracle Internal and Approved Partners Only Page 6 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
Table Showing Default IP Configuration Map (Base Rack)
RU# Front View Net 0 IP Management IP IB Bonded IP
42 compute node
41 compute node
40 compute node
39 compute node
38 compute node
37 compute node
36 compute node
35 compute node
34 compute node
33 compute node
32 compute node
31 compute node
30 compute node
29 compute node
28 compute node
27 compute node
26 compute node
25
XSIGO switch 192.168.4.20524
23
22
21 ESI-24 Switch A | B
192.168.4.200
and192.168.4.201
20 NM2-36P IB switch/Gateway 192.168.4.203
19 NM2-36P IB switch/Gateway 192.168.4.202
18
XSIGO switch 192.168.4.20417
16
15
14 compute node
13 compute node
12 compute node
11 compute node
10 compute node
9 compute node
8 compute node
7 compute node
6 management node 192.168.4.4 192.168.4.104 192.168.40.4
5 management node 192.168.4.3 192.168.4.103 192.168.40.3
4ZFS storage
3
2 ZFS appliance - head 192.168.4.2 192.168.4.102 192.168.40.2
1 ZFS appliance - head 192.168.4.1 192.168.4.101 192.168.40.1
PDU - A 192.168.4.210
PDU - B 192.168.4.211
Oracle Internal and Approved Partners Only Page 7 of 42 Vn 1.0a Created: 28. Aug. 2014
Table Showing Default IP Configuration Map (Expansion Rack)
U# Front View Net 0 IP Management IP IB Bonded IP
42 1U Filler
41 1U Filler
40 1U Filler
39 1U Filler
38 1U Filler
37 1U Filler
36 1U Filler
35 compute node
34 compute node
33 compute node
32 compute node
31 compute node
30 compute node
29 compute node
28 compute node
27 compute node
26 compute node
25 compute node
24 compute node
23 compute node
22 compute node
21 compute node
20 NM2-36P IB switch/Gateway 192.168.4.253
19 1U Filler
18 ESI-24 SwitchA | B
192.168.4.250
and192.168.4.251
17 1U Filler
16 NM2-36P IB switch/Gateway 192.168.4.252
15 compute node
14 compute node
13 compute node
12 compute node
11 compute node
10 compute node
9 compute node
8 compute node
7 compute node
6 compute node
5 compute node
4 compute node
3 compute node
2 compute node
1 compute node
PDU - A 192.168.4.240
PDU - B 192.168.4.241
Oracle Internal and Approved Partners Only Page 8 of 42 Vn 1.0a Created: 28. Aug. 2014
Task Comment Check
PREPARE INSTALLATION SITE
Review the safety precautions,
guidelines.
Section 4.2.2, Review Safety Guidelines
Thoroughly clean and vacuum the area
in preparation for the installation.
Note any problems or peculiarities at the site that require special attention or equipment.
Confirm that space, flooring, power
supply and climate control meet all
requirement.
Operate the air conditioning system for 48 hours to bring the room conditions to the appropriate level.
Ensure that all tools required for
unpacking and installation are present.
The following tools are required for installation:
Screwdriver handle (magnetic)
T-30 Torx wrench key
T-25 Torx wrench key
6-mm hexagon Allen wrench key
SW 12-mm single-headed wrench
Side panel removal tool
Keys to the front door, rear door and side panel locks
Cage nut mounting tool
32 M6 cage nuts
32 M6 screws
Straight tip
Oracle Internal and Approved Partners Only Page 9 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
Task Comment Check
UNPACKINGUnpack the Oracle Virtual Compute
Appliance.
For reference refer to the OVCA X4-2 Installation Guide.
Refer to the Sun Rack II Unpacking Guide (820-5210) included with the packaging when unpacking the Oracle Virtual Compute Appliance.
Verify that the hardware configuration
corresponds to your order.
Refer to the Customer Information Sheet (CIS) on the side of the packaging.
Allow the system to acclimatise (power
off) at the customer site.
Unpack outside data center to ensure no
contamination/dust is released inside
customer's controlled environment.
Refer to EIS standard Acclimatisation of Oracle Hardware Products.
Collect packing material together for disposal.
Follow local laws and guidelines to recycle the packaging properly.
Verify all packing material has been
removed from the appliance and
nothing is blocked.
Fans & air vents must be free to operate.
Metal brace plates screwed on the rear of the rack where the PDU power cords are tied are brackets for shipping only. They should be removed if they were not alreadyremoved by the unpacking engineers, so as to not block airflow out of the rack.
Collect the white Customer Information
Sheets (CIS).
Any documentation delivered with the
system should be stored with the spares.
The installer should inform the customer about location of spares (& documentation)kit and request the customer to safely storethe kit outside of the data center room.
Save the mounting brackets used to
secure the rack to the shipping pallet.
You can use these mounting brackets to secure the rack permanently to the installation site floor.
Moving the Oracle Virtual Compute Appliance to Installation Location
Ensure that the rack doors are closed
and secured.
Ensure that the levelling and stabilizing
feet on the rack are raised and out of the
way.
Push the system from the back of the
rack to the installation site.
It is preferred that two people push the rackand a third person in front helps to guide the rack.
Steer the rack by moving the rear
casters.
The front casters do not pivot.
When the rack is at the installation site,
verify that no components or
connections have become dislodged or
disconnected during transport.
If necessary, reattach components and cables properly.
Oracle Internal and Approved Partners Only Page 10 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
Task Comment Check
Ensure that the Rack levelling feet have
been lowered to stabilize the rack to the
floor.
This will prevent it rolling forward or back while working on the rack.
Refer to Sun Rack II 1242 User's Guide Chapter 2 for details on how to lower the feet.
Delivery complete?
Determine the Rack Master Serial
Number.
The Rack's Master Serial Number is located on the top left side wall (viewed from rear) inside the rack on the rear of the chassis.
Contact your regional Installation
Coordinator either by phone or email
and provide this serial number.
This is so that your Installation Coordinatorcan begin the process to verify Install Base information is correct for future entitlementpurposes.
Oracle Internal and Approved Partners Only Page 11 of 42 Vn 1.0a Created: 28. Aug. 2014
Task Comment Check
NETWORK CONNECTION REQUIREMENTS
This section describes the network connection requirements and IP address
requirements to connect Oracle Virtual Compute Appliance X4-2 to your
existing network infrastructure.
Before installation, you must run
network cables from your existing
network infrastructure to the Oracle
Virtual Cloud Appliance X4-2
installation site.
You must connect two 10 Gigabit Ethernet (GbE) IO module ports labelled Public on each F1-15 Director switch to your public Ethernet network.
This image shows the location of the 10 GbE Public IO module ports on the F1-15
Director switch. Refer to page 35 of this checklist for a more detailed description of
the card types in each slot.
Before you power on the Oracle Virtual
Compute Appliance X4-2 for the first
time, ensure that you have connected
the F1-15 Director switches according
to the network installation
requirements.
Section 3.1, Network Connection and IP Address Requirements.
You need to connect a workstation with
a monitor to the Oracle ES1-24 switch,
using the supplied blue Ethernet cable
connected to port 19 and start a web
session in order to initially administer
Oracle Virtual Compute Appliance X4-
2 using the pre-defined IP address
(192.168.4.3).
For information, see Section 5.3.5, Connect Oracle Virtual Compute Appliance X4-2 to the Network.
The PDUs are configured by default
with IP addresses and host names
according to the table on page 7.
PDUs only need to be configured upon
replacement, not during an install.
Oracle Internal and Approved Partners Only Page 12 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
Task Comment Check
STEPS FOR POWERING ON OVCA X4-2
Reference the Installation Guide at: http://docs.oracle.com/cd/E52085_01/E52086/html/
Review the safety precautions,
guidelines, site checklists and site
requirements.
Section 5.3.1 Review Safety Guidelines
Adding additional compute nodes. Compute nodes are added by preparing the rack to install the X4-2 nodes the same waythey would be installed in any rack, except that the cables are already pre-installed in the rack. Compute nodes can be added at any time, but for installation purposes it would be recommended to install all additional compute nodes after the OVCA install has been completed. This way you will be adding compute nodes to a known good installation.
See APPENDIX A for details.
Verify the hardware by visually
inspecting the system.
Perform preliminary checks before
connecting the power cords.
Section 5.3.2 Inspect Oracle Virtual Compute Appliance X4-2 .
Connect the F1-15 Director switches
according to the network installation
requirements.
Section 5.2 Before Initial Power On .
Connect a workstation with a monitor to
the Oracle ES1-24 switch to port 19.
Supply rack power, and perform the
power-on self-test device checks.
Section 5.3.3 Connect the Power Cords.
Switch on the two power distribution
unit (PDU) circuit breakers located on
the PDUs (PDU A and B).
Section 5.3.4 Power On Oracle Virtual Compute Appliance X4-2 .
Ensure that the PDU switches have had power applied for approximately two minutes to complete power-on configuration before starting the management nodes.
Oracle Internal and Approved Partners Only Page 13 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALAIMPORTANTE
Task Comment Check
Power on the management node in slot
number 5.
Make sure that the circuit breakers located on the rear left and right side power supplies of the Sun ZFS Storage Appliance
are in the ON (|) position.
Press the Power button located on the frontof the first Sun Server X4-2 management node.
The first management node is located in
rack unit 5 (U5). The second
management node is located in rack unit 6(U6). It is switched on and configured automatically during the initial power-on sequence.
A management node take approximately three to five minutes to power on completely. Once complete, the Power/OKLED illuminates and remains a steady green.
After powering on the first management
node, wait a while for the second
management node to be powered on automatically by the OVCA software.
Wait 3 to 5 minutes and then proceed to
the steps below for Initial Access to the
Oracle Virtual Cloud Appliance X4-2.
Oracle Internal and Approved Partners Only Page 14 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
INITIAL ACCESS ASSUMPTIONS
In an EIS installation the following assumptions are made:
Systems come pre-configured from the factory with a default name and IP
address. This is utilised in this checklist for actions before connecting to the
customer network. The root password on all systems OS and ILOM has been set
to Welcome1.
See APPENDIX C: Table References for Logins, Passwords, and
Hostnames in OVCA X4-2 for tables referencing logins, passwords and ports.
EIS recommends that connections from the rack components to the Customer
network should be made before the initial configuration (as described in this
checklist).
Component numbering starts with 1 at the rack bottom working upwards.
NOTES AND PRECAUTIONS
ILOM:
Each node has an integrated ILOM (remote management) controller.
In the OVCA setup we share the same physical Ethernet port (port 0/eth0) for
the ILOM's management interface and the nodes' host OS eth0 interface.
The ILOM and host have a separate MAC address and a separate IP address.
You can ssh into the ILOM by using the command line:ssh root@.
ILOM can be used to reset systems, connect to remote console, query mac
address, change boot parameters, etc.
WARNING: DO NOT RECONFIGURE NETWORK DURING COMPUTE
NODE PROVISIONING OR UPGRADE
In the Oracle Virtual Compute Appliance Dashboard, the Network Setup tab
becomes available when the first compute node has been provisioned
successfully.
DO NOT CHANGE any passwords from their default values until the
installation and any image updates are complete.
When installing and provisioning a new system, you must wait until all nodes
have completed the provisioning process before changing the network
configuration.
When provisioning new nodes at a later time, or when upgrading the
environment, DO NOT APPLY a new network configuration before all
operations have completed.
Failure to follow these guidelines is likely to leave your environment in an
indeterminate state.
Oracle Internal and Approved Partners Only Page 15 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
Task Comment Check
INITIAL ACCESS TO OVCA X4-2
For initial access to Oracle Virtual
Compute Appliance X4-2, you can use
the pre-installed blue Ethernet cable
connected to port 19 on the Oracle ES1-
24 switch to connect a workstation with
a monitor. The Oracle Virtual Compute
Appliance Dashboard can be reached by
means of a web browser.
You can connect to the Ethernet port at anytime during the system power-on process. However, you should wait approximately two to three minutes after starting the power-on process to allow the IP address to become active.
If you connect too soon to the port, you will see an HTTP error code 404 or similarcode. If this occurs, wait a few minutes and try to connect again.
An overview of the Oracle Virtual
Compute Appliance Dashboard can be
found in APPENDIX B: Oracle Virtual
Compute Appliance Dashboard
Ensure that the F1-15 Director switch is
connected to your datacenter (public)
network.
For details, see Section 3.1.1 Network Connection Requirements.
Connect a workstation with a web
browser directly to the management
network using the supplied blue
Ethernet cable connected to port 19 of
an Oracle ES1-24 switch.
There should be an existing cable connected to this port for field service use.
Configure the wired network connection
of the workstation to use the static IP
address 192.168.4.254.
Using the web browser on the
workstation, connect to the Oracle
Virtual Compute Appliance Dashboard
with the predefined IP address of the
first management node.
http://192.168.4.3 is the predefined
port IP address for configuring Oracle Virtual Compute Appliance X4-2.
Log into the Dashboard. user name: ovcaadminpassword: Welcome1
The Dashboard opens in the Hardware
View tab.
This view indicates the status of the appliance as it is being powered on. All the networking and storage should be green. Compute Nodes will not provision until the mandatory software update is done, so they will not show green at this time.
Using the Dashboard, congure the
system environment parameters.
Including: input locale, domain name, time zone, NTP and DNS servers.
Go to the Network Setup tab and
replace the default IP conguration of
the management nodes with the
reserved IP addresses in your data
center network.
During the initial configuration of the Oracle Virtual Compute Appliance X4-2, you change the predefined configuration IPaddress to the reserved virtual IP address in your datacenter network. For details, see Section 3.1.2 IP Address Requirements.
Oracle Internal and Approved Partners Only Page 16 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
Task Comment Check
Enter the default gateway of your
datacenter network.
Reconnect to the Oracle Virtual
Compute Appliance Dashboard at the
new virtual IP address of the
management node cluster.
https://:7002/ovca
After the initial power-on, you may
proceed to the next steps to update the
OVCA software if needed.
Compute node provisioning is locked as long as the update has not been completed successfully.
Oracle Internal and Approved Partners Only Page 17 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
ZAVALA
Task Comment Check
UPDATING THE OVCA IMAGE
Make sure you have reviewed the Administration guide and Release notes
prior to starting the update procedure.
Refer to Section 2.5 Update in the Oracle Virtual Compute Appliance X4-2
Administrator's Guide for instructions to update the Oracle Virtual Compute
Appliance controller software.
Follow the README file in patch 18499286 to prepare for the upgrade.
CAUTION If direct Internet access is not available within your datacenter
and you make use of proxy servers to facilitate HTTP, HTTPS and FTP
traffic, it may be necessary to edit /etc/ovca.conf, on each management
node, to ensure that the correct proxy settings are specified for a download to
succeed from the Internet. See 6.1 Adding Proxy Settings for Oracle Virtual
Compute Appliance Updates for more information.
PREPARING TO UPDATE THE OVCA SOFTWARE
Check the contents of /etc/ovca-info to confirm whether or not you need
to apply the latest OVCA software.
Example: (partial output):
# cat /etc/ovca-info==== Begin build info ====date: 2014-03-27release: 1.1.1build: 410=== Begin compute node info ===
Compare the installed release with the downloaded version from page 4.
If the version installed is the same as what you downloaded, then you can
skip this section and move on to VALIDATING THE INSTALLATION on
page 21.
Unzip the patch files you downloaded on page 4 and join them in to a single
zip file.
There is a README.html file included in the 1of2 zip file that details how to
do this.
The patch comprises two files that must be unzipped to obtain the two files
within that need to be concatenated into a zipfile. Be patient. The files are
large (one of them is approximately 3.6GB) and may take some time to
decompress and recompress.
# unzip p18499286_30_Linux-x86-64_1of2.zip Archive: p18499286_30_Linux-x86-64_1of2.zip inflating: README.html inflating: ovca-1.1.3-b3_1 # unzip p18499286_30_Linux-x86-64_2of2.zip Archive: p18499286_30_Linux-x86-64_2of2.zip inflating: ovca-1.1.3-b3_2 # cat ovca-1.1.3-b3_1 ovca-1.1.3-b3_2 > ovca-1.1.3-b3.zip
Compare the MD5 checksum with that included in the README.html file.
# md5sum ovca-1.1.3-b3.zip5db7f34a5700d39baef3394dc4d0add3 ovca-1.1.3-b3.zip
Oracle Internal and Approved Partners Only Page 18 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
Task Comment Check
The resulting zip file is then uploaded to the OVCA per the instructions in
chapter 2.5 Update, item 3 in the OVCA Administrator's Guide.
Using SSH and an account with
superuser privileges, log into the
management node.
Use a workstation connected to the provided cable attached to port 24 of the Oracle Switch ES1-24 and statically assign IP address 192.168.4.254 to it. In this internal appliance management network, the first management node IP address is 192.168.4.3.
# ssh [email protected]@192.168.4.3's password:root@ovcamn05r1 ~]#
You must log in to both management
nodes using SSH to create the file /tmp/install.log
Note: Before the mandatory initial
update, you need to make sure the second
management node is on.
# ssh [email protected]@192.168.4.3's password:# touch /tmp/install.log
# ssh [email protected]@192.168.4.4's password:# touch /tmp/install.log# exit
UPDATING THE OVCA SOFTWARE
Use the ovca-updater command to download and process the file on to the
OVCA node.
Example:# ovca-updater -m download -s -u file:////ovca-1.1.3-b3.zipDownload of http://download-url.example.com/ovca-version-build.zip started successfully. \Task id is 5ba4f1a09c9546b29a560e3d6682ce67
Check the progress of the ISO download
using the Task ID noted in the above
output.
When the download is finished, proceed
with the next step.
Once the image has been downloaded it is extracted into the mgmt_image, hmp_image, and ovm_image subdirectoriesof /nfs/shared_storage, which resides in the MGMT_ROOT file system on the Sun
ZFS Storage Appliance 7320.
To list individual task status with Task ID provided (above):
# ovca-updater -m download -l -i 5ba4f1a09c9546b29a560e3d6682ce67Task ID Pct Elapsed time Status5ba4f1a09c9546b29a560e3d6682ce67 60% 155.305 sec RUNNING # ovca-updater -m download -l -i 5ba4f1a09c9546b29a560e3d6682ce67Task ID Pct Elapsed time Status5ba4f1a09c9546b29a560e3d6682ce67 70% 285.904 sec RUNNING # ovca-updater -m download -l -i 5ba4f1a09c9546b29a560e3d6682ce67Task ID Pct Elapsed time Status5ba4f1a09c9546b29a560e3d6682ce67 100% 338.102 sec SUCCESS
To list the status of all downloads:
# ovca-updater -m download -lTask ID Pct Elapsed time Status5ba4f1a09c9546b29a560e3d6682ce67 100% 338.102 sec SUCCESS
Intentionally left blank
ACTIVATING THE UPDATE
Oracle Internal and Approved Partners Only Page 19 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
ZAVALA
Task Comment Check
When the download has completed
successfully, activate it by launching the
update process.
This update takes approximately 2 hours.
Updates are controlled with ovca-updater commands.
Using SSH and an account with
superuser privileges, log into the
management node and enter the
command to perform the update.
# ovca-updater -m update -sWARNING:root:Activating updateprocess. Starting with nonmaster node 192.168.4.4
Check the progress of the software
update from time to time.
Example below
# ovca-updater -m update -lMgmt Node IP Update Started Update Ended Elapsed192.168.4.4 2013-10-02 16:52:14 ------------------- 0:02:18
At a certain point during the update
process, the active management node is
rebooted.
As a result, the SSH connection is lost.
In addition, this may cause the Dashboard to become unresponsive temporarily and you may be required to log back in.
Once the update is done on the
management nodes the compute nodes
will start being provisioned.
For a rack with 25 compute nodes this could take up to 3 hours. It will be less for fewer numbers of compute nodes.
Once the update is complete check the contents of /etc/ovca-info to
confirm the update version.
Example: (partial output):
# cat /etc/ovca-info==== Begin build info ====date: 2014-03-27release: 1.1.1build: 410=== Begin compute node info ===
Oracle Internal and Approved Partners Only Page 20 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
Task Comment Check
VALIDATING THE INSTALLATION
This section is not yet complete and will be expanded upon at a later time.
At this time there are no automatic
scripts that will check the hardware as
in some other ES systems you may be
familiar with like a heathcheck.
This is being worked on and will be available in the near future.
Start with visual check to confirm that
no components have service LEDs
illuminated.
If a service LED is found on, that component can be checked out via normal troubleshooting methods for that platform.
To access ILOM, use the node connected to port 19 which was previously set up and ssh into the ILOM service processor of the target node.
Compute node ILOM addresses can be discovered from the Dashboard. Other ILOM addresses are shown in the tables at the end of this checklist.
In /usr/sbin on every node is ovca-diag which is similar to sundiag on Exadata.
You can reference MOS Document ID 1612336.1.
USING OVM TO CHECK THE HARDWARE
To open the Login page of the Oracle
VM Manager user interface, enter the
following address in a Web browser:
https://hostname:7002/ovm/console
Where, hostname refers to the host name orIP address of the Oracle VM Manager hostand port refers to the port number on whichthe Oracle VM Manager user interface is listening (which is 7002 by default).
n previous versions of Oracle VM Managerunencrypted HTTP traffic was permitted by default. HTTP access is now disabled by default and Oracle VM Manager uses Secure Sockets Layer (SSL) to encrypt all HTTP traffic. Therefore you should always use https in the protocol section of your URI.
IMPORTANT: You must ensure that
if you are accessing Oracle VM
Manager through a firewalled
connection, that the firewall is
configured to allow TCP traffic on the
port that Oracle VM Manager is using
to listen for connections.
To connect to Oracle VM Manager on a host named example.com, use:
https://example.com:7002/ovm/console
Oracle Internal and Approved Partners Only Page 21 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
ZAVALA
ZAVALA
Task Comment Check
Check the Health tab first:
Next check the Servers and VM tab for
a list of all servers and the status.
Your number of compute nodes in your rack should be the same as the servers listed here.
This is a section of the Servers and VMs tab; not all data is shown here:
To examine data on each server you can
select info in the Perspective drop
down box.
The above screenshot is an example how toshow servers icons in a normal state listed under Rack 1. All compute nodes should be listed here.
In the unassigned server area you can see that there are two servers, ovcacn09r1 has a warning and ovcacn26r1 was not added to the Rack1 pool as it should have been. These two servers would need to be investigated.
To examine the ILOMs in any compute
node you will have to determine the
ILOM address.
Refer to this link, How to determine the IP addresses of the Service Processors an
OVCA rack (MOS Document ID
1591197.1), to help with discovering the ILOM IP addresses. These are not assigned in any order upon provisioning.
Oracle Internal and Approved Partners Only Page 22 of 42 Vn 1.0a Created: 28. Aug. 2014
Task Comment Check
Next you can log into each F1-15 Xsigo
Switch with ssh as admin. IP addresses
are 192.168.4.204 and 192.168.4.205.
Xsigo has no ILOM support at this time.
From the CLI you can run the show
hardware command.
This will show:
IO Card Version status
IO Card Environment status
Front Panel Version status
Front Panel Environment status
Fabric Card status
System Control Processor status
Power supply status
Fan controller status and Fan status
If the installation is free of any issues, the installation of the OVCA is
COMPLETE.
Proceed to the next section to perform the manual installation of ASR.
Oracle Internal and Approved Partners Only Page 23 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
Task Comment Check
ASR INSTALLATION AND CONFIGURATION
The necessary packages for ASR Manager are included in the Oracle Virtual
Compute Appliance Release 1.1 software image. For the ASR Manager to
work on a Oracle Virtual Compute Appliance, it must be installed on both
management nodes, and failover must be configured so that the ASR
Manager role is always fulfilled by the management node that also has the
master role.
The ASRM mode (standalone or relay) that you will use was determined
during the PREPARATION activities on page 3.
INSTALLING ASRM
Using SSH and an account with
superuser privileges, log into the master
management node.
Example (sample IP address used):
# ssh [email protected]@10.100.1.101's password:[root@ovcamn05r1 ~]#
Go to the packages directory of the mounted management software image.
Verify that the ASR packages are present. Example:
# cd /nfs/shared_storage/mgmt_image/Packages/# ls -al | grep SUNW-rw-r--r-- 1 root root 12406356 Apr 7 04:37 SUNWsasm-1.5.0-112.rpm-rw-r--r-- 1 root root 24090626 Apr 7 04:37 SUNWswasr-4.7-20140116133106.rpm
Install the ASR Manager packages without verifying dependencies.
For Oracle Virtual Compute Appliance the auto-update feature of ASR must
not be used.
Example:
# rpm -ivh SUNWsasm-1.5.0-112.rpm --nodepsCopyright 2008,2013 Oracle and/or its affiliates. All rights reserved.
License and Terms of Use for this software are described athttps://support.oracle.com/ (see Terms of Use)
# rpm -ivh SUNWswasr-4.7-20140116133106.rpm --nodepsCopyright [2008,2012], Oracle and/or its affiliates. All rights reserved.
License and Terms of Use for this software are described athttps://support.oracle.com/ (see Legal Notices and Terms of Use).
Directory /var/opt/SUNWsasm/configuration/caseinfo created.Directory /var/opt/SUNWsasm/configuration/supportfile created.
ASR Manager Auto Update functionality has been enabled by default.Please ensure that ASR Manager is registered with ASR backend to get thesoftware updates.
Warning: rpm-build package is not installed on this server. ASR ManagerAuto Update functionality will not work unless the rpm-build package isinstalled. Auto Update functionality will be disabled until rpm-buildpackage is installed. Please install the rpm-build package and then enableAuto Update by running "asrenable_autoupdate".Installation of SUNWswasr was successful.
At the end of the installation, the ASR Manager service (sasm) is started
automatically.
Stop the ASR Manager service and
prevent it from starting automatically.
# service sasm statusOracle Automated Service Manager (pid 450596) isrunning...
# service sasm stopStopping Oracle Automated Service Manager...
Stopped.
Oracle Internal and Approved Partners Only Page 24 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALAAuto service request for premier support
ZAVALA
ZAVALA
Task Comment Check
Turn off the autostart for the SASM
service.
# chkconfig sasm off
SET UP INIT SERVICE TO LOG STARTS & STOPS OF THE ASRM
Edit the /etc/init.d/sasm file. In the start and stop sections, add the echo
commands as shown:
'start') /opt/SUNWsasm/bin/sasm start-instance echo "START: `hostname` `date "+%D %T"`" >> /nfs/shared_storage/ASRM/ASRHA.log ;;
'stop') /opt/SUNWsasm/bin/sasm stop-instance echo "STOP: `hostname` `date "+%D %T"`" >> /nfs/shared_storage/ASRM/ASRHA.log ;;
Save and close the file /etc/init.d/sasm
Make sure that the sasm configuration
file points to the correct JDK
Verify and copy the path to the
appropriate java executable.
If you installed Oracle Java - JDK 7 by following the instructions in the ASR Prerequisites section, it should be /opt/jdk1.7.0_51/bin/java
Edit the sasm configuration file /var/opt/SUNWsasm/configuration/config.ini
Set the java.exec value to the path you copied. Refer to the emboldened
entry below:
# OASM version#sasm.version=1.5.0## The JVM lookup-order of OASM has been defined as follows:# 1. JAVA_HOME/bin# 2. java.exec value defined below# 3. java in path## Therefore, note that JAVA_HOME/bin/java takes precedence (if exists) over them# so remember to unset JAVA_HOME if you prefer to use following java.exec spe## java.exec=/usr/java/default/bin/javajava.exec=/opt/jdk1.7.0_51/bin/java#[...]
Save and close the file:
/var/opt/SUNWsasm/configuration/config.ini
Preserve the information in the original directories:
# mv /var/opt/SUNWsasm /var/opt/orig_SUNWsasm
Repeat this procedure on the other
management node.
The secondary management node does not need to take over the master role during theASR installation.
The ASR Manager service must remain stopped on both management nodes.
After you have installed ASRM on the
PASSIVE master node, you may
proceed to the next section.
Oracle Internal and Approved Partners Only Page 25 of 42 Vn 1.0a Created: 28. Aug. 2014
Oracle Internal and Approved Partners Only Page 26 of 42 Vn 1.0a Created: 28. Aug. 2014
Task Comment Check
CONFIGURING THE ASRM FOR FAILOVER
The following steps are to be done on the ACTIVE master node with all
ASRM services still stopped.
IMPORTANT: Do NOT do this on both management nodes.
Using SSH and an account with
superuser privileges, log into the master
management node.
Create the following directories and touch off the ASRHA.log file if they do
not already exist.
Directories:
# mkdir /nfs/shared_storage/ASRM# mkdir /nfs/shared_storage/ASRM/VarOptSUNWsasm
Log file:
# touch /nfs/shared_storage/ASRM/ASRHA.log
Copy the original files to their shared location.
# cp -r /var/opt/orig_SUNWsasm/* /nfs/shared_storage/ASRM/VarOptSUNWsasm
THE FOLLOWING STEPS ARE TO BE DONE ON BOTH NODES
Create the soft/symbolic links to the necessary directories.
# ln -s /nfs/shared_storage/ASRM/VarOptSUNWsasm /var/opt/SUNWsasm
Edit /var/lib/ovca/ovca-system.conf
to add a service.
On or about line 32, you will see an entry with the following entries:
foundational_services: ovmm_mysql
ovmm tinyproxy xms dhcpd sasm
Add the entry (sasm) to that list above.
Save and close the file.
Repeat these three steps on the other
node.
When you are done, proceed to the next section.
Oracle Internal and Approved Partners Only Page 27 of 42 Vn 1.0a Created: 28. Aug. 2014
Task Comment Check
START UP ASR
PERFORM THE FOLLOWING STEPS ON THE ACTIVE MASTER
Using SSH and an account with
superuser privileges, log into the master
management node.
Start the SASM service. # service sasm start
Monitor the status by tailing the file:/nfs/shared_storage/ASRM/ASRHA.log
Set logging to fine. # /opt/SUNWswasr/bin/asrasr> get_loglevel
INFO:
asr> set_loglevel finelog.level is set to fineStopping ASRASR stoppedStarting ASRASR started
asr> get_loglevelFINEasr>
Register the ASR Manager.
Refer to the earlier Preparation step on
page 3 as to which ASRM mode you
plan to use.
See ASR Installation instructions: Register the ASR Manager found in the online documentation.
The registration of the ASR Manager (ASRM) may be in one of two modes.
1. As a standalone ASRM
2. As an ASRM relay to another ASRM.
Test the failover. Reboot.
Monitor the status by tailing the file:
/nfs/shared_storage/ASRM/ASRHA.log
If you encounter any issues, check the troubleshooting guide here: 5.11 ASR Activation Failed Troubleshooting
If you still cannot resolve the issue, contactthe EEST per instructions on page 2 of thischecklist.
Oracle Internal and Approved Partners Only Page 28 of 42 Vn 1.0a Created: 28. Aug. 2014
Task Comment Check
SETTING UP TINYPROXY
The ZFS Storage Appliance runs its own ASR Manager and relays its ASR
data to the Oracle backend systems through the outbound connection of the
master management node. For OVCA, ASR requires tinyproxy version 1.8.3
or later to be installed and properly configured on both management nodes.
tinyproxy 1.8.3 is included in version 1.1.3 of the OVCA software
The following steps are to be done on the ACTIVE master first. Afterwards,
perform them on the PASSIVE master.
Using SSH and an account with
superuser privileges, log into the master
management node.
Stop the tinyproxy service and verify
the version installed on the system
# service tinyproxy stopStopping tinyproxy: [ OK ]# rpm -q tinyproxytinyproxy-1.8.3
Edit /etc/tinyproxy/tinyproxy.conf
file.
Comment out the current Listen directive.
#Listen 192.168.140.4
Scroll down to the section Customization of authorization controls. It starts
with # Allow. Add in the following two Allow directives in the
appropriate section around line 210.
Allow 192.168.4.0/24Allow 192.168.140.0/24
Verify your edits.
# grep Allow tinyproxy.conf# LogFile: Allows you to specify the location where information should# Set the logging level. Allowed settings are:# Allow: Customization of authorization controls. If there are any#Allow 127.0.0.1Allow 192.168.4.0/24Allow 192.168.140.0/24
# grep Listen tinyproxy.conf# Listen: If you have multiple interfaces this allows you to bind to#Listen 192.168.140.4
Save and close the tinyproxy.conf
file.
Restart tinyproxy. # service tinyproxy startStarting tinyproxy: [ OK ]# tinyproxy -versiontinyproxy 1.8.3
Repeat the steps in this section for the
passive master.
Oracle Internal and Approved Partners Only Page 29 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
ZAVALA
Task Comment Check
ACTIVATING ASR ASSETS
ASR activation of the servers used in the OVCA are all done in the same
manner. The ILOMs are configured to send the traps when a failure occurs
and then you tell the ASRM to accept their input with the activate_asset
command.
IMPORTANT: Do not activate the management nodes for OVCA image
1.1.1 or lower.
ACTIVATING COMPUTE NODES
In the ILOMs of the Compute Nodes, Management Nodes and NM2-36p's,
you will need to set up the alerts to point at both of the management nodes.
It is common practice to point rule #1 at Management Node A and rule #2 at
Management Node B but it is not required.
Any rules may be used as long as both management Nodes have a pointer.
# ssh root@(enter the root password)
-> cd /SP/alertmgmt/rules/SP/alertmgmt/rules
-> show 1
/SP/alertmgmt/rules/1 Targets:
Properties: type = snmptrap level = disable destination = 0.0.0.0 destination_port = 0 community_or_username = public snmp_version = 1 testrule = (Cannot show property)
If the ILOM already has rule #1 set up then skip it and go to rule #2. If that is
set up continue forward until you have one that is open. If it is open
(indicated by 'destination = 0.0.0.0') then proceed.
-> cd 1-> set level=minor destination=192.168.4.216 destination_port=162 snmp_version=2c-> show
/SP/alertmgmt/rules/1 Targets:
Properties: type = snmptrap level = minor destination = 192.168.4.216 destination_port = 162 community_or_username = public snmp_version = 2c testrule = (Cannot show property)
Commands: cd set show->
Log in to the master management node
Oracle Internal and Approved Partners Only Page 30 of 42 Vn 1.0a Created: 28. Aug. 2014
Task Comment Check
Activate the asset by adding its ILOM
IP to the ASR configuration with the
following command
# /opt/SUNWswasr/bin/asr activate_asset i
Verify that you are activating the asset withthe IP address of its ILOM, and not the IP assigned to another network interface.
Repeat this procedure for each compute
node you wish to activate as an ASR
asset.
ACTIVATING NM2-36P IB SWITCHES
On the ILOMs of the NM-36p's, set up the alerts to point at both of the
management nodes. Log in and launch the Service Processor Shell (spsh).
Example:
ssh root@(enter the root password)
[root@ilom-ovcasw19r1 ~]# spsh
-> cd /SP/alertmgmt/rules/SP/alertmgmt/rules
-> show 1 /SP/alertmgmt/rules/1 Targets:
Properties: type = snmptrap level = disable destination = 0.0.0.0 destination_port = 0 community_or_username = public snmp_version = 1 testrule = (Cannot show property)
Commands: cd set show
-> set level=minor destination=192.168.4.216 destination_port=162 snmp_version=2cSet 'level' to 'minor'Set 'destination' to '192.168.4.216'Set 'destination_port' to '162'Set 'snmp_version' to '2c'
-> show /SP/alertmgmt/rules/1 Targets:
Properties: type = snmptrap level = minor destination = 192.168.4.216 destination_port = 162 community_or_username = public snmp_version = 2c testrule = (Cannot show property)
Oracle Internal and Approved Partners Only Page 31 of 42 Vn 1.0a Created: 28. Aug. 2014
Task Comment Check
Verify that SNMP version 2c is enabled on the switch. This is not required
for servers.
-> cd /SP/services/snmp/SP/services/snmp
-> show/SP/services/snmp Targets: communities mibs users Properties: engineid = (none) port = 161 servicestate = enabled sets = disabled v1 = disabled v2c = disabled v3 = enabled Commands: cd set show
-> set v2c=enabled
Log in to the master management node
Activate the asset by adding its ILOM
IP to the ASR configuration with the
following command
# /opt/SUNWswasr/bin/asr activate_asset i
Verify that you are activating the asset withthe IP address of its ILOM, and not the IP
assigned to another network interface.
Repeat this procedure for the second
switch to activate as an ASR asset.
Intentionally left blank
Oracle Internal and Approved Partners Only Page 32 of 42 Vn 1.0a Created: 28. Aug. 2014
Task Comment Check
ACTIVATING THE ZFS STORAGE APPLIANCE
You will be setting up the ZFS appliance to use a proxy for sending the
events to the Oracle backend systems. More detailed instructions for
enabling ASR for the ZFS Storage Appliance are in MOS Document ID
1285455.1.
When prompted you should use the
following proxy settings.
inet addr: 192.168.4.216Broadcast: 192.168.4.255Mask: 255.255.255.0Port: 8888
The setup screen should look like this...
Oracle Internal and Approved Partners Only Page 33 of 42 Vn 1.0a Created: 28. Aug. 2014
ZAVALA
APPENDICES
APPENDIX A
Task Comment Check
ADDING A COMPUTE NODE
Compute nodes are added by preparing
the rack to install the X4-2 nodes the
same way they would be installed in any
rack, except that the cables are already
pre-installed in the rack.
Compute nodes can be added at any time, but for installation purposes it would be recommended to install all additional compute nodes before the initial power upof the OVCA.
The Oracle Virtual Compute Appliance
monitoring software will detect that one
or more new compute nodes are present
in the rack.
The monitoring software will automatically power on the new hardwareand will execute the provisioning procedure.
The expansion compute nodes are
incorporated seamlessly into the active
system.
This requires no further interventions by an administrator.
Expansion Node Setup Poster part one (P/N 7076467) and part two (P/N 7079062) are shipped with the system andhave installation instructions and illustrations to assist in the installation.
For complete details please review the
OVCA Installation Guide which will also
have helpful illustrations.
Specific steps to install the compute nodes are at section 6.5 Install the ServerInto the Rack
Follow all steps in this section.
Oracle Internal and Approved Partners Only Page 34 of 42 Vn 1.0a Created: 28. Aug. 2014
F1-15 Card locations
Below is a reference to the card types and their locations on the F1-15 Director
Switch. Tables on the following pages will reference which cables go to which port.
F1-15 Slot number: 1 2 3 4 5 6 7 8
Card locations:F
ILL
ER
FIL
LE
R
FC
Mod
ule
(VP
E-M
OD
-8F
C-2
P-R
13)
10-G
ig-E
Module
(VP
E-M
OD
-10G
E-4
P-R
13)
10-G
ig-E
Module
(VP
E-M
OD
-10G
E-4
P-R
13)
FIL
LE
R
FIL
LE
R
FIL
LE
R
F1-15 Slot number: 9 10 11 12 13 14 15
Card locations:
FIL
LE
R
FIL
LE
R
FC
Mod
ule
(VP
E-M
OD
-8F
C-2
P-R
13)
10-G
ig-E
Module
(VP
E-M
OD
-10G
E-4
P-R
13)
10-G
ig-E
Module
(VP
E-M
OD
-10G
E-4
P-R
13)
FIL
LE
R
FIL
LE
RBelow are tables to help show the types of cables used and where they are connected.
This section contains cabling connections for the storage head cluster.
SSC 7320 Storage Head Cluster Interconnects
From Port To Port Length Colour Notes
U1 PCIE-1 P0 U2 PCIE-1 P2 7' Yellow 530-4527-01
U1 PCIE-1 P1 U2 PCIE-1 P1 7' Black 530-4436-01
U1 PCIE-1 P2 U2 PCIE-1 P0 7' Green 530-4526-01
U2 PCIE-2 P1 U3 IOM1 (top) SAS Port1 2M Black 2M SAS
U1 PCIE-2 P1 U3 IOM1 SAS Port0 2M Black 2M SAS
U2 PCIE-2 P0 U3 IOM0 (bottom) SAS Port1 2M Black 2M SAS
U1 PCIE-2 P0 U3 IOM0 SAS Port0 2M Black 2M SAS
Oracle Internal and Approved Partners Only Page 35 of 42 Vn 1.0a Created: 28. Aug. 2014
Base Rack NM2/F1-15 Connections:
This section contains in-rack cabling connections for the NM2-36P InfiniBand (IB)
switch to the F1-15 Director switch.
Base Rack In-Rack IB Cable Connections NM2-36P to XSIGOFrom Name Port To Name Port
U19 NM2-36P 9B U22 Xsigo 8 bottom NM2 to top Xsigo - red velcro
U19 NM2-36P 10B U22 Xsigo 9 bottom NM2 to top Xsigo - red
U19 NM2-36P 11B U15 Xsigo 10 bottom NM2 to top Xsigo - red
U19 NM2-36P 9A U15 Xsigo 8 bottom NM2 to bottom Xsigo - red
U19 NM2-36P 10A U15 Xsigo 9 bottom NM2 to bottom Xsigo - red
U19 NM2-36P 11A U22 Xsigo 10 bottom NM2 to bottom Xsigo - red
U20 NM2-36P 9B U15 Xsigo 18 top NM2 to top Xsigo - Blue - velcro
U20 NM2-36P 10B U15 Xsigo 19 top NM2 to top Xsigo - Blue
U20 NM2-36P 11B U22 Xsigo 20 top NM2 to top Xsigo - Blue
U20 NM2-36P 9A U22 Xsigo 18 top NM2 to bottom Xsigo - Blue
U20 NM2-36P 10A U22 Xsigo 19 top NM2 to bottom Xsigo - Blue
U20 NM2-36P 11A U15 Xsigo 20 top NM2 to bottom Xsigo - Blue
Base Rack Server IB to NM2 Connections:
The following table contains cabling connections for the NM2-36P (U19 and U20)
InfiniBand switch to X4-2 compute nodes.
Compute Rack In-Rack IB Cable Connections NM2-36P to ServersFrom Name Port To Name Port
U19 NM2-36P 0A U42 X4-2 PCI-E 2 P2
U19 NM2-36P 0B U41 X4-2 PCI-E 2 P2
U19 NM2-36P 1A U40 X4-2 PCI-E 2 P2
U19 NM2-36P 1B U39 X4-2 PCI-E 2 P2
U19 NM2-36P 2A U38 X4-2 PCI-E 2 P2
U19 NM2-36P 2B U37 X4-2 PCI-E 2 P2
U19 NM2-36P 3A U36 X4-2 PCI-E 2 P2
U19 NM2-36P 3B U35 X4-2 PCI-E 2 P2
U19 NM2-36P 4A U34 X4-2 PCI-E 2 P2
U19 NM2-36P 4B U33 X4-2 PCI-E 2 P2
U19 NM2-36P 5A U32 X4-2 PCI-E 2 P2
U19 NM2-36P 5B U31 X4-2 PCI-E 2 P2
U19 NM2-36P 6A U30 X4-2 PCI-E 2 P2
U19 NM2-36P 6B U29 X4-2 PCI-E 2 P2
U19 NM2-36P 7A U28 X4-2 PCI-E 2 P1
U19 NM2-36P 7B U27 X4-2 PCI-E 2 P1
U19 NM2-36P 8A U26 X4-2 PCI-E 2 P1
U19 NM2-36P 12A U14 X4-2 PCI-E 2 P1
U19 NM2-36P 12B U13 X4-2 PCI-E 2 P1
U19 NM2-36P 13A U12 X4-2 PCI-E 2 P1
U19 NM2-36P 13B U11 X4-2 PCI-E 2 P1
U19 NM2-36P 14A U10 X4-2 PCI-E 2 P1
U19 NM2-36P 14B U9 X4-2 PCI-E 2 P1
U19 NM2-36P 15A U8 X4-2 PCI-E 2 P1
U19 NM2-36P 15B U7 X4-2 PCI-E 2 P1
U19 NM2-36P 16A U6 X4-2 PCI-E 2 P1
U19 NM2-36P 16B U5 X4-2 PCI-E 2 P1
U19 NM2-36P 17A U2 X4-2 PCI-E 0 P1
U19 NM2-36P 17B U1 X4-2 PCI-E 0 P1
U20 NM2-36P 0A U42 X4-2 PCI-E 2 P1
U20 NM2-36P 0B U41 X4-2 PCI-E 2 P1
Oracle Internal and Approved Partners Only Page 36 of 42 Vn 1.0a Created: 28. Aug. 2014
Compute Rack In-Rack IB Cable Connections NM2-36P to ServersFrom Name Port To Name Port
U20 NM2-36P 1A U40 X4-2 PCI-E 2 P1
U20 NM2-36P 1B U39 X4-2 PCI-E 2 P1
U20 NM2-36P 2A U38 X4-2 PCI-E 2 P1
U20 NM2-36P 2B U37 X4-2 PCI-E 2 P1
U20 NM2-36P 3A U36 X4-2 PCI-E 2 P1
U20 NM2-36P 3B U35 X4-2 PCI-E 2 P1
U20 NM2-36P 4A U34 X4-2 PCI-E 2 P1
U20 NM2-36P 4B U33 X4-2 PCI-E 2 P1
U20 NM2-36P 5A U32 X4-2 PCI-E 2 P1
U20 NM2-36P 5B U31 X4-2 PCI-E 2 P1
U20 NM2-36P 6A U30 X4-2 PCI-E 2 P1
U20 NM2-36P 6B U29 X4-2 PCI-E 2 P1
U20 NM2-36P 7A U28 X4-2 PCI-E 2 P2
U20 NM2-36P 7B U27 X4-2 PCI-E 2 P2
U20 NM2-36P 8A U26 X4-2 PCI-E 2 P2
U20 NM2-36P 12A U14 X4-2 PCI-E 2 P2
U20 NM2-36P 12B U13 X4-2 PCI-E 2 P2
U20 NM2-36P 13A U12 X4-2 PCI-E 2 P2
U20 NM2-36P 13B U11 X4-2 PCI-E 2 P2
U20 NM2-36P 14A U10 X4-2 PCI-E 2 P2
U20 NM2-36P 14B U9 X4-2 PCI-E 2 P2
U20 NM2-36P 15A U8 X4-2 PCI-E 2 P2
U20 NM2-36P 15B U7 X4-2 PCI-E 2 P2
U20 NM2-36P 16A U6 X4-2 PCI-E 2 P2
U20 NM2-36P 16B U5 X4-2 PCI-E 2 P2
U20 NM2-36P 17A U2 X4-2 PCI-E 0 P2
U20 NM2-36P 17B U1 X4-2 PCI-E 0 P2
Oracle Internal and Approved Partners Only Page 37 of 42 Vn 1.0a Created: 28. Aug. 2014
This section contains cabling connections for Oracle Switch ES1-24.
Base Rack CAT6 OPUS Connections (Net-0, Other)
From Port To New Ports Color Notes
U42 Net-0 U21-A 19 Blue
U41 Net-0 U21-A 18 Blue
U40 Net-0 U21-A 17 Blue
U39 Net-0 U21-A 16 Blue
U38 Net-0 U21-A 15 Blue
U37 Net-0 U21-A 14 Blue
U36 Net-0 U21-A 13 Blue
U35 Net-0 U21-A 12 Blue
U34 Net-0 U21-A 11 Blue
U33 Net-0 U21-B 18 Blue
U32 Net-0 U21-B 17 Blue
U31 Net-0 U21-B 16 Blue
U30 Net-0 U21-B 15 Blue
U29 Net-0 U21-B 14 Blue
U28 Net-0 U21-B 13 Blue
U27 Net-0 U21-B 12 Blue
U26 Net-0 U21-B 11 Blue
U22 U21-A 9 Black Xsigo
U20 U21-B 10 Black NM2-36P
U21-A 24 Customer Network TransceiverBlue Cable
U21-B 24 Customer Network TransceiverBlue Cable
U21-A 22 U21-B 22 SFP+ Switch to Switchconnection within rack
U19 U21-A 10 Black NM2-36P
U15 U21-B 9 Black Xsigo
U14 Net-0 U21-A 8 Blue
U13 Net-0 U21-A 7 Blue
U12 Net-0 U21-A 6 Blue
U11 Net-0 U21-A 5 Blue
U10 Net-0 U21-A 4 Blue
U9 Net-0 U21-A 3 Blue
U8 Net-0 U21-A 2 Blue
U7 Net-0 U21-A 1 Blue
U6 Net-0 U21-B 8 Blue
U5 Net-0 U21-B 7 Blue
U2 Net-2 U21-B 6 Blue
U2 Net-1 U21-B 5 Blue
U2 Net-0 U21-B 4 Blue
U1 Net-2 U21-B 3 Blue
U1 Net-1 U21-B 2 Blue
U1 Net-0 U21-B (Left switch) 1 Blue
PDU-A Net Mgt U21-A 20 White PDU-A
PDU-B Net Mgt U21-B 20 White PDU-B
Oracle Internal and Approved Partners Only Page 38 of 42 Vn 1.0a Created: 28. Aug. 2014
APPENDIX B: Oracle Virtual Compute Appliance Dashboard
Task Comment Check
ORACLE VIRTUAL COMPUTE APPLIANCE DASHBOARD
The Oracle Virtual Compute Appliance
X4-2 provides its own web-based
graphical user interface that can be used
to perform a variety of administrative
tasks specific to the appliance.
The Oracle Virtual Compute Appliance Dashboard is a Weblogic application that is available via the active management node. It is installed on top of the Oracle WebLogic Server 11g that is packaged with Oracle VM Manager, as described in
Section 1.3.3 Oracle VM
Manager.
Use the Dashboard to perform the
following tasks:
Appliance system monitoring and component identification.
Monitoring and identifying physical network connections.
Initial configuration of management node networking data.
Resetting of the global password for Oracle Virtual Compute Appliance components.
Updating Oracle Virtual Compute Appliance software.
Monitoring and configuring Oracle Virtual Compute Appliance backup.
The Oracle Virtual Compute Appliance
Dashboard should be used immediately
after installation to perform a software
update and to configure the management
node networking data.
The Oracle Virtual Compute Appliance Dashboard is described in detail in Chapter 2: Monitoring and Managing Oracle Virtual Compute Appliance X4-2.
Use the Oracle Virtual Compute
Appliance Dashboard to perform regular
appliance maintenance such as password
resets or hardware monitoring.
Refer to Section 2.1 Connecting and Logging in to the OVCA Dashboard.
To open the Login page of the Oracle
Virtual Compute Appliance Dashboard,
enter the following address in a Web
browser:
https://:7002/ovca
Where refers to the shared Virtual IP address that you have configured for your management nodes during installation. By using the shared Virtual IP address you ensure that you always access the Oracle VM Manager Web UI on the active management node.
Important: You must ensure that if you are accessing Oracle Virtual
Compute Appliance Dashboard through a firewalled connection, that the
firewall is configured to allow TCP traffic on the port that Oracle Virtual
Compute Appliance Dashboard is using to listen for connections.
Enter your Oracle Virtual Compute
Appliance Dashboard administration
username and password in the
appropriate fields.
This is the administration username you configured during installation.
Oracle Internal and Approved Partners Only Page 39 of 42 Vn 1.0a Created: 28. Aug. 2014
Task Comment Check
Important: The Oracle Virtual Compute Appliance Dashboard makes use of
cookies in order to store session data. Therefore, to successfully login and
use the Oracle Virtual Compute Appliance Dashboard your web browser
must accept cookies from the Oracle Virtual Compute Appliance Dashboard
host.
Task Comment Check
TABLE OF HARDWARE STATUS ICONSThe Hardware View within the OVCA
Dashboard provides a graphical
representation of the hardware
components as they are installed within
the OVCA rack.
Rolling over each item with a mouse raises a popup window providing the name of the component and its type.
Alongside each installed component
within the OVCA rack, a status icon
provides an indication of the health and
running status of the component.
The table below describes the different status icons and their meaning.
Icon Status Description
OK The component is running correctly and has passed all health check operations.
Warning The component is running, but has not passed all health check operations and investigation may be required.
Error The component is not running and has failed health check operations.Component troubleshooting is required and the component may need to be replaced.
Oracle Internal and Approved Partners Only Page 40 of 42 Vn 1.0a Created: 28. Aug. 2014
Task Comment Check
HARDWARE VIEW
The Hardware View provides an
accessible tool for troubleshooting
hardware components within OVCA and
identifying where these components are
actually located within the rack.
Where components might need replacing, the new component must take the positionof the old component within the rack to maintain configuration.
Any Warning or Error indicators must be
investigated for the cause of the issue.
The example below shows compute node ovcacn07r1 with yellow LED
because its only 30% complete with provisioning.
Be aware that as of the writing of this
checklist the dashboard only reports if
the node is known to the management
nodes as a provisioned node.
The node could be powered off and you will still see a green indicator. In other words the dashboard is basically reportingon software, not hardware.
Oracle Internal and Approved Partners Only Page 41 of 42 Vn 1.0a Created: 28. Aug. 2014
APPENDIX C: Table References for Logins, Passwords, and Hostnames in
OVCA X4-2
Account Username Password
ILOM root Welcome1
NM2 root Welcome1
NM2 ilom-admin Welcome1
NM2 ilom-operator Welcome1
OPUS 24 switch none Welcome1
Hosts root Welcome1
Xsigo Admin on IO director admin Welcome1
Xsigo IO director system root root Welcome1
Xsigo password recovery none Welcome1
Rack Unit # Component Hostname SP Hostname
22 F1-15 Xsigo Switch ovcasw22r1 ILOM-ovcasw22r1
21 OPUS Switch A | B
20 NM2-36P IB Switch ovcasw20r1 ILOM-ovcasw20r1
19 NM2-36P IB Switch ovcasw19r1 ILOM-ovcasw19r1
15 F1-15 Xsigo Switch ovcasw15r1 ILOM-ovcasw15r1
14 Compute node
6 Management node ovcamn06r1 ILOM-ovcamn06r1
5 Management node ovcamn05r1 ILOM-ovcamn05r1
2 ZFS-appliance head ovcasn02r1 ILOM-ovcasn02r1
1 ZFS-appliance head ovcasn01r1 ILOM-ovcasn01r1
PDU-A -PDUA
PDU-B -PDUB
Copies of the checklists are available on the EIS web pages or on the EIS-DVD. We recommend that you always check the web pages for the latest version.
Comments & RFEs welcome. Oracle staff should mail to [email protected] .Partners should mail to: [email protected] .
Oracle Internal and Approved Partners Only Page 42 of 42 Vn 1.0a Created: 28. Aug. 2014