DiscoScope. I made changes, is that what is blocking an IP address in discovery?
kcstone 0600021BUE Visits (7241)
With IBM Tivoli Network Manager if a scopeless discovery is not used the DiscoScope configuration file can be very large. It can contain inclusions and exclusions. How can I tell if an IP address should pass through the DiscoScope and be discovered?
First create a new test stitcher. You don't have to name it after me.
Place it in $PRE
I'm saving this to TestScopeKen.stch.
Leave the mask at 255, because you are checking only a single IP address, the 192.168.0.10
I recommend testing this when a discovery is finished. At that time your ncp_disco process should be at debug 4, or you can use kill -usr2 to bump the process to debug 4.
In one window, start a tail on that trace file in $NCH
[root@nc9053115085 precision]# tail -f ncp_
In another window, go into your -service disco and insert your stitcher.
[root@server bin]# pwd
Now go back to your first window.
If the output is true, then this IP would successful pass through the DiscoScope file. If the return is false, then either there is an exclusion in the DiscoScope file, or perhaps the wrong subnet mask is in the DiscoScope file.
Simply edit this Test stitcher to test other IP addresses.