Hegde, Ramesh (CMS | 21 Apr 18:05 2015

RHEL 7: SNMP V3 trap does not work anymore with cimserver

Hello All,


We are trying to explore snmp V3 traps on RHEL 7. We are getting following error from cimserver side.


“Failed to deliver an indication: Snmp Indication Handler failed to send the trap: USM unknown security name (no such user exists)”


When we drill down further and check the function on net-snmp i.e usm_get_user_from_list returns null and hence the comparison falls.


Do you know how to populate this list and which file does it read to populate this list?


Mainly we want to know how this list gets  populated and does it use snmpd by any chance and use any snmpd.conf file?


Currently we use wbemexec and xml file to subscribe and provide all security name, auth key and priv key in the same xml file.


I also see that on RHEL 7 there are some fixes around this usm user in the change log i.e


net-snmp-5.7.2/ChangeLog:      - make usm_get_user_from_list() handle a bogus initial user flag.

net-snmp-5.7.2/ChangeLog:      - use usm_get_user_from_list to ask not to return the default initial user.


This has created any regression on snmpv3 trap functionality in cimserver?



Ramesh Hegde
Project Manager- ACE OCMP/USP-M

rameshh <at> hp.com
T +91 80 338 66486
M +91 8197863555
Hewlett-Packard Company
No.192, Whitefield Road
Bangalore, Karnataka, 560048



Follow us on:          


Attachment (smime.p7s): application/pkcs7-signature, 8 KiB
Chang CrazyRushStar | 7 Apr 13:02 2015

Do you plan to come out a OpenPegasus "C" clinet interface?

There has be a OpenPegasus C++ Client Interface, but it is not enough for widely using C users. Do you have plan to create a C client Interface library? Or there are some others client library which highly complies with OpenPegasus server for C language users.


Karl Schopmeyer | 1 Apr 14:23 2015

OpenPegasus 2.14.1 Released

OpenPegasus 2.14.1 has been released specifically to bypass a problem in 
the ssl certificates and testing with 2.14.0.

This release only includes a fix for that bug (test certificates expired 
shortly after 2.14.0 release) but should be used in place of 2.14.0 if 
any of the OpenPegasus testing tools are to be used.

This release is defined:

     On the OpenPegasus wiki at:

And is available on the OpenPegasus web site at


and also through the wiki at:


The source RPM will be released shortly
Karl Schopmeyer
OpenPegasus Project Lead

Khushboo Sancheti | 31 Mar 19:25 2015

How can one disable the creation of TEST, SENT and RECV logs of Pegasus?


Is there a switch to disable the creation of TEST, SENT and RECV log created by Open Pegasus? Is there a configuration variable to change the location where these are created?

I am using Pegasus 2.13.


Karl Schopmeyer | 31 Mar 15:55 2015

Pegasus 2.14.0 Release - Warning

Shortly after the version 2.14.0 release a problem was created in the 
OpenPegasus tests in that the ssl certificate used for any tests 
involving ssl expired.  Since this blocks much testing, we are going to 
release 2.14.1 immediatly to fix this issue.

Karl Schopmeyer
OpenPegasus Project Lead

Karl Schopmeyer | 28 Mar 16:46 2015

The CVS Head of tree Open For Commits

The CVS head of tree (OpenPegasus 2.15) is now open for new commits.  It 
has been updated to include the new version and marked as

The same procedure as previous releases will be followed for new commits:

1. Documented in bugs
2. Bugs voted and marked approved if votes are positive
3. Only bugs with + votes to be committed.

The planning for this next version can be followed, commented on, etc. at


Karl Schopmeyer
Project Lead

Karl Schopmeyer | 28 Mar 16:40 2015

OpenPegasus Version 2.14.0 Released

OpenPegasus 2.14.0 has been formally released and is available for use.

This release includes a number of extensions, the primary of which is 
the inclusion of the
CIM/XML pull operations defined by the DMTF for the CIM/XML protocol.  
The full list of changes for this release are documented in the 
ReleaseNotes and the OpenPegasus bugzilla

For more details on the release, please use the Release Notes that are:

1. In the root directory of the source code
2. In the Release Table at 
3. On the OpenPegasus Wiki at 
4. Documented as OpenPegasus PEP 368.

The source code is available at on the OpenPegasus web page at:

2 Through the OpenPegasus WIKI on the ReleaseStatus Page 
3. Through the OpenPegasus CVS using the CVS tag RELEASE_2_14_0

The source RPM will also be made available shortly and will be announced 

Karl Schopmeyer
Project Lead

Karl Schopmeyer | 24 Mar 17:06 2015

OpenPegasus 2.14 branch created.

Effective immediatly, in preperation for the release of OpenPegasus 
2.14.0, the RELEASE_2_14 pegasus branch has been created.

This means that any future patches for OpenPegasus 2.14 must be put into 
this branch and, further, no patches will be inserted into
the branch without a prior patch for 2.15 (the CVS head of tree).


Karl Schopmeyer | 14 Mar 15:04 2015

Pegasus 2.14 Source Freeze (Release Canidate 1) tag RELEASE_2_14_0-RC1 has been set

The RC1 tag (RELEASE_2_14_0-RC1) has been set in the head of tree for 
OpenPegasus indicating that the source code is frozen.

 From this point to the release:

1. Only critical bugs will be committed and those must have at least 2 
votes (not that documentation bugs are excepted)

The remaining steps are:

1. Complete cho test
2. Complete release notes review
3. Create the 2.14 branch
4. Set release tag

Karl Schopmeyer
Project Lean

abhishek gupta | 12 Mar 11:16 2015

Error "invalid hostname" for Invoke method call when we use IPv6 address.

Hello All,

We are using 2.12.0 version of Tog-Pegasus in Rhel6.




When we query from Java client, enumerations works well with the IPv6 address.  But for invoke method call we receive "invalid hostname" from the tog-pegasus. This invoke method works well with the IPv4 address.

We did specify zone id for link local address.

failed with CIM_ERR_INVALID_PARAMETER: malformed object name: [fe80:0:0:0:224:e8ff:fe4d:d169%11], reason:"invalid hostname"


Please let us know if we missed anything?



Harshitkumar Jain | 23 Jan 09:34 2015

CIMPLE tool Key properties comparison issue

Hi Team,


We are using CIMPLE tool version 2.0.24 on CentOS7 linux platform. We are facing below issue related to key properties uniqueness amongst instances of a class.


The implementation of the "insert" function in case of and "Instance_MAP" is giving us issues.


inline size_t Instance_Map<CLASS>::insert(CLASS* instance)


It returns -1 "Duplicate instance" whenever we create and insert 2 or more instances into the map with different key properties.


The string check seems to be verifying only the first few characters of the key string.


For instance, the insert function returns (-1), if value used for a key property is "Setting:1 and "Setting:2". However the same implementation works if we use keys like "1:Setting" "2:Setting"


Has anybody faced this issue earlier or is this a known issue?



thanks in advance,


The information contained in this e-mail message and in any attachments/annexure/appendices is confidential to the
recipient and may contain privileged information. If you are not the intended recipient, please notify the
sender and delete the message along with any attachments/annexure/appendices. You should not disclose,
copy or otherwise use the information contained in the message or any annexure. Any views expressed in this e-mail
are those of the individual sender except where the sender specifically states them to be the views of 
Toshiba Software India Pvt. Ltd. (TSIP),Bangalore.
Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by Toshiba Software India Pvt. Ltd, for any loss or damage arising in any way from its use.