| Robert,
You have to force the pwrk$license_s process to run on the same cluster
member every time. Here's an article to help....Paul
[PW-DOS]V5 FastD: Obtaining a License From a Cluster Over a WAN
Any party granted access to the following copyrighted information
(protected under Federal Copyright Laws), pursuant to a duly executed
Digital Service Agreement may, under the terms of such agreement copy
all or selected portions of this information for internal use and
distribution only. No other copying or distribution for any other
purpose is authorized.
Copyright (c) Digital Equipment Corporation 1995. All rights reserved.
PRODUCT: PATHWORKS [TM] for OpenVMS [TM], V 5.0
PATHWORKS [TM] for DOS and Windows, Version 5.0, 5.1
OP SYS: OpenVMS, V 5.5, 6.0, 6.1
MS-DOS, Version 3.3, 4.0, 5.0, 6.0
SOURCE: Digital Equipment Corporation
BACKGROUND: FASTDETAIL
FASTLANE detail articles provide detailed information on topics discussed
in FASTLANE "master" articles.
This article provides detailed information on the FASTLANE MASTER article:
FASTM: V5 License Issues Master xFM0046
REFERENCES:
PATHWORKS Guide to Managing PATHWORKS Licenses
=========================================================================
=========================================================================
PROBLEM:
Your license server is in a cluster in a different TCP/IP subnet or
different DECnet area from your client. All attempts to get a license
for the PC fail.
SOLUTION:
There is a logical conflict when the license request is over a WAN and
the license server is in a cluster. This requires special handling.
The license server is active on only one node in the cluster, even if
all nodes run the license server. However, if a cluster alias is de-
fined, that is normally the name which will be used as the "listen name"
by the license server. This presents no difficulties in a LAN, because only
the active node will hear and respond to a broadcast.
However, for WAN access, you must communicate without broadcast. If you
specify the alias name and address for direct connection, the active
server may or may not be the responding node. If you specify the node
which is serving, the name will not be correct for the license server.
The procedure to operate properly is as follows:
Configure the PC using the cluster alias for the server name, but using
the IP or DECnet address of the license server. Then, assuming a node
name of "NODE" and an alias of "CLUSTER":
Modify CFG000x.TPL to set
SW_PWLICLM = CLUSTER
For TCP/IP, from DOS, put in
C:\> INETNAME PWRK$L{cluster} {license-server-IP-address} /S
For DECnet, from DOS, put in
C:\> NCP DEFINE REMOTE-ADAPTER-NAME PWRK$L{cluster} NODE {cluster}
Boot and get the license. This saves the information in PWLICLM.DAT.
Remove all INETNAME definitions and NCP node definitions.
Configure the PC using the correct LM or NW server name and address. Make
SW_PWLICLM null.
SPECIAL NOTE:
With this configuration you will need to be careful to see that only one
server is serving licenses. This can be managed by specifying the following
in SYS$UPDATE:PWRK$CONFIG.COM or by use of a VMS logical.
To prevent the license server from running on node VMSNET enter:
$ IF F$TRNLNM("SYS$NODE") .EQS. "VMSNET::" THEN -
$ DEFINE/SYSTEM PWRK$LICENSE_SERVER_INHIBIT "0"
To more generally limit the license server to running on specific nodes,
the following is offered as an example.
$! Cluster alias is "CLUSTER" with nodes "NODE1", "NODE2", ..., "NODEn"
$! and the license server is only supposed to run on two nodes
$! of the cluster: "NODE1" & "NODE2". ("ls" = "license server")
$!
$ ls_nodes = "NODE1,node2" ! <= user defined
$ ls_nodes = f$edit( ls_nodes, "upcase" )
$ ls_nodes = f$edit( ls_nodes, "upcase" )
$ ls_nodes_len = f$length( ls_nodes )
$ this_node = f$getsyi( "nodename" )
$ ls_on_this_node = ( f$locate(this_node,ls_nodes) .lt. ls_nodes_len )
$ if ( .not. ls_on_this_node ) then -
$ define/system pwrk$license_server_inhibit "0"
REFERENCE:
See the Guide to Managing PATHWORKS Licenses (part #AA-Q1BZA-TH) for more
information. This manual is included with the PATHWORKS Server documentation
sets and is also available in Bookreader format on OpenVMS Documentation
CDROM distribution starting in March, 1994.
|