Network Configuration and Maintenance

Overview of Network Maintenance

• Definition and Core Goals: Network maintenance involves a simplified yet critical set of tasks required to ensure the continuous and efficient operation of a network infrastructure.

• Primary Maintenance Tasks:

  • Fixing Network Problems: The process of identifying and resolving network issues to maintain smooth operational flow.

  • Setting up and Configuring Hardware and Software: The physical installation and logical configuration of necessary equipment and software programs required for network functionality.

  • Monitoring and Improving Network Performance: Continuous observation of the network to ensure efficiency, accompanied by making necessary adjustments or improvements.

  • Planning for Future Growth: Anticipating upcoming needs of the network to accommodate future expansion or technological changes.

  • Documenting the Network: Creating and maintaining detailed records, including network diagrams and configuration files, to ensure a comprehensive understanding of the setup.

  • Following Company Policies: Ensuring all network activities and setups comply with internal rules and guidelines established by the organization.

  • Following Legal Regulations: Meeting all legal requirements and government regulations applicable to network operations.

  • Securing the Network: Implementing protective measures to shield the network from threats like unauthorized access, data breaches, or cyberattacks.

Structured vs. Interrupt-Driven Maintenance

• Structured Network Maintenance:

  • Methodology: Utilizes a pre-defined plan to address potential issues proactively before they manifest as failures.

  • Philosophy: Engineers follow a specific maintenance schedule to prevent problems, ultimately making their workload more manageable and predictable.

  • Focus: Proactive approach and implementation of preventive measures.

• Interrupt-Driven Network Maintenance:

  • Methodology: A reactive approach where maintenance is only performed after an issue or problem has occurred.

  • Analogy: Often compared to a "fireman" who waits for an emergency to respond.

  • Drawbacks: Relying exclusively on this method leads to increased network downtime and significantly higher operational costs.

• Advantages of a Structured Approach:

  • Minimized Downtime: A clear strategy reduces the duration and frequency of outages.

  • Cost-Effectiveness: Maintenance activities are planned and executed efficiently rather than in emergency modes.

  • Proactive Troubleshooting: Issues are identified through preventive measures before impacting users.

  • Stability and Reliability: Leads to a consistently high-performing and dependable network infrastructure.

Network Maintenance Models

• Break-Fix Model:

  • A purely reactive approach where technicians are summoned only when equipment fails or problems arise.

  • Lacks proactive monitoring or preventive protocols.

• Preventive Maintenance Model:

  • Focuses on regular, scheduled tasks to avoid potential failures.

  • Key activities include: Routine equipment checks, firmware/software updates, security patching, and regular system backups.

• Predictive Maintenance Model:

  • Uses advanced monitoring and analytics tools to forecast potential failures.

  • Involves the collection and analysis of historical and real-time data to identify patterns and address issues before they occur, thereby maximizing uptime.

The FCAPS Model in Network Maintenance

Network maintenance is categorized into five functional areas defined by the FCAPS model:

• Fault Management: Detection, isolation, and correction of abnormal operations or failures.

• Configuration Management: Identification of managed resources, their physical/logical connectivity, and resource discovery.

• Accounting Management: Tracking usage statistics for the purpose of charging users or groups.

• Performance Management: Monitoring and evaluating the behavior and efficiency of managed resources.

• Security Management: Controlling access to network resources to ensure only authorized users have access.

Detailed Fault Management

• Objective: Managing network problems to ensure reliability and efficiency.

• The Fault Management Process:

  1. Detecting Problem Symptoms: Identifying the initial signs that something is wrong.

  2. Isolating the Problem: Narrowing down the specific cause or location of the fault.

  3. Fixing the Problem: Resolving the issue, either through automated systems (if available) or manual intervention.

  4. Logging: Documenting both the detection and the resolution of the problem for future reference.

Detailed Configuration Management

• Core Function: Monitoring and storing network/system configuration info in a Configuration Management Database (CMDB).

