Skip navigation
1 2 Previous Next

siddharth mahabal's Blog

17 posts
Siddharth Mahabal

Perfmon

Posted by Siddharth Mahabal Employee Aug 7, 2014
Share This:

When you first open Performance Monitor (perfmon), you see the following:

clip_image001

Let's briefly go through each one and talk about what they do.

Performance

At the very top level "Performance" gives you an overview of your systems memory usage, network usage, disk usage, etc.  You can right click on "Performance" and connect to another computer to view a remote computers performance statistics. (NOTE: Should add brief comments about what is required in order to remotely connect to another machine…)

Monitoring Tools

From the Monitoring Tools icon you can right click and launch the Resource Monitor.  Resource Monitor is another powerful tool that can help you see how your system resources are being used.  You also have the ability to launch the System Reliability Monitor.  This utility allows you to see information about software updates and installations.  You can also see critical events that occurred and on what day those events occurred.  Finally, you can see all of the problem reports that have been sent from your computer by clicking on the "View all problem reports" link at the bottom of the window.

Performance Monitor

The Performance Monitor is primarily for viewing real time statistics.  By default only one counter is selected; the %Processor Time counter.  However you can add additional counters by clicking on the green plus sign.  This will allow you to monitor any counters you wish in real time.

While you can see all of the performance counters you like here, the real power of Performance Monitor is found in its ability to capture performance metrics over an elapsed period of time.  Capturing data over a period of time allows you to see trends and these trends are what are most useful for determining the overall performance of your system.  To capture this data, you can create what are called "Data Collector Sets".

Share This:

Whenever We Check for Exchange KM Configuration , use this as a reference

 

User has the following explicit rights:

- Act as part of the operating system (SeTcbPrivilege)

- Replace a process level token (SeAssignPrimaryTokenPrivilege)

- Log on locally (SeInteractiveLogonRight)

- Log on as a service (SeServiceLogonRight)

 

 

User has the following inherited rights:

- Adjust memory quotas for a process (SeIncreaseQuotaPrivilege)

- Add workstations to domain (SeMachineAccountPrivilege)

- Manage auditing and security log (SeSecurityPrivilege)

- Take ownership of files or other objects (SeTakeOwnershipPrivilege)

- Load and unload device drivers (SeLoadDriverPrivilege)

- Profile system performance (SeSystemProfilePrivilege)

- Change the system time (SeSystemtimePrivilege)

- Profile single process (SeProfileSingleProcessPrivilege)

- Increase scheduling priority (SeIncreaseBasePriorityPrivilege)

- Create a pagefile (SeCreatePagefilePrivilege)

- Back up files and directories (SeBackupPrivilege)

- Restore files and directories (SeRestorePrivilege)

- Shut down the system (SeShutdownPrivilege)

- Debug programs (SeDebugPrivilege)

- Modify firmware environment values (SeSystemEnvironmentPrivilege)

- Bypass traverse checking (SeChangeNotifyPrivilege)

- Force shutdown from a remote system (SeRemoteShutdownPrivilege)

- Remove computer from docking station (SeUndockPrivilege)

- Enable computer and user accounts to be trusted for delegation (SeEnableDelegationPrivilege)

- Perform volume maintenance tasks (SeManageVolumePrivilege)

- Impersonate a client after authentication (SeImpersonatePrivilege)

- Create global objects (SeCreateGlobalPrivilege)

- Increase a process working set (SeIncreaseWorkingSetPrivilege)

- Change the time zone (SeTimeZonePrivilege)

- Create symbolic links (SeCreateSymbolicLinkPrivilege)

 

 

Summary of required system account role privileges:

- SeTcbPrivilege privilege is granted

- SeIncreaseQuotaPrivilege privilege is granted

- SeAssignPrimaryTokenPrivilege privilege is granted

Share This:

BPPM IS.JPG

Share This:

The AdDnsDcLdapSrvRecordExists parameter is in alarm
I don’t understand the meaning of the annotation point (see the attached file) : what does “no matching DC LDAP SRV records for <server_name> were found while querying the default DNS server for _ldap._tcp.dc._msds.cdm.cm-cic.fr” mean ?

 

>>AdDnsDcLdapSrvRecordExists
Determines if an LDAP SRV (service) record
matching the host name of the domain controller is
registered with the DNS server. The KM make the
following query to the default DNS server:
_ldap._tcp.dc._msdcs.<fully qualified domain name>

Share This:

>>With the PATROL for LOG KM, there is a limit of 2 Gb for the log file to be monitored. There is no specific documentation that mentions a limit for the LOG file monitoring with Express Solution, but you should be able to monitor a log file of upto 2 Gb

 

>> Size limit details for the Express for LOG KM -->

 

