SmartPath Enterprise Wireless Access Point, Outdoor Installation Guide
(a)The LWN602WA tries to connect to SmartPath EMS using the default- domain name “smartpath.<local_domain>”, where “<local_domain>” is the domain name that a DHCP server supplied to the LWN602WA and 12222 is the UDP port number. If a DNS server has been configured to resolve that domain name to an IP address, the
LWN602WA and SmartPath EMS then form a secure CAPWAP connection on Port 12222.
If the LWN602WA cannot make a CAPWAP connection to SmartPath EMS on Port 12222, it tries to reach it by using TCP Port 80: smartpath.<local_domain>:80.
Figure 14. Connecting to SmartPath EMS.
(b)If the DNS server cannot resolve the domain name to an IP address, the LWN602WA broad- casts CAPWAP Discovery messag- es on its local subnet. If SmartPath
EMS is on the local network and responds, they form a secure
CAPWAP connection.
(c)If the first two searches for a local SmartPath EMS produce noresults, the LWN602WA tries to contact SmartPath EMS Online at redirector.blackbox.com:12222. If the Black Box redirection server has a serial number for that
LWN602WA in its ACL, it responds and they form a secure
CAPWAP connection. If the LWN602WA cannot make a CAPWAP connection to SmartPath EMS Online on UDP
Port 12222, it tries to reach it on TCP Port 80. If this is unsuccessful, the LWN602WA returns to the initial search through a DNS lookup and repeats the cycle.
If an LWN602WA forms a CAPWAP connection with the redirection server and its serial number or MAC address has been assigned to a previously created VHM, to a physical SmartPath EMS appliance, or to a SmartPath EMS Virtual Appliance, the redirection server automatically redirects the CAPWAP connection to that SmartPath EMS instance. The redirection server does this by sending the LWN602WA the SmartPath EMS domain name or IP address as its new CAPWAP server. If the LWN602WA is currently using HTTP and it will be redirected to a SmartPath EMS Online VHM, the redirection server also sends it the configura- tion needed to continue using HTTP. Similarly, if the LWN602WA is accessing the network through an HTTP proxy server, the redirection server also saves those settings on the LWN602WA so it can reach the SmartPath EMS Online VHM using HTTP through the HTTP proxy server.
If the redirection server must redirect the LWN602WA to a standalone SmartPath EMS appliance or SmartPath EMS Virtual Appliance, then you must configure the connection settings on the redirection server that you want it to push to the LWN602WA to make that connection. The LWN602WA first uses whatever settings are configured on it to reach the redirection server, which might be on the other side of an HTTP proxy server or firewall that only permits outbound HTTP traffic. Then the redirection server might supply the LWN602WA with different settings so that the LWN602WA can reach a standalone SmartPath EMS instance, which might be on the same side of the HTTP proxy server or firewall as the LWN602WA and therefore requires different connection parameters.
If the LWN602WA serial number or MAC address is in the redirection server but the VHM has not yet been created or the con- nection settings of the standalone SmartPath EMS have not yet been configured on the redirection server, then the LWN602WA remains in the redirection server. The SmartPath EMS admin must manually reassign it later to the appropriate SmartPath EMS.
Page 12 |
|
