MetroCluster release notes
The requested article is not available. Either it doesn't apply to this version of the product or the relevant information is organized differently in this version of the docs. You can search, browse, or go back to the other version.
Event log files for MetroCluster Tiebreaker
Contributors
Suggest changes
-
PDF of this doc site
-
Install a fabric-attached MetroCluster
-
Cable a fabric-attached MetroCluster configuration
-
Plan and install a MetroCluster configuration with array LUNs
-
-
Install a MetroCluster IP configuration
-
Install a stretch MetroCluster configuration
-
Maintain the MetroCluster components
-
Transition from MetroCluster FC to MetroCluster IP
-
Upgrade, refresh, or expand the MetroCluster configuration
-
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
The event log file contains a log of all the actions performed by the MetroCluster Tiebreaker software.
The Tiebreaker software performs the following actions:
-
Detects site disasters
-
Detects configuration changes related to the database, other Tiebreaker monitors, or the MetroCluster Tiebreaker software
-
Detects SSH connections and disconnections
-
Discovers MetroCluster configurations
These actions are logged in the event log file in the following format:
<timestamp> <severity/log level> <thread-id> <module>
Example
2022-09-07 06:14:30,797 INFO [MCCTBCommandServer-16] [SslSupport] Successfully initiated SSL context. Protocol used is TLSv1.3. 2022-09-07 06:14:34,137 INFO [MCCTBCommandServer-16] [DataBase] Successfully read MCCTB database. 2022-09-07 06:14:34,137 INFO [MCCTBCommandServer-16] [ConfigurationMonitor] Debug mode disabled.