• Database Utility: Allows administrators to track hardware, software, and various network resources over time.

• Device-Specific Information Tracked:

  • Software Versions: Operating system versions, protocol software, and management software data.

  • Hardware Versions: Versions for interfaces and hardware controllers.

  • Contact Information: Identifying the specific person or department to contact if the device fails.

  • Physical Location: The exact geographical or building location of the device.

• Key Maintenance Components:

  • Device Configuration: Setup of parameters, interfaces, and security settings.

  • Configuration Documentation: Maintaining reference materials for troubleshooting.

  • Change Control: Processes to track and authorize changes to device configurations.

  • Version Control: Tracking different configuration versions with the ability to revert to previous states.

  • Configuration Auditing: Regular checks for compliance and vulnerabilities.

  • Backup and Restoration: Regular backups to prevent data loss.

  • Configuration Automation: Utilizing tools to ensure consistency and efficiency in configuration tasks.

Accounting Management

• Purpose: Measures network utilization parameters to regulate individual and group usage.

• Benefits:

  • Minimizes network congestion and problems.

  • Maximizes fairness by portioning resources based on network capacity and specific user needs.

Performance Management

• Objective: Maintaining network performance at acceptable, pre-defined levels.

• Key Variables: Includes network throughput, user response times, and line utilization.

• Basic Steps in Performance Management:

  1. Gathering Data: Collecting info on key performance variables.

  2. Analyzing Data: Determining the normal "baseline" performance levels.

  3. Determining Thresholds: Setting limits for each variable; exceeding these thresholds indicates a problem requiring attention.

• Operational Modes:

  • Reactive Performance Management: When a user-defined threshold is exceeded, the device sends an alert to the Network Management System (NMS).

  • Proactive Performance Management: Uses simulation to project how future network growth will affect performance, alerting admins to impending issues before they impact users.

• Reactive PM Workflow:

  • The management entity monitors variables.

  • If a threshold is crossed, the device or NMS detects the problem.

  • The device generates an alert/trap and sends it to the NMS.

  • The NMS alerts the administrator for action.

Monitoring Tools: Windows Performance Tools

• System Monitor (Performance Console):

  • Tracks counters such as % Processor Time, % Disk Time, Page/sec, and Bytes Received/sec.

  • Data captured includes instance types (e.g., _Total, explorer, 0, C:, D:) and computer source (e.g., \\LONDON).

  • Metrics tracked: Last, Average, Minimum, Maximum, and Duration (e.g., $1:40$).

• Windows Task Manager:

  • Applications Tab: Shows running tasks and their status (e.g., Building Schematic - Paint, Memo to Supervisor - WordPad).

  • Processes Tab: Displays Image Name (e.g., smss.exe, csrss.exe, winlogon.exe, svchost.exe, ntfrs.exe), PID, CPU, CPU Time, and Mem Usage.

  • Performance Tab Statistics:

    • CPU Usage: Visualized as a percentage (e.g., $3\%$ or $6\%$).

    • Memory Usage: Expressed as a ratio (e.g., $103452\,K / 310892\,K$).

    • Totals: Handles ($5932$), Threads ($381$), Processes ($30$).

    • Commit Charge (K): Total ($130612$), Limit ($27740$), Peak ($50704$).

    • Physical Memory (K): Total ($101600$), Available ($310892$), System Cache ($116896$).

    • Kernel Memory (K): Total ($22804$), Paged ($15704$), Nonpaged ($7100$).

Security Management

• Access Control:

  • Prevents intentional or unintentional network sabotage.

  • Protects sensitive information from unauthorized access.

  • Administrator Tasks: Partitioning the network into authorized/unauthorized areas, mapping user groups to these areas, and logging user access.

• Security Monitoring Components:

  • Security Event Collection: Gathering logs and security-related data.

  • Event Analysis and Correlation: Studying events to find patterns of attack.

  • Alert Generation and Handling: Creating and managing responses to security alerts.