on 01-04-2017 09:04 AM
Thank you for the solution. We have been troubleshooting expeditions within our district. We are using vlan ip pools and seemed to be causing issues when clients had different network IP addresses. This fixed that issue. Thank you.
on 01-19-2017 12:33 PM
Thanks for posting, Brett! Would you mind sharing more about the config you got Expeditions working with? I'm having some trouble getting Expeditions working on our Aruba network. The behavior I see is the teacher will open Expeditions on an Android or iOS device, enter Guide mode, create a class (e.g. download Mount Everest), click Start, and then on a student's Android or iOS device they go into Explorer mode but they never see the Guide. I can get this working fine on an old Linksys WRT54G. I cannot get Expeditions working on our campus Aruba controllers and AP's.
Here are some details about our infrastructure and the SSID I've been testing with: We have 7210 controllers, mostly AP-21x access points, and we're running code rev 220.127.116.11. I created a separate SSID and VLAN isolated to a single controller for testing this without affecting our production SSID's and VLAN's. I tried the following:
Created expeditions AirGroup service with service ID: _googexpeditions._tcp
airgroup service expeditions enable airgroupservice expeditions id _googexpeditions._tcp autoassociate apgroup description Google Expeditions
Verified that AirGroup was allowed for the VLAN
airgroup vlan 106 allow
Tried disabling auto associate
airgroupservice expeditions no autoassociate
Tried enabling IGMP snooping
interface vlan 106 interface vlan 106 ip igmp snooping
I tried various combinations of the broadcast / multicast options for the SSID. It seems logical to me that the problem exists somewhere in the broadcast / multicast settings on the controllers. The knob I was expecting to be blocking the traffic was Drop Broadcast and Unknown Multicast, but still no go.
wlan virtual-ap "Expeditions-vap_prof" no dynamic-mcast-optimization no broadcast-filter all no broadcast-filter arp
I also found a helpful blog post called "Running Google Expeditions on your Cisco Wireless" (https://www.rsaeks.com/?p=469) that suggested formatting the service string as "_googexpeditions._tcp.local." instead, and when I tried entering it that way the controller said "The format should be " _abc._tcp/udp, _abc-def._tcp/udp or urn:schemas-upnp-org:device:MediaServer:1" so I guess Aruba controllers don't like the _local part.
Any ideas or replies are greatly appreciated! Thanks!
01-20-2017 09:31 AM - edited 01-21-2017 11:41 AM
I got it working! I created a fresh VAP and SSID profile. The settings are basically identical to what I was testing with, so I'm not sure why this one is working. In any case, I'm still curious to see what other folks' configs look like. Here's mine...
wlan virtual-ap "Expeditions-vap_prof" aaa-profile "Expeditions-aaa_prof" ssid-profile "Expeditions-ssid_prof" vlan 106 dynamic-mcast-optimization dynamic-mcast-optimization-thresh 80 broadcast-filter arp
I created airgroup service for google expeditions (I disallow it on VLAN 1):
airgroupservice "expeditions" id "_googexpeditions._tcp" disallow-vlan "1" description "Google Expeditions" autoassociate "apgroup"
I made sure airgroup is allowed on vlan 106:
airgroup vlan 106 allow
Here is my VLAN config:
interface vlan 106 ip address 10.6.10.62 255.255.0.0 no suppress-arp operstate up bcmc-optimization
Here is my SSID profile:
wlan ssid-profile "Expeditions-ssid_prof" essid "Expeditions" opmode wpa2-psk-aes wpa-passphrase ***************
My aaa and user-role configs:
aaa profile "Expeditions-aaa_prof" initial-role "authenticated" authentication-dot1x "default" enforce-dhcp ! user-role authenticated access-list session global-sacl access-list session apprf-authenticated-sacl access-list session ra-guard access-list session allowall access-list session v6-allowall
on 05-03-2017 09:51 AM
on 05-05-2017 12:24 PM
Thanks for the reply, David. We don't use ClearPass, so our "AirGroup CPPM enforce registration" knob is set to Disabled. Also note that I've noticed problems when the "AirGroup location discovery" knob is set to Enabled. I set "AirGroup location discovery" to Disabled and it works better. For the service policy (Configuration > Advanced Services > AirGroup > Services > expeditions) I have found that setting "Auto Associate" to "AP-Group" works better than using "AirGroup location discovery".
One very unfortunate thing I've found about getting Google Expeditions working on Aruba (without ClearPass) is that I need a separate VAP / SSID specifically just for Expeditions to work. The reason being that I had to uncheck "Drop Broadcast and Unknown Multicast" in order for it to work. I don't want to do that on our main network for obvious reasons. I'd really like to get Google Expeditions working on our main network instead of having this separate VAP / SSID, but it really wants to throw a ton of unknown multicast / broadcast traffic around.