Choose your language
Back to startpage






HP NonStop Server
Fusion95 Release Notes

Last updated: October 2006

Contents

  1. Overview
  2. Security methods
  3. Users and User IDs
  4. Enhancements
  5. Licensing
  6. Installation Procedures
  7. Using Fusion95 with D44, D45, G04, G05 or G06
  8. Using Fusion95 from Windows98, NT, W2000 or XP
  9. Further configuration of Fusion95
  10. Automatic Start-Up
  11. Accessing the Guardian File System
  12. Socket Transport Agent
  13. Download the latest versions for evaluation or upgrading.

Overview

Fusion95 is now available for the HP NonStop Integrity Server. Fusion95 will run on D44 and G04-G06 systems under OSS. This document is intended to help install and test on this platform. It will be updated continually as new information is obtained.

Fusion95 runs on a wide range of UNIX platforms. It is possible to run Fusion95 on the HP NonStop Integrity Server, because this now supports "UNIX" with the advent of OSS.

Please send technical questions and feed-back to : tech@april.se

To the top

Security methods

This port supports User-Level and Share-Level security. With Share-Level security the access to NonStop Server's resources are protected by passwords. With User-Level security the access to these resources is protected by user name/account and password authentication.

The configuration of whether Share-Level or User-Level security is used is determined by the secmode= parameter in the pcserve.ini file. Fusion95 parameters are documented in the User's Guide. The security type is always configured on a per-server basis. It is not possible to have different type of security for different shared disks.

Share-Level security

Share-Level security has shared resource access determined when the resource is used by validating the resource password. An example of this is a Windows 95 server. Share-Level security is the easiest to use and administrate, and it is this we recommend you use unless you really need functionality from one of the others.

Access to disks is determined at resource connection time, by the specification of passwords.Users will have full access to all files on shared resources to which they have access. The user id and access permission of any files created will be determined on a shared resource basis.

User-Level security

User-Level security has shared resource access determined at logon time by validating the user id and password. An example of this is a Windows NT server.

The client will send a session set-up request to the server containing the user-name and password. These will be validated against Fusion95. s User Database before access is allowed. Once access is permitted, the user can map all shared resources without specifying a password, and obtain access rights according to the user account.

If the user-name and password cannot be validated, then access to the server will normally be denied. It is however possible to allow guests to access the server; users without a valid account on the server will be logged on as a guest. In order to do this the guest= parameter must be included in the pcserve.ini file to specify the user-names whose access rights the guest will be given. The default is NOT to permit guests access.

To the top

Users and User IDs

When running the server in User-Level security, each PC user is mapped to a NonStop Server user (NSK User Id). This mapping can either be to a "full" name or to an alias. For example PC user DENNISA could be mapped to Guardian user edu.dennis or to Guardian alias dennis.

OSS does not provide the /etc/passwd and /etc/group files that are normally available in a UNIX environment. Features in Fusion95 that normally require these files (such as the Browse buttons in the F95ADMIN GUI administration program) will not work. It is possible for the Guardian System Administrator to create these files, and thus enable this functionallity. This would require that it be maintained over and above the Safeguard/CA user databases; although it might be possible to automate this process.

When configuring user id in Fusion95 with either F95ADMIN or pcconfig, (for example for a shared disk on a server running in Share-Level security), you can either enter the Guardian NSK User ID or the OSS User ID. The configuration programs will automatically calculate and display the other User ID.

When using F95ADMIN earlier than 1.07, or Fusion95 earlier than 4.03.5 then the UID should be entered as an OSS User Id (Guardian Group Id x 256 + User Id). For example a Guardian user 254,211 (group id 254 and user id 211) will have an OSS User Id of 65235.

To the top

Enhancements

If Fusion95 is received well in the Tandem marketplace, we hope to enhance the "UNIX" product with a number of HP NonStop Integrity Server specific features.

We have started this process by adding Tandem specific support for multiple Socket Transport Agents, a feature not in the UNIX port of this product.

To the top

Licensing

