Jayashree Arunkumar
ca.com
Initial IP Discovery
ovstart starts ovspmd
ovspmd starts netmon
netmon queries NNM management station’s SNMP
agent for configuration information which includes
– IP Address
– Subnet mask
– Default route
– ARP Cache
4. For each IP Address found
– Ping it to make sure it is alive
– Make an SNMP query to determine SNMP version
supported
– Use SNMP to retrieve configuration information
5. Repeat step 4 until no new IP addresses are found
Slide I - 2 ca.com
netmon Polling of a new node
Slide I - 3 ca.com
Setting Object Attributes and Symbol type
Slide I - 4 ca.com
Initial IPX Discovery
Slide I - 5 ca.com
MAC Layer Discovery and Monitoring
Slide I - 6 ca.com
Discovery of HTTP nodes
Slide I - 7 ca.com
Extended Topology Discovery
Heterogeneous Layer 2 switched network
management (LAN & WAN)
Targeted views for quickly identifying root
cause
– View switched environment and complex
relationships between devices
– View network services such as OSPF and VLAN
Enhances NNM views: neighbor, station,
internet
Superior root-cause analysis via improved
path detection
Slide I - 8 ca.com
What extended topology discovers
“Layer-two” connectivity
VLAN information
ATM information
OSPF information
Slide I - 9 ca.com
Troubleshooting IP Discovery
Slide I - 10 ca.com
Name Resolution problems
Slide I - 11 ca.com
Tracing and Logging Operations
Slide I - 12 ca.com
Configuring Extended Discovery
Slide I - 13 ca.com
Using loadhosts
Slide I - 14 ca.com
Seeding Initial IP Discovery
By default, netmon only discovers nodes on the local
subnet only
A seed file is a simple ASCII file containing a list of IP
addresses, preferably gateways and routers
All networks connected to the seed file entries are
discovered exclusively
Seed file typically contains
– IP address of management station
– IP address of default router
– IP address in other networks ( routers, file servers etc.)
Slide I - 15 ca.com
Using a seed file
Slide I - 16 ca.com
Redo Initial Discovery
Stop NNM
Remove Openview databases
– cd %OV_DB%
– remove \install_dir\databases\openview
Remove all events
– remove \install_dir\databases\eventdb
Re-register fields
– ovstart ovwdb
– ovw -fields
Start NNM
Slide I - 17 ca.com
Useful netmon Discovery options
-J Speed up discovery
-r Query the routing table
-Q SNMP-queue-length
-S Discover secondary addresses
-w Control discovery of software
loopback addresses
Slide I - 18 ca.com
Discovery filters
Slide I - 19 ca.com
Configuring netmon.noDiscover
Slide I - 20 ca.com
Discovery Filter Evaluation
Network and Segment objects are created after
discovery filtering
If a node passes, all interfaces associated with that
node also pass
If an interface passes, the node associated with the
interface passes, including all other interfaces
If you want to filter a node completely, you must filter
the node object and all the interfaces associated with
that node
filter file
– \install_dir\conf\C\filters
Slide I - 21 ca.com
Example Discovery Filter
Filters {
CMCLan “CMC Local LAN devices”
{ “IP Address” ~ 192.168.44.* }
}
Slide I - 22 ca.com
Applying a Discovery Filter
Slide I - 23 ca.com
netmon.noDiscover vs Discovery
Filter
Discovery filter queries a node and then
evaluates whether the node should be
included in the database
netmon.noDiscover does not even query the
device if IP address matches – saves network
bandwidth and speeds up discovery
For certain types of devices (routers, switches
etc.) the only option is to use Discovery filter
Slide I - 24 ca.com