@BBakkenist Wtf 😂
Using Celerra Manager to configure NTP services on the Control Station
The easiest fix is to change the date and timezone on the CS to the correct local time. However, there is a chance the date on the CS will (over time) become out of sync again.
Please note that this procedure requires a reboot of the CS. This should have little visible impact to Data Mover end-user access. However, it will impact administrative users and Celerra Manager access temporarily - only about 5 ~ 10 minutes while the CS reboots. Therefore, it is recommended that this reboot be done at a convenient time. If it is not going to be convenient to reboot the CS, then consider using the command line version procedure as an alternative.
For a more permanent fix to resolve this issue:
- Using Celerra Manager to configure NTP services on the Control Station.
- Check the production Data Mover(DM) properties to see if any DM is currently configured to talk to a NTP server.
- This can be done by logging into the Celerra Manager interface with the root user account and accessing the Data Movers menu from the left navigation panel.
- By clicking on "server_2, it will load the properties of the DM in the right-hand panel.
- The NTP configuration will be listed towards the bottom of the page.
- You may want to check more than one active Data Mover to see if there is a common NTP server used by more than one of them.
- On the left navigation panel, click the Control Station object to load the Celerra home page.
- On the Celerra home page, click the tab labeled Control Station Properties. This panel provides the ability to update the field named NTP Servers.
- Once the NTP server IP address(es) is added, then changed the Timezone to the correct local timezone, lastly then click Apply.
- The CS clock will not sync with the NTP servers until the NTP services are restarted. From the Celerra Manager, the only way to do this is to click the Reboot button on the Control Station Properties panel. This will reboot the CS. Once the CS is fully rebooted, the NTP service on the CS will begin to automatically sync with the NTP server.
- Using the command line to configure NTP services on the Control Station
- Verify if there is a NTP server in the environmentwith the following command. #server_date server_2 timesvc stats ntp
- Verify that the IP address listed above can be pinged from the CS. #ping 172.16.3.210
- Configure the NTP services on the CS by running the following commands from root:
- First step is to verify and if needed configure the Celerra for the correct local timezone. # /usr/sbin/timeconfig
- Make sure the ntpd service is stopped: # /sbin/service ntpd stop
- Use vi to edit the /etc/ntp.conf file accordingly: # vi /etc/ntp.conf and add your server or second server.
- Use vi to edit the /etc/ntp/step-tickers file to add the same NTP IP address: # vi /etc/ntp/step-tickers
- Make sure that you start ntpd service:# /sbin/service ntpd start
- At this point the NTP service is running & the time will begin to slowly Sync.
- Make the setting persistent after a CS reboot:
# /sbin/chkconfig ntpd --list
ntpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
# /sbin/chkconfig --level 345 ntpd on
# /sbin/chkconfig ntpd --list
ntpd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
- Run the following to check that the CS is now able to sync with the NTP server: # /usr/sbin/ntpq -p
- Network Time Protocol (NTP) is normally configured on a Celerra Data Mover to ensure there is no time skew from the Data Movers to the local time. This is to avoid problems with CIFS connections to Celerra CIFS servers. This ensures that the Domain Controllers, Data Movers and the end users are all syncronized to the correct time. Ideally it is best to have all of the Data Movers and Control Station(s) configured to talk to the same NTP server on the network. This will ensure proper log collection and timing of events.