Management
Device Management
Covers the protocols and practices used to manage, monitor, and maintain network devices, including time synchronization, logging, monitoring, and secure file transfer.
What you need to know
- NTP synchronizes device clocks; a device can be a client, server, or peer, and stratum number indicates distance from the reference clock (stratum 0).
- Syslog severity levels range from 0 (emergencies) to 7 (debugging); the default IOS console logging level is debugging (7).
- SNMPv1/v2c use plaintext community strings for authentication; SNMPv3 adds user-based security with authentication and optional encryption (authPriv, authNoPriv, noAuthNoPriv).
- SCP (Secure Copy) transfers files over SSH and requires the device to be configured as an SCP server with AAA authorization for file transfer.
- CDP is Cisco-proprietary and works only between Cisco devices; LLDP is an open IEEE standard (802.1AB) usable in mixed-vendor environments.
- show running-config vs show startup-config: running-config is the active memory (RAM) config, startup-config is saved to NVRAM and used on reload.
- Configuration changes are saved with copy running-config startup-config (or write memory) to persist across a reload.
Configuration commands
| Command | Mode | Purpose |
|---|---|---|
| ntp server <ip> | config | Configure the device to synchronize time from an NTP server. |
| clock timezone <name> <offset> | config | Set the local timezone relative to UTC. |
| logging host <ip> | config | Send syslog messages to an external syslog server. |
| logging trap <level> | config | Set the severity level of messages sent to the syslog server. |
| snmp-server community <string> RO | config | Configure a read-only SNMPv2c community string. |
| snmp-server group <name> v3 priv | config | Create an SNMPv3 group requiring authentication and encryption. |
| snmp-server user <user> <group> v3 auth sha <pw> priv aes 128 <pw> | config | Create an SNMPv3 user with authentication and privacy credentials. |
| ip scp server enable | config | Enable the device as an SCP server for secure file transfer over SSH. |
| copy running-config startup-config | exec | Save the active configuration to NVRAM. |
| copy scp: flash: | exec | Securely copy a file from an SCP server to local flash. |
Verify it
- show ntp status
- show ntp associations
- show logging
- show snmp
- show snmp user
- show clock detail
Common mistakes
- Not configuring a timezone or NTP, causing syslog timestamps to be inaccurate or inconsistent across devices.
- Using SNMPv2c community strings in a lab meant to demonstrate SNMPv3 security.
- Forgetting AAA authorization for exec/network needed for SCP file transfers to succeed.
- Saving configuration to startup-config before verifying the running-config is correct, locking in a mistake after reload.
- Confusing logging trap level numbers, sending too little or too much detail to the syslog server.
Practise Device Management in a real CLI
Generated labs, graded against the simulated network state.