- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- Re: SMS log - incorrect name resolution
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
SMS log - incorrect name resolution
Hi all.
I am facing a strange problem - in the logs of the IP address is assigned the wrong name.
For example IP 10.150.116.17 in DNS (nslookup from SMS server):
But in smartlog:
On PC with smartconsole:
Why? 😞
- Labels:
-
Logging
-
Monitoring
-
SmartConsole
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the answer,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is your dns suffix correct?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It was not set up for SMS. I added it to the configuration, updated the logs - nothing has changed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is that IP defined as an object in your management, by chance?
Because that's what will take precedence over DNS.
The other suggestion would be to execute a cprestart on the management.
It won't impact gateways, but it will restart the various processes on the management server.
Otherwise, you may need a TAC case to assist.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, there is no such object on the SMS. I also checked this, but forgot to post a screenshot. I will try to restart the processes on the server. If nothing helps, I will contact support. Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @EVSolovyev,
I undestand this is old post, however I'm facing the same issue. Did you find the root cause of this behavior ?
Bye,
Luca
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've currently got a ticket raised with our support provider for the exact same issue. I'd appreciate it if you could let me know if you find a resolution to this. I will do the same 😊
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@AaronCP Do you have solution from TAC?
Maybe it will help you:
SMS
cp $INDEXERDIR/conf/log_indexer_settings.conf $INDEXERDIR/conf/log_indexer_settings.conf.ORIGINAL
vi $INDEXERDIR/conf/log_indexer_settings.conf
Add the time_for_clearing_dns_cache attribute with desired value (in hours).
Note: Configure the value of this interval to be the same as the DHCP re-assignment policy.
Example:
################ Advance settings ########################
:time_for_clearing_dns_cache (8)
:index_directory ()
# Location of the indexed database
:min_disk_space (10240)
# Minimum free disk space to keep. In MB
Save the file and exit from Vi editor.
stopIndexer
startIndexer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I’m facing the same issue. Did you find the solution of this behavior?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good afternoon. I don't remember exactly, it's been a long time, but it seems that the problem was that there was such an object with the wrong name in SMC.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the answer,
