Anonymous_User Absent Member.
Absent Member.
1020 views

Generate relationships based on element properties in SCM


Hi,

We are currently working on a PoC at a customer and ran into a small
problem.
At the customer we are using DI as a structure for the SCM job and
AppManager as the source.
The structure elements holds a ip address as a property, on the source
elements from AM there also a property containing an ip address.

We can easily join the elements using SCM but we would also like to
create relationships based on properties on a structure and source
element.
This can be done by using dependency generators, but as they only work
with alarms and not element properties that creates a problem.

The manual states that you can create your own dependency consumers in a
SCM job. Any one have any experience using element properties to
generate dependencies?

Example.

Structure element: Server A -> Holds property of ip address:
192.168.1.1
Source element Server B -> Holds a property of ip address neighbour:
192.168.1.1

We would like to create a dependency between Server A and Server B based
on the properties described above.

Thanks,

Sebastian Kliber


--
skliber
------------------------------------------------------------------------
skliber's Profile: https://forums.netiq.com/member.php?userid=5238
View this thread: https://forums.netiq.com/showthread.php?t=48801

Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Generate relationships based on element properties in SCM


I have only used alarms with SCM dependency generator. If you look at
the screen in SCM, it states alarms or elements. It has both examples.


--
tisenberg
------------------------------------------------------------------------
tisenberg's Profile: https://forums.netiq.com/member.php?userid=1851
View this thread: https://forums.netiq.com/showthread.php?t=48801

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Generate relationships based on element properties in SCM


Yes, the SCM allows you to use either alarm or element properties for
origin or termination. But at least one of the sides needs to have an
alarm field to build the relationship. You can't use an element property
for both origin as well as termination. But this did give me an idea. As
the elements from AM will contain alarms, these alarms can hold the IP
of the affected element. This can then be matched against the property
of the destionation element. I will give it a try and let you know if it
works.

"-If no dependencies are available, create dependencies using alarm
information from any source.
Matching an alarm property with an element property establishes element
relationships that
previously were unknown.-"

Thanks,

Seba


--
skliber
------------------------------------------------------------------------
skliber's Profile: https://forums.netiq.com/member.php?userid=5238
View this thread: https://forums.netiq.com/showthread.php?t=48801

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Generate relationships based on element properties in SCM


Tried some different scenarios in SCM. Turns out both the origin and
termination requires alarms for SCM to pick up the properties.
If I specify only a element property in either as the origin or
termination the SCM job doesn't pic them up.
In this example I have set a alarm property called "hostname" for the
origin and a element property called "neighbour" for the termination
element.
The debug result gives the following: "Pass 1: sourceid = Element1,
targetid = null".
Verifying by debug that there is actually a property called neighbour,
with a value.

Using the same configuration but with alarms providing both origin and
termination works fine.
There seems to be a problem for the SCM to pic up element properties
while generating the dependencies.

Thanks,

Sebastian


--
skliber
------------------------------------------------------------------------
skliber's Profile: https://forums.netiq.com/member.php?userid=5238
View this thread: https://forums.netiq.com/showthread.php?t=48801

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.