We recently have been starting a small rollout of Aruba access points in some of our campuses. Today we got a 7240 installed in our data center running the latest 8.4 code. As a test, we put an Aruba 515 in our office to play with, but note that in this building the rest of the 14 APs are Cisco.
We also have a test VLAN and network set up for our Aruba gear that is not part of the production network. But the Aruba AP is broadcasting the same 4 SSIDs that the Cisco APs are. (But when you connect to the Aruba AP you are obviously getting IP from the test network)
I’m getting pretty crappy performance (0.05mpbs at times) out of this 515 and my SE is saying it is due to the rest of the building being Cisco and that the Aruba and Cisco APs are viewing each other as rogues. And that we will have much better performance on our remote campus when they are all switched over to Aruba APs.
But the channel utilization on the Aruba controller is showing around 10-15% interference so it seems like it may be a bigger problem than that.
I am running 20mhz channels on the 2.4 radio and 20/40Mhz on the 5Ghz radio on my Aruba AP.
Has anyone here ran Cisco/Aruba in the same building with the same SSIDs? Should I be looking into settings that can help solve the rogue issue (if that is the case)?
If your client is connecting to the 2.4ghz radio and there is alot of cochannel interference, that might be your issue. You need to confirm your channel width on the Aruba network and the Cisco network and see if you are facing cochannel interference there, as well...
There definitely could be an issue.
Interesting find. I found that when I went from WPA3 auth to WPA2 auth, it seemed to fix all my slowness issues. Anyone else see these kind of issues when using WPA2 or WPA3?
We are in the process of migrating from Cisco to Aruba on campus as well. In order to facilitate a smoother transition, we set up a different ssid (actually 3, one for.1x, one guest, and one IOT (Mac based with MPSK)).
The vlans are different, ip ranges are new (and larger to accommodate more devices), and there are many more APs. That allowed us to leave the Cisco stuff alone - it still works, and the user can still connect, but we plastered signs about the campus advising everyone of the new networks.
Since the process is different, it allows us to train users without denying access to those with existing devices. They can take a few weeks to cut over devices and our help desk isn't over burdened with students moving in with connecting issues.
Through the semester we will begin to remove the old Cisco devices, which will force those still on the old to switch, but at a moderate pace.
It also lets us refine the process, instructions, etc with less pressure to make sure all the bugs are worked out. If it's busted, they can connect to old-network until we can figure out their issue to get them on new-network.
hth good luck!
I'm getting pretty crappy performance (0.05mpbs at times) out of this 515 and my SE is saying it is due to the rest of the building being Cisco and that the Aruba and Cisco APs are viewing each other as rogues. And that we will have much better performance on our remote campus when they are all switched over to Aruba APs.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.