There is no specific limitation for Express for LOG KM Solution. The only limitation that exists is size of buffer: On each cycle the Log solution can read max of 98304 bytes. Those will be read from the last position.It means, on big files which are updated with large data, it will take time to read all the files.This number is configurable and can be set to higher value, but then it can cause performance issues.

Share This:

>>Search for Adding an adapter for BMC PATROL using the automated workflow. Following are the details for the same -->

 

Configuring PATROL Agents with the Integration Service

Automated workflow enables the PATROL Agent to automatically connect to the

Integration Service, register itself, and start sending performance data to the

Integration Service. The PATROL Agent is added to the default profile called

"_SA_DEFAULT_" in the Integration Service. The Integration Service uses the

Staging Adapter (a component of the Integration Service) to accept inbound

connections from the PATROL Agents. This default Staging Adapter profile is

created during the Integration Service startup (if not already available). You cannot

remove this profile. For added flexibility and scalability, the Integration Service

configures multiple Staging Adapter profiles and provides the ability to run multiple

Staging Adapter instances.

 

Importing monitor types and creating an adapter instance

Automated workflow imports monitor types and creates an adapter instance

whenever a remote agent configured with the Integration Service is added to the

BMC ProactiveNet Server. Once the remote BMC ProactiveNet Agent is added to the

server, all the application classes that are loaded in the PATROL Agents are added to

the server. All instances pertaining to these application classes are made part of the

newly created adapter instance. This adapter instance polls for performance data

more frequently compared to the earlier instance.

Deleting the remote BMC ProactiveNet Agent also deletes the associated adapter

instance. This is true even for PATROL Agents earlier than version 3.8.50, once they

are configured manually with the Integration Service. However, all information

pertaining to application classes (such as KPI, graph by default, and so on) may not

be synchronized.

 

Features of automated workflow

Automated workflow:

¦ Automatically creates a profile of type SA_ADAPTER in the Integration Service

(only for PATROL Agents version 3.8.50 or later)

¦ Imports monitor types

¦ Creates adapter instances

¦ Discovers and creates monitor instances

¦ Imports new KMs as BMC ProactiveNet monitor types every minute (by default)

¦ Re-imports changes to KMs every minute (by default)

 

Limitations

¦ You cannot use a local BMC ProactiveNet Agent installed on a BMC ProactiveNet

Server.

¦ Automated workflow imports all the monitors loaded in the PATROL Agent as

there is no option to select specific monitors.

¦ Automated workflow imports all devices and monitor instances without any filter

option. You can edit the adapter instance after its creation to change the monitor

type selection and/or apply filters. Once you edit the adapter instance, it is

converted to the manual workflow.

¦ It is not possible to distinguish between PATROL Adapters created manually and

those created using the automated workflow.

¦ If you have converted a manual adapter instance to automated workflow, you

cannot revert to the manual adapter instance except to edit the adapter.

¦ Automated workflow does not import thresholds automatically. You must

manually import thresholds using the pw adapter get_thresholds CLI command.

¦ If you edit the automated workflow-enabled monitor instance and change the

monitor type, fetching of the new application classes added on the PATROL

Agent will stop.

¦ You cannot enable automated workflow when you have upgraded a remote BMC

ProactiveNet Agent with Integration Service and changed the default password

but have not created an adapter instance.

¦ If multiple BMC ProactiveNet Agents connected to different Integration Services

and running on different ports are installed on the same Solaris system,

automated workflow will work only for the first agent connected to the server.

Siddharth Mahabal

WbemTest

Posted by Siddharth Mahabal Employee Jul 9, 2014
Share This:

WbemTest and see what it results.

 

 

1. Open a command prompt window [From RSM machine!], and type the following command: wbemtest.

2. Click Connect.

3. Change namespace to \\RemoteComputerToBeMonitored\root\CIMV2

4. Type user: domain\user (same username and password by which you have configured the element)

5. Type the password for the user.

6. Click Connect.

7. Click Query.

8. Type the following query: select * from win32_logicaldisk where caption='C:'

9. Now check, if it provide some results or note. Take a snapshot of this and send us.

Siddharth Mahabal

FINEST Level LOGS

Posted by Siddharth Mahabal Employee Jul 9, 2014
Share This:

How to Enable Debug for the Windows Event Log Monitor application class?

 

 

com.bmc.patrol.patsdk.lib.wmi.level=FINEST

com.bmc.patrol.windows.collectors.eventlog.level=FINEST

com.bmc.patrol.windows.collectors.eventlogc.level=FINEST

com.bmc.patrol.windows.solutions.eventlog.level=FINEST

com.bmc.patrol.windows.solutions.ParamletBase.level=FINEST

com.bmc.patrol.windows.collectors.wmi.level=FINEST

