Hreap and spectralink

Hi
We're currently deploying a wireless network and I've come across a problem.
We're going to be using Polycom/Spectralink handsets and I've set a wlan up according to spectralinks documentation including the setting the multicast mode to multicast but when I do this the message "H-REAP supports 'unicast' mode only" appears.
We were planning deploying H-Reap APs to remote locations but this message suggests that we'd have to deploy an additional controller for this.
Can anyone confirm if there is another way to do this?
Thanks
Martin

To start, the basic difference between Multicast > Multicast, and Multicast > Unicast, is how the packet is handeled. In MM, when the WLC gets a packet, it sends a single reply to the multicast group address that is configured, this is the group the AP's will join. In MU, the WLC sends a packet to each AP. The only real difference is that MU is more network intense then MM is.
Part of my normal trouble shooting, is if Multicast is not working and it's configured for MM, we'll change to MU, and test. If it works in MU, then we know we have to look at multicast routing issues.
HTH

Similar Messages

HREAP and Remote Office VLAN

We have a corporate office which we have a 5508 WLC and 2 WiSMs (v7.0.116) and WCS (v7.0.172) and rolling out remote offices which will have 2 or 3 APs (1142N). I setup the first remote office with wireless using HREAP and its working well. Configuring the WLAN for the remote office we select an interface we created with the VLAN at the remote office and now that we are preparing for the next remote office can I use the same VLAN for the second office? For example, we are using local switching for a WLAN using VLAN 6 and will need the same at the second remote office.
Thanks for any help.
Jeff

if you are user FlexConnect, and are on 7.2 or better code on the WLC.
http://www.cisco.com/en/US/docs/wireless/controller/7.2/configuration/guide/cg_flexconnect.html#wp1247954
If you are not using FlexConnect, which you said you weren't, the traffic doesn't get locally switched. it all is handeld at the WLC.
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

Mobility between HREAP and NON HREAP does not work..

HREAP Local Switch and Auth has been enabled on SSID.
Indoor AP is in HREAP mode.
Outdoor AP does not support HREAP mode.
Client connects to indoor AP....continous PING breaks after client roams to outdoor AP. The state of the client is RUN.
Disable HREAP Local Auth and the issue goes away. Why?

Without HREAP config, you will not be able to do local-auth on the AP
The design guid says roam between a HREAP and non-HREAP will not work,
Thanks
NikhiL

HREAP and Dynamic VLAN assignment (MS NPS)

Hi All
Just a quick rundown of what I am trying to achieve.
We have a Cisco 5508 WLC (running AIR-CT5500-K9-7-0-116-0.aes). At the moment the WLC is controlling only 1 AP (Cisco 1142N LWAP). I want this AP to be placed at a remote site, and users that authenticate via the RADIUS (MS Windows 2008 NPS) server must be assigned their respective VLANs based on the Active Directory groups they belong to (staff, student, or guest).
The AP and dynamic VLAN assignment works 100% if the AP is in local mode. Authentication works, and dynamic VLAN assignment works. As soon as you change the AP to HREAP mode, dynamic VLAN assignment stops working, and the client gets assigned an IP of whatever VLAN is assigned to the SSID under the HREAP tab. Allow AAA Override is enabled on the main SSID that I am broadcasting.
I have read in some of the discussions that HREAP does not support dynamic VLAN assignment, but I haven't seen why this is not supported. Is this true with the latest version of WLC software as well? I cannot see why local traffic destined for a local resource must be sent via a WAN link to the controller, and then back over the WAN link again. This seems very inefficient.
Is there anybody that can confirm if this is in fact an HREAP limitation, and why (if so) it is a limitation, please? Any info would be much appreciated.
Regards
Connie

Do you perhaps know if there are plans for this limitation being addressed in the near future?
We are looking to deploy wireless from end-to-end in all 6 of our sites, and you biggest competitor was penalized because they do not support this feature. It seems we're going to have to apply the same penalty in this respect to Cisco as well.
Thanks for the feedback, though!
Regards
Connie

HReap and Mesh

We have many sites using HReap successfully and I am now setting up a site that needs Mesh for extra distance. The Mesh works fine and if i plug a device into the child it gets a dhcp and works no problem, but laptop devices cannot get a dhcp address from the APs via wireless. Im guessing this is because the wireless isnt HReap. Can you Mesh and connect wireless clients to the APs on remote sites.

Typically when using mesh, you will have a RAP that is wired into the network and a MAP that connects to the RAP. Now the newer code allows you to have a mesh ap in H-REAP mode but it does require an Ethernet connection. A MAP needs to connect back to a RAP though. This is how mesh is designed.
Sent from Cisco Technical Support iPhone App

HREAP and DHCP

Hi All,
I have a Cisco 4402 wireless controller and I am trying to set up HREAP to dump traffic off locally. I have the HREAP function working as I can see my wireless MAC address on the correct vlan in the MAC table on various switches. The problem, the Wireless NIC isn't recieving a DHCP address. I have verified that my pool is operational. I connected a laptop to the same switch that the WAP is connected to and it pulls an IP address from that VLANs DHCP pool.
What am I missing? Another question is what interface to I set up for this WLAN? If it is going to be at a remote office, what should it be set to?
Thanks,
Chris

I went to go add a virtual interface on VLAN 14 and that brought down my access to the WLC. I rebooted and now I can pull IP addresses at my office. I have this WLAN in my Corporate office and now it is working just fine. I have now applied this WLAN to a remote office WAP (will be using the same vlan, just differnet subnet) and it won't pull an IP address. Again, I can see the MAC address on the swtich that is directly connected to the router with the IP Helper address and it still can't pull an IP address. This is a different switch from which the WAP is connected. If I plug a laptop into the same switch that the WAP is connected to, it pulls an IP address not problem.

Difference between HREAP and Local AP

I am interested to know if there is any difference between HREAP (centrally switched, centrally authenticated) with normal local AP.
As I can see all the traffic from the AP will still go through the controller to at the central site.

Hybrid Remote Edge Access Point (H-REAP) is a wireless solution for branch office and remote office deployments. It enables customers to configure and control access points in a branch or remote office from the corporate office through a wide area network (WAN) link without deploying a controller in each office. The H-REAP access points can switch client data traffic locally and perform client authentication locally when the connection to the controller is lost. When connected to the controller, H-REAPs can also tunnel traffic back to the controller.

HREAP and Multicast traffic

I have a controller sat on a network (10.10.10.0/24) with a management address of 10.10.10.250. There's a distant site we have at the other side of the network with a range at 192.168.0.0/24. I have 5 thin HREAP access points on this network with three WLANs from the controller and one WLAN delivered via a trunk point with VLAN 2 tagging (the 192.168.0.0/24 network is VLAN1). The VLAN2 (e.g. 172.16.0.0/24) network is basically an untrusted network to us , but I didn't think this would matter as the HREAP config would mean that none of this traffic should even leave the access point - apart from stats/client info.
However, i've recently been seeing something odd in that there must be some multicast-talking clients on this untrusted network and whatever they are talking about I can see on my management LAN (10.10.10.0). I can basically see multicast packets with source IPs from the untrusted network. How is this possible? More importantly how can I stop it?
All network numbers are just examples. Any help or ideas would be gratefully received.

Hi Stuart,
Just to clarify a point:
"but I didn't think this would matter as the HREAP config would mean that none of this traffic should even leave the access point"
Keep in mind that when an ap is hreap mode, the ap essentially acts like a switch with respect to its ethernet port. When it gets a packet from the wireless side, if appropriate, it tags it and puts it on the wire.
Under ordinary circumstances (unless something is configured to stop this), if a wireless client connected to an hreap ap sends a multicast packet, it absoutely will be put on the wire by the ap, just as a broadcast would. I just confirmed this with lab equipment.
So if there isn't a routed path from the remote untrusted networks to your mgmt vlan, there may (should) be L3 multicast routing configured for the untrusted and your management routed interfaces. Is this the case?
thanks
Jeff

HREAP and cisco 5508

Dear Forum Members I have found the below link which is great, but I was wondering if you can provide some additional info.
http://www.cisco.com/en/US/partner/products/ps6087/products_tech_note09186a0080736123.shtml
The piece that is missing from the above document is the LAN WAN side of the NTWK>
How do I configure the switchport where the AP is terminated on the remote site?
What if I would like to have 2 SSIDs/VLANs? one for voice and one for data. That port I assume would have to be trunk port right?
Also what are the best practices commands I can use for QoS or anything else for Voice?
Thank you and I do appreciate your help on this matter.

Take a look at this document in order to understand what h-reap mode are you going to implement.
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00807cc3b8.shtml
then if you are uing locally switching then you need to configure the ap to match the remote set of vlans and therefore configure the remote switch as trunk with only the vlans that you are going to use over that ap.
for voice over wifi, here it is the guide, there are a lot of details...
http://www.cisco.com/en/US/docs/solutions/Enterprise/Mobility/vowlan/41dg/vowlan41dg-book.html
let me know if it answers your questions.

