Sie sind auf Seite 1von 11

NNM Troubleshooting

ca.com
Troubleshooting Discovery

 After initial discovery, opening NNM


takes a long time
– Could be a DNS problem
– Use checkDNS tool
C:> install_dir\support\checkDNS.ovpl –v

Slide I - 2 ca.com
Troubleshooting Discovery

 NNM Discovery found zero nodes


– Verify netmon is running – ovstatus –c
– Ensure network devices are responding to ping
and snmp requests – ping, snmpwalk/ snmpget
– Ensure that SNMP agent is installed and running
on the gateway device
– Use loadhosts for loading specific nodes
– Check if SNMP Emanate Master agent service /
snmpdm is running

Slide I - 3 ca.com
Troubleshooting Discovery

 All or most of the map is wrong


– Check if the subnet mask of key routers
is wrong

Slide I - 4 ca.com
Troubleshooting Discovery

 Whole IP networks are missing


– Check to see if there are routers which
are not accessible by SNMP
– Check if the management domain is
limited

Slide I - 5 ca.com
Troubleshooting Discovery

 Router shows up as a host


– Check SNMP configuration of router
– Check if router has more than one
interface configured and IP Forwarding
set

Slide I - 6 ca.com
Troubleshooting Discovery

 Some routers are missing


– Check to see if missing routers are
‘backup’ routers
– If ‘backup’ router
 Manually add the router in the map
 Use Fault  Network Connectivity  Ping to get the status of
the router
 Use Fault  Network Connectivity  Poll Node to get the
information that netmon needs to place the device on map

Slide I - 7 ca.com
Troubleshooting Discovery

 An SNMP device shows up on the


map as a non-SNMP node
– Problem may be that all of netmon’s
SNMP requests to a node failed
– SNMP requests can fail if transport is
very busy, as SNMP runs over UDP
– Most likely reason is SNMP Community
string mismatch

Slide I - 8 ca.com
Troubleshooting Discovery

 A host shows up as a router


– Possible if the host has multiple interfaces and
IP Forwarding enabled
 IP Forwarding configuration (.1.3.6.1.2.1.4.1)
 Number of interfaces (.1.3.6.1.2.1.2.1)
– Check for the same sysObjectID using Find by
Attribute
– If same behaviour exists for all the objects, edit
oid_to_type to use M parameter to designate the
device as a multi-homed host and not a router

Slide I - 9 ca.com
Troubleshooting Data warehouse

 Historical records – log files in \install_dir\logs


folder
– embeddedDbconf.log
– externalDbconf.log
– ovdbcheck.log
– ovdwtrend.log, ovdwtopo.log etc.
 Run ovdbcheck to start/stop embedded
database to validate if it is working properly
 Backup all data, recreate an Empty database

Slide I - 10 ca.com
Troubleshooting backup

 Check for adequate file space


 Run as administrator
 Check for timeouts on
ovpause/ovresume
 Check for disk space errors

Slide I - 11 ca.com

Das könnte Ihnen auch gefallen