Version 1.0.5.0 release notes (January 2018)

The Version 1.0.5.0 release introduces a number of new improvements to service requests, offline backups, and firmware upgrades.

What's new

Administering

Service request status is now displayed as SR Status when running the ap issues alert_id command.
You can now manually open a service request for selected alerts by running:
```
ap issues --open_service_request alert_id [alert_id ...]
```
Incremental restores can now be performed from both the command line and the console.
Offline backups and restore scripts stop and start HA and DSM connections automatically. There is no longer a need to run db_stopsrc and db_startsrc commands separately.
A system health check is now performed before each backup and restore.
For systems with Call Home enabled, you can now open service requests on any alert directly from the IAS console by using the new Create Service Request button on the Monitor > System > Notifications screen.
A Test connection button has been added to the web console Call Home configuration panels to assist in configuration and verification of network connectivity to these IBM services.
A feature which approximates the time taken by apdiag and aphealth utilities has been added.

Upgrading

Firmware upgrades for the terminal server (ts), fabric switch (fabsw), and power distribution units (rpc) are now automated through the apupgrade command.
A status report is now generated after an upgrade.

After a node reboot, Platform Manager might not have started the node's application container due to an issue in the startup policy.
An unreachable node could be disabled when the docker service starts to fail too quickly.

When running sys_hw_check, the configuration reports as FAIL. You need to manually reconfigure the fiber channel switch (SAN switch) by using the PFS tool.