WDS and VLAns

How may WDS APs can coexist in one vlan ?

No. The communication protocol between the WDS AP and infrastructure APs is WLCCP. It is a layer 2 protocol.
If you want a WDS device co-exist in more than one VLAN, you need to use WLSM as the WDS device.

Similar Messages

WDS and Roaming with 1130AG APs

Hi there,
I was wondering if someone could provide me with some insight into a configuration scenario i'm facing:
Our office is situated in an old building and as such , wireless range is an issue as the walls are very thick and we have a mixture of clients from Laptops to android devices to iPhones that require access.
we have 2 goals (first 2 are more important)
1. to be able to roam anywhere in the building and pickup the wireless (fast roaming isn't really that necessary as voice isn't utilised)
2. to have only 1 SSID for corporate access - Corp VLAN
3. to have an SSID for guests to access - Guest VLAN
The VLANs aren't an issue, i have an 1130AG setup which already has 2 SSIDs which does what i need.
My main concern is around roaming, and i've read a lot about WDS, but this needs an external radius server, i've seen the articles that describe how to set up an AP as WDS and then add Infrastructure APs
I've also seen that you can simply configure each AP exactly the same, but with different channells.
I have 4 1130AGs at my disposal.
What would you guys suggest is my best solution?
Any help would be gratefully received.

To get the best roaming, you need to make sure you have enough coverage. That usually means a good site survey was performed to specify how many access points and the locations of the access point. Without this piece, there is no guarantee of roaming.
As far as WDS, you can setup an autonomous ap as a WDS server that is either dedicated as a WDS or is a WDS server and also serves clients.
Sent from Cisco Technical Support iPhone App

PXE, WDS and DHCP Option 66 and 67 PXE-M0F: Exiting

Hello,
I have configured DHCP options 66 and 67 to point to my site server running WDS and SCCM 2012 R2 with a DP with PXE enabled.
My DHCP server is on 10.1.54.199 and my sccm server is on 10.1.184.60 whilst my client is on 10.1.141.245. I have set the options in DHCP to 10.1.184.60 and SMSBoot\x86\wdsnbp.com
When i boot my client I get
Client MAC:xxxx GUID:xxxxxClient IP: 10.1.141.245, MASK: 255.255.254.0, DHCP IP: 10.1.54.199Gateway IP: 10.1.140.1TFTP.PXE-M0F: Exiting Intel Boot Agent.
Can anyone offer any help on where to begin troubleshooting this? Previously this has all worked but the server was recently moved to a new IP address and VLAN where IP helpers are not configured. This method worked a treat for us in 2007 but for whatever
reason not in 2012?
Any advice would be greatly appreciated.

Hi Gerry, Yes When I added the second DP to the All DPs Distribution Point Group it then went and distributed some 70 or so packages, among these were the boot images. I just double checked and the second DP is listed in the content locations tab for both
boot images.
Hi Jason,
Not yet but when i tried this earlier (16:00 ish where I am) the date modified time of the log had not changed (it reported sometime like 14:30). I will have a look in the log... It has indeed changed...
It seems to be looping through a process of:
Begin Validation of Certificate thumbprint...
Completed Validation of Certificate thumbprint...
PXE Client Certificate Valid...
Purging Old Images 0...
Purging Old Images 0...
There are a few lines above from a few hours earlier (when i installed the second DP and enabled PXE) where it shows it adding files to install que, No errors though. Further up the log I can see errors...
Initializing PXEPerfObject. SMSPXE 18/02/2014 14:21:18 3164 (0x0C5C)
Failed to get logging settings for 'ccmperf' from Registry (80070002) SMSPXE 18/02/2014 14:21:18 3164 (0x0C5C)
Could not load logging configuration for component ccmperf. Using default values. SMSPXE 18/02/2014 14:21:18 3164 (0x0C5C)
Client is set to use HTTPS when available. The current state is 224. SMSPXE 18/02/2014 14:21:19 3164 (0x0C5C)
CLibSMSMessageWinHttpTransport::Send: URL: primary-site-server.co.uk:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 18/02/2014 14:21:19 3164 (0x0C5C)
RequestMPKeyInformation: Send() failed. SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
Failed to get information for MP: http://primary-site-server.co.uk. 80004005. SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
PXE Provider failed to initialize MP connection.
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
CLibSMSMessageWinHttpTransport::Send: URL: primary-site-server.co.uk:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
RequestMPKeyInformation: Send() failed. SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
Failed to get information for MP: http://primary-site-server.co.uk. 80004005. SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
PXE::CPolicyProvider::InitializeMPConnection failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
I am not sure if the above is relevant but it is the only stuff marked red in cmtrace in SMSPXE thats around the timeframe where I was testing it earlier today.
Any suggestions?
EDIT: I dont think I have imported the web server certificate on the second DP or configured IIS to use this cert for https, I am guessing that is what these error are all about? Not sure why this would effect PXE though especially as it should be getting the
content from the first DP. I will crack on sorting this cert problem tomorrow and see if it fixes the issue I am having with PXE with no IP Helper.
EDIT 2: I also changed the DHCP option 67 from SMSBoot\x86\wdsnbp.com to SMSBoot\\x86\\wdsnbp.com. It may have been the \\ in here that also helped solve my problem.

