HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
StoreVirtual Storage
Showing results for 
Search instead for 
Did you mean: 

NTP Configuration Status is 'Misconfigured'

Go to solution
Occasional Contributor

NTP Configuration Status is 'Misconfigured'

2xP4500G2's, 1 vSphere OVF VSA.  All on (and current per the CMC Update Checker).


I already have the cluster's NTP setting pointed at two AD servers that they are connected to (that in turn are connected to pool.ntp.org NTP servers).


My only alarm is this:



Severity: Warning

Component: Storage System

Object Type: Configuration Check

Object Name: NTP


The Resolution section links to the 'Online Event Resolution Help' (which links to this: http://h20000.www2.hp.com/bizsupport/site/search/r4_0/jsp/search.jsp?lang=en&cc=US&pc=0&sc=2&cf=1&cm=1&cs=1&c130=1&c115=1&c110=1&c120=1&nh=10&rf=0&lkc=1&lk=1&tx=E02000203 )


And doesn't turn up any results; tossing the search term 'E02000203' into Google and Bing don't turn anything up either.


Wondering if anyone knows why it is still complaining or where in the guide(s) I can find the 'proper' NTP config so it will stop alerting.


Thanks in advance for your help!

Trusted Contributor

Re: NTP Configuration Status is 'Misconfigured'

Clear all your settings.

Close the CMC down and make sure the values are empty, sometimes they dont clear!!

Open the CMC and double check the NTP setting is empty.

Make sure you can ping the each NTP server from the nodes, you can do this by right clicking then pinging.

If you are using jumbos make sure you set the packet size to something above 1500.

If all checks out close the CMC again

Now add back your settings see if it goes away.


Occasional Contributor

Re: NTP Configuration Status is 'Misconfigured'

Immediately after putting the settings in, it had an alert that it was misconfigured (after connecting to both) - but after it sat for a bit, it cleared up.

Thanks for the help!