tivWi-Fi Technology Protocols is allowing to connect with your LAN network without wire over Mobile, Laptop with seamless Roaming without any wire connectivity. It is LAN technology which is used to connect Home, Campus, Building and Corporate network. There are some design considerations and Protocols used for designing the WI-FI LAN network.
Wireless LAN Protocol
As we all know Network LAN is working on some protocols to communicate with multiple network. Protocols are nothing but a Set up Rules which define how traffics will be route or communicate. Wireless Protocols also some standards and specification that define how Wireless Devices ( Access Points) are communicate to each other and with WLC.
AP to WLC Connectivity
When we design Wireless network them, it is also based on LAN network. First of all we need to design and setup and LAN network like Internet link, Internet router, Core Switch, Distribution Switch and Access points known as Three Tier Hierarchy architecture. for Wireless there always recommended that use POE+ enable Switch so Access points will get Power and Data connectivity from same port.
CAPWAP
CAPWAP (Control and Provisioning of Wireless Access Points)use to discover and manage lightweight access points. It creates a CAPWAP tunnel between WLC and AP for Management traffic. CAPWAP is open standard Wireless control Protocol. Also it depend or replacement of LWAPP.
UDP Port- 5246, 5247
LWAPP (Lightweight Access Point Protocol)
LWAPP consist 6 byte header packet has a AP IP and MAC address as the source and the WLC IP and MAC address as the destination. After header recd and rewrite the ( inc SA, DA, RA) and WLC send it to wired networks. WAPP can operate in either Layer 2 LWAPP mode or Layer 3 LWAPP mode.
UDP Port- 12222, 12223
How LWAPP Works
Step 1. An AP sends an LWAPP discovery request message.
Step 2.-(WLC) receives the LWAPP discovery request and responds with an LWAPP discovery response message.
Step 3. The AP chooses a controller based on the response received and sends a join request.
Step 4. The WLC receiving the LWAPP join request responds to the AP join request with an LWAPP join response. This process is going to include a mutual authentication.
Step 5. After the AP has joined the WLC, LWAPP messages are exchanged, and the AP initiates a firmware download from the WLC (if the AP and WLC have a version mismatch).
Step 6-After firmware WLC and AP make some setting including settings might include service set identifiers (SSID), security parameters, 802.11 parameters such as data rates and supported PHY types, radio channels, and power levels.
Step 7. After the provisioning phase is completed, the AP and WLC enter the LWAPP runtime state and begin servicing data traffic.
Step 8. During runtime operations, the WLC might issue various commands to the AP through LWAPP control messages.
Step 9. During runtime operations, LWAPP keepalive messages are exchanged between the AP and WLC to preserve the LWAPP communication channel.
Layer 3 LWAPP control and data messages are transported over the IP network in User Datagram Protocol (UDP) packets.
LWAPP has two main traffic types,
■ Control: Management traffic between AP and WLC. It is a control channel for configuration, session management, firmware management, and so on. Traffic is encrypted
and authenticated.
■ Data: Wireless traffic, encapsulated, sent between AP and WLC. You can make an analogy to a GRE-Tunnel
LWAPP has two encapsulation types:
■ Layer 2: All communication between the AP and WLC is done on top of native 802.3 Ethernet frames, with an Ether type of 0xbbbb or 0x88bb, depending on the release.
■ Layer 3: LWAPP is carried over IP/User Datagram Protocol (UDP), using port numbers 12222 and 12223 (data and control, respectively).
AWPP (Cisco Adaptive Wireless Path Protocol): In Wireless Outdoor Solution there are a solution called Mesh technology. In MESH technology we need to design the solution the form of RAP (Root Access Points) and MAP (Mesh access Points). So All MAPs are communicate to RAPs and using their route to reach WLC. MAPs communicate among themselves and back to the RAP using wireless connections over the 802.11a/n radio backhaul. MAPs use the Cisco Adaptive Wireless Path Protocol (AWPP) to determine the best path through the other mesh access points to the controller.
Network Mobility Services Protocol (NMSP): The protocol handles communication between controllers and the mobility services engine. In a wIPS deployment, this protocol provides a pathway for alarm information to be aggregated from controllers and forwarded to the mobility services engine and for wIPS configuration information to be pushed to the controller. This protocol is encrypted.
Controller TCP Port: 16113
Simple Object Access Protocol (SOAP/XML): The method of communication between the mobility services engine and the NCS. This protocol is used to distribute configuration parameters to the wIPS service running on the mobility services engine.
MSE TCP Port: 443
Native VLAN
“The native VLAN is an IEEE stipulation to the 802.1Q protocol that states that frames on the native VLAN are not modified when they are sent over trunk links. In Cisco switches, the default native VLAN is VLAN 1. it is important to ensure that the native VLAN is the same VLAN on both ends of the link. Because the traffic for the native VLAN is not tagged, the switches assume that the frames are on the native VLAN. If the native VLAN is different on either side, traffic can hop from one VLAN to another”
How Native Works
As we know that with 802.1Q carrying Tagged VLAN details. Tagged means Vlan allowed on Trunk Port.
But, End device like PC, Access Points, Printer, Scanner doesn’t support Trunk / 802.1Q. These devices are worked on Access Ports or untagged port.
So, if we have multiple end devices or if we can say multiple Access Points connected on Access Switch, then it is not possible to connect Access Switches with Core or dist switch as Access Port, we have to configure these uplink ports as Trunk ports only.
Then, how untagged Vlans with travel on Trunk port, for that on Trunk when we allowed VLANs than we also run a command Native Vlan XXX ( By Default Vlan-1 is Native Vlan, but we can make any Vlan as Native), Now this untagged VLAN travel along with tagged VLAN on same trunk Ports and End devices are also configured as part og that Native VLAN. ( little complicate to understand).
So, if we are configure any port as trunk and AP’s are connected on that switch then always configure Native VLAN ( ther VLAN in which you want to assign for AP’s).
Visit to our site : https://www.kbrosistechnologies.com/
Watch more Video https://www.youtube.com/channel/UCpcd6IshE1caAbf9EdJd3gw
https://www.youtube.com/channel/UCTbOmLTSlHggEBkt5wFGNRA
FAQ
Q. How to design a Wi-Fi Network?
Wi-Fi designing requires a expertise during Designing and Implementation, as it needs a Site Survey first to get coverage area with good signal strength, so end user can connect with Wi-Fi from every corner of that area to access network.
Q. What is CAPWAP
A. CAPWAP use to discover and manage lightweight access points. It create a CAPWAP tunnel between WLC and AP for Management traffic. CAPWAP is open standard Wireless control Protocol. Also it depend or replacement of LWAPP.
Q. Which UDP Port used by CAPWAP
A. UDP Port- 5246, 5247
Q. What is LWAPP
A. LWAPP (Lightweight Access Point Protocol): LWAPP consist 6 byte header packet has a AP IP and MAC address as the source and the WLC IP and MAC address as the destination. After header received and rewrite the ( inc SA, DA, RA) and WLC send it to wired networks. LWAPP can operate in either Layer 2 LWAPP mode or Layer 3 LWAPP mode.
Which UDP Port used by LAWAPP
A. UDP Port- 12222, 12223
