NetView(R)MultiSystem Manager Network Manager IP Agent

This readme file contains information about the "IBM Tivoli NetView for z/OS MultiSystem Manager Network Manager IP Agent" component of Tivoli(R) NetView for z/OS(R) Version 5 Release 4.

This file is divided into the following categories:


Installation Planning for MultiSystem Manager Network Manager IP Agents

MultiSystem Manager Network Manager IP Agents are available on the following platforms:


Prerequisites

Software Requirements

Note: x86-64 (also noted as x64) term refers to AMD64/EM64T (AMD64 Opteron or Intel EM64T Xeon). x86-64 support statements for these chipsets do not include IA64 architecture (Itanium or Itanium-2).

Platform details for MultiSystem Manager Network Manager IP Agent support:


Selecting the Correct files

The files to launch the installation process are located on the Tivoli NetView for z/OS distribution media under the directory "msm_nm_ip".

setup_msm_itnm_ip_agent_windows.exe Install image for supported Windows.
setup_msm_itnm_ip_agent_aix_ppc.bin Install image for AIX.
setup_msm_itnm_ip_agent_linux_x86.bin Install image for x86 Linux.
setup_msm_itnm_ip_agent_solaris_sparc.bin Install image for Solaris.
msm_nm_ip_readme_en.html English version of this readme file.
msm_nm_ip_readme_ja.html Japanese version of this readme file.
msm_nm_ip.gen Maintenance file to query build level, patch level, and maintence level
msm_nm_installer.properties Multi-platform response file for "silent install".


Installing/Uninstalling the MultiSystem Manager Network Manager IP Agent

General information concerning Installing and Uninstalling Agents

Install - Important Information:


Starting/Stopping the MultiSystem Manager Network Manager IP Agent

On all platforms, the agent can be started and stopped from the command line. Although the install directory could have been customized during installation, the default for Windows is "C:\Program Files\IBM\msm_nm_ip" or "C:\Program Files (x86)\IBM\msm_nm_ip\bin" depending on if your system is 32 bit or 64 bit, and on UNIX platforms, it is "/opt/IBM/msm_nm_ip"

To start the agent perform the following steps in a command window:

  1. Configure the environment for IBM Tivoli Network Manager.
  2. Change the directory to the "bin" directory MultiSystem Manager Network Manager IP Agent installation location.
  3. Invoke the start or stop script as appropriate


Post-Installation Customizations

Initial Configuration
The first time the Agent is started, it will configure the system for use as appropriate. During this configuration, the following panel will be presented that will allow for configuration of such things as User IDs and passwords for communication with the Omnibus and Precision IP databases.

Configuration Panel

See Starting/Stopping the MultiSystem Manager Network Manager IP Agent for the steps required to start the Agent.

The Agent can be forced into configuration mode by starting it with a -Configure option.

FLCP_StartAgent.bat -Configure

The configuration panel will have the following fields:

Command Support
The Agent can be configured to allow commands to be issued to the operating system and restrict where commands can be received from. After the initial configuration, a command control file will be created in the "msm_nm_ip/bin" directory called "command.xml". See the header information inside this file for details of the file format.

SNMP Gateway Configuration
During the initial Agent configuration, configuration files will be created for use by the SNMP Gateway. The SNMP Gateway must use these new configuration files in order for traps to be received and processed at NetView. The SNMP Gateway configuration file is called "MSM_snmp.conf" and will be copied into the appropriate directory on the system. The SNMP Gateway must be started specifying the MSM_snmp.conf file as the configuration file. For example on Windows:

nco_g_snmp -propsfile $OMNIHOME/etc/MSM_snmp.conf Note: If you are not using the default OMNIbus gateway name, you must update the created MSM_snmp.conf file to include the name of the Object Server from where the gateway reads alerts.
Gate.Reader.Server: 'OMNIBUS'

See the publication Installation: Configuring Graphical Components for details on how to configure NetView for z/OS to receive snmp traps.

User Views
The agent will retrieve data from the topology database based on views configured for a specific user. The user can be specified on the GETTOPO command. If the user is not specified on the GETTOPO, the agent will use the user id specified in the FLCP_Defaults.properties file in the field GETTOPO_USER.

Configuring the agent as a service on Windows
The agent can be configured to run as a service on Windows using the flcpmain command. This will allow the agent to start and stop with the operating system. To install the agent as a service, the agent must first be run from the command line in configuration mode. After the initial configuration, the agent can be installed as a service using the following command:

C:\Program Files\IBM\msm_nm_ip\bin\flcpmain -install NCOObjectServer

Note:This will configure the agent to be dependant on the NCOObjectServer service, but only if that service is installed on the local machine.

The agent can be removed as a service using the following command:

C:\Program Files\IBM\msm_nm_ip\bin\flcpmain -remove
Autostarting the agent on a Unix system.
The MultiSystem Manager Agent for ITNM can be configured to autostart with the operating system by modifiying the inittab file in the /etc directory. See the documentation that came with your operating system on how to modify the inittab file.
For example, on AIX, the following line can be added to the inittab to autostart the agent on system startup: flcp:2345:once:/opt/IBM/msm_nm_ip/bin/FLCP_StartAgent.pl > /dev/null

