WLC & Swich vlan-int communication issues

Hello,
I have a Cisco-Switch configured with 3-VLANs (1,3 & 6) . im using VLAN-1 as the management vlan for communication between WLC & Switch.
I have 1-management interface and 2-dynamic interfaces created on WLC. management-int is using untagged vlan. and from the Cisco-Switch i can ping WLC Management-int ip. but i can not ping other WLC Dynamic-interfaces, while all the subnets-ips are configured properly. also wifi clients can not connect through those dynamic-interfaces ssids
can any one help please, here is some config outputs from my WLC >>>>>>>>>>>>>>>>>
(Cisco Controller) >show wlan summary
Number of WLANs.................................. 3
WLAN ID WLAN Profile Name / SSID               Status    Interface Name
1        FMFB-WIFI-MGT / FMFB-WIFI-MGT          Enabled   management
2        FMFB-HO-LAN / FMFB-HO                  Enabled   vlan-3
3        FMFB HO Guest / FMFB-Guest             Enabled   vlan-6
(Cisco Controller) >show interface summary
Number of Interfaces.......................... 4
Interface Name                   Port Vlan Id IP Address      Type    Ap Mgr Guest
management                       1    untagged 192.168.2.239   Static Yes    No
virtual                          N/A N/A      1.1.1.1         Static No     No
vlan-3                           1    3        192.168.100.239 Dynamic No     No
vlan-6                           1    6        192.168.110.239 Dynamic No     No
(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >show interface detailed management
Interface Name................................... management
MAC Address...................................... 50:06:04:ca:97:20
IP Address....................................... 192.168.2.239
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 192.168.2.250
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. untagged
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
DHCP Proxy Mode.................................. Global
Primary DHCP Server.............................. 192.168.2.250
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
mDNS Profile Name................................ Unconfigured
AP Manager....................................... Yes
Guest Interface.................................. No
L2 Multicast..................................... Disabled
--More-- or (q)uit
(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >show interface detailed vlan-3
Interface Name................................... vlan-3
MAC Address...................................... 50:06:04:ca:97:24
IP Address....................................... 192.168.100.239
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 192.168.100.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 3
Quarantine-vlan.................................. 0
NAS-Identifier................................... HO_WLC
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
DHCP Proxy Mode.................................. Global
Primary DHCP Server.............................. Unconfigured
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
mDNS Profile Name................................ Unconfigured
AP Manager....................................... No
Guest Interface.................................. No
--More-- or (q)uit
L2 Multicast..................................... Enabled

it is my switch port config,
interface FastEthernet0/23
description connected-to-ap
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,3,6
switchport mode access
no ip address
interface FastEthernet0/24
description connected-to-WLC
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,3,6
switchport mode access
no ip address
I also enabled LAG, but with no result still>>>>>>>>>

Similar Messages

Nexus1000v - ? communication issue vcenter - N1Kv ???

Unregulary we get these kind of alarms in our vcenter although there were no changes made on nexus or VM side.:
"vSphere HA detected that host HOSTNAME is in a different network partition than the master MASTERNAME"
They are cleared after a certain time without any manual action.VMware assumes a communication issue between vcenter and nexus1000.
Anyone with similar experiences (or even a solution)???

Hi Sachin,
Thanks for your response.
Please find my reply below:
Is the module showing as up in the VSM when you execute 'show module'?
>Yes the module is up and showing active when i execute the given command
Is you ESX management VLAN allowed on the access port profile and on the uplink? Is it created on the switch?
>Yes it is created on the vswitch as well as the upstream switches and allowed in the link also.
Do you have system VLANs for your control, packet connectivity? For your ESX mgmt connectivity?
> Yes i had defined control, packet and management vlans as system vlans.
I feel that the port profile is not allowing the traffic to go in and out from the DVS.
When i change the uplink of VSM from vswitch to DVS then the VSM doesnt reach gateway itself.
Thanks,

FIX: FireWire communication issue solved - What worked for me

After installing the iPod Updater 2006-01-10, I found that my FireWire devices (not just my iPod) no longer worked. After much messing about with all the suggestions I found online (none of which worked) I've managed to sort out the FireWire communication issues I had.
you can read about the exact issues I had here:
http://forums.kustompcs.co.uk/showthread.php?t=35034
and here:
http://discussions.apple.com/message.jspa?messageID=1562072
Unfortunately those looking for a quick fix will be disappointed, I had to:
a) Send my iPod Mini back to Apple, which was promptly replaced
b) Totally re-install Windows (including drive format)
c) Borrow the install CD that came with my friends iPod, which had a later version of iPod Updater (2005-10-12) than the one I had on my install CD, but earlier than the dreaded 2006-01-10
If anyone needs this updater (as it's impossible to find an earlier one on Apple's website) drop me your email in here and I'll send you the web address to download it. This is basically a ZIP of the original CD, totally virus free (for those that are worried) and appears to work fine.
If Apple have an issue with this, then why don't you fix the link on your site to this updater; this is simply my response to the complete lack of response from Apple on this matter.
A quick note about the: 'connection rate=S100 ERROR'.
If you discover you have this error when you test your iPod in diagnostic mode; find out how to do this here:
http://www.methodshop.com/mp3/ipodsupport/diagnosticmode/index.shtml
Then it appears there is nothing you can do to fix this other than sending it back to Apple. No amount of restoring will solve it.
I hope this helps someone out there! I've yet to fix the issue with my LaCie drive (basically it needs sending back) which if anything proves that whatever screwed my system did something to the hardware on a low level, it wasn't a Windows software issue, because after re-installing it, I download SP2 and ALL the latest hotfixes, if that was the cause, it would have done it again.
This leaves one culprit - the iPod Updater 2006-01-10, as this was the only software I installed at the time both of my FireWire devices went down, avoid it like the plaque.
Regards
Matt

After installing the iPod Updater 2006-01-10, I found that my FireWire devices (not just my iPod) no longer worked. After much messing about with all the suggestions I found online (none of which worked) I've managed to sort out the FireWire communication issues I had.
you can read about the exact issues I had here:
http://forums.kustompcs.co.uk/showthread.php?t=35034
and here:
http://discussions.apple.com/message.jspa?messageID=1562072
Unfortunately those looking for a quick fix will be disappointed, I had to:
a) Send my iPod Mini back to Apple, which was promptly replaced
b) Totally re-install Windows (including drive format)
c) Borrow the install CD that came with my friends iPod, which had a later version of iPod Updater (2005-10-12) than the one I had on my install CD, but earlier than the dreaded 2006-01-10
If anyone needs this updater (as it's impossible to find an earlier one on Apple's website) drop me your email in here and I'll send you the web address to download it. This is basically a ZIP of the original CD, totally virus free (for those that are worried) and appears to work fine.
If Apple have an issue with this, then why don't you fix the link on your site to this updater; this is simply my response to the complete lack of response from Apple on this matter.
A quick note about the: 'connection rate=S100 ERROR'.
If you discover you have this error when you test your iPod in diagnostic mode; find out how to do this here:
http://www.methodshop.com/mp3/ipodsupport/diagnosticmode/index.shtml
Then it appears there is nothing you can do to fix this other than sending it back to Apple. No amount of restoring will solve it.
I hope this helps someone out there! I've yet to fix the issue with my LaCie drive (basically it needs sending back) which if anything proves that whatever screwed my system did something to the hardware on a low level, it wasn't a Windows software issue, because after re-installing it, I download SP2 and ALL the latest hotfixes, if that was the cause, it would have done it again.
This leaves one culprit - the iPod Updater 2006-01-10, as this was the only software I installed at the time both of my FireWire devices went down, avoid it like the plaque.
Regards
Matt

Any fix for the PC based network printer communication issue with Mavericks?

Any fix for the PC based network printer communication issue with Mavericks?

I just signed up for FIOS and am not experiencing your problem (had enough other ones instead).
Go to mail preferences ~ click on a mail account ~ click on the advanced tab. The only settings that worked for me were: port 110 SSL OFF, authentication: Authenticated POP (APOP). If I remember correctly when I first set this up another window opened and I typed in my password and never had to do that again.
Hope this helps.

Topology for servers' side VLAN int

With an ACE SM in the cat65k configured in routed mode and the real servers' defaul gateway being the server side Layer 3 VLAN int on the ACE, when the real server initiates the connection, does it go to the MSFC-ACE-server side Layer 3 VLAN int or does it somehow hit the Layer 3 VLAN int on the ACE without going thru MSFC?
Thanks..

It depends what ip address is configured as default gateway on the server.
If ACE, it will go to ACE.
And the problem is that the response will probably bypass ACE if the MSFC is attached to the server vlan.
You should not configure the MSFC interface on the server vlan. Let the ACE route between servers and MSFC.
Gilles.

Ethernet Communications Issue

Hello list,
I have an ethernet communications issue.
We can communicate with our products using two communications modes, ethernet, and a proprietary CAN. For the ethernet connection, I have a router that assigns a DHCP address to the product (169.254.130.005). For the CAN connection there is a hardware ethernet to CAN adapter that has an assigned address of 169.254.130.006.
Below is a simplified example of the code I use to talk to the product. (there is only one loop...two loops are shown. One showing the True Cases, one showing the False cases.
So I set the I.P. address, set "Connect?" to true, and run my code for a while. I then set "Connect?" to false, change the I.P. address, and then set "Connect?" to true.
What I have found is that the "TCP Close Connection" does not actually close the connection, and the "TCP Read" and "TCP Write" are reading and writing to BOTH I.P. addresses simultaneously! (confirmed by using Wireshark). I don't understand how this can be since I only have one TCP Write and one TCP Write, and see only one "Connection I.D." when I probe that wire.
Am I not closing the connection properly? Do I have to kill the connection ID in Windows somehow?
Any ideas would be appreciated.
Thanks in advance,
Mike
Using Labview 8.2
Windows XP
Attachments:
Ethernet Issue.JPG ‏274 KB

Nathand,
The code shown is a simple representation of what I'm doing. I guess it wasn't clear. The switch is connected to a shift register to compare the previous & current loops itterations and only opens one connection "on change" of the "Connected?" input. (that is confirmed with Wireshark). Also, the product tells me that I have made only one TCP/IP connection on each IP address.
I pass the Connecion ID that is created out the right side of the loop and into the left with a shift register when the connectionis made...so the same Connection ID is used for each read/write. What I'm not understanding is how I can see only one Connection ID on the wire but a read/write to both I.P. addresses with only one one read and one write in my code.
Any other ideas would be appreciated.
Thanks,
Mike

Xi3 companion box communication issues with X1 platform

Hopefully someone has had this issue as I haven't been able to find this one during my search.   Subject: Xi3 set top boxes will not connect to the X1 platform on the same outlet(s) that my RNG150 will.   Background: 4 weeks ago a very polite gentleman working with an Xfinity subcontractor arrived at 8am to install our Xfinity package and equipment. 8 hours later he finally left. During that time, there were multiple connectivity issues with the small Xi3 set top boxes. The X1 platform (DVR) and modem were easily set up and tested and worked perfectly (and still do) at the main location in our great room, however, when it came time to connect the other 3 rooms (all located upstairs), there were communication issues. As my wife set up services with Xfinity, she didn't realize we needed these extra set top boxes, so the technitian had to call and add them and only had (2) of the "new" Xi3 boxes, but had an "older" RNG150 set top box in his vehicle so we had him install that one as we didn't mind the older larger box in the rec room. After multiple calls to trouble shoot why these two boxes weren't communicating, he apparently resolved the issue, tested the boxes and we signed off and he left. That evening I went to turn on the bedroom tv and nothing but the red screen of death. Error code RDK 03030. So, I followed the troubleshooting guildlines, rebooting the platform in sequence, several times to make sure I got it right. Still red screen. I checked the other Xi3 box, same issue. Since the rec room tv was still working, I just jacked that box and moved it to our bedroom. BOOM. Full functionality. Only problem was the inability to access our saved programs. So, i've been doing this for the last 4 months. Moving the box from our room to the rec room for our little one to watch cartoons, then back to our room at night. Suffice it to say, my wife is growing tired of this so I put a call into the technician as he wanted to make sure I call him first so the install doesn't look negative on his record. No response. I've been researching this for the last week and have come to the following conclusions. - Possible wire/coax issue.This seemed the most plausible, however, I was able to confirm we have the COMMSCOPE Amp installed and the line to the X1 platform does in fact work based on the fact the older box works on the same line, so if it is some sort of wiring issue its lost at the Xi3 box or perhaps the older box requires a weaker signal to perform? I've also seen many comments suggesting the COMMSCOPE amps are garbage. Thats fine, but if it worked previously, and the older box works, would that still be the culprit?
- Moca issue.I'm not entirely sure how this works, but when checking diagnostics, the grid shows 0's across the matrix. Even with the older box active. I'm at work currently so I cannot post the rest of the diagnostics, can provide that once I get home.- Hardware issue. Even though these boxes worked when the technician installed and tested them, perhaps there is a hardware failure or these boxes are "bad".   Hopefully someone on here can help, I'd prefer not to have to contact customer service, follow all the trouble shooting steps I've perfomed ad nauseum and have a tech come out if possible. However, if it has to happen then so be it. Thanks for your help in advance.

Hopefully someone has had this issue as I haven't been able to find this one during my search.   Subject: Xi3 set top boxes will not connect to the X1 platform on the same outlet(s) that my RNG150 will.   Background: 4 weeks ago a very polite gentleman working with an Xfinity subcontractor arrived at 8am to install our Xfinity package and equipment. 8 hours later he finally left. During that time, there were multiple connectivity issues with the small Xi3 set top boxes. The X1 platform (DVR) and modem were easily set up and tested and worked perfectly (and still do) at the main location in our great room, however, when it came time to connect the other 3 rooms (all located upstairs), there were communication issues. As my wife set up services with Xfinity, she didn't realize we needed these extra set top boxes, so the technitian had to call and add them and only had (2) of the "new" Xi3 boxes, but had an "older" RNG150 set top box in his vehicle so we had him install that one as we didn't mind the older larger box in the rec room. After multiple calls to trouble shoot why these two boxes weren't communicating, he apparently resolved the issue, tested the boxes and we signed off and he left. That evening I went to turn on the bedroom tv and nothing but the red screen of death. Error code RDK 03030. So, I followed the troubleshooting guildlines, rebooting the platform in sequence, several times to make sure I got it right. Still red screen. I checked the other Xi3 box, same issue. Since the rec room tv was still working, I just jacked that box and moved it to our bedroom. BOOM. Full functionality. Only problem was the inability to access our saved programs. So, i've been doing this for the last 4 months. Moving the box from our room to the rec room for our little one to watch cartoons, then back to our room at night. Suffice it to say, my wife is growing tired of this so I put a call into the technician as he wanted to make sure I call him first so the install doesn't look negative on his record. No response. I've been researching this for the last week and have come to the following conclusions. - Possible wire/coax issue.This seemed the most plausible, however, I was able to confirm we have the COMMSCOPE Amp installed and the line to the X1 platform does in fact work based on the fact the older box works on the same line, so if it is some sort of wiring issue its lost at the Xi3 box or perhaps the older box requires a weaker signal to perform? I've also seen many comments suggesting the COMMSCOPE amps are garbage. Thats fine, but if it worked previously, and the older box works, would that still be the culprit?
- Moca issue.I'm not entirely sure how this works, but when checking diagnostics, the grid shows 0's across the matrix. Even with the older box active. I'm at work currently so I cannot post the rest of the diagnostics, can provide that once I get home.- Hardware issue. Even though these boxes worked when the technician installed and tested them, perhaps there is a hardware failure or these boxes are "bad".   Hopefully someone on here can help, I'd prefer not to have to contact customer service, follow all the trouble shooting steps I've perfomed ad nauseum and have a tech come out if possible. However, if it has to happen then so be it. Thanks for your help in advance.

About the communication issues in the client-server program

About the communication issues in the client-server program
Hi, I have some questions about the communication issues in a java project, which is basically the client and server architecture. In brief, the client, written in java, can be deployed anywhere, and in the following part, assume it is in the LAN (Local Area Network) which is connnected to the internet through the firewall and/or proxy, and the server, written in
java too, simply provides the listening service on a port in a remote machine. And assume the server is connected to the internet directly so that the scenario can be simple to focus on the core questions.
My questions are as follows:
1 About the relationship between the communication port and protocol
Generally, protocols at the application level like HTTP, FTP have their own default port, e.g., HTTP is corresponding to 80,
FTP is to 25. But it is NOT necessary for the web server to provide the HTTP listening service at port 80, right? E.g, Tomcat provides the HTTP listening service at 8080. So it means the default relationship between the application protocl and their port is some routine, which is not necessary to follow, right?
2 Assume a LAN connected to the internet through a proxy, which only allows HTTP protocol, then questions are:
2.1 Does the proxy recognize the HTTP request from the client by the port number (carried in the request string)? For example, when the server provides the HTTP listening service at 80, then the request from the client will include the port number 80, then the proxy will parse such info and decide if or not the request can be out.
2.2 Does the proxy recognize the HTTP request from the client by protocol (carried in the request string)? For example, the protocol used in the communicatin should be included in the request, then the proxy can parse it to make the decision.
3 In java programm, if using the HTTP protcol, then on the client: the corresponding API is java.net.URLConnection, right?
If using the TCP protocol directly, then on the client:the corresponding API is java.net.Socket, right? In both cases, the server side use the same API, java.net.ServerSocket?
Is it correct to say that the communication by Socket is faster than URLConnection?
4 Take MSN messenger for example, which protocol does it use? Since proxy configure is only the possible option, so I guess generally the TCP protocol is used directly so that the better perfomrance can be achieved, right?
5 Given 3 computers within the same LAN, can the client, proxy, server environment above be correctly simulated? If so, can
you recommend me some typical proxy program so that I can install it to configure such an enviroment to perform some test?
6 I guess there should be some software to find out which port number a given program/process is going through to connect to
the remote machine, and which port number a given program/process is listening on? Also, what protocl is used in the given
communication.
7 Finally, regarding each of the above questions, it will be highly appreciated that if you can recommed some references,
tutorials, books etc. In summary, what I care about is how to enable the java client behind the proxy and firewall to
communicate with the remote server without problems, so if you know some good tutorials plz let me know and thx in advance!
Finally, thanks for your attention so such long questions =).

FTP is to 25. But it is NOT necessary for the web
server to provide the HTTP listening service at port
80, right? E.g, Tomcat provides the HTTP listening
service at 8080. So it means the default relationship
between the application protocl and their port is
some routine, which is not necessary to follow,
right?Not sure what you're saying here.
There must be a server listening on some port. The client must know what port that is. If you open the connection using the Socket class, you'll explicitly specify the port. If you use some higher level class like URLConnection or something in the commons Net package, there's probably a default port that will be used if you don't explicitly specify another.
There's no way for the client to know that the HTTP request will go to port 80 instead of port 8080. If you think the the client contacts the server without explicitly naming a port, and then asks the server "get me your HTTP server", and the port is determined from that, you're mistaken.
Not sure if you're thinking that, but it sounded like you might be.
2 Assume a LAN connected to the internet through
a proxy, which only allows HTTP protocol, then
questions are:
2.1 Does the proxy recognize the HTTP request
from the client by the port number (carried in the
request string)? For example, when the server
provides the HTTP listening service at 80, then the
request from the client will include the port number
80, then the proxy will parse such info and decide if
or not the request can be out. I'm not sure, but I think most proxies and firewalls are configured by ports. I thought I'd heard of more sophisticated, higher-level ones that could understand the content to some degree, but I don't know anything about those.
3 In java programm, if using the HTTP protcol,
then on the client: the corresponding API is
java.net.URLConnection, right?That's one way.
You might want to look into this:
http://jakarta.apache.org/commons/httpclient/
If using the TCP protocol directly, then on the
client:the corresponding API is java.net.Socket,
right? In both cases, the server side use the same
API, java.net.ServerSocket? A Java client will user Socket, and a Java server will use ServerSocket and Socket.
Is it correct to say that the communication by Socket
is faster than URLConnection?Probably not.

WLC DHCP & VLAN issue

Hello,
I configured on my WLC 5508 a new Interface & VLAN . The WLC act as DHCP Proxy.
I enabled also Flex Connect local switching . Then I removed on my Switch under the
VLAN settings the IP helper because as I know the WLC act as IP helper.
What is still not clear for me is where I have to insert the DHCP server adress
on my WLC controller. Must I insert the DHCP server IP under my management Interface
or where I have to enter the DHCP server IP.
I tested this with the new VLAN interface and added the DHCP server IP but without success.
Thanks for help.
Regards

Hi,
I addedd an IP helper under the L3 configuration without success. Same, WLAN clients don´t get an IP .
I configured following:
add a new VLAN into the switch with layer 3 and addedd IP helper on the L3 switch.
add the VLAN into the WLC controller wth a new SSID and Interface for this VLAN.
Enabled Flex Connect under the SSID.
Done a test with a wired client direct on a switch without problems.
If I try to connect over the WLAN then the client don´t get an IP.
Regards

WLC 4402 vlan questions

I am trying to implement a Cisco Wireless solution. I have some Cisco knowledge, but it is limited. I did successfully configure the WLC 4402 with 1200 series APs. Created two WLANs, each with its own SSID. SSID ?guest? uses WEP, and gets addresses via the internal DHCP server. The DCHP range I chose exists within out current network, something I need to change according to the documentation I have read. This network should not see our network, but can browse the internet. SSID ?secure? uses WPA with MAC authentication. I can connect to either SSID and access all network resources. However this only works with two caveats.
1) I have to use the management interface
2) The DHCP range for the guest network needs to fall within our network
Trying to implement any kind of security for the ?guest? network has not gone so well. I have problems just about at every point. After reading some documents, I decided I needed to add 2 interfaces for the 2 WLANs. My interface info is below.
Interface Name Mgr Port Vlan Id IP Address Type Ap
ap-manager LAG untagged 10.1.104.154 Static Yes
guest LAG 10 192.168.10.10 Dynamic No
management LAG untagged 10.1.104.153 Static No
production LAG 20 192.168.20.20 Dynamic No
service-port N/A N/A 192.168.1.1 Static No
virtual N/A N/A 1.1.1.1 Static No
My intention was to apply an access list the guest VLAN so as to limit its traffic. If I apply the guest interface ?VLAN 10 (instead of the management-VLAN 0) it doesn?t work. I found a doc that addresses this so I added trunking to the interface the WLC is attached to on our 6509 (CatOS)switch.
MySwitch (enable) set trunk 2/6 on dot1q
Trunking is enabled, but no dice. I thought this might be a routing issue between my switch and my gateway. So I changed the VLAN on the management interface. I thought this would at the very least allow me to ping the switch, but I was wrong. I changed that back and added this entry into our gateway
interface Vlan10
ip address 192.168.20.1 255.255.255.0
I thought that way the wireless controller would be able to see the IP address, on the router, but it didn?t work.
Also I cannot use the new DHCP range I chose (192.168.10.x), I assume because it is not 10.1.x.x, so it can?t find it.
I would really appreciate some help from someone who has done this. I am very confused.

Hi
Okay number of things here.
Firstly you are correct about needing a trunk interface between the WLC and your switch. Make sure that all the vlans you have created are allowed on the trunk link.
On the 6509 run
"sh int trunk" and confirm that the status is up.
You will need to create vlan interfaces for each of your WLC vlans on the 6500. You say you have created vlan 10 interface on the 6500.
What is the default gateway on the WLC set to ?
For DHCP addressing to work you will need to us eth "ip helper-address "DHCP IP address" under the vlan interface eg
vlan 10
ip address 192.168.20.1 255.255.255.0
ip helper-address "DHCP server address"
You need to do this for all vlan interfaces you want to pick IP addresses up for clients.
HTH
Jon

WLC 5508, vlan select, reserved address in external DHCP server

Hi guys,
I have a deploy with a WLC 5508 version 7.0.116.0, APs mode local and vlan select feature enable. The issue is that the reserved IP address in external DHCP server not work. The DHCP contains a reserved IP address associates with mac address, but the assignement of IP is not match with de policies in DHCP. All others services operate normally.
This reserved assignment operate previusly to modificate the WLAN to vlan select feature. Help me to improve this situation.
Thanks.-
Best regards

Hello Abhishek, thanks for you quick answer....
the link was a document used for the deploy, but not especifict nothing about the reserved IP address for particular host. In other words, the reserved IP address (through MAC address) in external DHCP server not work when "vlan select" its enable.

WLC 5508 Internal DHCP server issues

Hi,
I am hoping to get your feedback around the dhcp issues I am facing with Two Centrally Switched Wireless LANs. I have tried to explain the setup and the problems below and would appreciate it if anyone can suggest a solution for the problems I am facing:
The setup is as follows:
- I have a WLC 5508 which has been configured with 4 SSIDs, out of which 2 are using Central Authentication and Switching.
- I have an LWAP connected to the WLC in HREAP mode.
- WLC is configured as the DHCP server for clients connecting to the SSID 'Guest'. For the rest, I am using external dhcp server.
- Only one scope for Guest Interface is setup on the WLC.
Problems:
1. As far as I know, for WLC to act as internal dhcp server, it is mandatory to have the proxy enabled, but the Clients connecting to SSID 'Internet' are
unable to get an ip address from the external dhcp server, if dhcp proxy is enabled on the WLC. If i disable the proxy, it all works fine.
2. DHCP does not release the ip addresses assigned to clients even after they are logged out.
3. If a machine which was earlier connected to 'Guest' SSID connects to the 'Internet' SSID, it requests the same ip it was assigned by the WLC which it was assigned under 'Guest', but gets tagged with the Vlan configured on the management interface.
************Output from the Controller********************
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.116.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS + LDPE
(Cisco Controller) >show interface summary
Interface Name                   Port Vlan Id IP Address         Type        Ap Mgr        Gu
est
guest                                        1    301      10.255.255.30    Dynamic   No              No
management                          1    100      172.17.1.30        Static          Yes            No
service-port                              N/A N/A      192.168.0.1       Static         No               No
virtual                                        N/A   N/A      10.0.0.1              Static         No               No
(Cisco Controller) >show wlan summary
Number of WLANs.................................. 4
WLAN ID WLAN Profile Name / SSID               Status    Interface Name
1        LAN                                    Enabled   management
2        Internet                               Enabled   management
3        Managment Assets          Enabled   management
4        Guest                                  Enabled   guest
(Cisco Controller) >show dhcp detailed guest
Scope: guest
Enabled.......................................... Yes
Lease Time....................................... 86400 (1 day )
Pool Start....................................... 10.255.255.31
Pool End......................................... 10.255.255.254
Network.......................................... 10.255.255.0
Netmask.......................................... 255.255.255.0
Default Routers.................................. 10.255.255.1 0.0.0.0 0.0.0.0
DNS Domain.......................................
DNS.............................................. 8.8.8.8 8.8.4.4 0.0.0.0
Netbios Name Servers............................. 0.0.0.0 0.0.0.0 0.0.0.0
(Cisco Controller) >show interface detailed management
Interface Name................................... management
MAC Address...................................... e8:b7:48:9b:84:20
IP Address....................................... 172.17.1.30
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 172.17.1.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 100
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. 172.30.50.1
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... Yes
Guest Interface.................................. No
L2 Multicast..................................... Enabled
(Cisco Controller) >show interface detailed guest
Interface Name................................... guest
MAC Address...................................... e8:b7:48:9b:84:24
IP Address....................................... 10.255.255.30
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 10.255.255.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 301
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. Unconfigured
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... No
Guest Interface.................................. No
L2 Multicast..................................... Enabled
(Cisco Controller) >show dhcp leases
       MAC                IP         Lease Time Remaining
00:21:6a:9c:03:04    10.255.255.46    23 hours 52 minutes 42 seconds        <<<<<<< lease remains even when the client is disconnected.
*********Example of Client connected to the right Vlan with an ip address from the incorrect interface. *************
(Cisco Controller) >show client detail 00:21:6a:9c:03:04
Client MAC Address............................... 00:21:6a:9c:03:04
Client Username ................................. N/A
AP MAC Address................................... a0:cf:5b:00:49:c0
AP Name.......................................... mel
Client State..................................... Associated
Client NAC OOB State............................. Access
Wireless LAN Id.................................. 2                 <<<<<<<<   'Internet' SSID
BSSID............................................ a0:cf:5b:00:49:ce
Connected For ................................... 319 secs
Channel.......................................... 36
IP Address....................................... 10.255.255.46      <<<<<<< IP address assigned from the 'Guest' Interface or dhcp scope on the WLC
Association Id................................... 1
Authentication Algorithm......................... Open System
Reason Code...................................... 1
Status Code...................................... 0
Session Timeout.................................. 1800
Client CCX version............................... 4
Client E2E version............................... 1
QoS Level........................................ Silver
802.1P Priority Tag.............................. disabled
WMM Support...................................... Enabled
Power Save....................................... OFF
Mobility State................................... Local
Mobility Move Count.............................. 0
Security Policy Completed........................ Yes
Policy Manager State............................. RUN
Policy Manager Rule Created...................... Yes
ACL Name......................................... none
ACL Applied Status............................... Unavailable
Policy Type...................................... N/A
Encryption Cipher................................ None
Management Frame Protection...................... No
EAP Type......................................... Unknown
H-REAP Data Switching............................ Central       <<<<<<<<<
H-REAP Authentication............................ Central       <<<<<<<<<<
Interface........................................ management
VLAN............................................. 100           <<<<<<<<<<< right Vlan
Quarantine VLAN.................................. 0
Access VLAN...................................... 100

Hi All,
I have a similar issue where Wireless clients are not receiving automatic addressing from an internal DHCP server. I have multiple interfaces configured on the WLC which are connected to separate VLANS. The manually specified DHCP primary server entry is the same on all interfaces. Some clients are able to authenticate and receive automatic IP configuration but some clients are failing the address assignment process. I have checked connectivity between the WLC and DHCP server, this is confirmed as working. When I carry out a "debug dhcp packet enable", I get the following outputs which seems as if the DHCP discover request from the client is skipped. Your thoughts and inputs on this are appreciated.
DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: message type = DHCP DISCOVER
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 116 (len 1) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 61 (len 7) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: requested ip = 169.254.223.5
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 12 (len 13) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: vendor class id = MSFT 5.0 (len 8)
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 55 (len 11) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 43 (len 2) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP options end, len 76, actual 68
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP Forwarding DHCP packet (332 octets) packet DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
Thanks,
Raj Sandhu

802.1X dyanmic VLAN assignment DHCP issue (Vista client)

I am labbing dynamic VLAN assignment and have run into a small problem. The switchport is succesfully changing to the new VLAN, but my test PC seems to get an IP address in the native data VLAN before being moved to the new dynamic assigned VLAN. So when the switch changes the VLAN the PC keeps its old IP address and nothing talks any more.
Is this a Vista issue? I thought all of these problems were just issues in XP? Do I need to tweak any interface dot1x timers?
(Cat3750 with 12.2.55 / ACS5.1. Everything else is running fine by the way.)

if i do a show run on the switchport the config hasnt changed, but i dont expect it to, as its not a permanent config change that you would want to be saved by a different admin user saving the config. You can see the debug report it is changing the VLAN:
Apr 19 09:22:56.263: %AUTHMGR-5-START: Starting 'dot1x' for client (0014.c209.896f) on Interface Gi1/0/19 AuditSessionID C0A8FE250000000900291476
Apr 19 09:22:58.604: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to up
Apr 19 09:22:59.560: %DOT1X-5-SUCCESS: Authentication successful for client (0014.c209.896f) on Interface Gi1/0/19 AuditSessionID
Apr 19 09:22:59.568: %AUTHMGR-5-VLANASSIGN: VLAN 12 assigned to Interface Gi1/0/19 AuditSessionID C0A8FE250000000900291476
Apr 19 09:22:59.585: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan12, changed state to up
Apr 19 09:23:00.307: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
Apr 19 09:23:00.315: %AUTHMGR-5-SUCCESS: Authorization succeeded for client (0014.c209.896f) on Interface Gi1/0/19 AuditSessionID C0A8FE250000000900291476
as well as checking with the show int switchport command and it is in v12 which is the dynamically assigned vlan
DHCP server is the cat3750 for all local VLANs

2106 wlc different vlan accessibility

I have 1 2106 wlc 6 1131AG LAPs that are going to be placed in three vlans. All three vlans are created and configured on a 3550G switch.
I created two additional virtual interfaces on the WLC, tagged it with appropriate vlan number and connected the port with untagged vlan identifier to a dot1q enabled trunk port on the 3550 switch. That is,
man int - untagged, port 1
vlan2, tagged -2, port 2,3
vlan3, tagged -3, port 4,5
vlan4, tagged - 3, port 6
and port 1 is connected to a trunk port on the 3550G switch with dot1q.
I am not able to reach the created vlan interfaces on the WLC !?1?!
Kindly help?

jeff.velten, wouldn't that break the very use of the WLC? documents I referred from cisco recommend to connect the WLC to a trunked port. Like here: http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00805e7a24.shtml
So how are the vlan tags from the wlc not passed on to the trunk port? Is there something I missed, somewhere?

Cisco Catalyst Supervisor communication issue?

Hey all,
I had a slight issue regarding two supervisor engines on a Cisco Catalyst 4500 device where the keepalives between the two sups lost communication for roughly 50~ seconds. This triggered an SNMP alert but it looks like they regained connectivity before a switchover was initiated. Has anyone ever experienced anything like this before?

You obviously need to configure the ports etc. but the switch should recognise the module as long as you have an IOS that supports it.
There is nothing extra to do, you just slot the module in.
If you are connecting all your distribution switches to the 6500 then if you don't need a vlan/IP subnet in multiple buildings then you should use L3 connections to the 6500.
Note also that you may want to consider at some time in the future a second supervisor or another chassis as this 6500 with one supervisor is a single point of failure ie. if it goes then there is no communication between buildings.
Jon

WLC & Swich vlan-int communication issues

Similar Messages

Maybe you are looking for