• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. setenv LBS_CLUSTER_MANAGER

Stats

  • Locked Locked
  • Replies 13
  • Subscribers 126
  • Views 17039
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

setenv LBS_CLUSTER_MANAGER

JustinTaylor86
JustinTaylor86 over 13 years ago

 Hi,

 

Does anyone know how to set LBS_CLUSTER_MANAGER environment varaible?

 

Thanks,

 

Justin

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Hi Justin,

    I assume you mean LBS_CLUSTER_MASTER? The env var LBS_CLUSTER_MANAGER doesn't mean anything to the Cadence Tools.

    Did you try reading the Virtuoso Analog Distributed Processing Option User Guide ? (<ICinstDir>/doc/distproc/distproc.pdf )

    What is the problem you're trying to solve?

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • JustinTaylor86
    JustinTaylor86 over 13 years ago

    Yes I am looking at that pdf but it's not very clear for me how I can set this LBS_CLUSTER_MANAGER to look at my host.

     

    I also can't find where the .cshrc file is.

     

    I am trying to set up distributed processing.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Maybe you're using a different shell - e.g. ksh or bash? If using bash, you'd put:

    export LBS_CLUSTER_MANAGER=hostName

    in the .bashrc (say). This is basic UNIX knowledge - so you should find out which shell you're using, and set the environment variables the appropriate way for the shell you're using.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • JustinTaylor86
    JustinTaylor86 over 13 years ago

     Thanks, that worked.

     Next issue is 

     ERROR (219): The script failed to detect the OS type of "hostname"

     .....make sure the following command is running without problem

     ../../../tools/dfII/bin/cdsDPrsh.

     How can I make sure it is running?

     Thanks,

     Justin

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Justin,

    You didn't say what you were doing at the time, but my guess is that you might have been using the "check setup" option, and it's unable to rsh onto the remote machine.

    You might need to configure cdsRemsh to use ssh instead of rsh - maybe rsh is not allowed in your environment? That can be done by following the instructions in <ICinstDir>/share/cdssetup/cdsRemsh/cdsRemote.scr assuming you're using IC61X.

    Otherwise, please log a service request

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • amwygah
    amwygah over 13 years ago

    Hi Andrew,

    Could you tell me where can i modify rsh to ssh in my ic5141 ?

    Thanks,

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    For distributed processing, you can set this via the .cdsenv setting:

     asimenv.distributed remoteShell         string          "rsh"

    (that's the default), or the equivalent SKILL:

    envSetVal("asimenv.distributed" "remoteShell"   'string   "ssh")

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • amwygah
    amwygah over 13 years ago

     

     Thans for reply

    and now my check setup result is like this:

     ##############################################################################
    Checking Distributed Processing (DP) setup..........
    ##############################################################################
    Current User is:  eda5141
    Submission host name is: amwygah-desktop
     
    Checking for DP environment variables.....
    ##############################################################################
     
    Environment variable LBS_CLUSTER_MASTER is set to 202.115.29.26
    Checking for LBS mode setup
    Checking if cdsqmgr is running properly on "202.115.29.26" .........Ok
    Checking if cdsNameServer is running properly on "202.115.29.26" .........Ok
    Checking for queue config file...
    Using variable CDS_QUEUE_CONF_FILE as this is set to /home/eda5141/queue_config
    ********************************************************************************
     The queue config file identified is /home/eda5141/queue_config                        
     This may not be correct due to the OS command's (ps) limitations.             
     You can set the env variable CDS_QUEUE_CONF_FILE to specify the queue config  
     file used by the cdsqmgr daemon running on 202.115.29.26                     
    ********************************************************************************
    ##############################################################################
    Checking if the hosts are up......
    ##############################################################################
     
    ##############################################################################
    Checking for password related requirements(from Submission to Cluster Hosts)
    ##############################################################################
     
    ##############################################################################
    Checking for password requirements in reverse direction (from Clusters to Submission Hosts)
    ##############################################################################
     
    ##############################################################################
    Checking for hierarchy compatibility with login shell: none
                  1. Check for the hier locations
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                  2. Check for the presence of spectre binary.
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                     <<< Local spectre version : 7.2.0 >>>
                  3. Check for the presence of cdsserv binary.
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                     <<< Local cdsserv version : 06.00 >>>
    ##############################################################################
     
    ##############################################################################
    Checking for space in /tmp area.......
    ##############################################################################
     
    ##############################################################################
    Checking for Network Mode......
    ##############################################################################
     
    ##############################################################################
    Checking if artmonitor works...FAILED.
     
    WARNING (220): Although the setup appears to be fine, artmonitor
    is not responding. Therefore, DP may not run. It might be a network
    or the DP daemon related issue.
    ##############################################################################
     
    Setup check completes with 0 errors and 1 warnings.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • amwygah
    amwygah over 13 years ago

     and the content of CDS_QUEUE_CONF_FILE just like this

    queque 1
    eda5141@ubuntu-eda 20

     

    And in the /etc/hosts, i resolve  ubuntu-eda to 202.115.29.166

     

    does it should be right?

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

     I suggest you log a service request - I don't really have the time to debug this myself right now (have you tried just running a simulation?)

    I probably wouldn't put an "@" in the hostname - it's supposed to just  be a hostname (I'm guessing that's a username for the ssh before the @ ?).

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
>

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information