headers
Rich Glazier | 5 Feb 2009 03:58
Picon
Favicon

migrating boot disk (root_domain) from one EVA to another

5.1A PK6, DS20E, EVA5000

Managers,

I know that the root domain is the only domain in AdvFS that you can not add a volume to.  We are migrating our
storage from an old EVA5000 to a new EVA8100, and I've been using addvol/rmvol to accomplish this for the
non root domains. 

    (presented a new lun from the 8100, labeled it, added the volume into the domain (addvol), and
removed the 
    old 5000 volume from the domain (rmvol)).

I can not do this for the bootable root disk; I boot off the SAN.  I need to migrate the root_domain another
way.  Here was my plan.  Please see if this seems sounds.  If there's a better way to do it, or if anyone
has done it, please let me know.

- present new root lun from 8100
- hwmgr sc sc
- hwmgr sh sc / hwmgr v d  (note Lun # /OSID of new disk)
- disklabel -rw new disk (making it bootable)
- mkfdmn /dev/disk/dskxx root2_domain
- mkfset root2_domain root
- mkdir /root2
- mount root2_domain#root /root2
- shutdown system application
- vdump -0f - / | vrestore -xf - -D /root2
- change system to not reboot
    - consvar -s auto_action HALT
    - consvar -l (see that it changed)
    - consvar -a (write it to NVRAM)
(Continue reading)

Permalink | Reply | 2 comments |
headers
Dave Sill | 9 Feb 2009 18:57
Picon

Administrivia: Tru64-UNIX-Managers information and policy statement

EVERYONE WHO RECEIVES THIS MESSAGE HAD BETTER READ IT THOROUGHLY.

Tru64-UNIX-Managers Information and Rules

This message is a summary of the Tru64-UNIX-managers charter and rules.
Failure to adhere to these guidelines may result in severe chastisement by
the list maintainer and other list participants. Retain a copy of this
statement and refer to it before submitting messages to the list or the list
administrator.

Last modified: 2002-10-09                                                     |

  1. Send only HP Tru64 UNIX (formerly Compaq Tru64 UNIX (formerly            |
     Digital UNIX (formerly Digital OSF/1))) system management questions and  |
     summaries to tru64-unix-managers <at> ornl.gov. Include your return address in
     the body of your message so people can reply directly to you. Avoid MIME
     and HTML--many people can't read them.

  2. This list is not moderated! Every message that is sent to the list will
     be passed on to every member of the list (with a few small exceptions).

  3. This mailing list is managed by a utility called Majordomo. You can
     subscribe to the list by sending a message like:

           subscribe tru64-unix-managers

     to majordomo <at> ornl.gov.

     Likewise, if you want to remove yourself from the list, send the
     message:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rich Glazier | 10 Feb 2009 23:40
Picon
Favicon

SUMMARY: migrating boot disk (root_domain) from one EVA to another

Thanks to Jean-marc, DAvid, Thomas, Johan, Bruce, Chris, Jason, and Bluejay.

The procedure I used, that worked, was...

- present new root lun from 8100
- hwmgr sc sc
- hwmgr sh sc / hwmgr v d  (note Lun # /OSID of new disk)
- disklabel -rw –tadvfs /dev/rdisk/dskxxa (making it bootable)
- start exceed / export display / start diskconfig 
    - partition a as advfs, and h as swap
- mkfdmn –r /dev/disk/dskxxa root2_domain
- mkfset root2_domain root
- mkdir /root2
- mount –tadvfs root2_domain#root /root2
- shutdown system application
- vdump -0f - / | vrestore -xf - -D /root2
- check /etc/sysconfigtab for swap disks.  Remove old ones, put disk part in.
- bring to single user mode(init s)
- add to fstab file so that root2_domain#root mounts to / 
- change fstab file so that root_domain#root is renamed to oldroot_domain#root mounted to /oldroot
- mkdir /oldroot
- change root_domain to oldroot_dominan in /etc/fdmns
- halt system (shutdown -h) to SRM prompt, show old boot device
    -  P00>>> show bootdef_dev  (pga...)
- go into wwidmgr and quickset to new lun paths
    -  P00>>> init
    -  P00>>> wwidmgr -show wwid  (take note of old boot disks)
-    P00>>> wwidmgr -clear all
    -  P00>>> wwidmgr -show wwid   (find UDID that matches OSID from lun on 8100)
    -  P00>>> init
(Continue reading)

Permalink | Reply | 1 comment |
headers
Rich Glazier | 16 Feb 2009 21:59
Picon
Favicon

SUMMARY:CORRECTION migrating boot disk (root_domain) from one EVA to another

Make sure you are in the new /etc when editing files for the new boot disk (in this case /root2/etc/...)

----- Original Message ----
From: Rich Glazier <rglazier2002 <at> yahoo.com>
To: tru64-unix-managers <at> ornl.gov
Sent: Tuesday, February 10, 2009 3:40:09 PM
Subject: SUMMARY: migrating boot disk (root_domain) from one EVA to another

Thanks to Jean-marc, DAvid, Thomas, Johan, Bruce, Chris, Jason, and Bluejay.

The procedure I used, that worked, was...

- present new root lun from 8100
- hwmgr sc sc
- hwmgr sh sc / hwmgr v d  (note Lun # /OSID of new disk)
- disklabel -rw –tadvfs /dev/rdisk/dskxxa (making it bootable)
- start exceed / export display / start diskconfig 
    - partition a as advfs, and h as swap
- mkfdmn –r /dev/disk/dskxxa root2_domain
- mkfset root2_domain root
- mkdir /root2
- mount –tadvfs root2_domain#root /root2
- shutdown system application
- vdump -0f - / | vrestore -xf - -D /root2
- check /etc/sysconfigtab for swap disks.  Remove old ones, put disk part in.
- bring to single user mode(init s)
- add to fstab file so that root2_domain#root mounts to / 
- change fstab file so that root_domain#root is renamed to oldroot_domain#root mounted to /oldroot
- mkdir /oldroot
- change root_domain to oldroot_dominan in /etc/fdmns
(Continue reading)

Permalink | Reply | 0 comments |
headers
Padiyath Sreekumaran | 21 Feb 2009 17:53
Picon
Favicon

PC SW for X-application

Hi,

I want to open an X-Window application on my MS Windows PC from a Tru64
machine. Which SW I can run on my PC to connect to Tru64 and then run
the X-Application except X-Reflection? I prefer Free SW if possible.

Regards,

Kumar
Permalink | Reply | 0 comments |
headers
Richard Glazier | 24 Feb 2009 00:13
Picon

SWAT root login

Tru64 5.1A PK6

What do I need to be able to do to get SWAT to work?  I can log in
with a non root account, but that's essentially worthless, because all
that really has is man pages.

I have opened root access wide up, putting ptys in /etc/securettys.  I
could then telnet and log in as root, but still refused by Swat.  I
added my IP:0 to /etc/securtetys, but same thing.  Looks for a Swat
samba config file, but no luck.

I can do this on other Unix/Linux servers, but not on Tru64.

Thanks for the help!

Rich G.
Permalink | Reply | 1 comment |
headers
Rich Glazier | 24 Feb 2009 03:07
Picon
Favicon

SUMMARY: SWAT root login

Thank you James Sainsbury 

ad "-a" to /etc/inetd.conf swat entry
       swat stream tcp nowait root /usr/local/samba/sbin/swat swat -a

kill -HUP inetd pid

----- Original Message ----
From: Richard Glazier <glazier <at> gmail.com>
To: tru64-unix-managers <at> ornl.gov
Sent: Monday, February 23, 2009 4:13:31 PM
Subject: SWAT root login

Tru64 5.1A PK6

What do I need to be able to do to get SWAT to work?  I can log in
with a non root account, but that's essentially worthless, because all
that really has is man pages.

I have opened root access wide up, putting ptys in /etc/securettys.  I
could then telnet and log in as root, but still refused by Swat.  I
added my IP:0 to /etc/securtetys, but same thing.  Looks for a Swat
samba config file, but no luck.

I can do this on other Unix/Linux servers, but not on Tru64.

Thanks for the help!

Rich G.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane