VCS generates two error message logs: the engine logs and the agent logs. Log file names are appended by letters. Letter A indicates the first log file, B the second, C the third, and so on.
The agent log is located at %VCS_HOME%\log\agent_A.txt. The format of agent log messages is:
Timestamp (Year/MM/DD) | Mnemonic | Severity | UMI | Agent Type | Resource Name | Entry Point | Message Text
Table: Log message components and their description describes the agent log message components and their descriptions.
Table: Log message components and their description
|
Log message component
|
Description |
|
Timestamp
|
Denotes the date and time when the message was logged.
|
|
Mnemonic
|
Denotes which Symantec product logs the message. For Symantec Cluster Server, the mnemonic is 'VCS'.
|
|
Severity
|
Denotes the severity of the message. Severity is classified into the following types:
CRITICAL indicates a critical error within a VCS process. Contact Technical Support immediately. ERROR indicates failure of a cluster component, unanticipated state change, or termination or unsuccessful completion of a VCS action. WARNING indicates a warning or error, but not an actual fault. NOTE informs the user that VCS has initiated an action. -
INFO informs the user of various state messages or comments.
Among these, CRITICAL, ERROR, and WARNING indicate actual errors. NOTE and INFO provide additional information.
|
|
UMI or Unique Message ID
|
UMI is a combination of Originator ID, Category ID, and Message ID. For example, the UMI for a message generated by the SQLServer agent would resemble: V-16-xxxxx-yy. Originator ID for all VCS products is 'V-16.' Category ID for the agents is as follows:
Message ID is a unique number assigned to the message text.
|
|
Message Text
|
Denotes the actual message string.
|
You can view these message logs using Notepad or any text editor. All messages are logged to the engine and the agent logs. Messages of type CRITICAL and ERROR are written to the Windows event log.
