Verifying the RPM file version on both devices
After a successful F5
®
Herculon
™
SSL Orchestrator
™
HA deployment, verify that the latest version of the
Herculon SSL Orchestrator zip file is installed on both devices.
1.
On the Main tab, click
SSL Orchestrator
>
Updates
.
The Updates screen opens.
2.
Check the RPM versions in the
Version
field.
If the versions are not identical, you must install an updated RPM file and verify that both devices are
identically configured.
Configuring general properties and redeploying
If your configured deployment continues to fail, you can remove and reconfigure all general property
settings, or restore a previously successful backup file per device.
1.
Remove all configurations present on all devices.
Note: You may want to restore a backup file instead, per device, to remove all current configurations.
2.
For all devices, individually configure each section in the F5
®
Herculon
™
SSL Orchestrator
™
configuration utility and select
Deploy
. Verify that all new objects are properly synced and deployed.
Note: If synchronization or deployment issues persist after deploying after each section, attempt to
deploy after updating each item (instead of after each section) in the Herculon SSL Orchestrator
configuration utility and verify that all new objects are properly synced and deployed.
Note: See the Configuring general properties section for more detailed information.
Reviewing error logs and performing recovery steps
You can review log messages to help you debug system activity and perform recovery steps. Refer to the
Configuring logging
section of this document for more information on generating logs and setting the
level of logging you want the system to perform.
1.
Verify that all BIG-IP
®
LTM
®
and network objects are present on each of the devices in the HA device
group.
2.
If the configuration deployment fails on each device, review the logs:
•
/var/log/restnoded/restnoded.log
•
/var/log/restjavad.0.log
3.
Use the following REST GET command to determine the state of the deployed device block in the
REST storage:
•
curl -s -k -u admin:admin
https://localhost/mgmt/shared/iapp/blocks
| json-format
4.
Since failure scenarios can vary, after reviewing the logs, attempt the following recovery steps:
a) Redeploy Herculon SSL Orchestrator.
If this succeeds, you have recovered from the failure situation.
b) Undeploy Herculon SSL Orchestrator.
By undeploying, a cleanup of MCP objects on each of the devices occurs while also cleaning up
required data properties within the block stored in REST storage. If this succeeds, attempt to
redeploy again.
F5 Herculon SSL Orchestrator: Setup
45
Summary of Contents for Herculon SSL Orchestrator
Page 1: ...F5 Herculon SSL Orchestrator Setup Version 13 1 3 0 ...
Page 2: ......
Page 6: ...What is F5 Herculon SSL Orchestrator 6 ...
Page 26: ...Setting Up a Basic Configuration 26 ...
Page 38: ...Importing and Exporting Configurations for Deployment 38 ...
Page 54: ...Using Herculon SSL Orchestrator Analytics 54 ...