Having routers that do not have a calendar - I somehow need to make sure my routers keep proper time. I've been pointed to NTP. Routers being used are 36xx and 26xx. What I thought I would do is run ntp master on our central router (point to point network) and have the rest sync with this router. Although this router does not have a calendar - I will know exactly when it reboots, etc - so I can change the time as necessary. (Note: Wasn't planning on having the master router sync with an external reference. This would be our only implementation of NTP to date - but just in case, used stratum 15 for master.)
Master - ntp master 15
Router - ntp server IPADDRESSOFMASTER
The way I'm configuring this doesn't appear to be working.
So - if you were me, how would you do this? What is the command syntax?
If this is a bad idea - let me know. I'm not a big fan of doing it this way. I'm not a major control freak - but I do want our routers running with some semblance of the correct time.
I believe the reason your configuration is not working is that you are setting your master for Stratum 15 (highest level). Omit the 15 and, if memory serves, the internal clock will be Stratum 4 by default. Since your NTP clients will decriment a Stratum level you'll see them then clocked to your Stratum 4 reference.
I thought the lower the stratum number, the highest priority it hasin NTP - probably helpful in NTP broadcast environment. By setting it to 15 - I thought I was telling other NTP clients out there that this was NOT a 'highly reliable' clock source. Probably wrong on all accounts.....
Guess since this is the only implementation of NTP on the network I should not have cared anyway...
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...