|
|
|
|
Unique prefix for MiniCluster
|
System-level host name prefix to be used for your
MiniCluster. Specify up to 6 characters or fewer. For
example: mc2.
The host name prefix and domain name entries are used when host names are generated for components in the system, such as mc2-n1.us.example.com for the host name for the first compute node.
|
|
|
Netmask in CIDR form
|
Subnet mask for the client access network in CIDR
form. For example, 23.
|
|
|
First IP address (range 1)
|
Starting IP address for the IP addresses assigned to the client access network..
|
|
|
Count of IP addresses (range 1)
|
Total number of IP addresses that you need for the
client access network. This number represents the number
of consecutive IP addresses that will be available for
the client access network when creating database or
application virtual machine groups, beginning with the
starting IP address you entered above.
|
|
|
Starting IP address and pool size (additional
ranges)
|
(Optional) If you want additional separate sets of IP
addresses, provide the starting IP addresses and pool
sizes for those additional IP address sets.
|
|
|
Default gateway address
|
Gateway IP address for the client access network. For example,.
|
|
|
Domain name
|
Domain name for your company. The name can contain alphanumeric characters, periods (.), and hyphens (-). The name must start with an alphanumeric character. This field cannot be empty. For example, us.example.com.
The host name prefix and domain name entries are used when host names are generated for components in the system, such as mc2-n1.us.example.com for the host name for the first compute node.
|
|
|
DNS servers
|
IP address for the domain name servers. At least one
IP address must be provided in the first DNS server
location.
|
|
|
NTP servers
|
IP address for the Network Time Protocol servers. At
least one IP address must be provided in the first NTP
server location.
|
|
|
[ILOM] Netmask in CIDR form
|
Subnet mask for the management network in CIDR form.
For example, 24.
|
|
|
[ILOM] IP address of first compute node
|
ILOM IP address of the first compute node.
|
|
|
[ILOM] IP address of second compute node
|
ILOM IP address of the second compute node.
|
|
|
[ILOM] Default gateway address
|
Gateway IP address for the management network.
|
|
|
[ILOM] DNS servers
|
IP address for the domain name servers for the
management network. At least one IP address must be
provided in the first DNS server location.
|
|
|
[ILOM] NTP servers
|
IP address for the Network Time Protocol servers for
the management network. At least one IP address must be
provided in the first NTP server location.
|
|
|
Type of cable to be used to connect to client access
network.
|
|
|
|
Client access network high availability type
|
Method that you want to use to make the client access
network highly available. Options are IPMP (IP network
multipathing) or AGGR (data link aggregation).
|
|
|
Location 1
|
First level of time zone information. For example,
America.
|
|
|
Location 2
|
Second level of time zone information. For example,
Los Angeles.
|
|
|
PCI DSS Compliance
|
Allows you to enable Payment Card Industry Data
Security Standard (PCI DSS) compliance, if necessary.
Options are Yes or No.
|
|
|
Security Keystore Type
|
Functions that are used in the Oracle Solaris
cryptographic framework. Default choice: pkcs11.
|
pkcs11
|
|
VLAN ID information (optional)
|
If you want to set up a tagged VLAN configuration on
the client access network, enter the VLAN tag ID.
|
|
|
Port VLAN information (optional)
|
If you want to set up an untagged (port-based) VLAN
configuration on the client access network, enter the
port VLAN ID.
|
|
|
[ILOM] VLAN ID information (optional)
|
If you want to set up a tagged VLAN configuration on
the management network, enter the VLAN tag ID.
|
|
|
[ILOM] Port VLAN information (optional)
|
If you want to set up an untagged (port-based) VLAN
configuration on the management network, enter the port
VLAN ID.
|
|