The clock is slow CS1000e Co-resident

[amyygt]

The clock is slow.
Que tal?, One that happened with version 7.5 in a co-resident Rls clock tends delayed a few minutes. Configure and take reference from a network server, it is possible to synchronize but after one hour delay begins. Someone can help me. thanks

 

[Johnthephoneguy]

You can go into Element Manager and set it up to Automatically sync up to your network server. Never worry about it again.

JohnThePhoneGuy

"If I can't fix it, it's not broke!

 

[amyygt]

That's the idea, but always late,

 

[Triton101]

i think it's predefined to check every 10 min and if the threshold is exceeded it updates the clock.... just make sure you don't have the port blocked on the network (port 123) on your network.

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

 

[amyygt]

Try making these changes from the LD 117
=> CHG NTP TIMEINT 1 15
Command not Supported on Linux Call Server, please use "Base Manager" or "CLI" instead.
Base Manager Link :

https://cpmgs.thebristol.com/local-login/

>> Base System >> Date And Time.
Command Line Interface : ntpconfig.
no work Co-resident

 

[janaya]

correct. If co-resident run the ntpconfig from the linux prompt and it will ask you for the information.

 

[Tman45]

It could be your Co-Res is using a different NTP source or that your PCs are actually running slow from the NTP server. We had an issue lately and EVERYONE uses PCs as the time reference but what happened is that the PCs were actually running slow (so the PBX syncing off NTP was actually right!!). So after banging our heads as to why the PBX was not right it was an issue with NTP with the PCs. So, a good way to test is go to

http://www.time.gov/widget.html

Hope you can find the issue.

 

[amyygt]

I found this solution Avaya, I will try on Monday and tell them

Call Server (CS) system time drifts on Release 6.00 Co-resident ( Co-Res ) System[/b]
Rate this Page[/b]


Doc ID: SOLN188449
Version: 2.0
Status: Published
Published date: 27 Aug 2010
Updated: 06 May 2012
Author: Content Migrator

DETAILS
4605937
PROBLEM CLARIFICATION
On Co-RES systems, Linux Base provides system time for all elements including Call Server (CS).
Linux Base time is the SW ( Software ) time, while it gets initial time from HW ( Hardware) clock (BIOS battery) on startup,
then it continues to update system time according to its SW clock.The problem reported is, thatSW clock keeps drifting 30 seconds per day .
SOLUTION
If internal clock type is used as it is configured now in the system, system time is synchronized with BIOS time initially and then updated continously according to SW
clock.If machine type is CPPM ,system time could be corrected by setting an appropriate offset on Ld (Load )117 in case of a drift on system time.But, in Co-Res systems,
Linux Base time provides the system time and overlay commands on Ld 117 to modify system time couldn't be used.
Thus, in case of drift in Linux Base time, Network Time Protocol needs to be used ( NTP ). Rather than using Linux
Base time as an internal clock, an NTP server ( which could simply be a Personal Computer (PC) ) would provide correct time as an external time source.
NTP could be configured via Base Manager > Date and time > NTP edit> Add a reliable external clock source IP address from edit page .
After editing, when <Sync Now> button is pressed , time is received from NTP server and it is updated periodicallyafter that.
Though there's no available command on Linux Base to keep time accurate by setting an appropriate offset in case of drift,commands below
could be used to display SW clock time, HW clock time; synch SW clock to HW clock or HW clock to SW clock manually.
[spalav@cores ~]$ su
Password:
[root@cores spalav]#
[root@cores /] # find / -iname hwclock*
/usr/share/man/man8/hwclock.8.gz
/usr/sbin/hwclock
[root@cores /] # /usr/sbin/hwclock --------->prints HW clock time
18 Jun 2010 05:37:28 PM EEST -0.977187 seconds
[root@cores /] # date ---------> prints Linux Base (SW) clock time
Fri Jun 18 17:37:30 EEST 2010
[root@cores /] # /usr/sbin/hwclock --hctosys ---------> retrieves HW clock time and sets it to SW clock time
[root@cores /] # /usr/sbin/hwclock --systohc ---------> retrieves SW clock time and sets it to HW clock time
LEGACY ID
KB94605937

 

[amyygt]

Now try the settings below

[spalav@cores ~]$ su
Password: *******
[root@cores spalav]#
[root@cores /]

but that was to force me to change the root password

[admin@cppm ~]$ su
Password: *******
You are required to change your password immediately (password aged)
Password Change Utility

Please note that a valid password must contain at least 8 characters,
6 of which are UNIQUE from all 4 character classes (lowercase, uppercase,
digits, other characters) to be considered valid.
Your password should not contain words from any dictionary in any
language or jargon, and should not be based on any personal
or login information.


Changing password for root
(current) UNIX password:*******

You can now choose the new password.

A valid password should be a mix of upper and lower case letters,
digits, and other characters. You can use an 8 character long
password with characters from all of these classes. An upper
case letter that begins the password and a digit that ends it do
not count towards the number of character classes used.

Enter new password: x sample S1p2rt_3
Weak password: not enough different characters or classes.
Try again.

You can now choose the new password.

I do not understand that does not accept the values ​​of the new key Someone has this happened