Showing posts with label MP. Show all posts
Showing posts with label MP. Show all posts

Wednesday, 30 March 2016

Disk Performance dashboard view is empty in SCOM 2012 R2

Disk Performance dashboard view is empty in SCOM 2012 R2


  • Disk Performance Dashboard View is empty. This is because the rule to see this data is not enabled. In order to populate this view, please enable the rules.
In 2012 Monitoring MP:
  • Microsoft.Windows.Server.6.2.OperatingSystem.TotalPercentDPCTime.Collection
  • Microsoft.Windows.Server.6.2.OperatingSystem.TotalPercentInterruptTime.Collection
  • Microsoft.Windows.Server.6.2.Processor.PercentDPCTime.Collection
  • Microsoft.Windows.Server.6.2.Processor.PercentInterruptTime.Collection
In 2012 R2 Monitoring MP:
  • Microsoft.Windows.Server.2012.R2.OperatingSystem.TotalPercentDPCTime.Collection
  • Microsoft.Windows.Server.2012.R2.OperatingSystem.TotalPercentInterruptTime.Collection

Known Issues and Troubleshooting for SSAS 2008 MP

Known Issues and Troubleshooting for SSAS 2008 MP


  • Users who had the previous version of SSAS management pack installed should remove Microsoft SQL Server Analysis Services Visualization Library (version 1.0.5.0) manually.

Issue: The library has become a generic component and a new management pack that contains the functionally is released. Since it is impossible to remove the obsolete pack automatically during installation process, users have to do it manually.
Resolution: Remove Microsoft SQL Server Analysis Services Visualization Library (version 1.0.5.0).

  • If the last SSAS database or partition is deleted the object will be still displayed in SCOM as if it exists.

Issue: Current implementation of SSAS database and partition discoveries incorrectly resolves the situation when the last SSAS database or partition is deleted. In the case the information regarding the deleted object is still visible to the user.
Resolution: There is no resolution. The error may be addressed in future releases of the management pack. A user can either add a SSAS database/partition or remove the SSAS instance.

  • ‘An error occurred during execution of a SSAS 2008 MP managed module’ alert rule generates extra alerts for virtual nodes.

Issue: Current implementation of the rule uses ‘SSAS 2008 Seed’ as a target. Virtual nodes have mutual seed, as a result each time an error occurs on a physical machine an alert is automatically reported from every virtual entity which is currently associated with that physical machine.
Resolution: There is no resolution. The error may be addressed in future releases of the management pack.

  • Event 6200 “Analysis Services connection failed” error is reported into Operations Manager event log.

Issue: Instance discovery workflows of SSAS management pack require connection to a SSAS instance, if the connection is not provided the workflows report about encountered problems. Such an issue may occur when the instance is stopped during execution of a workflow, or when the instance is incorrectly configured.
Resolution: Set ‘Threadpool\Query\MaxThreads’ property to a value of less than or equal to two times the number of processors on the server.

  • Operations Consoles crash when user simultaneously opens two or more Instance/Database Summary dashboards on the same machine.

Issue: It is allowed to run two or more Operations Consoles on the same machine, but opening summary dashboards in more than one of them leads to a crash of all consoles. The issue is not observed in Web-consoles.
Resolution: There is no resolution.

  • Operations Console crashes if user who is browsing Instance Summary dashboard selects a SSAS Instance which has already been deleted.

Issue: The action cause a crash of Operations Console.
Resolution: Open Operation console again.

  • “Health Service State” monitor is in critical state and Health Service restarts periodically.

Issue: By default the threshold of “Monitoring Host Private Bytes Threshold Monitor” from the System Management Pack is 300 Mbytes. “MonitoringHost.exe” process may exceed the threshold and the “Health Service State” monitor may start the recovery procedure, when SSAS 2008 Monitoring Pack is collecting information about a large number of objects (more than 50 SSAS databases or 1500 partitions per server).
Resolution: Override the threshold of the “Monitoring Host Private Bytes Threshold Monitor” or reduce the number of objects being monitored by disabling discovery of partition objects.

  • Event 6200 “Category does not exist” (source – “SSAS 2008 MP”) is being generated on 64-bit operating systems running 32-bit SSAS instances.

Issue: SSAS doesn’t register performance counters properly when a 32-bit SSAS instance is installed on a 64-bit OS. In this case required performance counters cannot be found by Monitoring Pack and SSAS 2008 MP is unable to run properly.
Resolution: This issue cannot be resolved, WoW64 is not supported. It is highly recommended to use either 32-bit SSAS instances on 32-bit OS or 64-bit SSAS instances on 64-bit OS.

  • Health Service and Monitoring Host processes consume too much memory on systems running SSAS 2008 instances with large number of databases

