Getting Started with Configuration

This topic describes how to get started with configuration in HPE Aruba Networking Central.

Prerequisites

The following are the prerequisites before onboarding devices to HPE Aruba Networking Central:

  • Device onboarding requires Classic Central.

  • Greenfield provisioning is handled in HPE Aruba Networking Central configuration.

  • Devices onboarding to HPE Aruba Networking Central must be in the Factory Default mode.

  • All devices must be assigned to a site and device function when onboarding in HPE Aruba Networking Central.

Minimum Firmware Requirements

  • Access Point—10.4.1.7

  • AOS-CX—10.13.1110

  • AOS-S—16.11.0028

  • Gateway—10.4.1.6

Limitations

  • Brownfield migration is not supported.

  • The system internal-vlan-range and single local user CLIs are removed from the device when it is moved from Greenfield+ to the CNX site.

Planning the Network

This topic describes how to plan the network.

Note:

The scenarios listed in this topic are provided for the purpose of best practices, and not intended to enforce a specific network design. Administrators have autonomy to design the network as applicable, and are not required to implement the scenarios provided.

Recommendations

  • Pre-stage profiles to expedite provisioning.

  • Use Library profiles for configurations required across hierarchy and multiple device types.

  • Use Local Profiles for configurations unique to a particular device function and/or scope in the hierarchy.

Identifying the Deployment Model

This topic describes the following deployment models:

Standardized Model

The standardized design also known as a "cookie cutter" or "uniform" deployment model is when the configuration is shared across all sites and device types (switch, AP, gateway). The design is commonly deployed in branch sites. This topic covers the following scenarios:

Cookie Cutter

Common configurations (for example, NTP, DNS, AAA, SNMP, Syslog, VLAN, WLAN SSID, and so on) are identical across all sites and devices (switch, AP, gateway).

Table 1: Cookie Cutter Recommendation

Item

Recommendation

Profile Type

 Library

Scope for deployment

 Global

Uniform with SSID Variations

Common configurations (for example, NTP, DNS, AAA, SNMP, Syslog, VLAN, and so on) are identical across all sites and device types (switch, AP, gateway), however WLAN SSID varies amongst sites or subset of sites.

Table 2: Uniform with SSID Variations Recommendation

Item

Recommendation

Profile Type

 Library

Scope for deployment

 Global and Site Collection

Uniform with Time Zone Variations

Common configurations (for example, NTP, DNS, AAA, SNMP, Syslog, VLAN, and so on) are identical across all sites and device types (switch, AP, gateway), but time zone varies amongst sites or subset of sites.

Table 3: Uniform with Time Zone Variations Recommendation

Item

Recommendation

Profile Type

 Library

Scope for deployment

 Global

Non-Standardized Model

The non-standardized design model also known as "unique" is when the configuration varies per site, device (switch, AP, gateway), or both. This topic covers the following scenarios:

Configuration Varies per Site with Shared Device Configurations

Common configurations differ per site but shared across device types (switch, AP, gateway).

Table 4: Configuration Varies per Site with Shared Device Configurations Recommendation

Item

Recommendation

Profile Type

 Library

Scope for deployment

 Site and Site Collection

Configuration Varies per Site and Device

Common configurations differ per site and per device type (switch, AP, gateway).

Table 5: Configuration Varies per Site and Device Recommendation

Item

Recommendation

Profile Type

 Local

Scope for deployment

 Site and Site Collection

Infrastructure Model

An infrastructure design model is commonly deployed on core, backbone, or data center standalone devices. Examples of infrastructure devices include but are not limited to core switch, aggregation switch, or data center firewalls. These devices often require advanced configurations that are not shared among other sites or devices. However, common system configurations such as AAA, NTP, DNS, and so on, are the exception to shared configurations depending upon the design model. This topic covers the following scenarios:

Advanced Configuration with Shared Common Configurations

Table 6: Advanced Configuration with Shared Common Configurations Recommendation

Item

Recommendation

Profile Type

 Library and Local

Scope for deployment

 Device and Site

Advanced Configuration without Shared Common Configurations

Table 7: Advanced Configuration without Shared Common Configurations Recommendation

Item

Recommendation

Profile Type

 Local

Scope for deployment

 Device and Site

High Availability Model

The high availability design model is commonly deployed on node redundant devices. Examples of high availability devices include but are not limited to VSF stack, VSX pair, or gateway clusters. These devices share configurations amongst two devices or more.

Table 8: High Availability Model Recommendation

Item

Recommendation

Profile Type

 Library or Local

Scope for deployment

 Device Group or Site

Designing the Hierarchy

Before the Day 1 provisioning, it is best practice to evaluate the network design and determine which scopes align with the deployment model. A scope in HPE Aruba Networking Central refers to the blast radius of where the configuration is applied. Global, Site, and Device are mandatory levels in the hierarchy, while Site Collection and Device Group are optional constructs.

Figure 1: Scope Use Cases

Figure 2: Configuration Hierarchy Architecture