无线/移动 : "无线, LAN (WLAN)"

无线局域网控制器和轻量接入点故障切换外部移动组配置示例

2015 年 8 月 28 日 - 机器翻译
其他版本: PDFpdf | 英语 (2014 年 9 月 24 日) | 反馈


目录


简介

本文解释如何配置在无线局域网控制器(WLCs)的故障切换功能。此功能准许轻量级接入点(拉普)对故障切换对WLCs他们的移动组的外部。

先决条件

要求

尝试进行此配置之前,请确保满足以下要求:

使用的组件

本文档中的信息基于以下软件和硬件版本:

  • Cisco Aironet 1000 系列轻量 AP

  • 运行固件版本4.2.61.0的一Cisco 2100系列WLC

  • 运行固件版本4.2.61.0的一Cisco 4400系列WLC

在本文解释的功能在WLC版本4.2.61.0介绍。此配置仅工作与运行4.2.61.0或以上的Cisco WLCs。

注意: 如果运行最新的WLC版本, 5.0.148.0,确保,您知道这些限制:

  • 2000系列控制器不支持为了用在控制器软件版本5.0.148.0上。

  • 1000系列接入点不支持为了用在控制器软件版本5.0.148.0上。

注意: Cisco无线LAN控制器和轻量级接入点的参考的版本注释版本的5.0.148.0欲知更多信息。

本文档中的信息都是基于特定实验室环境中的设备编写的。本文档中使用的所有设备最初均采用原始(默认)配置。如果您使用的是真实网络,请确保您已经了解所有命令的潜在影响。

规则

有关文档规则的详细信息,请参阅 Cisco 技术提示规则

背景信息

在所有WLC版本中早于4.2.61.0,当WLC断开“时”, LAP注册对此WLC仅能故障切换对同样移动组的另一WLC,在LAP为故障切换情况下配置。参考WLAN轻量级接入点配置示例的控制器故障切换欲知更多信息。

从Cisco WLC版本4.2.61.0,呼叫备用控制器支持的新特性为对故障切换的接入点介绍到控制器移动组的外部

当他们在本地区域时,丢失主要控制器集中的位置的单个控制器能作为接入点的一个备份。集中化和地区控制器在同样移动组不需要是。通过使用控制器CLI,您能指定您的网络接入点的一个主要的,附属和第三控制器。在控制器软件版本4.2.61.0中,您能指定备用控制器的IP地址,准许对故障切换的接入点到控制器在移动组外面。此功能通过控制器CLI当前仅支持。

本文使用此初始配置设置解释此功能:

  • 两Cisco WLCs该运行固件版本4.2.61.0。

    为清晰,本文使用名称WLC1WLC2为了参考在配置中的WLCs。

  • WLC1的管理接口IP地址是10.77.244.210/27。

  • WLC2的管理接口IP地址是10.77.244.204/27。

  • 当前注册对WLC1的Cisco 1000系列LAP。在我们的配置中,此LAP名称是AP1

关于如何的参考的无线局域网控制器和轻量接入点基本配置示例配置在WLC的基本参数的更多信息。

配置

本部分提供有关如何配置本文档所述功能的信息。

完成这些步骤为了配置此功能:

  1. 配置 WLC 的移动组

  2. 配置WLC和LAP故障切换的移动组的外部

配置 WLC 的移动组

第一步将配置WLC1和WLC2在两不同移动组中。

在本例中, WLC1在TSWEB移动组配置,并且WLC2在backupwlc移动组配置。此部分显示如何通过控制器的CLI配置WLCs的移动组。

输入这些in命令WLC的CLI模式为了配置移动组:

  • WLC1 >config移动组域TSWEB

  • WLC2 >config移动组域backupwlc

因此, WLC1和WLC2配置在两不同移动组中。

您能用WLC GUI也配置此。参考请配置WLCs的移动组欲知更多信息。

配置WLC和LAP故障切换的移动组的外部

