Aironet 1252 DHCP with vlans

I have an aironet 1252 access point and I have it set up with 3 ssid's which in turn are 3 separate vlans. My question is, can the 1250 supply dhcp to each ssid or only to the native vlan. This access point is going to be connected to a 4507 routing switch. Currently I am unable to obtain any dhcp addresses. The port that the access point is connected to is a trunk port and is configure to only allow the 3 vlans that are on the access point. Any help would be greatly appreciated

Hi, rgonzalez_tec
Can you verify that the other two VLANs' DCHP mode is set to DCHP Server and that for each IP address, port based authentication is enabled?
I have found three documents on the knowledge base that may help you in the right direction.
Enabling Multiple Wireless Networks on RV320 VPN Router, WAP321 Wireless-N Access Point, and Sx300 Series Switches
DHCPv4 Configuration and Monitoring on RV32x VPN Router Series
DHCPv6 Configuration and Monitoring on RV32x VPN Router Series
More documents can be found using the GuideMe tool here.
-Andy

Similar Messages

4 Aironet 1252's with 2.4 & 5 GHz Radios

I just deployed 4 1252 Aironets. I had some reports of connections coming up and dropping. I think the issue is how the radios are tuned in them. I am using multiple SSID's and VLAN's. One of the SSID's is configured for both the 2.4 & 5 GHz. My questions is how these radios should be configured. For the 2.4 GHz I manually configured them on channels 5,6,7 & 8. For the 5 GHz I set them for 36, 40, 44 & 48. I looked for a test practice on this but haven’t found one. Is this right?

For the 2.4GHz the answer is "No" assuming the APs are in the same area/building. Have you tried reading anything on WiFi yet? Try a quick google search or a search on Cisco's page, I tried "wifi channel basics" in google and it seemed to work well.
Use channels 1, 6, and 11 and reuse channels between the two APs with the largest separation (most walls, largest distance etc) between them. If all APs see eachother then reuse channels between the two APs that have the least traffic. You will see a big improvement.
The 5GHz should be fine as you have them.
http://www.wireless-nets.com/resources/tutorials/assign_ap_channels.html
I had read of some devices having a problem when the SSID is the same between 2.4GHz and 5GHz, so you may want to try a different SSID between frequencies. (But my experience with this is limited, perhaps others have more to say).

Dhcp with Vlan AP 1240 AG

HI, I'm with problem to get IP by dhcp in my network wireless on AP 1240ag.
I wish that my AP has two VLANs and each VLAN issue IP by DHCP.My DHCP server is a Windows Server 2008 for VLAN 1 and a Linux for VLAN 12.
The AP it's connected by Trunk to a Switch that has the two DHCP Server each one on port Vlan.
but my clients it isn't able get IP address by any each one DHCP server. it's work only with static IP. there is more anything to do in my configuration?

1) Are you saying that clients can get a full network connectivity with a static ip on both vlan on your AP ? If that's the case then it looks like the AP is configured fine.
2) What happens if you plug a wired laptop to the switch and configure the port to be in one vlan then the other. Would the PC get an ip address ? If not, then it's a swicthing issue.

Aironet 1252 firmware update for official N?

Hi, we currently own several Aironet 1252 WAP with the N draft. Is there a firmware update to the official 802.11N? If so, where can I locate the firmware?
Our WAP is the "AIR-AP1252G-A-K9" model.

The 1250, by default, was designed specifically for 802.11N in mind. What you need to do is to get the configurations correct to operate.
The latest firmwares that updates the APs are the 12.4(10b)JDA3 and 12.4(21a)JA1. The former upgrades the firmwares for both radio modules to version 2.00.22. The latter upgrades the radios further to 2.10.19. Now this is not just number. The upgrades (either one) allows the AP to operate both radios with only 15.4 watts of power. There's a "cost" associated to it and it's lower MCS rates.
Hope this helps.

Aironet 1252 doesn't broadcast SSID and VLANs

