CA NSM CA SPECTRUM Root Cause Integration

Transcription

1 CA NSM CA SPECTRUM Root Cause Integration User Guide Version 1.3.1

2 Legal Notice This publication is based on current information and resource allocations as of its date of publication and is subject to change or withdrawal by CA at any time without notice. The information in this publication could include typographical errors or technical inaccuracies. CA may make modifications to any CA product, software program, method or procedure described in this publication at any time without notice. Any reference in this publication to non-ca products and non-ca websites are provided for convenience only and shall not serve as CA s endorsement of such products or websites. Your use of such products, websites, and any information regarding such products or any materials provided with such products or at such websites shall be at your own risk. Notwithstanding anything in this publication to the contrary, this publication shall not (i) constitute product documentation or specifications under any existing or future written license agreement or services agreement relating to any CA software product, or be subject to any warranty set forth in any such written agreement; (ii) serve to affect the rights and/or obligations of CA or its licensees under any existing or future written license agreement or services agreement relating to any CA software product; or (iii) serve to amend any product documentation or specifications for any CA software product. The development, release and timing of any features or functionality described in this publication remain at CA s sole discretion. The information in this publication is based upon CA s experiences with the referenced software products in a variety of development and customer environments. Past performance of the software products in such development and customer environments is not indicative of the future performance of such software products in identical, similar or different environments. CA does not warrant that the software products will operate as specifically set forth in this publication. CA will support only the referenced products in accordance with (i) the documentation and specifications provided with the referenced product, and (ii) CA s then-current maintenance and support policy for the referenced product. Certain information in this publication may outline CA s general product direction. All information in this publication is for your informational purposes only and may not be incorporated into any contract. CA assumes no responsibility for the accuracy or completeness of the information. To the extent permitted by applicable law, CA provides this document AS IS without warranty of any kind, including, without limitation, any implied warranties of merchantability, fitness for a particular purpose, or non-infringement. In no event will CA be liable for any loss or damage, direct or indirect, from the use of this document, including, without limitation, lost profits, lost investment, business interruption, goodwill or lost data, even if CA is expressly advised of the possibility of such damages. Copyright License and Notice This publication contains sample application programming code and/or language which illustrate programming techniques on various operating systems. Notwithstanding anything to the contrary contained in this publication, such sample code does not constitute licensed products or software under any CA license or services agreement. You may copy, modify and use this sample code for the purposes of performing the installation methods and routines described in this document. These samples have not been tested. CA does not make, and you may not rely on, any promise, express or implied, of reliability, serviceability or function of the sample code. Copyright 2008 CA. All rights reserved. All trademarks, trade names, service marks and logos referenced herein belong to their respective companies. Last Updated: May 8, 2009

3 Contents Introducing CA NSM SPECTRUM Root Cause Integration... 1 How it Works... 2 Process Flow... 4 Best Practices Considerations... 4 Installation... 7 Post Installation Configuration Executable Reference NSM - SPECTRUM Root Cause Integration Page iii

4 Introducing CA NSM SPECTRUM Root Cause Integration Enterprises today increasingly rely on multiple technologies to monitor and manage their IT environments. Many of them count on CA SPECTRUM to monitor their networks while utilizing CA Network and Systems Management (NSM) to manage their servers and applications. Until now, what has been missing is the ability to merge network reliability data with system performance and status data to create a single view of service status. Enterprise level IT systems cannot exist without reliable, robust networks to link them together. Similarly, the network is of little use without the systems and services it supports. By positioning SPECTRUM as the authority for network status and performance while NSM monitors applications and servers, the SPECTRUM Root Cause Integration package bridges that gap. It leverages the superb root cause analysis capability of SPECTRUM to identify when the interruption of IT Services managed by NSM Systems Management (SM) Pack results from network performance issues rather than server and application performance shortfalls. For example, consider a service that relies on an end user accessing data on your database server. The application might have the user connecting to an application server via a network infrastructure that includes an architecture of routers, hubs, switches, etc. The application server may similarly access data stored on a remote database server likewise connected through the network. When your user is unable to execute the application it costs you money and you need immediate access to information as to whether the fault lies in the network, the application server, the application, or the database. You need a system that will create trouble tickets and alert the responsible personnel. They need the information on the outage to expedite restoration of service. SPECTRUM Root Cause Integration consolidates performance data from the entire service s infrastructure into a single view drawing on the strengths of SPECTRUM, NSM and, optionally, other sources. The SPECTRUM Root Cause Integration package does the following: Enables correlation of SPECTRUM Service events and root cause analysis with SM Pack IT Services Deduplication of alerts, discovery and polling Suppresses ANY:ABSENT DSM messages for objects affected by SPECTRUM Service outages to avoid unnecessary trouble tickets Automatically and expeditiously restores monitoring of those objects when the SPECTRUM Service is restored Launches SPECTRUM OneClick in context with IT Service NSM - SPECTRUM Root Cause Integration Page 1

