Wireless Access

Controller is a 7210 running 8.10, most APs we are deploying have 8.7 on them out of the box.

Having some odd issues the past few months with joining APs to our controller. If I am at the main campus where my controller lives, we can plug the APs in just fine. They update and are ready to be provisioned on the controller. Now if I go to another campus with a new AP and plug it in. It almost immediately goes into Instant mode. If I plug my laptop into that same port, I can ping the controller, DCs, etc. just like I should.

I've checked my DHCP options and DNS settings and all seems correct, and obviously works when on the main campus. All the campuses are interconnected with dark fiber.

Has anyone run into anything like this. It really seems like a network issue, but I can't pinpoint it. I have a mix of Cisco and Aruba switches and it happens on both, we have made no network config changes recently either.

Controller is a 7210 running 8.10, most APs we are deploying have 8.7 on them out of the box.

Having some odd issues the past few months with joining APs to our controller. If I am at the main campus where my controller lives, we can plug the APs in just fine. They update and are ready to be provisioned on the controller. Now if I go to another campus with a new AP and plug it in. It almost immediately goes into Instant mode. If I plug my laptop into that same port, I can ping the controller, DCs, etc. just like I should.

I can provision an AP at the main site, and then take it to the new site and it works great.

I've checked my DHCP options and DNS settings and all seems correct, and obviously works when on the main campus. All the campuses are interconnected with dark fiber.

Has anyone run into anything like this. It really seems like a network issue, but I can't pinpoint it. I have a mix of Cisco and Aruba switches and it happens on both, we have made no network config changes recently either.

Also, you can add an entry in your DNS server for "aruba-mster" to resolve the mobility controller IP/VIP. DNS discovery is more scalable and easier to manage

Make sure to add the domain name field to each DHCP pool.

ip dhcp pool Aruba
 network <network> <mask>
 default-router <gateway ip>
 dns-server <ip>

domain-name <string>

As Shpat said, Option 43 and 60 should work in your case too

Controller is a 7210 running 8.10, most APs we are deploying have 8.7 on them out of the box.

Having some odd issues the past few months with joining APs to our controller. If I am at the main campus where my controller lives, we can plug the APs in just fine. They update and are ready to be provisioned on the controller. Now if I go to another campus with a new AP and plug it in. It almost immediately goes into Instant mode. If I plug my laptop into that same port, I can ping the controller, DCs, etc. just like I should.

I can provision an AP at the main site, and then take it to the new site and it works great.

I've checked my DHCP options and DNS settings and all seems correct, and obviously works when on the main campus. All the campuses are interconnected with dark fiber.

Has anyone run into anything like this. It really seems like a network issue, but I can't pinpoint it. I have a mix of Cisco and Aruba switches and it happens on both, we have made no network config changes recently either.

We are using Windows DHCP scopes so I think we have those options all set. I have DNS entries for master and conductor already. The one campus it doesn't seem to work on is connected to our network but is the only campus that is Layer 3.

Also, you can add an entry in your DNS server for "aruba-mster" to resolve the mobility controller IP/VIP. DNS discovery is more scalable and easier to manage

Make sure to add the domain name field to each DHCP pool.

ip dhcp pool Aruba
 network <network> <mask>
 default-router <gateway ip>
 dns-server <ip>

domain-name <string>

As Shpat said, Option 43 and 60 should work in your case too

Controller is a 7210 running 8.10, most APs we are deploying have 8.7 on them out of the box.

Having some odd issues the past few months with joining APs to our controller. If I am at the main campus where my controller lives, we can plug the APs in just fine. They update and are ready to be provisioned on the controller. Now if I go to another campus with a new AP and plug it in. It almost immediately goes into Instant mode. If I plug my laptop into that same port, I can ping the controller, DCs, etc. just like I should.

I can provision an AP at the main site, and then take it to the new site and it works great.

I've checked my DHCP options and DNS settings and all seems correct, and obviously works when on the main campus. All the campuses are interconnected with dark fiber.

Has anyone run into anything like this. It really seems like a network issue, but I can't pinpoint it. I have a mix of Cisco and Aruba switches and it happens on both, we have made no network config changes recently either.

Do you have any Firewall in between Sites? Also you said Layer-3, where does the AP get the Scope from?

We are using Windows DHCP scopes so I think we have those options all set. I have DNS entries for master and conductor already. The one campus it doesn't seem to work on is connected to our network but is the only campus that is Layer 3.

Also, you can add an entry in your DNS server for "aruba-mster" to resolve the mobility controller IP/VIP. DNS discovery is more scalable and easier to manage

Make sure to add the domain name field to each DHCP pool.

ip dhcp pool Aruba
 network <network> <mask>
 default-router <gateway ip>
 dns-server <ip>

domain-name <string>

As Shpat said, Option 43 and 60 should work in your case too

Controller is a 7210 running 8.10, most APs we are deploying have 8.7 on them out of the box.

Having some odd issues the past few months with joining APs to our controller. If I am at the main campus where my controller lives, we can plug the APs in just fine. They update and are ready to be provisioned on the controller. Now if I go to another campus with a new AP and plug it in. It almost immediately goes into Instant mode. If I plug my laptop into that same port, I can ping the controller, DCs, etc. just like I should.

I can provision an AP at the main site, and then take it to the new site and it works great.

I've checked my DHCP options and DNS settings and all seems correct, and obviously works when on the main campus. All the campuses are interconnected with dark fiber.

Has anyone run into anything like this. It really seems like a network issue, but I can't pinpoint it. I have a mix of Cisco and Aruba switches and it happens on both, we have made no network config changes recently either.