Wireless and guest network and HREAP

Hi,
I have inherited a wireless infrastructure which comprises of a head office with WCS and WLC plus LWAPP access points.
There is a sub office in another town who wishes to deploy a wireless infrastrucure and it struck me that as they only want to deploy a couple of AP's that HREAP would be good to use in this senario.
However they want to also use the guest wireless network that we have in the head office but I dont want their guest traffic to come to our DSL modem that we have set up for the HO guest wireless. The two offices are connected via an MPLS link which doesnt need anymore traffic on it.
Is there a way of configuring the HREAP and the WLC and WCS so that the sub office breaks out locally for guest and yet the lobby admin at HO can control the password?
Many thanks,

Hi Nell,
the feature you are looking for is "H-REAP local switching".
So you can set the remote AP to H-REAP mode (which optimizes it for "behind a WAN link") and from there you can set several ssids as "local switching".
this means that everything about the authentication phase is handled by WLC but after authentication, the traffic is dropped locally at the AP and doesn't transit through the WLC.
The guest SSID has to be enabled for local switching and then, on the H-REAP APs, go in the AP configuration (from WLC "wireless" tab, then click on ap) and in the hreap tab, you can configure the vlan where the guest traffic will be dropped on the remote site. It must be a vlan that exists on the remote site and users will get a DHCP address on that vlan.
Regards,
Nicolas

Hreap restrictions and limits

Is there any structural limit in the deployment of an hreap solution?
I mean if there is some limitation in the number of hreap ap's/sites on 440x controllers, a minimum requirement for wan bandwidth/delay and so on.
I think it's particularly interesting to know how much control bandwitdth needs to be reserved on the wan link for each remote ap.
Tnx,
Max.

Hi Max,
You are most welcome my friend! Here is some related info;
For HREAP's connected to a centralized wireless LAN controller, the WAN link must support a minimum speed of 128-kbps WAN throughput and 100-ms maximum roundtrip latency between each HREAP and the wireless LAN controller.
http://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps5861/prod_white_paper0900aecd804f1a23_ns337_Networking_Solutions_White_Paper.html
Hope this helps!
Rob

Cisco 851W - Internal WLAN and Guest WLAN

I have a Cisco 851W Router, which has an IPSEC Tunnel back to my corporate office.
I want to configure 2 WLANS, one for my internal network (vlan 1) which will have access to my corporate network, and one for guests which will just be for outbound internet access (http, https, ftp, sftp, etc ..).
I have not been able to find any Cisco Documentation with how to accomplish. Can someone inform me where I can find this or supply me with some configuration examples?

create 2 ip dhcp pools on the router for the 2 types of clients
create wlan for each type of client
I'm assuming a wlc is involved, then hreap and allow both vlans, procedure will be slightly different for standalone
acl by address to ban traffic from ipsec tunnel- easier on a WLC interface than on the router, no wlc then on the router
bob

WLC 5508 - WGBs & HREAP on LAN

So, I really have two questions here. For some background information, I have a wireless network with two WLC 5508 controllers and 220 LWAPs in the same location as the controllers. All APs are currently in local mode. I run a few guest networks as well as some other client networks. One client in particular uses their network to connect mobile machines to their VLAN. The only issue is that the machines do not have wireless adapters. Instead, the manufacturer put inside the chassis, a D-Link WGB, which has an ethernet cable, you then have to plug into the ethernet port. These devices cannot seem to connect to the network. I have found, the WGBs do associate on the network, but the wired client behind it cannot pass traffic onto the VLAN. I have also tried connecting PCs with different SOHO style WGBs from different manufacturers with the same result.
After going through Cisco's documentation, I found that using 1230s in WGB mode can resolve this issue since they use IAPP to communicate the MAC table of the wired side clients they service back to the controller. I have configured a 1230, and used it as the WGB for the client machine instead of the D-Link and it does seem to work, but this would mean configuring a considerable number of 1230s to hand over to the client.
The first question would be, Is there something I am missing that I would need to do in order to allow SOHO style WGBs to forward wired side client traffic onto the network while LWAPs are in local mode? Or would the WGB NEED to support IAPP?
The second question is that, I may have found another solution to this already, but would like some input prior to committing.
This client also uses these same machines with the same WGBs inside the chassis at another location where the client operates the network themselves. They also use the same WLC model with the same version, and same APs. The only difference is that they use H-REAP mode with local switching.
I also tested this idea, and it seemed to work. With the AP in H-REAP mode, and the client's WLAN set to local switching, the machine and WGB connected with no problem.
So the question with this, would be; would there be any disadvantages in running all 220 APs at this location in H-REAP mode? What would I be losing if anything? Also, I would like to keep all other WLANs centrally switched.
I understand what the difference would be for this client's WLAN if I ran in H-REAP mode with local switching, but what would the difference be in the other guest WLANs if I set them to be centrally switched? (Is there any difference between running APs in local mode vs running APs in H-REAP with central switching?)

