network.pl fail on selftest

Unanswered Question
Jan 30th, 2008
User Badges:

Hi,


Problem on my Ciscoworks LMS 2.6 is that I cannot discover devices. SNMP settings and discovery settings are already configured correctly. When I did the selftest I noticed that the network.pl has failed. It says "Default servers are not available. FAIL nslookup failed." How can I resolve this issue?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
miheg Wed, 01/30/2008 - 02:34
User Badges:
  • Gold, 750 points or more

How do you know you discovery settings are correct if you can't discover?


So lets assume snmp is OK. How about CDP and your seed devices?


Cheers,


Michel

benjo.rulloda Wed, 01/30/2008 - 05:51
User Badges:

Hi Michel,


SNMP string defined in Ciscoworks is ok. CDP is also enabled for all devices and seed device configured was the core switch. I have already ping all devices on the command prompt and they all responded. I noticed that the Local Area Connection icon on the lower right of the screen is not blinking to indicate device discovery activity. That's why I tried to conduct a selftest on Ciscoworks and came upon with a result that network.pl failed.


Any thoughts on what seems to be wrong?


Regards,

Benjo

yjdabear Wed, 01/30/2008 - 05:55
User Badges:
  • Gold, 750 points or more

"Default servers are not available." is an error from the nslookup commmand, meaning your specified default DNS servers were not reachable from your CiscoWorks server. Can you nslookup on the command line (Windows or Solaris), outside CiscoWorks?


benjo.rulloda Wed, 01/30/2008 - 06:02
User Badges:

I did not define any DNS servers on Ciscoworks, just statically assign IP address on it. The setup is purely LAN and no internet connection on it. any more suggestions?

yjdabear Wed, 01/30/2008 - 06:15
User Badges:
  • Gold, 750 points or more

Not in CiscoWorks, but on the host OS when you (or someone else) built this CiscoWorks server. The question still remains: Can you nslookup on the server's command line (Windows or Solaris)?


Edit: Another possibility is:


"This is due to Nslookup being unable to perform a reverse lookup on the IP address of the DNS server. When NSLookup starts, it attempts do a reverse lookup of the IP address of the DNS server. If this fails, NSlookup gives the message noted above, which is somewhat misleading. The solution is to either install a reverse lookup zone for your workstations or to ignore the message."



Actions

This Discussion