Asset ID:	1-71-1372153.1
Update Date:	2011-11-15
Keywords:

---

Solution Type  Technical Instruction Sure

Solution  1372153.1 :   VTL - How to configure NTP in the VTL Console  

In this Document
  Goal
  Solution

---

Created from <SR 3-4731200601>

Applies to:

Sun StorageTek VTL Plus Storage Appliance - Version: 1.0 - Build 1323 to 2.0 - Build 1656 - Release: 1.0 to 2.0
Sun StorageTek VTL Prime System - Version: 1.0 - Build 1813 to 1.1 - Build 2076   [Release: 1.0 to 1.0]
Sun StorageTek VTL Storage Appliance - Version: 4.0 - Build 1221 to 4.0 - Build 1221   [Release: 4.0 to 4.0]
Sun StorageTek VTL Value System - Version: 1.0 - Build 1323 to 1.0 - Build 1323   [Release: 1.0 to 1.0]
Information in this document applies to any platform.

Goal

Many times the NTP is not configured with the VTL initial installation.

Customer can configure the NTP server for to sync VTL log files to the time of the backup server log files providing the backup server is configured for NTP.

This document explains the steps for the VTL Appliance NTP configuration.

Solution

NTP Configuration from VTL Console GUI

1. Make sure no backup/migrations are running on the backup clients.

2. Configure NTP server

Note1: Root access is needed for the configuration task.

If the VTL servers are in Failover configuration, before Step A below, suspend Failover on both nodes (right click server name -> Failover -> Suspend Failover).

A. If you do not have any time-based policies set in VTL (automated tape caching (ATC), replication, etc.), the NTP configuration can be done on the live system without having to suspend the VTL server.

•  Log into the VTL Console GUI
•  Right click on the server node
•  Select System Maintenance from the drop down menu
•  Configure NTP server by specifying the NTP server IP in the popup window.

The log files should now reflect the time from the NTP server.

B. If you have time-based policy(s), then the following steps will be necessary:

• Configure the NTP server IP in the console GUI for both nodes as mentioned above in Step A.
• Restart VTL services.
  (VTL services can be restarted via VTL Console (right click server name -> System Maintenance -> Restart VTL or from a command line:
  # vtl restart

If the VTL servers are in Failover configuration, after performing Step A or B above, resume Failover on both nodes (right click server name -> Failover -> Resume Failover).

Note - VTL Prime or Value systems do not support HA configuration.

Attachments

This solution has no attachment