01-03-2013 09:26 PM
I installed SVS 6.0.1 on my server and update VRTSvcsag to version 6.0.2. Then i configured VMwareDisks resource in main.cf.
VMwareDisks VMwareDisks1 (
ESXDetails = { "10.172.117.95" = "root=ISIuJWlWLwPOiWKuM" }
DiskPaths = {
"[95_storage] rhel5104/rhel5104_1.vmdk" = "0:1",
"[95_storage] rhel5104/rhel5104_2.vmdk" = "0:2",
"[95_storage] rhel5104/rhel5104_3.vmdk" = "0:3" }
)
But after had started, the VMwareDisks resource is not probed with the error message:
Dec 28 01:19:42 rhel5104 AgentFramework[16962]: VCS ERROR V-16-10061-22521 VMwareDisks:VMwareDisks1:monitor:Incorrect configuration: The disk '[95_storage] rhel5104/rhel5104_3.vmdk' has incorrect RDM configuration.
--------------------------------------------------------------------------------------------
The Disk UUID is automatically updated in main.cf when hastart:
VMwareDisks VMwareDisks1 (
ESXDetails = { "10.172.117.95" = "root=ISIuJWlWLwPOiWKuM" }
DiskPaths = {
"6000C291-229e-4704-719c-2a66b8f21ad8:[95_storage] rhel5104/rhel5104_1.vmdk" = "0:1",
"6000C29a-82d7-d365-a09e-68d37698afd9:[95_storage] rhel5104/rhel5104_2.vmdk" = "0:2",
"6000C29d-0bd2-901d-5b95-24934b43144e:[95_storage] rhel5104/rhel5104_3.vmdk" = "0:3" }
)
Solved! Go to Solution.
01-08-2013 12:42 AM
If its RDM disk, then you should prepend the "RDM:" keyword in the vmdk path.
So, it should look something like the following:
"RDM:[95_storage] rhel5104/rhel5104_1.vmdk" = "0:1",
"RDM:[95_storage] rhel5104/rhel5104_2.vmdk" = "0:2",
"RDM:[95_storage] rhel5104/rhel5104_3.vmdk" = "0:3" }
Later on, disk UUID will be automatically populated by the agent as follows:
"RDM:6000C291-229e-4704-719c-2a66b8f21ad8:[95_storage] rhel5104/rhel5104_1.vmdk" = "0:1",
Hope that helps.
Thanks!
Soumya.
01-03-2013 09:27 PM
01-04-2013 10:43 PM
01-08-2013 12:42 AM
If its RDM disk, then you should prepend the "RDM:" keyword in the vmdk path.
So, it should look something like the following:
"RDM:[95_storage] rhel5104/rhel5104_1.vmdk" = "0:1",
"RDM:[95_storage] rhel5104/rhel5104_2.vmdk" = "0:2",
"RDM:[95_storage] rhel5104/rhel5104_3.vmdk" = "0:3" }
Later on, disk UUID will be automatically populated by the agent as follows:
"RDM:6000C291-229e-4704-719c-2a66b8f21ad8:[95_storage] rhel5104/rhel5104_1.vmdk" = "0:1",
Hope that helps.
Thanks!
Soumya.
01-09-2013 03:20 AM
Clarification: The agent supports RDM disks.
Please refer to Soumya's reply to properly configure VMwareDisks resource when the disk is RDM.
I am curious to know how did you configure VMwareDisks resource? Was it configured through 'Application Configuration Wizard' , or was it configured manually through VCS CLI or VCS UI (like VOM)?
--
regards,
Prasanna
01-09-2013 03:23 AM
For more information, please refer to DiskPaths attribute under Required Attributes table at https://sort.symantec.com/public/documents/sfha/6.0.2/linux/productguides/html/vcs_bundled_agents/ch02s10s03.htm.
04-22-2013 03:54 AM
Check this sample configuration....
06-12-2017 09:36 AM
Does anyone have a sample configuration that includes an entire SG, or entire main.cf file? The one set of examples that everyone at Veritas reference doesn't give me enough insight into how I integrate this agent into work SGs/configurations. I used to be able to call support about this stuff, but they keep copying the example out of the Agents reference document, which isn't enough information. The support folks don't seem to know th product very well, so I'm hoping someone out there can provide some guidance. I can post my main.cf if you like, and just let me know where I define the vmwaredisks resources to access them appropriately.
Thanks a lot for you time.
04-09-2021 08:11 AM
I got same problem.