Switch to standard view 
  Sybase logo
 
 
 



SySAM 2.0
Frequently Asked Questions

Q: Do I have to use SySAM?
Using SySAM 2.0 is mandatory with ASE 15. SySAM helps customer’s track license usage to manage compliance. SySAM 2.0 is the updated version of Sybase’s asset management tool. This new version provides effective license management and additional features such as usage reporting, asset management, support for multiple products and automated handling of evaluation.

Q:What happens if a customer has 1000s of machines? Do they each need SySAM running?
Not on each machine. Customers can setup one or more SySAM Network License servers that will dispense licenses to the individual machines running Sybase software. For large installations, such a network license server (where 1 or more SySAM license servers are serving up large number of ASE licenses) configuration is the recommended setup.

Q:What is a common cause of SySAM network server not starting?
SySAM server will not start if there is no valid Served License(s), obtained from SPDC, in the License Directory (e.g. on windows - %SYBASE%\SYSAM-2_0\licenses). SySAM will not start if only Un-served License, obtained from SPDC, are in the license directory. To tell if a license is served vs un-served, examine the content of files with extension .lic, and see if file contains line with keyword SERVER. e.g. SERVER <hostname>. On Windows system, the error message in this case is
From a DOS prompt:
C:\Sybase\ase150\SYSAM-2_0\bin>sysam start
Starting the SYSAM service
The SYSAM service is starting.
The SYSAM service could not be started.
The service did not report an error.
More help is available by typing NET HELPMSG 3534.
On some install scenarios when SySAM 2.0 is installed on a machine which had SySAM 1.0, and you did not do a
clean uninstall, there may be some data files that prevent SySAM server from starting. In these cases you can cleanup
SySAM, by performing a SySAM reinstall:
C:\sybase\SYSAM-2_0\bin>sysam reinstall
Removing the SYSAM service
The SYSAM service has been removed.
Creating the SYSAM service
FLEXlm License Manager is successfully installed

Q:What are the different methods for handling machine identification?
The only method used for identification in SySAM 2.0 is by host ID. The Host ID value depends on the operating system in use. Typically it’s one of embedded Host ID, Ethernet Mac address, Disk Serial number etc. See online help at SPDC for Host ID information.

Q:What if I have multiple networking cards in a system?
For systems that use Ethernet MAC address as host identification, if system has multiple networking ports, lmutil hosted can return multiple MAC addresses. Users only need to submit 1 of the hostid (recommendation to use MAC address from non-removable Ethernet port) in the SPDC registration step.

Q: Does the machine running Sybase software need Internet connectivity?
The machine running Sybase software does not need any internet connection. The licenses can be obtained using any machine with Internet connectivity (or from Sybase CS&S) and transferred to the machine running Sybase software. Because the license strings are long, transferring licenses using removable media may be preferred over typing it in. Note: No portion of SySAM will initiate a network connection outside of the customer’s network, such as back to Sybase.

Q: Does every license instance need to go through activation?
No, using Served License model, a batch of license can be obtained and installed.

Q: Is user privacy sacrificed during the license activation process?
No personal information is required for activating licenses. Only SPDC login and Host ID (Host id or Network card address) are needed to complete activation. The license activation steps are distinct from user registration. License activation does not require user registration.

Q: Can license infrastructure issues cause downtime of the production environment?
Great emphasis has been placed on balancing customer convenience vs. enforcement. Sybase software will not immediately stop working because of License infrastructure issues. Administrators will be notified about License issues via error logs and optional email alert mechanism. Software will continue to run for a specified grace period (7 to 30 days depending on the product). Product functionality will not be crippled during this grace period. Software will get out of grace mode to normal operation, if issues are fixed before the end of the grace period. Network License Server can be deployed with redundancy if desired. Software will shutdown at end of grace period, if the problem is not fixed.

Q: Is it possible to over-deploy software to meet emergency needs?
Licenses can be issued with controlled overdraft numbers. Customers can start software beyond the licensed capacity using this overdraft. Overdraft usage needs to be reconciled with Sybase. Customers can pro-actively lockout accidental overdraft usage.

Q: Can users deploy software without the Sybase provided Installer?
Cases where installation is replicated from a master tar/zip image, customers need to have an activated license available to use. Since in most cases such installs may not get the 30-day time to obtain activated licenses, use of network license server is recommended.

Q: Can I use one key for all of my License servers?
Starting with SySAM 2.0, the license keys are encoded with information about the machine where it will be
deployed. Therefore a license key issued for one machine cannot be used by another.

Q: When a user builds and starts a new server without a license key, what messages does the user see? What is the message in the error log for the missing license?
Adaptive Server and other products adopting SySAM 2.0 allow customers to install and run the products for an initial period without license keys. The period varies based on the product. For ASE, it is 30 days.
When user starts ASE without license keys, the following message will be displayed in the ASE errorlog:
00:00000:00000:2005/07/05 15:46:08.84 kernel Sybase Licensing: Using licenses from: /opt/sybase/SYSAM- 2_0/licenses
00:00000:00000:2005/07/05 15:46:08.91 kernel Sybase Licensing: Checked out graced license for 1 ASE_CORE (2005.0703) will expire Tue Jul 5 15:47:02 2005.
00:00000:00000:2005/07/05 15:46:08.91 kernel Sybase Licensing: Failed to obtain 1 license(s) for ASE_CORE feature from license file(s) or server(s).

