Time changed on HiPath 4000 V4 with GMT 00 (Africa/Lome)

[Bicaros]

thread965-1745606

Hi all
I have a problem with the configuration of the timetable of my HiPath 4000 v4: Despite that I chose the zone hoiraire Africa/Lome, my time changed on 1 April past while Lome is at GMT 00 and should not change time.
I do not have a NTP server but I told myself locally that this should work.
Help me correct that.
Kind regards

 

[donb01]

That system may be old enough that if it's not fully patched it may not have the updated tables for the DST start/end dates.

Try DIS-SONUS; on your system. That is the table of starting and ending dates for the PBX part of things. I believe the Unix part of things is handled differently. If your SONUS table doesn't have current year data in it you can add it. In the newer versions of the 4K SONUS is no longer used because using NTP is more common.



Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[Bicaros]

Thank you donb01 for your help.
Below is the result command DIS-SONUS which proves that there is no entry find in the table SWITCHOVER:

DISPLAY-SONUS;
DISPLAY-SONUS;
H500: AMO SONUS STARTED
ADJUSTED FUNCTION MODE OF SONUS - TASK : AUTOMATIC
H04 : EU-STANDARD APPLIES FOR THE AUTOMATIC TIME-SWITCHOVER.
H03 : NO VALID ENTRIES WERE FOUND IN THE SWITCHOVER TABLE.

AMO-SONUS-111 DAYLIGHT SAVING / STANDARD TIME SWITCHOVER
DISPLAY COMPLETED;
<

What should I do?

 

[donb01]

Let's see how bad this looks....

178 SONUS - Daylight Saving / Standard Time Switchover
 
Interrelationships
	
Parameter Description
Functions of the AMO
	
Error Messages and Advisories
Switchover from standard time to daylight saving time (DLS) and vice versa is handled by a resident task. This task has three function-modes:
•
	
Automatic
the task computes the switchover-dates itself according to the directives of the European Community (EU) regarding DLS / standard time switchover (last Sunday in March and September respectively), or to the US-directives (first Sunday in April and last Sunday in October), depending on the program system loaded to the actual switch.
•
	
Read from file;
the task is processing the dates contained in a table situated in a file on the hard disc of the system (switchover table).
This mode is used, when the switchover dates differ from the standard valid for the region, to which the program system refers (see above).
•
	
Deactivated;
the task is inoperative.
Normally, no switchover table is existing in the system, the task is operating in the automatic mode.
The AMO SONUS serves to maintain the switchover table, and to adjust the function mode of the resident task.
The table can hold up to 20 switchover dates. Accordingly, the system can be preset for ten years at two switchovers a year (in function mode "read from file").
178.1 Interrelationships
•
	
AMO DATE : Altering system date and/or time
178.2 Functions of the AMO
•
	
ADD-SONUS
	
:
	
Installing/changing the table of switchover dates
•
	
DISPLAY-SONUS
	
:
	
Displaying the table of switchover dates
•
	
SWITCHOVER-SONUS
	
:
	
Switchover the function mode of the resident task
•
	
REGENERATE-SONUS
	
:
	
Regenerate the table of switchover dates.
178.2.1 ADD-SONUS
Installing/changing the table of switchover dates.
The table containing the switchover dates is read. If there is no file containing the table , one will be created by AMO SONUS.
The AMO checks, if the date is logically correct, and if it is older than the date obtained from the system time. One switchover to daylight saving and one to standard time is permitted for each year. The date specified in the AMO call is entered at the correct place in the switchover data. If a similar switchover has already been entered for this year, it will be overwritten.
To warrant the correct function of the time-switchover, all entries should be valid for the same hemisphere. The first entry lays down the hemisphere, for which the table is valid. All consecutive entries are checked against this first entry for validity.
The table will hold up to 20 switchover dates. Old dates are removed in every ADD. Dates more than nine years in advance of the year of the system time are rejected.
If there's no valid system time, no switchovers can be entered.
For a faultless operation of the DLS / standard time switchover, the entries to DLS and standard time should follow each other in alternating order. The AMO therefore checks whether the preceding entry is the logical reversal in the opposite direction.
When daylight saving time reverts to standard time, the period between 02:00 and 03:00 hours runs twice. To avoid mistakes, you are not allowed to change the time table during this period on the day of switchover.
Procedure Overview
 
Command Code
	
Parameter
ADD-SONUS
	
YEAR=<number>,MONTH=<number>,DAY=<number>
 
	
,TYPE=<param>;
Examples
1.
	
Installing a switchover to standard time
Input:
ADD-SONUS:1988,09,25,STD;
2. Installing a switchover to daylight saving time
Input:
ADD-SONUS:1989,03,26,DLS;
Note:
If the table is created by the AMO, the function mode is set to “read from file“.
178.2.2 DISPLAY-SONUS
Displaying the table of switchover dates.
The table is read and the switchover dates found are compared with the date from the system. The output only shows dates that haven't yet expired. If no valid dates are found or if there is no such table, message H3 will be output.
If the function mode is set to AUTOMATIC, the message H4 will be output.
For each year, one line is output. The first column contains the switchover dates to daylight saving, the second those to standard time. If one of these dates is missing, its field will be left blank. If there are no entries for a certain year, there'll be no output for it.
Procedure Overview
 
Command Code
	
Parameter
DISPLAY-SONUS
	
;
Example
Displaying the switchover table
Input:
DISPLAY-SONUS;
Output:
+---------------------------------------+
| SWITCHOVER TO |
| DAYLIGHT SAVING STANDARD TIME |
|-------------------+-------------------|
| 1988-03-27 | 1988-09-25 |
| 1990-03-25 | |
| 1991-03-24 | 1991-09-29 |
| | 1992-09-27 |
|-------------------+-------------------|
| SWITCHOVER TIME |
| 02:00 HRS | 03:00 HRS |
+-------------------+-------------------+
ADJUSTED FUNCTION MODE OF SONUS - TASK : AUTOMATIC
H04: US-STANDARD APPLIES FOR THE AUTOMATIC TIME-SWITCHOVER.
178.2.3 SWITCHOVER-SONUS
Change the function mode of the switchover task.
Three different modes can be chosen from:
•
	
HD : read the switchover dates from the table in a hard disk file;
•
	
AUTO : the task computes the switchover dates
–
	
according to the directives of the European Community (EU) regarding DLS / standard time switchover in european program systems
(DEVELOPMENT LINE = EUROPE DEVELOPMENT at DISPLAY-DBC;)
– according to US-standard on american program systems
(DEVELOPMENT LINE = US DEVELOPMENT at DISPLAY-DBC;)
•
	
OFF : the task is deactivated
The AMO reads the table and the switchover mark will be changed according to the input.
If there is no SONUS-file on the hard disk, one will be created, similar to the ADD branch. The table of switchover dates will be initialised with dummy information. Thereafter the switchover mark will be adjusted according to the input command.
Procedure Overview
Command Code
	
Parameter
SWITCHOVER-SONUS
	
FUNCT=<param>;
Example
Switch over the resident task to automatic
Input:
SWITCHOVER-SONUS:AUTO;
Output:
H04: US-STANDARD APPLIES FOR THE AUTOMATIC TIME-SWITCHOVER.
178.2.4 REGENERATE-SONUS
Regenerate the table of switchover dates
The file is read and the switchover dates found are compared with the date from the system. The output only shows dates that haven't yet expired. If no valid dates are found or if there is no such table, message H3 will be output.
After all dates have been processed, the AMO adjusts the switchover mark by generation of a SWITCHOVER command (on new installation of the file it is set to "read from file").
Procedure Overview
Command Code
	
Parameter
REGENERATE-SONUS
	
;
Example
Regenerate the switchover table
Input:
REGENERATE-SONUS;
Output:
ADD-SONUS:1988,3,27,DLS;
ADD-SONUS:1988,9,25,STD;
ADD-SONUS:1990,3,25,DLS;
ADD-SONUS:1991,3,24,DLS;
ADD-SONUS:1991,9,29,STD;
ADD-SONUS:1992,9,27,STD;
SWITCHOVER-SONUS:AUTO;
178.3 Parameter Description
DAY
	
Date - Day
 
	
Type of Input
	
:
	
Single value, mandatory
 
	
Possible Values
	
:
	
1 - 31
 
	
 
	
 
	
 
	
 
FUNCT
	
Function Mode of the Resident SONUS Task
 
	
Type of Input
	
:
	
Single value, mandatory
 
	
Possible Values
	
:
	
AUTO computation of switchover dates according to standard, depending
on the program system installed:
EU-standard for european systems
(PRODUCTION-LINE EUROPE DEVELOPMENTat DISPLAY-DBC;)
US-standard for american systems
(PRODUCTION-LINE US DEVELOPMENTat DISPLAY-DBC;)
HD (read switchover dates from file on hard disk)
OFF (task is deactivated)
 
	
 
	
 
	
 
	
 
MONTH
	
Date - Month
 
	
Type of Input
	
:
	
Single value, mandatory
 
	
Possible Values
	
:
	
1 - 12
 
	
 
	
 
	
 
	
 
TYPE
	
Type of Switchover (Standard Time -> Daylight Saving / Daylight Saving -> Standard Time)
 
	
Type of Input
	
:
	
Single value, mandatory
 
	
Possible Values
	
:
	
STD (switchover to standard time)
DLS (switchover to daylight saving)
 
	
 
	
 
	
 
	
 
YEAR
	
Date - Year
 
	
Type of Input
	
:
	
Single value, mandatory
 
	
Possible Values
	
