Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About Spork Schivago
Stats
Member since
01-16-2019
45
Posts
10
Helpful
1
Solution
Created by
Spork Schivago
in Other Wireless - Mobility Subjects
in Other Wireless - Mobility Subjects
02-04-2019
11:21 AM
02-04-2019
11:21 AM
Thank you!
I also believe it's a configuration issue. I am uploading a hand-drawn picture of my network topology. The WLC and first AP are built into the router. I have not figured out how to disable FlexConnect on the WLC, nor have I figured out how to configure the interface as a trunk line on the WLC. In the Network Topology picture, I did not draw the Wireless APs. There are four total. One is built into the Router (along with the WLC), and the other three I have connected to the router instead of the switch because the router supports PoE and my switch does not. I have tried putting the management interface on the WLC and the wireless APs on one VLAN but the SSIDs on another VLAN, so users connecting to either SSIDs wouldn't have access to any of the management hardware (WLCs, Routers, Wireless APs, etc), but I could not get that working, then I tried putting the WLC, APs, and the employee SSID all on the same VLAN, with the SSID for Guests on another VLAN, but I could not get that working at all either. Depending on the configuration, I can get the built-in AP to show Join. I currently want FlexConnect disabled, just to try and make it a little easier getting everything working, but I am not against keeping FlexConnect enabled, I just thought it would be easier right now with it disabled. Eventually, we will be expanding (if everything goes right) and we will have a need for FlexConnect when that time comes. Thanks for the help!!!!
... View more
Created by
Spork Schivago
in Other Wireless - Mobility Subjects
in Other Wireless - Mobility Subjects
01-31-2019
11:43 AM
01-31-2019
11:43 AM
@Flavio Miranda, Thank you for the reply. Currently, because I cannot access any GUIs at all, I must do everything from the console ports. I did not do anything with the SSIDs, I didn't realize I had to. From your example, I have now issues the following command from the WLC's console session:
config wlan disable 1 config wlan flexconnect local-switching 1 disable config wlan enable 1
Where currently, the only SSID, is the 1st one there. After executing those commands though, I still see the AP is not joined to the controller, I still can only ping 10.0.0.2 (the management interface), I still cannot ping the vlan_employees interface (10.0.20.2), I cannot ping VLAN10 (10.0.0.1) or VLAN20 (10.0.20.1). I can ping the address the built-in AP is assigned though (currently through DHCP, it's ignoring my static IP address, 10.0.20.58). I am going about it the right way, trying to tell the WLC what APs are allowed to join? Using the config macaddress command? I am not certain which of the two MAC addresses for the WAP I am supposed to use either, whether I'm supposed to use the Base MAC or the AP EthernetMac (that's what they're called when I do the show ap join stats summary all).
I do not know what you mean by try using a txt file for the device config.
Thanks for helping.
... View more
Created by
Spork Schivago
in Other Wireless - Mobility Subjects
in Other Wireless - Mobility Subjects
01-31-2019
09:56 AM
01-31-2019
09:56 AM
Hi! I have a Cisco C1111-8PW router, which has a built-in WLC and a built-in Wireless AP. Currently, they are configured for FlexConnect, but I am having some issues setting up some VLANs on the WLC and the APs and using the VLANs, so I figured it's time to try ditching the FlexConnect and using Local Mode. I cannot seem to get the built-in AP to switch modes though. This is my current setup:
On the Router
-------------
!
interface GigabitEthernet0/0/1
description Gigabit Ethernet WAN port
mac-address <MAC ADDRESS SWITCHED FOR ONT>
ip address <STATIC PUBLIC IP> 255.255.255.128
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat outside
ip nbar protocol-discovery
ip verify unicast source reachable-via rx allow-default
ip access-group NO_OUTFACING_SERVICES in
speed 1000
no negotiation auto
vlan-range dot1q 1 40
!
end
!
interface Wlan-GigabitEthernet0/1/8
switchport trunk native vlan 10
switchport trunk allowed vlan 10,20,40
switchport mode trunk
end
interface Vlan1
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat inside
ip access-group BLOCK_INTERVLAN_ROUTING in
shutdown
!
interface Vlan10
description VLAN interface (Layer 3) with 254 Usable Hosts (10.0.0.1 - 10.0.0.254), network address 10.0.0.0
ip address 10.0.0.1 255.255.255.0
ip broadcast-address 10.0.0.255
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat inside
!
interface Vlan20
description VLAN interface (Layer 3) with 254 Usable Hosts (10.0.20.1 - 10.0.20.254), network address 10.0.20.0
ip address 10.0.20.1 255.255.255.0
ip broadcast-address 10.0.20.255
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat inside
!
interface Vlan40
description Guest VLAN interface (Layer 3) with 254 Usable Hosts (10.0.40.1 - 10.0.40.254), network address 10.0.40.0
ip address 10.0.40.1 255.255.255.0
ip broadcast-address 10.0.40.255
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat inside
!
ip access-list standard NAT_TRANSLATIONS
permit 10.0.0.0 0.0.0.255
permit 10.0.40.0 0.0.0.255
permit 10.0.20.0 0.0.0.255
!
ip access-list extended BLOCK_INTERVLAN_ROUTING
deny ip 10.0.0.0 0.0.0.255 10.0.40.0 0.0.0.255
deny icmp 10.0.0.0 0.0.0.255 10.0.40.0 0.0.0.255
permit ip any any
ip access-list extended NO_OUTFACING_SERVICES
deny tcp any any eq telnet
deny tcp any any eq 22
deny tcp any any eq www
deny tcp any any eq 443
deny tcp any any eq finger
deny tcp any any eq cmd
permit ip any any
WLC CONFIG: -----------
Number of Interfaces.......................... 3
Interface Name Port Vlan Id IP Address Type Ap Mgr Guest
-------------------------------- ---- -------- --------------- ------- ------ -----
management 1 10 10.0.0.2 Static Yes No
virtual N/A N/A 192.0.2.1 Static No No
vlan_employees 1 20 10.0.20.2 Dynamic No No
WLC BOOTUP MSG: ---------------
[*01/31/2019 12:22:26.6799] ethernet_port wired0, ip 10.0.20.3, netmask 255.255.255.0, gw 10.0.20.1, mtu 1500, bcast 10.0.20.255, dns1 1.0.0.1, is_static true, vid 0, static_ip_failover false, dhcp_vlan_failover false
[*01/31/2019 12:22:26.6899]
[*01/31/2019 12:22:26.6899] Configured VLAN Tag 20, failover_enabled 0
<CUT>
[*01/31/2019 12:22:29.5099] Failed to load flex AP config from file. Default config will be used.
[*01/31/2019 12:22:29.5599] Socket Valid Element wcp/wcp_db Handler set_vlan_name_map Data Length 10
[*01/31/2019 12:22:30.7799] ethernet_port wired0, ip 10.0.20.56, netmask 255.255.255.0, gw 10.0.20.1, mtu 1500, bcast 10.0.20.255, dns1 1.1.1.1, dns2 1.0.0.1, vid 20, static_ip_failover true, dhcp_vlan_failover false
[*01/31/2019 12:22:39.6099] DOT11_CFG[0] Radio Mode is changed from FlexConnect to FlexConnect
[*01/31/2019 12:22:39.6199] DOT11_CFG[1] Radio Mode is changed from FlexConnect to FlexConnect
[*01/31/2019 12:22:39.7199] AP IPv4 Address updated from 0.0.0.0 to 10.0.20.3
[*01/31/2019 12:22:39.7299] send CAPWAP ctrl msg to the socket: Socket operation on non-socket
[*01/31/2019 12:22:39.7299] send_msg_to_capwap_sm: Capwap SM restart message send failed for message: 9
[*01/31/2019 12:22:44.9899] AP IPv4 Address updated from 10.0.20.3 to 10.0.20.56
[*01/31/2019 12:22:44.9999] send CAPWAP ctrl msg to the socket: Socket operation on non-socket
[*01/31/2019 12:22:44.9999] send_msg_to_capwap_sm: Capwap SM restart message send failed for message: 9
[*01/31/2019 12:25:36.9999] chatter: tohost_virtual :: ToHost: device 'virtual' went down
[*01/31/2019 12:25:37.0399] chatter: tohost_vlan0 :: ToHost: device 'vlan0' went down
[*01/31/2019 12:25:37.0999] chatter: tohost_vlan1 :: ToHost: device 'vlan1' went down
<CUT>
Starting the Switchdriver...
Originally, I wanted it so the corporation stuff was on the 10.0.0.0 / 24 network, the guests were on a different network, like 10.0.40.0 / 24. I couldn't get that working right though, so I tried putting the WLC on the 10.0.0.0 / 24 network, I was going to have the APs on the 10.0.20.0 / 24 network, and then a WLAN called MyBusiness Guest on 10.0.40.0 / 24 network. To try and put the AP in Local mode, I typed this:
(WLC0) >show ap join stats summary all
Number of APs.............................................. 1
Base Mac AP EthernetMac AP Name IP Address Status
00:bf:77:e0:00:c0 00:a3:8e:95:ac:30 WAP0 10.0.20.56 Joined
(WLC0) >config macfilter add 00:a3:8e:95:ac:30 0 vlan_employees "Built-in WAP" 10.0.20.3
(WLC0)> config ap mode local submode none WAP0
I restarted, but as you can see from the WLC0's bootup messages that are displayed on the screen, the AP is still in the FlexConnect mode. Any ideas what I'm doing wrong in my attempt to stop using FlexConnect and switching everything over to Local mode? Any does anyone see anything wrong with the VLANs or know why from the WLC, I cannot reach the router or other various VLANs? I assigned the vlan_employees interface to the WLAN ID 1 (currently, the only wireless SSID). Thanks!
... View more
Created by
Spork Schivago
in Routing
in Routing
01-31-2019
09:24 AM
01-31-2019
09:24 AM
I think the WLC and router had some sort of caching going on somewheres, because no matter how I configure the router or the WLC interfaces, I cannot seem to reach the router or the outside world. I'm converting the AP to local mode (or trying). I believe the management interface has to be tagged. Very frustrating trying to get this working.
... View more
Created by
Spork Schivago
in Routing
in Routing
01-29-2019
10:00 PM
01-29-2019
10:00 PM
A bit of progress. If I set the management interface to VLAN10 and then on the built-in AP, I tag the packets with the VLAN ID 10, then the WLC can reach the outside world, but the AP fails to join the WLC with a message saying:
Layer 3 discovery request not received on management VLAN I'm not sure how to fix that, besides having the AP and WLC's management interface on different VLANs.
... View more
Created by
Spork Schivago
in Routing
in Routing
01-29-2019
11:06 AM
01-29-2019
11:06 AM
So I reset the WLC config to the default. Then I reconfigured just the very basics. I set the IP address of the management interface to 10.0.0.2 with the subnet mask of 255.255.255.0. I executed these commands after doing the basic auto-configure stuff:
config interface address management 10.0.0.2 255.255.255.0 10.0.0.1
config sysname WLC0
config prompt WLC0
ping 10.0.0.1
<ping failed>
config wlan disable 1
config interface vlan management 10
config wlan enable 1
ping 10.0.0.1
<ping failed>
So from the WLC0, I still cannot ping the VLAN10. I will search the internet to see if there's something else I'm missing here.... **EDIT: I am looking at the Cisco Mobility Express User Guide for 8.8 ( https://www.cisco.com/c/en/us/td/docs/wireless/access_point/mob_exp/88/user_guide/b_ME_User_Guide_88/getg_started.html ) I see this:
Configuring the Switch Port
Connect the access points to the switch and power them up. Ensure the following while configuring the switch port:
All access points, including the Master AP, in a Mobility Express network should be in the same L2 broadcast domain. Management traffic must not be tagged.
The switch port to which the Master AP is connected can be a trunk port or an access port and must be configured to trunk Native VLAN for management traffic. Data traffic must be trunked with appropriate VLANs for local switching as well.
The following is a sample switch port configuration.
Interface GigabitEthernet1/0/37
description » Connected to Master AP «
switchport trunk native vlan 122
switchport trunk allowed vlan 10,20,122
switchport mode trunk
The part that I'm worried about is the part that reads management traffic must not be tagged. Does that mean I am not supposed to put the management interface on VLAN 10? I thought the only way to put the management interface on the VLAN 10 was to tag the management interface with VLAN 10....
I see for the APs, I can run that Lightweight AP Software and from looking at the release notes, it looks like it's IOS. I wonder if I could install that Lightweight AP Software on the WLC and if that would make things a little easier. I dunno. I am kind of lost as to why from the WLC, even with a default config, after setting the IP of the management interface to 10.0.0.2, I cannot ping the router's VLAN10, regardless of whether I tag the management interface on the WLC0 for VLAN10 or not. I would think I'd have to tag the management interface with VLAN10 if I wanted it to be able to communicate with other clients on VLAN10.
... View more
Created by
Spork Schivago
in Routing
in Routing
01-29-2019
10:21 AM
01-29-2019
10:21 AM
I don't think it's something like a bad cable, I will say why. The WLC I call WLC0, and the built-in AP I call AP0. They are built into the router. I do not run any cables to them. I have been actively working on configuring the network more, like fine tuning it, setting up the VLANs, more security, etc. That is why I think it's a config issue.
... View more
Created by
Spork Schivago
in Routing
in Routing
01-29-2019
10:07 AM
01-29-2019
10:07 AM
Here's a copy of the WLC0's config, with some stuff masked, like usernames and password. I've attached it as a file because it's so long, but I've decided to post in the thread what I feel is the relevant sections. Maybe someone can see something I cannot see?
config ap next-preferred-master <MAC ADDRESS OF BUILT-IN WAP (WAP0)>
config interface dhcp management primary 10.0.0.1
config interface vlan management 10
config interface address management 10.0.0.2 255.255.255.0 10.0.0.1
config interface dhcp service-port enable
config interface dhcp dynamic-interface vlan_guests primary 10.0.40.1
config interface create vlan_guests 40
config interface vlan vlan_guests 40
config interface port management 1
config interface address virtual 192.0.2.1
config interface address dynamic-interface vlan_guests 10.0.40.2 255.255.255.0 10.0.40.1
config interface port vlan_guests 1
config flexconnect vlan-name-id template-entry add corning_vlan_template vlan_guests 40
config flexconnect vlan-name-id template-entry add corning_vlan_template vlan_enterprise 10
config flexconnect vlan-name-id create corning_vlan_template
config flexconnect vlan-name-id apply corning_vlan_template
config flexconnect group default-flexgroup predownload mac-master <MAC ADDRESS OF BUILT-IN WAP (WAP0)>
config flexconnect group default-flexgroup predownload enable
config flexconnect group default-flexgroup vlan override-ap enable
config flexconnect group default-flexgroup vlan native 1
config flexconnect group default-flexgroup wlan-vlan wlan 1 add vlan 10
config flexconnect group default-flexgroup wlan-vlan wlan 2 add vlan 40
config flexconnect group default-flexgroup ap add <MAC ADDRESS OF BUILT-IN WAP (WAP0)>
config flexconnect group default-flexgroup avc 1 profile "Corning Electronics" enable
config flexconnect group default-flexgroup avc 1 visibility enable
config flexconnect group default-flexgroup avc 2 profile "Corning Electronics Guest" enable
config flexconnect group default-flexgroup avc 2 visibility enable
config flexconnect group default-flexgroup add
config flexconnect group default-flexgroup radius ap authority info "Cisco A_ID"
config flexconnect group default-flexgroup radius ap authority id <authority ID>
config flexconnect group default-flexgroup radius ap server-key encrypt 1 <password>
config flexconnect group default-flexgroup template-vlan-map add corning_vlan_template
I do not have a radius or a TACACS+ server setup yet, but I was working on setting one up. I wonder if that's causing some issues. I'm tempted to do a factory reset and clear the config on the APs and the WLC and try from scratch. Might be easier than trying to figure out what I did wrong. So, just to be clear, the management IP address on the WLC is 10.0.0.2 / 24 and the vlan_guests IP is 10.0.40.2. Two SSIDs, Corning Electronics (which gets assigned to the 10.0.0.0 / 24 network) and Corning Electronics Guest (which gets assigned to the 10.0.40.0 / 24 network). Currently, I cannot ping the 10.0.40.2 IP from the WLC! It's almost as if the vlan interface is shutdown. I also cannot ping anything outside of the WLC, minus the built-in AP IP address.
... View more
Created by
Spork Schivago
in Routing
in Routing
01-29-2019
09:23 AM
01-29-2019
09:23 AM
@tobyarnett,
Before I realized I couldn't access the 10.0.40.0 / 24 network from the WLC, we had some issues on the 10.0.0.0 / 24 network. We would lose packets and after investigating, we noticed the interfaces on the router was dropping unknown packets. The first thing I did was download the NBAR pack and update it, but that didn't fix the problem. So, then on the WAN facing interface, I disabled spanning-tree, and on that WAN facing interface, those dropped packets stopped. So for testing purposes, I disabled the spanning tree on the various access ports. When re-enabling it, I see this message:
%Warning: portfast should only be enabled on ports connected to a single
host. Connecting hubs, concentrators, switches, bridges, etc... to this
interface when portfast is enabled, can cause temporary bridging loops.
Use with CAUTION
%Portfast has been configured on GigabitEthernet0/1/0 but will only
have effect when the interface is in a non-trunking mode.
I said to myself, well, the AP is one host, but it's kind of like a switch in a way. The WLC, for instance, has multiple interfaces, on different networks. So maybe it should be left disabled? Should I go through and reenable it on all the switch ports? The ones that are in access mode? But keep it disabled on the Wlan-GigabitEthernet 0/1/8 trunk port? Something odd is going on, something I cannot figure out. The WLC's management interface has the IP address of 10.0.0.2 / 24. From the router, I can ping this 10.0.0.2 interface. From the WLC, I cannot ping anything on the router side. How is that possible? The router sends an ICMP packet, but the WLC has to respond...from the WLC side, if it cannot reach the 10.0.0.1 VLAN interface that's on the router, how can the router reach the 10.0.0.2 interface that is on the WLC? I will post my WLC config. I believe FlexConnect is setup properly. I was under the impression if I was going to have the WLANs on multiple networks, like I do (the company's WLAN is on the 10.0.0.0 / 24 network, the guest is on the 10.0.40.0 / 24 network, and there's going to be a couple more once I figure it all out), I was supposed to use FlexConnect mode.
... View more
Created by
Spork Schivago
in Routing
in Routing
01-28-2019
03:15 PM
01-28-2019
03:15 PM
@tobyarnett
I have tried configuring at suggested, but after doing so, I cannot reach the WLC at all from the router and vice-versa. Here is the current configuration of some of the interfaces:
!
interface Loopback0
description Local Loopback interface with 6 Usable Hosts (10.10.10.97 - 10.10.10.102), network address 10.10.10.96
ip address 10.10.10.100 255.255.255.248
ip broadcast-address 10.10.10.103
!
interface GigabitEthernet0/0/0
mac-address a093.5188.4f01
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
ip nbar protocol-discovery
media-type sfp
negotiation auto
!
interface GigabitEthernet0/0/1
description Gigabit Ethernet WAN port
mac-address a093.5188.4f00
ip address <STATIC PUBLIC IP> <NETMASK>
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat outside
ip nbar protocol-discovery
ip verify unicast source reachable-via rx allow-default
ip access-group NO_OUTFACING_SERVICES in
speed 1000
no negotiation auto
!
interface GigabitEthernet0/1/0
switchport access vlan 10
spanning-tree portfast disable
!
interface GigabitEthernet0/1/1
switchport access vlan 10
spanning-tree portfast disable
!
interface GigabitEthernet0/1/2
switchport access vlan 10
spanning-tree portfast disable
!
interface GigabitEthernet0/1/3
switchport access vlan 10
!
interface GigabitEthernet0/1/4
switchport access vlan 10
!
interface GigabitEthernet0/1/5
switchport access vlan 10
!
interface GigabitEthernet0/1/6
switchport access vlan 10
!
interface GigabitEthernet0/1/7
switchport access vlan 10
!
interface Wlan-GigabitEthernet0/1/8
switchport trunk native vlan 900
switchport trunk allowed vlan 10,40
switchport mode trunk
!
interface Vlan1
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat inside
ip access-group BLOCK_INTERVLAN_ROUTING in
shutdown
!
interface Vlan10
description Enterprise VLAN interface (Layer 3) with 254 Usable Hosts (10.0.0.1 - 10.0.0.254), network address 10.0.0.0
ip address 10.0.0.1 255.255.255.0
ip broadcast-address 10.0.0.255
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat inside
!
interface Vlan40
description VLAN interface (Layer 3) with 254 Usable Hosts (10.0.40.1 - 10.0.40.254), network address 10.0.40.0
ip address 10.0.40.1 255.255.255.0
ip broadcast-address 10.0.40.255
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat inside
!
ip nat inside source list NAT_TRANSLATIONS interface GigabitEthernet0/0/1 overload
ip forward-protocol nd
ip http server
ip http authentication local
ip http secure-server
ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0/1 <GATEWAY> permanent name ETC-BLK2
ip ssh time-out 60
ip ssh authentication-retries 2
!
!
ip access-list standard NAT_TRANSLATIONS
permit 10.0.0.0 0.0.0.255
permit 10.0.40.0 0.0.0.255
!
ip access-list extended BLOCK_INTERVLAN_ROUTING
deny ip 10.0.0.0 0.0.0.255 10.0.40.0 0.0.0.255
deny icmp 10.0.0.0 0.0.0.255 10.0.40.0 0.0.0.255
permit ip any any
ip access-list extended NO_OUTFACING_SERVICES
deny tcp any any eq telnet
deny tcp any any eq 22
deny tcp any any eq www
deny tcp any any eq 443
deny tcp any any eq finger
deny tcp any any eq cmd
permit ip any any
ip access-list extended NO_WEBCONFIG_SERVICES
deny tcp any any eq www
deny tcp any any eq 443
permit ip any any
!
ip access-list match-local-traffic
logging trap debugging
logging facility local2
access-list 100 permit udp any any eq bootpc
!
Router01#show interfaces wlan-GigabitEthernet 0/1/8 switchport
Name: Wl0/1/8
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 900 (NativeID)
Administrative Native VLAN tagging: enabled
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk associations: none
Administrative private-vlan trunk mappings: none
Operational private-vlan: none
Trunking VLANs Enabled: 10,40
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL
Protected: false
Priority for untagged frame: 0
Override vlan tag priority: FALSE
Appliance trust: none
Router01#show interface trunk
Port Mode Encapsulation Status Native vlan
Wl0/1/8 on 802.1q trunking 900
Port Vlans allowed on trunk
Wl0/1/8 10,40
Port Vlans allowed and active in management domain
Wl0/1/8 10,40
Port Vlans in spanning tree forwarding state and not pruned
Wl0/1/8 10,40
I have tried tagging and not tagging the management interface on the WLC. I've tried tagging it with VLAN ID 10, and then just untagging it (not assigning it a VLAN), but neither way do it allow me to reach the router from the WLC or vice-versa. Frustrating. If I plug an ethernet cable into one of the ports on the router, I am assigned an IP from the Enterprise DHCP pool and I can reach the outside world...any suggestions on what I'm doing wrong? I suspect it's now something on the WLC, not the router.
... View more
Created by
Spork Schivago
in Routing
in Routing
01-28-2019
02:08 PM
01-28-2019
02:08 PM
@tobyarnett, Thanks for the reply. I see the WLC and APs are currently in FlexConnect mode. Is that wrong for my setup? Here is a list of the VLAN IDs and their mappings on the router:
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Gi0/1/0, Gi0/1/1, Gi0/1/2
Gi0/1/3, Gi0/1/4, Gi0/1/5
Gi0/1/6, Gi0/1/7
40 GUESTS active
1002 fddi-default act/unsup
1003 token-ring-default act/unsup
1004 fddinet-default act/unsup
1005 trnet-default act/unsup
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
1 enet 100001 1500 - - - - - 0 0
40 enet 100040 1500 - - - - - 0 0
1002 fddi 101002 1500 - - - - - 0 0
1003 tr 101003 1500 - - - - - 0 0
1004 fdnet 101004 1500 - - - ieee - 0 0
1005 trnet 101005 1500 - - - ibm - 0 0
Primary Secondary Type Ports
------- --------- ----------------- ------------------------------------------
Here's the VLAN interfaces:
Vlan1 is up, line protocol is up
Hardware is Ethernet SVI, address is a093.5188.4f74 (bia a093.5188.4f74)
Description: VLAN interface (Layer 3) with 254 Usable Hosts (10.0.0.1 - 10.0.0.254), network address 10.0.0.0
Internet address is 10.0.0.1/24
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not supported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 01:02:13, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 6000 bits/sec, 3 packets/sec
5 minute output rate 1000 bits/sec, 2 packets/sec
6407358 packets input, 746600739 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
12422276 packets output, 14963271193 bytes, 0 underruns
0 output errors, 1 interface resets
109 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
Router01#show interfaces vlan 40
Vlan40 is up, line protocol is up
Hardware is Ethernet SVI, address is a093.5188.4f74 (bia a093.5188.4f74)
Description: VLAN interface (Layer 3) with 254 Usable Hosts (10.0.40.1 - 10.0.40.254), network address 10.0.40.0
Internet address is 10.0.40.1/24
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not supported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 1d22h, output 00:09:43, output hang never
Last clearing of "show interface" counters never
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1426860 packets input, 111304746 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
3248757 packets output, 4182025556 bytes, 0 underruns
0 output errors, 1 interface resets
89 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
I also have a ToR switch that I will be connecting to the router sooner or later, and I will need to setup the various VLANs on that switch as well, but I do not think that will be a problem. I just want to make sure I'm doing this right here. I'm catching on with the VLAN stuff, but the tagging stuff still confuses me a bit. So I am unconfiguring VLAN1 (the default VLAN) on the router and the WLC. I am creating a VLAN10 on the router and the WLC. I will assign the management port to VLAN10 on the WLC. I am going to keep the VLAN40 the way it is. On the router, I will assign whatever ports that are currently assigned to VLAN1 to VLAN10. So GigabitEthernet 0/1/0 - 0/1/7 now get assigned to VLAN10. After this, I think I have to figure out why the APs cannot connect to the WLC, but perhaps that's a better question for the wireless mobility thread. I know if I assign the management port on the WLC to a VLAN, and then assign the APs to the same VLAN, the APs never join. I suspect it has something to do with how those interfaces on the router's switch module are configured. I am going to setup the new VLANs now though and go from there.
... View more
Created by
Spork Schivago
in Routing
in Routing
01-27-2019
06:48 PM
01-27-2019
06:48 PM
I think you're right. I will add some stuff and I think I know why it broke. The router I have is a Cisco C1111-8PW that has a built-in WLC and a built-in AP. The three extra APs I have are 1832i's. None of them are very heavy duty, if you will. For example, all the web configuration examples I've seen for routers, WLCs, etc have a LOT more features than the web interface pages I see, so I have to do almost everything from the CLI, which isn't bad, but it'd be nice to have a dedicated, stand-alone WLC, and maybe something like the Cisco 3802i's would be nicer. The router is running IOS XE 16.06.05. The APs are running Mobility Express 8.8.111.0. I noticed online, some APs have IOS running. These are not like this for some reason. The OS is IOS like, but it's not IOS. I think I know why things broke. I powered up the other APs. I forgot all about them. I just plugged them into the router's ports and then started configuring them via the WLC's console cable. The APs are on interface GigabitEthernet 0/1/0 - 0/1/2. I bet I have to configure those interfaces on the router as well. I tried, and things did start happening. One was able to obtain an IP address from the DHCP server and got a 10.0.40.0 address, and I was able to reach the outside, but things got real weird when those APs where on a trunk line. They all acted like they were the built-in AP for the WLC. I could see each one, individually, had joined the WLC, but if I moved to the next AP, that one joined and the previous one didn't show. For example, While on WAP0, the WLC0 shows WAP0 was joined. But on WAP1, the WLC0 shows WAP0 is not joined, but WAP1 is joined. On WAP1, I had the WLC0 prompt, like I should have with only WAP0. This confused me a bit. I think I am going to call it a night and then tomorrow, I will implement your suggestions. The way I understand the native VLAN is if a packet comes from that native VLAN, only accept traffic from the VLAN if it's untagged. If that's correct, I am missing something. If the packet is untagged, how does the router know it came from the native VLAN? Thanks for the help and suggestions on how best to set this up. You guys are great.
... View more
Created by
Spork Schivago
in Routing
in Routing
01-27-2019
04:33 PM
01-27-2019
04:33 PM
I did just notice something in the config interface wlan-gigabitethernet 0/1/8's window. I saw a option called port-tagging. So I enabled it. I typed:
Router01(config-if)#port-tagging
Router01(config-if-port-tagging)#encapsulation ?
dot1ad IEEE 802.1AD Virtual LAN or S-VLAN
dot1q IEEE 802.1Q Virtual LAN or S-VLAN
Router01(config-if-port-tagging)#encapsulation dot1q ?
<1-4094> VLAN id
Router01(config-if-port-tagging)#encapsulation dot1q 40
Perhaps this was how I enable the dot1q encapsulation? When I do that though, I cannot ping either of the networks on the WLC. I tried setting the encapsulation dot1q to VLAN id 1 but that still did not allow me to ping the 10.0.0.0 / 24 addresses.
... View more
Created by
Spork Schivago
in Routing
in Routing
01-27-2019
04:24 PM
01-27-2019
04:24 PM
Andrew,
Thank you for the reply. I should add that we are actively working on fine tuning the configurations on the network equipment (we are a fairly new company) and there is a chance we did break something old while trying to configure something new, or had something configured properly but forgot to save the config file and the WLC rebooted.
I have tested this. I logged into the WLC using a console cable. I issued the command show interfaces summary and here is the output:
(WLC0) >show interface summary
Number of Interfaces.......................... 3
Interface Name Port Vlan Id IP Address Type Ap Mgr Guest
-------------------------------- ---- -------- --------------- ------- ------ -----
management 1 1 10.0.0.2 Static Yes No
virtual N/A N/A 192.0.2.1 Static No No
vlan_guests 1 40 10.0.40.2 Dynamic No No
(WLC0) >
What I find very frustrating and odd is that from the WLC0, I cannot ping 10.0.40.2. I cannot ping it at all, despite the fact that the vlan_guests dynamic interface was created on WLC0...even when I tell ping to use the source interface vlan_guests, I still cannot ping 10.0.40.2. So I think maybe the problem lies with the WLC somewheres.
Here is the information you requested though:
Router01#show ip interface brief
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0/0 unassigned YES NVRAM down down
GigabitEthernet0/0/1 <my public IP> YES TFTP up up
GigabitEthernet0/1/0 unassigned YES unset up up
GigabitEthernet0/1/1 unassigned YES unset up up
GigabitEthernet0/1/2 unassigned YES unset up up
GigabitEthernet0/1/3 unassigned YES unset up up
GigabitEthernet0/1/4 unassigned YES unset down down
GigabitEthernet0/1/5 unassigned YES unset down down
GigabitEthernet0/1/6 unassigned YES unset down down
GigabitEthernet0/1/7 unassigned YES unset down down
Wl0/1/8 unassigned YES unset up up
Loopback0 10.10.10.100 YES NVRAM up up
Vlan1 10.0.0.1 YES NVRAM up up
Vlan40 10.0.40.1 YES NVRAM up up
From the router, I can 10.0.40.1, but I cannot ping 10.0.40.2. This makes me think perhaps the router is fine, just the built-in WLC0 has an issue somewheres.
... View more
Created by
Spork Schivago
in Routing
in Routing
01-27-2019
04:16 PM
01-27-2019
04:16 PM
Mark, Thank you for the reply. Unfortunately, I cannot create a sub-interface on the WLan-GigabitEthernet 0/1/8 port. From what I've been reading though, if the switchport trunk encapsulation doesn't exist (if it doesn't show as an option while configuring the trunk port on the router), then the router is using the dot1q encapsulation by default and there is nothing else that needs to be done. So I no longer think that not being able to configure the Dot1q encapsulation on the router is the fault. I think it's something else.
... View more
02-04-2019
Thank you! I also believe it's a configuration issue. I am uploading a
hand-drawn picture of my netw...
01-31-2019
@Flavio Miranda,Thank you for the reply. Currently, because I cannot
access any GUIs at all, I must ...
01-31-2019
Hi! I have a Cisco C1111-8PW router, which has a built-in WLC and a
built-in Wireless AP. Currently,...
01-31-2019
I think the WLC and router had some sort of caching going on somewheres,
because no matter how I con...
01-29-2019
A bit of progress. If I set the management interface to VLAN10 and then
on the built-in AP, I tag th...
01-29-2019
So I reset the WLC config to the default. Then I reconfigured just the
very basics.I set the IP addr...
01-29-2019
I don't think it's something like a bad cable, I will say why. The WLC I
call WLC0, and the built-in...
01-29-2019
Here's a copy of the WLC0's config, with some stuff masked, like
usernames and password.I've attache...
01-29-2019
@tobyarnett, Before I realized I couldn't access the 10.0.40.0 / 24
network from the WLC, we had som...
01-28-2019
@tobyarnett I have tried configuring at suggested, but after doing so, I
cannot reach the WLC at all...
01-28-2019
@tobyarnett,Thanks for the reply. I see the WLC and APs are currently in
FlexConnect mode. Is that w...
01-27-2019
I think you're right.I will add some stuff and I think I know why it
broke. The router I have is a C...
01-27-2019
I did just notice something in the config interface wlan-gigabitethernet
0/1/8's window. I saw a opt...
01-27-2019
Andrew, Thank you for the reply. I should add that we are actively
working on fine tuning the config...
Public Statistics
| Date Registered | 01-16-2019 09:21 AM |
| Date Last Visited | 05-02-2019 01:16 AM |
| Total Messages Posted | 45 |
| Total Helpful Votes Received | 10 |
Helpful Votes Given To
| User | Helpful Count |
|---|---|
| 10 | |
| 10 | |
| 15 | |
| 5 | |
| 5 |
.jpg "VIP Advisor"){kind=icon}