Best regards.
I have an autonomus AP Aironet 1252 (software version: 12.4(18a)JA1)
I configured 3 SSID and VLANs, but the AP doesn't broadcast SSID, the vlans are working fine because I tested configuring manually the hide SSID on laptops.
Also the AP broadcasts the SSID whe only one SSID is configured!!!
How I can do the AP to broadcast all SSIDs?
Thanks in advance.

From the command line of your AP.
Change each SSID as follows. You want to turn off "guest-mode" and enable "mbssid" at each SSID. Guest-mode will only broadcast one SSID, you must use mbssid to allow all SSIDs to broadcast.
#config t
#dot11 ssid
#no guest-mode
#mbssid
Now from each radio
#int d0
#mbssid
#int d1
#mbssid

SG-300 28P switches problem with VLAN Data and Voice, working all the time as Voice VLAN

Hi Everyone,
Thank you very much for your help in advance. I’m pulling my hair to fix the problem.
I just got the new SG-300 28P switches. My Bios ordered for me. I did not know how it runs until now... not an IOS based. I really do not know how to configure it.
I have 2 VLAN are Data and Voice.
-          Data VLAN ID is 2 IP 192.168.2.X/255.255.255.0
-          Voice VLAN ID is 200 IP 192.168.22.X/255.255.255.0
-          I created two vlans, in switch, Data and Voice.
-          On the port number 28, it is trunk by default, so I add Data vlan ID 2 tagged.
-          On the port number 26, it is trunk by default, so I add Voice vlan ID 200 tagged.
-          On the port number 27, I add Data vlan ID 2 tagged for Data vlan out.
-          Port settings No.1
I set it up as Trunk with Data vlan 2 untagged, and 200 Tagged (voice vlan). I plugged in a phone with a pc attached. But the PC will get to the vlan 200 to get the DHCP address, but no from vlan 2. The Phone works with correct vlan ip.
-          Port settings No.2
Trunk with vlan 1UP, 2T, and 200T. The phone is even worse. Would never pick up any IP from DHCP.
-          Port settings No.3
Access with 200U...of course the phone will work... and the PC could not get to its own vlan. Instead, the PC got an ip from the voice vlan. Not from VLAN 2.
I have Linksys phone I’m not sure if this help.
For more information I setup in switch,
            - enable voice vlan
- set the port on auto voice vlan
- enable LLDP-MED globally
- create a network policy to assign VLAN 200
- assign this network policy to the port the phone is connected to.
I hope this information help to help me to setup Data and Voice vlans, to plug the phone to work with vlan Voice 200 (IP rang 192.168.22.X), from phone to Pc and pc work as Data vlan 2 (IP rang 192.168.2.X).

I just got done setting up voice VLANs on an SF 300-24P and verified working. This was working with Cisco 7900 series phones connected to a Cisco UC setup.
Here's my sample config.
Note that I edited this by hand before posting, so doing a flat out tftp restore probably won't work. However, this should give you a clue. Also, don't take this as 100% accurate or correct. I've only been working with these things for about a week, though I've worked with the older Linksys SRW switches for a couple of years. I'm a CCNP/CCDP.
VLAN 199 is my management VLAN and is the native VLAN on 802.1q trunks.
VLAN 149 is the data/computer VLAN here.
VLAN 111 is the voice/phone VLAN here.
VLAN 107 does nothing.
interface range ethernet e(1-24)
port storm-control broadcast enable
exit
interface ethernet e1
port storm-control include-multicast
exit
interface ethernet e2
port storm-control include-multicast
exit
interface ethernet e3
port storm-control include-multicast
exit
interface ethernet e4
port storm-control include-multicast
exit
interface ethernet e5
port storm-control include-multicast
exit
interface ethernet e6
port storm-control include-multicast
exit
interface ethernet e7
port storm-control include-multicast
exit
interface ethernet e8
port storm-control include-multicast
exit
interface ethernet e9
port storm-control include-multicast
exit
interface ethernet e10
port storm-control include-multicast
exit
interface ethernet e11
port storm-control include-multicast
exit
interface ethernet e12
port storm-control include-multicast
exit
interface ethernet e13
port storm-control include-multicast
exit
interface ethernet e14
port storm-control include-multicast
exit
interface ethernet e15
port storm-control include-multicast
exit
interface ethernet e16
port storm-control include-multicast
exit
interface ethernet e17
port storm-control include-multicast
exit
interface ethernet e18
port storm-control include-multicast
exit
interface ethernet e19
port storm-control include-multicast
exit
interface ethernet e20
port storm-control include-multicast
exit
interface ethernet e21
port storm-control include-multicast
exit
interface ethernet e22
port storm-control include-multicast
exit
interface ethernet e23
port storm-control include-multicast
exit
interface ethernet e24
port storm-control include-multicast
exit
interface range ethernet g(1-4)
description "Uplink trunk"
exit
interface range ethernet g(1-4)
switchport default-vlan tagged
exit
interface range ethernet e(21-24)
switchport mode access
exit
vlan database
vlan 107,111,149,199
exit
interface range ethernet g(1-4)
switchport trunk allowed vlan add 107
exit
interface range ethernet e(21-24)
switchport access vlan 111
exit
interface range ethernet g(1-4)
switchport trunk allowed vlan add 111
exit
interface range ethernet e(1-20)
switchport trunk native vlan 149
exit
interface range ethernet g(1-4)
switchport trunk allowed vlan add 149
exit
interface range ethernet g(1-4)
switchport trunk native vlan 199
exit
voice vlan aging-timeout 5
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
voice vlan oui-table add 108ccf MyCiscoIPPhones1
voice vlan oui-table add 40f4ec MyCiscoIPPhones2
voice vlan oui-table add 8cb64f MyCiscoIPPhones3
voice vlan id 111
voice vlan cos 6 remark
interface ethernet e1
voice vlan enable
exit
interface ethernet e1
voice vlan cos mode all
exit
interface ethernet e2
voice vlan enable
exit
interface ethernet e2
voice vlan cos mode all
exit
interface ethernet e3
voice vlan enable
exit
interface ethernet e3
voice vlan cos mode all
exit
interface ethernet e4
voice vlan enable
exit
interface ethernet e4
voice vlan cos mode all
exit
interface ethernet e5
voice vlan enable
exit
interface ethernet e5
voice vlan cos mode all
exit
interface ethernet e6
voice vlan enable
exit
interface ethernet e6
voice vlan cos mode all
exit
interface ethernet e7
voice vlan enable
exit
interface ethernet e7
voice vlan cos mode all
exit
interface ethernet e8
voice vlan enable
exit
interface ethernet e8
voice vlan cos mode all
exit
interface ethernet e9
voice vlan enable
exit
interface ethernet e9
voice vlan cos mode all
exit
interface ethernet e10
voice vlan enable
exit
interface ethernet e10
voice vlan cos mode all
exit
interface ethernet e11
voice vlan enable
exit
interface ethernet e11
voice vlan cos mode all
exit
interface ethernet e12
voice vlan enable
exit
interface ethernet e12
voice vlan cos mode all
exit
interface ethernet e13
voice vlan enable
exit
interface ethernet e13
voice vlan cos mode all
exit
interface ethernet e14
voice vlan enable
exit
interface ethernet e14
voice vlan cos mode all
exit
interface ethernet e15
voice vlan enable
exit
interface ethernet e15
voice vlan cos mode all
exit
interface ethernet e16
voice vlan enable
exit
interface ethernet e16
voice vlan cos mode all
exit
interface ethernet e17
voice vlan enable
exit
interface ethernet e17
voice vlan cos mode all
exit
interface ethernet e18
voice vlan enable
exit
interface ethernet e18
voice vlan cos mode all
exit
interface ethernet e19
voice vlan enable
exit
interface ethernet e19
voice vlan cos mode all
exit
interface ethernet e20
voice vlan enable
exit
interface ethernet e20
voice vlan cos mode all
exit
interface ethernet e1
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e2
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e3
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e4
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e5
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e6
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e7
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e8
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e9
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e10
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e11
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e12
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e13
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e14
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e15
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e16
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e17
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e18
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e19
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e20
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e21
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e22
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e23
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e24
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet g1
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet g2
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet g3
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet g4
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
exit
interface ethernet e1
lldp med notifications topology-change enable
exit
interface ethernet e2
lldp med notifications topology-change enable
exit
interface ethernet e3
lldp med notifications topology-change enable
exit
interface ethernet e4
lldp med notifications topology-change enable
exit
interface ethernet e5
lldp med notifications topology-change enable
exit
interface ethernet e6
lldp med notifications topology-change enable
exit
interface ethernet e7
lldp med notifications topology-change enable
exit
interface ethernet e8
lldp med notifications topology-change enable
exit
interface ethernet e9
lldp med notifications topology-change enable
exit
interface ethernet e10
lldp med notifications topology-change enable
exit
interface ethernet e11
lldp med notifications topology-change enable
exit
interface ethernet e12
lldp med notifications topology-change enable
exit
interface ethernet e13
lldp med notifications topology-change enable
exit
interface ethernet e14
lldp med notifications topology-change enable
exit
interface ethernet e15
lldp med notifications topology-change enable
exit
interface ethernet e16
lldp med notifications topology-change enable
exit
interface ethernet e17
lldp med notifications topology-change enable
exit
interface ethernet e18
lldp med notifications topology-change enable
exit
interface ethernet e19
lldp med notifications topology-change enable
exit
interface ethernet e20
lldp med notifications topology-change enable
exit
interface ethernet e21
lldp med notifications topology-change enable
exit
interface ethernet e22
lldp med notifications topology-change enable
exit
interface ethernet e1
lldp med enable network-policy poe-pse
exit
interface ethernet e2
lldp med enable network-policy poe-pse
exit
interface ethernet e3
lldp med enable network-policy poe-pse
exit
interface ethernet e4
lldp med enable network-policy poe-pse
exit
interface ethernet e5
lldp med enable network-policy poe-pse
exit
interface ethernet e6
lldp med enable network-policy poe-pse
exit
interface ethernet e7
lldp med enable network-policy poe-pse
exit
interface ethernet e8
lldp med enable network-policy poe-pse
exit
interface ethernet e9
lldp med enable network-policy poe-pse
exit
interface ethernet e10
lldp med enable network-policy poe-pse
exit
interface ethernet e11
lldp med enable network-policy poe-pse
exit
interface ethernet e12
lldp med enable network-policy poe-pse
exit
interface ethernet e13
lldp med enable network-policy poe-pse
exit
interface ethernet e14
lldp med enable network-policy poe-pse
exit
interface ethernet e15
lldp med enable network-policy poe-pse
exit
interface ethernet e16
lldp med enable network-policy poe-pse
exit
interface ethernet e17
lldp med enable network-policy poe-pse
exit
interface ethernet e18
lldp med enable network-policy poe-pse
exit
interface ethernet e19
lldp med enable network-policy poe-pse
exit
interface ethernet e20
lldp med enable network-policy poe-pse
exit
interface ethernet e21
lldp med enable network-policy poe-pse
exit
interface ethernet e22
lldp med enable network-policy poe-pse
exit
lldp med network-policy 1 voice vlan 111 vlan-type tagged
interface range ethernet e(1-22)
lldp med network-policy add 1
exit
interface vlan 199
ip address 199.16.30.77 255.255.255.0
exit
ip default-gateway 199.16.30.3
interface vlan 1
no ip address dhcp
exit
no bonjour enable
bonjour service enable csco-sb
bonjour service enable http
bonjour service enable https
bonjour service enable ssh
bonjour service enable telnet
hostname psw1
line console
exec-timeout 30
exit
line ssh
exec-timeout 30
exit
line telnet
exec-timeout 30
exit
management access-list Management1
permit ip-source 10.22.5.5 mask 255.255.255.0
exit
logging 199.16.31.33 severity debugging description mysysloghost
aaa authentication enable Console local
aaa authentication enable SSH tacacs local
aaa authentication enable Telnet local
ip http authentication tacacs local
ip https authentication tacacs local
aaa authentication login Console local
aaa authentication login SSH tacacs local
aaa authentication login Telnet local
line telnet
login authentication Telnet
enable authentication Telnet
password admin
exit
line ssh
login authentication SSH
enable authentication SSH
password admin
exit
line console
login authentication Console
enable authentication Console
password admin
exit
username admin password admin level 15
power inline usage-threshold 90
power inline traps enable
ip ssh server
snmp-server location in-the-closet
snmp-server contact [email protected]
ip http exec-timeout 30
ip https server
ip https exec-timeout 30
tacacs-server host 1.2.3.4 key spaceballz timeout 3 priority 10
clock timezone -7
clock source sntp
sntp unicast client enable
sntp unicast client poll
sntp server 199.16.30.1
sntp server 199.16.30.2
ip domain-name mydomain.com
ip name-server 199.16.5.12 199.16.5.13
ip telnet server

