NTP Configuration on router

-
NTP configuration on the router is pretty simple.

 Make your router as NTP server-
1. Set the clock on the router. You can use "clock" command in the privilege mode to set the time.
2. In order to configure it as master, configure the router as -
"ntp master <stratum>". The stratum number from 1 to 15. Indicates the NTP stratum number that the system will claim.
This will make your router as master.
06:49:10.078 UTC Sun Mar 22 2015
ntp master 5


 NTP client configuration-
1. Configure ntp master server address in the privilege mode-

ntp server <ip address of ntp master>
Validating NTP associations-

 Check its clock

R1#show clock

06:58:15.888 UTC Sun Mar 22 2015

 R1#show ntp associations

   address         ref clock       st   when   poll reach  delay  offset   disp
*~157.26.1.254    .LOCL.           1   1021   1024   377  0.706  -0.926  0.054
 * sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured





Comments

Post a Comment

Popular posts from this blog

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Admin...
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C...
Read more