Aironet 1252 management VLAN

I have here two or three 1252 s and I wonder if it is possible to configure the access management / VLAN.

Switch is configured like this:

encapsulation dot1q switchport
switchport mode trunk
switchport trunk vlan 99 native
switchport trunk allowed vlan 10

Access point should be as follows:
1. VLAN 10 - SSID CRM (tagged)
2. VLAN 99 - management VLAN (unidentified)

In vain I tried several things like:
1. configured sous-interface GigabitEthernet0.99 with native VLAN and IP address and BVI1 without IP address
2. don't GigabitEthernet0.99 subinterface configured with VLAN native and no IP address and BVI1 with the IP address

GigabitEthernet0.99 is in the bridge-Group 1.
GigabitEthernet0.10, DotRadio0.10 and DotRadio1.10 are in the bridge-group 255.

Still can not ping IP address of the access point management. Default GW is correct.

Hello

Please change your configuration VLANS allowed to it and try:

switchport trunk allowed vlan 10 99

Even if you define a VLAN a VLAN native you still add to the allowed list of VLAN.

Best regards

www.wifitrainers.com

Learn from the best to be the best!

Change the way you look at connectivity of wireless clients forever by registering to watch this free webinar and also a chance to win our starter kit worth $ 8000 wireless for free!

Tags: Cisco Wireless

