Introdução ao Gerenciamento de Redes - parte 1

Main ideas / lessons conveyed

• Network management is essential because managers need to understand:
  • how employees/teams perform,
  • how network equipment behaves,
  • how devices interconnect,
  • and whether systems reliably support projects and services on a company network and the internet.
• A networked organization contains many devices (often hundreds or thousands). Without documentation, it becomes difficult to identify where failures originate.
• Good management relies on knowing:
  • network topology
  • device roles and interconnections
  • current and historical performance
  • logs and time synchronization
  • monitoring + alerting
  • problem documentation and continuous improvement

Methodology / process (step-by-step, as presented)

1. Know the network topology well

   • Maintain diagrams showing how devices are interconnected and organized.
   • Keep documentation describing each device’s function and its relationships to other components.
   • Maintain an inventory of equipment.

2. Use backups for important configurations

   • Implement automatic backups of critical equipment configurations (e.g., servers, routers).
   • Store history of changes.
   • Generate alerts on unauthorized changes.
   • Support restoration if a planned change causes unexpected side effects.

3. Establish a performance baseline (“standard behavior”)

   • Track normal operating metrics such as:
     • speed, bandwidth
     • availability
     • CPU and memory usage
   • Learn typical/expected values and how they vary over time (day-to-day).

4. Collect and visualize historical data

   • Use tools to collect network/service data and store it over time.
   • Present data in graphs to:
     • identify cyclical patterns,
     • reveal long-term increases/decreases,
     • determine whether a parameter is abnormal.
   • Use historical trends to plan actions early, such as:
     • renegotiating internet/transit contracts if link usage is steadily rising,
     • addressing decreasing disk space before it becomes critical.

5. Centralize and analyze logs

   • Devices produce logs containing:
     • user access,
     • program access,
     • important events,
     • errors.
   • Store logs on a central server to retain investigation evidence.
   • This supports forensic analysis even if a device is later compromised.

6. Synchronize device clocks

   • Ensure all equipment uses synchronized time via NTP.
   • Use a standard time zone (example given: “TC”).
   • Benefits:
     • consistent log timestamps,
     • easier cross-referencing across systems,
     • identification of cause-and-effect relationships using topology + baseline.

7. Monitor the network continuously

   • Monitoring tools check whether:
     • equipment,
     • services,
     • applications
     • are working correctly.
   • Monitoring modes:
     • Passive monitoring: collects data already produced during normal operation.
     • Active monitoring: tool generates additional traffic to test/evaluate system behavior.
   • Also include tools that automatically analyze logs for anomalies.

8. Compare monitoring data to standard metrics and alert quickly

   • Collected data is compared against baseline/standard parameters.
   • If a problem is detected, tools send alerts via:
     • visual notifications,
     • audible alarms,
     • email,
     • SMS,
     • instant messaging platforms, etc.
   • Goal: enable rapid action to correct issues.

9. Identify common types of network problems

   • Device failures (most common)
   • Security problems (e.g., attempted intrusions)
   • Capacity problems / bottlenecks, caused by:
     • gradual growth in usage exceeding equipment capability,
     • temporary abnormal events increasing workload.

10. Diagnose using topology + baseline + history

    • Use:
      • alert details,
      • network topology,
      • normal operating parameters,
      • historical graphs and logs
    • to find the root cause and correct it quickly.
    • If needed, use manual testing tools to further validate hypotheses.

11. Improve processes and document incidents

    • Use organizational documentation (described as analogous to:
      • job descriptions and process diagrams) to find efficiency improvements.
    • Maintain a system to document each addressed problem:
      • enables control and tracking,
      • helps build a knowledge base.
    • Use the knowledge base to detect recurring issues likely caused by structural flaws, then:
      • replace insufficient equipment,
      • adjust/change network topology to better distribute traffic.

Sources / speakers featured

• nickbr (referenced as the creator; also mentioned as the channel to watch more videos)
• Background audio: [Music] (no specific performer identified)