Bill,
thank you for pointing me this. Usualy the main difference between USA and
EMEA announcement letters is the number and I easily found the section you
pointed in EMEA Letter ZP00-0350. So I was wrong and admit it.
However there is no strict definition of the terms "managed system" and
"managing system". If this is the box, not the OS image what happens in the
following scenarios:
SP with more than one frame
several servers running PSSP, PE, Parallel ESSL, GPFS, LoadLeveler either
in separate boxes or in a single rack but w/o SP switch and not ordered as
SP system
several rack-mounted servers in single rack being or not part of a
cluster
HP HyperPlex system
In the first scenario is each frame counting as separate "managed system"
or not. In latter case if we have imaginary SP with three frames with 8
dual-processor Wide Nodes each should we consider this Tier 2 system
because number of processors in the frame is 16 !?!
In the second scenario we are having switchless SP system of RS/6000
servers (or pSeries). But if not ordered as SP this may mean that 4
dual-processor B80s or pSeries 610 for total of 8 processors will need four
times more Tivoli MP compared to the 48-processor SP in the above example.
And on the end several servers in a single rack - what if they are separate
OS images with different application services, if they are in a cluster
running same application (Parallel Oracle, partitioned DB2, round-robin web
servers, etc.) or if it is single OS image and application instance as in
HP HyperPlex (I have no experience with HyperPlex. AFAIK with it up to four
servers are interconnected to form signle large server running one OS image
something like predecessor of SuperDome. But I may read this wrong also
so comments are welcome direct mail or through list).
Another issue with SP is if we treat it as single system - does this mean
we can start TSM servers on more than one node. And how many library
sharing licenses would be necessary in this case - one for each node, only
one for the whole SP or nothing. The explained usage of both TSM server and
MgSysSAN maybe is for TSM server on a SP node and another node performing
activities LAN-free. But what if third node also is SAN-attached for backup
and on fourth node we run a test TSM server? Are points for one Tier 2/3
server and *one* MgSysSAN T2/3 enough?
In the light of this information a load-balancing cluster cleraly needs
only two MgSysSAN licenses for LAN-free transfer. But what happens with
failover cluster? Can we use one MgSysSAN for active node and one MgSysLAN
for passive node or we should get again two MgSysSAN licenses? It is hard
to answer.
Yes, I know this are not questions to ask you. However we are discussing,
sharing opinions and I will be glad to read what people on the list think.
Zlatko Krastev
IT Consultant
Bill Mansfield <WMansfield AT SOLUTIONTECHNOLOGY DOT COM> on 16.01.2002 17:35:34
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: What qualifies as an in use license?
Yeah, should have said machine, not "platform".
Yes, you should consider the whole SP (or p690 or the like) as a single
entity with regard to licensing provided. The same is true for your
desktop running Windows, OS-2, and Linux. The cluster you refer to counts
for 2 licenses, since there are two machines involved. In every case I
have commented on Tivoli policy I have attached sections from the USA
Tivoli announcement letter, which I consider to be official, committed
Tivoli policy for the USA. Here's the relevant section regarding SP.
Distributed server tiers are defined by the machine, not operating system,
based
on installed processors. For IBM RS/6000(superscript: ®) Scalable POWER
Parallel
Systems (RS/6000 SP?), Sun Ultra Systems and similar systems, the
licensing is
based on the number of processors in the frame, not per individual node or
card.
For clustered environments, the licensing is determined by the number of
installed processors in each server in the cluster.
William Mansfield
Senior Consultant
Solution Technology, Inc
Zlatko
Krastev/ACIT To: ADSM-L AT VM.MARIST DOT EDU
<acit@ATTGLOBA cc:
L.NET> Subject: Re: What qualifies as
an in use license?
Sent by:
"ADSM: Dist
Stor Manager"
<ADSM-L AT VM DOT MAR
IST.EDU>
01/16/2002
07:13 AM
Please respond
to "ADSM: Dist
Stor Manager"
Let try to define it further - what do you (or "Tivoli" you have contacted)
mean of "single hardware platform" ?
For me this means type of hardware, i.e. IBM RS/6000, HP9000, PC, etc. I do
not believe that buying enough points for a server and three MgSysLAN
licenses will allow me to define nodes and use the client on bunch of PCs
with Windows&Linux and all HP9000s + RS/6000s. Or having two clients
RS/6000 and one of them through processor upgrade becomes pSeries I should
be forced to get more points for this second "platform".
So probably this is not a "platform" but "box" or "machine".
However this raises the question of many *real* nodes within one box. I
already presented my opinion in answer to your (Bill Mansfield) post on the
thread "Licensing MS SQL cluster - managed system for LAN/SAN and TDP
licenses?" on 19.11.2001:
"How can we distinguish between two nodes on two machines, two nodes on the
same OS and two nodes on different OS images with the same box (HP
SuperDome or IBM eServer pSeries 690 for example)? Or should we consider
whole IBM SP(2) cluster as a single system with multiple nodes registered?"
Unfortunately I do not know *OFFICIAL* Tivoli contact to ask licensing
questions for my country. In the thread mentioned above we already got
*unofficial* (any opinion presented here from IBM/Tivoli people does not
bind the company and is just informative) answer from Del Hoobler
confirming my guess - for two "boxes" in MSCS cluster we need three managed
system licenses. Two for the local files on each box and third for the
cluster resourses jumping from box to box.
So my personal opinion is that we need license for *EACH* defined node. If
I want to define two nodes for single box I am supposed to be ready to pay
for this. For example on my PC I have installed OS/2, Linux and Windows but
I had to pay licenses for both OS/2 and Windows (God save Linus).
Zlatko Krastev
IT Consultant
Bill Mansfield <WMansfield AT SOLUTIONTECHNOLOGY DOT COM> on 15.01.2002 22:53:29
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: What qualifies as an in use license?
Yes, the TSM licensing is anything but clear. I can't speak to the client
expiration issue, but I've looked very hard into the licensing aspects.
Here's a bit of what it says in the announcement letter for the USA
value-based program:
(
http://www2.ibmlink.ibm.com/cgi-bin/master?xh=JCvY43nNwaCFgG1USenGnN9332&request=announcements&parms=H%5f200%2d245&xhi=announcements%5e&xfr=Nhttp://www2.ibmlink.ibm.com/cgi-bin/master?xh=JCvY43nNwaCFgG1USenGnN9332&request=announcements&parms=H%5f200%2d245&xhi=announcements%5e&xfr=N
)
* One MANAGED SYSTEM FOR LAN feature is required for each managed system
* One MANAGED SYSTEM FOR LAN feature is required for each managed system
that will move data to and from storage over a LAN.
* One MANAGED SYSTEM FOR SAN feature is required for each managed system
that will move data to and from storage over a SAN.
* A managed system that moves data to and from storage, both on a LAN and
on a SAN, requires only the Managed System for SAN feature.
I have verified with Tivoli that a managed system is a single hardware
platform regardless of how many nodes TSM has defined for the box. So you
need either a MGSYSLAN or a MGSYSSAN license for every physical machine
that will be sending data. Not for each node registered to TSM.
Essentially this means that the license feature built into TSM is useless
for actually managing your license usage.
The TDPs only require their own specific licenses, even if they generate
extra nodes. Their data movement is covered by the MGSYSLAN license (or
MGSYSSAN if LANFree is required).
This may be different in other parts of the world, but don't trust your
reseller to get it right, call Tivoli directly to verify your
configuration.
William Mansfield
Senior Consultant
Solution Technology, Inc
Daniel Sparrman
<daniel.sparrman To: ADSM-L AT VM.MARIST DOT EDU
@EXIST.SE> cc:
Sent by: "ADSM: Subject: Re: What qualifies
as an in use license?
Dist Stor
Manager"
<[email protected]
T.EDU>
01/15/2002 02:20
PM
Please respond
to "ADSM: Dist
Stor Manager"
Hi
There seems to be a lot of confusion about licensing in TSM.
According to Wanda Prather, license for each client expires 30 days after
the clients last connection.
According to some other, clients not in use don't require a client license.
I've been looking in to this, and according to the License Agreement, each
registred client need and "Tivoli Storage Manager Managed Systems for LAN"
client. This means that each file client needs a license, each TDP need a
client, and according to internal sources on Tivoli, each Managed Systems
for SAN require a Managed systems for LAN. Special requirements have been
issued from Tivoli concering the use of Gresham EDT concerning licensing.
My suggestion is to here with your local Tivoli sales/dealer on how to
use/agree the licensing terms.
Best Regards
Daniel Sparrman
-----------------------------------
Daniel Sparrman
Daniel Sparrman
Exist i Stockholm AB
Bergkällavägen 31D
192 79 SOLLENTUNA
Växel: 08 - 754 98 00
Mobil: 070 - 399 27 51
Tom Melton <Tom Melton AT EMORYHEALTHCARE DOT ORG>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
2002-01-15 11:36 EST
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
bcc:
Subject: Re: What qualifies as an in use license?
It was my understanding that a "defined" client on the server would fall
from the "in-use" number after 30 days. IE, 30 days of inactivity and the
in-use count decrements.
Tom Melton
Emory HealthCare
>>> daniel.sparrman AT EXIST DOT SE 01/15/02 10:44AM >>>
Hi
Yes, every node registred on the server counts as one client license.
Also, if you use separate nodenames for Tivoli Data Protection clients,
everyone will count as 1 Managed System LAN.
I'm not sure, but I also think that every Managed System SAN counts as one
managed systems lan also.
Best Regards
Daniel Sparrman
-----------------------------------
Daniel Sparrman
Daniel Sparrman
Exist i Stockholm AB
Bergkällavägen 31D
192 79 SOLLENTUNA
Växel: 08 - 754 98 00
Mobil: 070 - 399 27 51
Dylan Ryback
<dryback@HOME To: ADSM-L AT VM.MARIST DOT EDU
.COM> cc:
Sent by: Subject: What qualifies as an
in use license?
"ADSM: Dist
Stor Manager"
<ADSM-L AT VM DOT MA
RIST.EDU>
2002-01-15
16:45
Please
respond to
"ADSM: Dist
Stor Manager"
I'm in the midst of doing a cleanup job on our TSM servers. When I do a 'q
license', one of the results is:
Number of Managed System for LAN in use: 107
My question is, what counts as 'in use'? For example, there are a bunch of
nodes that are defined and are no longer used or associated with any
schedules. Do these count as 'in use', and if so, should I export the node
out of the db and delete it to get the license counts down? One other
question: anyone got a query to figure out which nodes are NOT associated
with a schedule. This would help me identify nodes that are candidates for
export.
Many thanks,
Dylan
|
