Hello,
One thing you need to keep in mind with when using the "SNMP ipAddress" field is that it will only work for single interface devices. If you are trying to get a list of multiple interface devices you will need to approach this differently.
One method using nvUtil is (which can be used for creating a smartset):
# nvUtil e '(IN_SUBNET 19.39.0.0)'
The only problem with this is that it is based on a calculation of IP Address and Subnet Mask to determine which hosts match. If there are incorrect Subnet Masks results could be incorrect. This calculation thing also means that you would need to have more than one entry if you were looking addresses in a contiguous set of subnets... eg. ((IN_SUBNET 192.168.254.0) && (IN_SUBNET 192.168.254.1))
If you are just wanting to get this list from the command line or a script, a .format file with the nvdbformat command could be used:
###########################################################
#
# NVDBFormat interface listing .format file
# Modified version of interfaces.format
#
# Usage: nvdbformat -f <filename>
#
# If this file were named 'interfaces.format' it would be processed by:
#
# nvdbformat -f interfaces.format
#
###########################################################
SELECTRULE:isInterface=TRUE
SELECTRULE:IP Address~19.39.*.*
SELECTFIELD:1:TopM Node ID:Selection Name
SELECTFIELD:2:IP Address
SELECTFIELD:3:IP Subnet Mask
SELECTFIELD:4:IP Status
#
GROUPBY:1:TopM Node ID:Selection Name
SORTBY:1:IP Address
#
HEADER:Interface List by Selection Name
HEADER:Selection Name,IP Address,IP Subnet Mask,IP Status
#
OUTPUT:${1},${2},${3},${4}
#
With some modification and cron, this could be used to create/maintain a smartset with a list of nodes that meet fit.
# run nvdbformat command to get Selection Name list
# run nvUtil command to create a smartset with the selection names: nvUtil a "Smartset Name" "description" "(IN '"host1" "host2"')"
Hope this helps.
Regards,
Greg Keetch
IT Specialist (Advisor), Network Services
Network Management Tools Specialist
Information Technology Services Americas (ITSA), Global Services, IBM Canada
Leslie Clark <lclark AT us.ibm DOT com>
Leslie Clark <lclark AT us.ibm DOT com>
Sent by: nv-l-bounces AT lists.ca.ibm DOT com
05/22/2007 07:54 AM
Please respond to
Tivoli NetView Discussions <nv-l AT lists.ca.ibm DOT com> |
|
|
Look at the object info for a node. Nodes don't have a field 'IP Address'. That's an attribute of an interface. So you are getting a list of Selection Names of interfaces or Networks.
Nodes do have a field called 'SNMP ipAddress'.
Cordially,
Leslie A. Clark
IT Services Specialist, Network Mgmt
Information Technology Services Americas
IBM Global Services
(248) 552-4968 Voicemail, Fax, Pager
"Kain, Becki \(B.\)" <bkain1 AT ford DOT com>
Sent by: nv-l-bounces AT lists.ca.ibm DOT com
05/22/2007 09:51 AM
Please respond to
Tivoli NetView Discussions <nv-l AT lists.ca.ibm DOT com> |
|
To | "Tivoli NetView Discussions" <nv-l AT lists.ca.ibm DOT com> |
cc | |
Subject | [NV-L] Making a smart set based on ip's |
|
I tried making a smartset based on ip's:
nvUtil e '("IP Address" ~ "19.39.*.*")'
But the results that I get are not nodes but something else:
sdg100344q3b1.itek.ford.com:19.39.25.75
sdg100g3tfmb1.itek.ford.com:19.39.40.103
SEP001380AD917D.itek.ford.com:19.39.50.110
How do I make a smartset, based on a range of ip's, AND get actual nodes in it? Thanks in advance
_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
|