5 This document identifies further how the integration works, as well as how to install, configure and use it. How it Works SPECTRUM provides an excellent platform for managing your network assets. It has the ability to monitor a wide range of network devices and architectures and incorporates advanced root cause analysis to suppress false alerts from network elements downstream of the actual outage. At the core of the SPECTRUM solution is a concept called Business Service Intelligence (BSI) a methodology for understanding the relationships and impact of IT infrastructure on business services. SPECTRUM and OneClick enable you to organize your IT resources into logical groupings or services. When an alert is generated for one of these services, policy within the SPECTRUM Alarm Notifier forwards the alert to the NSM Event Management Server where SM Pack is running. SM Pack is one of several Capability Solutions upon which CA has built its vision for unifying and simplifying Enterprise IT Management (EITM). Available as an additional downloadable component from the CA Support website ( SM Pack utilizes prewritten policy, custom WorldView Instance Level Properties (ILPs) and easy-to-use installation and configuration wizards to organize the applications, servers and resources associated with IT Business Services into NSM IT Service views. The relationships between SPECTRUM Services and SM Pack IT Services can be one-to-one, one-to-many or many-to-many. For example, a single router failure detected by SPECTRUM could affect multiple IT Services. Similarly, one IT Service could be vulnerable to outages from one or more network devices. The Root Cause Integration tool includes flexible strategies to handle all of these different situations. Correlation between SPECTRUM Services and SM Pack IT Services is achieved by establishing a link in NSM WorldView as below. NSM - SPECTRUM Root Cause Integration Page 2

6 In the picture above, an object representing the SPECTRUM Service model Hdqtrs_Acctg is displayed in the MCC. The service is linked to the Hdqtrs_Acctg IT Service by copying the SPECTRUM Service object under it. While the names here are the same for clarity, this is not required. As discussed later in this guide, you could also have several SPECTRUM Services related to the SM Pack IT Service or one SPECTRUM Service related to several SM Pack IT Services. Note: See Best Practices Considerations section below. NSM Enterprise Management (EM) processes messages forwarded from SPECTRUM to set the status of the SPECTRUM Service tracking object and, thereby, reflect the status in all affected IT Services. SM Pack can also utilize the Alert Management System (AMS) to generate Service Desk trouble tickets and alert the appropriate personnel of the outage. Note: Messages in blue indicate that the alert has been suppressed. This occurs when SM Pack has found a pre-existing alert for the same service. This occurrence is exclusive of messages for UNKNOWN services or UNCLASSIFIED objects which will also be shown in blue. SM Pack also pre-processes DSM alerts indicating ANY:ABSENT or polling timeout status. This prevents generation of duplicate\false alerts or trouble tickets for NSM objects under a SM Pack IT Service when the associated SPECTRUM Service tracking object reflects that SPECTRUM has already determined a possible root cause of the problem. When SPECTRUM clears the alert, a message is again transmitted to the NSM server. EM policy identifies which IT Services have been affected by the alert and commences rediscovery of those objects associated with the services to restore normal monitoring. NSM - SPECTRUM Root Cause Integration Page 3

7 Process Flow This section describes the process flow followed by this integration. SPECTRUM Alarm Processing First, the SpectroSERVER monitoring network devices determines that an outage has occurred for an object associated with a SPECTRUM service. This causes an alarm to be passed to the SPECTRUM Alarm Notifier (SAN). SAN scripts execute a NSM CAWTO command to send an alert message to the NSM Event Management Server where SM Pack is active. Although using CAWTO requires that a NSM Event Agent (or Manager) be installed on the SPECTRUM server, it assures that the alarm is delivered. NSM Event Management Processing Next, EM policy on the NSM server intercepts the SPECTRUM alarm message and uses it to set the WorldView SPECTRUM Service tracking status. When a DSM poll fails, it issues an ANY:ABSENT or similar timeout message. SM Pack determines if the polled object is part of an IT Service that includes the alerting SPECTRUM Service. If so, SM Pack suppresses the alert, thus preventing creation of duplicate alarms and trouble tickets. Alarm Resolution Finally, once SPECTRUM detects that the root cause device has returned to service, it issues an event to SAN. SAN forwards the message to NSM where EM determines which IT Services the SPECTRUM Service is associated with and which hosts have been affected. It then initiates a onetime rediscovery of the affected hosts to rapidly restore full monitoring and recovery from the incident. Best Practices Considerations Before you install the integration you need to carefully consider how you plan to use it and to do that you need to take a close look at how you currently define your SPECTRUM and SM Pack IT services. The BEST approach is to define a one-to-one relationship between the respective services defining the network components that support a particular IT Service as a SPECTRUM Service. However, it is more likely that you do not have such flexibility as the result of previously defined services and requirements of different system support organizations and management. Therefore, you will need to adapt your service configuration to achieve the best relationship possible. NSM - SPECTRUM Root Cause Integration Page 4

8 The following sections discuss some things you should consider before proceeding. The first of these is the definition of SPECTRUM Network Services models. For more information on this, please refer to the SPECTRUM Service Manager User Guide (document 5155). Shared Network Resources Network devices often support multiple business systems. For example, a major router may be responsible for managing the network traffic to Sales Accounting, Sales Offices, and Warehousing components downstream. This entire network could be defined as a single SPECTRUM Service. That service could then also be defined as a component of the respective SM Pack IT Services. As a result, an alarm generated by that SPECTRUM Service can be shown to have impacted three SM Pack IT Services. Clearly, although this categorization can provide some value, it is also a bit clumsy. The more granularity you can build into your SPECTRUM services the better the definition will be. Following is an example of how a shared device is defined in each of the services it supports. Shared Network Resources RouterA Sales Accounting Warehousing Sales Offices A better approach in this case might be to allocate the interfaces of RouterA to the service it supports. NSM - SPECTRUM Root Cause Integration Page 5

9 Distributed Network Resources In some cases IT Service components may be spread over several SPECTRUM Services. In the example below, the Sales IT Service depends on network components in several shared network segments. This configuration is better because the SPECTRUM Service definition closely matches the IT Service definition. Distributed Sales IT Service Resources RouterA Western Sales Region Eastern Sales Region Headquarters Once again, a one-to-one relationship is the BEST approach but it s likely you will need to be more flexible. In these cases, Spectrum Root Cause Integration provides the flexibility to adapt your system to those requirements in one-to-many, many-to-one and many-to-many relationships. Distributed SpectroSERVER Environment Another consideration is how SPECTRUM will manage your services. If you have implemented a Distributed SpectroSERVER (DSS), here are some things you should consider: 1. Any SpectroSERVER that would send alarms to NSM will need an Event Agent installed. 2. When there are multiple SpectroSERVERs, services can use resource models from other SpectroSERVERs and, of course, those resource models can be other services. Therefore, an individual service resides on a single SpectroSERVER, but your service hierarchy can span multiple SpectroSERVERs. NSM - SPECTRUM Root Cause Integration Page 6

10 Note: This may enable you to resolve any concerns raised by the Event Agent requirement identified in the first list item, by creating all of your services in a single SpectroSERVER or MLS that models remote services. 3. If you have a set of geographically distributed SpectroSERVERs then this could be a good place to run an instance of Alarm Notifier for each and roll the data to a common NSM server where SM Pack resides. 4. In other deployments the DSS might be used just for device capacity, where services across the distributed environment feed up to parent services on the MLS (top level SpectroSERVER), and a single instance of Alarm Notifier on the MLS could report for the top tier services. Whatever your actual requirements may be, the SPECTRUM Root Cause Integration is designed to provide the flexibility needed to support your architectural requirements. SpectroSERVER and DSM Network Perspectives Ideally, the SpectroSERVER and DSM should have the same perspective of the network in order to ensure that an outage perceived by SPECTRUM is similarly perceived by NSM. In other words, the DSM should not have an alternate route to the device that was unavailable to the SpectroSERVER. Since this is understandably difficult to ensure in a distributed environment, the integration policy pack does include an Event Action to ping a host when DSM reports a failed poll (ANY:ABSENT or timeout). If the ping succeeds, the message will be considered the result of other causes. However, to the extent possible this situation should be avoided. Installation This section provides details on how to install the integration package on both the NSM and SPECTRUM machines. Prerequisites The following components must be installed on the SPECTRUM host: CA SPECTRUM 8.1 SP 1 or newer CA NSM r11.1 or newer Event Agent CA NSM communications with CA NSM Event Management server The following components must be installed on the CA NSM Event Management host: CA NSM r11.1 or newer NSM - SPECTRUM Root Cause Integration Page 7

11 CA Systems Management Pack r2.0 with TSAMP0004, TSAMP0005 and TSAMP0006 fixes applied or later It is strongly recommended that the Event Command Proxy (EvtCmdProxy) utility be installed to preclude errors due to multiple MDB logons. This utility is included on the installation media. SPECTRUM Install The only updates made to the existing SPECTRUM host are modifications to the SAN SetScript and ClearScript scripts. SetScript Change to the $SPECROOT\Notifier directory and add the following lines to the SetScript file: # Send message to NSM Event Manager if [ $MTHANDLE = 0x1046f ] then <NSM install dir>/wvem/bin/cawto n <nsm server> %SSRC_I_001: $SERVER reports service $MNAME alarm new alarmid $AID status $STATUS severity $SEV model handle $MHANDLE fi Note: When SPECTRUM runs on a Windows platform, AlarmNotifier runs in a bash shell and, therefore, the path must use forward slashes ( / ). ClearScript A similar message must then be added to the ClearScript for message ID %SSRC_I_003 as follows: # Send message to NSM Event Manager if [ $MTHANDLE = 0x1046f ] then <NSM install dir>/wvem/bin/cawto n <nsm server> %SSRC_I_003: $SERVER reports service $MNAME alarm cleared alarmid $AID status $STATUS severity $SEV model handle $MHANDLE fi NSM Install The Root Cause Integration package includes a convenient installer to expedite setup on the NSM server. The install defines and loads necessary binaries, SM Pack Policy Packs, and documentation. You can also launch a Service Locator utility at the end of the install to discover your Spectrum Services and add them to the MDB. Once the Spectrum Services are defined, the Spectrum Service Coordinator will assist you in associating these services with your IT Services. NSM - SPECTRUM Root Cause Integration Page 8

12 Once the install confirms that all prerequisites, such as user credentials, OS, and NSM, have been met on the target system, it presents a welcome screen, indicating that Spectrum Root Cause Integration will be installed. Click Next to continue. The next screen is the End User License Agreement (EULA) dialog. Please read the license in its entirety by scrolling to the bottom. This will activate the I agree button. NSM - SPECTRUM Root Cause Integration Page 9

13 If you agree to the license click this button, otherwise click I disagree and the install will terminate. Next, provide your name and company name in the Customer Details dialog. Click Next to continue. In the next screen, enter the path where you would like the SPECTRUM Root Cause Integration files to be installed. NSM - SPECTRUM Root Cause Integration Page 10

14 Click Next to proceed to the MDB Information screen: Event Management requires access to the NSM MDB in order to manage the service objects. In this dialog provide the logical name of the MDB. This may be the node or SQL instance on which the MDB is installed or it could be a proxy name. If you are unsure, execute the NSM wvrepsel command, which will display the name of the MDB in use. Then, enter the MDB administrative user id, which is typically nsmadmin, and password. The password will be encrypted and stored in the system registry along with other MDB access information. Click the Test mdb connection button to verify the credentials are correct. This will activate the Next button which will continue the install. Setup now has the information needed to install the integration. The Ready to install screen displays the list of tasks that will be performed. NSM - SPECTRUM Root Cause Integration Page 11

15 Click Next to begin the install. When the install completes, the final screen is displayed. This screen includes two checkboxes. The first launches the Readme file which you are encouraged to read in order to familiarize yourself with the latest updates and tips on using the integration package. The second checkbox is used to launch the Spectrum Services Setup tool which is described in Using SPECTRUM Service Setup Wizard. NSM - SPECTRUM Root Cause Integration Page 12

16 Post Installation Configuration Once these updates have been made to both the SPECTRUM and NSM installations, you need to perform the following tasks to complete installation of the integration package: define SPECTRUM Services in the MDB configure Service Management Pack (SMP) associate those objects with SM Pack IT Services identify IT Services as SPECTRUM Managed Services set NSM Event Management CA_OPR_FORMAT_NODEID This section describes how to perform those steps, however, before proceeding be sure to review the earlier Best Practice Considerations section in order to make the best configuration choices. Define SPECTRUM Services to SM Pack The installation creates a SPECTRUM Root Cause object and the following two new WorldView classes: SpectrumService. Used to define Spectrum Service objects. SpectrumITServices. Used to define the container for the Spectrum Services associated with an IT Service. The SPECTRUM Root Cause BPV is displayed in the NSM server s Managed Object Root container in MCC. It contains three objects: Unknown Spectrum Services Spectrum Services NSM - SPECTRUM Root Cause Integration Page 13

17 Related IT Services Unknown Spectrum Services This BPV contains all of the SPECTRUM Service objects that have not been associated with IT Services. SPECTRUM service objects created by the Spectrum Service Setup tool are placed in this BPV. The Unknown Spectrum Services object is defined with Severity Propagation turned off and as an unmanaged object so that any alerting objects do not affect other objects. NSM - SPECTRUM Root Cause Integration Page 14

18 Spectrum Services This BPV contains all of the Spectrum Service objects associated with IT Services. Move Spectrum Service objects from the Unknown Spectrum Services BPV before you attach them to an IT Service. From there you will copy them to the Spectrum IT Service BPV under the appropriate IT Service. Related IT Services This is a Dynamic BPV which will display all IT Service objects that have a Spectrum Service attached to them. This object is useful for determining all IT Services that have been affected by a Spectrum Service alarm. NSM - SPECTRUM Root Cause Integration Page 15

19 SPECTRUM Services can be added to the MDB using the SPECTRUM Services Setup wizard, as described in Using SPECTRUM Service Setup Wizard, or manually, as described in Manually Creating SPECTRUM Service Objects. Using SPECTRUM Service Setup Wizard Note: In order for this program to function, permission must be granted to the NSM machine and user ID as documented in the Spectrum Security & User Maintenance (document #2602) and other SPECTRUM documentation. The SPECTRUM Service Setup Wizard, which is included in the SPECTRUM Root Cause Integration package, enables you to access your SpectroSERVER or DSS Location Server to import the defined SPECTRUM Services into the MDB. The tool is launched by executing the following command <Installation Directory>\bin\getspecsrvr.cmd In the initial screen select the SPECTRUM version running on the target SPECTROServer. NSM - SPECTRUM Root Cause Integration Page 16

20 In the next screen enter the name of your SpectroSERVER or Location Server if you are running a DSS environment and change the default port for the OsAgent, if required. Note: Beginning with r1.3.1, a SPECTRUM user id must be entered in the Spectrum User field. If the machine from which you are executing getspecsrvr.cmd and the SPECTRUM user do not have access defined in SPECTRUM, the utility will generate a message Bad server name or port entered. In the Spectrum User field provide a Spectrum user id which is authorized to access service models. Note: The OsAgent port is not used in SPECTRUM 9.x and higher and therefore is grayed out. SPECTRUM SERVICES SETUP will retrieve a list of servers defined to the Location Server and populate the dropdown box. Select the SpectroSERVER from which you want to extract services. NSM - SPECTRUM Root Cause Integration Page 17

21 Next, select the SPECTRUM Services that you want to add to the MDB from the left hand pane and click the > button to move those services to the right hand pane. Alternately, click the >> button to move all of them. Enter the name of the MDB where the SpectrumService objects are to be created. This is the logical name of the MDB not the database server s node name. The default is the local MDB. Use wvrepsel to determine the correct name if you are unsure. Click Commit to NSM to add the selected services to the MDB. Click Next server to return to the prior screen to select another SpectroSERVER server. Click Finish when done. NSM - SPECTRUM Root Cause Integration Page 18

22 The WorldView objects created in the MDB will be found in the Spectrum Root Cause => Unknown Spectrum Services folder. Next, use the Spectrum Service Coordinator (setitservice.cmd) to associate the Spectrum Services with your IT Services. This UI will move the service objects you choose to implement at this time to the Spectrum Services folder. It will then copy the objects to the IT Service =>SpectrumITService folder. Identify Spectrum Managed Services The installation process creates a NSM Dynamic BPV to contain the IT Services that are managed by Spectrum. A Dynamic BPV automatically collects WV objects that match certain criteria. In the case of the Related IT Services DBPV, it looks for IT Services in which the Spectrum Root Cause Instance Level Property (ILP) has been set to Yes. Any IT Service with this ILP set and which has a severity other than Normal will be copied into the DBPV. You do not need to perform any configuration on this object. Note: Spectrum Root Cause ILP is defined during the installation process. Using the SPECTRUM Service Coordinator Wizard The SPECTRUM Service Coordinator is a UI application that will link the IT Service with the SPECTRUM Service. It performs the following functions: Displays the defined IT Services Displays the defined SPECTRUM Services Moves selected SPECTRUM Services from the Unknown SPECTRUM Services BPV to the SPECTRUM Services BPV Executes samp_manage.exe to create the SpectrumITService class object under the IT Service Copies the selected SPECTRUM Services to the SpectrumITService BPV. Configure Service Management Pack (SMP) SMP must be configured to manage SPECTRUM services before you execute setitservice.cmd. To do this: Edit the %CA_TND_HOME%\SAMP\config\SAMP.dat file Locate the setting Spectrum_Managed_Services Change the setting to yes and save the file Launch the SMP Configuration wizard NSM - SPECTRUM Root Cause Integration Page 19

23 Click the Policy Pack>> button Select the SpectrumRC policy pack and click Build and Load Policy Click Next Update SpectrumService impact if desired and click Next NSM - SPECTRUM Root Cause Integration Page 20

24 Regenerate SMP cache by clicking Generate CacheList Click Next Click Save Click OK NSM - SPECTRUM Root Cause Integration Page 21

25 Execute SetITservice.cmd Launch the SPECTRUM Service Coordinator by executing the stitservice.cmd command. Once launched, select the IT Service you want to configure and then select the SPECTRUM service or services you want to associate with that IT Service. When complete, your IT Service hierarchy should look like this: IT Service \_ Monitored instances \_ Monitored instances \_ Monitored instances \_ Spectrum IT Services \_Spectrum Service \_Spectrum Service Set NSM Event Management CA_OPR_FORMAT_NODEID In order to normalize node names for messages arriving from SPECTRUM, NSM Event Management and other sources it is necessary to set the CA_OPR_FORMAT_NODEID to NONE. To do this: From Windows Start, Run execute caugui settings Click on the Event Management tab NSM - SPECTRUM Root Cause Integration Page 22

26 Locate the Format of the Node field of incoming messages entry Double click the Setting column and select NONE from the list Click Yes to confirm the change Restart Event Management to implement the change Executable Reference The following are the main executables provided in this package. Getspecsrvr.cmd Getspecsrvr.cmd launches the Spectrum Services Selector application. There are no command arguments for this command. A description of the Spectrum Services Selector can be found in Using SPECTRUM Service Setup Wizard. SetITservice.cmd SetITService.cmd launches the SPECTRUM Service Coordinator application. There are no command arguments for this command. The command must be executed on the SMP server. A description of the SPECTRUM Service Coordinator can be found in Using the SPECTRUM Service Coordinator Wizard. SSRC_redisc.exe SSRC_redisc.exe is executed by Event Management when the status of a Spectrum Service changes. SSRC_redisc.exe sets the Spectrum Service object s severity and launches rediscovery of the host machines associated with the IT Service that the Spectrum Service supports. NSM - SPECTRUM Root Cause Integration Page 23

27 The arguments are specified without an intervening space between the flag and the value, for example, -d1. The command line arguments for SSRC_redisc.exe are: -d Specify a value greater than 0 to turn on additional debug messages -s The name of the Spectrum Service. -v The new status the service. An invalid value will cause the program to terminate. The valid values for this argument are: UP OK UNKNOWN MINOR WARNING MAJOR CRITICAL DOWN WARNINGACKNOWLEDGED CRITICALACKNOWLEDGED -r The repoll interval. By default, SSRC_redisc.exe will not repoll a host if its status last changed in less than 1200 seconds. This is to preclude a host that supports multiple services from repeated rediscovery. SSRC_enc.exe SSRC_enc.exe is used to encrypt and set the MDB password in the MDBPassword registry key. The command line arguments for SSRC_enc.exe are positional and must be entered as follows: Operation Enter encrypt for this parameter Key Enter MDBPassword for the name of the registry key Password Enter the name of the new password NSM - SPECTRUM Root Cause Integration Page 24