Configures URWB network settings and parameters using the wireless controller interface. This process enables centralized management and deployment of ultra-reliable wireless backhaul profiles for optimized connectivity in mission-critical environments.
Create URWB network profile (GUI)
A URWB Network Profile is a configuration framework designed to enable the setup of an Ultra-Reliable Wireless Backhaul (URWB) network for APs. This profile allows APs to form a wireless mesh network with enhanced reliability, performance, and security.
Complete these steps to configure URWB network profile:
Procedure
The URWB network profile is created.
Configure URWB network profile (CLI)
Configure the URWB network key in the URWB pofile. The URWB profile is a wireless profile type that contains the URWB configuration parameters. All the APs with the same site-tag are configured with the URWB configurations defined in the URWB profile.
Complete the following steps to create a URWB network profile and configure the URWB network key:
Procedure
The URWB network profile is created and the network key is configured in the wireless profile.
Example
Device# configure terminal
Device(config)# wireless profile urwb urwb-profile-name
Device(config-wireless-urwb-profile)# strong-network-key
Device(config-wireless-urwb-profile)# network-key network-key-type 0 <network-key>
Device(config-wireless-urwb-profile)# no shutdown
Device(config-wireless-urwb-profile)# exit
Configure URWB mobility backhaul check (CLI)
Procedure
The URWB mobility role and backhaul check is configured.
Example
Device# configure terminal
Device(config)# wireless profile urwb urwb-profile-name
Device(config-wireless-urwb-profile)# mobility role {base| base-relay | client}
Device(config-wireless-urwb-profile)# [no] mobility backhaul-check coordinator-down {handoff-inhibition | relay-switch}
Device(config-wireless-urwb-profile)# [no] mobility backhaul-check eth-down {handoff-inhibition|relay-switch}
URWB Backhaul Check
The Backhaul Check feature monitors the connectivity status of infrastructure (base/base_relay) units' wired Ethernet ports and/or mesh-end connectivity. When backhaul connectivity is lost, the feature prevents mobile units from handing off to that infrastructure unit. This process ensures that traffic is not routed to a 'dead end' in the network.
Purpose
In a Fluidity/URWB network, infrastructure units (track-side radios) provide wireless coverage to mobile units (vehicle radios). These infrastructure units typically connect to the wired network via Ethernet. If an infrastructure unit loses its wired backhaul connection, it becomes a 'black hole.' Mobile units could connect to it wirelessly, but their traffic would have no path to the network.
Standard (Ethernet Port) Backhaul Check vs. Mesh-End Backhaul Check
This feature supports two operational modes: Standard Backhaul Check and Mesh-End Backhaul Check.
Standard Backhaul Check
What it monitors: The physical Ethernet port status on the infrastructure unit itself.
Use case: The infrastructure unit has a direct wired Ethernet connection to the backbone network. If that cable or port fails, the unit has no backhaul.
Mesh-End Backhaul Check
What it monitors: The logical reachability to the mesh-end (coordinator) via the wired AutoTAP probing mechanism — essentially checking if a pseudowire path to the coordinator still exists.
Use case: The infrastructure unit does NOT have a direct Ethernet connection to the backbone. Instead it reaches the network through a chain of other infrastructure units (e.g., a base-relay daisy chain). Even if its own Ethernet port is operational or does not exist, the path to the coordinator or mesh-end may be broken further upstream.
Configure URWB mobility MPO parameters (CLI)
Procedure
The URWB mobility MPO parameters are configured.
Example
Device# configure terminal
Device(config)# wireless profile urwb urwb-profile-name
Device(config-wireless-urwb-profile)# [no] mobility mpo enable rx-only
Device(config-wireless-urwb-profile)# mobility mpo path 4
Device(config-wireless-urwb-profile)# mobility mpo rssi 4
Device(config-wireless-urwb-profile)# [no] mobility mpo telemetry
Configure URWB mobility scan parameters (CLI)
Before you begin
The mobility scan parameters are strictly connected to the channel list configuration. Together with this parameter, you must also configure the channel list for scanning. To configure the channel list, see the Configure URWB channel list (CLI) section.
Procedure
The URWB mobility scan parameters are configured.
Example
Device# configure terminal
Device(config)# wireless profile urwb urwb-profile-name
Device(config-wireless-urwb-profile)# mobility scan {isolation scan-wait-time 0-65535| periodic scan-period 0-65535 | rssi-threshold threshold-value 0-96}
Device(config-wireless-urwb-profile)# no mobility scan isolation
Device(config-wireless-urwb-profile)# no mobility scan periodic
Configure URWB MPLS parameters (CLI)
Procedure
The URWB MPLS parameters are configured.
Example
Device# configure terminal
Device(config)# wireless profile urwb urwb-profile-name
Device(config-wireless-urwb-profile)# [no] mpls ether-filter ethertypes filtering allow-all
Device(config-wireless-urwb-profile)# [no] mpls ether-filter ethertypes allow-list add 50
Device(config-wireless-urwb-profile)# [no] mpls ether-filter ethernet-I
Device(config-wireless-urwb-profile)# mpls high-availability
Device(config-wireless-urwb-profile)# mpls high-availability timeout 54
Device(config-wireless-urwb-profile)# [no] mpls high-availability
Configure multicast for URWB profile (CLI)
Procedure
The URWB multicast settings are configured.
Example
Device# configure terminal
Device(config)# wireless profile urwb urwb-profile-name
Device(config-wireless-urwb-profile)# multicast coordinator-only
Device(config-wireless-urwb-profile)# [no] multicast
Limitations and guidelines for secondary Ethernet ports
When deploying secondary Ethernet ports, observe these constraints:
-
Redundancy Impact : Activating the secondary Ethernet port disables dual-Ethernet redundancy (backup mode).
-
VLAN Configuration: The primary and secondary Ethernet ports must share an identical VLAN configuration.
-
State Changes: Any modification to the secondary port state (enabled or disabled) requires a device reboot for the change to take effect.
-
Model-Specific Restrictions: For the Cisco Catalyst 9124AX Series model, the third port (LAN1) is limited to client connections or daisy-chaining and cannot operate as a root port.
-
Mobility Infrastructure Limitation: In a mobility-configured network with two mesh-end devices, the mobility infrastructure must be deployed using a ring topology. The two mesh-end APs must be positioned as the first and last APs in the ring and must be directly connected to the controller. Additionally, both mesh-end APs are required to reach the controller through the same wired port, designated as the root port, to ensure proper network operation and failover capabilities.
Configure secondary Ethernet port (GUI)
Configure the secondary Ethernet port to enable wired client connectivity and optional PoE functionality.
From release 26.2.1, the URWB stack supports permanently enabling two wired interfaces, allowing independent management of Wired0 and Wired1 ports and enabling daisy-chaining or mesh ring deployments without external switches. This feature restores parity with standalone Industrial Wireless software and enhances flexibility and cost efficiency in URWB deployments. Enable optional PoE on the secondary Ethernet port to provide wired client support and power to downstream devices.
Before you begin
Ensure that your access point model supports configuration of a secondary Ethernet port and Power over Ethernet (PoE). Only the Cisco Catalyst 9124AX series supports PoE on port ID 2.
Procedure
What to do next
-
Navigate to Monitoring > Wireless > AP Statistics on the wireless controller interface.
-
Select the specific AP under the General tab to access its detailed statistics.
-
Click the URWB sub-tab to confirm that the secondary Ethernet configuration changes have been correctly applied after the device reboot.
Hot configuration support is limited to changing the mapping of the secondary URWB port to a different physical port (e.g., from LAN1 to LAN2).
Configure secondary Ethernet port (CLI)
Configure the secondary LAN port ID on compatible Cisco access points. Enable optional PoE on the secondary Ethernet port to provide wired client support and power to downstream devices.
Before you begin
-
Identify the correct LAN Port ID for your hardware (supported range: 1 to 4). You can use the show interface status command in privileged EXEC mode to list the LAN Port IDs of the device.
-
Ensure that your access point model supports configuration of a secondary Ethernet port and Power over Ethernet (PoE). Only the Cisco Catalyst 9124AX series supports PoE on port ID 2.
Procedure
Create URWB radio profile (GUI)
The URWB wireless radio profile is used to configure a particular radio slot for the URWB backhaul operation. The URWB wireless radio profile, when applied to a radio interface on a device, is relevant only if the device is in the URWB mode.
To set up a backhaul link with URWB, configure the URWB radio profile to a radio interface. Follow these steps to create a URWB radio profile:
Procedure
What to do next
Assign the URWB profiles to the wireless RF tag.
Create RF tags and assign profiles (GUI)
Complete these steps to create RF tags and assign profiles:
Create URWB radio profile (CLI)
Complete the following steps to configure the URWB radio profile:
Procedure
The URWB radio profile is created.
Example
Device# configure terminal
Device(config)# wireless profile radio urwb-radio-profile-name
Device(config-wireless-radio-profile)# urwb channel 5ghz 120
Device(config-wireless-radio-profile)# urwb cwidth 160MHz
Device(config-wireless-radio-profile)# urwb role fixed
Device(config-wireless-radio-profile)# exit
Configure URWB point-to-multi-point parameters (CLI)
Complete the following steps to configure the URWB fixed point-to-multi-point (PTMP) parameters:
Procedure
The URWB PTMP parameters are configured.
Example
Device# configure terminal
Device(config)# wireless profile radio urwb-radio-profile-name
Device(config-wireless-radio-profile)# urwb ptmp cluster-id cluster-id
Device(config-wireless-radio-profile)# [no] urwb ptmp autoscan
Device(config-wireless-radio-profile)# [no] urwb ptmp tower-id tower-id
Device(config-wireless-radio-profile)# [no] urwb ptmp rssi-threshold threshold-value
Configure URWB encryption parameters (CLI)
Complete the following steps to configure the URWB encryption parameters:
Procedure
The URWB encryption parameters are configured.
Example
Device# configure terminal
Device(config)# wireless profile radio urwb-radio-profile-name
Device(config-wireless-radio-profile)# urwb crypto policy {none | fixed-key | rotating-key}
Device(config-wireless-radio-profile)# urwb crypto rotating-key-timeout 120
Configure URWB channel list (CLI)
Complete the following steps to configure the URWB channel list for mobility scanning:
Procedure
The URWB channel list is configured for mobility scanning.
Example
Device# configure terminal
Device(config)# wireless profile radio urwb-radio-profile-name
Device(config-wireless-radio-profile)# [no] urwb chan-list channel 100 cwidth 40MHz
Create RF tags and assign profiles (CLI)
Complete the following steps to map the radio profile to RF tag and radio slot:
Procedure
The RF tags are created and assigned to the URWB profiles.
Example
Device# configure terminal
Device(config)# wireless tag rf rf-profile-name
Device(config-wireless-rf-tag)# urwb-profile urwb_profile
Device(config-wireless-rf-tag)# dot11 5ghz slot1 radio-profile urwb-radio-profile-name
Device(config-wireless-rf-tag)# exit
In the RF tag configuration, if you assign radio profiles on 2 radio slots in 5-GHz band (dot11 5ghz slot# radio-profile profile-name . Following restrictions apply:
The channels configured are separated by 100 MHz.
The channels cannot be in the same UNII2 Ext channels.
What to do next
-
Assign the URWB coordinator role to one of the APs.
-
Configure URWB DFS parameters.
-
Assign the URWB Fixed Base role to the selected APs.
Configure URWB parameters in the privileged EXEC mode
The URWB parameters in the EXEC mode are Fixed Base and Fixed Point-to-Multipoint.
-
Fixed Base in a point-to-multipoint topology, is the radio selected by the clients to connect to. Clients only connect to Fixed Base radios.
-
If Fixed Point-to-Multipoint is enabled, at least one AP has to be configured as a Fixed Base.
Configure URWB parameters per radio (GUI)
Complete the following steps to configure URWB parameters per radio:
Procedure
The URWB parameters are configured per radio.
Configure URWB parameters in the privileged EXEC mode (CLI)
Procedure
The URWB parameters are configured in the privileged EXEC mode.
Example
Device# ap name Cisco-AP dot11 5ghz slot slot-number urwb ptmp base
Device# ap name Cisco-AP no dot11 5ghz slot slot-number urwb ptmp base
Device# ap name Cisco-AP dot11 5ghz slot slot-number urwb dfs {auto | primary | secondary}
Device# ap name Cisco-AP urwb mode coordinator
Device# ap name Cisco-AP no urwb mode coordinator
Device# ap name Cisco-AP urwb mode coordinator radio-off fixed
Verify URWB details
Verify URWB profile details
To display the profile details specific to a URWB profile, use the following command:
Device# show wireless profile urwb detailed urwb-profile
Verify details about specific wireless radio profile
To display details about specific wireless radio profile, including the URWB information, use the following command:
Device# show wireless profile radio detailed radio_profile_name
Verify URWB details for a specific AP
To display the URWB details for a specific AP, use the following command:
Device# show ap name ap_name urwb info
Verify the configuration status from a URWB AP
To display the configuration status from a URWB AP, use the following command:
Device# show ap urwb status
Verify URWB details for an AP in a radio band
To display the URWB details for an AP in a radio band, use the following command:
Device# show ap name Cisco-AP dot11 band slot slot-id urwb detail