|
HP OpenVMS Systems |
|
HP Advanced Server for OpenVMS
|
| Previous | Contents | Index |
This chapter briefly describes the licensing components that run on the client computer and how to obtain them. These components communicate with the licensing software components (License Registrar and License Server). (The licensing software components are described in Chapter 1, How to Use Advanced Server License Software.) This chapter also explains how to enable client computers to obtain licenses over a wide area network (WAN).
This chapter includes the following topics:
To obtain a client-based license from the License Server, the client computer must be running the software for license acquisition --- the client licensing software. This software enables the client computer to request and store license information for access to the file server.
If you plan to use server-based licensing only, the software components described in this chapter are not required. |
The client license components include:
The CLR works with the License Server to assign licenses to your client system. It also checks with the License Server at startup time to see if the license has been revoked by the network administrator. The CLT stores assigned licenses and presents them to the file server when asked.
For information on client licensing messages, such as the system error message you receive when you attempt to access the file server without a license, or the messages you receive when you run the Client Transponder or Client Requester software, see the appropriate client online help utilities.
Clients use the same transports to obtain and use their license keys as
they do to access their file services.
For clients connecting to the server using a dial-up connection, or
from a local area network (LAN) other than the server's LAN, extra
steps may be required to obtain a license. Procedures for dial-up
connections are described in the README.TXT file provided with the
Advanced Server PWLICENSE share on the file server. Procedures for
connections from a LAN other than the server's LAN are described in
Section 5.3, Enabling Wide Area Network (WAN) Operations.
5.2 How to Obtain the Client Licensing Software
You can obtain client licensing software from the following sources:
Windows 2000 and Windows 2003 clients can obtain client license software from the PATHWORKS 32 distribution kit. Ensure that server-based licensing is enabled so that clients can access the PWLICENSE share and install the client licensing software. |
To connect to the PWLICENSE share from a client that has not yet obtained a client-based license, a server-based license must be available to assign to the client. If necessary, use the License Manager to allocate a license to the Server-Based license group. |
For information about installing the client licensing software, refer
to the README.TXT file provided in the Advanced Server PWLICENSE share
provided on the file server.
5.3 Enabling Wide Area Network (WAN) Operations
This section provides the basic information you need to configure licensing software on client computers that are not in the same LAN as the License Server and that must acquire client-based licenses.
When the License Server that is to provide client-based licenses is not in the same LAN as the client system, the following two steps are required to set up the client system:
For the CLR to communicate with a License Server, the client system must be able to resolve the NetBIOS name of the License Server. Client computers on the same LAN as the License Server can use broadcasts to locate the License Server. However, client computers outside the local area network where the License Server is running must use one of the following methods to resolve the NetBIOS name of the License Server:
tcp-address PWRK$Lname #PRE |
12.34.56.78 PWRK$LZIPHED #PRE |
NCP DEFINE REMOTE-ADAPTER-NAME PWRK$Lname NODE decnet-address |
NCP DEFINE REMOTE-ADAPTER-NAME PWRK$LZIPHED NODE 12.345 |
Once the WAN protocol stack has been configured to map the NetBIOS name of the License Server to the WAN address of the License Server system, configure the licensing software on the client, specifying the NetBIOS name of the License Server. On Windows NT 4.0, Windows 2000, Windows XP and Windows 2003 clients, run the program PNLCFG.EXE and add the License Server to the list of "Remote License Servers" in the dialog box.
This appendix explains the event messages that are logged to the License Server and License Registrar log files as well as the Event Logger (ADMIN/ANALYZE). It provides the License Server and License Registrar messages, an explanation of these messages, and corrective action if appropriate. It includes the following topics:
For information on client licensing messages, such as the system error
message you receive when you attempt to access the file server without
a license, or the messages you receive when you run the Client
Transponder or Client Requester software, see the appropriate client
online help utilities.
A.1 License Component Log Files
Log files are stored in a directory defined by the PWRK$LOGS logical name. The two types of log files are:
The names of the license processing-related log files are as follows:
PWRK$LOGS:PWRK$LICENSE_SERVER_name1.LOG |
PWRK$Lname2 |
PWRK$LOGS:PWRK$LICENSE_REGISTRAR_name.LOG |
The names of the license component program log files are as follows:
PWRK$LOGS:PWRK$LICENSE_S_name1.LOG |
PWRK$Lname2 |
PWRK$LOGS:PWRK$LICENSE_R_name.LOG |
This section describes events logged to the License Server log file (PWRKS$LOGS:PWRK$LICENSE_SERVER_name.LOG). Note that all the messages posted to the log file begin with a date/timestamp. Use the License Manager to control what events are logged. The types of events that the License Server posts to the License Server log file include:
ALERT_LEVEL_REACHED:
Product = product-name Group =
group-name Alert Level = alert-level-number
Allocation = number-of-licenses-allocated
Explanation: The number of licenses currently in use
for this product exceeds the alert level. If the group-name is
<none>, the alert level for all the product's licenses has been
exceeded. Otherwise, the alert level for the licenses in the specific
group has been exceeded.
User Action: Review the current license distribution.
Remove licenses from clients that no longer use the product,
redistribute the available product licenses, or add new product
licenses.
CLIENT_ADDRESS_CHANGE:
Client Id = client-id-number Old
Client Addr = old-address New Client Addr =
new-address
Explanation: The current client's address is different
from when the license was assigned. Typically, this message indicates a
license has been moved from one client to another.
User Action: Make sure that the change of client ID is
valid.
CLIENT_ID_CHANGE:
Client Id = client-id-number Old Client
ID = old-id New Client ID = new-id Old Client Addr =
old-address New Client Addr = new-address
Explanation: The current ID of the client is different
from the ID it had when the license was assigned. The client ID is the
address of the Ethernet adapter. Typically, this message indicates that
a license has been reassigned from one client to another.
User Action: Make sure that the Ethernet address
change is valid.
CLIENT_LICENSE_ASSIGNED:
Client ID = client-id-number
Client Addr = client-address Transport =
transport-name Product = product-name Group =
group-name
Explanation: A product license was granted to the
client from the group specified.
User Action: None required.
CLIENT_LICENSE_DENIED:
Client ID = client-id-number
Client Addr = client-address Transport =
transport-name Product = product-name Group =
group-name Reason = explanation-string
Explanation: The client's request for assignment of a
license could not be processed as requested.
User Action: If the reason is an incorrect product or
group, check to be sure the license type exists and reconfigure the
client to obtain a valid license. If there are not enough licenses, the
administrator must add, reallocate, or revoke licenses to create
available ones.
CLIENT_LICENSE_INVALID:
Client ID = client-id-number
Client Addr = client-address Transport =
transport-name Product = product-name Group =
group-name Reason = explanation-string
Explanation: The license presented for verification to
the License Server by the client is no longer valid.
User Action: If the reason is an incorrect product,
group, or license, the data on the client may no longer be valid (for
example, the group may have been deleted), or the license may have been
revoked. Reboot the client to obtain a valid license. If the license is
in use by another client, this may be a case of illegal copying of
license data between clients and should be investigated.
CLIENT_LICENSE_RELEASED:
Client ID = client-id-number
Client Addr = client-address Transport =
transport-name Product = product-name Group =
group-name
Explanation: The system manager released the product
license from the specified group.
User Action: None required.
CLIENT_LICENSE_REVOKED:
Client ID = client-id-number
Client Addr = client-address Product = product-name
Group = group-name Reason = explanation-string
Explanation: The product license from the specified
group was revoked or removed. The reason string indicates whether it
was due to an action taken by the License Manager, or due to changes in
the OpenVMS License Management Facility (LMF) database. This action can
explain why a client's license is considered invalid in a later log
event.
User Action: You may have to add, reallocate, or
revoke currently allocated licenses to allow this client to use the
file server in the future.
CLIENT_LICENSE_UPGRADE_ON_ASSIGN:
Client Id =
client-id-number Client Addr = client-address
Transport = transport-name Group = group-name Current
Product = version-product-name, for example PWLMDOSCC06.00,
PWLMXXCA06.00 Upgrade Product = product-name, for example,
PWLMXXXCA06.00
Explanation: The client requested a PWLMDOSCC06.00
license and the License Server has defined the logical so the License
Server upgraded and assigned the PWLMXXXCA06.00 license. The license
returned to the client will be a virtual license. (See the description
under Explanation for message,
VIRTUAL_CLIENT_LICENSE_RETURNED_ON_ASSIGN.)
User Action: None required.
CLIENT_LICENSE_VALID:
Client ID = client-id-number Client
Addr = client-address Transport = transport-name
Product = product-name Group = group-name Reason =
explanation-string
Explanation: The license presented for verification to
the License Server by the client is valid.
User Action: None required.
FATAL_ERROR:
module-name: module-name and
explanation-string
Explanation: An irrecoverable error has occurred that
will cause the License Server to terminate. The message may return the
name of the module in which the error occurred and an explanation of
the possible cause.
User Action: Notify your HP service
representative or local authorized reseller. Please save the log file
so that it may be used to help diagnose the problem.
INIT_LOGFILE:
Reason = explanation-string
Explanation: A new version of the log file was
created. The reason string indicates whether it was done because the
server started, or because of a License Manager request.
User Action: None required.
MESSAGE: message-text
Explanation: The message displayed describes
diagnostic log event information.
User Action: None required.
SERVER_STATE_CHANGE:
Old State = previous-state-name New
State = new-state-name Reason = explanation-string
Explanation: The License Server has been either
enabled to serve the client requests or disabled. The reason always
indicates that it was at the request of the License Manager.
User Action: None required.
VIRTUAL_CLIENT_LICENSE_RETURNED_ON_ASSIGN:
Client ID =
client-id-number Client Addr = client-address Group =
group-name Product = product-name Virtual Product =
virtual-product
Explanation: The license requested by the client was a
LAN Manager license, for example, PWLMDOSCC06.00. The license software
looks for a higher version of the product than requested either through
license version lookup (described in Section 3.3, Controlling License Version Lookup) or license upgrade
(described in Section 2.5, Upgrading Client Licenses). A license was assigned to that client,
for example, PWLMXXXCA06.00. Because the client will only accept a
license name in the format of the license requested, the License Server
returns a "virtual license" to the client that conforms to
the original format requested. So the virtual license returned is in
the form, PWLMDOSCC07.00. The client will accept it as simply a higher
version of the PWLMDOSCC06.00 that it requested.
User Action: None required.
A.3 License Registrar Events
This section describes the various events that can be logged to the License Registrar log file (PWRK$LOGS:PWRK$LICENSE_REGISTRAR_nodename.LOG) and the control logicals available to control the posting of events to the log file.
The types of events that the License Registrar posts to the License Registrar log file include:
By default, the License Registrar logs only the most significant events to prevent the log file from growing too rapidly. If no control logicals are used to indicate that additional events should be logged, the default behavior is to post only the following types of events to the License Registrar log file:
On occasion, it may be necessary to reconfigure the License Registrar to post more detail about requests being processed. Should this become necessary, use the following control logicals to control the type of events posted to the License Registrar log file. These logicals determine the License Registrar's configuration parameter values while it is running.
Each of these control logicals can be turned on by defining the logical to a value of one (1). They can be turned off by leaving them undefined or defining them to a value of zero (0). If the logical is defined, the logical name must be defined in such a way as to make the definition available to the License Registrar process (by defining a system logical or defining the control logical in the License Registrar startup command procedure SYS$STARTUP:PWRK$LICENSE_R_START.COM). For example, to always log events related to server-based licensing, turn on the PWRK$LR_Log_ServerBased_Activity by defining the following system logical:
$ DEFINE/SYSTEM PWRK$LR_Log_ServerBased_Activity 1 |
Note that these parameters affect reporting of individual events as they happen. For example, when a client takes or releases a license, an event message is logged reporting that activity. To generate reports that provide statistics such as the number of server-based licenses currently in use, see Section A.3.1, Monitoring Consumption of Server-Based Licenses.
CLIENT_ADDRESS_CHANGE:
Old Client Addr = old-address-name
New Client Addr = new-address-name
Explanation: The current network address of the client
is different from the one it had when the license was granted. This
change may be valid, or it may indicate the illegal copying of license
data from the old client to the new client.
User Action: Make sure that the change of address is
valid.
CLIENT_LICENSE_INVALID:
Client ID = client-id-number
Client Addr = client-address Product = product-name
Group = group-name Reason = explanation-string
Explanation: The product license specified is no
longer valid for the client.
User Action: If the reason is an incorrect product,
group, or license, the data on the client may no longer be valid (for
example, the group may have been deleted). Reconfigure the client to
obtain a valid license. If the license is in use by another client,
this may be a case of illegal copying of license data between clients
and should be investigated.
CLIENT_LICENSE_VALID:
Client ID = client-id-number Client
Addr = client-address Product = product-name Group =
group-name Reason = explanation-string
Explanation: The product license from the group
specified is still valid. The reason string indicates whether the
client license was actually inspected or whether there was a cache
entry match.
User Action: None required.
CLIENT_NOT_LICENSED:
Client ID = client-id-number Client
Addr = client-address Transport = transport-name
Reason = explanation-string
Explanation: The client is not licensed to access the
file server. The client does not have a client-based license that
grants it the right to access the services provided by the file server
and there are no server-based licenses available for the License
Registrar to assign to the client to give the client access rights to
the file server.
User Action: Either configure the client to acquire a
client-based license to access the file server or make server-based
licenses available on the file server system, which can then be used to
license the client.
FATAL_ERROR: module-name: module-name and
explanation-string
Explanation: An irrecoverable error has occurred that
will cause the License Registrar to terminate.
User Action: Notify your HP service
representative or local authorized reseller.
INIT_LOGFILE:
Reason = explanation-string
Explanation: A new version of the log file was
created. The reason string always indicates that it was done when the
License Registrar started.
User Action: None required.
MESSAGE: message-text
Explanation: The message displayed describes
diagnostic event information.
User Action: None required.
SERVER_LICENSE_ASSIGNED:
Product = product-name Client
Addr = client-address Client ID = client-id-number
Allocation = total-number-of-server-based-licenses-assigned
Explanation: The client indicated did not have a
client-based license sufficient to access the local file server and was
assigned a server-based product license, granting the client the right
to access the local file server. The allocation indicates the number of
server-based licenses in use after assigning the license.
User Action: None required.
SERVER_LICENSE_RELEASED:
Product = product-name Client
Addr = client-address Client ID = client-id-number
Allocation = total-number-of-server-based-licenses-assigned
Explanation: A client, previously assigned a
server-based product license, has disconnected from the file server.
The server-based license previously assigned to this client has been
released. The allocation indicates the current number of server-based
licenses in use after the release of the license.
User Action: None required.
| Previous | Next | Contents | Index |