Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Storage Manager (STM) > SRM Profiler Administrator Guide > Install SRM Profiler > Integrate SRM Profiler with Orion NPM

Integrate SRM Profiler with Orion NPM

Updated: June 16, 2017

Integrating SRM Profiler with Orion NPM allows you to have the SRM Profiler and the Orion Network Performance Monitor integrated on one browser tab rather using having to multiple browser tabs.

The SRM Profiler Installer package includes an integration module that can be installed on your Orion NPM server. This light integration provides a Storage tab in your NPM web console that provides a quick view of your storage metrics.

This installation requires Orion core 2012.2.2 or later.

Install the SRM Profiler /Orion NPM integration piece

  1. Locate the integration module installer (OrionIntegrationModuleforStorgaeManager.msi) that is included in the product download. Copy it to the Orion server (Core 2012.2.2 and later) and execute it.
  2. Go to NPM Settings > SRM Profiler Settings and enter the IP address and login credentials you want to use.

    File:Success_Center/Reusable_content_-_InfoDev/SRM_Profiler/Integrate_SRM_Profiler_with_Orion_NPM/0300001D_428x167.png

    On some browsers, if you click Test, it erases the password. If you are using HTTPS the Test button reports an error.

  3. Click on the storage tab to see the SRM Profiler main console.

When SRM Profiler is configured to use LDAP authentication, then the domain is assumed by SRM Profiler based on those settings. Therefore, when you configure the Orion SRM Profiler Settings, they should not specify the domain when filling in the Login Name field.

If you have configured LDAP authentication in SRM Profiler and configured a domain of foodev, they will not include this in the SRM Profiler settings page. For example, instead of foodev\john.doe, just use john.doe.

The user can also configure the credentials for the admin user, as that user will be authenticated against the local SRM Profiler user database, not LDAP, regardless of whether or not LDAP authentication is enabled.

 
Last modified
11:17, 26 Jun 2017

Tags

Classifications

Public