09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

timestamps debug> for debug messages. Timestamping logging<br />

messages is important and should be enabled, because it provides <strong>the</strong><br />

time and date <strong>the</strong> event occurred. Timestamping is helpful for debug<br />

messages as well, but in most cases is not required, and when<br />

enabled just adds <strong>to</strong> <strong>the</strong> size of <strong>the</strong> debug message.<br />

IOS Message Logging<br />

Keeping up with what is going on with your router is important.<br />

Logging provides this simple, but essential facility. In most cases, log<br />

information is simply status data, such as changes in <strong>the</strong> router's<br />

interface status, modifications <strong>to</strong> running configuration, and<br />

debugging output. When things are operating smoothly, this data is<br />

nice <strong>to</strong> have. When a problem comes up, however, this data can be<br />

quite valuable. The IOS uses UNIX's syslog logging system <strong>to</strong><br />

generate IOS logging messages. The IOS provides four methods for<br />

viewing logging information:<br />

• Console—The router's console port<br />

• Moni<strong>to</strong>r—The router's system moni<strong>to</strong>r, a VTY "console"<br />

message display<br />

• Trap—Syslog output <strong>to</strong> a remote syslog server running on UNIX<br />

or NT<br />

• Buffer—A place <strong>to</strong> s<strong>to</strong>re a list of logging events in <strong>the</strong> router's<br />

DRAM<br />

By default, all console and moni<strong>to</strong>r methods are enabled, buffer is<br />

disabled, and trap (while set up) needs <strong>to</strong> be configured <strong>to</strong> know<br />

where <strong>to</strong> send its messages.<br />

The trap and DRAM buffer logging methods provide a way <strong>to</strong> s<strong>to</strong>re<br />

logging information. Of <strong>the</strong> two, <strong>the</strong> trap method is more useful for<br />

logging because <strong>the</strong> messages are s<strong>to</strong>red on a remote server. The<br />

buffer approach s<strong>to</strong>res <strong>the</strong> messages in DRAM, which is lost when <strong>the</strong><br />

router is shut down or rebooted. S<strong>to</strong>ring messages in DRAM can also<br />

affect <strong>the</strong> router's performance if your router is tight on shared DRAM<br />

(which is why it is disabled by default). If your router has enough<br />

memory <strong>to</strong> spare, saving logging information on <strong>the</strong> router will not<br />

affect performance. It is helpful <strong>to</strong> have <strong>the</strong> messages accessible on<br />

<strong>the</strong> router, especially when you are trying <strong>to</strong> debug a problem.<br />

Before enabling local logging, check your router's memory usage (see<br />

<strong>the</strong> general info section for command help) after <strong>the</strong> router has been

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!