6.3Network management and performance

A network is not "done" once built—stable operation requires ongoing monitoring and performance management. SNMP-based monitoring is effective for early fault detection, but note that the monitoring mechanism itself can become an attack target—for example, older versions (SNMPv1/v2c) send the community name in plaintext. This section builds the judgment to determine which management approach or configuration suits a given monitoring or performance requirement.

6.3.1SNMP and network management

• SNMP is a protocol for monitoring and controlling the state of network devices. The database of management information held by a managed device is called the MIB (Management Information Base), and each item is uniquely identified by an OID (object identifier).
• Monitoring methods include polling, where the management server periodically queries devices, and traps, where a device proactively notifies the management server when an anomaly occurs. Polling is reliable but detection is delayed by the polling interval; traps are more immediate but a lost notification goes unnoticed. Combining both is the standard practical approach.
• A key security consideration: SNMPv1/v2c use a plaintext community name for authentication, risking eavesdropping and impersonation. SNMPv3 supports authentication and encryption, and the version should be selected according to the trust level of the network the monitoring traffic traverses.