Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
|A single word||
||Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".|
You can specify that the search results contain a specific phrase.
Topics that contain the literal phrase "cat food" and all its grammatical variations.
Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.
Two or more words in the same topic
|Either word in a topic||
|Topics that do not contain a specific word or phrase||
|Topics that contain one string and do not contain another||
|A combination of search types||
This section describes common problems and limitations that you may encounter when working in the Administration area of OMi.
For additional troubleshooting information, use the Self-Solve Knowledge Search https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result?keyword=
Additional troubleshooting information
With the following tools and tips you can gather troubleshooting information in addition to the OMi logs.
If you are having problems with your OMi installation and need to contact HPE Software Support, use the opr-checker tool to generate a summary of your installation.
Run the opr-checker tool from the following location and specify a target location for the output file:
<OMi_HOME>/opr/support/opr-checker.[bat|pl] -a > <TempDir>/opr-checker.xml
Send the resulting XML file to Software Support for analysis.
Verify that all ports required by OMi servers are not in use by other applications on the same machine. To do so, open a command prompt or terminal window, and run netstat (or use any utility that enables you to view port information). Search for the required ports.
You can also check the
<OMi_HOME>/log/jboss7_boot.log for ports in use. If the
jboss7_boot.log reports "
Port <> in use" but you do not see that this port is in use when you run netstat utility, restart the server and then start OMi.
For details on the ports required by OMi, see Port Usage.
Tip To troubleshoot port usage problems, use a utility that lists all ports in use and the application that is using them.
The OMi logging and tracing capabilities for Apache Flex-based UIs help simplify on-site troubleshooting.
Note Due to sandbox restrictions in the Adobe Flash Player and the browser, it is not possible to write logs to the client's local file system.
Tip Use the browser's built-in developer tools to troubleshoot the OMi HTML5-based UIs.
To enable logging, do the following:
Log on to OMi:
Open the following URL to open the logging configuration application.
The Logging Settings dialog box opens.
To enable logging, select the Enable logging for this session check box.
Select the required logging level. Each log level includes the higher levels:
Critical: Shows only problems of level Critical.
Error: Shows problems of level Error and Critical.
Warning: Shows problems of level Warning, Error, and Critical.
Info: Shows problems of level Info, Warning, Error, and Critical. The resulting information provides a brief overview over the flow of the executed steps.
Debug: Shows problems of level Info, Warning, Error, and Critical. The resulting information provides a detailed, verbose view over the flow of the executed steps.
Optional. Set a filter value to find instances of the specified text strings. By default, all messages that have a category starting with
com.hp. are logged. You can restrict this to certain categories to filter the output or extend it, for example, to show messages from the Flex framework.
The settings become effective for the current browser session.
Restart the user interface that you want to trace.
As soon as the first log output is sent, a browser window opens that shows the log messages.
Note Each time you change the logging settings you must restart the user interface that you want to trace.
The settings are for applications that are served from the same domain as that of the current browsing session. If you restart the web browser, you must reapply the logging settings.
To save the log information, do the following:
In the browser window that shows the log messages, click Export to log4j.
In the Opening GuiTrace.log dialog box, select whether you want to open or save the
Learn how to solve problems relating to event correlation, including creating, modifying, and enabling events.
If a high number of events with ETIs is forwarded to OMi over a long period of time (30 minutes or longer), the correlation engine only considers up to the specified number of most recent events. If this limit is exceeded, the oldest events are removed from the queue and no longer considered for correlation.
This limit is set using the Max Waiting Queue Size attribute and is located in:
Administration > Setup and Maintenance > Infrastructure Settings > Operations Management > Topology-Based Event Correlation Settings
The default value is 5000. The valid range is 100 to 20000.
If you are experiencing this problem, lower the incoming event rate or increase the Max Waiting Queue size limit. If the limit is increased, you should also monitor the memory consumption and, if necessary, increase the memory setting (parameter -Xmx) for the opr-backend process.
No rule is selected in the Correlation Rules pane
No view is active in the Rules Topology pane
No configuration item type is selected in the Rules Topology pane
No indicator is defined for the selected CI type
The rule is invalid or incomplete, for example:
The rule does not have at least one symptom event
The rule does not have a cause event
The topology path is invalid
The rule refers to a configuration item that is not resolvable
This issue is related to the Security Settings of Internet Explorer.
To display the title in place of the URL, go to:
Internet Options> Security> Internet Zone> Custom Level
Enable Allow web sites to open windows without address or status bars.
Load and access troubleshooting
Learn how to solve problems if components of OMi fail to load, or if certain areas in OMi cannot be accessed.
If the links from RTSM Administration do not work, this may be caused by one of the following:
Make sure that the OMi gateway server is able to access the Default Virtual Server for Application Users URL. This URL can be found in Infrastructure Settings:
Administration > Setup and Maintenance > Infrastructure Settings
Alternatively, click Infrastructure Settings.
In the Foundations field, specify Platform Administration. The URL is located in the Host Configuration table.
If you are using a reverse proxy or load balancer, make sure you log in through the URL specified above.
The Recipients page does not open, or the recipients page opens, but recipients cannot be added or modified.
This error occurs if the default templates for recipients were not loaded when OMi was installed. Do the following to fix this issue:
Access Administration > RTSM Administration > Package Manager.
Click Deploy packages to server (from local disk).
Click Add, select the
BSMAlerts.zipfile and click Open. Deploy the package.
You may have to copy the
BSMAlerts.zipfile from the OMi system to your local system.
Note Recipients that were create before
BSMAlerts.zip was redeployed have no valid notification template and must be deleted and added again.
Open Control Panel > Java > Temporary Internet Files > Settings and make sure Keep temporary files on my computer is selected. If the problem persists, clear the Java cache by clicking Delete Files in the same location.
Old java files on your client computer.
Clear the Java cache by following this procedure:
Open Control Panel > Java > Temporary Internet Files > Settings.
In the Temporary Internet Files section, click Settings.
In the Temporary File Settings dialog box, click Delete Files.
This is due to Java security enhancements. Before Java applets and Java Web Start applications run, the signing certificates are checked to ensure that a signing certificate was not revoked.
If there is a proxy problem or any other network issue, you should disable this Java feature.
To disable Java from performing certificate revocation checks:
- Open the Control Panel.
- Click the Java icon to open the Java Control Panel.
- Click the Advanced tab.
- Locate and deselect the option to perform certificate revocation checks.
After the reconfiguration of OMi in a distributed environment, the workspaces menu is empty.
This error might occur if a new database is created on the data processing server, with the
uimashup files being on the gateway server.
If the database was recreated during the reconfiguration, run the following commands to copy the
uimashup files to the correct location:
xcopy /S /Y "<OMi_Home>\conf\uimashup\import\loaded\*" "<OMi_Home>\conf\uimashup\import\toload"
-rf /opt/HP/BSM/conf/uimashup/import/loaded/* /opt/HP/BSM/conf/uimashup/import/toload
After reloading the Event Browser (HTML), Japanese view names are displayed as question marks, and no events are listed.
This issue occurs if the Microsoft SQL Server database is not installed on a Japanese operating system. To resolve the issue, install the MS SQL database on a Japanese operating system.
Load balancer troubleshooting
Learn how to solve problems that can occur if you use a load balancer.
OMi requires sticky sessions for users. Make sure the persistency settings are set to stickiness by session enabled or Destination Address Affinity (depending on the load balancer).
Check the KeepAlive URIs.
Virtual hosts and load balancer must be configured with a fully qualified domain name (and not an IP) for LW-SSO to work.
Connectivity and login troubleshooting
Learn how to solve connectivity and login issues.
Connectivity problems include the inability to log into OMi.
This can happen if the TopazInfra.ini file is empty or corrupt.
In a browser on the gateway server, type
https://localhost:29000to connect to the JMX console.
Under Topaz, select Topaz:service=Connection Pool Information.
Click the showConfigurationSummaryInvoke button toward the bottom of the page. If the Operation Result page is blank, the TopazInfra.ini file is empty or corrupt.
If prompted, enter the JMX console authentication credentials (if you do not have these credentials, contact your system administrator).
To solve this problem, rerun the OMi configuration wizard and either reconnect to your existing management database or define a new management database. If you did not discover a problem with the TopazInfra.ini file, contact HPE Software Support.
The page file size is too small.
Configure the page file size to be at least 150% of RAM size. Restart the server.
You can track who attempted to log into OMi:
Open the following file:
You can display a list of the users that are currently logged in:
Open the JMX console on the machine that is running OMi. (For detailed instructions, see JMX Console.)
Under the Topaz section, select service=Active Topaz Sessions.
Invoke the java.lang.String showActiveSessions() operation.
Find solutions for common problems that you may encounter when OMi is configured in a high availability setup.
If the High Availability Controller's Automatic Failover mode is enabled and the management database has been down for some time, some processes may be stopped and will not resume automatically when the management database returns to normal operation. These processes will have the status STARTING on the OMi
serverStatus.jsp tool (Windows:
Restart these processes once the management database is available again.
log/odb_boot.logshows RTSM failed error
The handling of the high availability information has been changed with RTSM 10.22, and due to this the following messages might be logged in
/log/odb_boot.log after an update to 10.62 or higher:
SEVERE: <db>_rtsm: failed removing row 1: java.io.EOFException; please delete it manually
The messages can be ignored, but they will make it difficult to find real problems in the log file. Stop the messages by emptying the following two tables in the RTSM database:
MS SQL databases:
DELETE FROM [TABLE_NAME].[dbo].[HA_WRITER]
DELETE FROM [TABLE_NAME].[dbo].[JGROUPSPING]
DELETE FROM "TABLE_NAME"."HA_WRITER"
DELETE FROM "TABLE_NAME"."JGROUPSPING"
DELETE FROM HA_WRITER;
DELETE FROM JGROUPSPING;
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to email@example.com.
Help Topic ID: