WAREHOUSE_ODBC.log and WAREHOUSE_ODBC.trc under target system <your
temp directory>\DSNUtil (for example, C:\Temp\DSNUtil).
Startup Center shows some system types as “Unknown
Operating System”
When you run the discovery process for available machines, the Startup Center
might not identify the type of operating system for some systems. These operating
systems are listed as Unknown Operating System.
This issue does not prevent the use of the affected systems. If the operating system
type of a specific system cannot be discovered, you are given the opportunity to
categorize the system manually in a later step. When you assign systems to the
components, if a system categorized as "Unknown Operating System” is assigned
to a component, you can select the correct operating system from the list in the
window that is displayed. After you have specified the correct OS, the system is
moved to the correct category in the list.
The Startup Center uses Nmap OS detection to categorize systems. Nmap OS
detection works by running through a set of probes against target IP
implementations and comparing responses with those in the fingerprint database.
These responses are affected by the specific IP stack creating the response, which
allows for OS detection. However, in some cases it can also be affected by the IP
stack on the system where nmap is running, as well as intermediate firewalls and
routers, for example. In other words, for the same target OS type, several different
fingerprints in the database might be required in order to address these variations.
For additional information, see “Dealing with Misidentified and Unidentified
Hosts” at the Nmap site: http://nmap.org/book/osdetect-unidentified.html
Whenever you find an OS that is not discovered correctly, you should ideally force
nmap to generate a signature, so that you can submit it to Insecure for integration
into the Nmap fingerprint database.
The nmap command is located on the Startup Center media in:
v (W32) StartupCenter/SDE/nmap-5.21-win32
v (Linux) StartupCenter/SDE/nmap-5.21-linux-x86
Run the nmap -O -sSU -T4 -d <target> command, where <target> is the
misidentified system in question. The fingerprint is a series of lines where each
start with "OS". Submit the information at http://insecure.org/cgi-bin/
submit.cgi?corr-os.
Tivoli Enterprise Monitoring Agents
Review the monitoring agent installation and configuration troubleshooting topics
for help with monitoring agent problems that occur during or after installation and
initial configuration.
OS agent installation does not detect system monitor agents
Any agent released with IBMTivoli Monitoring v6.2.2 or before, other than agents
built with the latest Agent Builder tool, should not be installed on top of the
IBMTivoli Monitoring v6.2.2 System Monitor agents.
70 IBM Tivoli Monitoring: Troubleshooting Guide
To Next Page
Loading...
Need help?
General
