cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
knevyn
New Contributor III

BSC Address

Jump to solution

Looking for best way to configure BSAPs that will be deployed at customer sites.

Controller is on a private LAN. BSAPs will connect back across the internet.

Any suggestions guide lines appreciated.

On the BSAP itself. The BSC Address has to be an IP address. Can a DNS name be used?

0 Kudos
1 Solution

Accepted Solutions
kennethfernandes
Contributor II
Contributor II

Re: BSC Address

Jump to solution

Most customer's deploy DHCP option 43. If the IP address of the vWLAN changes, you can simply modify the DHCP scope with the new IP address. Second to DHCP option 43 in terms of customer usage, is typically a DNS entry for apdiscovery. Statically configuring BSAPs for AP discovery is typically limited to small deployments or perhaps lab testing.

View solution in original post

0 Kudos
5 Replies
kennethfernandes
Contributor II
Contributor II

Re: BSC Address

Jump to solution

Have you seen the vWLAN AP Discovery guide posted on the community? It goes over the 3 discovery methods used by BSAPs to discover the vWLAN Appliance and or Virtual Appliance (VMware). For example you could statically configure them via the serial console/ssh, use DHCP option 43, or a DNS entry for apdiiscovery.


Controller is on a private LAN. BSAPs will connect back across the internet.



I'f the vWLAN is on a private LAN, I'm assuming your customer sites have a WAN link or VPN to the private LAN? Otherwise you would need to put a public IP address on the vWLAN and perhaps put it in your DMZ.



On the BSAP itself. The BSC Address has to be an IP address. Can a DNS name be used?


A DNS name cannot be used.

knevyn
New Contributor III

Re: BSC Address

Jump to solution

Thanks for the reply.

For APs in the LAN we're using DNS (apdiscovery) and it works well.

For WAN, the controller does have a private IP. An earlier post said vWLAN could not work with NATed addresses. This is what we tried at first. We can accomodate using a public IP. However we're concerned with statically configuring BSAPs with static IPs. IPs can change and ours will be soon. Ability to use DNS would be greatly appreciated or other suggestions appreciated too.

kennethfernandes
Contributor II
Contributor II

Re: BSC Address

Jump to solution

Most customer's deploy DHCP option 43. If the IP address of the vWLAN changes, you can simply modify the DHCP scope with the new IP address. Second to DHCP option 43 in terms of customer usage, is typically a DNS entry for apdiscovery. Statically configuring BSAPs for AP discovery is typically limited to small deployments or perhaps lab testing.

0 Kudos
kennethfernandes
Contributor II
Contributor II

Re: BSC Address

Jump to solution

Knevyn,

I went ahead and marked this post as "assumed answered".  Feel free to mark any correct or helpful answers from this post.  If you still need assistance with this issue I would be more than happy to help, just let me know in a reply.

Thanks,

Ken

erik
Contributor
Contributor

Re: BSC Address

Jump to solution

I went ahead and flagged the "Correct Answer" on this post to make it more visible and help other members of the community find solutions more easily. If you don't feel like the answer I marked was correct, feel free to come back to this post and unmark it and select another in its place with the applicable buttons.  If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.

Thanks,

Erik