Controller interface vlan identifier

Are the VLAN identifiers configured on the controller interfaces relevant when using H-REAP APs with VLAN mappings?

The vlan identifiers are configured on the interfaces of the wlc. In h-reap, the wlan points to the management interface which should be set to untagged "0". When the ap is set to h-reap mode, that is where you would specify the locally switched vlan id. The native vlan id on the h-reap ap is important though. Management interface of the h-reap ap should be configured for native. Does this answer you question???

Similar Messages

Cisco 2504 controller, setting management wlan interface Vlan Identifier to anything but 0 loses management ability

I have setting the Management Interface Vlan Identifier to 0 or untagged.
If i change this to a vlan, I am unable to manage the device, is this correct?
Steve

If u make it untagged then specify the NATIVE vlan on the switchport..
If u tag the management interface, then dont configure the native vlan on the switchport..
Both the cases u will be able to access!!
Lemme know if this answered ur question!!
Regards
Surendra

WLAN Controller 2125 VLAN issue

Hello,
i purchased a WLan Controller 2125.
this is my first time with Cisco's Wireless Controller :-)
previously i have worked with Motorola WLan Controller. configuring Vlan was easy.
now coming back to cisco Controller
i have installed and completed the initial configuration such as management console and 1st SSID working fine.
according to Company's requirement there should be 3 SSID's
1) management    VLAN-1 identifier   subnet 15.15.x.x           (SSID - VLAN-1)(interface1)
2) Guest             VLAN-20 identifier subnet 192.168.10.0      (SSID - VLAN-20)(interface2)
3) employees      VLAN-30 identifier subnet   20.20.x.x          (SSID - VLAN-30)(interface3)
now the issue is only the SSID VLAN-1 is working. i beleive it is because its under the VLAN1 and management interface.
as for fulfilling network requirement i have connected controller with L3 switch as below
controller's interface1 connected to trunking interface on the switch
controller's interface2 connected to interface vlan-20 on the switch
controller's interface3 connected to interface vlan-30 on the switch
i have also configured DHCP on controller for each SSID(interface)
I CANT EVEN PING the GATEWAY FROM THE SSID VLAN-20 & VLAN-30.
HELP Pls

First at all, test those other 2 vlans fromthe switch side just to make sure are working.
If it is working and not wirelessly, then I would need the show run-config and show arp switch
from the switch side, show cdp nei detail and show run and show arp

Help with wireless controller and VLANs

Hi I'm trying to setup a wireless controller in preparation for a large site go live later this year. I'm struggling to get the controller and the WLAN using the correct VLAN. I want the controller on VLAN 100 and the clients on the WLAN on VLAN 200.
My thought is that I would need a config similar to:
Switchport for wireless controller management port set to trunk VLAN 100 and 200 with no native VLAN set.
The management interface on the controller set to VLAN 100.
A dynamic interface created on VLAN 200.
When setup like this I can get to the controller on its management address but only from VLAN100 not from another VLAN on site or from other sites over the WAN.
I have setup a WLAN which is set to use the dynamic interface on VLAN 200.
I have set the AP to use HREAP and set the native VLAN as 200 and added the dynamic interface into the VLAN mappings
When I connecting a client to the WLAN I get an address on VLAN 100.
The switchport for the AP is set to native VLAN 100 and trunk 200 – this setup works for standalone APs at other sites.
What am I missing?
Also any idea why the management interface address is not routing? The netmask and gateway are set correctly.
Thanks
Paul

Just to add to Steve's post... You only need to create a dynamic interface for vlan 200 if you have ap's also in local mode. If your ap's are in H-REAP/FlexConnect mode, you don't need a dynamic interface for vlan 200.
In you H-REAP/FlexConnect ap, you would set the wlan to vlan mapping there and the switchport configuration would be a trunk allowing vlan 100 (im assuming your native vlan for your ap) and vlan 200. You should see something like the following:
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

5500 controller interfaces

The other day I configured our 5500 controllers to enable an Airplay application. Previously configured under 'Controller/mDNS' were 'Airprint', 'Airplay', and 'AppleTV' for another application. After some time on Google I found that to allow the 'Airplay' service to advertise from a wired machine running the application to a wireless iPad I had to add an interface under 'Controller/Interfaces' for each VLAN that one of these wired Airplay machines could be in.
This worked perfectly and solved the problem, however when I added an interface for VLAN 280 all of a sudden I could no longer log in to the controller with my TACACS+ user ID only the local admin account. It is no coincident that the Cisco ACS servers that run TACACS were in that VLAN. Previously to adding a VLAN 280 interface TACACS communication was via the management interface on VLAN 400.
A few Wireshark hours later I found that there was no TACACS communication between the controller and the ACS server. No TACACS traffic originating from the controller and none arriving at the WCS server. (RADIUS authentications for wireless clients continued to work for some reason)
The problem was solved by changing the IP addresses of the VLAN 280 interface to a bogus address.
My problem now is I'm not quite sure why adding a wired VLAN interface in the same VLAN as the ACS servers broke TACACS and why changing that interface IP address to a bogus one fixed the issue.

OK, got it.
Right after adding the vlan280 interface with a good address to WCS both Radius and TACACS broke. We fixed Radius by adding the vlan280 address of WCS to the ACS server as a radius client. After changing the vlan280 interface address in WCS to a bogus address we were able to remove it from ACS without issue.
However, TACACS already had both the vlan400 management address and the vlan280 addresses. The only thing that fixed this was the bogus address.
This is all moot anyway. When WCS has a good address for the vlan280 interface it does not send any TACACS traffic at all. Using Wireshark and monitoring the switchports that connect WCS to the network I could not see any traffic whatsoever coming from WCS during attempts to login.
When WCS has a bogus address for the vlan280 interface I do see the TACACS traffic being sent to ACS as well as the responses back from ACS.

Interface Vlan is not installed in routing table

Dear All,
Today I faced a strange problem and I want to share it with you to find what is the problem ?
we have a VRF for one customer and we use interface vlan to define customer's branch.
The customer interface is VLAN 422 and it is defined under customer VRF probably .
PE#sh running-config vrf V3056:RIYADHBANK
Building configuration...
Current configuration : 1321 bytes
ip vrf V3056:RIYADHBANK
rd 65000:3887
maximum routes 1400 80
route-target export 65000:5405
route-target import 65000:5405
route-target import 65000:5406
interface Vlan422
description By *****
ip vrf forwarding V3056:RIYADHBANK
ip address 172.29.12.97 255.255.255.252
service-policy input 2M_IN
PE#sh vlan id 422
VLAN Name Status Ports
422 422 active Gi3/0/11 efp_id 422
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
422 enet 100422 1500 - - - - - 0 0
Remote SPAN VLAN
Disabled
Primary Secondary Type Ports
PE#
we can see the interface vlan is up
PE-L3Agg-Khu-107-2#sh int vlan 422 description
Interface Status Protocol Description
Vl422 up up ****
PE#
and we can see the vlan 422 belongs to the correct VRF
PE#sh vrf V3056:RIYADHBANK
Name Default RD Protocols Interfaces
V3056:RIYADHBANK 65000:3887 ipv4 Vl627
Vl775
Vl422
PE#
when we tried to troubleshoot the customer routing we found :
PE-L3Agg-Khu-107-2#ping vrf V3056:RIYADHBANK 172.29.12.97
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.29.12.97, timeout is 2 seconds:
Success rate is 0 percent (0/5)
PE-#
we could not ping the ip address of interface vlan 422.
PE#sh ip route vrf V3056:RIYADHBANK 172.29.12.97
Routing Table: V3056:RIYADHBANK
% Subnet not in table
PE#
PE#show ip route vrf V3056:RIYADHBANK connected
Routing Table: V3056:RIYADHBANK
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is 192.168.111.16 to network 0.0.0.0
172.29.0.0/16 is variably subnetted, 338 subnets, 2 masks
C 172.29.12.44/30 is directly connected, Vlan627
L 172.29.12.45/32 is directly connected, Vlan627
PE-L3Agg-Khu-107-2#
PE-L3Agg-Khu-107-2#
My question is: Why the interface vlan 422 is not installed in VRF Table as it is UP ??
thanks in advance!
Rashed Wardi.

what platform is this? can you please paste the output of show version and show run?
Also when you tested this was int Gi3/0/11 up/up?
Best Regards,
Bheem

WLC 5508 , AP client dhcp address different from WLAN interface VLAN subnet?

Hope the title makes sense, here's my situation: I have multiple businesses on 1 WLC 5508, there's a LAG to my core switch with seperate interfaces for each, broken up by vlans.
My question is: if i have a WLAN setup to use interface "Company A" which is vlan 10 with an ip of 10.0.1.5 which then points to 10.0.1.10 for dhcp.
Can the WLAN client connecting to the Company A WLAN use an IP in a different IP range?(192.168.1.10?) can the wlc route? from the perspective of the DHCP server where doers the request come from? (10.0.1.5?)
Can the DHCP server 10.0.10.10 on vlan 10 respond back with and ip on a different subnet to assign to the client to use and still be fully fonctioning? would the default gateway for the client need to be 10.0.1.5? So the clients ip would be 192.168.1.10 /24 with a gateway of 10.0.1.5 (ip adress fo vlan10 interface on WLC) And if multiple clients on the same subnet wanted to talk to each other woudl the WLC know how to route them to each other without passing through the default gateway?
Sorry if this is confusing I'm having a bit of a hard time explaining it in works, i can try and draw somethign up if it makes more sense.
thanks
Eric

I think if you want these clients to stick to a WLAN configured on a VLAN that has a different IP addressing you could configure your VLAN with the normal IP addressing then add on the SVI the 2nd IP_Class_default_gateway.
E.G.
Vlan 10
interface vlan 10
ip address 10.0.10.1 255.255.255.0
ip address 192.168.1.1 255.255.255.0 secondary
Clients that receive IP address from 192.168.1.0/24 network will be able to reach 192.168.1.1 and all traffic will pass right.

FAQ: AII-DC-RFID (Auto ID Infrastructure - Device Controller Interface)

Version: 20060317
Q: Where can i find more information to the AII-DC-RFID interface ?
A: Have a look on our ICC webpage in the SDN:
SAP Supply Chain Management- Device Controller Interface (AII-DC-RFID) [original link is broken]
Q: What costs are arising when we want our product to be certified ?
A: See also out SDN page under the headline "Price List".
Q: Is there a link/page for the already certified products for this interface ?
A: Sure, have a look on our ICC page under the headline "Certified Solutions"
Q: Who can we ask in case of general question ?
A: Have a look at our general ICC forum:
SAP Integration and Certification Center (SAP ICC)
Of course, if you have urgent requests you can send them also directly to our local ICC's:
ICC Walldorf in Germany: [email protected]
ICC Palo Alto in USA: [email protected]
ICC Bangalore in India: [email protected]
Q: Who can we ask in case of technical questions ?
A: This depends on the state of your certification project.
1.) If the certification contracts have been signed then you can ask in this forum and if this does not solve your question go back to your assigned integration consultant.
2.) When the certification contracts have not been signed then you can ask questions in this forum.
Q: Are there differences between version 2.1 and 4.0 ?
A: The interface has no changes from AII 2.1 to AII 4.0.

Hi Sara,
SAP Device Controller Interface is the interface that will be used by device controller softwares to send data to SAP AII and vice versa. Device controllers filter the RFID reads and send a unique read event to SAP AII. SAP AII on receiving this message processes it. It can be the case that as part of processing we also require to send data back to devices/controller or send a command such as tag commissioning. At this time also the same interface is used.
Regards,
Yogesh Bhatia..

SAP Auto-ID Infrastructure Device Controller Interface

Hi,
Could you please explain the use of SAP Auto-ID Infrastructure Device Controller Interface?
Thanks & Regards
Sara

Hi Sara,
SAP Device Controller Interface is the interface that will be used by device controller softwares to send data to SAP AII and vice versa. Device controllers filter the RFID reads and send a unique read event to SAP AII. SAP AII on receiving this message processes it. It can be the case that as part of processing we also require to send data back to devices/controller or send a command such as tag commissioning. At this time also the same interface is used.
Regards,
Yogesh Bhatia..

Just installed the newest version. the controller interface doesn't work.

Just installed the newest version. the controller interface doesn't work.
Hello, I just installed the newest version from App Store.
I did not download the drum stuff when open the app for the first time (the check box that you can un-cheack it).
I open and try to go to the Control interface but it kept saying that it cannot find the layout.
Please help.
Thank you.

Sorry to post in the wrong place.
I try to move to post but didn't have authorize.
I guess I will be posting another one in the Garageband for Mac room.

HP Compaq dc7700p INTEL HOST EMBEDDED CONTROLLER INTERFACE (HECI) DRIVER

Hi.
I jusy took a HP Compaq dc7700p Small Form Factor. I just realised that there is no Intel Host Embedded Controller Interface (Heci) Driver. I use Windoes 7 32 bit. Why there is no driver for this computer with this System? I need help I really need to do a Wireless Connection please. And the sp34743.exe it's not helping at all.
Caprice77

