500-430 Pre-Deployment Planning

Pre-Deployment Planning Detailed Explanation

Objective:

Pre-deployment planning ensures that a wireless network is designed to meet user needs and environmental constraints. This phase minimizes potential issues during deployment and ensures smooth operation afterward.

1. Requirements Analysis

This step identifies the purpose of the wireless network and ensures it meets the needs of users and devices.

1. Number and Type of Devices:

   • Why is this important? Each device connected to the network consumes bandwidth and resources. Knowing the number of devices helps you estimate the capacity required.

   • What should you consider?

     • Smartphones, tablets, and laptops: These are the most common devices and typically require moderate bandwidth for internet browsing and email.
     • IoT devices (e.g., smart lights, cameras, sensors): These often have specific requirements, like low latency or high reliability, even if their bandwidth usage is low.
     • Heavy users: Video conferencing and online streaming consume large amounts of bandwidth.

   • How to plan?

     • Categorize devices based on their expected use (e.g., staff laptops vs. guest smartphones).
     • Estimate the total number of devices and their peak usage times. For example, in an office, peak usage might occur during meetings with video calls.

2. Application Needs:

   • Why is this important? Different applications have varying bandwidth and quality requirements.
   • Examples:
     • Video streaming (e.g., YouTube, Netflix): Requires high bandwidth and low latency to avoid buffering.
     • Voice calls (e.g., Zoom, Teams): Needs low latency and jitter for clear audio.
     • Web browsing and emails: Requires moderate bandwidth and is less sensitive to delays.
   • How to plan?
     • List all the applications expected to run on the network.
     • Determine their bandwidth requirements. For instance, a 1080p video stream may need 5 Mbps per device, while web browsing requires less than 1 Mbps.

3. User Density Evaluation:

   • Why is this important? High-density areas (e.g., meeting rooms, auditoriums) need more APs to ensure adequate coverage and capacity.
   • How to plan?
     • Identify areas with many simultaneous users, like conference rooms or cafeterias.
     • Calculate the number of users each AP should support. For example, an AP might efficiently support 25-50 users, depending on their activities.

2. Site Survey

A site survey examines the physical environment where the wireless network will be deployed. It helps identify potential issues with signal strength, coverage, and interference.

1. Physical Site Assessment:

   • Why is this important? Building materials and layout can significantly affect wireless signal strength.
   • What to check?
     • Walls: Concrete and brick walls absorb signals more than wood or drywall.
     • Obstructions: Large furniture or equipment (e.g., metal filing cabinets) can block or reflect signals.
     • Ceilings: High ceilings may require specialized AP placement or mounting brackets.
   • How to plan?
     • Walk through the building with a map, marking potential problem areas.
     • Decide on AP placement based on open spaces and areas where signal strength is critical.

2. Heatmap Generation:

   • Why is this important? A heatmap visually represents signal strength across an area, helping you see where coverage is strong or weak.
   • Tools:
     • Ekahau: A popular professional tool for generating heatmaps.
     • NetSpot: A beginner-friendly option.
   • How to use these tools:
     • Place an AP at a planned location, then measure signal strength at various points in the area.
     • Adjust AP placement until the heatmap shows adequate coverage (signal strength above -65 dBm).

3. Interference Analysis:

   • Why is this important? Nearby devices or networks can interfere with your Wi-Fi signal, reducing performance.
   • Potential interference sources:
     • Other Wi-Fi networks on overlapping channels.
     • Non-Wi-Fi devices like Bluetooth headsets or cordless phones.
     • Physical devices like microwaves or fluorescent lights.
   • How to mitigate interference:
     • Use a spectrum analyzer to detect interference sources.
     • Choose frequencies and channels that are least affected by interference.

3. Spectrum Planning

Spectrum planning optimizes the use of available frequencies to maximize performance and minimize interference.

1. Channel Selection:

   • Why is this important? Wi-Fi operates in specific frequency bands (e.g., 2.4 GHz and 5 GHz). Proper channel selection avoids interference and improves network reliability.
   • How to plan?
     • 2.4 GHz Band: Use non-overlapping channels (1, 6, and 11).
     • 5 GHz Band: Offers more channels and less interference, ideal for high-density environments.
   • Example: For an office with three APs, assign each AP a different channel to minimize overlap.

2. Power Planning:

   • Why is this important? Too much signal power can cause interference between APs, while too little power may leave dead zones.
   • How to plan?
     • Start with moderate power settings and adjust based on coverage needs.
     • Use automatic power adjustment features in modern APs.

3. Dynamic Channel Allocation (DCA):

   • Why is this important? Wi-Fi environments change over time (e.g., new networks, temporary interference). DCA helps the network adapt to these changes.
   • How to configure DCA:
     • Enable this feature in the wireless controller.
     • Set parameters for how frequently channels are adjusted (e.g., daily or weekly).

4. Regulatory Compliance

Regulatory compliance ensures the network adheres to local laws and standards.

