Time zones and time stamps

General information

To simplify creating NFM-P-based schedules when the user and server are in different time zones, the NFM-P converts and displays schedule times specific to the user and server. For example, if a client user in Chicago wants to schedule a task on a server that is in New York, the NFM-P calculates the time difference and displays the local client and server times.

User time zones are configured in the user preferences form. If a time zone is not configured on the main server, the NFM-P uses the default time zone on the single-user client or client delegate server station, If the default time zone is not one of the NFM-P time zone options, the NFM-P displays the time zone ID and uses the UTC value without the time zone offset.

The NFM-P displays whether daylight saving time is in effect for the client and the server. Daylight saving time is specified for the user start time and is based on the client time zone. Daylight saving time does not specify the current time and end time.

For scheduled OAM tests, the timeCaptured attribute in a specific result is a time stamp inserted by NFM-P at the time that the test result is processed (accounting file transfer time plus test processing time). The date stamp is taken from the NFM-P server clock, with a resolution of milliseconds.

The scheduledTime attribute is a time stamp inserted by a managed NE, and corresponds to the accounting policy configuration on that NE. The current (or most recent) test result for each test is written to the accounting file with this time stamp. The actual timing is derived from the NE’s clock. An accounting file can contain multiple test results for one such time stamp. The actual number of test results depends on the file policy rollover and accounting policy collection interval.

Figure 5-1: Schedule management and configuration forms