How do I add a Subnet and vlan with a catalyst 3550 and RV120

Hello Friends.
I have a scenario that i'm hoping i can get some help with. I'll be as detailed and descriptive as i can.
This is for a business with 100 employees nodes and 100 camera nodes all needing IP internet through private addressing and public gateway.
I have a business class gateway with a private range of 12 public addresses. Ther modem does nothing but act as a gateway since i have disabled the firewall and DHCP.
In place of the firewall and DCHP from the modem i have installed a RV120 Firewall with VPN. When installing i replicated the IP scheme of the modem as to not disturb and distrup the devices assigned addresses from that scheme from the modem. I did this because the owner could not have any down time or any disruption to the business operations.
The RV120 now acts as firewall , DHCP , and VPN. I'll address the subnet first. I's using 10.0.0.0/24 subnet range.
DHCP is assigning 10.1.10.50 - 10.1.10.100 the rest are static and i plan to use static DHCP with the IP and MAC assigned to each static DHCP address.
There are 100 cameras with static IP addresses in the range of 10.1.10.11 - 10.1.10.40, and 10.1.0.1.101 - 10.1.10.170.
VPN uses PPTP assigned address 10.1.10.6 - 10.1.10.10.
There are no layer 3 switches that i know of. Just a layer two that is the primary swith and ports have run out, and various out of the box switches and wireless access points connected to the primary switch.
I want to implement subnets into the network and VLANS as well on a new Layer 3 switche from cisco. Thinking 3550 from Cisco or one of the older layer 2 switches with layer three capabilities.
I also want to introduce a 192.168.0.0/24 IP range for the existing wireless network and segment the traffic from the rest of the traffic on other ranges.
I want to replace the 10.0.0.0/24 DHCP alltogether and the static addresses for end user nodes on the same network, but keep that range just for camera nodes segmented.
I want to implement a NEW end user IP range and VLAN for employee/guest networks using the 172.16.0.0/24 range.
Iv'e thought of replacing all the wireless nodes with RV120's and use VLAN. Dont know if that strategy works. Need to think it through.
I want the 192.168.0.0/24 IP range comunicate to with the 172.16.0.0/24 and possibly the 10.0.0.0/24 range.
Any advice on how to do this?
As a side note the next step after this is to install a server domain controller as all the computers are all stand alones in their own workgroups. It's a simultaneous project that will introdue a DCHP, WINS, DNS server.

Hi Omid, it sounds like you're proposing the 3550 switch but you're not decided yet. The 3550 switch is a pretty old device and needs enhanced multilayer image. It may be more prudent to use a more current switch such as small business SG300 or SG500 as the feature set is more rich and it supports around 480 LAN connections.
To answer the inquiry, the RV120W, when you create a VLAN it will automatically create an IP interface. From this you may assign subnet as you like along with 'enable or disable' for inter vlan routing. Since the RV120W has this feature, a layer 3 switch is not required unless you are looking to keep the routing load smaller by routing locally with the switch.
With Catalyst or a small business switch you would need to create a VLAN. After creating the VLAN, on a Catalyst you can simply issue "switchport trunk encapsulation dot1q" on the desired interface and all VLAN will passage without issue. For a port connecting a user "switchport mode access" "native vlan xx" This will assign the port as untag member of the desired VLAN.
If using a small business switch, it is slightly different, you still create the VLAN but the command issue is a bit different "switchport trunk allowed vlan add xx" for the link to the router, where xx = the VLAN ID to tag to the router. For access client it remains the same as Catalyst.

Logical network to physical network mapping (subnets and VLANS) in SCVMM 2012 R2

In much of the blogs, documentation and literature on VMM, there are examples of deploying multiple logical networks onto one physical network i.e. Cluster (logical) + Storage (logical) + Backup (logical) + Live Migration (logical) + Management
(logical) on top of Datacenter (physical).
Does this mean it would be possible to have one (physical) flat VLAN-less network with one subnet and then have all those logical networks (with subnets and VLANs) on top of it? Even with a simple unmanaged L2 switch that doesn't support VLANs itself?
If not, just how do you map multiple logical networks to just one physical network? How does that work in practice? Is a L3 switch needed to route traffic between logical networks for example?