Similar Questions

  • Connect 6224 VLAN routing and management VLAN

    Happy holidays all the world-

    I read several posts here and elsewhere on the inability of the 6224 to deliver its own management interface. OK, enough, I get it. But what I don't understand is a practical solution to what seems to be a huge problem if you want to use the network to connect to the device to manage (instead of the serial console port).

    Let's say I want to have three networks A, B, and C on the 6224 and configure it to route between any combination of them. Let's call them VLANS 1, 2, and 3. Three ethernet cables will connect to three ports on the 6224. for the network A, b and C. Let's just ignore shifts and redundant connections to do this.

    The management VLAN can not be assigned to one of these networks, right? He said in the documentation, and it turns out if you try to do it on the configuration of the switch. It doesn't let you do.

    So, how do you reach the 6224 for management? Create a fourth network, VLAN 4? This seems to be the general theme of the answers to questions like that, but how do you reach this seemingly isolated network? By definition, it cannot be routed. Any computer that you normally use on A, B or C, can not reach D.

    So what then? A dedicated computer for D who cannot reach the other thing than the switch management port? What about another completely separate router (I have a Cisco ASA with some ports to spare, or a hint of irony, an another 6224!) to provide a connection between D and a networks normally used? This is crazy.

    Of course, missing me something here. I can't believe that the answer is, 'If you enable routing, the management interface is essentially unusable"but that's what it looks like, from my possibly twisted point of view. I want to have my laptop computer and any other computer, sitting on a network that can be put to rout by the 6224, and for that same laptop also be able to reach this same 6224 management interface.

    Someone please help me understand this?

    Thank you

    Chris

    PS: I have an email address. It is almost unique on the entire planet. I use it to connect to this forum. But Dell, like so many others, insists on ignoring these facts and let me create an another unique identifier while playing a game of 20 questions. That's why my remarkably stupid random username.

    Thanks again, and I hope that someone gets at least a good laugh over this.

    Vlan management can be considered as a port OOB. If the intention is that it be separated from the rest of the traffic and on its own dedicated network. However, you are not limited to manage the switch through just the interface vlan management. Each VLAN with an IP address can be used by customers in this vlan to manage the switch.

    For example, if you assign a VLAN 2 address and ip 192.168.2.1. Customers in VLAN 2 with and the 192.168.2.x subnet ip address can access 192.168.2.1 to manage the switch, while being able to communicate with clients in other VLANs.

    I hope this helps some, let me know if you need help on your config, or to specify anything.

    Thank you

  • Change of SG 200-18 - management - VLAN / telnet/ssh-access?

    Hello

    We have a switch SG200-18 that should be used as a switch of working group in our environment (SW

    Version 1.1.1.8). In collaboration with CLI on big and mid range Cisco gear during the past two decades, I have a hard time to understand what follows on the SG200:

    (o) I want to change the management VLAN by default '1' to the management - VLAN used in our environment. Of course, I created this vlan in SG200-config, however when it comes to assign the management IP and VLAN management interface in the advancement of the corresponding film under "Interface IPv4-> management VLAN" selectable is the default "1". see screenshots (closed)

    So, how to define a management VLAN 1 different?

    (o) how to enable telnet/ssh-access the SG200-18 - I'd be much more comfortable with a CLI environment ;-)

    Thank you very much in advance for your help,.

    -ewald

    Hello Ewald,

    Sx200 series switch does not currently offer a CLI option. Have this feature if the Sx300 and 500 series.

    What about chaning the vlan management, you have two options.

    (1) changes the vlan by default under management VLAN > Default vlan settings. This will change all the ports and the management vlan.

    (2) adds a port as a port untagged in the new VLAN. Once this is done, make sure that something is connected to this port, like a computer. Now you should be able to change the vlan management. (This is done to prevent locking)

  • Cisco 2112 WALN controller unable to detect Aironet 1252

    I'm new on this.

    A new Aironet 1252 and trying to hang on until Controller 2112. There are already two existing WAP related to the controller, but the new, it is not displayed. I need instructions step by step how get this working because I do not know where to start

    I have attached the aironet config

    Please help

    Hello

    The AP is in mode Autononous... therefore, it will not work with the WLC until we convert ITTO LWAPP or CAPWAP... Please download the latest capwap / LWAPP image from below link for1252 AP (image = c1250-rcvk9w8 - tar.124 - 21A .JA2 .tar)

    http://www.Cisco.com/Cisco/software/release.html?mdfid=281235915&flowid=6779&softwareid=280775090&release=12.4%2821A%29JA2&rellifecycle=&relind=available&RelType=latest

    and then get the TFTPd32 on your laptop and install... Make sure that the PA and the interface ethernet laptop are on the same subnet and try ping AP bvi IP of your laptop inte... If we are able to then...

    Tap the image to the tftp server by going to the right directory... then issue the belkow command...

    / force-reload DOWNLOAD-sw AP #archive / overwrite tftp: / /image.tar

    ex

    Assuming 10.10.10.1 is your tftp server... change accordingly...

    / force-reload DOWNLOAD-sw AP #archive / overwrite tftp://10.10.10.1/c1250-rcvk9w8-tar.124-21a.JA2.tar

    This recharge and get to image LWAPP AP will join the WLC and then you need to configure on the WLC stand according to your needs...

    Let me know if that answers your question...

    Concerning
    Surendra
    ====
    Please do not forget to note positions that answered your question and mark as answer or was useful

  • Why can't I change the management VLAN?

    This will sound like a newb question (but I'm used to COS not MISTLETOE), but how to change the vlan management on a SLM2048 and still have access to the GUI switch? The steps I use:

    (1) create a vlan (say vlan 2) / save the changes

    (2) add a non-tagging port (say, g2) to change vlan / save

    (3) change the vlan management to the vlan 2 in gui/save changes

    (4) physically to move my pc on port connection of vlan 2 (g2)

    (5) delete my cache arp (arp - d)

    (6) the switch switch in. ping or log not rspond pings 8 ^)

    What in the world could be missing (outside a few screws)?

    Thanks much for any help!

    This is going to sound like a newb question (but I'm used to COS not the GUI), but how do you change the managment vlan on a SLM2048 and still have access to the switch GUI?? The steps I'm using:

    1) create a vlan (say vlan 2)/save changes

    2) add a non-tagging port (say, g2) to the vlan/save changes

    3) change the management vlan to vlan 2 in the gui/save changes

    4) physically move my pc connection to the vlan 2 port (g2)

    5) delete my arp cache (arp -d)

    6) ping the switch or log in. switch doesn't rspond to pings 8^(

    What in the world could I be missing (besides a few screws)??

    Thanks very much for any help!

    Hello

    Check out the link to change the management vlan in SLM2048 below

    http://www.Cisco.com/en/us/docs/switches/LAN/csbss/slm2024/release/notes/SLM2024_SLM2048_RN_V1-0-1.PDF

    Hope to help!

    Ganesh.H

    Don't forget to note the useful message

  • How to upgrade IOS for Aironet 1252 G

    I'm trying to update the IOS for Aironet 1252 G wirless access point, I look at all the instruction and they do not make sense! And there is just no instuctions on how to upgrade the IOS in the WEB BROWSER interface. I just did an install of Windows Server 2008R2 and real simple compared to only raise AP and running, but there still Microsoft and their staff try to keep things simple for people where CISCO makes more complex theings.

    Hello

    If you try to update the IOS on a Cisco AP upgrade recomeneded uses the cli via a telnet session or console.

    **************************************************************************** RECOMMENDED UPGRADE TROUGH CLI: The following are the proper steps to do an IOS upgrade in a CLI/Telnet session (This is the recommended upgrade): 1st: Use a TFTP server in the computer that you are going to use for the upgrades. If you don't have one, get the free TFTP server in the following link: http://tftpd32.jounin.net Note: Make sure that the computer and the APs are in the same subnet. For example and AP in default settings will have IP: 10.0.0.1, so you need to have the computer as IP 10.0.0.2, subnet mask: 255.255.255.0. 2nd: Download the IOS image from the Cisco.com Web site. Note: Do not "unzip" the image. 3rd: Open the TFTP server (make sure that the TAR file's name of the IOS image is shown as in the web site, because sometimes it gets renamed to "Download .tar" and if that happens you need to rename it).  Browse the TAR file and select it, then click ok. 4th: Telnet the unit, go to enable mode and enter the following command: ap#archive download-sw /overwrite /force-reload tftp://IPAddress of_the_tftp_server/name_of_the_IOS_image_you_downloaded In this link, you must specify the extension, as an example: ap#archive download-sw /overwrite /force-reload tftp://10.0.0.2/c1200-k9w7-tar.122-13.JA.tar Note: The IOS image name is case sensitive, and it should be complete.
    ******************************************************************************

    This is the same procedure for any AP in IOS mode, the difference would be the image used for each specifc model.

  • Example config for 2 management vlan and ip Routing.

    We have a stack 6224, we use two vlan on it

    VLAN network 10.1.1.X 24 10

    VLAN network 192.168.0.X 24 40

    Our workstations reside also in the 10.1.1.X network, so we need to administer the switch there.

    192.168.0.X traffic must be routed to 192.168.0.X (and vice versa)

    How can I set this up, when I set up a 10.1.1.1 address for the administration interface and vlan 10 I can't configure the routing for this vlan?.

    (Actually I don't want to just out-of-band of our lan fault management)

    Please advice,

    Message edited by OnnoB on 08/09/2008 06:39

  • Tagged management VLAN and the virtual machines on the same VLAN

    I'm faced with a problem related to our Brocade switches newly acquired and get the private VLAN to work on trunk connections to our ESX servers.  Every time I try something different, he creates a new problem.

    In our configuration, our management of VLAN is not tag and we have a VLAN for this management network that is placed on our switches VLAN no marked native.  We also have virtual machines hosted on those same ESX servers that are on the same VLAN and everything works fine.  However, when I change the ESX management to carry a label on this VLAN and change the switchports accordingly (IE no untagged VLAN native), management work, but hosted on the ESX Server machines that are on the same VLAN can get no network connectivity.

    Is it possible to have a management network labeled and also the host of virtual machines on the same VLAN or is it totally impossible?  I'm not very familiar with networking behind ESX, so I apologize if this is a dumb question with an obvious answer.

    Thank you

    Mark J.

    Is it possible to have a management network labeled and also the host of virtual machines on the same VLAN or is it totally impossible?

    Yes, it is possible... why it doesn't work for you I don't know, but try the following:

    1. set up the Group of ports of VMS to use VLAN;

    2 configure the interface of management VMkernel port group use VLAN;

    3 configure the physical switch port to allow to this VLAN and put the default VLAN natively for these interfaces.

  • Management VLan in Dell Powerconnect 6224

    Hello

    I have power supply dell switch connect 6224. I created 3 vlan, Vlan 10,20 and 30. different ip network given to all the vlan...

    The problem, he can access via telnet or Http from the IP two vlan 3...  I want that she needs to access from only a single IP address not all the...

    should what additional configuration I do on switch?

    I will seek to implement the ACL to deny access to the address IP of the VLAN.

    This is a good, white page that covers the ACLs on the 6224.

    http://www.Dell.com/downloads/global/products/PWCNT/en/pwcnt_ip_acls.PDF

    To help control access to the switch, one of the first things I suggest you do allows SSH and HTTPS, then disable Telnet and HTTP.

  • Aironet 1252 with catalyst 2960-8TC-L & 1841 router compatibility

    Hello

    First of all they are togther a good combination?

    I'll buy new ap 1252 and switch catalyst 2960-8TC-L my question can I connect the access point to 1 x 10/100/1000Base-T/SFP (mini-GBIC) (uplink) port?

    because to work on ap with capacity 300 Mbps, it needs port 1000, I will use to power ap powerinjector.

    It will be 15 sereve pc as a working group and 60 customers on wlan.

    Concerning

    Saher

    Depending on the type of traffic and bandwidth customer requirements demand, you might need a couple more of ap which means you may have to settle for a switch of 24 ports. Cisco recommends 15-25 users by so, but still, you can have more if it's just e-mail and web browsing.

  • Management of VLANS on switches PowerConnect 28XX

    I had already tried the PowerConnect 27XX switches (mainly the 2708), and while it worked very well, he had a very, very frustrating feature: the IP address of management was always assigned to VLAN 1 - there is no way to change this.  I wonder if someone who has the (2708 or 2716) 28XX series could tell me if they have added a way to change the management VLAN, or if the management VLAN is always pasted to the VLAN1?  It is a decisive feature - I can't lose a port on VLAN1 on the switch just to be able to manage, as our current environment uses a VLAN for management.

    Thank you

    Nick

    management of VLANs is always vlan 1 on 28xx switches.

    An option is outwardly loop back one vlan 1 coelio to an access port vlan XX.   This will allow you to manage the switch on any vlan.  Of course, it burns 2 ports, not just 1.  But these switches are inexpensive, so you can have a hard time to find a solution less expensive just to avoid to manage on the vlan 1 or using the hack of the outer loop.

    Note: 28xx executes a single PLEASE, so you will need to disable the STP Protocol on the loop back ports if you go with this hack.

  • PowerConnect 2824: Can't access web management using VLAN TAG 1?

    Let's say I have port 20, which is a member with LABEL of VLAN 1, 10 and 20.

    If I try to access web management to help interface VLAN 1 TAG, it is not accessible.  However, if I remove the tag VLAN (and the default PVID value of 1), then it works fine.

    Is this a known limit?

    In addition, change the management VLAN on my 2824?  (what I read, it is not possible)

    You're right about the two statements.  The Web GUI is accessible only through the untagged VLAN 1 and it is not possible to change the management VLAN on the 2800 Series switches.  On the other upper level switches, you can use the ip address command vlan xx to move the management VLAN in the VLAN specified in the statement.

    I hope this helps.

  • Manage one 1240 AP on another VLAN?

    I set up an AP 1240 with 2 VLANS, works very well. But our network uses the management VLAN 200, not VLAN 1. I have configured int BVI200 and gave it an IP address, but cannot get an IP connectivity. If I use BVI1, everything works, but on the VLAN evil. How can I manage my AP on a different VIRTUAL LAN?

    Use BVI1 and configure the switch port that is a trunk for vlan 200 native. Who give a shot.

  • VLAN Management with the 1000V and UCS

    If I want to use 10 VLAN management, to configure the following:

    1000V - VM vEthernet port profile coelio with VLAN 10, Ethernet uplink profile includes 10 VLANS

    UCS - vNIC in the Service profile, VLAN 10 and include the UCS uplink trunk VLAN 10

    Switch upstream: include 10 VLANS in trunk port.

    Ok?

    Now, this management VLAN, I then jeutiliser can for everything? I mean to 1000V management VLAN, vSPhere management, management FI and switch? For example management of 1000V or different from others?

    Hi Atle,

    Yes, is that what you mentioned, it's good in terms of activities you need to perform. However, I wish to add a few:

    (1) define him vlan on the UCS - except if you do this, that you won't be able to add to the vnic. More once you have set the vlan automatiaclly will get added to the list of trunk on uplink ports (unless you l2-disjoint set up)

    You can have the same vlan for all management, unless you have some traffic that you would not want some devices to see / meet.

    . / Afonso

  • WLC management port is another trunk that vlan native

    Hello

    I installed my first WLC 5508 with this topology:

    WLC connected trought distribution SFP 1 GB port to the port of switch configured as a Trunk port cut 3 Wireless VLAN:

    -Management WLC, wireless and wireless voice data Vlan (Vlan native is WLAN Management).

    -J' created 2 dynamic interface on WLC on my VLAN Wireless:

    10.7.1.0/24: default management Virtual Interface installing WLC +.

    10.7.6.0/24: Virtual Interface of voice and

    10.7.2.0/24: Wireless Data Interface virtual trought GUI.

    DHCP configured on each dynamic interface is the interface vlan L3 subent for SWITCH main technical IP DHCP Pool equal VLAN.

    WLC management interface IP address is: 10.7.1.10/24

    I create 2 WLAN SSID name with given ID 1, and ID2 voice.

    I create and AP group named APGRP1 that contains the AP recorded about WLC and using the two WLAN SSID.

    The two AP are connected to the switch acess port configured as native management WLC VLAN access port.

    I have to create 3 IP DHCP pool on main switch with the related L3 Interfaces for Inter VLAN routing.

    Problem: when I try to connect from mobile data SSID I get IP address of management WLC VLAN a VLAN data no.

    the same case of Wireless IP Phone configured with voice SSID.

    What I can likely that allows two devices to get the address IP of the correct VLAN?

    Thnks

    Hi Adil,

    T1 > coelio AP on the switch must be configured on a mode of access to the port or trunk mode?

    YEARS - the LWAPP / CAPWAP APs connected to the switchport should be an access port not trunk.

    Q2 > if the first case, the configuration of the port, on the same VLAN as WLC management VLAN support Vlans other WLANS (voice and data)?

    YEARS - Yes it supports, since traffic that involes the WLAN will be inside the tunnel of logic LWAPP/CAPWAP.

    Q3 > I will check the interface between WLAN and dynamic Interfaces map and I'll tell you.

    YEARS - I will wait for your answer!

    Let me know if that answers your question...

    Concerning
    Surendra
    ====
    Please do not forget to note positions that answered your question and mark as answer or was useful

Maybe you are looking for