NTP time sync

I recently found among 40 controllers 7 are not in sync, what might be the probable cause? I repeated the symmetricom installation procedure twice but the same controllers are not in sync!! Is thr any method to sync each controller?

10 Replies

  • It tends to take time for nodes to re-sync to the master time server.
     
    Can you see the symmetricom time server’s IP address listed in the node’s NTP diagnostics? Or is it pointing to another node?
     
    From: bobgally [mailto:bounce-bobgally@community.emerson.com]
    Sent: Tuesday, October 30, 2012 5:29 PM
    To: DeltaV@community.emerson.com
    Subject: [EE365 DeltaV Track] NTP time sync
     

    I recently found among 40 controllers 7 are not in sync, what might be the probable cause? I repeated the symmetricom installation procedure twice but the same controllers are not in sync!! Is thr any method to sync each controller?

  • In reply to AdrianOffield:

    i cannot see it in the diagnostics for those 7 controllers for rest of them i can see symmetricom ip address. Thats what my question about can i sync individual controller?

  • Download setup data is the only way I know of getting them to see the IP address of the NTP server, are you sure your networks are 100%? Can you multicast ping the controllers from the PRO+ using diag?
     
    Are these controllers in a separate building, connected to a separate set of switches? Are they behind a DeltaV Firewall?
     
    Until a successful connection is made to the NTP server (from the perspective of the controller), it won’t display the NTP server IP in diagnostics.
     
    From: bobgally [mailto:bounce-bobgally@community.emerson.com]
    Sent: Wednesday, October 31, 2012 7:10 AM
    To: DeltaV@community.emerson.com
    Subject: RE: [EE365 DeltaV Track] NTP time sync
     

    i cannot see it in the diagnostics for those 7 controllers for rest of them i can see symmetricom ip address. Thats what my question about can i sync individual controller?

  • In reply to AdrianOffield:

    While digging i found few problems with those 7 controllers.

    1.Firmware version are different for those 7 (10.3.1.3611).

    2.When i tried to flash them in controller upgrade utility , i cannot find those 7 controllers in drop down list.

    3.When i view revision info controller upgrade utility i found that these controllers are in INVALID state, utility is not recognizing them as MD controllers.

  • Hmm, that sounds like a bit of a problem, are they redundant controllers?
     
    Make sure you can really see them across your network, does telnet work from the PRO+ to those controllers?
     
    From: bobgally [mailto:bounce-bobgally@community.emerson.com]
    Sent: Wednesday, October 31, 2012 8:18 AM
    To: DeltaV@community.emerson.com
    Subject: RE: [EE365 DeltaV Track] NTP time sync
     

    While digging i found few problems with those 7 controllers.

    1.Firmware version are different for those 7 (10.3.1.3611).

    2.When i tried to flash them in controller upgrade utility , i cannot find those 7 controllers in drop down list.

    3.When i view revision info controller upgrade utility i found that these controllers are in INVALID state, utility is not recognizing them as MD controllers.

  • It sounds like you have your DeltaV Primary ACN cable reversed with your DeltaV Secondary ACN cable on those controllers. Try swapping the Ethernet.

    Duane

    On Oct 31, 2012, at 12:17 AM, "bobgally" <bounce-bobgally@community.emerson.com> wrote:

    While digging i found few problems with those 7 controllers.

    1.Firmware version are different for those 7 (10.3.1.3611).

    2.When i tried to flash them in controller upgrade utility , i cannot find those 7 controllers in drop down list.

    3.When i view revision info controller upgrade utility i found that these controllers are in INVALID state, utility is not recognizing them as MD controllers.

  • Before swapping Ethernet, try to PING these controllers from within DeltaV Diagnostics and see if you get the correct response or not.

    Duane

    On Oct 31, 2012, at 5:16 AM, "Harnish, Duane [PROCESS/PSS/AUS]" <Duane.Harnish@emerson.com> wrote:

    It sounds like you have your DeltaV Primary ACN cable reversed with your DeltaV Secondary ACN cable on those controllers. Try swapping the Ethernet.

    Duane

    On Oct 31, 2012, at 12:17 AM, "bobgally" <bounce-bobgally@community.emerson.com> wrote:

    While digging i found few problems with those 7 controllers.

    1.Firmware version are different for those 7 (10.3.1.3611).

    2.When i tried to flash them in controller upgrade utility , i cannot find those 7 controllers in drop down list.

    3.When i view revision info controller upgrade utility i found that these controllers are in INVALID state, utility is not recognizing them as MD controllers.

  • In reply to txharnish:

    I tried to reverse the ACN ethernet cables and saw in the diagnostics that communications went bad so i revert the as it was before.

    I tried TCP/IP ping, TELNET for these controllers from all the engineering stations but it is not pinging and not able to connect to telnet.

  • In reply to bobgally:

    We need to not be doing tech support on this board.  Please refer this question to the Global Service Center for help. (if you have not already done that).  We often have already delt with this type of issue and can provide immediate help.

  • In reply to BobHuba:

    Thanks BobHuba for your suggestion i found the solution!!!! there was something wrong with the black box (IPD) jus rotated the keys and kept in same position as it was bfore!!! Now i cam upgrade firmware and NTP is also syncing.

    Thanks again  AdrianOffield, txharnish