Recommended Settings for Interoperability with Catalyst APs in URWB Mode

Restrictions on deploying IEC6400 as coordinator (mesh end)

When deploying the IEC6400 as Coordinator or as Mesh end node, ensure these requirements are met:

  • IEC6400 must be deployed only in Layer-2 mobility systems (without a Global Gateway). Legacy URWB Layer-3 architectures that rely on multi-subnet routing and L2TP tunneling are not supported.

  • IEC6400 must be monitored using the FMQuadro interface when it is used as the mesh coordinator.

  • When the IEC6400 operates as the mesh Coordinator, the network topology is not displayed on the controller WebUI and must be monitored through the FMQuadro interface on the IEC6400 unit.

  • If the URWB network includes both Catalyst access points operating as fixed infrastructure and mobility nodes, disable the MPLS reduce-broadcast feature. Disabling this feature prevents association issues for access points that cannot join the controller.

VLAN configuration for Catalyst APs in URWB mode

This section explains how to configure VLANs so that Catalyst APs in URWB mode can communicate with the IEC6400 controller.

It includes:

  • Untagged VLAN setup: configuration steps for the IEC6400, connected Catalyst APs in URWB mode, and switch ports when CAPWAP VLAN Tag feature is not configured on the APs.

  • Tagged VLAN setup: configuration requirements for deployments using CAPWAP VLAN Tag feature on the APs, including the list of allowed VLANs for both the IEC6400 and Catalyst APs in URWB mode.

Make sure wired clients use a VLAN that is different from the controller's VLAN. Update your configurations to maintain network segmentation and connectivity. For configuration instructions, see Add a VLAN for Wired Clients.

Configure untagged VLAN setup

Use this configuration when the Catalyst APs in URWB mode do not use CAPWAP VLAN tags. In this scenario, traffic between the controller and the APs uses the native VLAN.

This configuration is needed when Catalyst APs operate in URWB mode without CAPWAP VLAN tags, requiring native VLAN communication between controller and APs.

Before you begin

To enable communication between Catalyst APs that operate in URWB mode and the IEC6400, enable VLAN functionality on the IEC6400 using the VLAN status enabled command.

Follow these steps to configure untagged VLAN setup:

Procedure

Step 1

Set the management and native VLAN IDs to 1.

  1. Use the VLAN mgm-vid management-ID to set the management ID.

    Example:

    Device# vlan mgm-vid 1

  2. Use the VLAN native-vid native-VLAN-ID to set the VLAN ID.

    Example:

    Device# vlan native-vid 1

Step 2

Configure the switch port connected to the IEC6400 to use the controller VLAN as the native VLAN.

Note

 

The examples given in this section assume that the IEC6400 is connected to the switch port Te1/0/5 and that the controller is on VLAN 87.

  1. Use the interface TenGigabitEthernet interface command on the switch CLI to enter interface configuration mode by specifying the slot and port number of the interface.

    Example:

    Device# interface TenGigabitEthernet 1/0/5

  2. Use the switchport trunk native VLAN VLAN command to configure the native VLAN on a trunk port. This specifies which VLAN will be treated as the default (untagged) VLAN on the trunk.

    Example:

    Device# switchport trunk native vlan 87

  3. Use the switchport trunk allowed VLAN VLAN command to specify which VLANs are allowed to pass through a trunk port. This controls which VLAN traffic can traverse the trunk.

    Example:

    Device# switchport trunk allowed vlan 87

  4. Use the switchport mode trunk command to configure a switch port to operate as a trunk. A trunk port can carry traffic for multiple VLANs between network devices.

    Example:

    Device# switchport mode trunk

Step 3

Configure the switch port connected to the local Catalyst AP in URWB mode.

Note

 

The examples given in this section assume that the Catalyst AP is connected to port Te1/0/9 of the backbone switch.

  1. Use the interface TenGigabitEthernet interface command to enter interface configuration mode by specifying the slot and port number of the interface.

    Example:

    Device# interface TenGigabitEthernet1/0/9

  2. Use the switchport trunk native VLAN VLAN command to configure the native VLAN on a trunk port. This specifies which VLAN will be treated as the default (untagged) VLAN on the trunk.

    Example:

    Device# switchport trunk native vlan 87

  3. Use the switchport trunk allowed VLAN VLAN command to specify which VLANs are allowed to pass through a trunk port. This controls which VLAN traffic can traverse the trunk.

    Example:

    Device# switchport trunk allowed vlan 87

  4. Use the switchport mode trunk command to configure a switch port to operate as a trunk. A trunk port can carry traffic for multiple VLANs between network devices.

    Example:

    Device# switchport mode trunk

  5. Use the spanning-tree portfast command to enable PortFast on a switch port.

    Example:

    Device# spanning-tree portfast