com.bmc.patrol.windows.collectors.wmic.level=FINEST

 

 

 

 

 

 

How to Enable Debug for the WMI Collector?

 

 

com.bmc.patrol.patsdk.lib.wmi.level=FINEST

com.bmc.patrol.patsdk.solutions.wmi.WmiMethodParamlet.level=FINEST

com.bmc.patrol.patsdk.solutions.wmi.WmiParamletFactory.level=FINEST

 

 

 

 

How to Enable Debug for the Perfmon Collector?

 

 

com.bmc.patrol.patsdk.lib.perfmon.level= FINEST

com.bmc.patrol.patsdk.solutions.perfmon.level= FINEST

com.bmc.patrol.patsdk.solutions.perfmon.PerfmonParamlet.level=FINEST

com.bmc.patrol.patsdk.solutions.perfmon.DiscoveryHelperParamlet.level=FINEST

 

For log monitoring issues on Unix:

 

 

com.bmc.patrol.logfiles.lib.DR2AH.LogSmb.level=FINEST

com.bmc.patrol.logfiles.lib.DR2AH.Log.level=FINEST

com.bmc.patrol.logfiles.lib.DR2AH.LogCommandShell.level=FINEST

 

 

 

 

Discovery is not able to detect application instances

For commands:

 

 

com.bmc.patrol.patsdk.solutions.commandshell.CommandshellParamlet.level=FINEST

com.bmc.patrol.patsdk.solutions.commandshell.level=FINEST

com.bmc.patrol.patsdk.solutions.commandshell.CommandshellParamletFactory.level=FINEST

 

 

 

 

For SSH

 

 

com.bmc.patrol.patsdk.lib.ssh.SshService.level=FINEST

com.bmc.patrol.patsdk.lib.ssh.SshCommandShellSession.level=FINEST

com.bmc.patrol.patsdk.lib.ssh.SshHostKeyFingerprintVerification.level=FINEST

com.bmc.patrol.patsdk.lib.ssh.SshClient.level=FINEST

Share This:

We can enable the Debug for PCM via the below options

 

debugwindow=true

debuglevel=7

 

 

The options for n are:

0 = deactivated (no messages)

1 = critical errors

2 = all errors

3 = warnings

4 = informational messages

5 = detailed messages

6 = trace messages

7 = verbose (all messages) . Please choose this.

 

 

PCM must be restarted for the changes to take effect.

Share This:

As per latest findings,

Classic Console - 3.6.00

PATROL Agent - 9.5.00

 

We observe that the PSL taks are not refreshed when executed from the Classic Console.

 

 

>>The behaviour is desired, where the task will remain open until that session is Open.

 

 

>> The Options that we have in that option are -->

 

 

You can repeat the task by doing RMB on the task symbol and selecting

repeat .

 

 

Or

 

 

else if you don't want that task you can

destroy it.

Siddharth Mahabal

Blue Screen KM

Posted by Siddharth Mahabal Employee May 8, 2014
Share This:

Configuration of the Blue Screen KM

blue screen.jpg

Share This:

>>PCC is a Reporting Utility that can be installed when you install the Patrol Agent

 

>>Once installed, the executable will be present in \BMC Software\Patrol3\bin = pcc.exe, you can run the exe from that location.

pcc.jpg

Share This:

>>Please refer to the document "BPPM Administrator Guide" = to find the information as mentioned below

>>Search for Adding an adapter for BMC PATROL using the automated workflow. Following are the details for the same -->

 

Configuring PATROL Agents with the Integration Service

Automated workflow enables the PATROL Agent to automatically connect to the

Integration Service, register itself, and start sending performance data to the

Integration Service. The PATROL Agent is added to the default profile called

"_SA_DEFAULT_" in the Integration Service. The Integration Service uses the

Staging Adapter (a component of the Integration Service) to accept inbound

connections from the PATROL Agents. This default Staging Adapter profile is

created during the Integration Service startup (if not already available). You cannot

remove this profile. For added flexibility and scalability, the Integration Service

configures multiple Staging Adapter profiles and provides the ability to run multiple

Staging Adapter instances.

 

Importing monitor types and creating an adapter instance

Automated workflow imports monitor types and creates an adapter instance

whenever a remote agent configured with the Integration Service is added to the

BMC ProactiveNet Server. Once the remote BMC ProactiveNet Agent is added to the

server, all the application classes that are loaded in the PATROL Agents are added to

the server. All instances pertaining to these application classes are made part of the

newly created adapter instance. This adapter instance polls for performance data

more frequently compared to the earlier instance.

Deleting the remote BMC ProactiveNet Agent also deletes the associated adapter

instance. This is true even for PATROL Agents earlier than version 3.8.50, once they

are configured manually with the Integration Service. However, all information