下一步是配置WLC和LAP故障切换的移动组的外部。

如被提及前在本文, LAP当前注册对WLC1。您在WLC1能验证此,在我们的示例是10.77.244.210。为了执行此,请点击从控制器GUI的无线。在本例中, LAP名称是AP1

/image/gif/paws/105434/wlc_lap_failover-1.gif

目标将配置此LAP,在这种情况下能故障切换对在一不同的移动组的WLC2 (10.77.244.204)。为了达到此,登录到LAP当前注册WLC的CLI模式(WLC1)通过Telnet应用程序或通过直接控制台连接和配置此LAP主要的和附属WLCs。

  1. 在WLC1 CLI模式,请发出此命令:

    WLC1>config ap primary-base
    		controller_name Cisco_AP [controller_ip_address] 
    
    
    • controller_name字段代表主要的WLC的系统名称。在我们的示例中, WLC1是AP1 LAP的主要的WLC。这里, WLC1是WLC1系统名称。您能看到在GUI模式的控制器名称在WLC的(日志)监控程序

    • Cisco_AP字段代表思科AP的名称。在我们的示例中,它是AP1

    • [controller_ip_address]字段代表主要的WLC的管理接口IP地址。在本例中, 10.77.244.210是WLC1的管理接口IP地址。

    注意: 如果备用控制器是接入点连接的移动组的外部(主要控制器),则您总是需要提供主要的,附属或者第三控制器的IP地址,分别。否则,接入点不能加入备用控制器。

    因此,用于的命令在本例中配置是WLC1 >config ap主要的BASE WLC1 AP1 10.77.244.210

  2. 现在,万一主要的WLC, WLC1,断开,请配置WLC2作为LAP的附属WLC对故障切换。为了配置WLC2,是从一不同的移动组,请发出从WLC1 CLI模式的此命令:

    WLC1>config ap secondary-base
    		controller_name Cisco_AP [controller_ip_address]
    
    
    • controller_name字段代表备份或附属WLC的系统名称。在我们的示例中, WLC2是AP1 LAP的附属WLC。这里, WLC2是WLC2系统名称。

    • Cisco_AP字段代表思科AP的名称。在我们的示例中,它是AP1

    • [controller_ip_address]字段代表附属WLC的管理接口IP地址, WLC2。在本例中, 10.77.244.204是WLC2的管理接口IP地址。

      注意: 如果备用控制器总是接入点连接的移动组的外部(主要控制器),则您需要提供主要的,附属或者第三控制器的IP地址,分别。否则,接入点不能加入备用控制器。

    因此,用于的命令配置在我们的示例是WLC1 >config ap第二BASE WLC2 AP1 10.77.244.204

展示从WLC1的配置的这是CLI屏幕。

 
      WLC1 >config ap primary-base  WLC1 AP1 10.77.244.210
       

      WLC1 >config ap secondary-base WLC2 AP1 10.77.244.204


      WLC1 >save config

      Are you sure you want to save? (y/n) y


      Configuration Saved!

验证

您需要验证您的配置是否适当地工作。在示例,当WLC1断开时, AP1必须故障切换和寄存器对WLC2,在一不同的移动组。

为了验证此,请完成这些步骤:

  1. 断开电源或连接WLC1和AP1的以太网电缆。一旦断开, LAP从WLC和搜索注销登记自己一不同的WLC的。

  2. 根据LAP的正常注册过程与WLC的, AP1一定能成功注册与WLC2。从GUI模式WLC2验证此(10.77.244.204)。

    /image/gif/paws/105434/wlc_lap_failover-2.gif

    注意在此屏幕画面的被包围的参数。这里,您看到AP1注册对WLC2 (10.77.244.204)。

您能也验证从WLC2 CLI模式的注册过程用debug lwapp events enable命令。示例如下:

