Troubleshooting Web Applications

Use this troubleshooting information to help you resolve common problems that might occur when you administer the Web applications.

Device not found
A Device Not Found error might occur when you right-click an event in the Tivoli Netcool/OMNIbus Web GUI and click Find in Hop View.
Topoviz screen is blank
If Topoviz fails to start, or starts with a blank screen, refresh the browser window. If the Network Manager splash screen does not appear, check the topology database access settings.
Unable to access domain
If the Domain drop-down list does not show the expected domain, check your topology database access settings. Also check the files in the $NMGUI_HOME/profile/logs/tnm/ directory for relevant information about the GUI, especially the ncp_topoviz.0.log and ncp_topoviz.0.trace files for relevant information about Topoviz.
Unable to execute right-click tools in Event Viewer
If the Show Root Cause or Show Suppressed Events context menu options fail to execute and return an error message, this might be because the CGI scripts, which are run when you select these menu options, are unable to find the path to Perl.
Device in Topoviz appears as generic node
If a device is known to be a switch or router but appears in the Network Hop View or in the Network Views as a generic node icon, then the device may not be correctly mapped to an icon in its active object class (AOC) file.
Performance impact in network views when many MPLS-TE tunnels are present
The Path View Engine process runs as a background process to build all required views for the network topology. When the topology contains many MPLS-TE tunnels, the Path View Engine process is highly active while the process is building the views, and in some cases the process might impact the performance of the Network Manager GUI.
GUIs not appearing
If you integrate Network Manager web applications into your own product, and certain web applications are not appearing, then this might be because of the clickjacking filter. This filter is applied by default to the Database Access GUI and the Discovery Configuration GUI.
Not authorized error message when logged into Network Manager
You might be unexpectedly logged out of ITNM, or your might receive unexpected error messages about not being authorised when you are logged in, for example, when you try to access Network Manager online help. One solution to this issue is to change the name of the WebSphere Application Server single sign-on (SSO) cookie to ensure that users logged into Network Manager are always recognized as being authenticated with Network Manager, regardless of any other SSO cookies set by concurrent login sessions to other servers, such as Intranet login sessions.

Parent topic: Troubleshooting Network Manager