How to avoid discovering IPV6 addresses for Windows and Unix hosts ? (284 Views)
Reply
Regular Advisor
Praveen_Shan
Posts: 111
Registered: ‎01-12-2012
Message 1 of 10 (284 Views)

How to avoid discovering IPV6 addresses for Windows and Unix hosts ?

Hello,

 

uCMDB version: 9.05 CUP 12.351

DDM Content Pack 11.08.802

 

I see a lot of Unix hosts in our test environment that have two ip addresses connected to them. One is IPV4 and the other is IPV6. How can I control the discovery process such that it disables IPV6 and finds only IPV4's ?

 

Kindly oblige.

 

Thanks,

PKS

Please use plain text.
HP Expert
Dima Gomel
Posts: 826
Registered: ‎03-09-2010
Message 2 of 10 (281 Views)

Re: How to avoid discovering IPV6 addresses for Windows and Unix hosts ?

Please check properties for IPv6 IPs and let us know what job are creating/updating those CIs.

 

Do you have IPv6 configured on the destinations?

Regards
-Dima, HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Click the KUDOS star on the left to say 'Thanks'
I'll be happy to be in touch at LinkedIn .
Please use plain text.
Regular Advisor
Praveen_Shan
Posts: 111
Registered: ‎01-12-2012
Message 3 of 10 (280 Views)

Re: How to avoid discovering IPV6 addresses for Windows and Unix hosts ?

To my knowledge, we need to go to the input TQL on the adapter(Host Resources and Applications by Shell) and set the node attribute on Ip Address CI to "IpAddressType Equal IPv4".

 

Is this good enough or do we need to do something at the script level ?

Please use plain text.
HP Expert
Dima Gomel
Posts: 826
Registered: ‎03-09-2010
Message 4 of 10 (276 Views)

Re: How to avoid discovering IPV6 addresses for Windows and Unix hosts ?

This will prevent running of HR and App by Shell from running on IPv6 IPs, but won't prevent creation of IP CIs.

Regards
-Dima, HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Click the KUDOS star on the left to say 'Thanks'
I'll be happy to be in touch at LinkedIn .
Please use plain text.
Regular Advisor
Praveen_Shan
Posts: 111
Registered: ‎01-12-2012
Message 5 of 10 (274 Views)

Re: How to avoid discovering IPV6 addresses for Windows and Unix hosts ?

Dima,

 

I just checked the IPV6 IPs and they were created and updated by Host Connection by Shell job.

So, the node attribute changes should be done to this Input TQL, correct ?

 

I am pretty sure this was already in place but I think it might have changed after a recent patching of CP 11.

Please use plain text.
HP Expert
Dima Gomel
Posts: 826
Registered: ‎03-09-2010
Message 6 of 10 (261 Views)

Re: How to avoid discovering IPV6 addresses for Windows and Unix hosts ?

Hi,

You can't avoid creation of IPv6 when the interfaces are on destination without changing of the script.

At the same time other jobs shouldn't be triggered on discovered IPv6 unless you have custom trigger/input TQLs.

In OTTB it's done by restriciting IPs to "IP Probe Name" attribute not equal "null".

In other words, any IP which isn't part of IP ranges shouldn't be triggered.

 

 

Regards
-Dima, HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Click the KUDOS star on the left to say 'Thanks'
I'll be happy to be in touch at LinkedIn .
Please use plain text.
Regular Advisor
Praveen_Shan
Posts: 111
Registered: ‎01-12-2012
Message 7 of 10 (258 Views)

Re: How to avoid discovering IPV6 addresses for Windows and Unix hosts ?

Thanks Dima, for all the answers.

I'll check all the custom TQL's that we have and see what best can be done.

Please use plain text.
HP Expert
Dima Gomel
Posts: 826
Registered: ‎03-09-2010
Message 8 of 10 (256 Views)

Re: How to avoid discovering IPV6 addresses for Windows and Unix hosts ?

For your convinience, I'm adding OTTB TQL for HC by Shell job from CP11.08.802.

Regards
-Dima, HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Click the KUDOS star on the left to say 'Thanks'
I'll be happy to be in touch at LinkedIn .
Please use plain text.
Regular Advisor
Praveen_Shan
Posts: 111
Registered: ‎01-12-2012
Message 9 of 10 (249 Views)

Re: How to avoid discovering IPV6 addresses for Windows and Unix hosts ?

Thanks again!

But now, another question popped up:

 

The attachment in your previous post shows the OOTB Trigger TQL for Host Connection by Shell and we have the exact same thing.

 

I was actually referring to the Input Query on the adapter. Please take a look at the screen shots attached. One's for HR&A by Shell and the other one for HC by Shell.

Please use plain text.
HP Expert
Dima Gomel
Posts: 826
Registered: ‎03-09-2010
Message 10 of 10 (241 Views)

Re: How to avoid discovering IPV6 addresses for Windows and Unix hosts ?

UCMDB has two consiquent filter Input TQL-> Trigger TQL.

In case all your queries are OTTB, please open Trigger TQL, press calculate and right click on IP -> show instances.

It shoudn't contain IPv6 CI.

 

OTTB input TQLs has no restiction for IPv6...

Regards
-Dima, HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Click the KUDOS star on the left to say 'Thanks'
I'll be happy to be in touch at LinkedIn .
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation