Introducing Simultaneous Wi-Fi and CURWB

In this previous blog, we discussed the Cisco CURWB architecture, where Cisco CURWB required a dedicated infrastructure using devices like the IW9167 and IW9167-APs. The good news is that Cisco has now introduced a unified solution: Cisco wireless can now support both Wi-Fi and Ultra-Reliable Wireless Backhaul on a single hardware platform, bringing URWB functionality into a unified architecture.

Introducing Simultaneous Wi-Fi and URWB

The question you might have is: why is this important?

This new innovation allows the use of one Access Point variant that can run both Wi-Fi and CURWB: no need to duplicate APs any longer. CURWB is used for devices such as vehicle automation that need very low latency - now two devices are combined into one.

ASSOCIATED BLOGS:


Why is CURWB Important?

There is a slight terminology difference between the standard CURWB architecture and Cisco’s Unified URWB approach. In the unified model:

  • The Mesh End Gateway is now called the Coordinator.
  • The MeshPoint (whether fixed or vehicle-based) is now referred to as a Node.

Role selection happens per radio or slot, and all radio types can support Wi-Fi. URWB is currently available only on the 5 GHz and 6 GHz bands (2.4 GHz is not supported yet). This functionality starts with IOS-XE 17.18.1 and does not require a separate AP mode, making deployment much simpler. All configuration and management are centralized through the Wireless LAN Controller (WLC).

Key highlights of the unified architecture:CURWB Blog 2_2

  • Single software image – no need to dual-boot separate URWB and Wi-Fi images.
  • URWB can be enabled per radio or per AP without requiring a dedicated mode.
  • Supported on APs running both Local and FlexConnect mode.
  • All URWB/WGB APs are managed by the 9800 WLC.
  • The standalone URWB architecture will continue to be supported.

CURWB Blog 2_1

Image copyright Cisco Systems

ASSOCIATED BLOGS:


Supported Hardware

There's a range of hardware that you can run URB - see the image below:

CURWB Blog 2_3

Image copyright Cisco Systems

ASSOCIATED BLOGS:


How to configure Wireless/URWB using 9800 WLC

The Cisco 9800 WLC is the core of any Cisco wireless network and is the central point in managing the URB and Wi-Fi installs:

CURWB Blog 2_4

Image copyright Cisco Systems

As many of you know, the Cisco 9800 WLC uses a profile- and tag-based configuration model. Starting from version 17.18.1, a new option called the URWB Network Profile is introduced.

All URWB settings—such as radio roles and channel configurations—are applied within this profile. The URWB Network Profile can then be linked to the RF Tag, alongside the standard RF profiles for 2.4 GHz, 5 GHz, and 6 GHz.

CURWB Blog 2_5

Image copyright Cisco Systems

We previously discussed the MPLS Gateway, which served as the connection point between the wireless and wired networks for all mesh points in a standard CURWB deployment.

In the unified architecture, this role is replaced by the Coordinator. The following explains how to configure the coordinator role on a Cisco 9800 WLC.

CURWB Blog 2_6

Image copyright Cisco Systems


Licensing

URWB functionalities are included as part of the current DNA or Unified Licensing model. For Wi-Fi 6, Wi-Fi 6E, and Wi-Fi 7 platforms, the required license depends on the deployment type. URWB fixed infrastructure (point-to-point links) requires DNA Essentials or Cisco Wireless Essentials, while URWB mobility (mobile assets) requires DNA Advantage or Cisco Wireless Advantage.

URWB design guidelines:

  • 6 GHz standard power (requiring AFC) is not supported on URWB radios.
  • L3 architectures are not supported; all APs in the same URWB network must be in the same Layer 2 domain (mostly affects mobility deployments).
  • 6 GHz LPI for mobile assets is supported in the US only (not in Australia).
  • URWB is limited to two or fewer 5 GHz or 6 GHz radios per AP.
  • SD-Access (Wireless Fabric) is not supported, URWB is supported as part of an SDA underlay.
  • URWB supports only one wired network port per AP.
  • URWB cannot split VLANs at the AP port; a switch is required.
  • IW Monitor has limited URWB support, with more functionality coming in IW Monitor 3.0.
  • URWB is subject to processing throughput ceilings, which vary by platform

ASSOCIATED BLOGS:


Cisco Ultra-Reliable Wireless Backhaul Explained: Summary

Cisco has made things easier by combining Wi-Fi and Ultra-Reliable Wireless Backhaul (URWB) into one platform. No more separate hardware or software—everything runs on a single image and is managed through the 9800 Wireless LAN Controller.
 
URWB works on 5 GHz and 6 GHz bands starting with IOS-XE 17.18.1, and setup is simpler thanks to the new URWB Network Profile. There are a few name changes too: the Mesh End Gateway is now called the Coordinator, and MeshPoint is now a Node.
 
Licensing is included under Cisco DNA, and while some design limitations still apply, this unified approach makes deployment much more straightforward.

If you'd like to talk to us about undertaking CURWB for your business, drop us a line on our quote request form: https://info.iptel.com.au/request-a-quote 

Free Quote

 

Need Help with your Network Install?

If you’re looking for a partner to help you through the future of networking – or to help you work through the maze of how to upgrade your network, we're here to help.

Contacting us is easy:

We are experts in network design and especially Wi-Fi design and remediation and Cisco ISE. If you're ready to take the plunge, we're ready to help you with DNA Center and SDA too. 

IPTel Solutions - Experts in Network Engineering Excellence

 

Click to Download "Top 8 Secrets to Great Wi-Fi"