Hi. VMM Networking may be overwhelmed for the most, at first. But you really need to understand the modeling here and how things are related to each other. Especially if using NIC teaming in WS 2012 (and R2) together with this mix.
I suggest that you read the following whitepaper where we explain how to setup networking in VMM (also to support network virtualization, but that is absolutely not mandatory): http://gallery.technet.microsoft.com/Hybrid-Cloud-with-NVGRE-aa6e1e9a
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

WLC2112 with Guest / Web-Auth and vlan

Hi
I'm trying to configure my WLC with guest SSID and vlan 10.
The security is only set to Web-auth, and it is all working if the guest network is set to nativ vlan (1) But it seems that the http(s)://1.1.1.1/login.html is not reacheble from the guest SSID/VLAN??
Please help.
Management IP Address 192.168.14.252
Software Version 6.0.182.0
Emergency Image Version
I have tried with ver. 5.2 also -

I think that 1.1.1.1 is only reachable from a wireless client during webauth. They should not be able to reach that address once they have passed through the web auth page.
Don't know if that helps, or not.

WDS, DHCP and WSUS on same server, Virtuals find WDS and start up process, Physicals get PXE-X55 error.

I have a Windows 2012 R2 server that has the WSUS, WDS and DHCP roles installed. I also have a SCVMM (Win2012R2) server on different machine and it has been connected to the WDS server
Followed many different guides on the internet to configure the WDS server but if I have option 60 configured the virtual machines will find and do a PXE boot successfully, but the physical systems will fail with a E55 error.
I take out option 60 and both fail.
Did I miss a niggly bit some where?

Have you tried this (from article):
Custom-made Option 60 – String – PXEClient
Predefined Option 66 – IP or Hostname of the WDS Server (in our case 10.150.150.1)
Predefined Option 67 – boot\x86\wdsnbp.com
and this in WDS properties:
and
Many people remark this as solution:
WDSUTIL /Delete-AutoAddDevices /DeviceType:ApprovedDevices

WDS and authentication

We have 1200 APs configured with mobility networks (mGRE tunnels terminated on a WLSM). The APs are pointed at the WLSM WDS and pass their authentication requests to the WLSM acting as the WDS using WLCCP. However, these APs also provide wireless access to the local wired networks. This can be configured, but it appears that all authentication requests go via the WDS (i.e. all locally configured RADIUS servers for local network authentication are ignored).
The WLSM Deployment Guide suggests that it is possible to have "WDS" and "non-WDS" SSIDs coexist. The consequence is that the availability of the WDS (on the WLSM) becomes critical, even for APs which could authenticate local wireless users through RADIUS servers configured directly on the AP.

WDS checks its local list for authentication . If the Mac address is not present it uses configured Radius server for authentication. Make sure Mac address is either in the Local list or Radius server. If you are using Radius server make sure Mac address is configured as user

WDS and MDT

I setup my WDS and MDT Deployment and the image booms out at TFTP and never gets to the menu screen.

Hi dektame,
Some required information are needed for us to help you. A screen shoot would be appreciated.
By the way, if you mean you stuck in TFTP step, you need check if imported right boot image to WDS.
Regards
D. Wu
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

WDS AND WLSE

Hi all , one we have set up the wds, what would happen if my wlse device broke? would this take down my wds service ?

Sorry I forgot to answer this.
As I mentioned, WLSE is just monitoring.
Only If WLSE is being used as Radius server, then the NEW authentications might fail.
"Might", because remember that WDS will try to cache the credentials, for example, for roaming.
But sometimes it cache it for a long time. And additionally the current authenticated users will still be associated and authenticated. So only if a new user trys to associate and authenticate, you will notice that the authentication is not working.
Now, the other possibility is that you are using a backup WDS and or backup radius server. So everything will keep working as expected.

WDS and Unattended queries/clarification (Server 2012)

Hi Folks
I am studying for my 70-411 exam and have a few points that I would like clarification on relating to unattended installations and WDS:
1: When you create an unattend.xml for the 'Windows Deployment Services client’, in SIM which image do you need to base this on?
Do you just use the install.wim from the server iso?
2: Are both a WDSClientUnattend and a ClientUnattend mandatory for unattended to work?
For example if you only want to automate the image settings but not the settings pre-image selection (such as usename/password to connect to WDS) can you specify only a ClientUnattend?
3: Can disk partitions be set in the ClientUnattend or do these have to be in the WDSClientUnattend file?
Thanks in advance.

