Troubleshooting integration of Network Performance Insight (NPI) and DASH
Use this information to troubleshoot issues that are related to NPI and DASH integration. If you have any further issues, contact our integration expert Amanda YS Yap (email@example.com).
- Check if you have enabled the option to automate remote DASH SSL configuration in IIM during the installation of NPI.
- If Yes, proceed with step 3. If No, proceed with Section B.
IMPORTANT: Take note of WebSphere AppServer path. NPI will create a dash-integration folder, two directories up the WebSphere AppServer path, and Device Dashboard will look for the install.User.cfg file there. In this case:
WebSphere AppServer path = /opt/IBM/WebSphere/AppServer
Dash-integration directory = /opt/IBM/dash-integration
- During the installation, observe the following logs:
- Ambari server’s /tmp/npiDashIntegration.log
You must be able to see that files are being transferred to DASH server
- DASH server’s /tmp/enableDash.log
You must be able to see that it is creating NPI users and groups, grant roles to npiadmin, and creates the certificate.
If successful, proceed with step 5. If there is an error that says “netcool already exists”, proceed to Section C.
- When you proceed to deploy NPI cluster in Ambari, the DASH details and passwords are auto populated:
- After NPI cluster is deployed using Ambari, log in to WebSphere Application Server, go to Security > SSL certificate and key management > SSL configurations > NodeDefaultSSLSettings, to configure the server and client certificate alias. Set them to netcool.
- Restart the WebSphere Application Server. When WebSphere Application Server is stopping, an SSL Signer Exchange Prompt appears. Click Y.
- Download the ca.crt from Ambari server (/opt/IBM/npi/installer-tools/ca.crt) and import it to your browser.
- Go to Options > Advanced > Certificates > View Certificates > Authorities > Import.
- Select the ca.crt from your local machine, select all to trust, and then click OK.
- Do a quick check in the NPI UI log that the component is up and running, and JDBC connection is enabled by using the following command.
cat /opt/IBM/npi/npi-ui/logs/npi-ui.log à symbolic link to /var/log/npi-ui/npi-ui.log
- Install the Device Dashboard. Jazz SM security services that are required for this integration is installed along with it.
- Log in to DASH as smadmin and assign the following user roles to npiadmin:
- Log in again to DASH as npiadmin/netcool.
- Check that the Console Integration URL is created, and that the snowflake icon appears. You might have to click Save again.
- Copy the Console Integration URL and paste to another browser. The URL is as follows:
- Click the deployments link, and then details link. You can see the following screen:
- In the system where Ambari server is installed, configure the /opt/IBM/npi/installer-tools/install.User.cfg
- Run the npiDashIntegration.sh script as follows:
Note: Absolute paths must be given.
- Proceed with Section A, step 3 on wards.
- Log in to WebSphere Application Server and click Security > SSL certificate and key management > SSL configurations > NodeDefaultSSLSettings.
- Configure both default server and client certificate alias to none.
- Go to Security > SSL certificate and key management > Key stores and certificates > NodeDefaultKeyStore > Personal certificates. Remove netcool alias.
- Go to Security > SSL certificate and key management > Key stores and certificates > NodeDefaultTrustStore > Signer certificates. Remove npi_ca alias.
- Restart the WebSphere Application Server.
- Proceed with Section B.
For more information about IBM Network Performance Insight, see IBM Knowledge Center from here.