After installing the Web UI, you can browse to server and see the login page below.
The default username and password is -
Username: admin
Password: Password1
Note: The web UI will not attempt a login if the password field contains certain special characters. See password note in user creation section for the list.
Please change the default password after you login. See the Admin User section for details.
Once you login, you will see the landing page -
You will notice a few items on the page header -
The settings tab has all of the user configurable settings.
The general settings has the following configurable options -
Additional local user accounts for the web UI can be added/changed/modified here.
To add a user simply click the "Add" button which will take you to the "Create New User" page -
Note: The password field can not have the following special characters for security purposes -
The backup settings section contains all settings relevant to the backup daemon -
You can configure the following settings -
Note: The username for the F5 login must be an admin account as it needs to be able to create UCS files.
Note: The backup password is encrypted in the database. It is encrypted with a key that Apache does not have access to by standard linux file permissions and SELinux (if enabled).
The admin password can only be changed by the admin user. Like the user passwords, the admin password also can not have certain special characters listed in the previous section.
<nr/>
The status indicator monitors the internal services of the Config Backup program. Clicking the indicator on the top left hand corner will send you to a page with more detail about the nature of the error. There are 3 states the indicator can have -
There are 2 python services that run the config backup utility -
If there is ever a problem with the services and it is reported to the web UI status indicator you can restart these services with the standard Linux service init command running as root or sudo. -
[root@f5backup ~]# service f5backup Usage: service f5backup {start|stop|restart} [root@f5backup ~]# service f5backup restart Shutting Down F5 Backup Program: [ OK ] Starting F5 Backup Program: [ OK ] [root@f5backup ~]# service backupapi restart Shutting Down Backup API: [ OK ] Starting Backup API: [ OK ]
Example running as sudo (for example, appliance users) -
[console@f5backup ~]$ sudo service backupapi restart Shutting Down Backup API: [ OK ] Starting Backup API: [ OK ]
In the devices page, you can see a list of all currently managed devices and download UCS archives. If the device uses the DNS hostname rather than the IP, the IP field will say "N/A".
To add a device, click the "Add" button on the device list page. This will take you to the add device page -
When you adding a device, if you use a DNS record check the box and leave the IP field blank. If you will connect by IP then leave the DNS box unchecked and enter the IP address.
You can remove devices from the device list simply by checking the box next each device on the device list and clicking the delete button. You can select multiple devices at once. Then you will get a confirmation page as such -
Click "Yes" to delete the devices.
To see more detail about a device click on the name of the desired device and you will get a page similar to this-
In the following properties about the device -
Hardware details -
Software Details -
Backup Info -
In the bottom table you will see all of the associated UCS files for the device. Click on any file to download it. The number of backup files retained for devices is controlled by the archive size setting in the backup settings.
The backup jobs tab has a list of backups done by the program. The number of backup jobs retained in this section is determined by the log size setting the backup settings section.
Details of the backup job are available by clicking on any job -
The page will have the following information -
The certificate section has a list of all certs for all active and standalone devices. It does not keep track of certs on standby devices as it would be a duplicate of what is on the active peer. The list is arranged chronologically by expiration date with the following color codes on the date -
Clicking on a cert will provide more detail as in this example of an expired cert -
Below we have an example of a cert about to expire within 30 days.