12-18-2015 06:38 AM - edited 07-05-2021 04:24 AM
At one of our location we have Cisco SF500 switches. Recently we installed a primary and a backup WLC 2504 and some 2702 AP's. The back-up WLC is connected to a Cisco 2960x and works fine (This is also our default setup for all locations) But the primary must be connected to the SF500. All switches are configured to use vlan99 as native vlan.
The WLC should connect to the switch with a LAG and 802.1q. As I read somewhere the WLC use vlan0 as native vlan, correct? This can't be changed?
I also tried to change the native vlan on the trunk to the wlc on th sf500 switch but the WLC does not "come up" . I preconfigured WLC on a "normal" cisco switch (3750). Etherchannel/LAG is comming up but ip address not reachable
Info
SF500
data vlan 105
guest vlan 90
native vlan 99
channelgroup mode on
port-channel
sw mode trunk
WLC
LAG
802.1q
12-21-2015 06:25 PM
Pls post "show interface detailed management" output from your WLC.
HTH
Rasika
12-28-2015 06:26 AM
(Cisco Controller) >show interface detailed management
Interface Name................................... management
MAC Address...................................... 38:ed:18:50:9e:ef
IP Address....................................... 10.105.70.254
IP Netmask....................................... 255.255.0.0
IP Gateway....................................... 10.105.1.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
Link Local IPv6 Address.......................... fe80::3aed:18ff:fe50:9eef/64
STATE ........................................... REACHABLE
Primary IPv6 Address............................. ::/128
STATE ........................................... NONE
Primary IPv6 Gateway............................. ::
Primary IPv6 Gateway Mac Address................. 00:00:00:00:00:00
STATE ........................................... INCOMPLETE
VLAN............................................. 105
Quarantine-vlan.................................. 0
Active Physical Port............................. LAG (13)
Primary Physical Port............................ LAG (13)
Backup Physical Port............................. Unconfigured
DHCP Proxy Mode.................................. Global
Primary DHCP Server.............................. 10.105.10.11
--More-- or (q)uit
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
DHCP Option 82 bridge mode insertion............. Disabled
IPv4 ACL......................................... Unconfigured
IPv6 ACL......................................... Unconfigured
mDNS Profile Name................................ Unconfigured
AP Manager....................................... Yes
Guest Interface.................................. No
L2 Multicast..................................... Enabled
12-24-2015 08:21 AM
yes, use management vlan tag = 0 on 2500 side. On the switch side set native vlan to X but not 0 ie., untagged with 99, it should work then.
Below commands may be helpful to check the status:
show port
show arp switch
check the status of 2500 connected uplink switch port.
http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-vlan/70937-guest-internal-wlan.html
12-28-2015 06:32 AM
the management interface is nog configured with vlan 105 (same as data vlan. We do not use a seperate management vlan for our devices).
Tagging it with vlan 0 will then also not work, correct?
12-28-2015 07:08 AM
correction these are Cisco SGE2000-24 switches not SF500
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide