DescriptionHow do I configure my Cisco switch to connect to the Meru Controller?
ScopeKB ARTICLE TYPE: Configuration
RELATED PRODUCTS: Meru controller and Cisco Catalyst switches
RELATED SOFTWARE VERSIONS: NA
KEYWORDS: Switch configuration, Cisco, Catalyst
SolutionSwitch Configuration and Setup
When
implementing multiple VLAN's from the controller to your Cisco switch,
the switch port that is connected to the Meru Controller must be
configured to support trunking for the VLANs that are configured on the
Controller. If no VLANs are used, trunking is not necessary.
The
Cisco Catalyst Ethernet Switch configuration below assumes trunking to
Meru Controller is desired for VLANs 10 and 20. It is recommended to
prune off any VLAN's on the switchport that are not being utilized on
the Meru controller.
Note the helper-ip address in the VLAN
interface is configured, which is used to make sure the DHCP broadcast
messages from the requesting client are forwarded to the unicast IP
addresses of the DHCP server across VLANs
interface GigabitEthernet1/1
description "CONNECTION TO MERU CONTROLLER"
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk allowed vlan 10, 20
!
Interface Vlan10
ip address 10.1.10.1 255.255.255.0
ip helper-address 10.1.1.254
!
Interface Vlan20
ip address 10.1.20.1 255.255.255.0
ip helper-address 10.1.1.254
For
Ports that do not need trunking, “switchport mode access” would be used
instead of trunk mode, and the access VLAN number would be configured.
To confirm the configuration, use the Catalyst switch command “show
vlan” for the list of the configured VLANs and associated ports. In
order to verify the trunking configuration, use the command “show
interface trunk” which will display the status for trunking on each
switch port, the encapsulation type used, the native VLAN for the trunk
port, and the VLANs that are allowed and active in the management
domain.
For further assistance on configuring your Cisco product, contact your Cisco TAC representative.