pertaining to application classes (such as KPI, graph by default, and so on) may not

be synchronized.

 

Features of automated workflow

Automated workflow:

¦ Automatically creates a profile of type SA_ADAPTER in the Integration Service

(only for PATROL Agents version 3.8.50 or later)

¦ Imports monitor types

¦ Creates adapter instances

¦ Discovers and creates monitor instances

¦ Imports new KMs as BMC ProactiveNet monitor types every minute (by default)

¦ Re-imports changes to KMs every minute (by default)

 

Limitations

¦ You cannot use a local BMC ProactiveNet Agent installed on a BMC ProactiveNet

Server.

¦ Automated workflow imports all the monitors loaded in the PATROL Agent as

there is no option to select specific monitors.

¦ Automated workflow imports all devices and monitor instances without any filter

option. You can edit the adapter instance after its creation to change the monitor

type selection and/or apply filters. Once you edit the adapter instance, it is

converted to the manual workflow.

¦ It is not possible to distinguish between PATROL Adapters created manually and

those created using the automated workflow.

¦ If you have converted a manual adapter instance to automated workflow, you

cannot revert to the manual adapter instance except to edit the adapter.

¦ Automated workflow does not import thresholds automatically. You must

manually import thresholds using the pw adapter get_thresholds CLI command.

¦ If you edit the automated workflow-enabled monitor instance and change the

monitor type, fetching of the new application classes added on the PATROL

Agent will stop.

¦ You cannot enable automated workflow when you have upgraded a remote BMC

ProactiveNet Agent with Integration Service and changed the default password

but have not created an adapter instance.

¦ If multiple BMC ProactiveNet Agents connected to different Integration Services

and running on different ports are installed on the same Solaris system,

automated workflow will work only for the first agent connected to the server.

Share This:

The steps to Configuring Cluster KM via External CLA on Windows 2008 R2 are as below:

Step 1) Setup the cluster environment

 

Step 2) Install the BMC PATROL Agent, Cluster KM, and Windows OS KM on each of the cluster node. Also install BMC PATROL Agent, Cluster KM, and Windows OS KM on another computer, which is the external CLA (This computer is outside of the Microsoft cluster environment.).

 

Note: All PATROL components (especially the Cluster KM) need to be the same version on the cluster nodes and external CLA.

 

Note: See Chapter 2 of the PATROL for Microsoft Windows Servers Getting Started guide for more information about installing the Cluster KM and Chapter 3 for configuring the Cluster KM.

 

Step 3) Install PCO-Win, PATROL Console Server, RTserver, PATROL Agent, Windows OS KM, and PCM on another server that is not a cluster node (if not already installed). If using external CLA then these PATROL components can be installed on the same computer that is the external CLA (from Step 2).

 

Step 4) Preload the Cluster KM (MCS_Load.kml) on External CLA and preload the Windows OS KM on each cluster node. The Cluster KM is dependent on the Windows OS KM and it is needed for the MCS_Performance application class. The Cluster KM is calculating performance parameters base on CPUProcessorTime parameters value of each node.

 

Step 5) From PCO console, monitor the external CLA with Cluster KM and Windows OS KM only.

 

Step 6) Configure the Cluster KM from the PCO console

 

Note: If using Cluster KM 1.7.00 or later, ensure the “Log on as a batch job” user right is granted to the Cluster KM user account as well. If using external CLA then all of the user rights (e.g. Log on Locally, Log on as a batch job, etc.) need to be granted on each of the cluster nodes and external CLA.

 

1) From PCO-Win, right click on the Microsoft Clusters - Setup application class on the external CLA

 

2) Select Knowledge Module Commands -> PATROL Admin -> Select Cluster to Monitor

 

3) Enter the information and click OK

 

4) Right click on the Microsoft Clusters application class on the external CLA and select Knowledge Module Commands -> PATROL Admin -> Maintain Account Info

 

5) Enter the information and click OK

 

6) It will monitor the cluster

 

7) If using external CLA, you do not need to push the /MCS agent configuration variables from the external CLA to the cluster nodes. This should be performed by the Cluster KM. However, you should still verify if these /MCS agent configuration variables are set correctly.

 

8) Ensure the files called MCS_DomainInclList.cfg, mcsClusterList.cfg, and mcsMonitorAgent.cfg are located in the %PATROL_HOME%\mcs directory on each of the cluster nodes in the same directory.

 

Note: The file called MCS_DomainInclList.cfg is created at the time of installation while the files called mcsClusterList.cfg and mcsMonitorAgent.cfg are created when you configure the Cluster KM. It will do automatically through remote agent. However, you should still verify if these files are created and the value are set correctly

Share This:

Log KM debug.jpg

 

LOG KM --> KM Commands --> Configure Debug