Comware

Hello,

I have an issue with some 5130 stacks. When i configure the NTP directly with IP, it works fine.

But when i use the full fqdn the ntp service doesn't seem to resolve it, it shows 0.0.0.0. And my dns is working, when i ping the full name, i get the ip.

exemple :

Is there a way to force the ntp to use the working name ? (i know i can workaround the issue by typing the ip directly, but i'd prefer to work with the dns name)

Thanks

Hi,

This seems to be a strange and erratic behavior as the 'ntp-service unicast-server' command should (according the command reference guide) accept both IP and FQDN. Are you sure that the issue is with DNS, e.g. if you set the IP address of this particular NTP2 server then it will work? I see that NTP2 wasn't reachable by ICMP, so just double-checking we don't miss anything obvious here... 

BTW, what is the s/w version your 5130 are running?

Hello,

Thanks for the answer,  when i do the config with the ip directly, it works fine. See the second line here :

My version is this one : 

Boot image: flash:/5130ei-cmw710-boot-r3507p02.bin
Boot image version: 7.1.070, Release 3507P02
  Compiled Sep 15 2021 11:00:00
System image: flash:/5130ei-cmw710-system-r3507p02.bin
System image version: 7.1.070, Release 3507P02
  Compiled Sep 15 2021 11:00:00

I'm replying to myself if anyone come across this subject.

The behaviour is strange, i have different stacks on the same network that will resolve the dns on the ntp configuration and another not. I have the exact same firmware and hardware versions with different behaviour.

Probably a bug. I did the workaround by setting directly the IP Adress of our multiple ntp servers.

Hi,

Sorry for the late reply, I was on vacation trying to minimize my exposure to IT and social media :)

That is very, very strange as an obvious bug in the firmware would affect all the stacks.. Have you checked the DNS settings on the affected and non-affected stacks? The command is 'display dns server'? Also, you can verify the DNS cache and name resolution for certain hosts by 'display dns host' command. From the 'ping' output it seems like DNS resolving works fine, but still it's worth to be checked. That '0.0.0.0' in the 'display ntp sessions' output points us to the name resolving issue, otherwise you would see an IP address of the server there... Another point - you can try to sniff the traffic on the DNS server to see if the affected switch really sends DNS queries for the NTP server. And the last thing to check - 'display current | inc dns' - do you see any difference in DNS commands between working and non-working 5130s?

TBH, your issue seems to be a very good opportunity to contact Aruba TAC as it definitely requires deep analysis that can hardly be done in the format of forum posts :(

------------------------------
Ivan Bondar
------------------------------