Network Device Management Flashcards
Syslog Message Format
Full format
Seq no:time stamp: %facility-severity-MNEMONIC:description
Seq no
Optional sequence number
Time stamp
Time of event
%facility
The thing that generated the event
Severity
The severity level
MNEMONIC
Short description of what happened
Description
A more detailed description of what happened
Syslog Severity Levels
0 = Emergency
System is unusable. A panic condition
1 = Alert
A condition that should be corrected immediately
Ex: corrupted system database
2 = Critical
Critical conditions, such as hard device errors
3 = Error
Error conditions
4 = Warning
Warning conditions
5 = Notice
Normal but significant conditions. Not errors, but may require special handling
6 = Informational
Informational messages
7 = Debug
Messages that contain info normally of use only when debugging a program
Logging Locations
Console Line
—Events will be shown in the CLI when you are logged in over console connection
—All events logged by default
VTY Terminal Lines
—Events will be shown in CLI when you are logged in via Telnet/SSH
—Not enabled by default
The logging buffer
—Events saved in RAM, you can review them with the “show logging” command
—All events logged by default
External Syslog servers
Specifying Severity Levels to Log
You can specify the same or different severity levels to log for each location
All messages of that severity level & higher will be logged
Example:
If you set a logging level of 3 for the console
It will log 0, 1, 2, & 3 events
If you set a logging level of 7 for an external Syslog server
Events from all severity levels 0-7 will be logged there
Command: Disable logging on the console line
no logging console
Command: Events with severity level informational & higher will be logged to VTY lines
logging monitor 6
Command: Events with severity level 7 & higher will be logged to the buffer
Logging buffered debugging
Logging to an External Syslog Server (With configuration)
You can log to an external Syslog server to centralize event reporting
You will typically set verbose logging to provide detailed troubleshooting info
Configuration
Logging 10.0.0.100
Logging trap debugging
SIEM
Security Information & Events Management:
A basic Syslog server provides a centralized location for Syslog logging messages
SIEMs provide a centralized location for all logging messages
—And typically provide advanced analysis & correlation of events
Command: View logging buffer
show logging
Logging Synchronous
When working in a CLI session, by default any syslog messages will be printed into the middle of any commands you are currently typing
—Super annoying
To Override:
Logging synchronous
This causes a new line to be printed where you were in the command
Debug & Terminal Monitor
Commands:
-Enable debug output to VTY lines
-Turn off debug
Show & Debug commands can be used to view specific info over & above the standard syslog messages
Show output shows a static point in time state
Debug output dynamically updates in real time
Be careful with debug commands in production environments
—A large amount of output can overwhelm a device
Debug output is logged to the console line & buffer by default
Enable debug output to VTY lines:
Terminal monitor
Turn off debug:
Undebug all
Or you can abbreviate to “u all”
SNMP
Simple Network Management Protocol:
SNMP is an open standard for network monitoring
SNMP Manager/Server/NMS
SNMP Manager | SNMP Server | NMS (Network Management System):
Can collect & organize info from an SNMP Agent
Can pull info from the device (Get)
—Ex: Manager could query traffic statistics from device
Or the device can push it to the server (Trap)
—Ex: Device reports HSRP state change
SNMP Agent
Software which runs on managed devices (routers, switches)