-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.14.z, 4.15.z, 4.17.z, 4.16.z, 4.18.z, 4.19
-
None
-
Telco kube-compare Sprint 266
-
1
-
False
-
-
The default value for Westport Channel GrandMaster configurations for the RAN DU profile contained an incorrect value for the "MaxInSpecOffset" setting. The default of 100 should be updated to 1500 for proper functioning.
-
Bug Fix
-
In Progress
This is a clone of issue OCPBUGS-49785. The following is the description of the original issue:
—
Description of problem:
T-GM uses the MaxInSpecOffset value to determine the state change from HOLDOVER to FREERUN. By default, HoldoverTimeout is set to 14,400 seconds, LocalMaxHoldoverOffset is 1,500 ns, and MaxInSpecOffset is set to 100 ns. With this configuration, the holdover state times out in 16 minutes due to the slope increment occurring every second, reaching MaxInSpecOffset of 100ns within 16 minutes.E810 support 4 hours of holdover and to keep this behavior consistent need to set default MaxInSpecOffset to 1500 These values should be configurable by end-users and allowed to be different in the cluster-compare templates, but default to the values below:
Actual results:
LocalMaxHoldoverOffSet: 1500 LocalHoldoverTimeout: 14400 MaxInSpecOffset: 100
Expected results:
LocalMaxHoldoverOffSet: 1500 LocalHoldoverTimeout: 14400 MaxInSpecOffset: 1500
Additional info:
- blocks
-
-
- New
-
- clones
-
-
- Verified
-
- is blocked by
-
-
- Verified
-
- is cloned by
-
-
- New
-
- links to
-
RHEA-2024:139467
OpenShift Container Platform 4.18.0 CNF vRAN extras update
- mentioned on
(1 links to, 1 mentioned on)