Wireless Alternate Management Interface Configuration
Dashboard Location: Network-wide > Configure > General > Alternate Management Interface
Wireless Management Network Isolation
Wireless alternate management interface configuration in Meraki networks provides administrators with comprehensive out-of-band management capabilities for wireless access points, enabling management traffic isolation, dedicated management VLAN assignment, protocol-specific routing, and enhanced network security. This functionality supports network segmentation, management traffic separation, administrative access control, and security boundary enforcement. Alternate management interfaces are essential for creating secure management networks, isolating administrative traffic, implementing network access policies, and ensuring reliable management connectivity in enterprise wireless deployments.
Diagram
Classes
wireless (meraki.domains.organizations.networks)
Name | Type | Constraint | Mandatory | Default Value |
---|---|---|---|---|
alternate_management_interface | Class | [alternate_management_interface] | No |
alternate_management_interface (meraki.domains.organizations.networks.wireless)
Name | Type | Constraint | Mandatory | Default Value |
---|---|---|---|---|
enabled | Boolean | true , false | No | |
vlan_id | Any | Integer[min: 1 , max: 4094 ] or String[matches: `(?:[1-9] | [1-9][0-9] | [1-9][0-9]2 |
protocols | List | Choice[ldap , radius , snmp , syslog ] | No | |
access_points | List | [access_points] | No |
access_points (meraki.domains.organizations.networks.wireless.alternate_management_interface)
Name | Type | Constraint | Mandatory | Default Value |
---|---|---|---|---|
alternate_management_ip | IP | Yes | ||
subnet_mask | String | Regex: ^(255|254|252|248|240|224|192|128|0+)(\.0|\.128|\.192|\.224|\.240|\.248|\.252|\.254|\.255){0,3}$ | No | |
gateway | IP | No | ||
dns1 | IP | No | ||
dns2 | IP | No | ||
device | Any | String[matches: ^[A-Z0-9]{4}-[A-Z0-9]{4}-[A-Z0-9]{4}$ ] or String[min: 1 , max: 127 ] | Yes |
Examples
Example-1: The example below demonstrates wireless alternate management interface configuration using tested YAML configuration from pipeline fixtures.
meraki: domains: - name: "!env domain" administrator: name: "!env org_admin" organizations: - name: "!env org" networks: - name: "!env network_name" product_types: - appliance - switch - wireless - camera - sensor - cellularGateway wireless: alternate_management_interface: enabled: true vlan_id: 100 protocols: - ldap - radius - snmp - syslog access_points: - device: "!env ap_01" alternate_management_ip: 1.1.1.1 subnet_mask: 255.255.255.0 gateway: 1.1.1.254 dns1: 8.8.8.8