Common issues

Check the configuration of the database system.

• On the Log Retrieval and Configuration page, click the Appliance tab and check the Identity data store configuration, server system out, and server messages.
• If your configuration is not successful, try to configure again. In case of any problems, you might want use a previously taken snapshot to restore the virtual appliance to its previous state.

Check the configuration of the directory server:

• On the Log Retrieval and Configuration page, click the Appliance tab and check the directory server configuration, server system out, and server messages.
• If your configuration is not successful, try to configure again. In case of any problems, you might want use a previously taken snapshot to restore the virtual appliance to its previous state.

To resolve this issue, add the certificate to the client.

1. Log on with Administrator privileges on the client computer.
2. Start a web browser and go to the HTTPS URL for the IBM Security Identity Manager Server https://hostname where host name is the name of the computer that has the IBM Security Identity Manager virtual appliance Server.
3. In the web browser, export the security certificates to a file.
4. Complete the following instructions:
   1. On the Microsoft Internet Explorer, click File > Properties.
   2. Click Certificates.
   3. Click the Certification Path tab.
   4. Click the Details tab.
   5. For each certificate marked with a red X in the certificate hierarchy, do the following actions.
      1. Click View Certificate.
      2. Click Details.
      3. Click Copy to File.
      4. Follow the instructions in the wizard with the following considerations:
         • When the Export format page is displayed, select the DER encode binary x.509 (CER) format.
         • Save the certificates on your local computer. For example: webhost.cer.
5. Restart the computer.

getStatus Status of Node <ISIM_VA_NodeName> is unavailable 

1. Navigate to the monitor command.

   
   <ISIMVA_SERVER> > isim
   <ISIMVA_SERVER>: isim> logs
   <ISIMVA_SERVER>: logs> monitor
   <ISIMVA_SERVER>: monitor> 
   

2. Select option 2, and then option 4 to view the trace.log file contents.

1. <isimva_server>: tools> connect
2. <isimva_server>: tools> ping
3. <isimva_server>: tools> traceroute

Possible reasons:

• The IBM Security Identity Manager virtual appliance has short host name.
• The short host name does not map to the same IP address as the long host name.

1. Ensure that the IBM Security Identity Manager virtual appliance cluster nodes have fully qualified domain names (FQDN) as a host name.

   To change the host name, see Changing host name of the IBM Security Identity Manager virtual appliance.

2. Ensure that the hosts file is correctly configured with the fully qualified domain names of IBM Security Identity Manager virtual appliance cluster nodes.

   To manage hosts file, see Manage hosts file.

1. <isimva_server>: tools> connect
2. <isimva_server>: tools> ping
3. <isimva_server>: tools> traceroute

• Firewall exists between IBM Security Identity Manager virtual appliance and external system and it is blocking incoming traffic from IBM Security Identity Manager virtual appliance.
• Firewall exists on external system and it is blocking incoming traffic from IBM Security Identity Manager virtual appliance or outgoing traffic from an external system.
• Issue with the subnet and subnet mask. Should the system belong to the same subnet or different subnets?
• Another DNS entry for some other system by using the same IP address.

• Modify the firewall setting to allow the incoming and outgoing traffic between IBM Security Identity Manager virtual appliance and external systems.
• The DNS must not grant entry to another system with the same IP address.
• Ensure that the correct subnet and subnet mask details are set. If IBM Security Identity Manager virtual appliance and external systems belong to different subnets, then make sure that you have added a static route. To add a static route, see Configuring static routes.

1. Navigate to the monitor command.

   
   <ISIMVA_SERVER> > isim
   <ISIMVA_SERVER>: isim> logs
   <ISIMVA_SERVER>: logs> monitor
   <ISIMVA_SERVER>: monitor> 
   

2. Select option 5, and then option 2 to view the SystemOut*.log file contents.

   You can also find SystemOut *.log files in support file at: <SupportFile_ExtractedDirectory>/opt/ibm/WebSphere/AppServer/profiles/<NodeName>/logs/<APP_MEMBER_NAME>/SystemOut*.log

1. View the trace*.log of IBM Security Identity Manager by using ISIM VA CLI .
2. Browse for the monitor command.

   
   <ISIMVA_SERVER> > isim
   <ISIMVA_SERVER>: isim> logs
   <ISIMVA_SERVER>: logs> monitor
   <ISIMVA_SERVER>: monitor> 
   

   You can find trace*.log files in support files at: <SupportFile_ExtractedDirectory>/var/ibm/tivoli/common/CTGIM/logs/trace*.log

1. Navigate to the monitor command.

   
   <ISIMVA_SERVER> > isim
   <ISIMVA_SERVER>: isim> logs
   <ISIMVA_SERVER>: logs> monitor
   <ISIMVA_SERVER>: monitor> 
   

2. Select option 6, and then option 2 to view the SystemOut*.log file contents.

   You can also find SystemOut *.log files in support file at: <SupportFile_ExtractedDirectory>/opt/ibm/WebSphere/AppServer/profiles/<NodeName>/logs/<MSG_MEMBER_NAME>/SystemOut*.log

   For more information about how messaging and transactions work, see the IBM WebSphere Application Server product documentation.

   To check the SIB tables that are involved in messaging, see Clearing the service integration bus.