During the installation procedure of a new Fusion95 system the user will be asked if he has a license code. If he does not have a code, a 10 user evaluation license with a one month expiry date will be automatically generated.

When the license database is displayed using the /usr/fusion95/license command, the expiry date will be shown along side this code.

When the purchase is made, a "live" license code can be added, without the need to re-install or even pause the Fusion95 server.

To the top

Installation Procedures

An evaluation of Fusion95 for HP NonStop Integrity Server is available for download from the internet. This is provided in compressed tar format. The following steps are used to install Fusion95:

  1. Make sure that you have Super-User access permissions (super.super) to the Tandem machine.

  2. Download Fusion95 using FTP to the Tandem machine and name the file:

    /tmp/fusion95.tar

  3. To expand the tar file, and create a release tree called /tmp/usr/fusion95, enter the following command:

    tar -xvf /tmp/fusion95.tar

  4. Run the install script using the command:

    /tmp/usr/fusion95/install/install

  5. If you are performing an upgrade you need to stop Fusion95. If you have not done so you will be prompted to do so now. Reply "Y" to do so.

    You appear to have Fusion95 running, you should stop it before upgrading.
    Do you want to stop Fusion95 now (y/n) ?

  6. You will be asked to enter network node name for this Fusion95 machine. This should be no more than 8 characters, and should normally be in upper case.

    The fusion node name is currently set to: FUSION
    Is this OK (y/n) ?

    If this is not OK, a different name can be selected:

    Please enter the network name (8 characters or less):

  7. You will be asked to enter workgroup/domain name in which this Fusion95 server will reside. This should be no more than 15 characters, and should normally be in upper case.

    The workgroup/domain name is currently set to: WORKGROUP
    Is this OK (y/n) ?

    If this is not OK, a different name can be selected:

    Please enter the workgroup/domain name (15 characters or less):

  8. You will be asked to enter tcp/ip driver name.

    The tcp/ip driver name is currently set to: $ZTC0
    Is this OK (y/n) ?

    If this is not OK, a different name can be selected:

    Please enter the tcp/ip driver name:

  9. The installation then prompts for an authorization code. If upgrading or re-installing then the previous code will be used.

    If this is a first-time or trial installation, you may not have a Fusion95 authorization code. Without an authorization code you will be able to test Fusion95 for 30 days.

    Please find your authorization code.
    If you do not have an authorization code, you may still evaluate Fusion95 for 30 days.
    Do you have a Fusion95 authorization code (y/n) ?

    If Y was entered, you will be asked to enter the code:

    The license code consists of 16 characters. It may be entered as a 16 character string or in blocks of 4 separated by dashes . -. .
    Enter the new license code (type q to quit):

  10. The system will now be copied to /usr/fusion95.

  11. The installation is now complete, Fusion95 will start automatically when the system is rebooted. In order to start Fusion95 without rebooting use the command:

    /usr/fusion95/f95start

    The installation then prompts to see if it should execute this command for you, in order to start Fusion95 immediately.

    Do you want to start Fusion95 now (y/n) ?

    Type Y to start Fusion95 immediately.

  12. The files extracted into /tmp, for use temporarily during the installation, can now be removed using the command:

    rm -r /tmp/usr/fusion95

To the top

Using Fusion95 with D44, D45, G04 ,G05 or G06

Early versions of OSS did not fully implement all of the system calls normally found in a UNIX system. Fusion95 uses the ioctl with the SIOCGIFCONF parameter to Get the InterFace CONFiguration. Running Fusion95 on a D44 or G04 system (and sometimes on a D45 or G05 system) will cause the error:

  SIOCGIFCONF ioctl: Invalid function argument

In order to get round this problem, a file called /usr/fusion95/cfg/interface0 should be created containing a list of the TCP/IP interfaces on which Fusion95 will run. This file should contain one line per interface with the format:

  Interface-Name space IP-Address space Network-Mask space Broadcast-Address

For example:

  SN31 204.160.16.36 255.255.255.0 204.160.16.255