Aironet 1252 Antenna quantity

Hi There,
I already have an Aironet 1252 and I am going to increase the coverage.
I would like to buy "AIR-ANT24120" but I dont know if I have to buy 3 of them or only would be enough?

Let me try to answer your questions:)
Did you decide to use lmr600 for longer cables and lmr400 for shorter? I could just use lmr600 for all, I think. Of course, as long as the holes in the wall allow for six lmr600's to fit in.
The cost between the two is huge, so when I was 75' or less, I would use the lmr400, anything else would be the lmr600.
Not familiar with what it takes to crimp on RP-TNC vs. N-type connector. Is N-type easier to crimp on? Or is there another reason?
If you can have the cabler's only have to deal with one type of crimp.... the easier the install and that is why we did that. Sparco arrestors were 'N" type and then we used a small jumper from the top of the NEMA enclosure to the AP which of course was rp-tnc.
I just noticed that omni antenna has SMA connector, but it also says "connector options available". I'll talk to them, hopefully they have an N-connector option. Otherwise, not sure about crimping SMA connector.
They offer other connector types.
Duly noted on the tilt and arrestors. I want to protect the AP. I don't think I'll be using enclosures inside, the AP might just be mounted on the wall. In this case. If my LMR has N-type on both ends. I would have to attach RP-TNC arrestor directly to the AP (I'm using 3500e), then attach a RP-TNC to N-type adapter, and then connect the N-type LMR. Or I might just end up using enclosures as in your example with N-type arrestor.
They have small jumpers so you can go from 'N' type to RP-TNC. We used a NEMA enclosure just so it is more clean. the arrestors actually just screwed into the top of the NEMA enclosure, 3 toward the fron and 3 toward the back and the console and ethernet connection on the bottom.

SG300-20 - Configure DHCP on VLAN interface

I have been reading the various related discussions on the SG300 and SG500 switches regarding setting up VLAN's and DHCP on those VLAN's. For whatever reason I have been unable to even get this simple task to work.
First thing I did was to update my firmware and boot version as follows:
SW version    1.3.7.18 ( date 12-Jan-2014 time 18:02:59 )
Boot version    1.3.5.06 ( date 21-Jul-2013 time 15:12:10 )
HW version    V02
When I reloaded the SG300 after the SW/Boot updates the startup config was wiped out and I had to setup my switch from scratch. The intent is to have two VLAN's:
VLAN 1: all devices, servers, etc.
VLAN 2: basic subnet that hands out DHCP addresses
The SG300-20 is connected to an Asus RT-AC66U router on the 192.168.1.x subnet and provides internal network access and WiFi access (router IP address is 192.168.1.1 and is default gateway). All that works with no issues. So my task is simply to create VLAN 2 on 192.168.2.x subnet and use DHCP to allocate addresses. I have spent many hours on this and I still can't get it to work. When I connect a laptop to the port (GI8) assigned to VLAN 2, I end up getting some wonky 169.254.x.x address. I certainly thought something this "easy" wouldn't be that hard to setup, but apparently I was wrong.
The SG300 is running in L3 mode as shown in my running-config below.
Does anyone happen to see something that might be preventing my laptop client from recieving IP addresses from the VLAN 2 DHCP interface that are not in the 192.168.2.x subnet?
Any ideas / suggestions would be greatly appreciated!
Here's my running-config:
config-file-header
MYSTICSW1
v1.3.7.18 / R750_NIK_1_35_647_358
CLI v1.0
set system mode router
file SSD indicator encrypted
ssd-control-start
ssd config
ssd file passphrase control unrestricted
no ssd file integrity control
ssd-control-end cb0a3fdb1f3a1af4e4430033719968c0
vlan database
vlan 2
exit
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
bonjour interface range vlan 1
hostname MYSTICSW1
logging host 192.168.1.15
logging origin-id hostname
username cisco password encrypted b4a0fcf20b2cd9d80a55b06ab8f83277f9733904 privilege 15
snmp-server location Office
clock timezone " " -5
clock summer-time web recurring usa
clock source sntp
sntp unicast client enable
sntp unicast client poll
sntp server 192.168.1.10 poll
interface vlan 1
ip address 192.168.1.254 255.255.255.0
no ip address dhcp
interface vlan 2
name MysticWAN
ip address 192.168.2.254 255.255.255.0
interface gigabitethernet8
switchport mode access
switchport access vlan 2
exit
ip default-gateway 192.168.1.1
Thanks in advance!
Clint Lambert

Tom,
Thanks ... I followed the steps you outlined and it worked! The only difference being that I have an Asus RT-AC66U router and the there is no "enable multiple subnet" option. So, I just followed your instructions on creating the static routes in the RT-AC66U and everything worked. The DHCP addresses were correct and I had internet connectivity when I plugged a laptop into the gi8 port.
I did make one tweak to the Network Pools screen as follows:
My DHCP configuration for gi8 on VLAN 2 now looks like:
ip dhcp server
ip dhcp pool network InternalWAN
address low 192.168.2.1 high 192.168.2.99 255.255.255.0
lease infinite
domain-name MYSTIC
default-router 192.168.2.254
dns-server 8.8.8.8
Previously I had followed your advice in the article "Need help configuring SG300-10 switch" and had setup everything using CLI. However, I didn't think about needing the static routes. So, I think it was probably setup correctly beforehand but had no chance to work because the routes were not setup.
Thanks very much for your help!
Clint

Which Aironet 1252 radio module(s)

I was going to use an Aironet 1252 access point to set up a wireless network and was wondering which radio module (or modules) to get. I have no need for backwards compatibility, so it seems that for best performance I should go with a pure 802.11n network. In order to achieve that goal, is one radio module sufficient? And which band would be best? Or is there any advantage (or disadvantage to getting both the 2.4 GHz radio module (AIR-RM1252G-A-K9) and the 5 GHz one (AIR-RM1252A-A-K9)?
Any and all suggestions or thoughts are greatly appreciated. Oh, and if you need any other information about my setup please feel free to ask.
Thanks,
Paul

fella5 is right. You've just mentioned the need for backward compatibility therefore both A/B/G modules is OK.
Are you going to be using a Wireles LAN Controller (WLC)?
The reason why I'm asking is because the 1252 AP, in order to get both RM to work, you need at least 19.0 watts of power. This can only be achieved using either a enhanced PoE switch (such as the 3560-E/3750-E) or a power injector.
The latest code of the WLC (firmware 5.2) will upgrade the AVR of both the radio modules of the 1250 to be able to operate at 15.4 watts of power. Here's the catch though: The new WLC code will allow the 1252 to operate both radios BUT the power output (or signal strength) is curtailed.
However, do you look the 1140 series AP. This model will operate at 15.4 watts of power, full signal strength but the range is not as far as the 1250.
The 1140 (like it's other brother, 1130) was designed for office use: lots of walls, partitions and corners. The 1250 is designed for industrial use: wide-open space, environmental protection (thus the armoured-tank look-feel-weight).
Hope this helps.

Cisco 2112 WALN Controller unable to detect Aironet 1252

I'm new to this.
Got new Aironet 1252 and trying to hook up to 2112 Controller. There are already two existing WAPs linked to the controller but the new one is not showing up. I need step-by-step instructions how to get it working as I'm not sure where to start
I attached the config of the aironet
Please assist

Hi,
The AP is in Autononous mode.. so it will not work with the WLC till we convert itto LWAPP or CAPWAP... Please download the latest capwap / LWAPP image from the 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 it.. make sure the AP and the laptop ethernet interface are in the same subnet and try pinging the AP bvi inte IP from your LAptop.. if we are able to then..
Point the image on the tftp server by going to the right directory.. then issue the belkow command ..
ap#archive download-sw /force-reload /overwrite tftp:///image.tar
ex
Assuming 10.10.10.1 is ur tftp server.. change accordingly..
ap#archive download-sw /force-reload /overwrite tftp://10.10.10.1/c1250-rcvk9w8-tar.124-21a.JA2.tar
This will reload and come up with LWAPP image and the AP will join the WLC and thne you need to configure on the WLC to get this up based on your requirements...
lemme know if this answered your question..
Regards
Surendra
====
Please dont forget to rate the posts which answered your question and mark it as answered or was helpfull

Need basic Help - SG300 with vlan and routing

Hi,
i need some basic help with configuring vlan/routing.
Situation:
DSL Router - Cisco 300 - XenServer
192.168.1.253 - 192.168.1.19 - 192.168.1.10 (mgmt ip)
goal is, to reach from inside xenserver vms the internet.
vms = 192.168.2.x
gateway ip = 192.168.2.1
what i did:
- configured vlan 102, tagged, with the xenserver port
- configured on xenserver a network with vlan id 102, attached to the vm
- this network is conntected to an external bond
- configured ipva4 interface: vlan102 - Static - IP 192.168.2.1 (this is the gateway ip of the vms)
- automatic configured IPv4 Route: 192.168.2.0/24 next hop 0.0.0.0, Directly connected
So at the moment i cant ping from inside a vm to the DSL Router (192.168.2.2 to 192.168.1.253)
any ideas what i misconfigured or whats wrong?
cheers,
-Marco

Hi Tom,
ok, that make sense. I can ping the router now inside vms from 192.168.2.x network.
But i cant ping external adresses, error: Destination net unreachable.
My other problem i have, i cant reach any server from outside over router portforwarding.
How do i have to configure the upload port to the dsl router? Is it a access port or a trunk
port with all vlans (tagged or untagged?) At the moment ive a tagged Trunkport with all vlans.
IPv4 Interface Table
Interface
IP Address Type
IP Address
Mask
Status
VLAN 1
Static
192.168.1.19
255.255.255.0
Valid
Should the VLAN1 ip adress not the router ip adress ? Do i need an additional vlan for
the router ? At the end i like to change the switch ip from dhcp to static (change automaticly
when switching to layer 3 mode), but ive to look for the ios commands first.
What else do i missing ?
Thanks a lot,
Marcus

Two srw switches with vlans and pfsense gatway

Hi,
I've got a bit of a problem that a can't seem to get a handle of things.
I've got two srw 48 port switches that I would like to link together and then on to the pfsense box.
First I'd like to connect the two switches to see if everything works and then on connect the pfsense box.
Now I would be very great full if someone with a bit more experience with VLANs would be so kind to walk me trough the procedure of creating VLANs, configuring them to ports on the switch and connecting the whole thing to another switch.
This is what I've done so fare.
1. I created 3 VLANs on both switches (VLAN2-office,VLAN3-WiFi, VLAN5-VoIP). I've created these VLANs with the same tags on all the devices.
2. I configured the ports that connect the switches as trunk. (I can't seem to be able to configure anything else on this port. Is there something else I should configure on these ports?)
Now as fare as I understand the documentation the VLANs on each switch should now see each other.
I'm still not sure on how to configure a physical port to one VLAN. After creating the VLANs on both switches and connecting them trough the trunk port I set ports 10-20 to VLAN2 by going to VLAN Management -> Ports to VLAN I selected VLAN2 and marked ports general and untagged and saved the settings. I repeated the procedure on the other switch. Now if I stuck my network cable into one of this ports I didn't get an IP anymore form the DHCP witch means that they were on a different VLAN than the other ports so I setup another router to act as a test DHCP with a different IP range as the main DHCPto see if it works. Now when I connectedthe test router to one of the ports in VLAN2 and my PC to the same VLAN2 port I got the test IP no problem. But when I connected the PC to the other switch VLAN2 port nothing happened until I connected the test DHCP to one of the VLAN2 ports. So clearly the switch VLANs are not communicating.
Now I don't know did I forget something, made a mistake with some setting or I just don't know what I'm doing because I think I need to get the VLANs between switches working before tackling the pfsense connection.
I would be really great full if someone explains to me how to set these VLANs up so that they would work between switches.
Thank you for your help.

Hi,
I was successful and I did exactly that. I put all VLANs on trunk ports and the switch to switch to pfSense started to work.
The only thing that gave me some problems was the end port(port connecting to the device pc, phone, printer) configuration. I was under the impression that the port was supposed to be in general mode and tagged. But I figured out that the port is supposed to be in access mode and untagged and only a member of one VLAN(the one I wanted it to connect to).
Anyway all is working now and I've figured out all the kinks.
So thanks guys for the help.
Nice day to all.
Bye

Dhcp sg300 vlan

Okay. I have two scopes for two vlans configured on the sg300. When I put my laptop in vlan 1 I get an ip from 192.168.0.0/24. I then release the ip, I put the port my laptop is in into vlan 20 and try to renew to get an ip from 172.20.20.0/24 subnet associated with vlan 20 but I get an ip from 192.168.0.0/24 which is associated with vlan 1. The only way to get this to work is I have to go into the sg300 and delete the dhcp binding and then renew and I then get an IP address from 172.20.20.0. I would have thought that if I put the laptop in vlan 20 and released and renewed the sg300 would give me an IP address from 172.20.20.0 not 192.168.0.0 which is associated with vlan 1. What am I missing? Why is the sg300 responding with an ip from different vlan?
Sent from Cisco Technical Support iPad App

I've also experienced this and there was a similar post unanswered this month I believe. It may not be considered a bug or a problem since hosts aren't expected to change vlans like they do when we use are PCs for testing. Personally I would think that each vlan would have it's own isolated binding table as well as every other table, array or structures. Maybe some one can explain a solution or the reason why this is normal.

Aironet 1252 Power Inline Cat3560e

6 units of Aironet 1252g
1 unit of Catalyst 3560e
Straight out of the box, 5units of my Aironet 1252 are able to power right on when plugged into the Cat3560e, with the "power inline static" command on interface ports.
However 1 unit of it, does not power up. On the switch it indicates power granted. But there is no LED activity at all.
I would like to confirm if this particular 1 AP is faulty? Or is there a special command for it to power on?

It shouldn't require a special command to turn on. Did you try plugging it into the wall? Did you try unplugging the other 5 and plugging this one into one of their switchports?
Maybe plug a console cable in and see if you get anything, just in case the LEDs are bad.
Either way, it sounds like something's wrong with it. That's my evaluation :D

Aironet 1252 Boot Error

Hi Guys,
I need a help with an Aironet 1252 which is failing on boot. When power on the access-point shows the error below.
WARNING: A memory error occurred during the system start-up
self-test. The device must be serviced if the error persists.
The following commands can, optionally, be used to initialize
the flash file system and the TFTP file transfer system:
But when this happen, I can start the IOS manually doing flash_init and boot in ROMMON. After do this commands, the access-point starts and works normally.
How can I check and correct the memory and solve this issue? Anyone had an idea?
Thanks

Hi,
Yes, it looks like you will need to have the unit RMAd, if you like you could try the mode button procedure to reload the IOS to the AP and reset the AP to defaults as a last option.

Aironet 1252 DHCP with vlans

Similar Messages

Maybe you are looking for