Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Setting time and date on newer CS1000 systems 7.5
- Thread starter nconick
- Start date
datetimeconfig is a Linuix command line entry---------------OVL responses indicates you are in the sl1 overlay.
If this is not a CO-RES platform (cs and ss on same card) then it is still LD 2 STAD.
If this is a CO-RES--then you need to be in the Liniux Shell
If this is not a CO-RES platform (cs and ss on same card) then it is still LD 2 STAD.
If this is a CO-RES--then you need to be in the Liniux Shell
- Thread starter
- #3
- Thread starter
- #4
Firebird Scrambler
Systems Engineer
Here are a few reports below for you.
TFC0200 and TFC007 received on switch when trying to change time in LD2.
On co-res systems, time and date must be set from the Linux Base.
This can be done with CLI using 'datetimeconfig'
*LAN on to the site
*Access the call server via putty/telnet and login using ADMIN account
*Type 'datatimeconfig' and follow prompts
*You will be asked if you want to keep the current time zone and this will be
followed by the current time and date set.
*At this point you can opt to change the time and date, this is done step by step
i.e
month - xx,
day - xx,
year - xx etc
#####################################################################
If trying to configure NTP config in a Linux box, don't allow yourself to be confused by the bad wording on the Web page.
Run ntpconfig from a command line.
This worked on Co-res..... Standalone is almost the same.
In Co-res this will update the Call Server time as well.
It will ask questions like these.
Please determine NTP transfer mode within your whole system:
Do you wish to configure NTP in secure MD5 transfer mode? (Y/N) [Y]? (no thanks, insecure is fine for me) [N]
Q Are you
Please indicate the Clock Source function of this Linux system:
1) Primary Clock Source server (This is the Primary NTP server) NOPE
2) Secondary Clock Source server (another one is the Primary NTP server) NOPE
3) This Linux system is NOT a Clock Source server (This one looks promising...)
Select an option (1-3) [3]:
Choose option 3 (I will use the customers NTP server, it is at the right time after all)
NTP Configuration
-----------------
Provide the IP addresses of the Primary and/or Secondary Clock Source Server(s)
Enter MACHINE IP of the Primary Clock Source Server [10.10.2.35]:
10.10.2.35
(Input the first address the customer gave you)
Enter MACHINE IP of the Secondary Clock Source Server [10.10.2.35]: (if it exists).
NTP server configuration:
NTP is not configured in secure MD5 transfer mode:
NTP Clock Source: Other
External IP(s): 10.10.2.35
This setting will override any other clock sources!
Are you sure you want to continue (Y/N) [N]?
[Y]
Job done.
At any time cntl-c will take you out of the set up.
To print off your settings
ntpconfig --show (The 2 dashes are important)
However
If you DO want to be the primary or backup server, then work it out for yourself.
Again, much easier as command line.
The Linux box will then go off to the NTP server and get the time.
64 seconds later, it will do it again, then 128 seconds, then 256 (Get the pattern) right up to 1024 Seconds.
So long as the time drift between the 2 is not excessive, it will continue to get the time every 1024 seconds. UNLESS the time drifts.
It will then half the time interval each time, until it is happy enough that it is keeping step with the NTP server.
After running it as command line, then the web interface might mean something. (But you will never go back, honest)
This needs to be performed on ALL Linux Servers in your network. (If you want them all to be in sync)
This covers the Linux Server. The Call Server is another bag of worms.
#################################################################################
Firebird Scrambler
Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer
Website = linkedin
TFC0200 and TFC007 received on switch when trying to change time in LD2.
On co-res systems, time and date must be set from the Linux Base.
This can be done with CLI using 'datetimeconfig'
*LAN on to the site
*Access the call server via putty/telnet and login using ADMIN account
*Type 'datatimeconfig' and follow prompts
*You will be asked if you want to keep the current time zone and this will be
followed by the current time and date set.
*At this point you can opt to change the time and date, this is done step by step
i.e
month - xx,
day - xx,
year - xx etc
#####################################################################
If trying to configure NTP config in a Linux box, don't allow yourself to be confused by the bad wording on the Web page.
Run ntpconfig from a command line.
This worked on Co-res..... Standalone is almost the same.
In Co-res this will update the Call Server time as well.
It will ask questions like these.
Please determine NTP transfer mode within your whole system:
Do you wish to configure NTP in secure MD5 transfer mode? (Y/N) [Y]? (no thanks, insecure is fine for me) [N]
Q Are you
Please indicate the Clock Source function of this Linux system:
1) Primary Clock Source server (This is the Primary NTP server) NOPE
2) Secondary Clock Source server (another one is the Primary NTP server) NOPE
3) This Linux system is NOT a Clock Source server (This one looks promising...)
Select an option (1-3) [3]:
Choose option 3 (I will use the customers NTP server, it is at the right time after all)
NTP Configuration
-----------------
Provide the IP addresses of the Primary and/or Secondary Clock Source Server(s)
Enter MACHINE IP of the Primary Clock Source Server [10.10.2.35]:
10.10.2.35
(Input the first address the customer gave you)
Enter MACHINE IP of the Secondary Clock Source Server [10.10.2.35]: (if it exists).
NTP server configuration:
NTP is not configured in secure MD5 transfer mode:
NTP Clock Source: Other
External IP(s): 10.10.2.35
This setting will override any other clock sources!
Are you sure you want to continue (Y/N) [N]?
[Y]
Job done.
At any time cntl-c will take you out of the set up.
To print off your settings
ntpconfig --show (The 2 dashes are important)
However
If you DO want to be the primary or backup server, then work it out for yourself.
Again, much easier as command line.
The Linux box will then go off to the NTP server and get the time.
64 seconds later, it will do it again, then 128 seconds, then 256 (Get the pattern) right up to 1024 Seconds.
So long as the time drift between the 2 is not excessive, it will continue to get the time every 1024 seconds. UNLESS the time drifts.
It will then half the time interval each time, until it is happy enough that it is keeping step with the NTP server.
After running it as command line, then the web interface might mean something. (But you will never go back, honest)
This needs to be performed on ALL Linux Servers in your network. (If you want them all to be in sync)
This covers the Linux Server. The Call Server is another bag of worms.
#################################################################################
Firebird Scrambler
Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer
Website = linkedin
- Thread starter
- #6
I can't seem to get back to the Linux shell. I type ~. and I thought that was supposed to get me back to the shell.......?
I just get into pdt and type exit and that gets me back to Linux shell. Hold control button and type PDT. It will prompt you for username and password (use your UCM login) and you are back.
Or you just close the putty session and log back in.
John Anaya
Amdocs Inc.
ACSS/ACIS - CS1000 Rls 7.5/Call Pilot 5
ACSS/ACIS - SME - IP Office 8.0
APSS/APDS - Avaya UC Services
Public Profile
I just get into pdt and type exit and that gets me back to Linux shell. Hold control button and type PDT. It will prompt you for username and password (use your UCM login) and you are back.
Or you just close the putty session and log back in.
John Anaya
Amdocs Inc.
ACSS/ACIS - CS1000 Rls 7.5/Call Pilot 5
ACSS/ACIS - SME - IP Office 8.0
APSS/APDS - Avaya UC Services
Public Profile
- Thread starter
- #8
- Status
Similar threads
- Locked
- Question