Black Box LWN600CM-1 Guía de usuario descargar pdf (Pagina 95)

724-746-5500 | blackbox.com

Page 95

Chapter 8: Basic Configuration Examples

NOTE: If you see a different group of SmartPath AP settings, make sure that Monitor is selected as the view mode at the top of

the SmartPath APs page. The GUI provides two view modes for SmartPath APs, one that focuses on monitoring SmartPath

APs (Monitor) and another that focuses on configuring them (Config).

How SmartPath APs Connect to SmartPath EMS VMA

SmartPath APs and SmartPath EMS communicate with one another through CAPWAP (Control and Provisioning of Wireless

Access Points). SmartPath APs act as CAPWAP clients and SmartPath EMS acts as a CAPWAP server. SmartPath APs can form a

CAPWAP connection with SmartPath EMS in any of the following ways:

•WhenSmartPathAPsareinthesamelayer2broadcastdomainasaSmartPathEMSapplianceorSmartPathEMSVMAVirtual

Appliance, the SmartPath APs broadcast CAPWAP Discovery Request messages to discover SmartPath EMS and establish a

secure connection with it automatically.

•IfthereisnoSmartPathEMSVMAinthesamebroadcastdomainbuttheSmartPathAPscanreachtheSmartPathEMSOnline

redirector—and serial number entries for the SmartPath APs have already been added to the SmartPath EMS Online ACL (access

control list)—then they can form secure CAPWAP connections with the redirector (redirection server). From there, an adminis-

trator can assign the connected SmartPath APs to a SmartPath EMS VMA (virtual management appliance) at the cluster site or

to a SmartPath EMS VMA appliance—virtual or otherwise—at another site.

•Finally,SmartPathAPsandalocalSmartPathEMSVMAmightbeindifferentsubnetsandtheSmartPathAPseithercannot

reach SmartPath EMS Online or they can but they are not listed in the ACL (perhaps because they are not included in any

SmartPath EMS Online account). In this case, the SmartPath APs cannot discover SmartPath EMS by broadcasting CAPWAP

Discovery Request messages, nor can they reach the redirector. So that the SmartPath APS can form a CAPWAP connection to

SmartPath EMS, you can use one of the following methods to configure them with the SmartPath EMS VMA domain name or

IPaddressorconfigurethemsothattheycanlearnitthroughDHCPorDNSsettings.WhenSmartPathAPshavetheIPaddress

of the CAPWAP server, they then send unicast CAPWAP Discovery Request messages to that address.

•LogintotheCLIontheSmartPathAPandentertheIPaddressordomainnameoftheCAPWAPserver:

capwap client server name <string>

•ConfiguretheDHCPservertosupplytheSmartPathEMSVMAdomainnameasDHCPoption225oritsIPaddressasoption

226initsDHCPOFFER.(Ifyouuseadomainname,theauthoritativeDNSserverforthatdomainmustalsobeconfiguredwith

an A record that maps the domain name to the SmartPath EMS VMA IP address.) A SmartPath AP requests options 225 and

226bydefaultwhenitbroadcastsDHCPDISCOVERandDHCPREQUESTmessages.

NOTE: If you need to change the DHCP option number (perhaps because another custom option with that number is already in

use on the DHCP server), enter this command with a different option number:

interface mgt0 dhcp client option custom clustermanager <number> { ip | string }

•IfSmartPathEMSVMAcontinuestouseitsdefaultdomainname(“smartpathemsvma”)plusthenameofthelocaldomainto

which it and the SmartPath APs belong, configure an authoritative DNS server with an A record that resolves

"clustermanager.<local_domain>" to an IP address. If a SmartPath AP does not have an IP address or domain name configured

fortheCAPWAPserveranddoesnotreceiveanaddressoradomainnamereturnedinaDHCPoption,thenittriestoresolve

the domain name to an IP address.

If you are using SmartPath EMS Online instead of a physical SmartPath EMS VMA appliance or SmartPath EMS VMA Virtual

Appliance and the SmartPath APs go on-line for the first time without any specific CAPWAP server configuration entered manual-

lyorreceivedasaDHCPoption,theyprogressthroughthefollowingcycleofCAPWAPconnectionattempts.First,theytryto

connect with a CAPWAP server at clustermanager.<local_domain>. If that is unsuccessful, they next try to elicit a response from

the broadcast of CAPWAP Discovery messages on their local subnet. If neither of these efforts produces a response, they try to

connecttoSmartPathEMSOnline,firstusingtheCAPWAPUDPport12222andthenusingCAPWAPovertheHTTPTCPportof

80. This cycle is shown in Figure 8-9.

1 2 ... 90 91 92 93 94 95 96 97 98 99 100 ... 191 192

Comentarios a estos manuales

Sin comentarios

Black Box LWN600CM-1 Guía de usuario Pagina 95

Comentarios a estos manuales