The current nslookup functionality uses external services and cannot see or resolve internal system names. We are running "ping- a [ip]" commands by hand to get name resolution on internal systems.
Hi rduvall,
Have you configured your LEM Manager network configuration using a static configuration? It is key to ensure you complete the network configuration and provide at least one DNS server for your local network. You can do this from the command line.
Hi,
I see your point for WhoIS, but NSLookup and Traceroute tools use your configured DNS Server on the LEM Manager. I have validated this on my own installation, by querying several devices on my local domain and domain names external to my organisation and they return the expected results. Can you confirm that you have your LEM manager configured to use the correct DNS servers (i.e. a local DNS server with a forward lookup zone in your network).
Here is a Traceroute to bbc.co.uk
External NSLookup
Lookup to a sever on my training LAN
Traceroute to a server on my Training LAN
Hi,
Yes there is.
1) Open the Console in Hyper-V/ vSphere client or SSH to the appliance and login to the cmc account (view advanced configuration if from the former)
cmc> appliance
cmc::acm# viewnetconfig
Would you like to view the (b)rief network configuration or (a)dvanced? <B/a> a
Look for:
DNS Server Information:
search xxxx.local
nameserver 192.168.xxx.
Locally Configured Hosts:
127.0.0.1 localhost localhost.localdomain db
192.168.xxx.xxx lemhostname
Take a note of every setting. If it is not correct, you should take a note of it then re-run the netconfig command and specify the settings (you will need to set everything again).
Go to Manage --> Appliance in the GUI console. Under the Properties pane, pick "Settings." Look for the Current Default Agent.
Is that a valid hostname or IP? Is that Agent on-line? Does that Agent have the right network configuration? The LEM sends all those Explore commands to the Command Agent, and has the Agent execute them. This way, the LEM and the web console aren't trying to execute strange network queries, but if the command Agent is off-line/unreachable/isn't allowed to run nslookup or traceroute/doesn't have the right network configuration, then they won't work.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.