VideoXpert: How to setup the CMG / VXS to sync with an NTP server (NTP client setup)

Issue

The VideoXpert equipment needs to sync to an external time source (i.e. SM5200, VideoXpert Accessory Server, GPS clock).

Product Line

Pelco Video Management

Environment

VideoXpert CMG v1.12
VideoXpert VXS v1.12

Cause

Improper setup can cause devices to display a wide range of symptoms including the wrong time on the overlay, connect failed messages and failure to record.

Resolution

NTP Setup:

  1. If needed, download and install Meinberg NTP on the CMG or VXS.

    Note: Current units shipped with v1.12 have Meinberg pre installed. If this is the case, edit the ntp.conf file to match the screenshot in Step 12. Otherwise proceed with the installation steps below.
     
  2. Right click the installer and select Run as administrator.
  3. Click I Agree.
  4. Click Next.
  5. Click Next.
  6. Select Create an initial configuration file with the following settings.
  7. Under You can specify up to 9 NTP servers, type in the IP Address of the Accessory Server or Virtual IP of the CMG's if in a dual core environment.
  8. Uncheck Use fast initial sync mode.
  9. Check Add local clock as a last resort reference.
  10. Click Next.
  11. When prompted to review the config file click Yes.
  12. Edit the file (C:\Program Files (x86)\NTP\etc\ntp.conf) to match the below.

    A (#) needs to be placed in front of server 127.127.1.0
    A (#) needs to be placed in front of fudge 127.127.1.0 stratum 12
    Under  Use specific NTP servers, it should display the IP address of the SM5200, VideoXpert Accessory Server, or the VIP if running in dual core environment . There should NOT be a (#) in front of this line.


     
  13. Save and close the file.
  14. Select Use SYSTEM account.
  15. Click Next.
  16. Click Finish.
     

Validation:

  1. Validate the CMG / VXS is syncing with the NTP device (Start > Apps > Meinberg > Quick NTP status).
  2. Any change made to the ntp.conf file will require the service to be restarted (Start > Apps > Meinberg > Restart NTP Service).
  3. There should be an (*) next the the IP address of the NTP device as shown below. If the service was just started or restarted it may take up 15 minutes for the (*) to appear.

Note: At some point after configuration, the NTP server software on the cores and accessory server may show a truncated host name or alias, rather than the NTP server's IP address.  When this occurs, the local "hosts" file will contain the hostname/alias and IP address can be verified using the following process:

  1. Open a command promp window on the core
  2. Use the following command to change to Meinberg's installation directory (note the double quotes due to spaces in the path:
    cd \"program files (x86)"\ntp\bin
  3. Check NTP server status using the following command:
    ntpq -p
  4. Look up the displayed host name in the hosts file (replace with the text displayed in the ntpq -p command):
    type c:\windows\system32\drivers\etc\hosts | find ""
    the "|" character in the command is called "pipe" and is found on the slash key above "Enter" on the keyboard
  5. Refer to the following screen shot as a sample where the time server's address is 10.221.89.143:

 

 

When checking the NTP status on the accessory server, the following process can be used:

  1. SSH into the accressory server (using a terminal program such as PuTTY)
    login credentials are pelco / Pel2899100
  2. Check NTP status using ntpq -p
  3. Lookup the hostname/alis in the hosts file:
    cat /etc/hosts | grep