Cisco AS5800 Specifications Page 142

  • Download
  • Add to my manuals
  • Print
  • Page
    / 334
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 141
4-4
Cisco AS5800 Operations, Administration, Maintenance, and Provisioning Guide
DOC-7810814=
Chapter 4 Administration
Enabling Management Protocols: NTP, SNMP, and Syslog
An NTP enabled network usually gets its time from an authoritative time source, such as a Cisco router,
radio clock, or an atomic clock attached to a timeserver. NTP then distributes this time across the
network. NTP is extremely efficient; no more than one packet per minute is necessary to synchronize
two machines to within a millisecond of each another. NTP runs over UDP, which in turn runs over IP.
Step 1 Locate an authoritative clock source. For example, you can use a Cisco router or an atomic clock that is
attached to a time server.
Step 2 Specify the primary NTP server IP address and automatic calendar updates as shown below:
!
ntp update-calendar
ntp server 172.22.66.18 prefer
!
Step 3 Verify that the clock is synchronized to the NTP server. Inspect the status and time association.
Clock sources are identified by their stratum levels. The following example shows a stratum level five
clock.
5800-NAS# show ntp status
Clock is synchronized, stratum 5, reference is 172.22.66.18
nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**24
reference time is BB944312.4451C9E7 (23:11:30.266 PDT Wed Sep 22 1999)
clock offset is 0.5343 msec, root delay is 13.26 msec
root dispersion is 18.02 msec, peer dispersion is 0.09 msec
5800-NAS#
The following command identifies how often the NAS is polling and updating to the stratum clock.
An asterisk (*) next to the NTP servers IP address indicates successful synchronization with the stratum
clock.
5800-NAS# show ntp association
address ref clock st when poll reach delay offset disp
*~172.22.66.18 172.60.8.1 16 46 64 377 1.0 0.53 0.1
* master (synced), # master (unsynced), + selected, - candidate, ~ configured
5800-NAS#
Enabling Syslog
The Cisco IOS software can send syslog messages to one or more element manager servers. Syslog
messages are then collected by a standard UNIX or NT type syslog daemon.
Syslog enables you to:
Centrally log and analyze configuration events and system error messages such as interface status,
security alerts, environmental conditions, and CPU process overloads.
Capture client debug output sessions in a real-time scenario.
Reserve Telnet sessions for making configurations changes and using show commands.
This prevents Telnet sessions from getting cluttered up with debug output.
Figure 4-2 shows the Cisco IOS software sending syslog data to an element manager. Syslog data either
stays in the Cisco IOS software buffer, or is pushed out and written to the element managers hard disk.
Page view 141
1 2 ... 137 138 139 140 141 142 143 144 145 146 147 ... 333 334

Comments to this Manuals

No comments