# Ampere Server Platforms

```{include} common-alert-enablement.md
```

This guide covers the setup and configuration of Ampere server platforms, including:
- **AmpereOne Server Platform** - Uses USB TTY serial connection with fan noise reduction
- **Altra® Max AC02** - Uses IPMI SOL (Serial Over LAN) connection

## Components

The following components are required to fully automate Ampere servers:

### For AmpereOne
- [LAA (Linaro Automation Appliance)](/generality/laa.md)
- USB to TTY serial cable
- Network cables for private network and IPMI connections
- Power control via IPMI

### For Altra Max AC02
- Network cables for private network and IPMI connections
- Power control via IPMI
- SOL (Serial Over LAN) via IPMI

## Firmware Requirements

### GRUB Configuration

Both platforms require a properly configured GRUB bootloader with network boot capabilities:

- **Required modules**: `net_bootp`, `tftp`
- **Architecture**: aarch64/arm64
- **Firmware location**: `https://firmwares.lavacloud.io/grubaa64.efi`

The GRUB firmware must be installed on the server's EFI system partition and configured as the primary boot option.

## Platform-Specific Configuration

### AmpereOne Server Platform

The AmpereOne platform has specific considerations:

1. **Serial Connection**: Uses `telnet localhost 2010` for serial console access via USB TTY
   - More reliable than IPMI SOL for this platform
   - Requires USB serial adapter connected to LAA

2. **Fan Noise Reduction**: The platform includes IPMI raw commands to reduce fan noise:
   ```bash
   ipmitool -I lanplus -H <BMC_IP> -U ADMIN -P ADMIN raw 0x3c 0x03 0x01
   for i in $(seq 0 10); do
       ipmitool -I lanplus -H <BMC_IP> -U ADMIN -P ADMIN raw 0x3c 0x04 $i 0x1e
   done
   ```
   These commands are automatically executed during hard reset operations.

3. **USB Control**: LAA USB port 2 is used for additional control:
   - `laacli usb 2 off` - Disable USB port
   - `laacli usb 2 on` - Enable USB port

### Altra Max AC02

The Altra Max AC02 platform configuration:

1. **Serial Connection**: Uses IPMI SOL for console access
   ```bash
   ipmitool -I lanplus -H <BMC_IP> -U ADMIN -P ADMIN sol activate
   ```

2. **Boot Delay**: Configured with a higher boot character delay (500ms) for stability

3. **Standard IPMI Power Control**:
   - Power on: `ipmitool -I lanplus -H <BMC_IP> -U ADMIN -P ADMIN power on`
   - Power off: `ipmitool -I lanplus -H <BMC_IP> -U ADMIN -P ADMIN power off`
   - SOL deactivation on power off for clean disconnection

## Network Configuration

### BMC/IPMI Network Setup
The BMC (Baseboard Management Controller) must be configured with a static IP address:
- **Required static IP**: `198.18.0.3`
- **Default credentials**: `ADMIN/ADMIN` (should be changed in production)

### LAA Private Network
The LAA provides a private network with DHCP:
- **DHCP range**: Provides `198.18.0.2` to the DUT (Device Under Test)
- **LAA IP**: `198.18.0.1` (gateway and TFTP server)

### Network Switch Configuration
To allow the LAA private network to communicate with both the IPMI interface and the DUT, you need one of the following:

1. **Dumb/Unmanaged Switch** (Simplest option):
   - Connect LAA private network port
   - Connect server's primary network interface (DUT)
   - Connect server's IPMI/BMC network interface
   - All devices will be on the same 198.18.0.0/24 network

2. **Managed Switch with VLAN** (For larger deployments):
   - Configure a dedicated VLAN for the test network
   - Add the following ports to the VLAN:
     - LAA private network port
     - Server DUT network port
     - Server IPMI/BMC port
   - Ensure all ports are untagged/access ports for this VLAN

### Network Connectivity Requirements
- LAA must reach IPMI at `198.18.0.3` for power control
- LAA must reach DUT at `198.18.0.2` for TFTP boot and testing
- DUT receives DHCP from LAA at `198.18.0.1`

## GRUB Setup Instructions

1. **Download the GRUB firmware**:
   ```bash
   wget https://firmwares.lavacloud.io/ampere/grubaa64.efi
   ```

2. **Copy to EFI partition** (from a booted Linux system on the server):
   ```bash
   mount /boot/efi
   cp grubaa64.efi /boot/efi/EFI/BOOT/BOOTAA64.EFI
   ```

   The GRUB firmware is should now drop to a `grub>` prompt, allowing LAVA to take control and execute network boot commands directly.

## Troubleshooting

### AmpereOne Fan Noise
If the AmpereOne server fans are running at high speed:
1. Verify the IPMI raw commands are being executed during reset
2. Check BMC firmware version for compatibility
3. Consider adjusting the fan control parameters in the raw commands

### Serial Console Issues
- **AmpereOne**: Verify USB serial cable connection and telnet port (2010)
- **Altra Max**: Check IPMI SOL configuration and network connectivity

### Network Boot Failures
1. Verify GRUB has the required network modules
2. Check DHCP/TFTP server configuration on the LAVA worker
3. Ensure BMC and target networks are properly segregated

## Additional Resources

- [LAA Documentation](/generality/laa.md)
- [LAVA Device Dictionary Documentation](https://docs.lavasoftware.org)
- [Ampere Computing Documentation](https://www.amperecomputing.com/docs)