Issue: On agent-managed systems that host one or more instance of SQL Server 2008 Analysis Services with large number of databases and/or partitions, “Health Service” and “Monitoring Host” processes may consume too much memory.
Resolution: It is not recommended to monitor more than 50 SSAS Databases on a single server. It is recommended to disable SSAS partitions discovery if you have more than 1500 partitions on a single server.

  • SSAS 2008 Summary Dashboards for Instances, Databases and Partitions display all active alerts if nothing is selected in the navigation widget (leftmost widget on the dashboard).

Issue: Dashboards display all active alerts if nothing is selected in the navigation widget (leftmost widget on the dashboard).
Resolution: Make sure that at least one Instance, Database or Partition is selected in the navigation widget.

  • WMI errors may occur when SQL Server AS 2008/2008 R2 and SQL Server AS 2012 are installed on the same server.

Issue: Modules can throw an error during WMI query.
Resolution: Update SQL Server 2008/2008 R2 with the latest service pack.

  • Partition Storage Free Space Monitor may generate too many alerts.

Issue: The monitor may generate a lot of alerts if database default storage folder and partition storage folder are sharing the same drive.
Resolution: Disable the monitor for all partitions which are sharing the same drive with database storage folder.

  • SSAS Seed object cannot be discovered if SQL Server 2008 Express Edition and SQL Server 2008 are installed on the same server.

Issue: SSAS 2008 Monitoring Pack can throw a WMI error during Seed object discovery.
Resolution: Update SQL Server 2008/2008 R2 with the latest service pack or disable Seed object discovery for a given server if that server is not running an Instance of SQL Server 2008 Analysis Services.

  • SSAS 2008 Monitoring Pack generates an alert: “An error occurred during execution of a SSAS 2008 MP managed module”.

Issue: Alert “An Error occurred during execution of a SSAS 2008 MP managed module” can be found in global “Active Alerts” view.
Resolution: This alert is generated if SSAS 2008 Monitoring Pack cannot execute one of workflows due to unknown issue. Examine alert message and alert context to determine the root cause.

  • SSAS 2008 Monitoring Pack may register Errors in the event log during installation of a new instance of SQL Server Analysis Services.

Issue: SSAS 2008 Monitoring Pack may generate a lot of errors in event log during installation of a new instance of SQL Server Analysis Services.
Resolution: The issue occurs because Monitoring Pack cannot get all required properties from the registry and WMI during installation process. Once the installation process is completed, the Monitoring Pack will be able to operate properly.

  • SQL Server 2008 Analysis Services reports incorrect value for Total and Low memory limit performance counters.

Issue: SQL Server Analysis Services may report incorrect values for Total and Low memory limit performance counters after reconfiguration.
Resolution: SQL Server Analysis Services doesn’t apply new configuration values immediately. SSAS service should be restarted to apply new settings.

  • SSAS 2008 Monitoring Pack generates an alert: “Could not find a part of the path to configuration file 'msmdsrv.ini'”

Issue: SSAS 2008 Monitoring Pack reports an error in the Event log and generates an alert “Could not find a part of the path to configuration file 'msmdsrv.ini'”. The issue occurs during cluster failover.
Resolution: There is no resolution. The issue may occur when monitoring workflow is trying to collect information during cluster failover. Once the failover is completed, the Monitoring Pack will be able to operate properly.

  • SSAS 2008 Monitoring Pack may not collect OS performance counters with localized names

Issue: SSAS 2008 Monitoring Pack may not collect OS performance counters with localized names.
Resolution: Workaround: set English display language for user accounts associated with SSAS Discovery and Monitoring Run AS Profiles. Also apply English as display language for system accounts.

Monday, 8 February 2016

Dell EqualLogic Storage MP Suite for SCOM v 6.0 supports PS 6610 and Firmware 8.1.x

Dell EqualLogic Storage MP Suite for SCOM v 6.0


  • The Dell EqualLogic Storage Management Pack Suite v6.0 enables System Center 2012 R2 Operations Manager, System Center 2012 SP1 Operations Manager, System Center 2012 Operations Manager and System Center Operations Manager 2007 R2 to Discover, Monitor and accurately depict the status of Dell EqualLogic PS Arrays on a defined network segment.
  • The new version supports EqualLogic devices PS6610.
  • Latest version also support Firmwares 8.1.x