Hey,
I read your quesiton quickly so I might miss some points, but I think you need to do some more configuraiton for your passive clients behind the WGB:
'''snip'''
Passive Clients Behind a WGB
The controller might not be able to see passive clients behind a WGB. Clients (such as cameras and programmable logic devices) do not initiate a traffic stream unless they are connected. Complete these steps in order avoid this issue:
Add a static MAC filter entry for the passive WGB device and MAC filter entry for the devices that are behind it.
Use this command in order to enable MAC filtering on the WLAN along with aaa override:config macfilter ipaddress MAC_address IP_address
Add a static entry on the WGB IOS-based device: bridge 1 addressxxxx.xxxx.xxxx forward FastEthernet0Note: In addition, increase the dot11 activity timer.
Add a static ARP entry on the L3 router:
hostname(config)#arp
arpa
'''snip'''
Reference: http://tiny.cc/cjsxu
Also, know please that WGB is not supported with hybrid REAP (H-REAP).
Even if it worked with you sometimes, it is not supported and cisco did not design it to work with HREAP.
http://bit.ly/yLn9D1
I am only aware about one difference between central switching HREAP and local mode; which is that any limitation applied to HREAP will be applied if it is central switching. just like our situation with WGB with HREAP.

Understanding how mobility between a 3850 MA and 5760 MC should work

We just recently purchased some 3850s and are considering leveraging their wireless capabilities. We have one building that utilizes HREAP and have discovered the WLC 5760 no longer supports that so they are stuck on our old 5508s for now. One thought was to use the 3850 installed there to accomplish this. If we install AP licenses and use it as a MC I know we can easily accomplish this and drop the clients locally. One question is if it is possible to do this running the 3850 as a MA? Right now I have one setup in lab as MA using one of our 5760s as the mobility controller. When I newly connect to our primary WLAN I get an IP address from a VLAN on the 3850, but if I roam from a non-3850 AP I maintain my IP address from the 5760 interface. This also works in reverse and I assume this is expected as part of the new mobility?
Thanks,
Rob

Hi Rob,
"How the clients operate when roaming between an AP attached to the 3850 versus an AP that tunnels back to the 5760. My client maintained its initial IP that it received from either end when roaming between them. I assume that is normal operation?"
Yes, it is standard roaming between 5760/3850 & 5508 setup as long as you properly configure mobility peering by enabling this new mobility on your 5508 setup.
HTH
Rasika
**** Pls rate all useful responses ****

1130 not connecting to controller after setting to HREAP

I had an 1130 AP connected to my 4402 controller running 4.2.207. I went to set the AP to HREAP and after I applied the HREAP setting, the AP rebooted and will no longer connect to the controller.
This is the error message I am getting on the controller.
WARNING: invalid slot ID (255) passed to REAP -Traceback=
0x4F026C 0x4F0394 0x498B24 0x491DC4 0x4AAF90 0x48DAC4 0x48E35C 0x197630o REAP -Traceback=
The AP part number is AIR-LAP1131AG-A-K9.
This AP was up and running with no problem until I tried to change it to HREAP.
Any suggestions on how I can recover this AP?
Seth

I had reloaded the AP last night using c1130-k9w7-tar.124-10b.JDA3.tar renamed to C1130-k9w7-tar.default. After the AP came up in Autonomous mode I then converted back to LWAPP using c1130-rcvk9w8-tar.124-21a.JA2.tar. Once the AP joined the controller and got the image it then rebooted and came up with the same error.
So after reading your response I deced to rename c1130-rcvk9w8-tar.124-21a.JA2.tar to c1130-k9w7-tar.default and let the AP load this image. After downloading the image the AP then joined the controller, got its image, then reloaded and succesfully joined.
Thank you for the help.
Seth

Hreap and spectralink

Similar Messages

Maybe you are looking for