Home page of Satellite Internet and Information

Satellite Internet Forum.

Welcome, Guest.
Welcome to this satellite broadband discussion forum. Wherever you are and whatever your problem we are here to help each other. Connecting to the internet via satellite is not always easy but is critically important to those in remote places or with poor terrestrial infrastructure. Both service providers and customers are encouraged to contribute. Register at the bottom of the forum home page if you wish to contribute or ask question. Read the Forum rules.
      Satellite Internet Forum : Home Page          
Pages: 1

HUB time and date

(Read 4194 times)
Ex Member
Ex Member


Jul 23rd, 2009 at 10:31pm  
how to change the time and date on the NMS server so that the settings will be globaly populated on all iDirect hardware and software. We changed time and date settings to EST but still some GTM instances are showing?
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #1 - Jul 24th, 2009 at 2:46am  
If you think you have set it properly, you still need to sync the hardware clock and reboot the NMS. 

Command to sync:

# hwclock w

Reboot the box.  (should not cause outage, network will stay alive without the NMS, however it is still considered a HAZCON, and you should do this in a SLOW period on the hub, in the event it does cause outage).

M



Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #2 - Jul 29th, 2009 at 8:05pm  
Thanks for the reply. How about the PP servers?
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #3 - Jul 29th, 2009 at 9:37pm  
1. Login as root:

2. Enter date by typing the following command:date MMDDhhmmYYYY

For example: You can set the time to July 29, 21:40, 2009 by the following command: date 072921402009

3. Enter the following command to synchronize the hardware clock: hwclock w

4. Reboot the box.  (command: reboot)
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #4 - Jul 29th, 2009 at 9:57pm  
Thanks. I've already done that, but I was wondering if I should have the time set in all servers (NMS1, NMS2, NMS3, PP1, and PP2). I've updated the NMS servers but worried if I reboot the PP server will cause brief outage?
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #5 - Jul 29th, 2009 at 10:58pm  
Yes, rebooting a PP will cause a service interruption for the remotes that reside on the blade.

If you are determined to change the time, you are going to have to endure the outage.

When you reboot the PP, the remotes will fail over to the "other"....blade. Then, when you reboot the second blade, they will fail back to the first blade. Once you are finished adjusting time on both, you will need to get on the NMS pp_controller process and balance the blades (which will cause another service interruption for a select few remotes) .....as the blades are balanced with an equal amount of remotes.

3 NMS's?  Are you running a Distributed NMS? 
Bottomline: Rebooting the PPs will cause outage.  Plan accordingly and ensure you balance when you are done.

Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #6 - Jul 30th, 2009 at 4:03pm  
I am. Will do next maintenance outage. Thanx.
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #7 - Apr 5th, 2011 at 1:11pm  
Hello all,


This is my first post on this informative forum.

I just followed this procedure posted by TDMAMike. However I skipped the reboot step of the procedure to avoid downtime if possible.

After restarting iMonitor and iBuilder the time is shown correctly there, and it was also immediately shown correctly on the NMS and PP.

I was wondering whether there is any experience that indicates that the reboot is actually required?

The network seems fine atm.
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #8 - Apr 5th, 2011 at 9:59pm  
why do not you use ntp for time syncronization?
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #9 - Apr 6th, 2011 at 8:41am  
Hello vydrik,

Thanks for feedback.

The reason is  simple, as I do not know what ntp is. Smiley Could you explain what it is and how it is configured. We would like to avoid having to manually adjust time again in the future.

The procedure did cause a small hickup in the network. Remotes had a "re-acquire network outage" of less than 1 minute.

Probably affected the BTP when I set the HWClock on the PP's?
Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #10 - Apr 6th, 2011 at 8:45am  
I read up a bit on NTP. I like that it will slowly adjust the time, and should thus not cause remotes to have to reacquire the network.

Are there any drawbacks of implementing such a solution for time synch?

Back to top
 
 
IP Logged
 
Ex Member
Ex Member


Reply #11 - Apr 6th, 2011 at 11:09pm  
no there are no drawbacks, and we use it everywhere for everything Smiley
you may want to configure two NTP servers for redundancy
Back to top
 
 
IP Logged
 
Pages: 1