Managing a cisco router syslog
View PDF | Print View
by: Admin
Total views: 75
Word Count: 311
Among the keys to a well managed cisco router syslog is having the router properly configured to log events to the proper level, and having the log exported appropriately to protect it from loss. The idea of proper varies from one business to the next, and on how the router is being employed in a network. The role of the router can dictate how the cisco router syslog should be configured, as the data may need to reflect the traffic being carried by the router.
This should be established by an engineer who is familiar with how a cisco router syslog should be ideally set up, and by someone intimately aware of your network and its layout. A cisco router syslog is also vulnerable to loss, being volatile in nature by design on the router itself. Most network engineers establish some form of centralization for all of they cisco router syslog data, so that each router does not have to be logged into to access the log information stored on it. There are limited ways to view the log data when viewed directly on the router, so exporting the cisco router syslog will open up a whole other level of parsing and analysis capabilities, making the data far more useful than just raw log entries.
Exporting the cisco router syslog also allows the data to survive a reboot of the router or a loss of power. There is also limited space for the cisco router syslog on the router device itself, as there is not a huge amount of space provided with the intent of providing archiving capabilities built right into the router. The cisco router syslog can be archived permanently, however, if it is being stored on a server that has a sufficient amount of hard disk space to do so.
About the Author
Find more info regarding syslog analysis, visit this web page I found.
Rating: Not yet rated