1. Frequency Usage Restrictions:

   • Why is this important? Different regions have specific rules for Wi-Fi frequency bands and power levels.
   • Examples:
     • The FCC in the US regulates maximum power and allowed frequency bands.
     • The ETSI in Europe imposes stricter limits on outdoor APs.
   • How to comply:
     • Use region-specific firmware for your APs.
     • Avoid using prohibited channels or exceeding power limits.

2. Security Standards:

   • Why is this important? Secure networks protect sensitive data and prevent unauthorized access.
   • Key security measures:
     • WPA3 Encryption: The latest Wi-Fi encryption standard, ensuring strong data protection.
     • 802.1X Authentication: Provides enterprise-level authentication using RADIUS servers.
   • How to implement:
     • Configure these security features during AP setup.
     • Ensure all user devices support the chosen security protocols.

Summary

Pre-deployment planning is the foundation of a successful wireless network. By analyzing requirements, conducting a thorough site survey, planning the spectrum, and adhering to regulations, you can ensure reliable coverage and optimal performance. As a beginner, focus on understanding each step and using tools like heatmap generators to visualize and refine your plan.

Pre-Deployment Planning (Additional Content)

1. Application & Architecture Assessment

Purpose:

Before deploying AppDynamics, it is essential to understand the nature and structure of the target application. This helps determine which agents are needed and how they should be configured.

Key Components:

• Application Architecture Type:

  • Determine whether the application is monolithic or microservices-based.

  • Identify the programming platforms involved (e.g., Java, .NET, Node.js, Python).

  • In a microservices environment, instrumentation often involves multiple tiers and containerized environments like Docker or Kubernetes.

• Communication Topology:

  • Define the network path between AppDynamics agents (e.g., Java Agent, Machine Agent) and the Controller.

  • Ensure bidirectional communication is possible if required (especially for on-premises deployments).

• Supported Components:

  • List which AppDynamics components are needed:

    • Application Agent (e.g., Java Agent, .NET Agent)

    • Machine Agent (for infrastructure metrics)

    • Database Agent (for backend database monitoring)

    • Browser RUM / Mobile RUM (for end-user experience)

  • This determines installation targets and priorities.

2. Sizing & Capacity Planning

Purpose:

Proper sizing prevents performance degradation and ensures scalability as your monitoring footprint grows.

Key Components:

• Controller Sizing:

  • Estimate the number of applications, business transactions, nodes, and tiers.

  • Use Cisco’s or AppDynamics’ official sizing calculators for Controller and Events Service requirements.

• Data Retention Policy:

  • Define how long metrics, events, snapshots, and logs will be stored:

    • Example: metrics retained for 8 days, events for 30 days.

  • This affects disk usage and Controller performance.

• Resource Estimation:

  • Calculate required CPU, memory, disk space, and network bandwidth based on expected workload.

  • Include contingency for performance spikes or onboarding new applications.

3. Network & Security Requirements

Purpose:

Ensure all AppDynamics components can communicate securely and reliably across the network.

Key Components:

• Required Network Ports:

  • Confirm availability of critical ports such as:

    • 8090 / 443 – Controller communication

    • 389 – LDAP if directory services are used

    • 20xx–4xxx – Dynamic port range for Java Agents

• Firewalls & NAT:

  • Validate whether there are firewalls or NAT gateways between Agents and the Controller.

  • NAT may require special handling for Agent registration or name resolution.

• Security Configuration:

  • Define if SSL certificates will be used (AppDynamics supports custom or self-signed certificates).

  • Set role-based access controls (RBAC) in the Controller UI.

  • Plan access restrictions to the Controller, especially in production environments.

4. Integration Planning

Purpose:

Plan ahead for how AppDynamics will integrate with your existing IT ecosystem and automation pipelines.

Key Components:

• Third-Party System Integration:

  • Identify integrations with:

    • ITSM tools like ServiceNow or JIRA for ticket automation

    • Incident response platforms like PagerDuty

• API Usage Planning:

  • Will you use AppDynamics REST APIs to:

    • Automate alert generation

    • Pull monitoring data into dashboards (e.g., Grafana)

    • Integrate with CI/CD tools (e.g., Jenkins)

• Authentication Considerations:

  • API access may require access keys, OAuth tokens, or client credentials, depending on deployment type (SaaS vs. on-prem).

5. Risk Assessment & Rollback Plan

Purpose:

Mitigate risk by preparing fallback mechanisms and ensuring a smooth transition from any existing monitoring tools.

Key Components:

• Parallel Deployment:

  • Consider running AppDynamics in parallel with your existing APM or monitoring platform during an evaluation phase.

  • This helps you validate visibility and tune configuration without impacting production monitoring.

• Rollback Strategy:

  • Define clear steps for removing or disabling Agents in case of unexpected application behavior or performance impact.

  • Ensure logs and configurations are backed up so agents can be safely re-enabled later.

• Failure Scenarios:

  • Plan for how to handle:

    • Controller downtime (failover setup)

    • Agent crashes or incompatibility

    • Performance impact on monitored applications

Summary

Effective Pre-Deployment Planning for AppDynamics ensures:

• The right agents are selected and properly scoped

• The infrastructure can handle the expected load

• Network and security are correctly configured

• Integration and automation are ready

• Rollback is possible without business risk