Table Of Contents
Release Notes for CiscoWorks Common Services 3.1 on Solaris
Time Zone Acronyms and Offset Settings
Integrating with Third-party Vendors
CiscoWorks Home Page Known Problems
Software Center Known Problems
Integration Utility Known Problems
Grouping Services Known Problems
Internally-Found Resolved Problems
Customer-Found Resolved Problems
Obtaining Documentation, Obtaining Support, and Security Guidelines
Open Source License Acknowledgements
Release Notes for CiscoWorks Common Services 3.1 on Solaris
This release notes is for CiscoWorks Common Services 3.1 running on a Solaris platform.
The release notes contains the following sections:
•
Time Zone Acronyms and Offset Settings
•
•
•
•
New Features
The new features in CiscoWorks Common Services 3.1 are:
•
The Common Services installation framework is enhanced to support installation of multiple applications in one solution bundle. You can install Common Services 3.1 or upgrade the earlier versions to Common Services 3.1, using the single installable bundle image packaged in the LMS 3.0 product DVD.
Common Services 3.1 now provides a cleanup script for both Solaris and Windows. If an installation fails, this script clears the files from the installation directory.
•
You can configure a default credential set comprising primary, secondary, SNMP, HTTP and RxBoot Mode credentials, and store them in DCR. You can also add or import devices into DCR with the default credentials.
•
DCR allows the applications to store primary device credentials such as Primary Username, Password, and Enable Password. The primary device credentials allows the applications to access the devices and operate on them.
In this release, DCR allows you to add a secondary set of credentials. The secondary credentials serve as an alternative to primary device credentials.
Applications such as Resource Manager Essentials can use the configured secondary credentials as a fallback, if they cannot access the devices using the primary credentials.
•
The earlier DCR command line (CLI) utility allowed you to delete devices using their device ID.
With the enhanced DCR CLI delete devices option, in both shell and batch modes, you can delete the devices using their own identifiers such as hostname and domain name combination, and display name.
You can also delete devices from DCR as specified in the input CSV file, using the enhanced DCR CLI utility.
The DCR CLI now provides an option to export the device information from DCR to ACS Server.
•
Common Services 3.1 has the following security related changes:
–
Common Services supports integration of ACS 3.3.4 for Windows Server and Appliance (except ACS 3.3.4 Appliance), and ACS 4.1 for Windows Server and Appliance with CiscoWorks server, in addition to the support for ACS 3.3.3 and ACS 4.0 versions.
This security related enhancement requires the role and task definitions to be revisited. You should register the revised role and task definitions with ACS Server in the ACS mode.
–
In the enhanced Permissions Report, the tasks are grouped based on applications and displayed in a tabular form. This allows you to quickly locate a particular task in the report.
You can also sort the display of tasks in alphabetical order or in reverse alphabetical order within a task group.
–
This is a predefined role introduced in this release. This role has full access rights to perform any task including the administration and approval tasks in CiscoWorks.
You can assign this role to a user only on ACS Server and only when your login module is set to ACS. This role is not available in CiscoWorks local mode and during the local user setup in CiscoWorks Server. The Permissions report does not display information about this role.
–
Earlier, CiscoWorks supported only distinguished name based authentication to Microsoft Active Directory Server.
In this release, the integration of CiscoWorks Server with Microsoft Active Directory Server is made more flexible.
CiscoWorks now also supports User Principal Name (UPN) based authentication, domain name based authentication, and Security Account Manager (SAM) account based authentication to the Microsoft Active Directory server.
–
In the earlier releases, Common Services allowed you to add local users to CiscoWorks Server only through the user interface. Common Services did not support bulk addition of local users.
With the introduction of a script for adding local users, you can add bulk local users through CLI. You can also import the local user information from remote servers of similar version through CLI.
•
CiscoWorks home page and the application windows that are launched from CiscoWorks home page now contain the name of the CiscoWorks Server along with the browser title.
This feature helps you to identify the server in which the applications are installed. This is particularly useful in a multi-server setup and Single Sign-On (SSO) based setup.
•
Common Services 3.1 provides an enhanced user interface to select a specific SSH protocol version (SSHv1 or SSHv2) for a device using the Management Station to Device tool. This is used to test the protocol connectivity against the chosen device.
•
The new Logging Configuration user interface allows you to enable debug modules in Common Services such as DCR, Software Center, CiscoWorks home page and so on.
You do not need to restart the daemon manager after you have enabled the debugging option for a particular module.
•
You can monitor the disk space availability in your CiscoWorks Server and configure the threshold level of disk space utilization. You can also set an option to notify end users through e-mail when the disk space exceeds the selected threshold level.
•
The Backup-Restore component is enhanced to send you an e-mail on the status of immediate or scheduled backup jobs when they complete.
The e-mail notification is also sent when you schedule a backup job or remove a scheduled backup job.
You should configure one or more e-mail addresses if you want to receive the email notification.
•
Earlier when you changed the hostname of the CiscoWorks Server, you needed to manually change the hostname related entries in the CiscoWorks directories and files, registry entries, and databases.
Common Services 3.1 provides a script to automatically update the CiscoWorks directories and files, registry entries, and databases, after you have changed your hostname.
•
Earlier, you could not create a device group for devices within a specified IP Address range.
With the introduction of new range operator, you can group devices within a range of IP Addresses. You can also perform an advanced search of devices within a specified IP Address range.
•
Common Services 3.1 supports new LMS applications namely CiscoWorks LMS Portal and CiscoWorks Assistant that help to improve the usability of existing applications in the LMS bundle.
CiscoWorks LMS Portal helps you to set up a customized home page. The status summary of Common Services jobs, security configurations and other information are available as portlets in the LMS Portal application.
CiscoWorks Assistant is a web-based tool that provides workflows to help you to overcome network management and LMS deployment challenges. Using CiscoWorks Assistant you can easily deploy multiple LMS server and maintain device credentials.
See the User Guide for CiscoWorks LMS Portal 1.0 and User Guide for CiscoWorks Assistant 1.0 for more information.
•
Meta Data Framework (MDF) Package defines device types in a uniform way across CiscoWorks applications. This package contains new device types, new device type definitions, new device icons, and solutions to some problems in earlier MDF packages.
This package contains new device types, new device type definitions, new device icons, and solutions to some problems in earlier MDF packages.
The MDF package version 1.18 contains the following new device types:
–
–
–
–
–
When you add new device types through MDF Package, it does not guarantee support for these device types in all the CiscoWorks applications.
Device support has to be provided by individual applications, such as DFM, RME and Campus Manager. For a list of supported device types, see the relevant Product Documentation at the following URLs:
http://www.cisco.com/en/US/products/sw/cscowork/ps2421/products_device_support_tables_list.html
http://www.cisco.com/en/US/products/sw/cscowork/ps2073/products_device_support_tables_list.html
http://www.cisco.com/en/US/products/sw/cscowork/ps563/products_device_support_tables_list.html
For details on Common Services 3.1 features, see:
http://www.cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html
Product Documentation
Note
Table 1 describes the CiscoWorks Common Services documentation that is available.
Table 1 Product Documentation
Release Notes for CiscoWorks Common Services 3.1 on Solaris (this document)
•
–
–
•
User Guide for CiscoWorks Common Services 3.1
•
–
–
•
http://cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html (part number OL-11776-01)
User Guide for CiscoWorks Integration Utility 1.7
•
–
–
•
http://cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html (part number OL-13627-01)
Context-sensitive Online help
•
Time Zone Acronyms and Offset Settings
Table 2 shows time zone acronyms supported in the CiscoWorks applications that use the time zone feature.
•
•
•
•
•
•
If you generate reports, the output will vary depending on whether the data has been processed through Perl or Java. Table 2 also provides possible output for either case scenario.
To ensure that time zones are translated correctly—especially when your devices, servers, and clients are in different time zones—follow these guidelines:
•
•
•
Changes made to the system time zone from outside CiscoWorks applications might not be reflected in already-running CiscoWorks applications. After changing the time zone, restart all CiscoWorks applications.
Multi-homed Machines
A multi-homed machine is a machine that has multiple NIC cards, each configured with different IP addresses. To run CiscoWorks Common Services on a multi-homed machine, there are two requirements.
•
•
To select an IP address:
Step 1
Step 2
•
•
•
•
Step 3
/etc/init.d/dmgtd start
Operating System Upgrade
While installing CiscoWorks Common Services, the installation process checks for required patches. Install any missing solaris patches and cluster patches.
For a list of required patches, see Chapter 2 of Installing and Getting Started with CiscoWorks LAN Management Solution 3.0 at: http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html.
Caution
Server and Client Information
For information on server and client requirements for the system and browser, see the Prerequisites chapter of Installing and Getting Started With CiscoWorks LAN Management Solution 3.0.
Integrating with Third-party Vendors
Use the Integration Utility to integrate Cisco device information and Cisco applications into SNMP management platforms such as:
•
•
Note
See User Guide for CiscoWorks Common Services 3.1 and the online help for information about importing devices.
You might need to run the Integration Utility to:
•
•
•
•
For more information on Integration Utility, see User Guide for CiscoWorks Integration Utility 1.7.
Known and Resolved Problems
Tables 3 to 10 describe the problems known to exist in this release; Tables 11 and 12 describe the problems resolved from Common Services 3.0 onwards.
Note
The CiscoWorks Common Services known problems are broken down into the following sections:
•
•
•
•
•
•
Installation Known Problems
Table 3 describes the known problems related to the installation of Common Services.
CiscoWorks Home Page Known Problems
Table 4 describes the known problems related to CiscoWorks homepage.
Software Center Known Problems
Table 5 describes the known problems that you might encounter while working with Software Center.
Integration Utility Known Problems
The file NMIDBOptions.properties contains Cisco.com passwords, in an encoded form, and is accessible only to root users. Root access to the host needs to be restricted if Cisco.com password security is a concern.
Table 6 describes the known problems related to Integration Utility.
Browser Known Problems
Table 7 describes the known problems that you might encounter with web browsers.
Table 7 Browser Known Problems
CSCsh21917
In the PSU device download operation, the Close button in the Job Details URL does not work.
When Mozilla is used as the Client bowser, the window launched for the Job Details URL during the PSU device download operation does not close.
Workaround:
Either:
•
Or
•
CSCsh49922
Cannot use Telnet to connect to a device from Ciscoworks > DeviceCenter > Telnet.
This occurs when Internet Explorer 7 is used as the Client browser.
Workaround:
The following can be done:
•
Or
•
Or
•
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_DISABLE_TELNET_PROTOCOL] "iexplore.exe"=dword:00000000 and then restart the browser.
CSCdt11838
While launching an application, you are not prompted to install the Java Plug-in.
If you install RealJukeBox Netscape Plug-in before you install Java Plug-in, you are not prompted to install Java Plug-in software when you launch an application. A blank screen appears.
Workaround:
Install Java Plug-in manually. For more information regarding the Java Plug-in, see the Server and Client Information.
CSCsa31202
Tooltips in UII get truncated in Netscape and Mozilla browsers.
If the tooltip for the data cell within HTML scrolling table is large, Netscape and Mozilla browsers truncate the last few characters.
This does not occur for Internet Explorer 6.0.
Workaround:
None.
CSCsc19380
Cannot select the contents of certain pages.
For example, you cannot select the contents of Results page after a PSU operation.
Copying the contents of a page is not possible when using Netscape/Mozilla browsers.
Workaround:
Use IE when the contents of a page need to be copied.
None.
If you have a popup-blocker enabled in your browser, popups do not appear.
Popups do not appear
Workaround
Disable the popup-blocker, if you have installed any.
DCR Known Problems
Table 8 describes the known problems that you might encounter while working with DCR.
Grouping Services Known Problems
Table 9 describes the known problems associated with managing groups of devices.
General Known Problems
Table 10 describes the miscellaneous known problems associated with Common Services (not specific to any module in Common Services).
Table 10 General Known Problems
CSCsi66749
Device authorization fails in ACS mode though the devices are displayed in DCR Administration and in application pages.
When CiscoWorks is in ACS mode, device authorization fails for some of the IP addresses of devices.
This happens when you enter multiple IP addresses of devices with the total length exceeding 4096 characters, during AAA client configuration in ACS.
This is because ACS does not support more than 4096 characters in the IP Address field for a AAA client configuration.
Device authorization fails for devices whose IP addresses are entered after the 4096th character.
Workaround:
Add multiple IP Addresses with the total length not exceeding 4096 characters.
CSCsi87682
Cannot launch LMS 3.0 on Internet Explorer 6.x after LMS 3.0 is installed.
When LMS 3.0 is uninstalled and then installed again on an LMS configured server using Internet Explorer 6.x, the product does not launch.
Workaround:
In Internet Explorer 6.x, enable the Use TLS1.0 option in Tools > Internet Options > Advanced > Security.
CSCsh24651
Improper connection to database caused by no disk space leads to indefinite waiting.
When there is no free space available in the NMSROOT drive, the database server will be slow as it performs operations on the temporary files created by Sybase.
Workaround:
Restart Daemon Manager after freeing up some disk space.
CSCsa63026
Page not found error appears when installing new device packages.
When adding new device packages through RME > Software Center > Device Update, the Daemon Manager script, dmgtd restarts.
The browser attempts to access a URL on the server but the page does not load because dmgtd has restarted. Instead, it displays a Page Not Found error.
Workaround:
None.
CSCsg84927
Error or warning messages opens in a new tab.
Any notification window (error or a warning message) opens in a new tab instead of a new window.
Workaround:
Launch the application links using <a href=[url]/>.
CSCsg84924
In Firefox 2.0, any link opens in a new tab instead of a new page.
If you select an item from the Table of Contents items for an application in the CiscoWorks page, it opens in a new tab instead of a new page.
Workaround:
Use Options > Tabs > Use Options > Tabs > Open in a new window, to activate this option.
CSCsg84938
In Firefox 2.0, the minimise button should be disabled for all notification windows.
A notification window that requires an action from you, must not have an optin to minimize it. However, such an option is available in Firefox 2.0.
Workaround:
None.
CSCsi01719
On Solaris 10, authentication fails while configuring AAA server setup.
This happens while creating and logging in the local user for the AAA server setup mode using local Unix system as a login module.
Workaround:
None.
CSCse01118
Registration of any application from a remote server fails.
If you add a remote server's certificate in the peer server certificate setup, the registration fails and an error message appears.
Workaround:
None.
CSCsg76235
Portlets do not appear if you launch the server before some application is registered.
This problem occurs when the Portal engine is not started and ready. However, Tomcat and other deamons are started.
When Tomcat or the deamons are restarted, the application will get registered with the portal engine and if you try to launch the server before this then the application will not appear.
Workaround:
Wait for sometime and the portlets will appear.
CSCsi52867
Cannot access some portlets until you refresh the screen.
Some portlets display messages such as
You do not have the required role to access this portlet
although you may have System Administrator privileges.This problem could occur when you have opened multiple sessions.
Workaround:
Refresh the screen to view the details.
CSCsg54946
If you configure mail.yahoo.com or http:// in IFrame and click Back, it launches in a full window.
After configuring the URL, if you click Back, the screen occupies the entire window.
Workaround:
Use the following URL to remove all the IFrame portlets in the view protocol://servername:portno/cwportal/c/portal/RemoveIFrame.
CSCsh94522
Portlet menu options may not appear correctly
In this case even if the portlets appear, the submenu options may not appear.
This can occur if the browser's cache has stale data for the server in question.
Since the portal web pages do not specify any caching pragmas, the browsers will cache the content.
Workaround:
Clear the browser cache.
CSCsi96540
Some portlets are missing in Functional view after Remote Migration.
After you migrate, some portlets do not appear in the Functional View.
For instance, if you have installed an application, some portlets will not appear in the Functional View.
Workaround:
Unregister the missing application and re-register the application.
To re-register the application do the following:
Go to CS > Server> Home page Admin >Application Register > Register.
CSCsh27565
When Syslog is more than 4 GB, the crmlog service does not start.
During start-up when the crmlog process loads the syslog.log for writing, if the file is more than 4GB, the file loading fails.
Workaround:
The syslog needs to cleared or rotated when it is more than 4 GB.
CSCsa38716
Management Statement To Device picks up the altered port value from the etc/services file.
This occurs when the third-party SNMP agent changes the standard SNMP port value. The Management Statement To Device picks up this altered port value, queries the device and fails.
Workaround:
Make sure that the SNMP port value is 161.
CSCec82508
When multiple community string support is enabled on Campus Manager, the devices become unreachable in topology.
This problem is caused by the way IOS responds when it has a community defined with no view for it.
Workarounds:
•
•
•
CSCin07838
Cannot invoke CiscoWorks if you start Daemon immediately.
Cannot invoke CiscoWorks if you stop the Daemon Manager and restart it immediately.
Workaround:
Do not restart the Daemon Manager immediately after stopping it. You must wait for some time for the ports to be released.
CSCin16992
EDS displays errors when you change the hostname.
The errors appear if you change the hostname without restarting the daemons.
Workaround:
See the following link:
http://cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html
CSCin22086
JRM does not schedule jobs properly when you change the system time manually.
JRM time does not reset when you change the system time manually.
Workaround:
Restart Daemon Manager by entering /etc/init.d/dmgtd start
CSCin41971
Authentication from NMS fails for valid users.
This problem occurs when:
•
•
•
Workaround:
Configure the primary IP address of the NMS as a client in ACS.
CSCin59328
CatOS returns the engine parameters only when you initiate two requests.
CatOS returns the SNMP engine ID, boots, and time values only when you initiate two requests.
Workaround:
None.
CSCsa03997
Shortcuts to links are not preserved after upgrade.
The shortcuts that you create in the earlier version of CS are not preserved when you upgrade to CS 3.1.
Workaround:
None.
CSCsa04366
If you send two SNMP queries when there is congestion, the response for the second request fails.
This occurs when the device is flooded with heavy traffic or when it is busy.
Workaround:
None.
CSCsa12204
Cannot perform Restore if you take a backup on a mounted directory from GUI.
Restore displays the following error:
Cannot find the generation in the backup directory [<backup Directory>].Verify the backup directory and the generation.This occurs under the following conditions:
1.
2.
3.
Workaround:
Give read permission to Backup Director for Others in the Backup Server (Server A).
CSCsa24015
Evaluation license expires few hours before the default 90 days period.
This problem occurs when the Time Zone TZ value in /etc/TIMEZONE is set as GMT+5 then CiscoWorks applications installed in Evaluation mode will expire 5 hours before 90 days.
Workaround:
Set the time zone opposite to the one that is actually required and restart the machine.
For example, if GMT+5 is the required time zone then set the time zone to GMT-5.
CSCsa24624
Apache does not start after installation, if the kernel parameters are not configured,
If the kernel parameters are not configured, Apache process does not start and results in a core dump.
This occurs when the shmget system call fails.
Workaround:
Configure the semaphore and shared memory-related kernal parameters in /etc/system file.
CSCsa24921
Packet Capture status displays wrong messages if the Packet Capture time is short.
When device IP is not reachable, the Packet Capture status window displays wrong messages. This occurs if Packet Capture time is short.
Workaround:
Perform Packet Capture for a longer time.
CSCsa26875
Error messages appear when you stop jobs.
When you stop jobs before their completion, some error messages with codes appear such as:
Cannot stop job 1064.14.The problem occurs when the you try to stop the job just milliseconds before the job completes.
Workaround:
Stop the job again to see the proper error message.
CSCsa29023
If you enter wrong SNMPv3 credentials when Multiple Community String (MCS) is enabled, SNMPv1/v2 credentials are not taken into consideration.
Multiple community string is not applicable only to SNMPv3. This is available only for SNMPv1/v2.
Workaround:
None.
CSCsa38647
Event Services Software (ESS) does not start.
This problem can occur when a machine is configured to access NIS.
Workaround:
Remove the NIS entry for services in the /etc/nsswitch.conf file.
Modify the services entry to services: files
CSCsa83440
Cannot resize the columns in HTML scrolling tables.
This is the UI behavior.
Workaround:
Place the cursor on top of the text (do not click). The entire text present in the column will be displayed.
CSCsb54879
The format in which the document appears after PDF export in a report is improper.
When you export data to a PDF file in a report, the following inconsistencies appear:
•
•
•
Workaround:
None.
CSCsb71591
Application links appear after upgrading to CS 3.0.3 from CS 3.0.
Applications are not disabled during an upgrade from CS 3.0 to a higher version. So, application links appear.
Workaround:
Upgrade all applications to the latest available version for proper functionality.
CSCsc24337
RME uses send mail application interface of CS for sending mails.
All RME jobs fail with a message
Unable to Send Mail.This happens because the port (25) is blocked.
Workaround:
Set the option given below:
Start > Network Associates >
VirusScan Console > Access Protection > Uncheck the Prevent Mass Mailing Worm From Sending Mail checkbox.CSCsc38627
JRM failed to run, JRM core dump created under NMSROOT.
While creating jobs in RME, JRM fails to run and JRM core dump is created.
This is not consistent.
Workaround:
Restart the Daemons.
CSCsd21327
CMF database does not run and displays the following Sybase Assertion error message:
*** ERROR *** Assertion failed: 100909 (9.0.0.1383).100909 is the Assertion ID.
The following are the scenarios where Assertion Error might appear:
1.
This is because some of the database pages that have been modified will be in the database server cache, so the database file will be in an inconsistent state.
2.
This is because Adaptive Server Anywhere performs many reads and writes other than the normal I/O operations, which contribute to the good performance of Adaptive Server Anywhere.
However, anti-virus software might detect this as a potential problem and quarantine the file. This becomes hazardous if the .log or temporary files are quarantined, and it may cause corruption by interfering with the normal functions of the database.
Poor performance can also occur if the anti-virus software is checking all I/O operations performed by the database server.
Workaround:
We recommend that you do not use third-party backup software for backing up a running database.
We also recommend that you configure your anti-virus software so that it must not scan the NMSROOT/databases directory.
NMSROOT is the directory where you have installed CiscoWorks.
CSCsd79317
PSU screens in the Summary window allow you to edit values while installing device packages.
The Summary window allows you to right-click and select the window contents for cut, paste, and delete operations after you select the products for which you want to check for device updates.
Workaround:
Use Mozilla or Netscape family of browser.
Internally-Found Resolved Problems
Table 11 lists the problems that were found internally and have been resolved since the last release of Common Services.
Customer-Found Resolved Problems
Table 12 lists the customer-found problems that have been fixed since the last release of Common Services.
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Open Source License Acknowledgements
The following acknowledgements pertain to this software license.
OpenSSL/Open SSL Project
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
License Issues
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
OpenSSL License:
© 1998-1999 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
4.
5.
6.
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License:
© 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".
The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.
4.
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].
This document is to be used in conjunction with the documents listed in the Product Documentation section.
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0705R)
Release Notes for CiscoWorks Common Services 3.1 on Solaris
Copyright © 2007, Cisco Systems, Inc.
All rights reserved
Guest
