cannot configure vxfen after reboot
Hello, We move physically a server, and after reboot, we cannot configure vxfen. # vxfenconfig -c VXFEN vxfenconfig ERROR V-11-2-1002 Open failed for device: /dev/vxfen with error 2 my vxfen.log : Wed Aug 19 13:17:09 CEST 2015 Invoked vxfen. Starting Wed Aug 19 13:17:23 CEST 2015 return value from above operation is 1 Wed Aug 19 13:17:23 CEST 2015 output was VXFEN vxfenconfig ERROR V-11-2-1041 Snapshot for this node is different from that of the running cluster. Log Buffer: 0xffffffffa0c928a0 VXFEN vxfenconfig NOTICE Driver will use customized fencing - mechanism cps Wed Aug 19 13:17:23 CEST 2015 exiting with 1 Engine version 6.0.10.0 RHEL 6.3 any idea to help me running the vxfen (and the had after ... ) ?6KViews0likes7CommentsSF5.1 VxDMP caches LUN size?
I recently recrated a LUN with a different size but the same LUN ID (Linux SLES11) and when trying to initialize it as a new disk to VxVM I keeps sticking to the old size, whatever I do (I tried to destroy and reinitialize in different formats and grow many times): # vxdisk list isar2_sas_1 Device: isar2_sas_1 public: slice=5 offset=65792 len=167700688 disk_offset=315 Multipathing information: numpaths: 8 sdu state=disabled sdt state=enabled sds state=disabled sdam state=disabled sdan state=enabled sdb state=enabled sda state=disabled sdv state=enabled ... but the main reasons seems to be DMP is somehow sticking to the old size: # fdisk -l /dev/vx/dmp/isar2_sas_1 Disk /dev/vx/dmp/isar2_sas_1: 85.9 GB, 85899345920 bytes 255 heads, 63 sectors/track, 10443 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x55074b8b pepper:/etc/vx # fdisk -l /dev/sdt Disk /dev/sdt: 128.8 GB, 128849018880 bytes 255 heads, 63 sectors/track, 15665 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x55074b8b Any hints are greatly appreciated :)SolvedBuilding NetBackup Global Cluster with VVR Option... need main.cf
Hello, I am trying to build a global cluster with VVR option. Where i have one NetBackup cluster in Site A with two nodes and one Netbackup Cluster in Site B with single node. I know how to do replication manually for the catalog but would like to add it to global cluster configuration to automate everything. I would appreciate if anyone can share the details what services need to be modified or new service group need to be created to accomodate replication part. If i can have a working main.cf for the above solution it will be really helpfull. Best Regards4.6KViews0likes4Commentsdmp 5.1SP1PR2 installation prevents RHEL 6.4 server to boot
Hello All, The dmp 5.1SP1PR2 installation is completing but it unable to start it. getting follwing error Veritas Dynamic Multi-Pathing Startup did not complete successfully vxdmp failed to start on ddci-oml1 vxio failed to start on ddci-oml1 vxspec failed to start on ddci-oml1 vxconfigd failed to start on ddci-oml1 vxesd failed to start on ddci-oml1 It is strongly recommended to reboot the following systems: ddci-oml1 Execute '/sbin/shutdown -r now' to properly restart your systems After reboot, run the '/opt/VRTS/install/installdmp -start' command to start Veritas Dynamic Multi-Pathing installdmp log files, summary file, and response file are saved at: after reboot also it is not starting. i installed sfha-rhel6_x86_64-5.1SP1PR2RP4 rolloing patch and took a reboot, the server is stuck to start during the boot process. i am seeing the error messages from the console as below vxvm:vxconfigd: V-5-1-7840 cannot open /dev/vs/config: Device is already open ln: creating symbolic link '/dev/vx/rdmp/dmp'file exits /bin/mknod/ '/dev/vx/config': File exits . . . Loading vxdmp module Loading vxio module Loading vxspec module the server is stuck at here also i cannot take it to single user mode for trouble shooting. Kindly help me on this issue. Thanks and regards UvSolvedUnable to boot RHEL 6.3 server after installing DMP 5.1 SP1 RP2
Dear Gents, I have recently installed DMP 5.1 SP1 RP2 on a rhel 6.3 os x86_64, after the installation when i took a reboot the system got hung during the boot time. i found the follwoing error message from teh console. "this release of vxted doesnot contain any moduels which are suitable for your 6.6.32-279.el6.x86_64 kernel. error reading module 'vxdmp'see documentation. i have found that there is an another release SFHA 5.1 SP1PR2RP4 and installed that too to verify but no luck. in my enviroment i need to install DMP 5.1 SP1 RP2 on a rhel 6.3 os x86_64 Os. any help much appreciated. Thanks. UvSolvedVxDMP and SCSI ALUA handler (scsi_dh_alua)
Hi, I have an question on scsi alua handler and VxDMP on Linux. we have a scsi_dh_alua handler on linux, which can handle the ALUA related check conditions sent from target controllers. so this will be handled by scsi layer itself and will not be propogated to the upper layers. So do we have anything simalar with VxDMP to handle the ALUA related errors reported by scsi layer or does it depend on scsi_dh_alua handler to handle the ALUA related check condions from target and retry at the scsi layer it self ??? Thanks, Inbaraj.Solvedbulk transfer?? block size??
About bulk transfer with secondary logging To effectively use network bandwidth for replication, data is replicated to a disaster recovery (DR) site in bulk at 256 KB. This bulk data transfer reduces VVR CPU overhead and increases the overall replication throughput. With compression enabled, bulk data transfer improves the compression ratio and reduces the primary side CPU usage. question 1.Smaller than 256k did before? 2.Did you send compressed 256k?Solved2.9KViews0likes1CommentSymantec Application HA 6.2 - ERROR V-16-1-52577 [Licensing] Unable to find a valid base VCS license key
Hi, I had just installed the Symantec Application HA using a trial license key but Im getting an error while trying to start the engine. Here is the engine log: 2015/07/13 23:16:19 VCS INFO V-16-1-51138 Number of processors configured on this system are 8 2015/07/13 23:16:19 VCS WARNING V-16-1-51140 In a multi-CPU system, configure an adequately high value for the ShutdownTimeout attribute. This ensures that when a system panics, its service groups successfully fail over to other systems. For more information, refer to the VCS Administrator's Guide 2015/07/13 23:16:19 VCS INFO V-16-1-10118 GAB timeout set to 30000 ms. GAB peak load timeout set to 30000 ms. 2015/07/13 23:16:19 VCS INFO V-16-1-10077 Received new cluster membership 2015/07/13 23:16:19 VCS NOTICE V-16-1-10112 System (rh7) - Membership: 0x1, DDNA: 0x0 2015/07/13 23:16:19 VCS NOTICE V-16-1-10086 System rh7 (Node '0') is in Regular Membership - Membership: 0x1 2015/07/13 23:16:19 VCS NOTICE V-16-1-10322 System rh7 (Node '0') changed state from CURRENT_DISCOVER_WAIT to LOCAL_BUILD 2015/07/13 23:16:20 VCS NOTICE V-16-1-10322 System rh7 (Node '0') changed state from LOCAL_BUILD to RUNNING 2015/07/13 23:16:20 VCS ERROR V-16-1-52577 [Licensing] Unable to find a valid base VCS license key (Local Build) 2015/07/14 13:23:27 VCS INFO V-16-1-10196 Cluster logger started 2015/07/14 13:23:27 VCS NOTICE V-16-1-11022 VCS engine (had) started 2015/07/14 13:23:27 VCS NOTICE V-16-1-11050 VCS engine version=6.2 2015/07/14 13:34:34 VCS INFO V-16-1-10196 Cluster logger started 2015/07/14 13:34:34 VCS NOTICE V-16-1-11022 VCS engine (had) started 2015/07/14 13:34:34 VCS NOTICE V-16-1-11050 VCS engine version=6.2 2015/07/14 13:34:34 VCS NOTICE V-16-1-11054 VCS engine join version=6.2.0.000 The error is this one: 2015/07/13 23:16:20 VCS ERROR V-16-1-52577 [Licensing] Unable to find a valid base VCS license key (Local Build) # ./hastatus attempting to connect.... VCS ERROR V-16-1-10600 Cannot connect to VCS engine attempting to connect....not available; will retry These are the licenses I have: [root@rh7 bin]# vxlicrep Symantec License Manager vxlicrep utility version 3.02.62.003 Copyright (C) 1996-2014 Symantec Corporation. All rights reserved. Creating a report on all VERITAS products installed on this system -----------------********* ********** ****------ ---------- - License Key = AJZU-PX6K-3K7U-R4MR-XXXX-X XXX-XXXX-X XXX-P Product Name = VERITAS Storage Foundation Basic Serial Number = 1436 License Type = PERMANENT OEM ID = 2006 Site License = YES Editions Product = YES Features := VxVM#VERITAS Volume Manager = Enabled CPU Count#VERITAS Volume Manager = Not Restricted VXFS#VERITAS File System = Enabled CPU Count#VERITAS File System = Not Restricted QLOG#VERITAS File System = Enabled PGR#VERITAS Volume Manager = Enabled VERITAS Storage Foundation Basic = Enabled Storage Expert#VERITAS Volume Manager = Enabled Platform = un-used Version = 6.2 Maximum number of volumes#VERITAS Volume Manager = 4 Volumes Maximum number of file systems#VERITAS File System = 4 File Systems -----------------********* ********** ****------ ---------- - Product Name = VERITAS Volume Manager License Type = PERMANENT Features := Dynamic Lun Expansion = Enabled Hardware assisted copy = Enabled Cross-platform Data Sharing = Enabled PGR = Enabled PGR_TRAINING = Enabled RAID5SNAP = Enabled -----------------********* ********** ****------ ---------- - Product Name = VERITAS File System License Type = PERMANENT Features := File Change Log = Enabled Cross-platform Data Sharing = Enabled Extra-Big File Systems = Enabled Multi-Volume Support = Enabled -----------------********* ********** ****------ ---------- - License Key = AJZU-WONB-DDH2-8OZE-XXXX-X XXX-XXXX-X XXX-P Product Name = VERITAS Volume Manager Serial Number = 1436 License Type = PERMANENT OEM ID = 2006 Site License = YES Point Product = YES Features := Storage Expert = Enabled VxVM = Enabled CPU Count = Not Restricted PGR = Enabled Platform = un-used Version = 6.2 Maximum number of volumes = 4 Volumes -----------------********* ********** ****------ ---------- - License Key = AJZU-BNZK-D37O-P4OL-XXXX-X XXX-XXXX-X XXX-6 Product Name = VERITAS File System Serial Number = 1436 License Type = PERMANENT OEM ID = 2006 Site License = YES Point Product = YES Features := VXFS = Enabled QLOG = Enabled CPU Count = Not Restricted Platform = un-used Version = 6.2 Maximum number of file systems = 4 File Systems ========================== ========== ========== ======= I have already tried to reinstall the license.. but no luck.. # cp -pR /etc/vx/licenses/lic /etc/vx/licenses/lic_bkp # cd /etc/vx/licenses/lic # rm *.vxlic # /opt/VRTS/bin/vxlicinst ( Install the license key ) ======= Any suggestion? The OS is RHEL7.1 Tks, Joao2.6KViews0likes1CommentHow to write udev rules for persistent device name for DMP subpaths?
Hi experts, I'm using SFRAC 6.0.3 on Oracle Linux 5.8 with Oracle storage (2 HBA cards, 4 paths) and would like to make the DMP subpaths persistent after rebooting. I knew that for single path I can write the following udev rule: KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -s %p", RESULT=="<scsi_id>", SYMLINK+="<your_disk_name>%n" But it didn't work for multipath... Anyone can help on this issue? Thanks in advance... Thanks and Regards, Kiluwa