2 Prepare Installation Site
It is important that you plan ahead for the installation of your Oracle Private Cloud Appliance. This ensures a fluent end-to-end process with minimal risk of unplanned interruptions or delays in system initialization. Preparations include making sure that the installation site meets all installation requirements, collecting all the required configuration parameters for the data center infrastructure as well as the appliance, completing the applicable checklists, and so on.
Review Safety Guidelines
Before your Oracle Private Cloud Appliance arrives, review the following safety precautions to ensure that the site is safe, as well as ready for delivery. Failure to observe these precautions can result in personal injury, equipment damage, or malfunction.
-
Do not block ventilation openings.
-
Do not install the system in a location that is exposed to direct sunlight or near a device that may become hot.
-
Do not install the system in a location that is exposed to excessive dust, corrosive gases, or air with high salt concentrations.
-
Do not install the system in a location that is exposed to frequent vibrations. Install the system on a flat, level surface.
-
Use a power outlet that uses proper grounding. When using shared grounding, the grounding resistance must not be greater than 10 ohms. Ensure that your facility administrator or a qualified electrical engineer verifies the grounding method for the building, and performs the grounding work.
-
Ensure that each grounding wire used for the system is used exclusively for the Oracle Private Cloud Appliance. Also observe the precautions, warnings, and notes about handling that appear on labels on the equipment.
-
Do not place cables under the equipment or stretch the cables too tightly.
-
Do not disconnect power cords from the equipment while its power is on.
-
Do not place anything on top of the system or perform any work directly above it.
-
If you cannot reach the connector lock when disconnecting LAN cables, then press the connector lock with a flathead screwdriver to disconnect the cable. You could damage the system board if you force your fingers into the gap rather than using a flathead screwdriver.
-
Do not let the room temperature rise sharply, especially in winter. Sudden temperature changes can cause condensation to form inside the system. Allow for a sufficient warm-up period prior to server operation.
-
Do not install the system near a photocopy machine, air conditioner, welding machine, or any other equipment that generates loud, electronic noises.
-
Avoid static electricity at the installation location. Static electricity transferred to the system can cause malfunctions. Static electricity is often generated on carpets.
-
Confirm that the supply voltage and frequency match the electrical ratings indicated on your Oracle Private Cloud Appliance.
-
Do not insert anything into any Oracle Private Cloud Appliance opening, unless doing so is part of a documented procedure. The system contains high-voltage parts. If a metal object or other electrically conductive object enters an opening in the system, then it could cause a short circuit. This could result in personal injury, fire, electric shock, and equipment damage.
See also:
-
Important Safety Information for Sun Hardware Systems (816-7190) included with the rack
-
Oracle Rack Cabinet 1242 Power Distribution Units User's Guide
-
Oracle Engineered System Safety and Compliance Guide (non-Nordic)
-
Oracle Engineered System Safety and Compliance Guide (Nordic)
Verify Installation Requirements
The Oracle Private Cloud Appliance Installation Guide specifies in detail which requirements the installation site must meet. Checklists allow you to register the requirements you have verified and the potential adjustments needed before the installation can take place. The table guides you through the verification steps by providing links to the relevant resources.
Item | Description | Resources |
---|---|---|
Logistic requirements |
Review the safety guidelines. Confirm that the working environment is safe and secure at all times. Verify that sufficient space is available for receiving, unpacking and installing the appliance. Consider the dimensions of the product and its packaging, the delivery location, the access route to the data center room, and maintenance access to the rack after installation. Make sure that the required personnel is on-site, that arrangements have been made for access to the building, and that any required equipment and tools are available. |
|
Data center environment requirements |
Verify that the data center flooring is adequate and that sufficient ventilation and cooling capacity is provided. Make sure that temperature and humidity levels are maintained within in the optimum range. |
|
Electrical power requirements |
Ensure that power is provided reliably, protecting your systems from electrical disturbances. Verify that the appliance power distribution units correspond with the facility power supply. Verify that the correct circuit breakers and uninterruptable power supply are provided, and that grounding guidelines are followed. |
|
Network infrastructure requirements |
The appliance connects to the data center network using high-speed Ethernet cabling. Choose the appropriate number of uplinks, cabling topology and routing design that are suitable for your operational requirements and data center infrastructure. Ensure that the required switches, ports, transceivers and cables are available. Verify that subnet configurations and IP address reservations have been made, and that the data center network configuration does not conflict with the appliance's reserved network resources. To ensure that these requirements are met, and that the appliance is integrated successfully into your data center infrastructure, complete the initial installation checklist. |
Complete Integration Checklist
This section contains a checklist to help you plan for the initial installation wizard, which walks you through first boot on your Oracle Private Cloud Appliance. Work with your network and site administrators to plan the integration of the appliance into your data center. For initial configuration you can choose either a dynamic network or static network configuration. This checklist contains information for both options, but you only need data for the implementation you choose.
Items noted in the table with an asterisk (*) are required fields for all configurations. Fields marked with a (†) are required for static network configuration, and fields marked with a (‡) are required for dynamic network configuration.
Item | Your Configuration | Description and Example |
---|---|---|
Administrator user name and password |
The appliance does not ship with a default administrative user account. You create an administrator account during the initial installation. User names and passwords have a maximum length of 100 characters. Passwords must contain at least 12 characters with at least one of each: uppercase character, lowercase character, digit, and any punctuation character (expect for double quote ('"') characters, which are not allowed). |
|
Appliance Details |
||
Availability Domain* |
|
Your on site Oracle Private Cloud Appliance is considered an
availability domain and is assigned the value |
System Name* |
Name for your Oracle Private Cloud Appliance that will also be used as the Realm. This attribute has a maximum length of 24 characters. Acceptable characters are "a"→"z", "A"→"Z", "0"→"9", and "-". Once set this parameter cannot be changed. |
|
Domain* |
Domain name for your system which is used as the base domain for the internal network, and by Oracle Private Cloud Appliance public facing services. This attribute has a maximum length of 190 characters. Acceptable characters are "a"→"z", "A"→"Z", "0"→"9", "-" Example: us.example.com Once set this parameter cannot be changed. |
|
Rack Name |
Identify the appliance type, for example |
|
Description |
Free text field with a 256 character limit to optionally provide a description of your appliance. |
|
Static Routing Network Details | ||
Routing Type* |
Choose static or dynamic routing based on your network topology. |
|
Uplink Gateway† |
IP address for the uplink switch to the default gateway in your data center. Chose a valid IP address in customer data center subnet that the Oracle Private Cloud Appliance uplink switches are attached to. Example: 10.68.48.86 |
|
Spine switch virtual IP† |
Virtual IP address which acts as the public VIP for the spine switches in your company network. Chose a valid IP address in the data center subnet that the Oracle Private Cloud Appliance uplink switches are attached to. Example: 10.68.49.103 |
|
Uplink VLAN |
VLAN used to connect to an uplink switch. Chose a VLAN value between 2 and 3899. VLANs 3900 to 4095 are reserved. Example: 322 |
|
Uplink HSRP Group |
Assign an HSRP group number to your appliance. Acceptable values are 0 to 255, and the default value is 151. If there are multiple Oracle Private Cloud Appliance racks connected to the same data center infrastructure switches, ensure they use different HSRP groups. |
|
Management node 1 IP addresses and host name* |
10/25/40/100G*: 1G: host name: |
Static IP addresses for management node 1 in your company network. Provide a valid host name. An appended domain name is used if you don't provide a host name. |
Management node 2 IP addresses and host name* |
10/25/40/100G*: 1G: host name: |
Static IP addresses for management node 2 in your company network. Provide a valid host name. An appended domain name is used if you don't provide a host name. |
Management node 3 IP addresses and host name* |
10/25/40/100G*: 1G: host name: |
Static IP addresses for management node 3 in your company network. Provide a valid host name. An appended domain name is used if you don't provide a host name. |
Management virtual IP address and host name* |
10/25/40/100G*: 1G: host name*: |
Virtual IP addresses of the management node cluster in your company network. This is the IP used to DNAT to the internal management node VIP. Oracle Private Cloud Appliance DNS will resolve Oracle Private Cloud Appliance endpoints to this IP. Chose a valid IP address in the data center CIDR. Example: 10.68.49.170 Provide a valid host name. An appended domain name is used if you don't provide a host name. |
Spine switch 1 IP address* |
IP address for the spine switch 1 in your company network. Chose a valid IP address in the data center subnet that the Oracle Private Cloud Appliance uplink switches are attached to. Example: 10.68.49.101 |
|
Spine switch 2 IP address* |
IP address for the spine switch 2 in your company network. Chose a valid IP address in the data center subnet that the Oracle Private Cloud Appliance uplink switches are attached to. Example: 10.68.49.102 |
|
Dynamic Routing Network Details | ||
Peer 1 IP‡ |
Neighbor BGP IP - IP address of customer datacenter router-1 that the Oracle Private Cloud Appliance uplink switches are attached to. Example: 10.68.48.86 |
|
Peer 1 ASN‡ |
BGP ASN of customer datacenter router-1. Example: 64512-65533 or 4200000000-4294967294 (Note: Oracle Spine switch default ASN is 136025.) |
|
Peer 2 IP‡ |
Neighbor BGP IP - IP address of customer datacenter router-2 that the Oracle Private Cloud Appliance uplink switches are attached to. Example: 10.68.48.88 |
|
Peer 2 ASN‡ |
BGP ASN of customer datacenter router-2 Example: 64512-65533 or 4200000000-4294967294 (Note: Oracle Spine switch default ASN is 136025.) |
|
Uplink Gateway* |
IP address for the uplink switch to the default gateway in your data center. Chose a valid IP address in customer data center subnet that the Oracle Private Cloud Appliance uplink switches are attached to. Example: 10.68.48.86 |
|
Oracle ASN |
The default is 136025. |
|
BGP Topology |
Options are triangle, square, or mesh. The default is mesh. |
|
BGP Authentication |
Enter the BGP credentials for your network. |
|
BGP Password |
Enter the BGP password for your network. |
|
BGP KeepAlive Timer |
The default is 60. |
|
BGP Holddown Timer |
The default is 180. |
|
Enable MDA Authentication |
The default is false. |
|
Uplink Details |
||
Uplink Port Speed* |
All uplink ports must have the identical speed. The options are 10, 25, 40, 100. The default is 100. |
|
Uplink Port Count* |
The number of uplink ports per spine switch. Connectivity must be identical on both spine switches to provide redundancy and load-splitting. For 100G and 40G speeds, valid values are 1, 2 and 4. For 10G and 25G ports, valid values are 1, 2, 4, 8 and 16. The default for both is 4. |
|
Uplink VLAN MTU* |
MTU size determines the maximum packet size that can be transmitted over your uplink connection. The valid range is 68 to 9216. The default is 9216. |
|
Uplink Netmask* |
Netmask of the subnet Oracle Private Cloud Appliance is connected to in your data center. Example: 255.255.252.0 |
|
Uplink Port FEC |
Configure Forward Error Correct (FEC) for the uplink port. The default option is auto, with on and off as other valid options. |
|
NTP Server Details |
||
NTP servers* |
At least one valid IP address for an NTP server in your data center. You can enter multiple IP addresses in a comma-separated list. Example: 10.147.24.1,10.211.17.1 |
|
Optional Administration Network Details |
||
Admin Networking |
Enable or disable a separate Administration network to transport administrative traffic. |
|
Management virtual IP address and host name |
10/25/40/100G: 1G: host name: |
Virtual IP address of the management node cluster in the administration network. This is the IP used to DNAT to the internal management node VIP. Oracle Private Cloud Appliance DNS will resolve Oracle Private Cloud Appliance endpoints to this IP. Chose a valid IP address in the administration network CIDR. Example: 10.168.141.170 Provide a valid host name. An appended domain name is used if you don't provide a host name. |
Management node 1 IP addresses and host name |
10/25/40/100G: 1G: host name: |
Static IP addresses for management node 1 in the administration network. Provide a valid host name. An appended domain name is used if you don't provide a host name. |
Management node 2 IP addresses and host name |
10/25/40/100G: 1G: host name: |
Static IP addresses for management node 2 in the administration network. Provide a valid host name. An appended domain name is used if you don't provide a host name. |
Management node 3 IP addresses and host name |
10/25/40/100G: 1G: host name: |
Static IP addresses for management node 3 in the administration network. Provide a valid host name. An appended domain name is used if you don't provide a host name. |
Admin DNS servers |
IP addresses for 1-3 DNS servers providing name resolution in the administration network. Example: 10.168.20.31,10.168.20.32,10.147.36.60 |
|
Admin Port Speed |
Port speed options are 10, 25, 40, 100. The port speed of your administration port can be different from the data port speed. |
|
Admin Port Count |
For 100G and 40G speeds, valid value is 1. For 10G and 25G ports, valid values are 1 to 4. |
|
Admin HSRP Group |
Assign an HSRP group number to your Administration network. Acceptable values are 0 to 255, and the default value is 152. If there are multiple Oracle Private Cloud Appliance racks connected to the same data center infrastructure switches, ensure they use different HSRP groups. |
|
Admin VLAN |
VLAN used to connect to the Administration network (only access mode supported). The valid range for users to select is 2 to 3899. The default is 3915, in the Oracle-reserved range. |
|
Admin VLAN MTU |
MTU size determines the maximum packet size that can be transmitted over your administration connection. The valid range is 68 to 9216. The default is 9216. |
|
Admin Port FEC |
Configure Forward Error Correct (FEC) for the administration port. The default option is auto, with on and off as other valid options. |
|
Admin Gateway IP |
IP address of the default gateway in your Administration network. Example: 10.168.141.1 |
|
Admin Netmask |
Netmask of the subnet the Administration network is connected to. |
|
Admin CIDR |
CIDR range for which the default route is the Administration gateway IP. |
|
Admin Spine 1 IP |
Public IP address of spine switch 1. Needed for HSRP configuration or the spine virtual IP. |
|
Admin Spine 2 IP |
Public IP address of spine switch 2. Needed for HSRP configuration or the spine virtual IP. |
|
Admin Spine VIP |
Public virtual IP of the spine switches. |
|
DNS Server Details |
||
DNS server 1 |
IP address for primary DNS server. Example: 10.68.50.60 |
|
DNS server 2 |
IP address for secondary DNS server. Example: 10.147.36.60 |
|
DNS server 3 |
IP address for tertiary DNS server. Example: 206.233.27.1 |
|
Appliance Public IP Addresses |
||
Public IP Addresses |
A range of customer data center IP addresses can be used for Oracle Private Cloud Appliance components that require public IP addresses. Note: In this context, public IP addresses refer to IP addresses that have access to the data center network from the Oracle Private Cloud Appliancesubnet. You must specify IP addresses or ranges that are routed to the Oracle Private Cloud Appliance from the data center. Route tables must be correct and consistent. Enter a string containing a comma separated list of valid CIDRs. Example: "10.68.49.249","10.68.50.32/32","10.68.51.4/31" Partial CIDR deletion is not supported. |
|
Object Storage IP address |
Valid IP address for an |