Comment on page
The appliance service account
The TrilioVault Appliance is providing an account that allows doing the following through the console:
- Change network interface configuration
- Show logs on the TrilioVault Appliance
- Restart TrilioVault services on the TrilioVault Appliance
The following default credentials allow the usage of the service account:
- username: rhv_nw
- password: OphaeHaet0
The rhv_nw user is capable of editing the network configuration files and restarting the interface service.
The network interface files are located under:
/etc/sysconfig/network-scripts/
Use the vi editor to configure the network interface. TrilioVault's default interface is eth0, which is using the following file for its configuration:
ifcfg-eth0
Edit this file according to the attached network. A typical interface configuration looks as follows
BOOTPROTO=static
DEVICE=eth0
HWADDR=52:54:00:90:cc:a1
IPADDR=192.168.1.10
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
DNS1=192.168.1.1
DNS2=8.8.8.8
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
A warning will appear that a read-only file is edited. This warning needs to be overwritten using
wq!
Restarting the network interface through ssh will lead to a network disconnect and might end in the TrilioVault appliance becoming inaccessible.
Only restart network interfaces, when there are means available to reconnect to the Appliance, even when the interface stays down.
To restart the network interfaces the rhv_nw user is capable of using the ifdown and ifup commands.
Below examples are shown for the default interface eth0.
ifdown eth0
ifup eth0
Using these two commands will reread the network configuration and apply any changes to the interface.
The rhv_nw user does have full read permissions on all TrilioVault Appliance log files located in
/var/log
The rhv_nw user does have the permission to start, stop and restart the workloadmgr services running on top of the TrilioVault appliance.
The following services can be controlled through the service account:
- wlm-api
- wlm-scheduler
- wlm-workloads
Use the systemctl commands as shown in the following examples for the wlm-api.
systemctl stop wlm-api
systemctl start wlm-api
systemctl restart wlm-api