[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

799.0. "pcm/vcs pak problem?" by MERIDN::BUCKLEY (ski fast,take chances,die young) Fri Jun 09 1995 16:18

I am working with a customer that a)added pcm to a alphaserver 4/200 and b)
upgraded their vaxstation 3100 from VMS v5.5-1 to v5.5-2 to v6.1 and added pcm.
The vaxstation had been running vcs and had a valid unlimited pak for vcs.

As they are working the the license issues with sales, I loaded vms,net-app and
pcm temp licenses on the alphaserver and everything is ok there. After upgrading
the 3100 to vms 6.1, installing pcm and turning off vcs (comment out in startup,
adding pcm to sysman) and rebooting, the daemon processes were dying. I defined
console$debug and the resulting error was license poly-consolemgr or vcsconsole
(or something like that) not loaded. A show license showed the vcsconsole
license WAS loaded... As a short term solution I loaded the temporary pcm
license that I was using on the alpha and everything was fine.

Does pcm v1.5 plus MUP use the old VCS pak correctly?
Some of the VCS lat definitions were still being done in startup, could this
have caused vcs to grab the license and somehow prevented pcm from getting it?

I am worried that the 3100 will die when the temporary pcm license expires!

Dan Buckley
P.S. the performance difference between a vaxstation 3100 and a 2 cpu alpha
2100 4/200 is incredable!!!!!!!!!!!!!!!!!!
T.RTitleUserPersonal
Name
DateLines
799.1ZENDIA::DBIGELOWInnovate, Integrate, EvaporateFri Jun 09 1995 17:2921
    Dan,
    
        There was no such thing as an unlimited VCS license. Each console 
    license required 100 units. The only unlimited use license as for
    Digital internal use only. So, if your customer had 6 systems, there
    should be 600 units.
    
    However, PCM should honor the license on the 3100. The fact that it has
    unlimited license units may be the cause, but I'd tend to doubt it. 
    Phil, can you shed any light here? Also, someone entered a note just last 
    week with some questions regarding this just a few days ago. 
    You might look there for some additional information.
    
    As for the startup command procedure which creates the lat definitions,
    the answer is no, it has no impact on licensing. As a matter of fact,
    you can tell your customer to comment that out as well. PCM will create
    the lat definition for you.
    
    
    
                                                                       
799.2IP$16.36.32.41::PHILIPAnd through the square window...Fri Jun 09 1995 17:5310
Dan and Dave,

  All we do in the code is suck out VAXCLUSTER-CONSOLE licences 100 units
  at a time. All the testing we have done works.

  Dan, could you Mail me the PAK which gives you problems, I will load it
  here and see what happens.

Cheers,
Phil
799.3Sorry, I can't...MERIDN::BUCKLEYski fast,take chances,die youngFri Jun 09 1995 21:2517
>  Dan, could you Mail me the PAK which gives you problems, I will load it
>  here and see what happens.


Unfortunately no, I had the problem last week and am no longer at the customer
(lotus). I just faxed the customer a new set of 2 week temp paks to keep them
running until they get the correct paks from sales. I do not know the details
of the license, only that I expected it to work (same machine, same nodes being
monitored) and it didn't. If we ran out of license points on the 15th node,
would PCM die or would we get an unable to connect to node xxx type message?
I seem to remember that it was a VERY fast failure as if it saw no licenses
right off the bat. I did a show license and saw the license loaded that it
complained did not exist. This was at 8:30pm, I loaded the temp pak and 
everything worked so I forgot about it until the sending of temp paks today
reminded me...

Dan Buckley, CT dc
799.4CSC32::BUTTERWORTHGun Control is a steady hand.Fri Jun 09 1995 23:558
    Well, I've personally tested a VCS PAK on a 4000-300 and it worked
    fine. The PAK will tell us all. If it was a 0 unit PAK that the
    customer had gotten from the CSC ( these existed several years ago) it
    would have had a "Product release date" field with a date at least 2
    years in the past. This could account for the behavior that you saw.
    
    Regs,
      Dan