1. The WDS Client itself is based on "boot.wim" from a preferably new OS. For instance if you plan to deploy Windows Server 2012R2 or Windows 8.1, you need to have a 6.3 version of the boot.wim, either from the 2012R2 server iso, or Windows 8.1
iso (it doesn't actually matter). You can deploy e.g. windows 7 from the 6.3 boot.wim aswell, but not the other way around.
2. The WDSClientUnattend is for the "WDS Client" part, that means you should specify settings here on "how you want to perform the installation", e.g. which edition of Windows to install (Server standard, or Server Enterprise...), to
which DISK (and how to partition it), credentials to connect to WDS share (remoteinstall$ on WDS), and also what language and keyboard settings to use during setup. If you don't specify this, you can still specify an unattend.xml file for an install Image,
that is settings relevant to a specific image only. So you can decide to do either of them, or both.
3. This needs to be done in WDSClientUnattend, that is "1 - WinPE-phase". You can see this phase as the first phase Before first reboot, that is lang settings, partition settings, image selection, and then copying of files. Upon next reboot, and
not Before is when you reach the next Phase, that is "4 - Specialize"

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"

WAP321 - No WDS and Single Point Setup

Hi folks
I bought 3 WAP321s with the intention of creating a fairly wide network in a large building where I can't easily add wiring. Access was to be via a captive portal where I would create logins for all of the users. However since I have bought the devices I discover that it isn't possible to use both WDS and clusters at the same time. I have connected 2 devices by WDS by duplicating settings by hand in both but I have some questions that maybe some folks can answer?
1. Do I have to copy both the captive portal design and the username and logins to each of the 3 devices for this to work? (I think that I do now)
2. In the manual under the WDS discussion there is talk of both point to point and point to multipoint setups. It seems to imply that with point to multipoint then there is a single WAP handling the client associations. In that case does only one WAP handle the logins by captive portal? I am trying to avoid having to duplicate the logins on all devices.
3. How do you decide in WDS if you are point to point or point to multipoint? Is it just the number of connections that you have on the WDS setup page?
An alternative if I am desperate is to use RADIUS but I am trying to avoid that
Just for reference I have already read the manual for the WAP321 several times as well as watching the video on WDS setup
Thanks
Richard

Hi Richard, thank you for using our forum, my name is Luis I am part of the Small business Support community.
1 and 2. It isn't necessary to copy the same captive portal configuration for all the equipment, you should just configure the central WAP and the rest will receive the Captive portal.
3. In the point-to-multipoint bridge mode, one WAP device acts as the common link between multiple access points. In your case if you are connecting two WAPs to one that is a multipoint bridge.
I hope you find this answer useful
Greetings,
Luis Arias.
Cisco Network Support Engineer.

VRF configuration on subinterface and VLAN subinterface

Hi
Can I configure VRFs on subinterface (physical and VLAN) basis in a normal BGP/MPLS VPN configuration.
Thanks
VK

Hi Sultan,
You are very welcomed, i'd be more than glade to help you out your confusion, below is the output of one of my lab PEs, and moreover i've in production customers running with this setup, i've never faced the issue you are describing, if you can regenerate the test you are describing we can elaborate on it:
interface FastEthernet0/0
no ip address
interface FastEthernet0/0.1
encapsulation dot1Q 101
ip vrf forwarding a
ip address 101.101.101.1 255.255.255.252
interface FastEthernet0/0.2
encapsulation dot1Q 202
ip vrf forwarding b
ip address 202.202.202.1 255.255.255.252
This is a 7200VXR (NPE-300) running "c7200-p-mz.122-25.S14.bin".
BR,
Mohammed Mahmoud.

SCCM 2012 R2, DHCP and WDS and PXE same server

hi
I am using DHCP and PXE on same server and getting error PXE-E55: proxyDHCP did not reply to request on port 4011

HI,
To get WDS and DHCP to work on the same machine, you need to configure WDS to share the same server as DHCP, here is how it is done.
You must have a functioning DHCP server with an active scope. WDS will utilize PXE which requires a DHCP server.
Whether you plan to co-host WDS and DHCP on the same server or use two different servers you must configure WDS to listen on a specific port. DHCP and WDS both require port number 67. If you have co-hosted WDS and DHCP you can move DHCP or the PXE site role
to a separate server or use the procedure below to configure the WDS server to listen on a different port.
Modify the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE
Set the registry value to:
UseDHCPPorts = 0
For the new configuration to take effect run the following command on the co-located DHCP and WDS server:
WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes
https://technet.microsoft.com/en-us/library/bb680753.aspx
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

WDS and VLAns

Similar Messages

Maybe you are looking for