Installation Steps by Step:

  • Download the file to a directory on your hard drive. The file downloaded is a self-extracting executable.
  • Go to the location where you downloaded the file and double-click the executable to unzip the files. The default extraction folder is " C:\Program Files\Dell Management Packs\EqualLogic Storage Management Suite\6.0 ". You may select a different location for file extraction by editing the path.
  • Launch the Dell_EqualLogic_Management_Pack_Suite_x86_x64.exe file from the extracted location. The welcome screen for Dell EqualLogic Management Pack is displayed.
  • Click Next. The license agreement is displayed.
  • To continue the installation, accept the license terms after reading them, and click Next.
  • Click Change (if required) to change the default installation folder and click Next. The Ready to Install the Program screen is displayed.
  •  Click Install. The Installing Dell EqualLogic Storage Management Pack progress screen is displayed.
  • Click Finish on the Install Shield Wizard Completed screen.

Citrix Aquires Comtrade Managemet pack

Citrix Aquires Comtrade Managemet pack

  • Citrix Product is one of the most important product that is monitored via SCOM
  • Almost 50 % of desktops and app are Citrix Apps in any environment.
  • Comtrade was the only reliable MP for Citrix across the world for SCOM.
  • Citrix has now aquired Comtrade MP which means we will get it lke HP mp's free of cost .

Read More:-->

Tuesday, 25 August 2015

Cool Dashboards in recent SQL 2012 MP

Cool Dashboard in recent SQL 2012 MP


  • Microsoft has released a pretty cool dashboard in recent SQL 2012 MP.
  • It gives awesome dashbaord view for the team to Monitoring and know you database perforamnce from single console
  • To Download latest MP click here --> Download


Monday, 29 June 2015

Lync 2013 MP Install Step by Step SCOM 2012 R2

Lync 2013 MP Install Step by Step:


  • Lync has taken over the entire communication channel.
  • Gone are the VOIP IP Cisco Phones which use to sit on your Desk.
  • Today everything is going to Mobile and Lync is the best and cheapest option from Micrososft.
  • So almost all enterprise have decided to migrate to Lync. So much is the Lync affects today that, we need a realtime monitoring more critical then outlook.
  • So Microsoft has worked on it very hard and have brought the realtime Monitoring using SCOM for Lync 2013.
Microsoft Lync Server 2013 includes two SCOM management packs:

  • The Component and User Management Pack (Microsoft.LS.2013.Monitoring.ComponentAndUser.mp):
  • This MP Monitors Lync Server issues recorded in event logs, registered by performance counters, or logged in the call detail records (CDR) or the Quality of Experience (QoE) databases.

Active Monitoring Pack (Microsoft.LS.2013.Monitoring.ActiveMonitoring.mp):

  • This MP proactively tests key Lync Server components such as logging on to the system, exchanging instant messages, or making calls to a phone located on the public switched telephone network (PSTN). These tests are conducted using the Lync Server synthetic transaction cmdlets. 

Example:

Test-CsIM: cmdlet is used to simulate an instant messaging conversation between a pair of test users. If this simulated messaging conversation fails an alert will be generated.

Steps to Install MP:

  • Download the files Microsoft.LS.2013.Monitoring.ActiveMonitoring.mp and Microsoft.LS.2013.Monitoring.ComponentAndUser.mp.
  • In System Center Operations Manager, click Administration.In the Administration pane, right-click Management Packs, and then click Import Management Packs.
  • In the Select Management Packs dialog box, click Add, and then click Add from disk.
  • In the Online Catalog Connection dialog box, click Cancel to prevent Operations Manager from going online to see if any dependencies exist for the Lync Server management packs. If you are using System Center Operations Manager 2012, click No.
  • In the Select Management Packs to import dialog box, locate and select the files Microsoft.LS.2013.Monitoring.ActiveMonitoring.mp and Microsoft.LS.2013.Monitoring.ComponentAndUser.mp and then click Open. To select multiple files in the dialog box, click the first file, hold down the Ctrl key and then click the second file.
  • In the Select Management Packs dialog box, click Install. If you get an error message and installation fails, that typically means that the management pack files are in a folder protected by the Windows User Account Control. If this occurs, copy the files to a different folder and then restart the import and installation process.
  • In the Select Management Packs dialog box, click Close. Note that the import and installation process might require several minutes to complete.

Wednesday, 10 June 2015

New features in Veeam V7 MP for SCOM 2012 R2

New features in Veeam V7 MP for SCOM 2012 R2


Support for Hyper-V:

With Veeam MP v7, you can monitor health and performance of both Microsoft Hyper-V
and VMware vSphere environments. Now Hyper-V administrators can get the same great
monitoring, alerting, advanced reporting and unique dashboards that Veeam provides for
vSphere.

Heatmap Dashboard:



Easy to access live data from any object in your Hyper-V or vSphere environment with incontext dashboards and drill-down capabilities. Veeam widgets work in tandem with dashboards to give you instant visualization of the metrics that matter most to you.

Capacity planning for hybrid cloud:



Veeam Management Pack takes the guesswork out of planning resources to run your virtual workloads in the cloud. Capacity planning for both Microsoft Azure and for VMware vCloud Hybrid Service first analyzes your on-premises virtual workloads and then provides recommendations for the required cloud IaaS resources.

Sunday, 26 April 2015

Oracle MP for SCOM 2012 R2

Oracle MP for SCOM 2012 R2:


  • Oracle is one of the Widely used databases in the world. They are proven for there robustness in transaction databases and can easily scale through Peta bytes of data for Datawharehousing.
  • SCOM is the enterprise monitoring tool used to monitor the Infrastructure and leads the Gartner Monitoring Quadrant for many years.
  • Oracle has released a free Connector which you can download and install and intergrate with SCOM.
  • Features Include: 
     
    -
    Bi-directional exchange of alerts between Microsoft SCOM and Enterprise Manager
    -
    Automatic synchronization of alert state in Microsoft SCOM with the state of alert in Oracle Enterprise Manager (and vice-versa)
    -
    Webservices based communication
    -
    Out-of-box mapping of Oracle Enterprise Manger alert severity to SCOM alert severity
    -
    Ability to customize severity mapping between Enterprise Manager alert and SCOM event
  • You can see live demo on how it works by clicking here --> click here
  • You can download the connector here --> Click here

Saturday, 25 April 2015

HP latest Management Pack for Blade Systems and Proliant Servers - Step by Step Installation steps

HP latest Management Pack for Blade Systems and Proliant Servers - Step by Step Installation steps:

  • HP has released the latest MP for monitoring the Blade and Proliant server
  • Following are the list of MP:
  • HP BladeSystem Management Pack (v 2.1)
  • HP ProLiant Agentless Management Pack (v 3.1)
  • HP ProLiant Linux Management Pack (v 3.1)
  • HP ProLiant PRO Management Pack (v 2.1)
  • HP ProLiant Server Management Pack (v 2.2)
  • HP ProLiant VMware Management Pack (v 3.1) 
  • You can download it from the here --> Click here

Following are the Components that are important in this MP:
  • HP management packs
  • HP Device Monitor Console (DMC)
  • HP Device Monitor Service(DMS)
  • HP Custom Data Manager(CDM)

HP management Packs:
              I suggest you install the HP Blade System Management Pack and the HP Proliant Server Management Pack. These should be enought to monitor all the Servers. Other are just some additional addon.

HP Device Monitor Console (DMC):
The HP Device Monitor Console (DMC) provides the user interface for connecting to the HP Device
Monitor Service (DMS) to add or remove devices supported by management packs that use the 
DMS. 

So you need to Install DMC first. You can install on any management server.
If you are already having older version called as HP enterprise manager, then Device Console replaces it.Just install the new DMC and it will automatically upgrade.

Then install the Above MP and everything will be discovered and start working.





Wednesday, 22 April 2015

Exchange 2010 MP not raising alerts after upgrading from SCOM 2007 to SCOM 2012 R2

Exchange 2010 MP not raising alerts after upgrading from SCOM 2007 to SCOM 2012 R2


  • Recently we upgraded from SCOM 2007 to SCOM 2012, after upgrade we also migrated the MP's.
  • Everything seems to work fine and after couple of days we got a call from Exchange team that they are not receiving Exchange 2010 related alerts.
  • Exchange 2010 raises alerts based on correlation engine. So Correlation Engine decides when to raise an alert.
  • So we immediately went and check on the RMS emulator server where the correlation engine was installed.
  • We checked the "Application Logs" and there is lot of  Event ID 717 logged.
  • When further investigated we found that the Exchange Correlation Auto alert resolution feature is failing because of which you see this Event ID 717.
  • Looks like Exchange 2010 Correlation Engine is no longer compatible with SCOM 2012.
  • To resolve this 
  • We uninstalled the Exchange Correlation engine from Management Server (RMS emulator).
  • We Installed Exchange Correlation engine on normal system which is not a Management Server.
  • Then Stopped the Microsoft Exchange Monitoring Correlation service and Copied SCOM 2007 R2 SDK binaries into the Correlation Engine install directory %\Program Files\Microsoft\Exchange Server\v14\Bin. 
  • Microsoft.EnterpriseManagement.OperationsManager.Common.dll
  • Microsoft.EnterpriseManagement.OperationsManager.dll
  • MomBidLdr.dll
  • Start the Microsoft Exchange Monitoring Correlation and the alerts started flowing again.