Why architecture comes first
Wireless works only as well as the model behind it. This chapter shows the main ways an Aruba style network can be built.
Analogy: choosing a building plan
Before bricks are laid you decide on one big hall or many small rooms; the choice shapes everything after.
- Two broad models exist: access points tunnelling to a gateway, and access points working on their own under cloud or central management.
- The model decides where traffic is switched, where policy is enforced and what fails together.
- Many real sites mix both: gateways at large campuses, standalone APs at small branches.
- Start from requirements: size, user types, security, budget and staff skills.
- Write the choice and the reasons down so later changes stay consistent.
Requirements pick the model.
A school with one large campus and six small offices uses gateways at the campus and standalone APs at the offices.
Common mistake: choosing a model by habit. The site then carries cost or limits it does not need.
Wrong fit
A small shop runs a large controller design.
Lesson: match the model to size and skills.
What decides the architecture?
Size, security needs, budget and staff skills.
Key takeaways
- Two broad models.
- Model decides traffic path.
- Mixed sites are normal.
- Start from requirements.
- Document the reason.