Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Multiple Tivoli's MN/GW on the same box(To Clone ManagedNodes)

IP.com Disclosure Number: IPCOM000030251D
Original Publication Date: 2004-Aug-03
Included in the Prior Art Database: 2004-Aug-03
Document File: 5 page(s) / 89K

Publishing Venue

IBM

Abstract

The idea is to install multiple instances of Tivoli managed nodes and gateways on a single server as a means to increase endpoint management capabilities without requiring the purchase of additional hardware

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 5

Multiple Tivoli's MN/GW on the same box(To Clone ManagedNodes)

The idea is to install multiple instances of Tivoli managed nodes and gateways on a single server. This has been created at the request of customers who have powerful servers (multiple CPUs, multiple Network Interface Cards (NICs), and substantial memory and disk space) in their Tivoli management environment. These servers are physically capable of hosting additional instances of Tivoli managed node and gateway servers as a means to increase endpoint management capabilities without requiring the purchase of additional hardware

Example Configuration

    Figure 1 shows an example of a configuration in which multiple managed nodes and gateways might be used in a single server. In this example, a modified spoke and hub configuration allows both the spoke and hub servers to manage endpoints.

1

Page 2 of 5

    Recommendations and Assumptions The IBM Tivoli Management Framework and IBM Tivoli Configuration Manager code base assume oserv listening ports are the same throughout a management region. It may be possible to assign different listening port numbers to each oserv, but this has not been tested. Similarly, all gateway listening port assignments should also use the same port. Unique identification of sockets for each managed node is accomplished by binding a unique IP address and name to each socket. This approach has a minor shortcoming in that a remote start of managed nodes on the same computer (using odadmin start) will only work on one instance of

2

[This page contains 1 picture or other non-text object]

Page 3 of 5

a managed node on any one physical server. Once the managed nodes are installed, as described below, there are no other known considerations when working with the managed nodes. They should be treated as separate nodes for all other operations, except as noted regarding a remote start.

    The software used when testing this configuration included the following IBM Tivoli products:

* IBM Tivoli Management Framework 4.1
* IBM Tivoli Configuration Manager 4.2 (for software distribution and inventory functions)
* IBM Tivoli Remote Control 3.8

    Installing additional managed nodes and gateways on a system will consume system resources. For example, system memory utilization will increase. Additionally, customers employing this configuration will need to determine the performance impact on their own networks, taking into account LAN/WAN bandwidth availability and any slow links that may be present in their network. During testing in the Tivoli lab, no significant performance problems were detected using the hardware test bed. Performance may be adversely affected on machines with slower CPUs, less memory, and so on.

    Installing additional managed nodes on a server requires that you create unique subdirectories for each managed node and copy files that were installed by the install...