Archive for April, 2011

NTCMD Discovery on Windows 2008 R2 Nodes

As of uCMDB 9.03, CUP1, Host Resources and Applications discovery will fail if executed against Windows 2008 R2 nodes with the NTCMD protocol.

xCmd v1.01 for NT4/2000 – executes commands remotely
Freeware! 2001 Zoltan Csizmadia
Connecting to remote service … Failed to start remote service
Couldn’t start remote service
Failed with error code:5
Access is denied.
Remote service executable is deleted.

To overcome this, a local administrator user needs to be created on each 2008 R2 host (admin privilege will not work).  Create a OS user as built in user and set the registry as per below:

To disable UAC remote restrictions, follow these steps:

  1. Click Start, click Run, type regedit, and then press ENTER.
  2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  3. If the LocalAccountTokenFilterPolicy registry entry does not exist, follow these steps:
    • On the Edit menu, point to New, and then click DWORD Value.
    • Type LocalAccountTokenFilterPolicy, and then press ENTER.
  4. Right-click LocalAccountTokenFilterPolicy, and then click Modify.
  5. In the Value data box, type 1, and then click OK.
  6. Exit Registry Editor.

For more information, please visit:
support.microsoft.com
support.openview.hp.com

Fragmented MSSQL uCMDB Tables

Run this command as regular select statement from table, for example:

select * from sys.dm_db_index_physical_stats (DB_ID('Database_Name_Here'), object_id('Table_Name_Here'), NULL, NULL, 'SAMPLED')

The Avg_fragmentation_in_percent column returned by sys.dm_db_index_physical_stats is the logical and extent fragmentation of the index.

For more information about sys.dm_db_index_physical_stats, see Microsoft SQL Server 2005 Books Online at:
link.

Handling Fragmentation

The table column Avg_fragmentation_in_percent returned by sys.dm_db_index_physical_stats reflects the degree of fragmentation per index. Based on this value, you can determine whether to handle the fragmentation and which method to use in handling it.

Use the following rough guidelines to determine the best method to correct
the fragmentation:

  • Between 5% and 30%. Use the ALTER INDEX REORGANIZE command to reorganize the index. Index reorganization is always executed online.
  • Greater than 30%. Use the ALTER INDEX REBUILD command to rebuild the index. Index rebuilding can be executed online or offline. Rebuild the indexes online to achieve the availability similar to that of the Reorganize option.

Very low levels of fragmentation (less than 5%) should not be addressed by either of these commands due to the negligible benefit gained from removing such a small amount of fragmentation.

For more information on defragmenting indexes, refer to "Reorganizing and Rebuilding Indexes" under Designing and Implementing Structured Storage in SQL Server Books Online (link).

Pattern Model Bug Workaround – Reusing Deleted Names

There exists a bug that does not allow you to create a new model with a name that was previously used and in deleted pattern model. What we observe is if the model is deleted, the TQL remains.  If the TQL is deleted first, both the model and TQL are deleted. However, in either case, a related job remains in the Scheduler that will as a result re-create the model/tql on its next scheduled run.

The real issue is that the current "delete function" does not actually delete a pattern model name/ucmdb_id value from the database.  As of 9.03, there is only the following workaround:

1)  In SQL Server Management 2008, run the following Query:

select CMDB_ID, A_SCHEDULER_JOBNAME from CDM_SCHEDULER_JOB_1

The output correlates the pattern model name to a hex value.  With the hex value, the JMX console can be used to delete the object.

Note: When copying the hex from the DB query, remove the "0x", otherwise the JMX console will not recognize the hex value.

2)  Go to JMX console [http://:8080/jmx-console], and login with credentials (default: sysadmin/sysadmin).

3)  Click on UCMDB:service=ModelServices – under UCMDB, and then Click on removeCMDBObject.

4)  Enter the following:

customerID: 1
objectID: <your hex value>

5)  Click Invoke.  Done.

UPDATE: 04-19-2011

This Bug will be addressed in the uCMDB 9.03, CUP2 patch, slated for release by June, 2011.

ADM and CMDB – Part Two

Evelyn Hubbert, Forrester Research, runs through her research on application dependency mapping, the trends in the market and how ADM connects with CMDB.

 

HP Software Introduces BSM 9 – Whiteboarding Session

www.hp.com/go/bsm – BSM 9 redefines IT operations by enabling IT teams to efficiently and effectively manage the performance & availability SLA's of today's fast-changing virtualized and cloud-based services.

Return top