Re: [Veritas-ha] VCS 5.0 MP1: issue probing disk-group !?
Part of the main.cf.
I created a test_SG to make things easier which contains only one
resource, test_DG, which is linked to the dba_DG disk-group. I took that
dba_DG since it is the one I took as example so far, but as a reminder,
I have the same issue with all disk-groups: all disk-groups behave
properly using commands on the command-line or the VERITAS Enterprise
Administrator, (no warning, no errors). However, in the VERITAS Cluster
Manager disk-group resources remain in status unknown (? mark) because
of apparently probing issues on both systems/nodes !?
Note that if I import the disk-group manually, it's status remains
unkown in the GUI, but the volume-resources related to that disk-group
(for dba_DG) are probed successfully and shown online in the GUI. So
the probe issue is related to disk-groups only.
Licensing is OK, with permanent license, for VxFS, VxVM and VCS.
bash-3.00# uname -a
SunOS . 5.10 Generic_127127-11 sun4u sparc SUNW,Sun-Fire-V440
group test_SG (
SystemList = { A = 0, B = 1 }
)
DiskGroup test_DG (
DiskGroup = test_DG
)
// resource dependency tree
//
// group test_SG
// {
// DiskGroup test_DG
// }
The header of the main.cf looks like this:
bash-3.00# more /etc/VRTSvcs/conf/config/main.cf
include types.cf
include OracleTypes.cf
cluster testcluster (
UserNames = { admin = fkl..ki }
Administrators = { admin }
)
system A (
)
system B (
)
Regards,
/Pascal
___
Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
Re: [Veritas-ha] VCS 5.0 MP1: issue probing disk-group !?
Cut and paste main.cf for the service group in question? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pascal Grostabussiat Sent: Tuesday, October 21, 2008 9:11 AM Cc: Veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] VCS 5.0 MP1: issue probing disk-group !? To Jim, Scott and Gene. Jim Senicka wrote: Is the disk group agent running on the systems? Yes it is: root 16295 1 0 16:16:01 ? 1:29 /opt/VRTSvcs/bin/DiskGroup/DiskGroupAgent -type DiskGroup Has the cluster been started since you created the service group definition? Yes. I restarted VCS hopping it might somehow change something, but no. I am thinking about rebooting one server. Are all resources enabled in the service groups? Yes. I tried to disable them and re-enable them. But I come back to the same situation. Scott3, James wrote: Have you made sure the volumes are ENABLED ACTIVE? Can you send a vxprint on the group? Is it a shared group or a active/passive group? Also send a vxdg list. Enabled and active, yes. The disk-group is active/passive (to be mounted on one host at a time). bash-3.00# vxprint -l dba_DG Disk group: dba_DG Group:dba_DG info: dgid=1224062934.119.hostname version: 140 alignment: 8192 (bytes) detach-policy: global dg-fail-policy: dgdisable copies: nconfig=default nlog=default devices: max=32767 cur=3 minors: = 62000 cds=on bash-3.00# vxprint -g dba_DG TY NAME ASSOCKSTATE LENGTH PLOFFS STATETUTIL0 PUTIL0 dg dba_DG dba_DG ----- - dm dba_DG01 c0t216000C0FF87E774d10s2 - 525417536 - -- - v dba_archive fsgenENABLED 20971520 -ACTIVE - - pl dba_archive-01 dba_archive ENABLED 20971520 -ACTIVE - - sd dba_DG01-02 dba_archive-01 ENABLED 20971520 0 -- - v dba_data fsgenENABLED 104857600 - ACTIVE - - pl dba_data-01 dba_data ENABLED 104857600 - ACTIVE - - sd dba_DG01-03 dba_data-01 ENABLED 104857600 0 -- - v dba_redo fsgenENABLED 20971520 -ACTIVE - - pl dba_redo-01 dba_redo ENABLED 20971520 -ACTIVE - - sd dba_DG01-01 dba_redo-01 ENABLED 20971520 0-- - bash-3.00# vxdg list NAME STATE ID xxx_DG enabled,cds 1224062531.89.hostname xxx_DG enabled,cds 1224062634.101.hostname xxx_DG enabled,cds 1224062699.109.hostname dba_DG enabled,cds 1224062934.119.hostname xxx_DG enabled,cds 1224062443.81.hostname xxx_DGenabled,cds 1224062569.93.hostname xxx_DG enabled,cds 1224062672.105.hostname xxx_DG enabled,cds 1224062491.85.hostname Gene Henriksen wrote: If you have a ? in the GUI, then it cannot probe the resource on one system or the other. It will not import on either until it is probed on both. This is to avoid a concurrency violation. Yes. Fully agree. Hold the cursor on the resource and a pop-up box should show the status so you can see where it is not probed. Status is unkown on both server A and B. This could be due to one system having never seen the DG. Can you run vxdisk -o alldgs list and see the DG on both systems? I can import/deport that disk-group using vxdg without a problem bash-3.00# vxdisk -o alldgs list DEVICE TYPEDISK GROUPSTATUS c0t216000C0FF87E774d0s2 auto:none --online invalid c0t216000C0FF87E774d1s2 auto:cdsdiskxxx_DG01 xxx_DG online c0t216000C0FF87E774d2s2 auto:cdsdiskxxx_DG01xxx_DG online c0t216000C0FF87E774d3s2 auto:cdsdiskxxx_DG01xxx_DG online c0t216000C0FF87E774d4s2 auto:cdsdiskxxx_DG01 xxx_DGonline c0t216000C0FF87E774d5s2 auto:cdsdisk-(xxx_DG)online c0t216000C0FF87E774d6s2 auto:cdsdiskxxx_DG01xxx_DG online c0t216000C0FF87E774d7s2 auto:cdsdiskxxx_DG01xxx_DG online c0t216000C0FF87E774d8s2 auto:cdsdiskxxx_DG01 xxx_DG online c0t216000C0FF87E774d9s2 auto:cdsdisk-(xxx_DG) online c0t216000C0FF87E774d10s2 auto:cdsdiskdba_DG01 dba_DG online c2t0d0s2 auto:none --online invalid c2t2d0s2 auto:none --online invalid c2t3d0s2 auto:none --online invalid The other possibility is a typo in the DiskGroup resource attribute. Make sure it has no leading spaces, is the correct case (just like vxdisk list shows it. I thought about this and double-checked. Nothing. I recreated the resource and paid attention to such possibility, nothing. Regards, /Pascal ___ Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
Re: [Veritas-ha] VCS 5.0 MP1: issue probing disk-group !?
Is the disk group agent running on the systems? Has the cluster been started since you created the service group definition? Are all resources enabled in the service groups? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pascal Grostabussiat Sent: Tuesday, October 21, 2008 7:09 AM To: Veritas-ha@mailman.eng.auburn.edu Subject: [Veritas-ha] VCS 5.0 MP1: issue probing disk-group !? Hi, I have experiencing a weird issue since yesterday and I cannot get that solve buy surfing and checking around. So I hope to get a hint using the mailing-list. Our sysadmin recently installed a system with two Sun SPARC for me with VxVM, VxFS and VCS. In short I have VERITAS Foundation 5.0 with MP1. DESC: Veritas Cluster Server by Symantec PSTAMP: Veritas-5.0MP1-11/29/06-17:15:00 DESC: Virtual Disk Subsystem PSTAMP: Veritas-5.0-MP1.26:2007-02-28 DESC: Commercial File System PSTAMP: VERITAS-FS-5.0.1.0-2007-01-17-5.0MP1=123202-02 Now I have an issue with all disk-groups, like for example dba_DG. Using the command line or the VERITAS Enterprise Administrator I can import/deport the disk-group, I can mount the corresponding volumes and creates file-systems on them. No issue there. Now I go to the VERITAS Cluster Administrator and there our sysadmin had already created resources for the disk-groups. However, I cannot bring anyone online because the GUI keeps on telling me that the resource has not been probed on the system (I have two systems, tried to online on A and B, but same behavior). I deleted the resource, created a new one, same issue. I still have a ? mark on the resource. Issuing a probe does not solve anything. I checked the engine_A.log and can see that the probe was fired, but nothing more. I can run the hares -probe dba_DG -sys A and I get the prompt back, nothing else appears !? I am puzzled ! Any idea ? Any known issue ? Many thanks in advance. Regards, /Pascal ___ Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha ___ Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
Re: [Veritas-ha] VCS 5.0 MP1: issue probing disk-group !?
To Jim, Scott and Gene. Jim Senicka wrote: Is the disk group agent running on the systems? Yes it is: root 16295 1 0 16:16:01 ? 1:29 /opt/VRTSvcs/bin/DiskGroup/DiskGroupAgent -type DiskGroup Has the cluster been started since you created the service group definition? Yes. I restarted VCS hopping it might somehow change something, but no. I am thinking about rebooting one server. Are all resources enabled in the service groups? Yes. I tried to disable them and re-enable them. But I come back to the same situation. Scott3, James wrote: Have you made sure the volumes are ENABLED ACTIVE? Can you send a vxprint on the group? Is it a shared group or a active/passive group? Also send a vxdg list. Enabled and active, yes. The disk-group is active/passive (to be mounted on one host at a time). bash-3.00# vxprint -l dba_DG Disk group: dba_DG Group:dba_DG info: dgid=1224062934.119.hostname version: 140 alignment: 8192 (bytes) detach-policy: global dg-fail-policy: dgdisable copies: nconfig=default nlog=default devices: max=32767 cur=3 minors: = 62000 cds=on bash-3.00# vxprint -g dba_DG TY NAME ASSOCKSTATE LENGTH PLOFFS STATETUTIL0 PUTIL0 dg dba_DG dba_DG ----- - dm dba_DG01 c0t216000C0FF87E774d10s2 - 525417536 - -- - v dba_archive fsgenENABLED 20971520 -ACTIVE - - pl dba_archive-01 dba_archive ENABLED 20971520 -ACTIVE - - sd dba_DG01-02 dba_archive-01 ENABLED 20971520 0 -- - v dba_data fsgenENABLED 104857600 - ACTIVE - - pl dba_data-01 dba_data ENABLED 104857600 - ACTIVE - - sd dba_DG01-03 dba_data-01 ENABLED 104857600 0 -- - v dba_redo fsgenENABLED 20971520 -ACTIVE - - pl dba_redo-01 dba_redo ENABLED 20971520 -ACTIVE - - sd dba_DG01-01 dba_redo-01 ENABLED 20971520 0-- - bash-3.00# vxdg list NAME STATE ID xxx_DG enabled,cds 1224062531.89.hostname xxx_DG enabled,cds 1224062634.101.hostname xxx_DG enabled,cds 1224062699.109.hostname dba_DG enabled,cds 1224062934.119.hostname xxx_DG enabled,cds 1224062443.81.hostname xxx_DGenabled,cds 1224062569.93.hostname xxx_DG enabled,cds 1224062672.105.hostname xxx_DG enabled,cds 1224062491.85.hostname Gene Henriksen wrote: If you have a ? in the GUI, then it cannot probe the resource on one system or the other. It will not import on either until it is probed on both. This is to avoid a concurrency violation. Yes. Fully agree. Hold the cursor on the resource and a pop-up box should show the status so you can see where it is not probed. Status is unkown on both server A and B. This could be due to one system having never seen the DG. Can you run vxdisk -o alldgs list and see the DG on both systems? I can import/deport that disk-group using vxdg without a problem bash-3.00# vxdisk -o alldgs list DEVICE TYPEDISK GROUPSTATUS c0t216000C0FF87E774d0s2 auto:none --online invalid c0t216000C0FF87E774d1s2 auto:cdsdiskxxx_DG01 xxx_DG online c0t216000C0FF87E774d2s2 auto:cdsdiskxxx_DG01xxx_DG online c0t216000C0FF87E774d3s2 auto:cdsdiskxxx_DG01xxx_DG online c0t216000C0FF87E774d4s2 auto:cdsdiskxxx_DG01 xxx_DGonline c0t216000C0FF87E774d5s2 auto:cdsdisk-(xxx_DG)online c0t216000C0FF87E774d6s2 auto:cdsdiskxxx_DG01xxx_DG online c0t216000C0FF87E774d7s2 auto:cdsdiskxxx_DG01xxx_DG online c0t216000C0FF87E774d8s2 auto:cdsdiskxxx_DG01 xxx_DG online c0t216000C0FF87E774d9s2 auto:cdsdisk-(xxx_DG) online c0t216000C0FF87E774d10s2 auto:cdsdiskdba_DG01 dba_DG online c2t0d0s2 auto:none --online invalid c2t2d0s2 auto:none --online invalid c2t3d0s2 auto:none --online invalid The other possibility is a typo in the DiskGroup resource attribute. Make sure it has no leading spaces, is the correct case (just like vxdisk list shows it. I thought about this and double-checked. Nothing. I recreated the resource and paid attention to such possibility, nothing. Regards, /Pascal ___ Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
Re: [Veritas-ha] VCS 5.0 MP1: issue probing disk-group !?
Can you put the SG info from main.cf in an email so we can see the configuration? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pascal Grostabussiat Sent: Tuesday, October 21, 2008 9:11 AM Cc: Veritas-ha@mailman.eng.auburn.edu Subject: Re: [Veritas-ha] VCS 5.0 MP1: issue probing disk-group !? To Jim, Scott and Gene. Jim Senicka wrote: Is the disk group agent running on the systems? Yes it is: root 16295 1 0 16:16:01 ? 1:29 /opt/VRTSvcs/bin/DiskGroup/DiskGroupAgent -type DiskGroup Has the cluster been started since you created the service group definition? Yes. I restarted VCS hopping it might somehow change something, but no. I am thinking about rebooting one server. Are all resources enabled in the service groups? Yes. I tried to disable them and re-enable them. But I come back to the same situation. Scott3, James wrote: Have you made sure the volumes are ENABLED ACTIVE? Can you send a vxprint on the group? Is it a shared group or a active/passive group? Also send a vxdg list. Enabled and active, yes. The disk-group is active/passive (to be mounted on one host at a time). bash-3.00# vxprint -l dba_DG Disk group: dba_DG Group:dba_DG info: dgid=1224062934.119.hostname version: 140 alignment: 8192 (bytes) detach-policy: global dg-fail-policy: dgdisable copies: nconfig=default nlog=default devices: max=32767 cur=3 minors: = 62000 cds=on bash-3.00# vxprint -g dba_DG TY NAME ASSOCKSTATE LENGTH PLOFFS STATETUTIL0 PUTIL0 dg dba_DG dba_DG ----- - dm dba_DG01 c0t216000C0FF87E774d10s2 - 525417536 - -- - v dba_archive fsgenENABLED 20971520 -ACTIVE - - pl dba_archive-01 dba_archive ENABLED 20971520 -ACTIVE - - sd dba_DG01-02 dba_archive-01 ENABLED 20971520 0 -- - v dba_data fsgenENABLED 104857600 - ACTIVE - - pl dba_data-01 dba_data ENABLED 104857600 - ACTIVE - - sd dba_DG01-03 dba_data-01 ENABLED 104857600 0 -- - v dba_redo fsgenENABLED 20971520 -ACTIVE - - pl dba_redo-01 dba_redo ENABLED 20971520 -ACTIVE - - sd dba_DG01-01 dba_redo-01 ENABLED 20971520 0-- - bash-3.00# vxdg list NAME STATE ID xxx_DG enabled,cds 1224062531.89.hostname xxx_DG enabled,cds 1224062634.101.hostname xxx_DG enabled,cds 1224062699.109.hostname dba_DG enabled,cds 1224062934.119.hostname xxx_DG enabled,cds 1224062443.81.hostname xxx_DGenabled,cds 1224062569.93.hostname xxx_DG enabled,cds 1224062672.105.hostname xxx_DG enabled,cds 1224062491.85.hostname Gene Henriksen wrote: If you have a ? in the GUI, then it cannot probe the resource on one system or the other. It will not import on either until it is probed on both. This is to avoid a concurrency violation. Yes. Fully agree. Hold the cursor on the resource and a pop-up box should show the status so you can see where it is not probed. Status is unkown on both server A and B. This could be due to one system having never seen the DG. Can you run vxdisk -o alldgs list and see the DG on both systems? I can import/deport that disk-group using vxdg without a problem bash-3.00# vxdisk -o alldgs list DEVICE TYPEDISK GROUPSTATUS c0t216000C0FF87E774d0s2 auto:none --online invalid c0t216000C0FF87E774d1s2 auto:cdsdiskxxx_DG01 xxx_DG online c0t216000C0FF87E774d2s2 auto:cdsdiskxxx_DG01xxx_DG online c0t216000C0FF87E774d3s2 auto:cdsdiskxxx_DG01xxx_DG online c0t216000C0FF87E774d4s2 auto:cdsdiskxxx_DG01 xxx_DGonline c0t216000C0FF87E774d5s2 auto:cdsdisk-(xxx_DG)online c0t216000C0FF87E774d6s2 auto:cdsdiskxxx_DG01xxx_DG online c0t216000C0FF87E774d7s2 auto:cdsdiskxxx_DG01xxx_DG online c0t216000C0FF87E774d8s2 auto:cdsdiskxxx_DG01 xxx_DG online c0t216000C0FF87E774d9s2 auto:cdsdisk-(xxx_DG) online c0t216000C0FF87E774d10s2 auto:cdsdiskdba_DG01 dba_DG online c2t0d0s2 auto:none --online invalid c2t2d0s2 auto:none --online invalid c2t3d0s2 auto:none --online invalid The other possibility is a typo in the DiskGroup resource attribute. Make sure it has no leading spaces, is the correct case (just like vxdisk list shows it. I thought about this and double-checked. Nothing. I recreated the resource and paid attention to such possibility, nothing. Regards, /Pascal ___ Veritas-ha maillist - Veritas-ha@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
