Permissions
network:read permits viewing current settings and running health checks. network:manage permits proposing,
confirming, cancelling, and handing an approved change to the host administrator.
Review current settings
Open Administration → Network settings to review:
- hostname and access mode;
- HTTPS and proxy status;
- expected public addresses, when configured;
- the most recent health check; and
- any pending or recently applied change.
The displayed status is operational guidance. Confirm DNS, firewall, proxy, and certificate configuration with the client teams that own them.
Run health checks
Select Run checks after installation and after a DNS, certificate, proxy, or firewall change. Review:
- hostname resolution;
- reachability from the intended network;
- HTTPS certificate validity and hostname match;
- expected-address match where configured; and
- proxy forwarding where applicable.
Do not include private keys, credentials, or configuration exports in troubleshooting evidence.
Access-mode responsibilities
Automatic HTTPS
The hostname must resolve to the OneView server and the required public ports must reach it. The client owns DNS, router, firewall, and public-address configuration.
Client-managed TLS
The client owns certificate issuance, renewal, chain completeness, private-key protection, and secure delivery to the server.
External reverse proxy
The client owns public TLS termination, proxy availability, trusted forwarding, request-size/time-out policy, and the private route from the proxy to OneView.
Evaluation tunnel
Use a temporary tunnel only for approved evaluation. Tunnel hostnames may change and are not a production availability or security design.
Change the hostname or access mode
- Confirm the target DNS, certificate, proxy, and firewall plan.
- Open Network settings and create the proposed change.
- Run the pre-change checks.
- Review and confirm the exact proposal.
- Copy the generated host command.
- Have the authorised host administrator run it without editing it.
- Keep the old address available during the validation window where practical.
- Run checks against the new address and confirm sign-in, license, updates, and a safe synthetic verification.
- Close the change only after the client network owner accepts it.
The browser records and validates the proposal but does not change host deployment settings directly.
Failed or interrupted change
If the host command fails, keep the previous access path available and review the safe failure shown by the command. Do not hand-edit deployment configuration or application data.
If neither address works, use the installed diagnostic report and approved network-recovery procedure for the exact installed version. Preserve the proposed hostname, access mode, time, and safe error code without sharing credentials or certificate private material.