9167E configuration guide in unified platform

[QW_netzwerk]

As far as I have understand the newer 17.18.2 software version on 9800 wlc It is possible to configure the 9167E as URWB. So I have the following questions:

• When i want to use on a single 9167E AP simultaneously as URWB and for WiFi for the clients does the AP, does the AP boot version should be URWB?
• Does the each radio role has to be defined under RF tag for the URWB?
• How the other radio will be configured where the end points will be connected?

Is there any configuration guide is available? 

Thanks in advance.

[Jens Albrecht · Accepted solution]

Hello @QW_netzwerk,

Since IOS XE 17.18.1, the Catalyst 9167E must boot in URWB mode to use both URWB backhaul and Wi‑Fi client access simultaneously. 
You configure each radio’s role under an RF Tag → URWB Profile, while the non‑URWB radio is managed through normal WLAN tags for client access.

There are configuration guides as well as a Youtube video if you are interested:

Cisco Catalyst 9800 Series Wireless Controller Software Configuration Guide, Cisco IOS XE 17.18.x

Cisco Ultra-Reliable Wireless Backhaul for Catalyst IW Access Points, Software Configuration Guide, Release 17.18.x

Episode 65: URWB Comes To The 9800 In IOS-XE 17.18.1

HTH!

[QW_netzwerk]

Hey, thanks a lot for your help. The links you have shared have answered almost all my queries I just have one question about mobility. Should an AP connected to wired be configured as based and the AP mounted on a movable vehicle be configured as a client under the mobility tab?

[Jens Albrecht]

Yes, the wired AP must be configured as Base, and the moving AP on the vehicle configured as Client.

[Rich R]

Am I missing something @QW_netzwerk and @Jens Albrecht ? 17.18.2 has not been released yet - it's currently in beta/EFT.
If you are part of the beta/EFT then you might want to remember you've signed NDA so should not be discussing it in public forums and all questions about it should be directed to the beta/EFT team.

[Jens Albrecht]

These changes were introduced with release 17.18.1 and are officially documented as everyone can see based on the links provided above. No secrets at all, all information is publicly available.

[Rich R]

I am very well aware of 17.18.1 @Jens Albrecht 
I am questioning your references to 17.18.2 ?
Or was that a typo and you didn't bother to check what you wrote in response to my question?

[Jens Albrecht]

I changed the wording of my post but still don't get your point as none of the links reference 17.18.2 in any way. There simply are no references to 17.18.2. So really no clue at all what the problem is.
If it is forbidden to mention the simple existence of new versions, then some moderator should have edited to original question immediately after this thread got created.