Scalable Network Technologies: QUP Membership Requirements

Submit a completed license agreement.
Remit payment according to the Payment Schedule to Scalable Network Technologies. Note: applicants from countries outside of North America will be routed to the QualNet Distributor in their region for pricing. If no distributor is specified, SNT will manage the transaction.
Be currently employed as a full-time professor at a college or university OR sponsored by a currently employed full-time professor at a college or university.
Agree that the software license will be used for teaching or research purposes with no work done by or for an employee, contractor, or agent of any commercial or for-profit organizations.
Agree that the software shall not be used for commercial business purposes, whether or not a payment is made or expected.
Ensure that QualNet is present only on the licensed research or teaching workstations.
Agree that all work done with the aid of discounted Scalable Network Technologies software and tools will be done in the lab holding the QualNet license.
Any materials, inventions, or findings produced by the recipient, directly or indirectly, through the use of Scalable Network Technologies software will be made available in the public domain upon completion.
Agree that a QUP Button & QualNet Link will be displayed on a university research project web page. The HTML markup to display the image and link will be provided by Scalable Network Technologies.
Agree not to decompile, disassemble, or otherwise reverse engineer the executable code or data files supplied with the software, or produced as output files by the software.
The licensee is not authorized to sublicense, distribute, sell, or rent access to the software, or use the software as part of a service bureau, or other program sharing activity.
The QualNet source code is licensed, not sold, and is subject to this written license agreement. Among other things, no portion of this source code may be copied, transmitted, disclosed, displayed, distributed, translated, used as the basis for a derivative work, or used, in whole or in part, for any program or purpose other than its intended use in compliance with the license agreement as part of the QualNet software. This source code and certain of the algorithms contained within it are confidential trade secrets and/or copyrighted material of Scalable Network Technologies, Inc. and may not be used neither as the basis for, nor incorporated into, any other software, hardware, product, or service.

QUP participants must include a SNT provided image and a link to our site on their research project webpage. After completing the membership application, please insert the following HTML markup on your project page (the image and link may be spearated):

When you purchase QualNet, you will need to install a license server. The license server runs on a single computer in your network and requires very little resources. The license server software is supported on Linux, Mac OS, Windows NT/2000/XP, and Solaris SPARC.

You can install QualNet itself on any number of computers in your network, on any of the above operating systems. These computers, though, must have an IP address belonging to your organization or lab (the permitted IP addresses are designated by you on your application form).

Usually an organization or lab has purchased one floating license. With this license, you can have QualNet installed on all the computers in your organization or lab. However, only one person can be actively using QualNet at any given time. If that person isn't actively using QualNet, you can have one simulation running. If someone else wants to use QualNet, the first user will have to stop using QualNet (terminating any running simulations and GUI programs) before the second user can start. Users will have to share the one floating license, in other words.

If you have three floating licenses, then any three users can be actively using QualNet at any given time; if none of these users are actively using QualNet, then three simulations can be running.

This section discusses the resources used by the license server. When you select a server node, you may need to take into account the system limits on these resources. For small numbers of licenses (under about 100), most of these items should not be a problem on any workstation.

When you run lmgrd, it automatically starts up one copy of each vendor daemon specified in the DAEMON line(s) in the license file. Each time a TCP client connects to the server, it uses a process file descriptor. If the maximum number of file descriptors is exceeded, additional vendor daemons will be started to accommodate the overflow requests.

When using TCP a single vendor daemon can support as many users as the system limit for file descriptors, which ranges from 256 on SunOS 4.x to 4000 on OSF/1. When files are exhausted, additional vendor daemons are spawned to allow for extra file descriptors. When using UDP, there is no limit to the number of end-users per vendor daemon process, since they can share a single socket in the vendor daemon.

Each client connected to a license server uses one socket. The total number of sockets used by the license server programs is slightly larger than the total number of simultaneous clients.

On SCO`systems, the default number of sockets may be set fairly low; if you choose to run a server on such a machine, you may need to reconfigure your kernel to have more sockets.

The license server uses very little CPU time. The server might have only a few seconds of CPU time after many days.

For a large number of clients (who are each exchanging heartbeat messages with the server), or for high checkout/checkin activity levels (hundreds per second), the amount of CPU time consumed by the server may start to become significant although, even here, CPU usage is normally not high. In this case, you may need to ensure that the server machine you select will have enough CPU cycles to spare.

The only output files created by the license servers are the debug and report log files. These log files contain one line for each checkout and one line for each checkin. If you have a lot of license activity, these log files will grow very large. You will need to consider where to put these files and how often to delete or prune them. The license administrator can opt not to log messages to the debug log file if disk space is at a premium.

The FLEXlm daemons use little memory. Typically, lmgrd uses approximately 100 kB and the vendor daemon uses approximately 120 kB.

FLEXlm sends relatively small amounts of data across the network. Each transaction, such as a checkout or checkin, is typically satisfied with less than 1Kbyte of data transferred. This means that FLEXlm licensing can be effectively run over slow networks (such as dial-up SLIP lines) for small numbers of clients.

The value of the "License server hostid" depends on which operating system the license server is running.

On Windows NT/2000 and Linux, it is the MAC address of any network interface installed on the license server. To obtain this on Windows, run "ipconfig /all" -- on Linux, /sbin/ifconfig -a. The hardware address has this format:

If the QualNet license server has more than one IP address, please use the first IP address of the first network interface.

QualNet can be run only on computers within a specific range of IP addresses. The range you specify should belong to your organization.

For off-site users, we recommend that you set up an ssh server on on-site UNIX machine(s) where QualNet is installed. Users can ssh in, and run QualNet from there. Graphics-intensive parts of QualNet, however, do not work very well in this way, as they require a bandwidth-hungry X session, but console sessions are fine in our experience.

The example below lists a single class C address. Larger organizations may have a class B address. University labs sometimes have multiple subnetted class C addresses (e.g., 131.179.96.*, 131.179.120.*), and it's fine to list these, or the larger class B address (131.179.*.*).


	Scalable Network Technologies, Inc. Privacy Statement Copyright © 2006-2008.