- Add sites/BCN01-LAB with full Meraki configuration: VLANs, SSIDs,
switch ports, 802.1X policy, firewall rules, WAN uplinks and warm spare
- Extend modules/meraki-site to support wan2_* fields in mx_wan_uplinks
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
La API de Meraki exige virtual_ip2 cuando WAN2 está activo.
Se usa la IP DHCP actual del primary (10.212.169.132) como VIP WAN2.
Pendiente: hacer reserva DHCP para estabilizar esa IP.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
El campo no está expuesto en el provider CiscoDevNet/meraki v1.9.0.
Solo se usan los campos de IP estática soportados por el recurso.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Configura meraki_appliance_warm_spare con VIP flotante en WAN1:
- Spare: BCN01-F04-MX02 (serial resuelto por nombre)
- Uplink mode: virtual
- VIP WAN1: 213.229.159.148
La IP de salida del tráfico será siempre la VIP (.148),
independientemente de qué MX esté activo.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Igual que con los switches, el serial del MX se resuelve dinámicamente
usando data.meraki_network_devices (device_serials local). El tfvars
ahora usa el campo 'name' en lugar de 'serial'.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Añade recurso meraki_device_management_interface para configurar
IP estática en el puerto WAN1 de ambos firewalls MX:
- Primary: 213.229.159.145/28 (255.255.255.240), GW 213.229.159.147
- Spare: 213.229.159.146/28 (255.255.255.240), GW 213.229.159.147
Los seriales del MX deben reemplazarse en wan.auto.tfvars.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
La API de Meraki requiere encryption_mode="wpa" cuando auth_mode="psk",
además de wpa_encryption_mode. Sin este campo la API devuelve el error
"Pre-shared key mode requires a valid encryption mode (wep, wpa)".
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Puerto 3 eqt-lab-st01-sw01: trunk, native 108 (APs), tagged 100+101
- VLAN 111 WAN sin subnet ni appliance_ip (switching puro)
- subnet/appliance_ip pasan a ser opcionales en el módulo
- Add data source meraki_switch_stacks to resolve member serials by stack name
- Add switch_stack_port_configs variable: specify stack_name + port_range
instead of individual switch serials
- Terraform applies port_range to ALL members of the stack automatically
- Merge switch_port_configs and switch_stack_port_configs into all_ports local
- Add example for bcn01-lab-stack01 (2x48p) in switch.auto.tfvars
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Replace port_id with port_range in variable; add local to expand ranges
into individual port entries before creating meraki_switch_port resources.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Add meraki_switch_access_policy resource to module (multi-auth, critical VLAN)
- Add meraki_switch_port resource for per-port policy assignment
- Add switch_access_policies and switch_port_configs variables to module and site
- Create switch.auto.tfvars for BCN01-LAB with 802.1X-CORPO policy
(RADIUS: 15.15.15.15:1912, critical VLAN: 100, host_mode: Multi-Auth)
- switch_port_configs starts empty; add serial + port_id to assign policy to ports
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Rename sites/bcn01/ -> sites/BCN01-LAB/
- Update S3 backend key: bcn01/terraform.tfstate -> BCN01-LAB/terraform.tfstate
- Rename Terraform module: bcn01 -> bcn01_lab
- Update working-directory in apply.yml and plan.yml
- Update job/step names to BCN01-LAB
NOTA: mover manualmente en S3 el objeto
bcn01/terraform.tfstate -> BCN01-LAB/terraform.tfstate
antes de hacer terraform init en el nuevo directorio.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
