AP-VPN Deployment
20.2 Configuring AP and Controller for AP-VPN Operations
SCALANCE W1750D UI
338 Configuration Manual, 02/2018, C79000-G8976-C451-02
For branches deployed in Distributed, L3 and Distributed, L2 modes, the master AP in the
branch and the controller should agree upon a subnet/IP addresses to be used for DHCP
services in the branch. The process or protocol used by the master AP and the controller to
determine the subnet/IP addresses used in a branch is called BID allocation. The BID
allocation process is not essential for branches deployed in local or Centralized, L2 mode.
The following are some of the key functions of the BID allocation process:
● Determines the IP addresses used in a branch for Distributed, L2 mode
● Determines the subnet used in a branch for Distributed, L3 mode
● Avoids IP address or subnet overlap (that is, avoids IP conflict)
● Ensures that a branch is allocated the same subnet or range of IP addresses irrespective
of which AP in the branch becomes the master in the AP cluster
Branch Status Verification
To view the details of the branch information connected to the controller, execute the
command.
Example
This example shows the details of the branches connected to the controller:
(scalance) #show iap table long
AP Branch Table
----------------
Name VC MAC Address Status Inner IP Assigned Subnet Assigned Vlan
---- -------------- ------ -------- --------------- ------------- Tokyo-CB:D3:16
6c:f3:7f:cc:42:f8 DOWN 0.0.0.0
Paris-CB:D3:16 6c:f3:7f:cc:3d:04 UP 10.15.207.140 10.15.206.99/29 2
LA 6c:f3:7f:cc:42:25 UP 10.15.207.111 10.15.206.24/29 2
Munich d8:c7:c8:cb:d3:16 DOWN 0.0.0.0
London-c0:e1 6c:f3:7f:c0:e1:b1 UP 10.15.207.120 10.15.206.64/29 2
Instant-CB:D3 6c:f3:7f:cc:42:1e DOWN 0.0.0.0
Delhi 6c:f3:7f:cc:42:ca DOWN 0.0.0.0
Singapore 6c:f3:7f:cc:42:cb UP 10.15.207.122 10.15.206.120/29 2
2(10.15.205.0-10.15.205.250,5),1(10.15.206.1-10.15.206.252,5)
7(10.15.205.0-10.15.205.250,5),8(10.15.206.1-10.15.206.252,5)