Viewing information about the agent
The FLCP_Level command is provided to display basic information about the agent such as build levels and Java levels.

To issue the command:

  1. Change the directory to the "bin" directory MultiSystem Manager Network Manager IP Agent installation location.
  2. Invoke the FLCP_Level script as appropriate


Restrictions of the MultiSystem Manager Network Manager IP Agent

View Types

The agent is designed to retrieve topology data from the IBM Tivoli Network Manager database and store it in the Resource Object Data Manager for NetView. However, the agent is only able to retrieve a subset of the data obtained by the IBM Tivoli Network Manager. The agent is limited to the following view types:

Dynamic Views

The IBM Tivoli Network Manager product has the ability to change views dynamically based on filter criteria. These criteria can include resources with outstanding alerts or resources that have had ping failures outstanding over an hour for example. The agent builds all views from a snapshot of the database at the time the GETTOPO is issued, therefore these dynamic view may not be up to date. The RODM Collection Manager function of the NMC Console can be used to create dynamic views similar to those created by IBM Tivoli Network Manager.

View differences

The agent will gather data for display in the NMC Console based on the views defined in IBM Tivoli Network Manager, however the views displayed in the NMC Console may not match the layout and in some cases the content of the views displayed in IBM Tivoli Network Manager product. Specifically subnets are laid out in a parent/child relationship where subnet views will contain hosts as opposed to the IBM Tivoli Network Manager views that may contain the subnet and the host in a single view. In addition, view objects may be drawn in a grid or a single line in the IBM Tivoli Network Manager product, but be drawn in a circle on the NMC Console.

Topology links

Regardless of the view type, the agent will only display layer 2 links when they directly connect to a z/OS resource. All other resource can display layer 3 or subnet connections depending on the specifications in the IBM Tivoli Network Manager view creation panel. Although IBM Tivoli Network Manager may collect other types of topology links, such as PIM and IPM Route, the agent will not include these connections in the data sent to the NetView for z/OS product.

Event Types

The MultiSystem Manager will only accept and react to events sent from IBM Tivoli Network Manager and the IBM Tivoli Network Manager probes.

Multi-Domain Support

The MultiSystem Manager agent does not support multi-domain environments. This includes a single Network Manager installation with multiple domains feeding a single database, or multiple Network Manager instances feeding a single database.

Japanese Language

The MultiSystem Manager agent does not support the use of Japanese character sets in data transferred from the IBM Tivoli Network Manager product. View names and other resources that use Japanese characters in IBM Tivoli Network Manager may not display properly when viewed from the NetView management console.


Late-Breaking News

New Enhancements

Hints and Tips

Known Defects

Service History

Further information regarding the MultiSystem Manager Network Manager IP Agent build level is contained in the file msm_nm_ip.gen under the doc subdirectory of the installation location.

Documentation Changes


Getting Help

For Technical Information

We are ready to help you with your MultiSystem Manager Network Manager IP Agent questions. You can contact us through standard problem reporting procedures.

Defect Reporting

For support for this or any Tivoli product, you can contact Tivoli Customer Support in one of the following ways:

Customers in the United States can also call 1-800-IBM-Serv, #2. International customers should consult the Customer Support Handbook, which is available on our Web site at http://techsupport.services.ibm.com/guides/handbook.html

When you contact Tivoli Customer Support, be prepared to provide identification information for your company so that support personnel can assist you more readily. Company identification information may also be needed to access various online services available on the Web site.

The Customer Support Web site offers extensive information, including a guide to support services (the Customer Support Handbook); frequently asked questions (FAQs); and documentation for all Tivoli products, including Release Notes, Redbooks, and Whitepapers. The documentation sets for some product releases are available in both PDF and HTML formats. Translated documents are also available for some product releases.

Additional support is also available on the NetView group on Yahoo!. These forums are monitored by NetView developers who answer questions and provide guidance. When it appears that a problem with the code is found, you will be asked to open a PMR to get resolution.

To find documentation online, point your web browser at the following site and select "Product Documenation and Manuals" in the Learn section.

We are very interested in hearing about your experience with Tivoli products and documentation. We also welcome your suggestions for improvements. If you have comments or suggestions about our documentation, please contact us in one of the following ways:

Determining Your Service Level

When reporting defects it will be necessary to provide Tivoli with your service level. You will receive instructions on how to do this when you contact Tivoli. You can edit or type the file named msm_nm_ip.gen under the doc subdirectory of the installation location. This file lists the level of maintenance of the MultiSystem Manager Network Manager IP Agent.

Also once you are signed onto the MultiSystem Manager Network Manager IP Agent, the service level of your application will appear on the About view.


Trademarks and Copyrights

The following terms are trademarks of the respective companies in the United States or other countries or both:

Licensed Materials - Property of IBM
Product Number 5697-ENV
© Copyright IBM Corp. 2009. All rights reserved.

US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corporation.

Top

Last Updated June 2, 2010