Table Of Contents
Release Notes for Network Connectivity Monitor 1.1
NCM Documentation
Additional Information Online
Network Connectivity Monitor Overview
NCM Components
New Features
New Features for All NCM Products
New Features for CNCC NCM Service Assurance Management Products
New Features for CNCC NCM IP Availability Management Products
Products and Document Titles
NCM Migration
Documentation Errata
Platform Support
Correction for Location of HTML Documents
Another Reason for "Qualified Access Address Not Found"
Correction for Modifying mail-custom.asl
Known and Resolved Problems
Obtaining Documentation
Cisco.com
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco Technical Support Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Network Connectivity Monitor 1.1
These release notes are for use with Cisco Network Connectivity Center (CNCC) Network Connectivity Monitor (NCM) running on a Solaris or Windows platform. Supported platforms are:
•
Windows 2000 Server and Advanced Server, Service Pack 4 (SP4) or later
•Windows 2003
•Windows XP (console only)
•Solaris 8 and 9 on SPARC
These release notes provide:
•NCM Documentation
•Additional Information Online
•Network Connectivity Monitor Overview
•NCM Migration
•Documentation Errata
•Known and Resolved Problems
•Obtaining Documentation
•Documentation Feedback
•Obtaining Technical Assistance
•Obtaining Additional Publications and Information
NCM Documentation
Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.
Table 1 describes the product documentation that is available.
Additional Information Online
You can download device packages for new devices from Cisco.com and find information about all supported devices by logging into Cisco.com at http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-ncm.
Device packages are released cumulatively; that is, new device packages contain the contents of any previous packages.
You can also obtain any published patches from the download site.
Network Connectivity Monitor Overview
See the following sections for information about NCM:
•NCM Components
•New Features
NCM Components
NCM consists of:
•CNCC NCM Service Assurance Management Suite—A full-featured, open solution for managing multiple network infrastructure domains that support services and your business. It consists of these components:
–CNCC NCM SAM Global Manager—A component that serves as a central point for monitoring and managing your entire technology infrastructure by obtaining data from multiple distributed domains. The SAM Global Manager consolidates the information from underlying sources and displays notifications in its client applications, CNCC NCM Global Consoles.
–NCM Broker—A component that facilitates communication between the SAM Global Manager and the underlying domains such as CNCC NCM IP Availability Manager and CNCC NCM SAM Adapter Platform server.
–CNCC NCM Global Console—The graphical interface for all NCM products. The console enables operators to monitor the state of the managed environment and quickly respond to notifications. Administrators with appropriate privileges and access control can use the CNCC NCM Global Console to discover NCM topology and administer underlying domains, as well as administer NCM users, user profiles, program tools, and escalation policies. The CNCC NCM Global Console is typically installed on many hosts.
–CNCC NCM SAM Adapter Platform Server—A component that imports traps from elements in the network infrastructure, processes the traps, and transfers the information to the SAM Global Manager.
–CNCC NCM SNMP Trap Adapter—A component that collects and parses SNMP traps.
•CNCC NCM IP Availability Management Suite—A solution that automates real-time root cause analysis of network faults and provides extensive impact analysis. It consists of these components:
–CNCC NCM IP Availability Manager (AM)—A component that diagnoses connectivity failures, including analysis of root causes, in IP networks.
–CNCC NCM Adapter for CiscoWorks LAN Management Solution and IP Telephony Environment Monitor (LMS/ITEM Adapter)—A component that imports topology from LMS and ITEM to the CNCC NCM IP Availability Manager.
–CNCC NCM Adapter for IBM/Tivoli NetView—A component that imports topology and traps from IBM/Tivoli NetView to the CNCC NCM IP Availability Manager.
New Features
This section contains information about the new features offered in NCM 1.1.
New Features for All NCM Products
The following are new features in CNCC NCM IP Availability Manager and CNCC NCM Service Assurance Manager:
•Integration with Cisco Network Connectivity Center products—Cisco Network Connectivity Center (CNCC) is a suite of products that complement NCM installations, providing multiservice solutions.
•New Operating System Support—NCM products are now supported on Windows 2003.
•Command Line Interface (CLI) and Unattended Installation Modes—In addition to the InstallShield Wizard (GUI interface) mode, two new modes of installation are available. The CLI mode is especially useful for UNIX users because it does not require X Display, fixed ports to permit communication through firewalls, or special access to production systems. The Unattended Installation mode reads the selections and settings for the installation from a user-modifiable file, which enables users to easily duplicate the installation on many machines. This mode also does not require the X protocol for UNIX users.
•InCharge Common Information Model (ICIM) 1.3—Updated to include new protocol classes such as those that support Hot Standby Routing Protocol (HSRP).
•Upgraded License Support—NCM applications now use the 9.2 Flexlm license server.
New Features for CNCC NCM Service Assurance Management Products
The following are new features and enhancements for CNCC NCM Service Assurance Manager, the Global Console, and the Web Console.
Global Console Enhancements
•Enhancements to Web Console—The contents of the Global Console can also be displayed as a Java applet within a web browser. An improved implementation now allows the Java applet to run inside a web browser.
•Enhancements and Customizations to Map Console—The ability to customize map backgrounds has been enhanced. Also, SAM users have the option to use custom map icons instead of the new default three-dimensional map icons that are included with NCM 1.1. NCM 1.1 also includes new severity icons.
•New Context Sharing of Console Views and Viewlets—Views in the Global Console can now participate in context sharing. This capability means that views or viewlets broadcast context information to other, listener views or viewlets. For example, if a Notification Log is set up to listen to instance context, selecting an instance in a Map will result in the Notification Log displaying information related to that instance.
•Enhancements to the Summary View—This console can now display three-dimensional pie charts as well as bar graphs, and is easier to configure.
•New Status Table View - This new view presents the overall status of a set of instances that affect the collection or group of other instances. For example, a Business Impact Manager user can view a Status table to determine the overall condition of customers based on the status of their respective services. The Status table shows information in a grid format, with Y and X axis, and uses the new severity icons.
Configuration Enhancements
Access Control of Console Operations—SAM Administrators can now restrict access to certain SAM console operations by controlling access as part of a user profile. To facilitate the configuration, the SAM Administration console also provides three predefined categories: Read-Only, Operator, and Administrator.
New Features for CNCC NCM IP Availability Management Products
The following are new features in CNCC NCM IP Availability Management products:
•Support for SNMP V3—In addition to supporting SNMP V1 and V2C, IP products can now discover and manage devices running SNMP V3 management agents. The seed file format and Add Agent function have also been extended to support SNMP V3, including the encryption of authentication passwords.
•Support for Cisco Hot Standby Routing Protocol (HSRP)—Availability Manager can now discover and monitor Cisco routers in HSRP configurations. The NCM analysis indicates the availability of the HSRP routers in normal, switchover, and failure scenarios. NCM also processes HSRP state change traps.
•Support for Point-to-Multipoint Frame Relay—Availability Manager can now discover multipoint Frame Relay virtual circuit connections. NCM accomplishes this by probing the CISCO-FRAME-RELAY-MIB and instrumenting connected Data Link Connection Identifier (DLCI) interfaces as subinterfaces.
•Support for Virtual Routers—Availability Manager can now discover and monitor virtual routers as implemented by Cosine and Juniper products.
•Initiated Volume Licensing—In addition to licensing NCM applications and features, Cisco is now implementing volume licensing for discovered systems (devices). Volume licensing applies to deployments of Availability Manager.
•Improved, Customizable Determination of Duplex Mode—IP Performance Manager provides a more flexible method for determining and adjusting the duplex mode of a network adapter (port or interface). The duplex mode is used to calculate the current utilization of an adapter and to monitor the adapter's HighUtilization faults.
•Additional Device Support—This release of NCM includes new support for additional devices. For a complete list of supported devices, see Supported Devices in Network Connectivity Monitor 1.1.
Products and Document Titles
NCM is part of the CNCC product offering. The Cisco Network Connectivity Monitor Roadmap document and other NCM documents contain references to InCharge software and InCharge documentation that may not be offered through Cisco Systems.
NCM Migration
If you are upgrading to NCM 1.1 from NCM 1.0 or a previous InCharge release, please contact Cisco Technical Assistance Center (TAC) for instructions.
Documentation Errata
The following sections describe documentation errata for NCM 1.1.
Platform Support
Some NCM 1.1 documents erroneously state that NCM products are supported on Linux, HP-UX, and AIX platforms. The supported platforms for this release of NCM products are:
•Windows 2000 Server and Advanced Server, SP4 or later
•Windows 2003
•Windows XP (console only)
•Solaris 8 and 9 on SPARC
Correction for Location of HTML Documents
HTML documents are not accessible from the CD-ROM, but they are installed on the host machine and are available from the BASEDIR/smarts/doc/html directory. The Network Connectivity Monitor Documentation Roadmap erroneously states that the HTML documents can be accessed from the CD-ROM.
Another Reason for "Qualified Access Address Not Found"
The DiscoveryError, Qualified access address not found, may occur during the rediscovery of a system for any of the following reasons:
•The IP address of the system's SNMP agent is null (missing).
•The IP address of the system's SNMP agent is unmanaged.
•The IP address of the system's SNMP agent is unmanaged because the interface that the address is layered over is in either OnDemand or Backup mode.
•The IP address of the system's SNMP agent is excluded because it is within the range of the ipExcludeList parameter in the discovery.conf file.
•The AccessAddressFormat parameter in the discovery.conf file is set to LOOPBACKADDRESS and no LoopBack Interface is configured on the system.
The Network Connectivity Monitor IP Discovery Guide lists all but the last reason for this DiscoveryError. The last reason needs to be added to the Network Connectivity Monitor IP Discovery Guide.
Correction for Modifying mail-custom.asl
Page 42 of the Network Connectivity Monitor Service Assurance Manager Notification Adapters User's Guide incorrectly states that you should use the following to invoke the use of the mail-custom.asl in Step 2:
(currentEvent->icType == "CLEAR"
|| currentEvent->icType == "NL_CLEAR")
do { currentEvent->filterMe = TRUE; }
do { currentEvent->sentByCustom = TRUE; }
The correct code after the START statement should be:
if (currentEvent->icType == "CLEAR"
|| currentEvent->icType == "NL_CLEAR")
{ currentEvent->filterMe = TRUE;
currentEvent->sentByCustom = TRUE;
Known and Resolved Problems
Table 2 describes problems in NCM 1.1. Table 3 describes problems specific to Availability Manager. Table 4 describes problems specific to Service Assurance Manager. Table 5 describes problems resolved in NCM 1.1.
Note To obtain more information about known problems, access the Cisco Software Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. (You will be prompted to log into Cisco.com.)
Table 2 Known Problems in CNCC NCM 1.1
Bug ID
|
Summary
|
Explanation
|
CSCsa33585
|
NCM 1.1: DFM and NCM integration not working
|
NCM 1.1 only supports the integration of either one LMS application or one ITEM application. It does not support the integration of multiple LMS or multiple ITEM servers or any combination of LMS and ITEM servers. In addition, NCM 1.1 does not support the ITEM Notification MIB.
|
CSCsa33300
|
NCM 1.1: Only installed components should be started and shown
|
NCM is a part of the Cisco Network Connectivity Center (CNCC) suite. Certain CNCC products are included as installation options on the NCM CD-ROMs, but these products are not part of the NCM offering and should not be installed from the NCM CD-ROM. BASEDIR/smarts/setup/info contains a list of all installed products and packages and should be used to verify the correctness of the installation. See Network Connectivity Monitor Service Assurance Management Suite Installation Guide and Network Connectivity Monitor IP Availability Management Suite Installation Guide for the list of the actual components.
|
CSCsa33304
|
NCM 1.1: Java exception while attaching to manager
|
If the Topobuilder console is used to attach to the underlying domain manager, a Java exception occurs, because the Topobuilder console does not support domain managers and can be attached only to the Global Manager. The Topobuilder console throws an exception instead of displaying an error message.
|
CSCsa33822
|
NCM 1.1: Solaris host is discovered as a switch
|
If, during discovery, some network devices are misconfigured and contain DNS-resolvable IP addresses belonging to other devices, these DNS names can be used to name the devices being discovered.
To work around the problem, eliminate the misconfiguration and rediscover the devices.
|
CSCsa33937
|
NCM 1.1: Not all VLANs discovered for a switch under Availability Manager
|
If, during discovery, the CISCO-VLAN-MEMBERSHIP MIB does not provide membership information for some VLANS, these VLANS are not discovered by NCM.
|
CSCef68436
|
Unable to show autodiscovery-related tabs error while ITEM reboots
|
If the DFM or VHM servers are down, when you attempt to display topology-related tabs in the domain console, an error message pops up, stating that the domain managers are disconnected.
To work around this problem, when the error message is displayed, verify that the DFM or VHM server is up, and restart the operation if necessary.
|
CSCef68457
|
NCM 1.1: Find Instance does not work for VHM under NCM
|
If the Domain Administration Console is attached to the DFM or VHM domain managers, certain functions, such as Find Instance or Find System, are not supported because of version incompatibility.
To work around the problem, use the Global Console attached to the Service Assurance Manager.
|
CSCsa36538
Solaris
|
Installing the Global Console may produce error message in installation log (Solaris 8 and 9)
|
When installing the Global Console on Solaris 8 or 9, the Global Console installation performs an action to install a desktop icon to the window manager. If no valid window manager (such as CDE) is installed on the machine, the following error message may appear in the installation log:
com.installshield.product.actions.DesktopIcon, err,
java.lang.UnsatisfiedLinkError: getenv STACK_TRACE:
33
The problem is benign; if the user does not have a valid window manager installed, there is no need for a desktop icon.
To work around the problem, run the installation with the following flag:
# setup-solaris.bin -P bean20.active=false
This flag disables the action to install a desktop icon to the window manager.
|
CSCsa36258
|
Full uninstallation does not stop sm_serviced and does not remove services from registry
|
If the user does not stop all NCM processes (except sm_serviced, which is required for uninstalling) before uninstalling a product suite, the uninstallation program cannot remove the files in use.
To work around the problem, stop all processes (except sm_serviced) before uninstalling a product suite. Or, after exiting the uninstallation program, remove all directories from the BASEDIR/smarts directory, except BASEDIR/smarts/local and BASEDIR/smarts/setup.
|
CSCsa36543
|
CLI Mode Sensitivity to a Terminal Window's Configuration
|
The Command Line Interface (CLI) mode of installation is sensitive to the terminal window's configuration. Depending on how the user's stty settings are configured for the terminal window, the installation program may interrupt or generate I/O errors if a special key (for example, Backspace or Delete) is pressed during the installation.
To work around the problem, do one of the following:
•Change the stty settings to a more traditional configuration and restart the installation.
•Restart the installation and do not press any special keys during the installation.
|
CSCsa36259
Solaris
|
Non-root installation generates warning message related to log service
|
When installing software with nonroot privileges (Global Console) on the UNIX operating system, or installing NCM using the Command Line Interface (CLI) mode of installation, the user sees messages concerning the inability to write to the /var/logs directory.
To work around the problem, install the software with root privileges or ask the system administrator to perform the installation.
|
CSCsa36545
|
NCM sets new SM_BROKER_DEFAULT variable
|
In NCM 1.0, the installation program set the variable SM_BROKER in the BASEDIR/smarts/local/conf/runcmd_env.sh. Thus, a user could not override the SM_BROKER value for a CNCC NCM product suite by presetting the SM_BROKER environment variable. For example:
SM_BROKER=localhost:427 ./sm_server [args]
The installation program sets the variable SM_BROKER_DEFAULT in the BASEDIR/smarts/local/conf/runcmd_env.sh. Thus, a user can override the SM_BROKER value for a product suite by presetting the SM_BROKER environment variable.
Because the installation program does not overwrite existing configuration files such as runcmd_env.sh file when performing an installation upgrade, you must edit the runcmd_env.sh file and change the variable SM_BROKER to SM_BROKER_DEFAULT after the installation upgrade completes.
|
CSCsa36546
Solaris
|
Using sm_logerror process to avoid stack trace printing problem
|
Every running program is accompanied by a child process running a program named sm_logerror. This process does nothing, except when asked to print a stack trace, at which time it prints the stack trace of its parent process; it exits automatically when its parent exits.
Use the sm_logerror process to avoid the stack trace printing problem for applications running on Solaris operating systems.
|
CSCsa36548
Windows
|
Recovery options prohibited for failover
|
For the Windows 2000 platform (Server or Advanced Server), users should not set recovery options for any NCM services. Recovery options are set in the Recovery Tab under Administrative Tools > Services. The options, First Failure, Second Failure, and Subsequent Failure, must not be changed. NCM services must use the default setting, Take No Action, for all these options.
|
|
CSCsa36550
Windows
|
Running multiple brokers or domain managers possible on the same port
|
On the Windows 2000 platform (Server or Advanced Server), starting several NCM Brokers or domain managers that listen on the same port is possible due to an incompatibility between the UNIX and Windows 2000 implementations of the Internet Protocol stacks. Running more than one copy of the Broker or the domain manager may cause unpredictable results.
To work around the problem, terminate all NCM Broker and domain manager processes that are listening on the same port and start only one NCM process listening on that port.
|
CSCsa36551
Windows
|
Directory names should not contain spaces
|
On the Windows 2000 platform (Server or Advanced Server) and the Windows 2003 platform, NCM does not install properly, or services do not start up properly.
To work around the problem, do not use spaces for the directory names in BASEDIR (for example, Program Files). Do not install NCM in directories that have names containing spaces.
|
CSCea25232
Windows
|
sm_server.exe pops up every time computer reboots
|
Every time the NCM Global Manager on Windows starts (either upon rebooting or restarting the Global Manager), a DOS command window pops up on the screen if Administrator is logged in.
This window should be minimized. Closing this window will not stop the Global Manager; however, server side tools (such as Ping or Ping-All) will not run, because they require service-interactive access, which this window provides.
|
CSCsa28101
|
Host is not a good name for ClassName of SNMP trap
|
When DFM pass-through traps are displayed in the NCM Notification Log Console, they will be classified as hosts. To obtain the actual class name of the device that generated the SNMP trap, see the ElementClass field of the notification. See the Class and Element Class fields in the following example.
********* snmp link down trap event *********
First Notify: Mon Feb 24 17:13:24 PST 2003
Last Notify: Mon Feb 24 17:13:24 PST 2003
Last Clear: Wed Dec 31 16:00:00 PST 1969
Last Change: Mon Feb 24 17:13:24 PST 2003
Event Text: Varbinds: 107 FastEthernet5/45 6
Keepalive failed
|
CSCea62447
|
Domain consolidation does not represent same class as domain managers
|
NCM domain consolidation classes represent a top-level abstraction of all underlying domain managers. For example, a CallManager class in VHM may be abstracted as a Host or CallManager class in NCM.
|
Table 3 Known Problems in CNCC NCM IP Availability Management Suite
Bug ID
|
Summary
|
Explanation
|
All CNCC NCM IP Availability Management Suite products
|
CSCsa36552
|
Illegal device names
|
During the discovery process, NCM discovers a network element that has the same name as an InCharge Common Information Model (ICIM) class name. Because NCM considers such a name to be invalid, NCM writes a warning to the log file and does not add the device to the topology.
Log files are found in the BASEDIR/logs directory. All log files have a ".log" file type. The name of a domain manager's log file is based on the domain manager's name. In typical installations, the log file is named INCHARGE.log.
The warning message for an invalid name reads:
<Device IP Address> is resolved to <INCHARGE Class Name> which is a class name in INCHARGE.
In this warning, <Device IP Address> represents the address of the device, and <InCharge Class Name> represents the exact class name.
For example, if you have a device named Switch at IP address 123.12.123.123, the warning will read:
123.12.123.123 is resolved to Switch which is a class name
in INCHARGE.
If this warning appears in your log file, you should rename the device before attempting another discovery.
|
CSCsa36252
|
Error message displayed while setting full discovery below 60 minutes via topology tab
|
In the Topology tab of the Domain Manager Administration Console, if the user selects Enable Full Discovery and sets an interval time below 60 minutes, an error message is displayed:
Apply changes failed: CI-E-ICF-TopologyManager:
reprobePeriod:constraint MinimumProbePeriod MR-Violation of
hard constraint
To work around the problem, enable Full Discovery by setting an interval time greater than 60 minutes.
|
CNCC NCM IP Availability Manager
|
CSCea62396
|
Diagnosis of Card Down problems on Cisco LS1010 switches
|
To diagnose a Card Down problem, the NCM domain manager needs to query the MIB variable ciscoLS1010ModuleOperStatus. However, this MIB variable is often not implemented on LS1010 switches. As a result, diagnosis of Card Down problems is disabled.
If the MIB variable ciscoLS1010ModuleOperStatus is available in the SNMP agent, contact Cisco TAC for assistance.
|
CSCea62402
|
Card Status not updated when card is reinserted
|
After discovering a switch, the NCM domain manager uses the ModuleInsertion trap to monitor the status of cards within the switch. When NCM receives a ModuleDown trap, it marks the card as OperationallyDown. When NCM receives a ModuleUp trap, it adds the switch to the Pending Devices List so that the switch is rediscovered and the status of the card is updated. Upon reinsertion of the card, the status may not be updated.
NCM domain manager currently supports the ModuleInsertion trap for Cisco switches. If you have a switch where the status of a card in not updated when it is reinserted, contact Cisco TAC. Cisco routinely adds support for new devices through Incremental Device Update (IDU) releases.
|
CSCsa36553
|
Connections between Foundry and Cisco switches not discovered
|
Availability Manager does not discover all connections (trunk cables) between Foundry switches and Cisco switches due to a known bug in the Foundry agent implementation. The bug causes incorrect Spanning Tree Protocol (STP) information which, in turn, causes Availability Manager to make connections to the wrong ports. Because of the known bug, Availability Manager no longer uses the incorrect STP information, which is why connections might be missing from the topology.
To work around the problem, do the following:
1. Update all Foundry switches to use MIB version 7.6. (The known bug is fixed in the 7.6 version of the Foundry MIB.)
2. Enter the following command (all on one line) to enable Availability Manager to use STP information to make connections between Foundry and Cisco switches:
dmctl -s <domain_manager_name> invoke
ICF_TopologyManager::ICF-TopologyManager insertParameter
STPTRUNK_EnableFoundryCisco TRUE
Note Step 1 is required; otherwise, the command in Step 2 will create connections to the wrong ports. The command in Step 2 remains in effect even if the domain manager is stopped and restarted.
To disable the use of STP information to make connections, use the above command and specify FALSE instead of TRUE.
For additional configuration information about connections between Foundry and Cisco switches, contact Cisco TAC.
|
CSCsa36576
|
Discovery pending interval too short
|
When the discovery pending interval is shorter than five minutes or the full discovery interval is less than one hour, the following exception is thrown from the Domain Manager Administration Console:
Apply changes failed: CI-E-ICF-TopologyManager:
reprobePending_period: constraint MinimumProbePeriod
MR-Violation of hard constraint
The discovery pending interval cannot be less than five minutes. The full discovery interval cannot be less than one hour.
|
Device Support
|
CSCsa36577
|
Cisco 2948G and 4232 L3 module conflict
|
Cisco 2948G and 4232 L3 modules share the same sysObjectID (that is, .1.3.6.1.4.1.9.1.275). Since NCM uses the sysObjectID to identify the device type, Availability Manager, by default, classifies both devices as switches.
Even though the 4232 L3 module is classified as a switch, it has all of the router properties (for example, interfaces, IP endpoints, memory, processors, and so on) as defined by Availability Manager, and is monitored as a router.
For some customers, the device type is critical for creating trouble tickets.
To work around the problem, if the device type is critical, you can classify the 4232 L3 module as a router. To do so, modify the field certification file, if it exists, for this unique situation.
The oid2type_Field.conf file, located in the BASEDIR/smarts/conf/discovery directory, contains field certification information. Under normal circumstances, Cisco recommends editing the file to include only non-network devices such as personal computers or printers. This modification is an exception.
If the oid2type_Field.conf file does not exist, use the oid2type_Field.conf.template to create it. For instructions about using the template, see Network Connectivity Monitor IP Discovery Guide.
If only the 4232 L3 module is deployed in the network, to classify the module as a router, add the following device entry to the oid2type_Field.conf file:
# CAT4232-IN-M L3 (Switch/Router)
CERTIFICATION = CERTIFIED
|
CNCC NCM IP Adapters
|
CSCsa36555
Windows
|
Adapters fail to create log files
|
For Windows 2000, the adapters OpenView/NetView Initial Topology Reader, OpenView/NetView Topology Update Reader, and OpenView/NetView Forwarder will not create a log file.
There is no workaround for this problem.
|
CSCsa36556
|
Adapters do not support SNMP V3
|
NCM can use the CNCC NCM Adapter for HP OpenView NNM or CNCC NCM Adapter for IBM/Tivoli NetView to import a list of candidate discovery systems having SNMP V1 or V2C agents but not SNMP V3 agents.
To work around the problem, import candidate discovery systems having SNMP V3 agents, list those systems in a seed file, and use manual discovery to add them to the NCM topology.
|
CSCsa36246
Windows
|
HP OpenView pathname not converted properly during installation
|
When HP OpenView 6.2 is installed on Windows, the pathname may contain spaces that are not converted properly in the OV_TOPO.import file. By default, HP OpenView 6.2 installs itself in Program Files/HP OpenView.
To work around the problem, perform the following steps:
1. Modify the OV_TOPO.import file.
2. Register CNCC NCM with HP OpenView.
To modify the OV_TOPO.import file, you must modify the BASEDIR\smarts\conf\OV\OV_TOPO.import file to state the correct path to the OpenView ovtopodump executable.
In the GA_Driver section of OV_TOPO.import, the command string setting should be changed from:
ReadsInputFrom = GA_ProgramFE::OpenView-Topology-FE
commandString = "/opt/OV/bin/ovtopodump -rl"
to:
"C:\Program Files\HP OpenView\opt\OV\bin\ovtopodump -rl"
Next, the registration files must be registered with OpenView. Use the following command (all on one line):
C:\"Program Files\HP OpenView"\NNM\bin\ovaddobj.exe
C:\InCharge\smarts\conf\OV\sm_ovtopo.lrf
Repeat for each file: sm_ovevent.lrf, sm_ovfwd.lrf, sm_ovlog.lrf, and sm_ovtopo.lrf.
Alternatively, change directory to OpenView and issue the following command (all on one line):
cd C:\"Program Files\HP OpenView"\NNM
bin\ovaddobj C:\InCharge\smarts\conf\OV\sm_ovevent.lrf
bin\ovaddobj C:\InCharge\smarts\conf\OV\sm_ovfwd.lrf
bin\ovaddobj C:\InCharge\smarts\conf\OV\sm_ovlog.lrf
bin\ovaddobj C:\InCharge\smarts\conf\OV\sm_ovtopo.lrf
|
Table 4 Known Problems in CNCC NCM Service Assurance Management Suite
Bug ID
|
Summary
|
Explanation
|
Global Console
|
CSCsa36557
|
Deleting SelectiveGroup from topology builder may cause error
|
Errors may occur if a SelectiveGroup is deleted from the Topology Builder in the Global Console.
The Topology Builder allows the deletion of a SelectiveGroup instance. However, if you delete a SelectiveGroup using the Topology Builder, you cannot create a SelectiveGroup with the same name.
To work around the problem, do not delete SelectiveGroups from the Topology Builder. Instead, in the Global Console, select Configure > Groups. In the Group Definition Window, delete the SelectiveGroup.
|
CSCsa36260
|
Trying to add view may cause null pointer exception
|
Access to views is controlled using the Global Manager Administration Console, by configuring user profiles and associating console operations. If a user tries to access a view to which the user does not have access, the console may generate a Null Pointer Exception.
In most cases, the Add View dialog box will only list the views to which the user has access. However, it is possible that the dialog box may incorrectly list views to which the user does not have access. If this happens, and the user tries to add an incorrect view, an error message will be written to the console. The error message indicates a Java Null Pointer Exception.
There is no workaround for this problem. The user can continue to use the Global Console after this error occurs.
|
CSCsa36261
|
Cannot attach to multiple domain managers at console startup
|
At console startup, putting a space in the list of CNCC NCM domain managers to which you want to attach results in all subsequent managers in the list not being attached. In the following example
sm_gui -D com.smarts.autoAttachDM="foo,bar, car"
car will not be attached.
To work around the problem, do not put spaces after the commas when specifying a list of domain managers (in a command line, in a properties file, or in an HTML file) to which you want to auto-connect.
|
CSCsa36558
|
IP network map node is always green
|
In a map, the node for an IP network is always green, even if the network is inaccessible.
There is no workaround for this problem.
|
CSCsa36253
|
Expanded topology tree not properly displayed
|
On UNIX, if the NCM topology is expanded such that more than approximately 2200 nodes are visible in the tree, the tree's background turns gray, and the tree is not repainted properly.
To work around the problem, close some class nodes in the tree so that fewer than 2200 nodes are visible.
|
CSCsa36559
|
Global Console windows displayed through Exceed appear minimized
|
When the Global Console is run from a UNIX platform and displayed through Exceed on a Windows desktop, the windows (popup window, dialog box, and so on) in the console may not be sized correctly. The windows may display in a minimized state.
To work around the problem, you should install the Global Console on the Windows desktop. Alternatively, you can run Exceed on UNIX in single-window mode with the XDMCP-query communication option.
|
CSCsa36560
|
Opening and closing console displayed through Exceed causes console to fail
|
When the Global Console is run from a UNIX platform and displayed through Exceed in multiwindow mode on a Windows desktop, opening a console with the sm_gui command and closing it repeatedly causes the console to fail and to print a stack trace.
To work around the problem, install the Global Console on the Windows desktop. Alternatively, you can run Exceed on UNIX in single-window mode with the XDMCP-query communication option.
|
Web Console
|
CSCsa36561
|
Java Plug-in version required for Web Console
|
Unless a version of the Java Plug-in 1.4 software is already installed on client machines, end users of the NCM Web Console will be prompted to install the latest revision of the Java Plug-in 1.4 software. Java Plug-in 1.4 software is required for the Web Console.
To work around the problem, if you are prompted to install the Java Plug-in software, visit the appropriate Sun web site and download and install the latest revision of the Java Plug-in 1.4 software.
Note Be aware that Java Plug-in versions earlier than 1.4.1_04 contain a security vulnerability. For details, see http://sunsolve.sun.com/search/document.do?assetkey=1-26-57221-1. (This website is Copyright 2000-2003 Sun Microsystems, Inc.)
|
CSCsa36265
|
Prompted to download JRE when starting the Web Console
|
Upon attempting to start the NCM Web Console with Java Web Start, a user is prompted to download the Java Runtime Environment (JRE), even though the JRE is already installed on the client machine.
To work around the problem, instead of pointing your browser to
http://<Tomcat_host>:8080/webconsole/globalConsoleCached.html
to start the Web Console, point your browser to
http://<Tomcat_host>:8080/webconsole/globalConsoleApp.jnlp
where <Tomcat_host> refers to the name of the machine where the Jakarta Tomcat Servlet Engine is installed, and 8080 refers to the default port for Tomcat.
The latter URL bypasses the JRE version-checking mechanism.
|
CSCsa36563
|
Web Console or Viewlets may run out of memory
|
Depending on the heap space (heap size) configured for the web browser in which the NCM Web Console runs, the Web Console may run out of memory.
By default, the Web Console and viewlets allocate less heap space than the Global Console. Less heap space may lead to out-of-memory errors in the Web Console or viewlets in deployments that heavily use large map background images.
To work around the problem, if the Web Console or viewlets run out of memory, adjust the maximum amount of heap space that the Java Plug-in uses for dynamic memory allocation. By specifying -Xmx256M as a runtime parameter, for example, you can increase the heap space allocation to 256 MB. The number can be set larger or smaller than 256 MB, depending on the resources available on the client machine running the web browser.
To increase the heap space for the Java Plug-in, perform the following steps:
1. Choose Start > Settings > Control Panel to launch the Control Panel.
2. In the Control Panel, double-click the Java Plug-in icon to launch the Java Plug-in Control Panel.
3. In the Java Plug-in Control Panel, click the Advanced tab.
4. In the Advanced tab page, below the Java Runtime Parameters line, enter the maximum heap-space runtime parameter (-Xmx) and a value for the parameter. For example:
5. Save your entry and close the Java Plug-in Control Panel.
6. Terminate and restart any web browser running on the host machine.
|
CSCsa36262
|
Summary view cannot be reactivated or deleted
|
The Global Console or Web Console is connected to multiple CNCC NCM domain managers, and the Notification Log is configured to listen to Summary context. Clicking the default summaries in the Summary View Console causes the Notification Log to respond accordingly. However, if a domain manager disconnects, the corresponding summary terminates but does not dim (gray out) to indicate that the summary is unavailable. Also, when the Global Console or Web Console reattaches to the previously disconnected domain manager, the corresponding summary does not reactivate and cannot be deleted.
To work around the problem, add a new summary to the Summary View Console or open a new Summary View Console.
|
CSCsa36263
|
Summary should show the default notifications when it no longer listening to context
|
The Summary View Console is configured to listen to Collection Entity context, and the summaries in the console respond accordingly to a selection of a collection entity in the Status Table. However, upon configuring the console to stop listening to Collection Entity context, the summaries in the console stop listening to the context but continue to show the notifications belonging to the collection entity. Ideally, the summaries should display the default notifications that they were displaying prior to listening to Collection Entity context.
To work around the problem, before configuring the Summary View Console to stop listening to Collection Entity context, manually open the Filter dialog box and remove the topological filter defined by the last collection entity. Then, configure the Summary View Console to stop listening to Collection Entity context, at which time the summaries in the console will stop listening to the context and display the default notifications that they were displaying prior to listening to the context.
|
sm_ems Issues
|
CSCsa36250
|
sm_ems does not prompt for authentication credentials
|
By default, the sm_ems command line interface does not prompt for authentication credentials.
To work around the problem, if you are working in a secure environment, you need to create an entry in the clientConnect.conf (using the sm_edit utility) that provides the necessary username and password for the sm_ems interface. The username in this entry must match a username in the corresponding serverConnect.conf. You must edit the clientConnect.conf file on the host where sm_ems is running.
|
CNCC NCM SAM Adapters
|
CSCsa36248
CSCsa36249
|
Minimum certainty and smoothing interval do not work for notification lists
|
Values specified for the MinimumCertainty and eventSmoothingInterval parameters in the configuration file of E-Mail Notifier, File Notifier, SNMP Trap Notifier, Script Notifier, and TIBCO Rendezvous Notifier are ignored.
In the configuration file of the affected adapters, the MinimumCertainty and eventSmoothingInterval parameters are not supported.
You can define a notification list using either the sm_gui command or the Global Manager Administration Console, and then apply the list to the adapter. You cannot define a smoothing interval using the adapter's configuration file.
For minimum certainty, you can specify a notification list filter that matches the Certainty field against a numeric value.
For example,
match("Certainty", "<30->")
results in a minimum certainty of 30%.
The name of the notification list specified in the adapter's configuration file must match an existing notification list created using either the sm_gui command or the Global Manager Administration Console.
|
Table 5 Resolved Problems in NCM 1.1
Bug ID
|
Summary
|
Explanation
|
CSCea30969
|
NCM install displays incorrect options
|
On Disk 2, the Product Selection menu displayed incorrect options, and the installation program displayed incorrect services to be installed.
This problem no longer occurs.
|
CSCea60435
|
Global console install instructions incorrect
|
The instructions for the global console only installation in the NCM installation guide and quick start guide stated that a prompt appears, asking you to install the NCM broker as a service. This prompt did not appear.
This has been fixed in the online versions of these documents.
|
CSCea61928
|
NCM processes not installed as services
|
By default, the NCM processes (ic-broker, ic-icoi-server, ic-sam-server, and ic-trapd-receiver) were not installed as services during the installation process.
This problem no longer occurs.
|
CSCea61964
|
Client connection times out after 60 seconds
|
When <PROMPT> was specified for the NCM username field of the clientConnect.conf file, a user had to type a username, and possibly a password, when invoking a client program. If the username and password (if required) were not entered within 60 seconds, the operation would timeout and report an I/O error. This timeout only affected clients started from the command line; it did not affect the Global Console.
This problem no longer occurs.
|
CSCea61967
|
Echo disabled if user exits unexpectedly
|
When the clientConnect.conf file was configured to prompt the user for a password, the terminal echo was disabled so that the typed password was not displayed. If the client program exited during the password prompt, the terminal's echo state was not reset.
This problem no longer occurs.
|
CSCea61977
|
MACs not removed when deleting device
|
During the Bridge probe of a switch, a MAC object was created for each valid MAC address in the bridge forwarding table. BridgedVia relationships to the Port object were also established. If the MAC address was found to belong to a system through the interface table or the ARP cache (for devices that do not support SNMP), the
Layer 2 connectivity was built between the system and the switch. The BridgedVia relationship between the port and the MAC was kept untouched during post processing so that NCM domain manager could build connectivity without rediscovery of the switch.
However, this practice prevented discovery from building more accurate Layer 2 topology because one of the conditions to build the cable between a port and an interface was that the port must correspond to only one MAC object. If a MAC object did not belong to any system, you had to empty its BridgedVia relationship.
This problem no longer occurs.
|
CSCea62410
|
Responsive device is reported as down
|
The NCM domain manager may have generated a Down notification for a device even if there was a responsive IP endpoint or agent.
This problem no longer occurs.
|
CSCea62413
|
Administratively disabled subinterfaces display Interface Down status
|
On some routers, when the physical interface was administratively disabled (AdminStatus DOWN), the subinterfaces did not assume that DOWN state. Instead, the subinterfaces retained their AdminStatus UP state, which resulted in an Interface Down notification in NCM domain manager.
Subinterfaces then assumed the same status as their associated interface. On routers, when the physical interface was administratively disabled (AdminStatus DOWN), the subinterfaces also assumed the DOWN state. As a result, an Interface Down notification was not generated, because NCM domain manager did not consider disabling an element via an explicit user request to be a reportable condition.
This problem no longer occurs.
|
CSCea62420
|
Subinterfaces do not correspond with physical Interface Down status
|
When the physical interface of a router was operationally down (AdminStatus UP and OperStatus DOWN), all of its subinterfaces became operationally down. As a result, the underlying NCM domain manager might have generated multiple Interface Down notifications for certain interface configurations.
This problem no longer occurs.
|
CSCea62703
|
Some notifier configuration parameters are ignored
|
Values specified for the MinimumCertainty and eventSmoothingInterval parameters in the configuration file of E-Mail Notifier, File Notifier, SNMP Trap Notifier, Script Notifier, and automated actions were ignored. Instead, you could specify a notification list filter in the ics.conf file.
This problem no longer occurs.
|
CSCea71513
|
NCM server exits when agent behaves erratically
|
The NCM server exited under certain conditions during which an SNMP agent responded with a valid SNMP response but with no data.
This problem no longer occurs.
|
CSCea61957
|
Need to modify default trap port 162 on NCM server
|
By default, NCM is configured to listen for traps forwarded from DFM on port 162. This well-known UDP port for SNMP traps may not always be available.
The port setting can be changed in the service. Or, a port can be specified in the trapd.conf file. The file is located in:
BASEDIR/smarts/local/conf/icoi/trapd.conf
The port setting in the service command line always overrides the setting in the configuration file.
See the Integration Guide for Network Connectivity Monitor for instructions on changing the port setting.
|
CSCea61960
|
NCM server should not be installable on Windows XP
|
NCM supports only the console on Windows XP. The installation process did not prevent the installation of other NCM components or applications even though they are unsupported.
This problem no longer occurs.
|
CSCea62390
|
Misconfigured DNS causes name resolution problems
|
The discovery of Windows-based devices may have used NetBIOS to resolve the IP addresses of these devices to names. When NCM domain manager resolved the NetBIOS name, it may have resolved to an IP address through which the SNMP agent was not reachable. As a result, if the device did not respond to SNMP requests, it was added to the Pending Devices List with the message No Response from SNMP Agents.
This problem no longer occurs.
|
CSCea62428
|
InstallShield Insufficient Memory error if > 2GB
|
For Windows only, NCM Disk 1 SETUP.EXE failed on systems with large amounts of extended memory (greater than 2 GB of RAM). The error code was 111, Insufficient memory available to run Setup, even though there was sufficient memory available.
This problem no longer occurs.
|
CSCea62454
|
Map Console not supported in NCM Console applet
|
The Map Console was not supported with the Java applet for any platform. It is now supported on the same platforms as the NCM Console.
|
CSCea62464
|
Client tool may not stop if ignoring SIGTERM
|
For client tools, when you pressed the Stop button in the Tool Output window, the client process may not have stopped. Processes (such as shell scripts) that did not respond to a SIGTERM signal would not stop.
This problem no longer occurs.
|
CSCea62470
|
Cannot launch NCM admin console from console applet
|
You could not launch the NCM Administration Console from the Global Console Java applet.
|
CSCea62485
|
Server tool does not work with X-Window
|
If you were running the Global Console as a Java applet, server tools that open an X Window on the client were not supported.
This problem no longer occurs.
|
CSCea62694
|
Recommending Windows Diagnostics tool
|
If you are running domain consolidation on Windows, we recommended that you use the Dr. Watson diagnostic tool as your debugger.
|
CSCea62700
|
Ping and Telnet tools have access constraints
|
The sample scripts for ping and Telnet server tools, located in your BASEDIR/smarts/local/actions/server directory, may not have worked properly in all cases.
They now work properly in all cases.
|
CSCea62715
|
Use sm_sched instead of cron or other scheduler
|
Users might have experienced some problems running processes or commands at regularly scheduled intervals in Windows (for example, jobs stopped running and scheduled jobs did not start).
This problem no longer occurs.
|
CSCea62719
|
Improving performance of a remote console over WAN link
|
If the NCM host machine was experiencing degraded performance due to memory swapping, you could improve performance by specifying the sm_gui command with the -H option:
|
CSCea62735
|
Default user profile is required for login
|
When logging in to NCM global console, if a username did not correspond to a user profile, NCM looked for a default user profile. If the default user profile did not exist, an error message was displayed.
The default profile should not be deleted.
|
CSCea62787
|
Global Console applet does not work on localhost
|
If you started the NCM Global Console applet, you could not log in to the Global Manager if:
•You used either localhost or the loopback IP address (127.0.0.1) for the server name
•The hostname did not resolve through DNS
This problem no longer occurs.
|
CSCea69415
|
Catalysts 4000 and 4507 should be categorized as switches, not routers
|
Catalysts 4000 and 4507 were categorized as routers with interfaces; however, they should have been reported as switches with ports.
They are now reported as switches with ports.
|
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
http://www.cisco.com
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:
http://www.cisco.com/en/US/partner/ordering/index.shtml
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
Documentation Feedback
You can send comments about technical documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.
Cisco Technical Support Website
The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool automatically provides recommended solutions. If your issue is not resolved using the recommended resources, your service request will be assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553 2447
For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:
http://www.cisco.com/go/marketplace/
•The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:
http://cisco.com/univercd/cc/td/doc/pcat/
•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:
http://www.ciscopress.com
•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:
http://www.cisco.com/packet
•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:
http://www.cisco.com/go/iqmagazine
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
http://www.cisco.com/ipj
•World-class networking training is available from Cisco. You can view current offerings at this URL:
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the "NCM Documentation" section.
Copyright © 2004, Cisco Systems, Inc.
All rights reserved.
Copyright ©1996-2004 by System Management ARTS Incorporated. All rights reserved.
The Software and all intellectual property rights related thereto constitute trade secrets and proprietary data of SMARTS and any third party from whom SMARTS has received marketing rights, and nothing herein shall be construed to convey any title or ownership rights to you. Your right to copy the software and this documentation is limited by law. Making unauthorized copies, adaptations, or compilation works is prohibited and constitutes a punishable violation of the law. Use of the software is governed by its accompanying license agreement. The documentation is provided "as is" without warranty of any kind. In no event shall System Management ARTS Incorporated ("SMARTS") be liable for any loss of profits, loss of business, loss of use of data, interruption of business, or for indirect, special, incidental, or consequential damages of any kind, arising from any error in this documentation.
The InCharge products mentioned in this document are covered by one or more of the following U.S. patents or pending patent applications: 5,528,516, 5,661,668, 6,249,755, 10,124,881 and 60,284,860.
"InCharge," the InCharge logo, "SMARTS," the SMARTS logo, "Graphical Visualization," "Authentic Problem," "Codebook Correlation Technology," "Instant Results Technology," "InCharge Viewlet," and "Dashboard Viewlet" are trademarks or registered trademarks of System Management ARTS Incorporated. All other brand or product names are trademarks or registered trademarks of their respective companies or organizations..
Third-Party Software. The Software may include software of third parties from whom SMARTS has received marketing rights and is subject to some or all of the following additional terms and conditions:
Bundled Software
Sun Microsystems, Inc., Java(TM) Interface Classes, Java API for XML Parsing, Version 1.1. "Java" and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. SMARTS is independent of Sun Microsystems, Inc.
W3C IPR Software
Copyright © 2001-2003 World Wide Web Consortium (http://www.w3.org), (Massachusetts Institute of Technology (http://www.lcs.mit.edu), Institut National de Recherche en Informatique et en Automatique (http://www.inria.fr), Keio University (http://www.keio.ac.jp)). All rights reserved (http://www.w3.org/Consortium/Legal/). Note: The original version of the W3C Software Copyright Notice and License can be found at http://www.w3.org/Consortium/Legal/copyright-software-19980720.
The Apache Software License, Version 1.1
Copyright ©1999-2003 The Apache Software Foundation. All rights reserved. Redistribution and use of Apache source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of Apache source code must retain the above copyright notice, this list of conditions and the Apache disclaimer as written below.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the Apache disclaimer as written below in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:
"This product includes software developed by the Apache Software Foundation (http://www.apache.org/)."
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.
4. The names "The Jakarta Project", "Tomcat", "Xalan", "Xerces", and "Apache Software Foundation" must not be used to endorse or promote products derived from Apache software without prior written permission. For written permission, please contact apache@apache.org.
5. Products derived from this Apache software may not be called "Apache," nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.
APACHE DISCLAIMER: THIS APACHE SOFTWARE FOUNDATION SOFTWARE IS PROVIDED "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 APACHE SOFTWARE FOUNDATION 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 Apache software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright © 1999, Lotus Development Corporation., http://www.lotus.com. For information on the Apache Software Foundation, please see http://www.apache.org.
FLEXlm Software
© 1994 - 2003, Macrovision Corporation. All rights reserved. "FLEXlm" is a registered trademark of Macrovision Corporation. For product and legal information, see http://www.macrovision.com/solutions/esd/flexlm/flexlm.shtml.
JfreeChart - Java library for GIF generation
The Software is a "work that uses the library" as defined in GNU Lesser General Public License Version 2.1, February 1999 Copyright © 1991, 1999 Free Software Foundation, Inc., and is provided "AS IS" WITHOUT WARRANTY OF ANY KIND EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED IN THE ABOVE-REFERENCED LICENSE BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARITES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. JfreeChart library (included herein as .jar files) is provided in accordance with, and its use is covered by the GNU Lesser General Public License Version 2.1, which is set forth at http://www.object-refinery.com/lgpl.html/.
BMC - product library
The Software contains technology (product library or libraries) owned by BMC Software, Inc. ("BMC Technology"). BMC Software, Inc., its affiliates and licensors (including SMARTS) hereby disclaim all representations, warranties and liability for the BMC Technology.
Crystal Decisions Products
The Software may contain certain software and related user documentation (e.g., Crystal Enterprise Professional, Crystal Reports Professional and/or Crystal Analysis Professional) that are owned by Crystal Decisions, Inc., 895 Emerson Street, Palo Alto, CA 94301 ("Crystal Decisions"). All such software products are the technology of Crystal Decisions. The use of all Crystal Decisions software products is subject to a separate license agreement included with the Software electronically, in written materials, or both. YOU MAY NOT USE THE CRYSTAL DECISIONS SOFTWARE UNLESS AND UNTIL YOU READ, ACKNOWLEDGE AND ACCEPT THE TERMS AND CONDITIONS OF THE CRYSTAL DECISIONS' SOFTWARE LICENSE AGREEMENT. IF YOU DO NOT ACCEPT THE TERMS AND CONDITIONS OF THE CRYSTAL DECISIONS' SOFTWARE LICENSE, YOU MAY RETURN, WITHIN THIRTY (30) DAYS OF PURCHASE, THE MEDIA PACKAGE AND ALL ACCOMPANYING ITEMS (INCLUDING WRITTEN MATERIALS AND BINDERS OR OTHER CONTAINERS) RELATED TO THE CRYSTAL DECISIONS' TECHNOLOGY, TO SMARTS FOR A FULL REFUND; OR YOU MAY WRITE, CRYSTAL WARRANTIES, P.O. BOX 67427, SCOTTS VALLEY, CA 95067, U.S.A.
GNU eTeks PJA Toolkit
Copyright © 2000-2001 Emmanuel PUYBARET/eTeks info@eteks.com. All Rights Reserved.
The eTeks PJA Toolkit is resident on the CD on which the Software was delivered to you. Additional information is available at eTEks' web site: http://www.eteks.com. The eTeks PJA Toolkit program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License (GPL) as published by the Free Software Foundation; version 2 of the License. The full text of the applicable GNU GPL is available for viewing at http://www.gnu.org/copyleft/gpl.txt. You may also request a copy of the GPL from the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. The eTeks PJA Toolkit program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
For a period of three years from the date of your license for the Software, you are entitled to receive under the terms of Sections 1 and 2 of the GPL, for a charge no more than SMARTS' cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code for the GNU eTeks PJA Toolkit provided to you hereunder by requesting such code from SMARTS in writing: Attn: Customer Support, SMARTS, 44 South Broadway, White Plains, New York 10601.
IBM Runtime for AIX
The Software contains the IBM Runtime Environment for AIX(R), Java™ 2 Technology Edition Runtime Modules © Copyright IBM Corporation 1999, 2000 All Rights Reserved.
HP-UX Runtime Environment for the Java™ 2 Platform
The Software contains the HP-UX Runtime for the Java™ 2 Platform, distributed pursuant to and governed by Hewlett-Packard Co. ("HP") software license terms set forth in detail at: http://www.hp.com. Please check the Software to determine the version of Java runtime distributed to you.
DataDirect Technologies
Portions of this software are copyrighted by DataDirect Technologies, 1991-2002.
NetBSD
Copyright © 2001 Christopher G. Demetriou. 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. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
This product includes software developed for the NetBSD Project. See http://www.netbsd.org/ for information about NetBSD.
4. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR "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 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. <<Id: LICENSE, v 1.2 2000/06/14 15:57:33 cgd Exp>>
RSA Data Security, Inc.
Copyright © 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved. License to copy and use this software is granted provided that it is identified as the "RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing this software or this function. License is also granted to make and use derivative works provided that such works are identified as "derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing the derived work. RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided "as is" without express or implied warranty of any kind. These notices must be retained in any copies of any part of this documentation and/or software.
AES
Copyright © 2003, Dr Brian Gladman <brg@gladman.me.uk>, Worcester, UK. All rights reserved.
License Terms:
The free distribution and use of this software in both source and binary form is allowed (with or without changes) provided that:
1. distributions of this source code include the above copyright notice, this list of conditions and the following disclaimer;
2. distributions in binary form include the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other associated materials;
3. the copyright holder's name is not used to endorse products built using this software without specific written permission.
ALTERNATIVELY, provided that this notice is retained in full, this product may be distributed under the terms of the GNU General Public License (GPL), in which case the provisions of the GPL apply INSTEAD OF those given above.
Disclaimer: This software is provided 'as is' with no explicit or implied warranties in respect of its properties, including, but not limited to, correctness and/or fitness for purpose. Issue Date: 26/08/2003
Feedback
