Sponsored Content
Full Discussion: live upgrade SUN cluster
Operating Systems Solaris live upgrade SUN cluster Post 302557999 by alex57 on Friday 23rd of September 2011 11:01:04 AM
Old 09-23-2011
good enough, thank you very much

---------- Post updated at 12:17 PM ---------- Previous update was at 11:59 AM ----------

The following example shows the names of DID device d3s3, which corresponds to /global/.devices/node@2, changed to its physical device names and the global entry removed:

Original:/dev/did/dsk/d3s3 /dev/did/rdsk/d3s3 /global/.devices/node@2 ufs 2 no globalChanged:dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s3 /global/.devices/node@2 ufs 2 no -

this is from doc. When I changed to slices, what disk do I have to use primary or alternative?

Thank you

---------- Post updated 09-23-11 at 10:01 AM ---------- Previous update was 09-22-11 at 12:17 PM ----------

in the beginning of doc it says to take SG offline and disable it, but in the liveupgrade it says to move to another node, so I can't decide what is the best solution. Also, what is the diff if I comment global entries in vfstab file or change them for local devices?
 

8 More Discussions You Might Find Interesting

1. High Performance Computing

SUN Cluster Vs Veritas Cluster

Dear All, Can anyone explain about Pros and Cons of SUN and Veritas Cluster ? Any comparison chart is highly appreciated. Regards, RAA (4 Replies)
Discussion started by: RAA
4 Replies

2. Solaris

Live upgrade Issue

Hi, I upgraded solaris 10 x86 from update 3 to update 7 with zones installed n UFS file system . The global zone was updated but the non global zone still shows update 3 what could be the reason for this and how can i update the local zones to update 7 (0 Replies)
Discussion started by: fugitive
0 Replies

3. Solaris

Sun Live Upgrade - lucreate fails

Hi, I currently have one BE and would like to create an ABE. # lustatus BE_name Complete Active ActiveOnReboot CopyStatus ------------------------------------------------------------------------ coolthreads yes yes yes - But... (3 Replies)
Discussion started by: pgarousi
3 Replies

4. Solaris

Sun cluster and Veritas cluster question.

Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC. Am thinking how to migrate to sun cluster setup instead. My plan as follows leave the existing vcs intact as a fallback plan. Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies

5. Solaris

Live upgrade question

I want to basically update an ABE that someone created a few months back. I'm sure stuff has changed since it was made, and I was going to delete it and create a new one. But from what I'm looking at, the lumake appears like it would be a faster approach. I want to use live upgrade to... (0 Replies)
Discussion started by: BG_JrAdmin
0 Replies

6. Emergency UNIX and Linux Support

Live Upgrade Query

I am upgrading Solaris-9 Update-7 to Solaris-9 Update-9 through live upgrade. I am able to create another boot environment and have OS DVD inside server. But i am confused for, what command/path should I give for luupgrade. OS DVD is mounted on /mnt Boot environments are Solaris9old (Active now)... (2 Replies)
Discussion started by: solaris_1977
2 Replies

7. Solaris

Sun cluster 4.0 - zone cluster failover doubt

Hello experts - I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts. (1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over) (2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies

8. Solaris

Live upgrade first steps

Hello Guys, I am a little confused about the first step in the live upgrade process. I will be glad if someone can clarify this for me. The pre-live upgrade patch, when do you add this patch to the OS you want to upgrade? 1. before creating the new boot environment? or 2. after creating... (1 Reply)
Discussion started by: cjashu
1 Replies
pcata(7D)																 pcata(7D)

NAME
pcata - PCMCIA ATA card device driver SYNOPSIS
pcata@socket#:a -u pcata@socket#:a -u,raw The PCMCIA ATA card device driver supports PCMCIA ATA disk and flash cards that follow the following standards: o PC card 2.01 compliance (MBR+fdisk table required for all platforms). o PC card ATA 2.01 compliance. o PC card services 2.1 compliance. The driver supports standard PCMCIA ATA cards that contain a Card Information Structure (CIS). For PCMCIA, nodes are created in /devices that include the socket number as one component of the device name referred to by the node. However, the names in /dev, /dev/dsk, and /dev/rdsk follow the current conventions for ATA devices, which do not encode the socket number in any part of the name. For example, you may have the following: +------------------------+---------------------------+---------------------+ | Platform | | | +------------------------+---------------------------+---------------------+ |/devices name | | | +------------------------+---------------------------+---------------------+ +------------------------+-/dev/dsk-name-------------+---------------------+ |/devices/isa/pcic@1,3e0 | | | +------------------------+---------------------------+---------------------+ |/disk@0:a | | | +------------------------+---------------------------+---------------------+ +------------------------+-/devices/iommu@f,e0000000-/sbus@f,e0001000-/SUNW, pcmcia@3,0 /disk@0:a |SPARC | | /dev/dsk/c1d0s0 | | | | | | | | | +------------------------+---------------------------+---------------------+ PRECONFIGURATION
If a PC Card ATA device is recognized, the pcata driver is automatically loaded, IRQs allocated, devices nodes created, and special files created (if they do not already exist). Known Problems and Limitations o vold does not support pcata. File systems must be mounted manually. o You need to umount the file system before removing the disk. o The ufs file systems on removable media (PC Card ATA) should have one of the onerror={panic, lock, umount} mount options set. CONFIGURATION
Configuration topics include initial installation and configuration, identifying an unrecognized device, special files and hot-plugging. Initial Installation and Configuration 1. Install the Solaris software. 2. Boot the system. 3. Insert the PC card ATA device. Identifying an Unrecognized Device If you insert a PC card ATA device and it is not recognized (no special files created), use the prtconf command to identify the problem. 1. Run the prtconf -D command to see if your pcata card is recognized. (A recognized device will appear at the end of the prtconf output. For example: # prtconf -D . . . pcic, instance #0 (driver name: pcic) . . . disk, instance #0 2. If pcata does not appear in the prtconf output, there is a problem with the PC card adapter configuration or with the hardware. Check to see whether the problem is with the card or the adapter by trying to use the card on another machine and by seeing if it works on the same machine using DOS. Special Files For PC card devices, nodes are created in /devices that include the socket number as one component of a device name that the node refers to. However, the /prtc/dev names and the names in /dev/dsk and /dev/rdsk do follow the current convention for ATA devices, which do not encode the socket number in any part of the name. Hot-Plugging o If you want to remove the disk, you must unmount the file system. o Use the mkfs_pcfs(1M) command to create a pcfs file system: # mkfs -F pcfs /dev/rdsk/c#d#p0:d o To mount a pcfs file system, type: # mount -F pcfs /dev/dsk/c#d#p0:c /mnt o If you want to create a ufs file system, use the newfs command and type: # newfs /dev/rdsk/c#d#s# o To mount a ufs file system, type: # mount -F ufs /dev/dsk/c#d#s# /mnt o To create a Solaris partition, run the format command and go to the Partition menu. For more information, see the format(1M) man page. /kernel/drv/pcata pcata driver See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE | +-----------------------------+-----------------------------+ |VALUE | | +-----------------------------+-----------------------------+ |Availability |SUNWpsdpr | +-----------------------------+-----------------------------+ format(1M), mount(1M), newfs(1M), pcmcia(7D), attributes(5), pcfs(7FS) 20 Oct 2000 pcata(7D)
All times are GMT -4. The time now is 05:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy