TADDM 7.2 Interim Fix 1

Get the first fix of the year for TADDM here.

There are only two bugs/solutions in this interim fix, both concerning upgrades from a previous version of TADDM.

From the readme:

IZ67686 TADDM upgrade on a Windows platform failed during the database migration.
The error occurs when TADDM is installed in a different location than default C:\IBM\CMDB
The Customer may find this message in the taddm_7.2.0_install_msg.log:
INFO : com.ibm.cdb.install.ia.utils.Utils (from runCommand(content, envs, filetype)) - Stdout: 
"Run command E:\ibm\cmdb\dist\bin\migration.bat -s -bv 7.1.2"
INFO : com.ibm.cdb.install.ia.utils.Utils (from runCommand(content, envs, filetype)) -
Stderr: 'migration.bat' is not recognized as an internal or external command, operable 
program or batch file.

IZ68633  If the following files are missing: collation/linux.zip, collation/solaris.zip, collation/aix.zip, 
collation/windows.zip, collation/linuxS390.zip the install/migration reports successful, but TADDM will 
not start because the jdks needed to run TADDM and move the internal users from the 7.1.2 encryption 
to 7.2 encryption are not available. The TADDM installation will be missing the 
file: dist/etc/ TADDMSec.properties.

All I can say is that these are boring bugs! ;)

Robert

Pinging the Unpingable

Despite it’s name, the TADDM PingSensor does not run the same ICMP ping that the command line utility ping does. What the PingSensor does is open a TCP socket on specific ports.
The list of ports used is in the Installation Guide:Planning Worksheet:

Port	Target
CiscoWorks	1741
DNS	53
LDAP	389
SSH	22
WBEM	5988
WMI	135

Other ports used are 23 and 161.

This means that if a firewall is blocking these ports, then TADDM will not see any device there, even if another port, such as 80, is open. In that case, you’ll see an error message in the PingSensor log:

2010-02-06 14:13:11,875 DiscoverManager [DiscoverWorker-14] PingSensor-64.12.100.5 INFO session.Ping - Ping failed for IP address 64.12.100.5 on all ports [22, 23, 135, 161]

In this case, you’ll either need to <gasp> open the firewall between TADDM and that server or add another port to the list TADDM scans by adding a property to collation.properties.

From the sensor settings section of the Administration Guide: com.collation.pingagent.ports=xx,yy, ...

By default, this property is used by the PingSensor sensor. It is not defined in the collation.properties file and has to be manually defined if needed. Valid values are non-negative, numerical. To override the default set of ports that the Ping sensor attempts to use, add this property to the collation.properties file and specify the port numbers as a comma-separated list. The default set of ports the Ping sensor attempts to use are port 22 and then port 135, if it cannot first make a connection to port 22. For example, to add the SNMP port 161 to the existing ports that the Ping sensor attempts to connect to, you would add 161 to the end of the list of default ports: com.collation.pingagent.ports=22,135,161. If you only wanted the Ping sensor to use port 161, set it to the following: com.collation.pingagent.ports=161.