-
3
- #1
Incorrect Year upon Change to 2016 Leading to Administration Block (all HiPath 4000 V6 & OpenScape 4000 V7 Versions are affected)
Problem
Detailed Problem Description and Symptoms: Incorrect year upon change to 2016 leading to administration block.
All HiPath 4000 V6 and OpenScape 4000 V7 versions are affected. HiPath 4000 V5 and earlier systems are not affected.
After year change to 2016 the system has an incorrect year. Due to this inconsistency the following effects can be noted:
• Administration blocked due to AMO CODEW date inconsistency
• Wrong year display on all TDM devices and IP devices not using NTP time as time source
• Potential issue on SPE (Signaling Payload Encryption) not working (currently under verification)
Problem Validation/Isolation Actions / Other Notes:
Solution
Permanent Solution: A permanent solution is under development with highest priority
Workaround/Temporary Solution: The following AMO commands can be used to provide a temporary workaround (not sevice impacting).
Care must be taken to execute them as written, and not alter or expand them to include additional commands
[e.g. do not add AMO APC commands].
CHA-FUNCT:SLANG=ENG;
CHANGE-DBC:LOCATION=TESTLAB;
EXEC-DATE:YEAR=2016,SYNC=NOSYNC;
CHANGE-DBC:LOCATION=CUSTOMER;
Notes:
• After any system restart/reload (including LINUX nodes switchover) the workaround must be re-applied (it is not persistent)
• 4K call control will no longer be synchronized to the main system and therefore some clock slippage maybe noticed over time
Problem
Detailed Problem Description and Symptoms: Incorrect year upon change to 2016 leading to administration block.
All HiPath 4000 V6 and OpenScape 4000 V7 versions are affected. HiPath 4000 V5 and earlier systems are not affected.
After year change to 2016 the system has an incorrect year. Due to this inconsistency the following effects can be noted:
• Administration blocked due to AMO CODEW date inconsistency
• Wrong year display on all TDM devices and IP devices not using NTP time as time source
• Potential issue on SPE (Signaling Payload Encryption) not working (currently under verification)
Problem Validation/Isolation Actions / Other Notes:
Solution
Permanent Solution: A permanent solution is under development with highest priority
Workaround/Temporary Solution: The following AMO commands can be used to provide a temporary workaround (not sevice impacting).
Care must be taken to execute them as written, and not alter or expand them to include additional commands
[e.g. do not add AMO APC commands].
CHA-FUNCT:SLANG=ENG;
CHANGE-DBC:LOCATION=TESTLAB;
EXEC-DATE:YEAR=2016,SYNC=NOSYNC;
CHANGE-DBC:LOCATION=CUSTOMER;
Notes:
• After any system restart/reload (including LINUX nodes switchover) the workaround must be re-applied (it is not persistent)
• 4K call control will no longer be synchronized to the main system and therefore some clock slippage maybe noticed over time