(Cisco Controller) >Fri Apr  4 04:31:36 2008: 00:0b:85:5b:fb:d0 
Received LWAPP ECHO_REQUEST from AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:31:36 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Ech
o-Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:31:36 2008: 00:0b:85:5b:fb:d0 Received LWAPP PRIMARY_DISCOVERY_REQ
 from AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:31:36 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Pri
mary Discovery Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:31:37 2008: 00:0b:85:5b:fb:d0 Received LWAPP RRM_DATA_REQ from AP
00:0b:85:5b:fb:d0
Fri Apr  4 04:31:37 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Air
ewave-Director-Data Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:31:37 2008: 00:0b:85:5b:fb:d0 Received LWAPP RRM_DATA_REQ from AP
00:0b:85:5b:fb:d0
Fri Apr  4 04:31:37 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Air
ewave-Director-Data Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:31:37 2008: 00:1c:58:05:e9:c0 Received LWAPP ECHO_REQUEST from AP
00:1c:58:05:e9:c0
Fri Apr  4 04:31:37 2008: 00:1c:58:05:e9:c0 Successful transmission of LWAPP Ech
o-Response to AP 00:1c:58:05:e9:c0
Fri Apr  4 04:31:37 2008: 00:1c:58:05:e9:c0 Received LWAPP PRIMARY_DISCOVERY_REQ
 from AP 00:1c:58:05:e9:c0
Fri Apr  4 04:31:37 2008: 00:1b:d4:e3:a8:1b Successful transmission of LWAPP Pri
mary Discovery Response to AP 00:1b:d4:e3:a8:1b
Fri Apr  4 04:31:38 2008: 00:1c:58:05:e9:c0 Received LWAPP RRM_DATA_REQ from AP
00:1c:58:05:e9:c0
Fri Apr  4 04:31:38 2008: 00:1c:58:05:e9:c0 Successful transmission of LWAPP Air
ewave-Director-Data Response to AP 00:1c:58:05:e9:c0
Fri Apr  4 04:31:56 2008: 00:1c:58:05:e9:c0 Received LWAPP RRM_DATA_REQ from AP
00:1c:58:05:e9:c0
Fri Apr  4 04:31:56 2008: 00:1c:58:05:e9:c0 Successful transmission of LWAPP Air
ewave-Director-Data Response to AP 00:1c:58:05:e9:c0
Fri Apr  4 04:32:06 2008: 00:0b:85:5b:fb:d0 Received LWAPP ECHO_REQUEST from AP
00:0b:85:5b:fb:d0
Fri Apr  4 04:32:06 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Ech
o-Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:06 2008: 00:0b:85:5b:fb:d0 Received LWAPP PRIMARY_DISCOVERY_REQ
 from AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:06 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Pri
mary Discovery Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:07 2008: 00:1c:58:05:e9:c0 Received LWAPP ECHO_REQUEST from AP
00:1c:58:05:e9:c0
Fri Apr  4 04:32:07 2008: 00:1c:58:05:e9:c0 Successful transmission of LWAPP Ech
o-Response to AP 00:1c:58:05:e9:c0
Fri Apr  4 04:32:07 2008: 00:1c:58:05:e9:c0 Received LWAPP PRIMARY_DISCOVERY_REQ
 from AP 00:1c:58:05:e9:c0
Fri Apr  4 04:32:07 2008: 00:1b:d4:e3:a8:1b Successful transmission of LWAPP Pri
mary Discovery Response to AP 00:1b:d4:e3:a8:1b
Fri Apr  4 04:32:36 2008: 00:0b:85:5b:fb:d0 Received LWAPP ECHO_REQUEST from AP
00:0b:85:5b:fb:d0
Fri Apr  4 04:32:36 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Ech
o-Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:36 2008: 00:0b:85:5b:fb:d0 Received LWAPP PRIMARY_DISCOVERY_REQ
 from AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:36 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Pri
