Configure the appliance

After you install the appliance image, you must accept the End User License Agreement (EULA), and enable or disable authorized support access (optional). Next, change the default administrator password for the appliance and configure the network connections. When you configure the network connections on the appliance using a REST API POST operation that includes all of the networking settings, the appliance starts. You can now import enclosures and start managing your data center environment.

To monitor and verify successful appliance configuration, you use the task API. Reference the TaskResource URI that is returned after you post the network configuration using the network-interfaces REST API.

Use REST APIs to ...

For information about the appliance resource, see the HPE OneView REST API Reference.

Accept the End User License Agreement (EULA)

Before you log in to the appliance for the first time, you must accept the EULA. During this step you can enable or disable authorized support access. Support access is enabled by default.

After the appliance is configured, you can use this REST API to enable or disable authorized support access.

Accepting the End User License Agreement (EULA) using REST APIs
`POST /rest/appliance/eula/save`

Change the default administrator password

The first time you log in to the appliance, you must change the default administrator password. Log in using the default administrator password, and then use the returned session ID to change the password.

Prerequisites

Default administrator password

Changing the default administrator password using REST APIs
Log in to the appliance using the default administrator password. `userName`: `Administrator` `password`: `admin` `POST /rest/login-sessions` Change the default administrator password. `POST /rest/users/changePassword`

Configure the network

Log in to the appliance as an administrator and create a REST request that includes the network information provided by your network administrator. After you POST the network configuration using the /rest/appliance/network-interfaces API, a TaskResource URI is returned in the Location header. Use the TaskResource URI to track the progress. When the network configuration is complete, the appliance starts.

You can also configure both the network as well as time and place settings using the /rest/appliance/network-interfaces API. You can change these settings together or separately using the /rest/appliance/network-interfaces API. The time and language settings include the NTP server settings.

Best practices

Always use static IP addresses when configuring the appliance. Use of DHCP addresses is not recommended unless the DHCP server is configured so that the same addresses are always assigned to the appliance. Use of randomly assigned DHCP addresses is not supported and will result in connectivity issues when the DHCP server changes the address assigned to the appliance.

Prerequisites

Minimum required session ID privileges: Infrastructure administrator
A virtual appliance connected to the network
Network information provided by your Network administrator, such as the IP address and host name for the appliance, DNS name servers, subnet, and gateway.

Configuring the network using REST APIs
`POST /rest/appliance/network-interfaces`


	NOTE: If you are setting up multiple network interfaces, provide the network interfaces information for all networks in the REST API `POST` operation.

Change to a dual-stack protocol

To change the appliance from an IPv4 protocol to dual-stack (to run both IPv4 and IPv6 protocols), update the appliance network setting.

Prerequisites

Minimum required session ID privileges: Infrastructure administrator
A virtual appliance connected to the network

Changing to a dual-stack protocol using REST APIs
Get the network settings. `GET /rest/appliance/network-interfaces` Change the `ipv6Type` attribute to `DHCP`. Update the network settings. `POST /rest/appliance/network-interfaces`

Update the SNMP read community string

The SNMP read community string is used by the appliance to communicate with the managed devices.

If you use the REST APIs to update the SNMP read community string for an appliance that has managed devices, you must also refresh the managed devices.

Prerequisites

Minimum required session ID privileges: Infrastructure administrator

Updating the SNMP read community string using REST APIs
Get the read community string. `GET /rest/appliance/device-read-community-string` Edit the `communityString` attribute. Update the SNMP read community string. `POST /rest/appliance/device-read-community-string`

Refreshing the connections between the enclosures and the appliance
Get a list of the enclosure IDs. `GET /rest/enclosures` For each enclosure ID, refresh the connection between the enclosure and the appliance.

Refreshing the connections between the rack mount servers and the appliance
Get a list of the rack mount server IDs. `GET /rest/server-hardware?filter="position=0"` For each rack mount server ID, refresh the connection between the server and the appliance.

See also

Quick Start: Initial configuration using REST APIs (top of chapter)

prev	up	next
Backup the appliance	home	Create a certificate signing request