LWAPP - client roaming - DHCP request

I was thinking that by using WPA-PSK, client roaming producing a DHCP request when changing AP will not be sent by the controller to the DHCP server, which appears to be false.
Wanting to know : does CCKM (with leap) could stop this behavior, eliminating that DHCP request ? I know Radius request will not be send but what about the DHCP request ?

Agreed. You should not be getting a dhcp request when roaming. THe only time I've seen that happen is when the dhcp server does not support dhcp requests by proxy. In that case go to the cli and
config dhcp proxy disable
That will force the controller to show the client information in the dhcp request and not the virtual interface of the controller.
I don't think this is your problem however.

Similar Messages

Do client dhcp requests go through the lwapp tunnel

do client dhcp requests go through the lwapp tunnel?
for local not h-reap.
do they drop out of the lwapp tunnel and hit the dynamic interface and get forwarded to whatever the dhcp is for that vlan?

The WLC will dump the traffic out on the appropriate dynamic interface. This interface is how the wireless communicates to that particular vlan.

Client Roaming Within Single WLC with Different AP Groups

I am trying to setup a 4400 WLC with 2 different AP Groups mapped to its respective Dynamic Interfaces / Vlans. AP's are equally mapped to both the AP groups by Floor wise ex: First floor AP's connect to one AP group and the Second Floor AP's connecting to other AP group.
Goal is to create separate Network policy for each Floor using ACL's and apply to their respective Vlans on Layer 3 Switch. Wireless Raoming should happen seamlessly between these Ap groups making the DHCP changes by not disconnecting and connecting every time user roam across the Floors.
Problem is When Clients Roam between Floors i,e moving between AP Groups, they still maintain their old DHCP IP addresses when moved to new AP group even after Client re-authetication. This defies our goal of creating a Wireless Network Policy using single WLC.
Knobs i have tuned in WLC to acheive our goal includes....
1. WLAN Session Timeout - No use
2. DHCP Proxy Disable - No Use
3. ARP Time out - No use
Looks like WLC is storing the IP address and MAC information of the Client unconditonally during roaming and clearing out untill a manual or forced disconnect or disassociation is done.
Did anyone tried to implement this setup and made it running? Any help or suggestion would be higly appreciated.
Thanks
Guru

abit late for a reply but....try going to the SSID>Advanced and ticking the "DHCP Addr. Assignment" Required checkbox and test again.
What does the DHCP Required field under a WLAN signify?
A. DHCP Required is an option that can be enabled for a WLAN. It necessitates that all clients that associate to that particular WLAN obtain IP addresses through DHCP. Clients with static IP addresses are not allowed to associate to the WLAN. This option is found under the Advanced tab of a WLAN. WLC allows the traffic to/from a client only if its IP address is present in the MSCB table of the WLC. WLC records the IP address of a client during its DHCP Request or DHCP Renew. This requires that a client renews its IP address every time it re-associates to the WLC because every time the client disassociates as a part of its roam process or session timeout, its entry is erased from the MSCB table. The client must again re-authenticate and reassociate to the WLC, which again makes the client entry in the table.

WLC 2106 does not send DHCP request

