After Upgrade to v6: monitor:Blockmountpointaccess not configured
Hi there We upgraded our Test single Node cluster to the version 6 with cp2. After the installation and reboot all of the mountv resource are in a failed state. in the mountv_a.txt logfile i found this line: monitor:Blockmountpointaccess not configured Any suggestions how to fix that? ThanksSolved2.5KViews6likes3Comments
not able to initialize the disk
I had a disk under VxVM control. I removed it from VxVM control. Again when I added the same disk, it is not allowing me to initialize .Also I feel, it is showing wrong multipaths in vxdisk list output. root@dbpdadc42> vxdisksetup -i c0t500507680140533Ad8 VxVM vxdisksetup ERROR V-5-2-3523 c0t500507680140533Ad8: Disk is in use root@dbpdadc42> vxdisk list c0t500507680140533Ad8 Device: c0t500507680140533Ad8s2 devicetag: c0t500507680140533Ad8 type: auto info: format=none flags: online ready private autoconfig invalid pubpaths: block=/dev/vx/dmp/c0t500507680140533Ad8s2 char=/dev/vx/rdmp/c0t500507680140533Ad8s2 Multipathing information: numpaths: 4 c1t500507680130064Ad10s2 state=enabled c1t500507680130533Ad10s2 state=enabled c0t500507680140064Ad10s2 state=enabled c0t500507680140533Ad10s2 state=enabled1.2KViews4likes4Comments
vcs resource status abnormal
I am facing a problem,i found a resource become online monitor timeout , and i don't know how to fix it ; could anybody give me some suggestion. thanks; #hastatus .............. group resource system message --------------- -------------------- -------------------- -------------------- cfsmount1 CCCG09BER ONLINE cfsmount1 CCCG10BER ONLINE cfsmount2 CCCG09BER ONLINE cfsmount2 CCCG10BER ONLINE ------------------------------------------------------------------------- cvmvoldg1 CCCG09BER ONLINE cvmvoldg1 CCCG10BER ONLINE group resource system message --------------- -------------------- --------------- -------------------- cvmvoldg1 CCCG09BER |MONITOR TIMEDOUT|UNABLE TO OFFLINE| cvmvoldg2 CCCG09BER ONLINE cvmvoldg2 CCCG10BER ONLINE cvmvoldg2 CCCG09BER |MONITOR TIMEDOUT|UNABLE TO OFFLINE| --------------------------------------------------------------------------------------------------------------------------------------------- # hares -state cvmvoldg1 #Resource Attribute System Value cvmvoldg1 State CCCG09BER ONLINE|MONITOR TIMEDOUT cvmvoldg1 State CCCG10BER ONLINE # # vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:SVM - - SVM c0t1d0s2 auto:SVM - - SVM c0t2d0s2 auto:none - - online invalid c0t3d0s2 auto:none - - online invalid c3t0d0 auto:cdsdisk - - online c3t0d1 auto:sliced mmdatadgemcpower4 mmdatadg online shared c3t0d2 auto:cdsdisk - - online c3t0d3 auto:cdsdisk - - online c3t0d4 auto:sliced mmdbdgemcpower2 mmdbdg online shared c3t0d5s2 auto:sliced mmdatadgc3t0d5 mmdatadg online shared c3t0d6s2 auto:sliced mmdatadgc3t0d6 mmdatadg online shared c3t0d7s2 auto:sliced mmdatadgc3t0d7 mmdatadg online shared c3t0d8s2 auto:sliced mmdatadgc3t0d8 mmdatadg online shared c3t0d9s2 auto:sliced mmdatadgc3t0d9 mmdatadg online shared c3t0d10s2 auto:sliced mmdatadgc3t0d10 mmdatadg online shared # vxprint Disk group: mmdbdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg mmdbdg mmdbdg - - - - - - dm mmdbdgemcpower2 c3t0d4 - 419348384 - - - - v vol01 fsgen ENABLED 419346432 - ACTIVE - - pl vol01-01 vol01 ENABLED 419346432 - ACTIVE - - sd mmdbdgemcpower2-01 vol01-01 ENABLED 419346432 0 - - - Disk group: mmdatadg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg mmdatadg mmdatadg - - - - - - dm mmdatadgc3t0d5 c3t0d5s2 - 1467866928 - - - - dm mmdatadgc3t0d6 c3t0d6s2 - 1887246288 - - - - dm mmdatadgc3t0d7 c3t0d7s2 - 1836919616 - - - - dm mmdatadgc3t0d8 c3t0d8s2 - 1887246288 - - - - dm mmdatadgc3t0d9 c3t0d9s2 - 1887246288 - - - - dm mmdatadgc3t0d10 c3t0d10s2 - 1417511040 - - - - dm mmdatadgemcpower4 c3t0d1 - 1887354784 - - - - v vol01 fsgen ENABLED 12271390720 - ACTIVE - - pl vol01-01 vol01 ENABLED 12271390720 - ACTIVE - - sd mmdatadgemcpower4-01 vol01-01 ENABLED 1887354784 0 - - - sd mmdatadgc3t0d5-01 vol01-01 ENABLED 1467866928 1887354784 - - - sd mmdatadgc3t0d6-01 vol01-01 ENABLED 1887246288 3355221712 - - - sd mmdatadgc3t0d7-01 vol01-01 ENABLED 1836919616 5242468000 - - - sd mmdatadgc3t0d8-01 vol01-01 ENABLED 1887246288 7079387616 - - - sd mmdatadgc3t0d9-01 vol01-01 ENABLED 1887246288 8966633904 - - - sd mmdatadgc3t0d10-01 vol01-01 ENABLED 1417510528 10853880192 - - - messages in engine_A log: 2015/03/06 13:44:21 VCS ERROR V-16-2-13027 (CCCG09BER) Resource(cvmvoldg2) - monitor procedure did not complete within the expected time. 2015/03/06 13:44:22 VCS ERROR V-16-2-13027 (CCCG09BER) Resource(cvmvoldg1) - monitor procedure did not complete within the expected time. 2015/03/06 13:46:28 VCS INFO V-16-1-50086 CPU usage on CCCG09BER is 61% 2015/03/06 13:50:21 VCS ERROR V-16-2-13210 (CCCG09BER) Agent is calling clean for resource(cvmvoldg2) because 4 successive invocatio ns of the monitor procedure did not complete within the expected time. 2015/03/06 13:50:21 VCS ERROR V-16-2-13210 (CCCG09BER) Agent is calling clean for resource(cvmvoldg1) because 4 successive invocatio ns of the monitor procedure did not complete within the expected time. 2015/03/06 13:50:39 VCS INFO V-16-2-13068 (CCCG09BER) Resource(cvmvoldg2) - clean completed successfully. 2015/03/06 13:50:53 VCS INFO V-16-2-13068 (CCCG09BER) Resource(cvmvoldg1) - clean completed successfully. 2015/03/06 13:51:40 VCS ERROR V-16-2-13077 (CCCG09BER) Agent is unable to offline resource(cvmvoldg2). Administrative intervention m ay be required. 2015/03/06 13:51:55 VCS ERROR V-16-2-13077 (CCCG09BER) Agent is unable to offline resource(cvmvoldg1). Administrative intervention m ay be required.Solved1.1KViews3likes1Comment
Can't locate object method "QEMU" Error During Upgrade to 6.0.x
Hi all, I have a two node VCS cluster running on two KVM Virtual Machines RHEL 5.5. VCS version is currently 5.1 SP1 RP2 and I'm trying to upgrade it to version 6.0.1. Right after I run the installer script I get the following error: [root@Hostname rhel5_x86_64]# pwd /shared_data/VCS/dvd1-redhatlinux/rhel5_x86_64 [root@Hostname rhel5_x86_64]# ./installer Can't locate object method "QEMU" via package "Padv::RHEL5x8664" at /shared_data/VCS/dvd1-redhatlinux/rhel5_x86_64/scripts/EDR/Padv/Linux.pm line 1061. [root@Hostname rhel5_x86_64]# Has anyone encountered such an error before? I've contacted support and so far they have only instructed me to approach RedHat and open a ticket with them. Any help will be much appreciated. Thanks, YairSolved626Views3likes4Comments
Issue while Extending file system in vxvm
Hi, I have a case as below, Please extend below file systems from 30G to 50G on server island. /dev/vx/dsk/VRP_PRD_ora_data_dg/sapdata2 30G 15G 14G 52% /oracle/VRP/sapdata2 /dev/vx/dsk/VRP_PRD_ora_data_dg/sapdata4 30G 15G 14G 51% /oracle/VRP/sapdata4 /dev/vx/dsk/VRP_PRD_ora_data_dg/sapdata1 30G 14G 15G 49% /oracle/VRP/sapdata1 /dev/vx/dsk/VRP_PRD_ora_data_dg/sapdata3 30G 27G 2.7G 91% /oracle/VRP/sapdata3 root@myers# vxdisk -o alldgs -e list DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR emcpower22s2 auto VRP_PRD_sapcent_dg01 VRP_PRD_sapcent_dg online emcpower22c - emcpower23s2 auto emcpower23s2 VRP_PRD_ora_data_dg online emcpower23c - emcpower24s2 auto emcpower24s2 VRP_PRD_ora_data_dg online emcpower24c - emcpower25s2 auto emcpower25s2 VRP_PRD_ora_data_dg online emcpower25c - emcpower26s2 auto emcpower26s2 VRP_PRD_ora_data_dg online emcpower26c - emcpower27s2 auto emcpower27s2 VRP_PRD_ora_bin_dg online emcpower27c - emcpower28s2 auto VRP_PRD_ora_arch_dg01 VRP_PRD_ora_arch_dg online emcpower28c - ====================================================================================== These are the 4 new luns of 30 GB assigned by Storage. 57. emcpower29e <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@29 58. emcpower30a <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@30 59. emcpower33a <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@33 60. emcpower34b <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@34 ==================================================================== When I tried to label them they are giving errors as, 57. emcpower29e <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@29 58. emcpower30a <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@30 59. emcpower33a <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@33 60. emcpower34b <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@34 Specify disk (enter its number): 57 selecting emcpower29e [disk formatted] Disk not labeled. Label it now? y Warning: error writing VTOC. Warning: no backup labels Write label failed FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute <cmd>, then return =========================================================================== There are 4 lunsemcpower29e,emcpower30a,emcpower33a,emcpower34b which is require to initilize it and add them to theVRP_PRD_ora_data_dg diskgroup to increase filesystem to 20 GB more. Shall I have to proceed with the disk initilization in vxvm without labeling it or Please help me to proceed step by step activities required for this. Thanks,Solved3.7KViews2likes24CommentsAgent failed in VCS
Agent are in failed status. Below are the messages in engineA.log file. Please let me knwo the cause of this issue VCS WARNING V-16-1-53025 Agent Script has faulted; ipm connection was lost; restarting the agent VCS ERROR V-16-1-10015 Cannot start /opt/VRTSvcs/bin/Script/ScriptAgent please check file VCS WARNING V-16-1-53025 Agent NIC has faulted; ipm connection was lost; restarting the agent VCS ERROR V-16-1-10008 Agent NIC has faulted 6 times since VCS ERROR V-16-1-10015 Cannot start /opt/VRTSvcs/bin/NIC/NICAgent please check file VCS WARNING V-16-10001-4028 (unix) IP:Unix-G1-IP:monitor:Empty NetMask is supplied, default netmask will be used. VCS WARNING V-16-1-10023 Agent DiskGroup not sending alive messages since VCS WARNING V-16-1-53025 Agent DiskGroup has faulted; ipm connection was lost; restarting the agent VCS ERROR V-16-1-10015 Cannot start /opt/VRTSvcs/bin/DiskGroup/DiskGroupAgent please check fileSolved7.4KViews2likes4CommentsMigrating VxVM volumes from a V240 to a T4-2 Ldom
Hi all, I have a V240 running Solaris 10U08 with VxVM 6.0.000 that I need to migrate to a Solaris T4-2 Ldom (LDM 3.1). I have loaded the software that is in source onto the LDOM and presented the required SAN LUNs that match source into the guest LDOM but when I try to set up a disk (LUN) in VxVM using vxdisksetup I get: "ERROR V-5-2-43 c0d3: Invalid disk device for vxdisksetup". I have tried using vxdisk init c0d3s2and get: "Disk sector size is not supported" and tried vxdisk init c0d3s2 format=sliced and get: "Disk VTOC does not list private partition"Don't know xhat else to try !!!1.8KViews2likes8CommentsDMP and MPxIO doubt
All the LUNs are under vxvm. If I want to use MPxIO instead of DMP for those LUNs, what is the proper method to do it? I have seen a method saying that we need to delete dmp/rdmp directories... is it required? Should I disable DMP in any way or I just need to enable MPxIO via stmsboot -e with out disabling DMP ? ?Solved987Views2likes1Comment
Service Group Failover fails !!!
Hi there, I'm having an issue with one of our cluster wherein, when tried to fail-over the service group it failed with below errors - 2013/10/30 22:22:19 VCS ERROR V-16-2-13006 (XXXXX) Resource(vdaappdg_dg): clean procedure did not complete within the expected time. 2013/10/30 22:22:30 VCS ERROR V-16-2-13006 (XXXXX) Resource(vdrapp_vol): clean procedure did not complete within the expected time. 2013/10/30 22:22:32 VCS ERROR V-16-2-13027 (XXXXX) Resource(mobius_dg) - monitor procedure did not complete within the expected time. 2013/10/30 22:23:30 VCS ERROR V-16-2-13077 (XXXXX) Agent is unable to offline resource(vdrapp_vol). Administrative intervention may be required. 2013/10/30 22:26:48 VCS ERROR V-16-2-13077 (XXXXX) Agent is unable to offline resource(vdaappdg_dg). Administrative intervention may be required. 2013/10/30 22:32:35 VCS ERROR V-16-2-13063 (XXXXX) Agent is calling clean for resource(mobius_dg) because offline did not complete within the expected time. 2013/10/30 22:33:22 VCS INFO V-16-2-13068 (XXXXX) Resource(mobius_dg) - clean completed successfully. 2013/10/30 22:37:24 VCS ERROR V-16-2-13027 (XXXXX) Resource(mobius_dg) - monitor procedure did not complete within the expected time. 2013/10/30 22:37:24 VCS ERROR V-16-2-13077 (XXXXX) Agent is unable to offline resource(mobius_dg). Administrative intervention may be required. Background - On this cluster we have large number of disks and worth of 54 TB data. DG-NAME #VD (GB) TOTAL used free mobius 176 14031.25 14000.00 31.25 vdaappdg 534 42596.69 40628.76 1967.93 While VCS fail-over happens it simply hangs! and says "Agent is unable to offline resource(vdrapp_vol). Administrative intervention may be required." As far as I understand, this message displays when an offline procedure does not complete on time. An offline procedure timeout can occur when the system is overloaded, is busy processing a system call, or is handling a large number of resources. I wanted to know if someone has ever gone through such a situation & if someone can advice if this is happening due to large number of storage?? Waiting for experts advice and possibly solution in order to make sure fail-over functionality works seamlessly. Thank you/NileshSolved2.7KViews2likes6Comments
New set of articles about troubleshooting the "failed" disk status, as reported by vxdisk
Hi, all. We have released a set of articles that contain information about troubleshooting the "failed" disk status, as reported by vxdisk. Here is the link: "Failed" or "failed was" is reported by vxdisk http://www.symantec.com/docs/TECH200618 Since this is a broad topic, the "technote" is actually a set of about a dozen article that have been organized into a logical tree structure, with TECH200618 at its "root." Let us know what you think! Regards, Mike498Views2likes0Comments
not able to initialize the disk
I had a disk under VxVM control. I removed it from VxVM control. Again when I added the same disk, it is not allowing me to initialize .Also I feel, it is showing wrong multipaths in vxdisk list output. root@dbpdadc42> vxdisksetup -i c0t500507680140533Ad8 VxVM vxdisksetup ERROR V-5-2-3523 c0t500507680140533Ad8: Disk is in use root@dbpdadc42> vxdisk list c0t500507680140533Ad8 Device: c0t500507680140533Ad8s2 devicetag: c0t500507680140533Ad8 type: auto info: format=none flags: online ready private autoconfig invalid pubpaths: block=/dev/vx/dmp/c0t500507680140533Ad8s2 char=/dev/vx/rdmp/c0t500507680140533Ad8s2 Multipathing information: numpaths: 4 c1t500507680130064Ad10s2 state=enabled c1t500507680130533Ad10s2 state=enabled c0t500507680140064Ad10s2 state=enabled c0t500507680140533Ad10s2 state=enabledMigrating VxVM volumes from a V240 to a T4-2 Ldom
Hi all, I have a V240 running Solaris 10U08 with VxVM 6.0.000 that I need to migrate to a Solaris T4-2 Ldom (LDM 3.1). I have loaded the software that is in source onto the LDOM and presented the required SAN LUNs that match source into the guest LDOM but when I try to set up a disk (LUN) in VxVM using vxdisksetup I get: "ERROR V-5-2-43 c0d3: Invalid disk device for vxdisksetup". I have tried using vxdisk init c0d3s2and get: "Disk sector size is not supported" and tried vxdisk init c0d3s2 format=sliced and get: "Disk VTOC does not list private partition"Don't know xhat else to try !!!New set of articles about troubleshooting the "failed" disk status, as reported by vxdisk
Hi, all. We have released a set of articles that contain information about troubleshooting the "failed" disk status, as reported by vxdisk. Here is the link: "Failed" or "failed was" is reported by vxdisk http://www.symantec.com/docs/TECH200618 Since this is a broad topic, the "technote" is actually a set of about a dozen article that have been organized into a logical tree structure, with TECH200618 at its "root." Let us know what you think! Regards, Mike