mary Discovery Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:36 2008: 00:0b:85:5b:fb:d0 Received LWAPP STATISTICS_INFO from
AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:36 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Sta
tistics Info Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Received LWAPP RRM_DATA_REQ from AP
00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Air
ewave-Director-Data Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Received LWAPP RRM_DATA_REQ from AP
00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Air
ewave-Director-Data Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Received LWAPP RRM_DATA_REQ from AP
00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Air
ewave-Director-Data Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Received LWAPP RRM_DATA_REQ from AP
00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Air
ewave-Director-Data Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Received LWAPP RRM_DATA_REQ from AP
00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Air
ewave-Director-Data Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Received LWAPP STATISTICS_INFO from
AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Sta
tistics Info Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Received LWAPP RRM_DATA_REQ from AP
00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Air
ewave-Director-Data Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Received LWAPP RRM_DATA_REQ from AP
00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Air
ewave-Director-Data Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Received LWAPP RRM_DATA_REQ from AP
00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Air
ewave-Director-Data Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Received LWAPP STATISTICS_INFO from
AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:0b:85:5b:fb:d0 Successful transmission of LWAPP Sta
tistics Info Response to AP 00:0b:85:5b:fb:d0
Fri Apr  4 04:32:37 2008: 00:1c:58:05:e9:c0 Received LWAPP ECHO_REQUEST from AP
00:1c:58:05:e9:c0
Fri Apr  4 04:32:37 2008: 00:1c:58:05:e9:c0 Successful transmission of LWAPP Ech
o-Response to AP 00:1c:58:05:e9:c0
Fri Apr  4 04:32:37 2008: 00:1c:58:05:e9:c0 Received LWAPP PRIMARY_DISCOVERY_REQ
 from AP 00:1c:58:05:e9:c0
Fri Apr  4 04:32:37 2008: 00:1b:d4:e3:a8:1b Successful transmission of LWAPP Pri
mary Discovery Response to AP 00:1b:d4:e3:a8:1b
Fri Apr  4 04:32:38 2008: 00:1c:58:05:e9:c0 Received LWAPP RRM_DATA_REQ from AP
00:1c:58:05:e9:c0
Fri Apr  4 04:32:38 2008: 00:1c:58:05:e9:c0 Successful transmission of LWAPP Air
ewave-Director-Data Response to AP 00:1c:58:05:e9:c0
Fri Apr  4 04:32:56 2008: 00:1c:58:05:e9:c0 Received LWAPP RRM_DATA_REQ from AP
00:1c:58:05:e9:c0
Fri Apr  4 04:32:56 2008: 00:1c:58:05:e9:c0 Successful transmission of LWAPP Air
ewave-Director-Data Response to AP 00:1c:58:05:e9:c0

在此输出中,您能看到所有配置参数从WLC2顺利地下载到AP1。只有当LAP注册对该WLC时,此下载过程发生。

显示ap设置将军Cisco_AP命令用于为了查看在本文解释的配置。示例如下:

WLC2 >show ap config general AP1

Cisco AP Identifier.............................. 5
Cisco AP Name.................................... AP1
.....................................................
.....................................................
.....................................................
.....................................................
Name Server......................................
Cisco AP Location................................ default_location
Cisco AP Group Name.............................. default-group
Primary Cisco Switch Name........................ WLC1
Primary Cisco Switch IP Address.................. 10.77.244.210
Secondary Cisco Switch Name...................... WLC2
Secondary Cisco Switch IP Address................ 10.77.244.204
Tertiary Cisco Switch Name.......................

故障排除

您能使用这些调试指令为了排除故障您的配置:

  • debug lwapp errors enable — 配置 LWAPP 错误的调试。

  • debug dhcp message enable — 配置与 DHCP 服务器相互交换的 DHCP 消息的调试。

  • debug dhcp packet enable — 配置与 DHCP 服务器相互往来的 DHCP 数据包详细信息的调试。

相关的思科支持社区讨论

思科支持社区是您提问、解答问题、分享建议以及与工作伙伴协作的论坛。


相关信息


Document ID: 105434