:
	
1988 - 2079
178.4 Error Messages and Advisories
178.4.1 Error Messages
F01:
	
DATE INVALID.
F02:
	
THE ENTERED SWITCHOVER DATE IS IN THE PAST.
F03:
	
SWITCHOVER ON SWITCH DAY NOT POSSIBLE BETWEEN <time> AND <time> HOURS.
F04:
	
SWITCHOVER DATA ENTRY ONLY POSSIBLE 10 YEARS IN ADVANCE
F05:
	
DATE/TIME NOT ASSIGNED IN SYSTEM.
F06:
	
THE FILE CONTAINING THE SWITCHOVER DATA IS NOT ON SYSTEM HARD DISK.
F07:
	
ACCESS TO THE FILE OF SWITCHOVER DATA IS NOT POSSIBLE, AS THE AREA CONTAINING THE FILE IS LOCKED.
ACTIVATE WITH: "
F08:
	
THE COMBINATION OF VALUES ENTERED FOR THE PARAMETERS "MONTH" AND "TYPE" DOES NOT LOGICALLY MATCH THE PRESENT TABLE OF SWITCHOVER DATES.
F09:
	
DMS ERROR ON ACCESS TO ":AMD:SONUS/UZTAB". DMS STATUS @@@@@.
Note:
If there are no valid entries in the table of switchover dates, there are no restrictions regarding month and changeover type.The first entry determines the validity of the table for the nothern or southern global hemisphere (e.g switchover to DLS in January - June -> northern hemisphere, switchover to DLS in July - December -> southern hemisphere). Thereafter only entries for the same hemisphere are possible.
178.4.2 Advisories
H01:
	
FOR <date>, A SWITCHOVER TO <type> HAS ALREADY BEEN ENTERED.
 
	
(The date output in the message is overwritten.)
H02:
	
FOR <year>, NO SWITCHOVER TO <type> HAS BEEN ENTERED.
 
	
(The AMO checks whether the preceding entry is the logical predecessor.)
H03:
	
NO VALID ENTRIES WERE FOUND IN THE SWITCHOVER TABLE.
 
	
(The file on the hard disk does not exist or doesn't contain any valid switchover dates.)
H04:
	
<region>-STANDARD APPLIES FOR THE AUTOMATIC TIME-SWITCHOVER.
H05:
	
THE CONFIGURATION TABLE OF THE SYSTEM COULD NOT BE READ.
178.4.3 List of abbreviations
 
<date>
	
Date consisting of year, month, day
<region>
	
EU or US (see chapter SWITCHOVER-SONUS)
<time>
	
Time in hours and minutes (e.g. 02:00)
<type>
	
Type of switchover (DLS / STANDARD TIME)
<year>
	
Year of changeover
 
 
OpenScape 4000 V7, Volume 1: AMO Descriptions, Service Documentation, Issue 3, ID: P31003H3170S101017620
Copyright © Unify GmbH & Co. KG 01/2015  -  All rights reserved.

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[donb01]

Your system is running in AUTO mode, which should work based on values to calculate the start/end valuse on the HD, but if it's not current on the updates the HD may not have provisions for the DST changes that were made many years ago. I used to update my SONUS tables by hand before V7. I started with V5 in 2010, so I have to assume V4 might have come out in the 2007 area somewhere. I can't remember when the DST changes happened, but I installed the first digital sign in my town in 2005, and it was several years after that that I had to flash the firmware in the sign controller with the new DST code, so I would guess it changed around 2007.

You can add the dates in by hand and it won't hurt anything and you should also be able to execute a switch manually without messing around with any of the other timers. Changeing date/times in the 4K is supposedly not a pleasant experience if you do it wrong because everything is time sensitive.


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[Bicaros]

Thank Donb01, I understand.
However my system is in Togo (universal GMT), so we have no change in date or time or winters. So the thought that the fact that I was not declared a start/end date was correct for not having a change of time, but this is not the case.
That's right my v4 version is 2007-2008.
-How to Flash the firmware in the sign controller with the new DST code?
-In the UNIX of the wizard HiPath 4000 v4, how to configure the NTP? What is the difference between IP card IP address, host, route, gateway, DNS?
Kind regards

 

[donb01]

I don't know the unix world in V4. I can tell you how to set it up in V6/V7 but that is linux now. Sorry.

The reference to the sign controller was just me talking about something I know I had to do in an attempt to guess the age of your system. If you are not affected by DST then I couldn't guess why the time would change, unless somehow you got a US version of the system. Considering there is no table there should be no time changes.

That's as far as I can go - someone who is closer to that than me or in the EU will have to address it further. I am in the US, and I always had to update the table by hand - I would just put in 5 - 6 years at a time and forget about it.


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[Bicaros]

It's well received Bond01,
Thank you very much for your guidance that has guided me a lot.
Kind regards