The message indicates the time when the grace period expires. Optionally, the customer is able to setup email notifications during product installation, in which case, an email will also be sent about the situation. This notification is repeated through the grace period with increasing frequency. If the license is provided during the grace period, ASE automatically picks up the license (does not need to be restarted). If a license is not found at the end of the grace period, then ASE shuts down. Subsequent restart of ASE will not be successful. The following entry in errorlog indicates no license available and grace period expired:
00:00000:00000:2005/07/05 16:09:12.96 kernel Sybase Licensing: Using licenses from: /usr/u/sybase/SYSAM- 2_0/licenses
00:00000:00000:2005/07/05 16:09:13.06 kernel Sybase Licensing: Failed to obtain
1 license(s) for ASE_CORE feature from license file(s) or server(s).

Q: How do I select who gets the warning emails regarding license issues?
During the ASE installation process, there is a dialog where this information can be provided. After installation, use the sp_lmconfig stored procedure to modify this configuration. See ASE Installation Guide, ASE Configuration Guide, and ASE Reference Manual for more details.

Q:What happens if my license server goes down?
If the license server goes down or ASE cannot communicate with it for any reason, ASE will fall into a “grace period”. This grace period is for 30 days. The ASE errolog will be updated with this information. If email alerts are setup, an email message will be sent. ASE is fully functional during this grace period. ASE will go back to normal mode, when the issue causing the failure is fixed. If the issue is not fixed, ASE may shutdown at the end of the grace period. The final action depends on the features whose license was lost—if the license is for an optional feature, that feature is disabled. If the license was for the base ASE, then ASE itself is shutdown. ASE errorlog is updated with an increasing frequency during the course of the grace period. Current ASE license status can be examined anytime by using the “sp_lmconfig” command.

Q: Does ASE do a heartbeat check on the license info?
Yes, ASE will periodically perform a heartbeat task with the license server to synchronize license usage information.

Q: How fast does ASE detect that the license info is not available?
ASE can detect lack of a license at startup or during a heartbeat cycle. ASE performs heartbeat checks approximately once every 4 hours.

Q:Will SySAM Licenses expire?
This depends on the type of license purchased. For traditional perpetual licenses, the SySAM license issued is a permanent license. For software purchased under “SybaseFLEX” licensing terms, the license issued is with an expiration date that corresponds to the end of the lease term. Evaluation licenses expire at the end of the evaluation period.

Q: Do SySAM Licenses need to be renewed?
While the SySAM licenses issued may be permanent, the license also embeds the date when Customer’s current support contract ends. When customers renew support, they should renew the SySAM licenses, so that the support end date is updated. When a customer installs updates/EBFs for ASE, the install checks for the support end date. If the update/EBF was released after the end of their support, Sybase will warn users not to install the update / EBF. If installed, the update may not work. Customers will need to renew support or revert to a release that was released while they were in support.
Customers renew their SySAM licenses from SPDC.We provide a one year grace period for customers to renew such licenses.

Q:What happens if the customer can't give out machine names, Host-ID or IP address?
We do not require customers to provide the hostname/machine name. The value is needed in the license file,
customers can provide it during license activation or add it to the license after license it is acquired from Sybase.
An IP address is never requested.

Q: Can machines be deployed with the licenses on them in a standalone configuration? Does SySAM need to be running?
SySAM can be deployed in standalone server-less mode or in network license server mode. In a stand-alone serverless mode, there is no need for a license server. Sybase products obtain the license by directly reading the license file. Licenses need to be individually activated for each machine in server-less mode. Therefore this approach is not scalable for large installations. This configuration also does not provide any license usage reporting.

Q:What happens when hardware needs to be replaced? Motherboards fail and need to be replaced? Network cards fail and need to be replaced?
Customers can re-activate the license(s) on new hardware by re-hosting the license from SPDC. The limit of rehost is 200% the number of the licenses per year. If you pass this limit, please call SYBASE CUSTOMER SUPPORT& SERVICES (CS&S).

Q:What is the longest grace period allowed?
This depends on the Product in question. For ASE, the longest grace period allowed is 30 days.

Q:What happens once the grace period expires?
ASE server will stop running. In case more time is required, please contact SYBASE CUSTOMER SUPPORT &
SERVICES (CS&S).

Q: How do we handle multiple versions of SYSAM running on the same machine?
The network license server from SySAM 2.0 can serve licenses for both SySAM 2.0 (ASE 15.0) and SySAM 1.0 (ASE 12.x, ASE 12.5.x and other Sybase products). Refer to the ASE Configuration Guide for details on upgrade and co-existence options.

Q: Can SYSAM count individual users? Will it have this capability in the future?
The current implementation of SySAM for ASE does not enforce Concurrent User or Network Seat licenses. Such usage information is however printed in the ASE errorlog for customer’s information.We may perform such enforcement in the future releases.

Q: How are legacy licenses handled?
All currently active license types are handled by SySAM. There is no change to the license terms associated with these licenses. SySAM will attempt to enforce the closest approximation of the license terms associated with these license types.

Q: How does SySAM work in a high-availability environment?
The network license server can be deployed in a high-availability configuration. But because of the grace periods provided by SySAM to account for license outages, we feel that the overhead to deploy a high-availability license server is not justified. Note that the high-availability configuration for License server is a proprietary FLEXlm implementation. See FLEX net Publisher End User Guide for details. There are some restrictions when Network license server is deployed on machines that use operating system or third party clustering solutions (such as Sun Cluster, Veritas to name a few). See ASE Configuration Guide for details.

Q: Where do I get my license key?
License key is available from SPDC. https://sybase.subscribenet.com.

Click here to view the SySAM 2.0 Frequently Asked Questions in PDF



Back to Top
© Copyright 2010, Sybase Inc.