# airec-network

Part of **AIREC**

<!-- intent-backlink:auto -->

> 💡 **Path Selection**: This skill is one implementation path for [Configure network for AIRec deployment](../../intent/airec-configure-airec/SKILL.md). If you're unsure which path to take, check the routing skill first.

# AIRec Network Configuration Console Guide

## Operations Overview

| Operation | Console Entry | Prerequisites | Description |
|-----------|---------------|---------------|-------------|
| Check In-Band Switch Auto-Configuration Status | Not applicable (verification via logs/script) | Switch has cleared its configurations, Switch has restarted during network bootstrap deployment | Verify whether an in-band switch automatically obtained its configuration using DHCP and bootstrap.py |
| Configure Out-of-Band Network | Apsara Stack Deployment Planner > Network Connection | Access to Apsara Stack Deployment Planner, Project and version selected in the planner | Download and load OSW/OMR switch configuration files for out-of-band management network setup |
| Configure IP Address Pool | Console > Network Connection > Configure IP Address Pool | AZone already set up, Access to the AIRec console with appropriate permissions | Define IP address segments, manage anycast-related pools, and complete global and cluster planning |

## Operation Steps

### Check In-Band Switch Auto-Configuration Status

**Navigation**: Not applicable — this is a verification procedure performed on the switch itself after reboot.

**Prerequisites**:
- Switch has cleared its configurations
- Switch has restarted during network bootstrap deployment

1. Ensure the switch reboots and initiates POAP/ZTP/Zero Configuration process.
   - Notes: The switch uses DHCP to obtain a temporary IP address and downloads **bootstrap.py** from Apsara Infrastructure Management Framework.

2. Confirm that **u_launcher.py** executes successfully on the switch.
   - Notes: Successful execution indicates the switch has automatically acquired its configuration.

3. Review system logs or console output on the switch to verify configuration download and application.
   - Notes: No console UI interaction is required; this operation is validated through switch-side logging.

**Form Fields**: None

### Configure Out-of-Band Network

**Navigation**: Apsara Stack Deployment Planner > Network Connection

**Prerequisites**:
- Access to Apsara Stack Deployment Planner
- Project and version selected in the planner

1. Locate the target project and version in the main content area.
   - Element: **project and version** (text_input) — main content area

2. Navigate to the Network Connection page.
   - Element: **Network Connection** (link) — left navigation panel

3. Download the switch configuration file.
   - Element: **Download Switch Configuration File** (button) — main content area
 - Notes: The UI label appears as “--” (Zhuque - Network Connection - Download Switch Configuration File)

4. Decompress the downloaded archive and identify .cfg files prefixed with **OSW** and **OMR**.
   - Notes: These files are used for out-of-band switch configuration. If using OPS#1 and OPS#2 with 2C model, verify LSW anycast configuration.

5. Manually load the OSW and OMR .cfg files onto their respective physical switches.
   - Notes: This step occurs outside the console (via switch CLI or management interface).

**Form Fields**: None

### Configure IP Address Pool

**Navigation**: Console > Network Connection > Configure IP Address Pool

**Prerequisites**:
- AZone already set up
- Access to the AIRec console with appropriate permissions

1. Hover over a connection line in the network topology diagram to view connection relationships.
   - Element: **Move the mouse over a connection** (hover) — network topology diagram

2. Double-click a pod module to drill into its detailed topology.
   - Element: **pod module** (clickable element) — network topology diagram

3. Click any network device to inspect local-to-peer port connections.
   - Element: **network device** (clickable element) — network topology diagram

4. Return to the parent topology view.
   - Element: **Return** (button) — top navigation bar

5. Switch to the out-of-band network view.
   - Element: **Switch To Out-Of-Band Network** (button) — top navigation bar

6. Open the IP allocation interface.
   - Element: **IP Address Allocation** (button) — upper-right corner of the page

7. Configure IP address segments and select ignore options for anycast pools.
   - Element: **IP address pool configuration form** (text_input) — tab page
   - Notes: Subnet mask for NTP/DNS/YUM anycast VIP must be /30. Ignore DMZ VPC CIDR and owner VPC CIDR IP pools.

8. Save and trigger IP allocation.
   - Element: **Save And Allocate IP Addresses** (button) — bottom of the form
   - Notes: The system automatically allocates IPs after saving.

9. Proceed to the Global Configuration page.
   - Element: **Next** (button) — bottom of the page
   - Notes: Values here are read-only; use **Edit Global Variables** elsewhere to modify.

10. Export the site-wide configuration file.
    - Element: **Export site.csv** (button) — bottom of the page
    - Notes: **site.csv** contains region-wide global variables shared across projects.

11. Advance to the Cluster Configuration page.
    - Element: **Next** (button) — bottom of the page

12. Accept the system-generated cluster identifier.
    - Element: **Automatically Generated** (radio) — cluster configuration section
    - Notes: Modification is discouraged; default value is recommended.

13. Finalize the planning workflow.
    - Element: **Completed** (button) — bottom of the page
    - Notes: Upon completion, the system prompts to export plan data.

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| IP address segments | text_input | Yes | — | Enter IP address segments based on the number of segments required. |
| Ignore anycast-related IP address pools | checkbox | No | — | Select to exclude anycast-related pools such as DMZ VPC CIDR and owner VPC CIDR. Default is checked. |

## FAQ

Q: Where can I find the option to configure IP address pools in the AIRec console?
A: Navigate to **Console > Network Connection**, then click **IP Address Allocation** in the upper-right corner of the page.

Q: What should I do if I don’t see OSW or OMR files after downloading the switch configuration package?
A: Ensure you’ve selected the correct project and version in Apsara Stack Deployment Planner. The files are included only when out-of-band network configuration is part of the deployment plan.

Q: Can I modify the IP address pool after clicking **Save And Allocate IP Addresses**?
A: Yes, but you must return to the IP Address Allocation page and reconfigure before finalizing the plan. Once **Completed** is clicked, changes require restarting the planning workflow.

Q: Do I need special permissions to access the Network Connection page?
A: Yes, you need appropriate console permissions granted by your administrator to view and configure network settings in AIRec.

Q: Is the in-band switch configuration check performed inside the AIRec console?
A: No. This verification is done on the physical switch by inspecting logs or script execution after reboot during POAP/ZTP bootstrap.

## Pricing & Billing

### Billing Model
Free — no usage-based charges apply for network configuration operations in AIRec.

### Free Tier
No usage-based charges mentioned; network configuration features are included in the base service tier.

### Billing Notes
No billing details are provided in the documentation. All described operations are part of the standard deployment workflow with no additional cost.