Hi,
I've several WLC2106 running 4.1(185) and all is working fine.
Now we started to migrate some of them to 4.2(207) but client didn't received anymore DHCP reply.
DHCP server is a Microsoft server with the address configuren under the dynamic interfaces parameter.
With the same config and 4402 all is working fine.
With the same config and 4.1.x with WLC2016 all is working fine.
It seems something changed from 4.2.
Any idea ? Here the log of DEBUG DHCP PACKET
00:22:fb:89:d1:dc DHCP received op BOOTREQUEST (1) (len 312, port 1, encap 0xec03)
00:22:fb:89:d1:dc DHCP processing DHCP DISCOVER (1)
00:22:fb:89:d1:dc DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
00:22:fb:89:d1:dc DHCP xid: 0x5cbacd54 (1555746132), secs: 3, flags: 0
00:22:fb:89:d1:dc DHCP chaddr: 00:22:fb:89:d1:dc
00:22:fb:89:d1:dc DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
00:22:fb:89:d1:dc DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
00:22:fb:89:d1:dc DHCP requested ip: 169.254.122.145
00:22:fb:89:d1:dc DHCP successfully bridged packet to DS
00:10:18:3d:9c:2b DHCP received op BOOTREQUEST (1) (len 268, port 1, encap 0xec00)
00:10:18:3d:9c:2b DHCP dropping packet (no mscb) found - (giaddr 0.0.0.0, pktInfo->
Many thanks
Luigi

In 4.1, disabling DHCP proxy did just that, it disabled the "proxy". If you ever look at your dhcp lease of a wireless client, it comes from a dhcp server of 1.1.1.1 (virtual IP of the controller). With proxy disabled, the address will no longer be masked.
In 4.2 and beyond, disabling dhcp proxy actually disables the DHCP Relay that is the process of the controller sending the dhcp requests to a specified server.
So if in 4.1, you had "dhcp proxy" disabled, in 4.2 and beyond, you are actually disabling the relay as well.
If this is indeed the case, enable dhcp proxy, or add an IP Helper adress to your router for this vlan, just like you would normally do for Wired clients.

OSX sends out Dhcp requests thru the wrong interface

I have setup an Xserve so far only providing file services over AFP. It is located in our computer room on a different broadcast domain. I use a separate machine as a DNS. I would like to use my Xserve's 2nd ethernet interface to provide Netboot/Netinstall services on a 192.168.x.x network for bulk imaging of our clients. I have enabled Dhcp and setup Netboot on the eth1 but the system.log shows that it is floding my computer room network sending dhcp requests from eth0.
I have checked the bootpd.plist file and the settings seem ok.

Check your terminology.
it is floding my computer room network sending dhcp requests from eth0.
The only way it would send any DHCP traffic on en0 would be if en0 was configured to use DHCP for its own configuration.
Running as a DHCP server is entirely passive - nothing happens until the server receives a request from a client on the LAN. Only at that point does the DHCP server send any traffic out over the wire.
In addition, 'flood' is a relative term. How much traffic are we talking here? Are you talking a few packets such as in the normal DHCP client request/refresh cycle, or are you talking hundreds of packets a second?

ASA DHCP Request incorrect hostname length

I have an ASA 5505 with software version 8.2(1). It is making DHCP requests for IPSec clients that connect to the ASA. The DHCP requests packets the ASA makes have an extra '00' appended to the hostname field, and the length field is the size of the hostname + 1.
The DHCP server is Microsoft Server 2003 and this causes the hostname to be registered with an unknown character which appears as []hostname. Then when server 2003 tries to update the DNS record, it fails because of the invalid character in the hostname.
Is there anyway to have the ASA have the correct length for the hostname field in the DHCP packet, or a workaround that will solve this problem?

I am thinking it may not be option 12 in the DHCP packet, but option 81. I have included a portion of the DHCP request from the ASA below:
   Option: (t=53,l=1) DHCP Message Type = DHCP Request
        Option: (53) DHCP Message Type
        Length: 1
        Value: 03
    Option: (t=57,l=2) Maximum DHCP Message Size = 1152
        Option: (57) Maximum DHCP Message Size
        Length: 2
        Value: 0480
    Option: (t=61,l=42) Client identifier
        Option: (61) Client identifier
        Length: 42
        Value: 00636973636F2D303032312E353537352E636131372D6D79...
    Option: (t=54,l=4) Server Identifier = 192.168.8.3
        Option: (54) Server Identifier
        Length: 4
        Value: C0A80803
    Option: (t=50,l=4) Requested IP Address = 192.168.8.105
        Option: (50) Requested IP Address
        Length: 4
        Value: C0A80869
    Option: (t=12,l=11) Host Name = "myhostname"
        Option: (12) Host Name
        Length: 11
        Value: 6D79686F73746E616D6500
    Option: (t=51,l=4) IP Address Lease Time = 8 days
        Option: (51) IP Address Lease Time
        Length: 4
        Value: 000A8C00
    Option: (t=55,l=6) Parameter Request List
        Option: (55) Parameter Request List
        Length: 6
        Value: 01060F2C0321
        1 = Subnet Mask
        6 = Domain Name Server
        15 = Domain Name
        44 = NetBIOS over TCP/IP Name Server
        3 = Router
        33 = Static Route
    Option: (t=81,l=14) Client Fully Qualified Domain Name
        Option: (81) Client Fully Qualified Domain Name
        Length: 14
        Value: 0400000A6D79686F73746E616D65
        Flags: 0x04
        0000 .... = Reserved flags: 0x00
        .... 0... = Server DDNS: Some server updates
        .... .1.. = Encoding: Binary encoding
        .... ..0. = Server overrides: No override
        .... ...0 = Server: Client
        A-RR result: 0
        PTR-RR result: 0
        Client name: 0A6D79686F73746E616D65
    End Option
    Padding
Notice in option 81 the Client Name has a leading binary value of 0A (which is a new line): 0A6D79686F73746E616D65.
Does CSCsz07757 relate to that? Is there a way to have the ASA not include option 81 as part of the DHCP requests it makes?
Thank you.

Time Capsule not passing wifi dhcp requests on the b/g network

Here's a weird one. Got two 1GB Time Capsules setup in bridge/extend mode. The Win2003 server is serving up DHCP on capsule 1 and I have wifi devices on capsule 2. Both laptops are using the N wifi spec and are getting an IP address from the Win2003 dhcp server. However, the iPhone is on the b/g network and it cannot get a dhcp request. I haven't tried the b/g network on capsule 1 yet but will. Has anyone seen this behaviour before? Would be annoying if I have to setup a 2nd dhcp server on the capsule 2 system. Essentially one capsule is in my basement and the other in my office upstairs. Any ideas?
Thanks, Joe

The reason you see conflicting conclusions is because we have to speculate about a lot of the details since Apple has not yet posted detailed specs, a user manual, or application tips.
Most of us are assuming the the wireless networking features of the Time Capsule will be similar if not identical to the existing Airport Extreme N base station. If that assumption is correct, your questions would be answered as follows:
1. yes, the TC could be used as an access point. It would have to be configured as a remote base station in a wireless distribution system (WDS).
2. and 3. yes, other clients on the network would be able to access the TC hard drive and printer
4. you could set things up the other way around - TC as the base station, and the older Airport Extreme as the remote base station.
5. for 802.11g connections, the older base station and its external antenna should give the older base station better range than the TC since power output for both models at the 802.11g standard should be similar.

DHCP request through accesspoint and router

This is how our setup is like:
Laptops => Cisco 1100 AP(static IP) => Wired LAN (Subnet 1) => Cisco Router => Wired LAN (Subnet 2) => DHCP server
What i would like is that the DHCP-request from our laptops is forwarded/relayed through the AP and Router to the DHCP-server and back.
We dont want to use the AP's internal DHCP server but centralise this.
At the moment i'v configured the AP through CLI and added the following command: ip dhcp-server xx.xx.xx.xx
Where xx is the IP of the DHCP server
On the Router i'v added the command ip helper-address xx.xx.xx.xx
Where xx is the IP of the DHCP server
Don't know if this is the correct way, but i do know it isn't working.
Some help is realy appreciated.
Grx,
Joris

You need at least the following connectivity for DHCP relay to work.
Between the DHCP relay agent and the DHCP server:
- UDP Port 67 <-> UDP Port 67
Between the DHCP server and the DHCP client:
- UDP Port 67 <-> UDP Port 68 (renewing/releasing a lease)
- ICMP echo (Most DHCP servers check if an IP is still free)
On the Cisco router you can use some debugging commands
to check that relaying works.
(This might produce a lot of output, careful on a production system.)
#term mon
#debug ip dhcp server packet
#debug ip dhcp server events
For Subnet 1 with the router's IP 10.0.0.1 and two configured
DHCP servers (192.168.0.1, 192.168.9.1) as "ip helper" a successfull
exchange looks like this:
DHCPD: DHCPREQUEST received from client 0100.aabb.bbcc.cc.
DHCPD: setting giaddr to 10.0.0.1.
DHCPD: BOOTREQUEST from 0100.aabb.bbcc.cc forwarded to 192.168.0.1.
DHCPD: BOOTREQUEST from 0100.aabb.bbcc.cc forwarded to 192.168.9.1.
DHCPD: forwarding BOOTREPLY to client 00aa.bbbb.cccc.
DHCPD: Forwarding reply on numbered intf
DHCPD: creating ARP entry (10.0.0.49, 00aa.bbbb.cccc).
DHCPD: unicasting BOOTREPLY to client 00aa.bbbb.cccc (10.0.0.49).
#undebug all
I would also try to ping the router's IP in Subnet 1 and a client
with a fixed IP in Subnet 1 from the server. (The DHCP server uses
this to check if a lease is actually free before handing it out)
Otherwise it's time for packet sniffing on the DHCP server
and the client. (snoop, tcpdump, ethereal)

Wireless Access servers 5508's won't proxy a DHCP request

Hi
This question comes from our CSC Facebook Community.
http://www.facebook.com/CiscoSupportCommunity
Who knows about Wireless Access servers 5508's and why they don't seem to want to proxy a DHCP request from a wireless client to a DHCP server?

They do.
The feature dhcp proxy must be enabled (but it is by default) and if the DHCP server ip is configured in the interface to which the SSID is attached, then it should do it.
The contrary would require a "debug client < mac address>" showing the problem to understand what is wrong.
Regards,
Nicolas

KDE Printer Manager fails with "client-error-bad-request"

I'm having some trouble with printing on my system. The KDE printer manager shows "client-error-bad-request" and no other information. When I run the KCM from the command line, I also get "kcmshell(17286) KCupsRequest::serverError: status unrecognised: 1024" on the console. I wasn't able to find any useful information on this issue on google or these forums; not even what the 1024 status code means. It seems to me that this may be a bug in the kcm_printer_manager module, but I'd like to rule out other possibilities first. Unfortunately, I don't know what to try from here. I'll provide as much potentially relevant information as I can think of below.
Changes since last successful print job:
Multiple updates to KDE packages
Update to cups that changed systemd unit file names.
Stopped and disbled old units
daemon-reload
Enable and start new units
Other updates to cups since then, if I recall correctly.
Packages and versions:
kdeutils-print-manager 4.14.3-1 (owns kcm_printer_manager module for kcmshell4)
kdebase-runtime 4.14.3-1 (owns kcmshell4 binary)
cups 2.0.1-1
libcups 2.0.1-1
systemd 218-1
linux 3.17.6-1
Let me know if any other information might be helpful.

Anyone please help.
Thanks,
Orton

Archive log missing on standby: FAL[client]: Failed to request gap sequence

My current environment is Oracle 10.2.0.4 with ASM 10.2.0.4 on a 2 node RAC in production and a standby that is the same setup. I'm also running on Oracle Linux 5. Almost daily now an archivelog doesnt make it to the standby and oracle doesnt seem to resolve the gap sequence from the primary. If I stop and restart recovery it gets the logfile and continues recovery just fine. I have checked my fal_client and fal_server settings and they look good. The logs after this error do continue to get written to the standby but the standby wont continue recovery until I stop and restart recovery and it fetches this missing log.
The only thing I know thats happening is that the firewall people are disconnecting any connections that are inactive for 60 minutes and recently did an upgrade that they are claiming didnt change anything:) I dont know if this is causing this problem or not. Any thoughts on what might be happening?
Error in standby alert.log:
Tue Jun 29 23:15:35 2010
RFS[258]: Possible network disconnect with primary database
Tue Jun 29 23:15:36 2010
Fetching gap sequence in thread 2, gap sequence 9206-9206
Tue Jun 29 23:16:46 2010
FAL[client]: Failed to request gap sequence
GAP - thread 2 sequence 9206-9206
DBID 661398854 branch 714087609
FAL[client]: All defined FAL servers have been attempted.
Error on primary alert.log:
Tue Jun 29 23:00:07 2010
ARC0: Creating remote archive destination LOG_ARCHIVE_DEST_2: 'WSSPRDB' (thread 1 sequence 9265)
(WSSPRD1)
ARC0: Transmitting activation ID 0x29c37469
Tue Jun 29 23:00:07 2010
Errors in file /u01/app/oracle/admin/WSSPRD/bdump/wssprd1_arc0_14024.trc:
ORA-03135: connection lost contact
FAL[server, ARC0]: FAL archive failed, see trace file.
Tue Jun 29 23:00:07 2010
Errors in file /u01/app/oracle/admin/WSSPRD/bdump/wssprd1_arc0_14024.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Tue Jun 29 23:00:07 2010
ORACLE Instance WSSPRD1 - Archival Error. Archiver continuing.
Tue Jun 29 23:00:41 2010
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
Tue Jun 29 23:00:41 2010
FAL[server, ARC2]: Begin FAL archive (dbid 0 branch 714087609 thread 2 sequence 9206 dest WSSPRDB)
FAL[server, ARC2]: FAL archive failed, see trace file.
Tue Jun 29 23:00:43 2010
Errors in file /u01/app/oracle/admin/WSSPRD/bdump/wssprd1_arc2_14028.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Tue Jun 29 23:00:43 2010
ORACLE Instance WSSPRD1 - Archival Error. Archiver continuing.
Tue Jun 29 23:01:16 2010
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
Tue Jun 29 23:15:01 2010
Thread 1 advanced to log sequence 9267 (LGWR switch)
I have checked the trace files that get spit out but they arent anything meaningful to me as to whats really happening. Snipit of the trace file:
tkcrrwkx: Starting to process work request
tkcrfgli: SRL header: 0
tkcrfgli: SRL tail: 0
tkcrfgli: ORL to arch: 4
tkcrfgli: le# seq thr for bck tba flags
tkcrfgli: 1 359 1 2 0 3 0x0008 ORL active cur
tkcrfgli: 2 358 1 0 1 1 0x0000 ORL active
tkcrfgli: 3 361 2 4 0 0 0x0008 ORL active cur
tkcrfgli: 4 360 2 0 3 2 0x0000 ORL active
tkcrfgli: 5 -- entry deleted --
tkcrfgli: 6 -- entry deleted --
tkcrfgli: 7 -- entry deleted --
tkcrfgli: 8 -- entry deleted --
tkcrfgli: 9 -- entry deleted --
tkcrfgli: 191 -- entry deleted --
tkcrfgli: 192 -- entry deleted --
*** 2010-03-27 01:30:32.603 20998 kcrr.c
tkcrrwkx: Request from LGWR to perform: <startup>
tkcrrcrlc: Starting CRL ARCH check
*** 2010-03-27 01:30:32.603 66085 kcrr.c
Beginning controlfile transaction 0x0x7fffd0b53198 [kcrr.c:20395 (14011)]
*** 2010-03-27 01:30:32.645 66173 kcrr.c
Acquired controlfile transaction 0x0x7fffd0b53198 [kcrr.c:20395 (14024)]
*** 2010-03-27 01:30:32.649 66394 kcrr.c
Ending controlfile transaction 0x0x7fffd0b53198 [kcrr.c:20397]
tkcrrasgn: Checking for 'no FAL', 'no SRL', and 'HB' ARCH process
# HB NoF NoS CRL Name
29 NO NO NO NO ARC0
28 NO YES YES NO ARC1
27 NO NO NO NO ARC2
26 NO NO NO NO ARC3
25 YES NO NO NO ARC4
24 NO NO NO NO ARC5
23 NO NO NO NO ARC6
22 NO NO NO NO ARC7
21 NO NO NO NO ARC8
20 NO NO NO NO ARC9
Thanks.
Kristi

It's the network that's messing up; unlikely due to firewall timeout as it waits for 60 minutes and you are switching every 15 minutes. There may be some other network glitch that needs rectified.
In any case - arch file missing/ corrupt / halfway through - FAL setting should have refetched the problematic archive log automatically.
As many had suggested already, the best way to resolve RFS issues I believe is to use real-time apply by configuring standby redo logs. It's very easy to configure it and you can opt for real-time apply even in max-performance mode that you are using right now.
Even though you are maintaining (I guess) 1-1 between primary & standby instances, you can provide both primary instances in fal_server (like fal_server=string1,string2). See if that helps.
lastly, check if you are having simiar issue at other times as well that might be getting rectified automatically as expected.
col message for a80
col time for a20
select message, to_char(timestamp,'dd-mon-rr hh24:mi:ss') time
from v$dataguard_status
where severity in ('Error','Fatal')
order by timestamp;
Cheers.

Change of Source client in transport request

Hi Gurus,
I want to change source client of transport request
Since I want to transport request between clients of same server.
I did it using scc1
But when I want to make any changes to form which was included in that request it is saying
Request/task DEVK***** has invalid source client XXX
I am trying this in YYY client
Please provide solution
Thanks in advance for your efforts

Yogesh,
Does both the clients allow development in the server? Generally it should not be the case.
Does the client still exists in the server?
Here is a thread with replies for such an error message.
Re: regarding Client change for transport request
Check it,it may give you some lead.
K.Kiran.

PXE boot problem: guest VM DHCP request packets not able to reach DHCP server

Hi Gurus,
I'm wondering if anyone could help me with this problem. I wanted to install Linux on Oracle VMs using PXE. I set up a DHCP server and the OVM running RHEL6.4 box. The DHCP server worked fine since other PHYSICAL servers could get IPs from this DHCP server. However, DHCP requests from Oracle VMs was not able to reach the DHCP server. So I suspect this is a VM-specific issue.
If I type in "dhcp net0" on gPXE prompt on the OVS machine(sappire), I can see the requests were being sent from the OVS server (sapphire):
gPXE> dhcp net0
DHCP (net0 00:21:f6:00:00:00) .............................................Connection time out (0x4c106035)
Could not configure net0: Connection time out (0x4c106035)
gPXE>
[root@sapphire ~]# tcpdump -i any -n udp dst portrange 67-68
tcpdump: WARNING: Promiscuous mode not supported on the "any" device
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
20:47:25.606400 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:21:f6:00:00:00, length: 387
20:47:25.606549 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:21:f6:00:00:00, length: 387
20:47:25.606559 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:21:f6:00:00:00, length: 387
^C
12 packets captured
14 packets received by filter
0 packets dropped by kernel
But if I snoop the same on the RHEL6.4 server running DHCP server and OVM, no request can be seen:
[root@bluestone Desktop]# tcpdump -i any -n udp dst portrange 67-68
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
^C
0 packets captured
0 packets received by filter
0 packets dropped by kernel
OVS(sapphire) and OVM(bluestone) are located in the same subnet:
[root@bluestone network-scripts]# ifconfig -a
eth0      Link encap:Ethernet HWaddr 00:14:22:72:7C:27
          inet addr:192.168.2.48 Bcast:192.168.2.255 Mask:255.255.255.0
          inet6 addr: fe80::214:22ff:fe72:7c27/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:106795 errors:0 dropped:0 overruns:0 frame:0
          TX packets:122056 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:59173975 (56.4 MiB) TX bytes:25362955 (24.1 MiB)
[root@sapphire ~]# ifconfig -a
10049df2fc Link encap:Ethernet HWaddr 8A:C5:05:83:AF:C9
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:80 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:33200 (32.4 KiB) TX bytes:0 (0.0 b)
eth0      Link encap:Ethernet HWaddr 00:1A:64:64:DA:64
          inet addr:192.168.2.202 Bcast:192.168.2.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:37664 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38939 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4537897 (4.3 MiB) TX bytes:23127790 (22.0 MiB)
eth0:0    Link encap:Ethernet HWaddr 00:1A:64:64:DA:64
          inet addr:192.168.2.212 Bcast:192.168.2.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[root@sapphire ~]# brctl show
bridge name    bridge id        STP enabled    interfaces
10049df2fc        8000.8ac50583afc9    yes        tap7.0
                            tap7.1
                            vif7.0
                            vif7.1
I turned off iptables and SELinux on the DHCP server, the issue still remained.
Any help will be highly appriciaited.
Thanks in advance,
Alex

Hi,
- Do you install Oracle VM Server (OVS) on an emulated environment like Oracle VM VirtualBox ? if yes so you can't do it.
- Don't forget to configure the Virtual Machines Network and also to add this network to this Virtual Machine.
I hope this can help you
Best Regards

DHCP Requests over Nexus Issue

Hello all, this is my first post so please be gentle. I am having an issue with DHCP requests on our new server network.
First some background:
The new network consists of 2x Nexus 5548UP runing NX-OS 6.0. Behind the N5ks are multiple FEX types, but for the purpose of this issue I am using 2232TM-E FEXs. Each FEX is setup in an active-active scenario, therefore each individual FEX port belongs to each N5k which are configured identically. The N5k have a vPC peer-link setup between them and each FEX is also setup with vPC. The N5ks are uplinked to a pair of Catalyst 4500X switches that function as our "core" switches. From there, we have our old network which consists of a pair of Catalyst 4507R switches. We use tansfer networks between the N5k and 4500X and between the 4500X and 4507R runing EIGRP.
I have "Server A" on VLAN 100 connected to FEX 2232TM-E... "DHCP Server B" is on VLAN 11 connected to 4507R. I have "ip dhcp relay address x.x.x.x" configured on VLAN 100 to point to DHCP Server B on the old network. VLAN 100 is configured with HSRP (see running-config output below).
Onto the issue:
Server A is not getting a DHCP addesses assigned to him. The DHCP Server B gets the Discover packet from Server A and sends back the Offer... but the Offer either never makes it to Server A, or Server A Request never makes it back the DHCP Server B. I am not sure which is the case exactly.
I know it may be hard to picture the whole scenario I described above, but any pointers would be greatly appreciated. I'll be glad to dig up a good diagram of the network or provide more configs if necessary.
Additional info:
version 6.0(2)N1(2)
feature dhcp
service dhcp
ip dhcp relay
N5k #1:
interface Vlan100
   description server vlan
   no shutdown
   no ip redirects
   ip address 10.112.100.2/23
   hsrp 100
     authentication text hsrp-100
     preempt delay minimum 180
     priority 200
     ip 10.112.100.1
   ip dhcp relay address 172.26.20.40
N5k #2:
interface Vlan100
   description server vlan
   no shutdown
   no ip redirects
   ip address 10.112.100.3/23
   hsrp 100
     authentication text hsrp-100
     preempt delay minimum 180
     priority 150
     ip 10.112.100.1
   ip dhcp relay address 172.26.20.40
Thanks for any information!

Here are the results of a tracert from a server in VLAN 11 to the gateway for VLAN 100:
K:\>tracert -d 10.112.100.1
Tracing route to 10.112.100.1 over a maximum of 30 hops
   1    1 ms    1 ms    <1 ms 172.26.20.243
   2    <1 ms    7 ms    4 ms 10.112.96.105
   3    <1 ms    2 ms    2 ms 10.112.100.1
Trace complete.
Here is a tracert from a server in VLAN 100 (staticly addressed) to the gateway for VLAN 11:
K:\>tracert -d 172.26.20.1
Tracing route to 172.26.20.1 over a maximum of 30 hops
   1    <1 ms    2 ms    2 ms 10.112.100.3
   2    <1 ms    6 ms    7 ms 10.112.96.73
   3    1 ms    <1 ms    <1 ms 172.26.20.1
Trace complete.
Does this help? Or do you need more specific switch config information?
Also, I've attached a basic drawing of the network for reference. I've ommitted all the IP information, just a visual representation of the connectivity.

Looking for 802.11 rfc in regards to client roaming

Specifically, I'm looking for information in regards to the client determining when to roam. Any ideas on spec documents?
Thanks,
Raun

Raun,
Yes there are basic rules the vendors follow but those rules are still vendor specific.
Vendors usually depend on signal strength, delay, noise, packet loss...etc in order to decide when to roam. But each vendor takes different decision based on the equation they use to decide roaming.
For example, if there are two APs show good signal to a client while the clients is moving from one AP toward another, one client may decide to roam because there is a new signal that is stronger. Another client however may decide not to roam if the connection to the old AP is still OK although the new signal strength is higher.
If you want you need to look into vendors documents about how they decide roaming. some vendors allow you to modify roamign aggressiveness though:
Roaming Aggressiveness
This setting allows you to define how aggressively your Wi-Fi client roams to improve connection to an access point. Click Use default value to balance between not roaming and performance.
Lowest: Your wireless client will not roam. Only significant link quality degradation causes it to roam to another access point.
Medium-Low/Medium-High: Allow Roaming.
Medium: Balanced setting between not roaming and performance.
Highest: Your Wi-Fi client continuously tracks the link quality. If any degradation occurs, it tries to find and roam to a better access point.
Reference: http://www.intel.com/support/wireless/wlan/sb/CS-025393.htm
Another link may help: http://howto.techworld.com/mobile-wireless/438/make-your-wlan-roam-faster/
HTH
Amjad

LWAPP - client roaming - DHCP request

Similar Messages

Maybe you are looking for