The campus with the issue is 1 router hop away.  APs that have joined in the past can continue to join and have no issues joining from any campus. That makes it seem like there is no firewall rules or routing issues. It definitely is confusing me.

The AP gets the scope from a Windows DHCP server at that campus, but never successfully grabs an IP.

Do you have any Firewall in between Sites? Also you said Layer-3, where does the AP get the Scope from?

We are using Windows DHCP scopes so I think we have those options all set. I have DNS entries for master and conductor already. The one campus it doesn't seem to work on is connected to our network but is the only campus that is Layer 3.

Also, you can add an entry in your DNS server for "aruba-mster" to resolve the mobility controller IP/VIP. DNS discovery is more scalable and easier to manage

Make sure to add the domain name field to each DHCP pool.

ip dhcp pool Aruba
 network <network> <mask>
 default-router <gateway ip>
 dns-server <ip>

domain-name <string>

As Shpat said, Option 43 and 60 should work in your case too

Controller is a 7210 running 8.10, most APs we are deploying have 8.7 on them out of the box.

Having some odd issues the past few months with joining APs to our controller. If I am at the main campus where my controller lives, we can plug the APs in just fine. They update and are ready to be provisioned on the controller. Now if I go to another campus with a new AP and plug it in. It almost immediately goes into Instant mode. If I plug my laptop into that same port, I can ping the controller, DCs, etc. just like I should.

I can provision an AP at the main site, and then take it to the new site and it works great.

I've checked my DHCP options and DNS settings and all seems correct, and obviously works when on the main campus. All the campuses are interconnected with dark fiber.

Has anyone run into anything like this. It really seems like a network issue, but I can't pinpoint it. I have a mix of Cisco and Aruba switches and it happens on both, we have made no network config changes recently either.

We are using Windows DHCP scopes so I think we have those options all set. I have DNS entries for master and conductor already. The one campus it doesn't seem to work on is connected to our network but is the only campus that is Layer 3.

Also, you can add an entry in your DNS server for "aruba-mster" to resolve the mobility controller IP/VIP. DNS discovery is more scalable and easier to manage

Make sure to add the domain name field to each DHCP pool.

ip dhcp pool Aruba
 network <network> <mask>
 default-router <gateway ip>
 dns-server <ip>

domain-name <string>

As Shpat said, Option 43 and 60 should work in your case too

Controller is a 7210 running 8.10, most APs we are deploying have 8.7 on them out of the box.

Having some odd issues the past few months with joining APs to our controller. If I am at the main campus where my controller lives, we can plug the APs in just fine. They update and are ready to be provisioned on the controller. Now if I go to another campus with a new AP and plug it in. It almost immediately goes into Instant mode. If I plug my laptop into that same port, I can ping the controller, DCs, etc. just like I should.

I can provision an AP at the main site, and then take it to the new site and it works great.

I've checked my DHCP options and DNS settings and all seems correct, and obviously works when on the main campus. All the campuses are interconnected with dark fiber.

Has anyone run into anything like this. It really seems like a network issue, but I can't pinpoint it. I have a mix of Cisco and Aruba switches and it happens on both, we have made no network config changes recently either.

What are those option 43 and 60 settings for those AP scopes?  Is there dynamic policy being applied?  Use a console cable on the AP and watch the boot cycle, if the DHCP options are correct then there should be an indication of such during boot.

We are using Windows DHCP scopes so I think we have those options all set. I have DNS entries for master and conductor already. The one campus it doesn't seem to work on is connected to our network but is the only campus that is Layer 3.

Also, you can add an entry in your DNS server for "aruba-mster" to resolve the mobility controller IP/VIP. DNS discovery is more scalable and easier to manage

Make sure to add the domain name field to each DHCP pool.

ip dhcp pool Aruba
 network <network> <mask>
 default-router <gateway ip>
 dns-server <ip>

domain-name <string>

As Shpat said, Option 43 and 60 should work in your case too

Controller is a 7210 running 8.10, most APs we are deploying have 8.7 on them out of the box.

Having some odd issues the past few months with joining APs to our controller. If I am at the main campus where my controller lives, we can plug the APs in just fine. They update and are ready to be provisioned on the controller. Now if I go to another campus with a new AP and plug it in. It almost immediately goes into Instant mode. If I plug my laptop into that same port, I can ping the controller, DCs, etc. just like I should.

I can provision an AP at the main site, and then take it to the new site and it works great.

I've checked my DHCP options and DNS settings and all seems correct, and obviously works when on the main campus. All the campuses are interconnected with dark fiber.

Has anyone run into anything like this. It really seems like a network issue, but I can't pinpoint it. I have a mix of Cisco and Aruba switches and it happens on both, we have made no network config changes recently either.

Controller is a 7210 running 8.10, most APs we are deploying have 8.7 on them out of the box.

Having some odd issues the past few months with joining APs to our controller. If I am at the main campus where my controller lives, we can plug the APs in just fine. They update and are ready to be provisioned on the controller. Now if I go to another campus with a new AP and plug it in. It almost immediately goes into Instant mode. If I plug my laptop into that same port, I can ping the controller, DCs, etc. just like I should.

I can provision an AP at the main site, and then take it to the new site and it works great.

I've checked my DHCP options and DNS settings and all seems correct, and obviously works when on the main campus. All the campuses are interconnected with fiber.

Has anyone run into anything like this. It really seems like a network issue, but I can't pinpoint it. I have a mix of Cisco and Aruba switches and it happens on both, we have made no network config changes recently either.