Print this pagePrint this page

Email this topicEmail this topic

View PDFView PDF

Download EPUBDownload EPUB

virtual-controller

Profile Config Commands

Enables an access point as a virtual-controller (VC) or a dynamic virtual controller (DVC)

When configured without the ‘auto‘ option, this command manually enables an AP as a VC. The ‘auto‘ option allows dynamic enabling of APs as VCs. When DVC is enabled on an AP‘s device or profile context, the AP is dynamically enabled as the VC on being elected as the RF-Domain manager.

Supported in the following platforms:

  • Access Points — AP7502, AP7522, AP7532, AP7562, AP7602, AP7612, AP7622, AP7632, AP7662, AP8163, AP8432, AP8533
  • Wireless Controller — RFS4010
  • Service Platforms — NX5500, NX7500, NX9500, NX9600, VX9000
Note

Note

The DVC feature is supported only on the AP7522, AP7532, AP7562, AP8432, and AP8533 model access points.

Syntax

virtual-controller {auto|management-interface}
virtual-controller auto
virtual-controller {management-interface [ip address <IP/M>|vlan <1-4094>]}

Parameters 

virtual-controller auto
virtual-controller auto Enables an AP as a virtual-controller
  • auto – Enables AP as a DVC. When enabled, the AP on being elected as the RF Domain manager takes on the role of the virtual controller. In an RF-Domain, DVC can be enabled on multiple access points. However, only the current RF-Domain manager AP has a running instance of the DVC. This option is applicable only if enabling DVC.
    Note: MLCP discovery does not function on APs enabled as VC or DVCs. Do an explicit “mint link vlan X” on the AP‘s device/profile context, or “control-vlan X” in the AP‘s RF-Domain context, to establish MiNT links between the VC and its adopted APs.
 
virtual-controller {management-interface [ip address <IP/M>|vlan <1-4094>]}
virtual-controller {management-interface [ip address <IP/M>|vlan <1-4094>]}
Note: Enables an AP as a virtual-controller. If enabling DVC, use this option to configure management interface details.
  • management-interface – Configures the management interface for the DVC. Configuring the management interface ensures failover in case the RF Domain manager is unreachable.
    • ip address <IP/M> – Specify the management interface IP address. Due to the random nature of DVC, specifying an explicit management interface IP address makes it easier to manage VCs. In case of fail over, this IP address is installed as the secondary IP address on the new VC.
    • vlan <1-4094> – Optional. Specifies the VLAN from 1 - 4094 on which the management interface IP address is configured.

      For DVC, configuring management-interface ip address is mandatory. However, VLAN configuration is optional. If you configure the ip address without specifying the VLAN, the system configures the specified ip address as secondary ip on VLAN 1.

Example

ap8533-9A1529(config-device-74-67-F7-9A-15-29)#virtual-controller auto

ap8533-9A1529(config-device-74-67-F7-9A-15-29)#virtual-controller management-interface ip address 110.110.110.120/24

ap8533-9A1529(config-device-74-67-F7-9A-15-29)#virtual-controller management-interface vlan 100

ap8533-9A1529(config-device-74-67-F7-9A-15-29)#show context | include virtual-controller
virtual-controller auto
virtual-controller management-interface ip address 110.110.110.120/24
virtual-controller management-interface vlan 100
ap8533-9A1529(config-device-74-67-F7-9A-15-29)#

The following example shows the management interface VLAN IP address being configured as the secondary IP address.

ap8533-9A1529(config-device-74-67-F7-9A-15-29)#show ip interface brief
-------------------------------------------------------------------------------
INTERFACE          IP-ADDRESS/MASK            TYPE        STATUS   PROTOCOL
-------------------------------------------------------------------------------
vlan1              10.1.1.11/24               primary     UP       up
vlan100            110.110.110.110/24         primary     UP       up
vlan100            110.110.110.120/24         secondary   UP       up
-------------------------------------------------------------------------------
Published August 2019prev | next

Email this topicEmail this topic

Print this pagePrint this page