Avoiding port conflicts Performing mdm configuration tasks Setting up mdm discovery preferences

This topic lists configuration procedures for avoiding port conflicts between WebSphere Application Server and Tivoli NetView. Additionally, instructions are given for enabling IBM Director to forward SNMP traps to Tivoli NetView.

The following configuration procedures are recommended to avoid port conflicts between WebSphere Application Server and Tivoli NetView.

Steps

Changing the Tivoli NetView Topology Manager Daemon port: There is a potential for conflict between the WepSphere Application Server SOAP connector port and the Tivoli NetView Topology Manager Daemon port. The Tivoli NetView Topology Manager Daemon should be installed on port 8981 by default. However, depending on the system setup, it can also be installed on another conflicting port.

  1. Check the 8981 port value in the \WINNT\system32\drivers\etc\SERVICES file on Microsoft Windows.

    You should see the following entry:

    ovtopmd 8981/tcp # Tivoli NetView Topology Manager daemon

  2. If necessary, change this port number to another unused port number that is not conflicting with WebSphere Application Server.
  3. Restart Tivoli NetView.
  4. Check that all daemons have started successfully by referring to the nv.log file.
Note:Note: It is also possible to set the WAS SOAP Connector port value during installation. You will have this option if you choose the 'advanced' installation path. Otherwise, the panel will be presented to you in the 'typical' path if the installation program detects a conflict.

Enabling the IBM Director to forward trap events to Tivoli NetView: It is possible that IBM Director and Tivoli NetView might have a conflict over the listening port for SNMP traps. The following steps describe how to avoid this conflict:

  1. Change the default port number (162) that NetView listens on for SNMP traps to another unused port number.
    1. Select Start --> Run Multiple Device Manager.
    2. Type the command regedit and click OK. This action starts the Registry Editor.
    3. Select HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\NetView\CurrentVersion.
    4. Right click on the registry value name called trapdSharePort162 and click Modify. Change the value in the Value Data window from 1 to 0.
      Note:Note: Ensure that "Decimal" is selected in the "Base" section when you enter the new value.
    5. Right click anywhere in the free space of the registry value names listing (except on an existing registry value) and select New --> DWORD Value. A new registry value entry should appear highlighted, called New Value #1. Enter the name trapdTrapReceptionPort.
    6. Right click on this new registry value and click Modify. Change the value in the Value Data window to an unused port number.
      Note:Note: Ensure that "Decimal" is selected in the "Base" section when you enter the new port number.
      This new port will be the one that Tivoli NetView will listen on for incoming SNMP traps.
    7. Stop the Tivoli NetView console.
    8. Restart the Tivoli NetView console and ensure that all the daemons are running by checking Options --> Server Setup. All daemons should be initialized and functioning properly. You can consult the nv.log file located in \usr\ov\logs, which will list any problems encountered.
  2. Configure IBM Director to forward SNMP traps to NetView.
    1. Open the SNMPServer.properties file located in \<IBMDirectorInstallationDirectory>\data\snmp.
    2. Ensure that the snmp.trap.port is set to 162. This is the port where IBM Director listens to incoming SNMP trap events.
    3. Set the snmp.trap.v1.forward.address.1 value to the host name of the machine where NetView is running.
      Note:Note: Ensure the host name will resolve.
    4. Set the snmp.trap.v1.forward.port.1 value to XXXX, where XXXX represents the port on which NetView is listening for SNMP traps.
    Note:Note: The same procedure can be used to set V2 traps.

    After completing the installation and configuration, it can be possible that IBM Director still does not see SNMP traps in the event log. This situation can be due to the following dependencies:

    1. IBM Director Service is started.
    2. After IBM Director has started, the Tivoli NetView service can be started which will in turn start the SNMTrap Service.
      Note:Note: If the Tivoli NetView service has started before the IBM Director service, then you will not see any SNMP trap events in the event console, nor will they be forwarded to the NetView console.

Changing the Tivoli Storage Area Network Manager user information: The Tivoli Storage Area Network Manager user information specified in the 'TSANM information' section of the Configure MDM panel must match the password that was entered during Tivoli SAN Manager installation. You can only change this password during the Tivoli SAN Manager installation process.

Related topics Performing mdm configuration tasks Setting up mdm discovery preferences

(C) Copyright International Business Machines Corporation 2004