Veritas Cluster Server Bundled Agents Reference Guide
Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec
Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec
- No tags were found...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
172<br />
Troubleshooting bundled agents<br />
VCS logging<br />
VCS logging<br />
VCS generates two error message logs: the engine log and the agent log. Log file<br />
names are appended by letters. Letter A indicates the first log file, B the second,<br />
C the third, and so on.<br />
The agent log is located at %VCS_HOME%\log\agent_A.txt. The format of agent<br />
log messages is:<br />
Timestamp (Year/MM/DD) | Mnemonic | Severity | UMI | Agent Type | Resource<br />
Name | Function | Message Text<br />
The agent log message components are defined as follows:<br />
■<br />
■<br />
■<br />
■<br />
■<br />
Timestamp: the date and time the message was generated.<br />
Mnemonic: the string ID that represents the product (for example, VCS).<br />
Severity: levels include CRITICAL, ERROR, WARNING, NOTICE, and INFO (most to<br />
least severe, respectively).<br />
UMI: a unique message ID.<br />
Message Text: the actual message generated by VCS.<br />
A typical agent log resembles:<br />
2004/03/02 16:34:07 VCS WARNING V-16-10051-5008<br />
NotifierMngr:ntfr:monitor:Expected correct SNMP and | or SMTP<br />
options<br />
Troubleshooting storage agents<br />
Storage agents comprise the Volume Manager Diskgroup agent and MountV agent.<br />
Note: In case of a NetApp storage environment, the Logical Unit Numbers (LUNs)<br />
on the NetApp Filer are made highly available by the NetApp Filer and NetApp<br />
SnapDrive agents instead of the VMDg and MountV agents respectively. Refer to<br />
the application-specific VCS implementation guides for more information on<br />
these agents.<br />
Disk Reservation agent error messages<br />
No arguments<br />
This is a VCS internal error.<br />
Recommended Action: Contact Symantec Technical Support.