This information can be obtained by running the following command from the OSS prompt (note that ztc0 might need to be changed to the correct TCP/IP driver process name):

gtacl -p scf 'assume process $ztc0 ; info subnet * ; exit'

SIOCGIFCONF was entered as a RFE (request for enhancement) and is available in some releases of D45 and G05 and all releases from D46 and G06. You need T9055D46, T9551D40-ADR, T8397D40-AAI and T8306D40-AAI.

To the top

Using Fusion95 from Windows98 or NT

Fusion95 is now ready to use. During installation it was configured for Shared-Level security and with one shared disk resource called TMP without a password which points at the /tmp directory. In order to map this disk on a Windows PC, go into Explorer and from the Tools menu select Map Network Drive. In the path field type \\ followed by the ip address of the Fusion95/Nonstop Server followed by \TMP, for example:

\\10.0.0.100\TMP

If the PC and Fusion95/Nonstop Server are on the same TCP/IP broadcast network then the node name specified at installation time can be used instead of the ip address, for example:

\\DEVELOPMENT\TMP

If the PC and Fusion95/Nonstop Server are not on the same TCP/IP broadcast network, then the node name can still be used instead of the IP address if name resolution is configured for the PC network. The simplest form of name resolution is performed by adding the Fusion95/Nonstop Server name and IP address to the PC's LMHOSTS file. Network wide name resolution can be performed by a Windows Name Server (WINS), into which the Fusion95/Nonstop Server name and IP address is added as a static entry.

Further configuration of Fusion95

Once access to the Fusion95/Nonstop Server's TMP disk has been tested, the next step is to add further shared disk resources. It is normal to protect these new disks with passwords. It might also be desired to removed the TMP disk or password protect it. Administration of the Fusion95 shared resources can be performed from an OSS prompt using the /usr/fusion95/pcconfig command or from a Windows PC with the F95ADMIN program installed.

To the top

Automatic Start-Up

It is usually desirable to make Fusion95 start automatically when then server is restarted. In order to do this, the system administrator must add a command to the system start-up file after TCP/IP has been started. This command should run the /usr/fusion95/f95start script.

For example:

osh -c "/usr/fusion95/f95start" -- >/usr/fusion95/f95start.log </dev/null

To the top

Accessing the Guardian File System

The Guardian File System is available to OSS programs such as Fusion95 via the /G directory.

Only unstructured files can be opened, it is not possible to open structured files such as databases. The file can be opened in the following cases:

Note: Sharing a directory with all uppercase letters, such as /G, requires Fusion95 version 4.03.8 and F95Admin version 1.08.

To the top

Socket Transport Agent

The Socket Transport Agent is a process that runs in the HP NonStop Integrity Server and allows OSS programs to communicate with TCP/IP sockets. This process is normally called $ZTC0 and is normally started in all the server's processors. If the name of the Socket Transport Agent has not be correctly specified at install time, or if a Socket Transport Agent process is not running in the same processor as Fusion95, the error "socket transport agent not running" will occur.

Support for multiple Socket Transport Agents

Fusion95 will run on all interfaces configured for the specified Socket Transport Agent. It is also possible to make Fusion95 run on multiple Socket Transport Agents.

To enable a second Socket Transport Agent, do the following:

  1. Change to the Fusion95 configuration directory:
    cd /usr/fusion95/cfg
  2. Create a configuration file containing the name of the server. The server name should probably be different from the first Fusion95 server.
    echo 'NONSTOP2' >uname1
  3. Create a configuration file containing the name of the workgroup/domain to which this server belongs.
    echo 'WORKGROUP' >domain1
  4. Create a configuration file containing the name of the Socket Transport Agent.
    echo '$ZTC01' >network1
  5. You might also need to create an interface1 file, see comments on installation together with D44 or G04.
  6. Restart Fusion95 so that these changes take effect.
To the top

Download the latest versions for evaluation or upgrading

Download now Click here to download the latest versions for evaluation or upgrading.
To the top

 

© Copyright 2004-2017 Developed by April System Design