Upgrade Considerations

Read these considerations before you start the upgrade process. These considerations are applicable to both standalone and High Availability (HA) environments.

  • After upgrading to version 6.3.1, if you try to access the appliance using Mozilla Firefox, the Secure Connection Failed error message might be displayed. See the Mozilla Firefox support site for tips on troubleshooting security error codes.
  • Advanced Features and Monitoring Console settings before and after upgrade:
    From LogLogic LMI version State of Advanced Features After upgrading to LogLogic LMI 6.3.1
    Advanced Features Advanced Aggregation Monitoring Console
    6.2.1 Enabled Enabled Enabled Disabled
    6.2.1 Disabled Disabled Disabled Disabled
    6.3.0 When upgrading from version 6.3.0, the state of Advanced Features, Advanced Aggregation, and Monitoring Console settings remains intact after upgrading to version 6.3.1.
  • In case of a Management Station cluster or a High Availability cluster, ensure that all appliances have the same LogLogic LMI and LogLogic LSP versions (the hot fix versions need not match). For more information about HA upgrade, see the TIBCO LogLogic® Log Management Intelligence Administration.
  • If the LogLogic LMI appliance uses LogLogic TCP as the message routing protocol, it is recommended that the source and destination appliances have the same LogLogic LMI version, for best compatibility.
  • To properly forward Check Point data, you must update both your sender and receiver LogLogic LMI appliances to the same LogLogic LMI version.
  • Even if you disable the SSH Daemon at Startup option before upgrading to version 6.3.1, the SSH daemon runs at startup after the upgrade is completed, although the option is displayed as disabled on the Administration > System Settings > General tab. You must disable the option again after the upgrade.
Next topic: Preparing to Upgrade the Appliance