HP3000-L Archives

January 2002, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Ranft <[log in to unmask]>
Reply To:
Mark Ranft <[log in to unmask]>
Date:
Thu, 3 Jan 2002 20:05:57 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (51 lines)
Very shortly, I will be implementing Cluster/iX.  If anyone has any
experience with this product, your assistance and advise would be greatly
appreciated.

Here are some of the items, I am interested in addressing:

IP Address Migration - because I have literally hundreds of users from
dozens of locations connection to the system with NS-VT, TELNET and
Client/Server connections, I feel it would be better and easiest to copy the
NMCONFIG (and other associated network configuration files (SERVICES,
INETDCNF, etc)) to the secondary system rather than ask the users to connect
to an alternate IP address.  I am a little concerned about my ability (or
need) to pre-validate the alternative NMCONFIG files with SYSGEN.  I intend
to use the identical DTS subsystem tree.  Will this work?  Also I plan on
having the original 'secondary system' NMCONFIG file safely tucked away in a
separate group to allow the reset back to being the secondary identity.)

Accounting Structure Migration - BULDACCT will duplicate the user volume set
accounting structure.  It will also set up the Users, the ability to
setcatalog without the UDC files existing still eludes me.  (Unless I put
the UDC group on the MPEXL_SYSTEM_VOLUME_SET.  But this causes other
concerns.).

AutoRestart/iX considerations - So the primary system has a system abort.
AUTORESTART kicks in and does a memory dump to disk and restarts the system.
If I use IP migration, the SYSSTART has to be smart enough to know if the
other system has taken over for it (or not.)

Lastly, here is a rouigh sequence of the steps I intend to take (assuming
the preevious set up considerations are met) :

    1- SXOUTIL - SXOSETLABEL command (part of Cluster/iX)
    2- VSOPEN volset (the secondary system now has access to the volume set.
Obviously the accounting structure for the accounts and groups
    3a - Stop Network jobs including STMSHUT.DIAG
    3b- NETCONTROL and NSCONTROL STOPs (and ABORT)
    4- COPY NMCONFIG.PRIMARY,NMCONFIG.PUB
    5a-  NETCONTROL and NSCONTROL STARTS
    5b- STMSTART.DIAG
    6-   Start up background Socket listener applicatons
    7-  LIMITs UP

I am sure I am missing a few things.  Any and all comments and suggestions
will be welcome.

Mark Ranft
[log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2