What is the VDID
VOM uses the VDID obtained from VxVM to identify the array as so has identifed an Hitachi USP-V (actually the USPis rebadged as StorageTek 9990V) as: HITACHI_R600_SerialNo This is not useful as I don't know what R600 means, so I am trying to understand what the VDID is. I have looked in: SF admin VOM users VOM Install VOM Add-ons User But I can't find any definitions in these. I could only find an old VOM windows guide reference to it -http://sfdoccentral.symantec.com/vom/4.0/win_unix/html/vom_winadm_addon_users/SFW_VOM40/ch04s03s13.htm which says: The Veritas Disk ID (VDID) is a string that contains information that can identify the array that a disk is contained in. The VDID string is shown in the GUI as a part of the display of information for disks. The VDID string is also shown as a result of thevxdisk diskinfoand thevxdisk listCLI commands. The format of the VDID string varies by array manufacturer and array model. The details of how to interpret the VDID string for a particular array are in an appendix. and the next page gives a table for format of VDID Strings for Various Arrays including Hitachi 9960, 9970, 9980, 9200, 9500,7700,USP HITACHI_{Model}_{EnclosureID}_{CU}_{ LogicalDeviceID } Hitachi other models WWWN+LUNID vxdisk list does not give VDID (and vxdisk diskinfo is Windows syntax), but I can get VDID from vxlist whichshows: Enclosure: hitachi_usp-v0 Status: connected Model: HITACHI Revision: 6008 Array Type: A/A Serial Number: SerialNo ASL: name=libvxhdsusp.so version=vm-6.1-rev-1 I/O Policy: default=MinimumQ current=MinimumQ Partition Size: default=512 current=512 Recovery Option: Throttle cur=Nothrottle[0] def=Nothrottle[0] Error-Retry cur=Timebound[300] def=Timebound[300] Failover Policy: default=Global current=Global Redundancy: default=0 current=0 Disk Count: 241 Path Count: 482 VDID: HITACHI_R600_SerialNo Target Ports: 5,5,6,6 As I understand, in vxdmpadm, the enclosure name is the enclosure type appended with a number (0, 1, 2 etc) so the enclosue is unqiue within the host, but not between hosts, so I understand the need to a unique identifier, but it would seem sensible to justappend the serial number to the enclosure name. So where can I find a recent definition for VDID on UNIX so I can find out whatR600 means - perhaps this is the Enclosure_id - are there any vxvm commands I can run to obtainEnclosure_id Thanks MikeSolved1.2KViews2likes3CommentsSupport using SFHA 6.1 for Java GUIs
Can Symantec clarify Support for SFHA 6.1 for Java GUIs: "Veritas Enterprise Administrator 3.4.30READ ME (Solaris)"fromhttps://www4.symantec.com/Vrt/offer?a_id=89446 says: SUPPORTED PLATFORMS ----------------------------------- Operating Systems (OS): Solaris Sparc OS Versions : 8, 9, 10 BASE PRODUCT VERSIONS (Install this package only on following base versions) ----------------------------------- * Veritas Storage Foundation 4.1, 5.0, 5.1, 6.0 and its minor releases (Minor releases include Service packs, Maintenance packs, Rolling patches etc.) So support is not listed for 6.1, however the SFHA install guide for 6.1 Solaris says: The Veritas Enterprise Administrator (VEA) console is no longer packaged with Storage Foundation products. If you want to continue using VEA, a software version is available for download from http://www.symantec.com/operations-manager/support. Symantec Storage Foundation Management Server is deprecated. If you want to manage a single cluster using Cluster Manager (Java Console), a version is available for download fromhttp://www.symantec.com/operations-manager/support. You cannot manage the new features of this release using the Java Console. Symantec Cluster Server Management Console is deprecated. So this is saying both VEA and Java GUI are supported and VCS Java GUI does not support new features, but the same is not said about VEA. So can you answer the following: Is management of SF 6.1 for UNIX/Linux supported with the UNIX/Linux VEA3.4.30 client Is management of SF 6.1 for UNIX/Linux supported with the Windows VEA3.4.35 client CanUNIX/Linux/Windows VEA clients be used to manage new features introduced in SF 6.1 Is management of VCS 6.1 for UNIX/Linux supported with the UNIX/Linux VCS Java Console 6.0.1 client Is management of VCS 6.1 for UNIX/Linux supported with the Windows VCS Java Console 6.0.1 client Is simultating 6.1 VCSUNIX/Linux clusters supported in the WindowsVCS Simulator 6.1client Thanks Mike1.9KViews2likes5Commentswould vxvm mirroring activities take lower priority than normal write activity before it is synced up?
hi, I have a question here, hoping someone could point out perhaps. is a vxvm mirroring event (before it is sync-ed up) takes lower priority than a normal I/O data write? the reason I am asking is because if during vxvm mirror setup, would it slow down normal data I/O it would make sense to lower the priority of these writes than normal data I/O I would think. thanks in advance.Solved859Views3likes1CommentDMP i/o error
Urgent...!!!! While runnung script the veritas command vxdiskadm -o allgs got stuck. My OS is running VVM and VCS. I tried to run manually and it is hanging. /var/adm/messages showing below error messages. My peers suggetion is to reboot the server. Can you suggest any other way to resolve this issue? vxdmp: [ID 443116 kern.notice] NOTICE: VxVM vxdmp V-5-0-0 i/o error occured (errno=0x0) on dmpnode 267/0x28422.3KViews0likes6CommentsTroubleshooting volume performance in Storage Foundation
Hi, all. We have released a set of articles about troubleshooting volume performance in Storage Foundation. Here is the link: "Troubleshooting volume performance in Veritas Storage Foundation" http://www.symantec.com/docs/TECH202712 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 TECH202712 at its "root." Let us know what you think! Regards, Mike754Views3likes0CommentsNew 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