By default, the upgrade changes the naming from osn ( os native ) to ebn ( enclosure based ). Additionally, disk_0 will not necessarily be c0t0d0s2, it could be c0t1d0s2. Run the following command and see if this clears up some of the confusion:
vxddladm set namingscheme=osn persistence=yes lowercase=yes use_avid=yes Hope this helps. Good luck ! ________________________________ From: veritas-vx-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of Asiye Yigit Sent: Wednesday, October 06, 2010 11:29 AM To: hud...@hra.nyc.gov; ger...@gotadsl.co.uk; veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] couldn't encapsulate boot disk Hello, I am really aware of zfs and other features. Just test purpose I am trying to do boot disk encapsulation. I think it is still supported on this system. ________________________________ From: Hudes, Dana To: Asiye Yigit; Christian Gerbrandt ; veritas-vx@mailman.eng.auburn.edu Sent: Wed Oct 06 17:45:29 2010 Subject: RE: [Veritas-vx] couldn't encapsulate boot disk don't do it. There is no longer, with a Solaris 10 system such as your 5120, a valid reason to use VERITAS boot disk encapsulation. Use ZFS. As I recall the 5120 has hardware mirroring so you could use that or you could use ZFS mirroring. The advantage of hardware mirroring is that it doesn't come up to the OS -- but a 5120 has enough CPUs to deal with mirroring. Managing the mirror with ZFS gives you more ready access via fmadm to any disk errors rather than having them buried behind the raid controller. Use Solaris 10, preferably update 9, and ZFS for your boot. This is also very important for zones and for Live Upgrade. VERITAS has its advantages in some situations for managing data disks (for example, raw volumes and Oracle if you have an ODM license), especially older Oracle releases (all of which are certified to work on Solaris 10). LU will make ZFS snapshots and clones if you have a ZFS boot disk. If you have VERITAS-encapsulated it will first unencapsulate the boot slice. VERITAS boot encapsulation also lacks a mirrored dump device: since Vx doesn't have the API for dump, you have to give the underlying swap slice. Lose that disk lose your dump device. Vx requires swap is a slice, it's fixed in size until you manually go in and grow that slice -- if you left room on your root disk to do that operation. ZFS root, by contrast, uses a zvol for dump and a zvol for swap. They are sparse devices only using space when needed. Of course that means you can fill your entire root disk and leave nothing for dump or swap -- so you could also just create them as regular zvols with nailed-up space which you can shrink and grow manually as desired without worrying that you left room in your disk layout. boot encapsulation was the thing to do on Solaris 8 and 9. Not 10. ________________________________ From: veritas-vx-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of Asiye Yigit Sent: Wednesday, October 06, 2010 10:18 AM To: Christian Gerbrandt; veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] couldn't encapsulate boot disk Hello; Disk is okay. I know it should be online invalid. For both T5120 systems, the problem is same. I have many disk from san and two disks internal. For the boot disk, for both system, it says error state. Disks are okay physically. There may be some point patch for SF 5.1RP2 for boot disk mirroring? From: Christian Gerbrandt [mailto:ger...@gotadsl.co.uk] Sent: Wednesday, October 06, 2010 5:17 PM To: Asiye Yigit; veritas-vx@mailman.eng.auburn.edu Subject: RE: [Veritas-vx] couldn't encapsulate boot disk As you can see, disk_2 is showing in 'error' state. But it should show as 'online invalid'. There seems to be an error with the disk. Check the status of the disk from OS/VxVM and SAN. From: veritas-vx-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of Asiye Yigit Sent: 06 October 2010 14:55 To: veritas-vx@mailman.eng.auburn.edu Subject: [Veritas-vx] couldn't encapsulate boot disk Hello; I have installed SP 5.1RP2 on solaris 10 system. I am trying to encapsulate the boot disk and after that I will make mirror. In the vxdisk list, It shows DEVICE TYPE DISK GROUP STATUS disk_2 auto - - error disk_3 auto:none - - online invalid st2540-0_0 auto:none - - online invalid when I try to encapsulate the disk disk_2; it says Select disk devices to encapsulate: [<pattern-list>,all,list,q,?] disk_2 Here is the disk selected. Output format: [Device_Name] disk_2 Continue operation? [y,n,q,?] (default: y) You can choose to add this disk to an existing disk group or to a new disk group. To create a new disk group, select a disk group name that does not yet exist. Which disk group [<group>,list,q,?] rootdg Create a new group named rootdg? [y,n,q,?] (default: y) Use a default disk name for the disk? [y,n,q,?] (default: y) A new disk group will be created named rootdg and the selected disks will be encapsulated and added to this disk group with default disk names. disk_2 Continue with operation? [y,n,q,?] (default: y) This disk device is disabled (offline) and cannot be used. Output format: [Device_Name] disk_2 Hit RETURN to continue. When I try to make online; It says Select a disk device to enable [<disk>,list,q,?] disk_2 VxVM vxdisk ERROR V-5-1-531 Device disk_2: online failed: Device path not valid Enable another device? [y,n,q,?] (default: n) Is there any idea? Best regards;
_______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
