Users Guide

Troubleshooting Your Application | Troubleshooting
OMNM 6.5.3 User Guide 703
branch. Navigate to ENTITY-MIB entPhysicalTable details and export/save this branch.
Attach the exported files to e-mail to support, or to a trouble ticket.
The following describe additional discovery issues.
HTTP Authentication
Often, an HTTP session with devices that support it exchanges data with the device after discovery.
This process fails if the HTTP Authentication information is incorrect. Create HTTP
authentications that match your devices’ in the Authentications portlet and use it in discovery.
Device O/S Overrides
The device driver installed must support the Operation System version on that device. Verify the
equipment’s firmware and operating systems are among those supported. Supported firmware and
operating systems appear listed in the release notes, or in
Manage > Show Versions .
Example: Override driver-unsupported operating systems for the Juniper devices in /owareapps/
juniper/lib/juniper.properties.
Change
com.dorado.juniper.supported.OS.dc.default.max
This revision does not support new features. Other device drivers have similar override
mechanisms.
If devices appear in Managed Resources as Discovered Entities, rather than specific vendors’
devices. This can mean the following:
• The equipment’s driver is not installed.
• The driver installed but not seeded to database.
Workaround: Run ocpinstall -s on a
command line.
• Monitored devices must be configured to connect and send SNMP traps to the element
management system.
If your system discovers only top level equipment, this can mean the following:
• Devices do not have components (interfaces, ports, and so on).
• An incorrect telnet/SSH authentication can have an incorrect password or no enable
password.
Workaround: You can right-click and edit the equipment with this problem to add
the telnet/SSH authentication. Make sure you also add a management interface, then resync
the device.
Backup/Restore/Deploy
Failures of backup/restore capabilities often stem from failures in the external FTP/TFTP server.
This means the FTP/TFTP server is offline, blocked by a firewall or incorrectly configured. Check
in the File Server Manager to correct this. Also, on such servers, FTP and TFTP server must share a
directory, and the directory must have all permissions to permit these servers to write, read and
delete temporary files.
If deploying firmware fails with the following symptoms:
• Selecting Deploy does nothing.
• The FTP/TFTP File Server status is Disabled.
Workaround: Back up the device first to validate it is connected with the FTP server.