Configure tagged VLAN setup

Use this configuration when the Catalyst APs in URWB mode use a specific CAPWAP VLAN tag, such as VLAN 87, to communicate with the controller.

This configuration allows Catalyst APs operating in URWB mode to communicate with the IEC6400 controller through tagged VLAN traffic on designated switch ports.

Before you begin

To enable communication between Catalyst APs that operate in URWB mode and the IEC6400, enable VLAN functionality on the IEC6400 using the VLAN status enabled command.

Follow these steps to configure tagged VLAN setup:

Procedure

Step 1

Set the management VLAN ID to the Controller's VLAN and native VLAN ID to 1.

Note

 

The examples given in this section assume that the controller is on VLAN 87.

  1. Use the VLAN mgm-vid management-ID command to set the management VLAN ID so that it matches the controller's VLAN.

    Example:

    Device# vlan mgm-vid 87

  2. Use the VLAN native-vid native-VLAN-ID to specify the native VLAN ID.

    Example:

    Device# vlan native-vid 1

Step 2

Configure the switch port connected to the IEC6400 to allow the controller VLAN.

Note

 

The examples given in this section assume that the IEC6400 is connected to the switch port Te1/0/5.

  1. Use the interface TenGigabitEthernet interface command to enter interface configuration mode by specifying the slot and port number of the interface.

    Example:

    Device# interface TenGigabitEthernet 1/0/5

  2. Use the switchport trunk native VLAN VLAN command to configure the native VLAN on a trunk port.

    Example:

    Device# switchport trunk native vlan 87

  3. Use the switchport mode trunk command to configure a switch port to operate as a trunk. A trunk port can carry traffic for multiple VLANs between network devices.

    Example:

    Device# switchport mode trunk

Step 3

Configure the switch port connected to the local Catalyst AP.

Note

 

The examples given in this section assume that the Catalyst AP is connected to port Te1/0/9 of the backbone switch.

  1. Use the interface TenGigabitEthernet interface command to enter interface configuration mode by specifying the slot and port number of the interface.

    Example:

    Device# interface TenGigabitEthernet1/0/9

  2. Use the switchport trunk native VLAN VLAN command to configure the native VLAN on a trunk port. This specifies which VLAN will be treated as the default (untagged) VLAN on the trunk.

    Example:

    Device# switchport trunk native vlan 87

  3. Use the switchport mode trunk command to configure a switch port to operate as a trunk. A trunk port can carry traffic for multiple VLANs between network devices.

    Example:

    Device# switchport mode trunk

  4. Use the spanning-tree portfast command to enable PortFast on a switch port.

    Example:

    Device# spanning-tree portfast

Add a VLAN for wired clients

Wired clients must be on a VLAN different from the controller. To support wired clients on a separate VLAN (for example, VLAN 90), update the switch port configurations to allow the new VLAN.

Procedure

Step 1

Update the switch port connected to the IEC6400 to allow the client VLAN.

  1. Use the interface TenGigabitEthernet interface command to enter interface configuration mode by specifying the slot and port number of the interface.

    Example:

    Device# interface TenGigabitEthernet1/0/5

  2. Use the switchport trunk native VLAN VLAN command to configure the native VLAN on a trunk port. The native VLAN is treated as the default (untagged) VLAN on the trunk.

    Example:

    Device# switchport trunk native vlan 87,90

  3. Use the switchport mode trunk command to configure a switch port to operate as a trunk. A trunk port carries traffic for multiple VLANs between network devices.

    Example:

    Device# switchport mode trunk

Step 2

Update the switch port connected to the local Catalyst AP to allow the client VLAN.

  1. Use the interface TenGigabitEthernet interface command to enter interface configuration mode by specifying the slot and port number of the interface.

    Example:

    Device# interface TenGigabitEthernet1/0/9

  2. Use the switchport trunk native VLAN VLAN command to configure the native VLAN on a trunk port. This specifies which VLAN will be treated as the default (untagged) VLAN on the trunk.

    Example:

    Device# switchport trunk native vlan 87,90

  3. Use the switchport mode trunk command to configure a switch port to operate as a trunk. A trunk port can carry traffic for multiple VLANs between network devices.

    Example:

    Device# switchport mode trunk

  4. Use the spanning-tree portfast command to enable PortFast on a switch port.

    Example:

    Device# spanning-tree portfast