Skip to main content

Install a New Network License (Unix/Linux/Solaris)

  1. IN­STALL THE LI­CENSE SOFWARE: If you have pur­chased a new net­work li­cense for LS-DY­NA, then you should de­cide where you want to run the li­cense serv­er. The LSTC Li­cense Serv­er may re­side on a Lin­ux, Unix, So­laris, or Mi­crosoft Win­dows plat­form. All ver­sions of LS-DY­NA may ac­quire per­mis­sion to run from this serv­er, re­gard­less of ar­chi­tec­ture or OS. A typ­i­cal in­stal­la­tion is found on this web page. More in­for­ma­tion can be found in the com­plete PDF In­stal­la­tion Guide.

    Choose a sta­ble ma­chine in or­der to min­i­mize li­cense down-time. Then down­load the LSTC Net­work Li­cense soft­ware for the ma­chine which will run the li­cense serv­er. It is gen­er­al­ly eas­i­er to in­stall, up­grade and ad­min­is­ter net­work li­cens­es if the LSTC Li­cense Serv­er is in­stalled un­der the Mi­crosoft Win­dows OS. How­ev­er, those fa­mil­iar with Unix/­Lin­ux/­So­laris should not find it dif­fi­cult to ad­min­is­ter li­cens­es on these plat­forms.

    Once you have cho­sen a plat­form on which to in­stall the LSTC Li­cense Serv­er, then down­load the LSTC Li­cense Soft­ware for the cho­sen tar­get ar­chi­tec­ture.

    HARD­WARE OS ARCHIVE
    AMD Opteron Red­Hat AS4.0 LSTC_­Li­cense­M­an­ag­er_­77918_­amd64_­red­hat40.tgz
    IN­TEL/­AMD SuSE 11.2 LSTC_­Li­cense­M­an­ag­er_­77918_­xeon64_­suse11.tgz
    IN­TEL/­AMD SuSE 11.4 LSTC_­Li­cense­M­an­ag­er_­77918_­xeon64_­suse114.tgz
    IN­TEL/­AMD SuSE 12.0 LSTC_­Li­cense­M­an­ag­er_­77918_­xeon64_­suse12.tgz
    IN­TEL/­AMD Red­Hat AS5.0 LSTC_­Li­cense­M­an­ag­er_­77918_­xeon64_­red­hat50.tgz
    IN­TEL/­AMD Red­Hat RHEL 3-5 LSTC_­Li­cense­M­an­ag­er_­77918_­ia32_­red­hat30.tgz
    IN­TEL/­AMD SuSE 9-10 LSTC_­Li­cense­M­an­ag­er_­77918_­ia32_­red­hat30.tgz
    IN­TEL/­AMD MS Win­dows 32/­64-bit LSTC_­Li­cense­M­an­ag­er_­85971_­win.exe

    Af­ter down­load­ing the ap­pro­pri­ate archive, choose a di­rec­to­ry where you want to in­stall the li­cense serv­er, move the archive to the in­stal­la­tion di­rec­to­ry, and cd in­to that di­rec­to­ry. Then un­pack the archive in­to the in­stal­la­tion di­rec­to­ry. For ex­am­ple,

            gun­zip LSTC_­Li­cense­M­an­ag­er_­77918_­al­pha_­51a.tgz
    	tar xvf LSTC_­Li­cense­M­an­ag­er_­77918_­al­pha_­51a.tar
    

    You should now see the fol­low­ing files in the in­stal­la­tion di­rec­to­ry

            lstc_­serv­er     lstc_­proxy     lstc_­client
            lstc_­qrun       lstc_­vrun      lstc_­qkill
            lstc_­lo­gre­port  gmid
    
  2. GEN­ER­ATE A LI­CENSE RE­QUEST:Run lstc_­serv­er with the in­fo com­mand line op­tion in or­der to gen­er­ate a li­cense re­quest form
            ./­lstc_­serv­er in­fo
    
    The serv­er will print the fol­low­ing mes­sage to the ter­mi­nal, in­di­cat­ing that it has cre­at­ed the sam­ple re­quest form LSTC_­SERV­ER_­IN­FO:
            Get­ting serv­er in­for­ma­tion ...
    
            The hostid and oth­er serv­er in­for­ma­tion has been writ­ten to LSTC_­SERV­ER_­IN­FO.
            Please con­tact LSTC with this in­for­ma­tion to ob­tain a valid net­work li­cense
    
    You will need to ed­it the top por­tion on this file, which looks like
            Your Com­pa­ny Name Here
                EMAIL: NONE
                  FAX: NONE
            TELE­PHONE: NONE
            #
            SERV­ER: E3707F52
            # Lin­ux desk­top 2.6.31.12-0.1-desk­top #1 SMP PRE­EMPT 2010-01-27
            # Host ID       : e3707f52
            #
            AL­LOW_­RANGE:  XXX.XXX.XXX.XXX XXX.XXX.XXX.XXX
            #
    
    Re­place "Your Com­pa­ny Name Here" with the name of your com­pa­ny or or­ga­ni­za­tion. Spec­i­fy the EMAIL ad­dress and TELE­PHONE num­ber of the pri­ma­ry tech­ni­cal con­tact for your or­ga­ni­za­tion. FAX is op­tion­al. The AL­LOW_­RANGE state­ment is re­quired so that li­cens­es are locked to your lo­cal net­work. You may spec­i­fy any num­ber of such state­ments such as
            AL­LOW_­RANGE: 127.000.000.001 127.000.000.001 (rec­om­mend­ed)
            AL­LOW_­RANGE: 192.168.053.000 192.168.053.255
            AL­LOW_­RANGE: 192.168.054.000 192.168.054.127
    
    Af­ter you have com­plet­ed edit­ing the li­cense re­quest form, please send your key re­quest to the dis­trib­u­tor through whom you pur­chased LS-DY­NA (send to at keys@lstc.com on­ly if you pur­chased LS-DY­NA di­rect­ly from LSTC.) Be sure to in­clude any oth­er in­for­ma­tion which is need­ed by LSTC to ful­fill your li­cense re­quest.
  3. START/­STOP THE LI­CENSE SERV­ER:LSTC will send you a 'serv­er_­data' li­cense file for your in­stal­la­tion. Place this file in the serv­er in­stal­la­tion di­rec­to­ry spec­i­fied in (2). It is rec­om­mend­ed that you spec­i­fy a log file for job re­port­ing. Hu­man-read­able en­tries are cre­at­ed in the log file for each job as it starts and stops. Any er­rors which oc­cur dur­ing li­cens­ing will re­sult in er­ror/­warn­ing log en­tries. Use the fol­low­ing com­mand to cre­ate a lot file named lst­clm.log in the cur­rent work­ing di­rec­to­ry:

            ./­lstc_­serv­er -l lst­clm.log
    

    The serv­er runs in the back­ground by de­fault. The serv­er au­to­mat­i­cal­ly cre­ates a kill script which may be used to kill the serv­er.

            ./­serv­er_­kill
    

    The serv­er al­so saves the last start-up ar­gu­ments in a file named "serv­er_­start", so that you may restart the serv­er us­ing the pre­vi­ous set of com­mand line ar­gu­ments, with­out hav­ing to re­mem­ber them.

    NOTE: Make sure that the user who runs the serv­er has per­mis­sion to cre­ate/­ed­it/­re­move any spec­i­fied log file and script files "serv­er_­start" and "serv­er_­kill". The serv­er must al­so cre­ate/­ed­it sta­tus files "serv­er_­sta­tus" and "serv­er_­done_­list".

  4. VER­I­FY THE IN­STAL­LA­TION:Make sure the li­cense serv­er is run­ning.

            ./­lstc_­qrun -s lo­cal­host -r
    

    You should see a full ta­ble of prod­ucts that you have li­censed, com­plete with (a) num­bers of li­cens­es and (b) exi­ra­tion dates. Ver­i­fy that the in­for­ma­tion is cor­rect. If the serv­er does not start for some rea­son, then you will see the mes­sage

            *** ER­ROR failed to open serv­er lo­cal­host
    

    In that case, try start­ing the serv­er in the fore­ground us­ing the -f com­mand line op­tion. The serv­er should print ver­bose in­for­ma­tion about the cause of fail­ure. If you can­not cor­rect the prob­lem on your own, then con­tact LSTC li­cense key sup­port.

  5. FIRE­WALL SET­TINGS:By de­fault, the li­cense serv­er lis­tens on port 31010 (both UDP and TCP/­IP.) So you must con­fig­ure any fire­wall on the li­cense serv­er ma­chine to al­low in­bound da­ta/­con­nec­tions on these ports. You may choose a dif­fer­ent port for the serv­er by adding a "PORT:" en­try in­to the li­cense file. For ex­am­ple, if you would like to use port 31111, then add the fol­low­ing "PORT:" en­try in­to "serv­er_­da­ta" di­rect­ly be­neath the "SERV­ER:" line:

            SERV­ER: E3707F52
            PORT: 31111
    

    *** WARN­ING *** Chang­ing oth­er lines in the file may in­val­i­date the li­cense file.

    If you change the de­fault port num­ber, then all util­i­ties (as well as LS-DY­NA) re­quire that you man­u­al­ly set the port num­ber. For ex­am­ple, you will need to spec­i­fy the port for "lstc_­qrun"

            ./­lstc_­qrun -s 31111@lo­cal­host -r
    

    Adding a file named LSTC_­FILE to the serv­er in­stal­la­tion di­rec­to­ry with the fol­low­ing line will elim­i­nate the need to spec­i­fy a de­fault port/­host name for the li­cense util­i­ties. This will make it eas­i­er to ad­min­is­ter li­cens­es:

    	#LI­CENSE_­SERV­ER: port@host_­or_­ip
    
        or (if us­ing the de­fault port)
    
    	#LI­CENSE_­SERV­ER: host_­or_­ip
    

    How­ev­er, this on­ly af­fects the be­hav­ior of "lstc_­qrun" and oth­er util­i­ties if you run the par­tic­u­lar util­i­ty lo­cat­ed in the serv­er in­stal­la­tion di­rec­to­ry. In­stead of run­ning "./­lstc_­qrun -s 31111@lo­cal­host -r", you may now run "./­lstc_­qrun -r" Of course, you may over­ride the de­fault in LSTC_­FILE by spec­i­fy­ing the -s com­mand line op­tion.