Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
HP.com home

HP OpenVMS Systems

Ask the Wizard
» 

HP OpenVMS Systems

OpenVMS information

» What's new on our site
» Upcoming events
» Configuration and buying assistance
» Send us your comments

HP OpenVMS systems

» OpenVMS software
» Supported Servers
» OpenVMS virtualization
» OpenVMS solutions and partners
» OpenVMS success stories
» OpenVMS service and support
» OpenVMS resources and information
» OpenVMS documentation
» Education and training

Evolving business value

» Business Systems Evolution
» AlphaServer systems transition planning
» Alpha RetainTrust program

Related links

» HP Integrity servers
» HP Alpha systems
» HP storage
» HP software
» HP products and services
» HP solutions
» HP support
disaster proof
HP Integrity server animation
Content starts here

Ask the Wizard Questions

Cluster: Satellite boot problem

The Question is:

Satellite node will not boot.  The message on the satellite
node's console is "Invalid satellite SCSSYSTEMID parameter".
Decnet messages from OPCOM which display on the load host
console show a request for load from the satellite, a
succesful load and less than one second later a
"Line open error, line communication error -
SYSTEM-F-TIMEOUT, device timeout.

MR/MS. WIZARD:  Please help.


The Answer is:


	From the boot server for this satellite execute the following
$ MCR NCP SHOW NODE {satellite} CHARA

From this you will see it's DECNET address and the system root at which
this system is supposed to boot .  It will look something like this

Node Volatile Characteristics as of  6-FEB-1996 16:50:11

Remote node =   28.384 (XXXXXX)

Hardware address         = 08-00-2B-0D-05-7D
Tertiary loader          = SYS$SYSTEM:TERTIARY_VMB.EXE
Load Assist Agent        = SYS$SHARE:NISCS_LAA.EXE
Load Assist Parameter    = SYS$SYSDEVICE:

So this node XXXXXX boots from the disk pointed to by the boot servers
SYS$SYSDEVICE logical and root SYS7.  The SYSGEN SCSSYSTEMID should be
(28*1024)+384 or 29056.  Now see if this is what is really there.

$ SET DEF SYS$SYSDEVICE:[SYS7.SYSEXE]
$ MCR SYSGEN
USE VAXVMSSYS.PAR
SHOW SCSNODE
SHOW SCSSYSTEMID

In the CURRENT column you should have 29056 for SCSSYSTEMID and XXXXXX in
the SCSNODE column.  If you don't then continue with the following while
still in SYSGEN

SET SCSNODE "XXXXXX"
SET SCSSYSTEMID 29056
WRITE VAXVMSSYS.PAR
EXIT

Now attempt to reboot the satellite again.  Also make sure that no other
system in the cluster is using this nodename or systemid by doing a
$ SHOW CLUSTER/CONT
ADD SYS_ID	! There will be no prompt just type it in



 

** About PDF files: The PDF files on this Web site can be read online or printed using Adobe® Acrobat® Reader. If you do not have this software installed on your system, you may download it from the Adobe Web site.
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.