Hi:
Unfortunately I do not know how to activate the AMT hardware.
I doubt that has anything to do with the wireless not working.
In the device manager, is there a device listed under an Other Devices category labeled as a Network Controller?
If there is, that is the wireless card that needs a driver.
If there is no Network Controller device listed, then your PC does not have a wireless card. That was a rare option on an HP business desktop.
If there is a Network Controller device listed, please do the following...
Go to the device manager and click on that Network Controller device needing drivers.
Then click on the Details tab. Now you see a Property drop down list and it is defaulted to Device Description.
Drop down on that and select the second item on the list (Hardware ID's).
Post the top string of characters you see there.

How to exclude the monitoring (device avaibility) on an interface vlan?

Hello All,
How can i exclude the monitoring on an "intervace vlan"
My switch 3750X have many interface vlan , LMS 4.2.2 discover the device and have an automatic poller that test the reachability on the IP for these interface vlan.
And i have many Critical alarmes when the interface vlan is down, because no end host are in this vlan
(Operationaly Down, Unresponsive).
Thank you.
Alain Pernelle.

Hello pkr_legend,
Take a look at these symptoms and see if the troubleshooting steps help to resolve your issues. Please let me know.
Good luck!
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

Usb Arcade Controller Interface - Axis problem

Hello sweet Arch user!
I have funny little problem I can’t see to solve myself, and I have searched the forum and the rest of the Net for solutions.
I got a Joystick/control-panel interface used in a homemade Arcade Cabinet. It got 4 axis (2x4 microswitches) and 22 buttons and is connected with USB.
It shows up as a joystick and is working perfectly in Windows XP / Debian (stable) / Archbang (Iso 2011/11). But the problem is when I use an up-to-date Arch version.
The 2 joysticks only works with DOWN and RIGHT, and nothing happens when I
Try UP or LEFT.
Tried jscal, jstest and cat /dev/input/js0, and the only thing that isn’t showing any event is LEFT and UP. In the other distros I got a negative value on these directions running jstest.
Any ideas what I can do? I still would like to use Arch for this Cabinet.
The only module loaded is joydev.
The Controller interface is made by Xin-Mo
Regards
//Andreas

Hello
I'm having the exact same problem.
I'm using a "PC (MAME) / PS3 to Arcade Controller USB Interface PCB Kit" http://www.jammaboards.com/store/pc-mam … a-usb.html
It also works perfectly on Ubuntu 12.04 LTS
This is the closest thing I've seen as a fix, but my knowledge doesn't allow me to know how to implement on my system
https://github.com/robmcmullen/hid-atari-retrobit
Any help would be greatly appreciated.
Thank you,
-Mike

Advanced Host Controller Interface (AHCI) support on a "P31 NEO-F"

hi all.. does my mainboard ( msi p31 neo-f ) supports native Advanced Host Controller Interface (AHCI) to use hdd hotplug with one sata>esata bracket?

Quote
not having a "safely remove hardware and eject media" its always a bit scary! some cached files will not be dumped to the hdd and cause errors.
Again, as long as you do not remove the hard drive (or plug it in) while the system is running, there will be no problem.

Interface vlan - ACL - pinging issues.

I'm trying to understand why an ACL which is applied to an interface vlan is affecting the traffic for a different interface vlan.
Both vlans are configured on the same device and there's a trunk connecting the "access" switch to the "distribution" switch.
so, what we have is:
UD-1 UD-1B
UA
Int vlan are configured in both UDs and the vlan is allowed in the trunk that connects the UD to the UA.
There's an ACL blocking traffic to the int vlan 225 ip that is configured in the UA, but there's no ACL on the vlan 185 (the same IP that Im trying to ping).
So , why is this happening?
configs:
UD-1A:
interface Vlan185
ip address 10.8.185.3 255.255.255.0
interface Vlan225
ip address 10.18.225.3 255.255.255.0
ip access-group ud1 in
int gi1/1
interface GigabitEthernet1/1
switchport trunk encapsulation dot1q
switchport trunk native vlan 225
switchport trunk allowed vlan 185,225
switchport mode trunk
UD-1B
interface Vlan185
ip address 10.8.185.4 255.255.255.0
interface Vlan225
ip address 10.18.225.4 255.255.255.0
ip access-group al_rpf_sre_ud1_pro in
interface GigabitEthernet4/4
switchport trunk encapsulation dot1q
switchport trunk native vlan 225
switchport trunk allowed vlan 185,225
switchport mode trunk
interface Vlan185
ip address 10.8.185.7 255.255.255.0
ip access-group ro in
interface GigabitEthernet1/1
switchport trunk encapsulation dot1q
switchport trunk native vlan 225
switchport trunk allowed vlan 185,225
switchport mode trunk
interface GigabitEthernet1/2
switchport trunk encapsulation dot1q
switchport trunk native vlan 225
switchport trunk allowed vlan 185,225
switchport mode trunk
so, when I ping 10.8.185.7
I get:
GMT-3: ICMP: dst (10.8.185.7) administratively prohibited unreachable rcv from 10.8.185.4
%SEC-6-IPACCESSLOGDP: list ud1 denied icmp 10.8.185.7 (GigabitEthernet1/1) -> 10.18.232.58 (0/0), 3 packets
anybody?

Hello Paresh,
thanks for replying.
But, actually I dont think this is what happening.
Because 10.18.232.58 comes from an uplink - core router, which enters from a different interface.
Let me give you the configs:
uplinks:
interface GigabitEthernet3/1
no switchport
ip address 10.18.192.26 255.255.255.252
And the core are doing load-balancing to reach the UA.
So, icmp packets are arriving from these 2 interfaces, the uplink gi3/1 (router port) and from the link that connects the UA switch.
so, pinging from the BC you have 2 ways to get to the UA, from UD1 and UD1-B, when it reaches UD1-B it goes to the vlan (ie. goes down to the UA and up to UD1A).
Not sure if this is helping.
If you need any other info let me know.
this is killing me.

Controller interface vlan identifier

Similar Messages

Maybe you are looking for