DHCP via Hyper-V VM, Server2012r2 Hyper-V host, clients not getting IP address
You have to authorize a dhcp server as Britv8 says. That's the only way it'll start dishing out leases. That's standard for Windows DHCP server in an AD Domain.
Also there's 0 reason to mention Hyper-V here. The whole point of virtualization is to do hardware level abstraction.
I recently encountered this. Setup:
Initial setup of the system was at a different location from its final destination, with different network equipment (switches) between the two. No teaming is involved, however.
Set up the system at its final destination, with DHCP via a Hyper-V VM (Server2012r2), Server2012r2 Hyper-V host, physical clients on the lan were not getting IP address.
The physical server box has a 4-port Intel Gigabit ethernet card.
I moved the setup (Hyper-V Virtual Switch manager) so that the interface for the DHCP server VM was isntead using one of two built-in Broadcom adapters.
While this topic seemed promising,
http://community.spiceworks.com/topic/251317-hyper-v-vm-not-leasing-ip-s-dhcp
unfortunately, "fiddling about" was not what I was looking for as possible solution.
My notes for the resolution:
Hyper-V system running...
This topic first appeared in the Spiceworks Community
Similar Messages
-
DHCP: Some clients not getting IP address
Recently setup a new DHCP server on Mac OS X Server 10.5.8 running on an Xserve. We migrated from a Linux server.
The Xserve was originally just a file server. So the only services currently running are: AFP, DHCP, NFS, and SMB. No additional software is running.
The DHCP server ran just fine for the first couple weeks. But then we found some computers just stopped getting IP addresses from the DHCP server. Some were new computers introduced to the network. Some were laptops that had left and come back. However, the DHCP server is definitely still giving out IP addresses and renewing them for most new and existing computers. There have been five computers that have not gotten IP addresses so far, and that had been the case both on the wireless and on a wired connection. Two were PC's, one running Windows 7 and one running Windows XP with Lenovo's ThinkVantage software. The other three were different models of MacBook Pros.
For those five computers, we managed to get them working in two ways. One, we can select to use DHCP with a manual address. When we do that, it manages to pick up all the other information from the DHCP server like DNS and gateway. The second thing we can do is configure the DHCP server to supply a static IP address by providing it with the MAC address of these machines. When we do that, the computers receive the IP address from the DHCP server.
So I guess you could say the problem I'm experiencing is for a few computers the DHCP server seems to only be able to provide static addresses, but not dynamic ones with a lease time.
I have logging set to the highest for the DHCP server. Below is the first thing I noticed that keeps showing up. Sometimes it shows a different MAC address than the one below. None of the afflicted computers have that MAC address, though. I have not seen any other errors in the logs for the DHCP server.
Jan 24 12:09:47 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:09:47 fileserver bootpd[73839]: service time 0.000304 seconds
Jan 24 12:09:50 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:09:50 fileserver bootpd[73839]: service time 0.000280 seconds
Jan 24 12:09:54 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:09:54 fileserver bootpd[73839]: service time 0.000264 seconds
Jan 24 12:10:03 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:03 fileserver bootpd[73839]: service time 0.000265 seconds
Jan 24 12:10:11 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:11 fileserver bootpd[73839]: service time 0.000283 seconds
Jan 24 12:10:19 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:19 fileserver bootpd[73839]: service time 0.000291 seconds
Jan 24 12:10:28 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:28 fileserver bootpd[73839]: service time 0.000324 secondsRecently setup a new DHCP server on Mac OS X Server 10.5.8 running on an Xserve. We migrated from a Linux server.
The Xserve was originally just a file server. So the only services currently running are: AFP, DHCP, NFS, and SMB. No additional software is running.
The DHCP server ran just fine for the first couple weeks. But then we found some computers just stopped getting IP addresses from the DHCP server. Some were new computers introduced to the network. Some were laptops that had left and come back. However, the DHCP server is definitely still giving out IP addresses and renewing them for most new and existing computers. There have been five computers that have not gotten IP addresses so far, and that had been the case both on the wireless and on a wired connection. Two were PC's, one running Windows 7 and one running Windows XP with Lenovo's ThinkVantage software. The other three were different models of MacBook Pros.
For those five computers, we managed to get them working in two ways. One, we can select to use DHCP with a manual address. When we do that, it manages to pick up all the other information from the DHCP server like DNS and gateway. The second thing we can do is configure the DHCP server to supply a static IP address by providing it with the MAC address of these machines. When we do that, the computers receive the IP address from the DHCP server.
So I guess you could say the problem I'm experiencing is for a few computers the DHCP server seems to only be able to provide static addresses, but not dynamic ones with a lease time.
I have logging set to the highest for the DHCP server. Below is the first thing I noticed that keeps showing up. Sometimes it shows a different MAC address than the one below. None of the afflicted computers have that MAC address, though. I have not seen any other errors in the logs for the DHCP server.
Jan 24 12:09:47 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:09:47 fileserver bootpd[73839]: service time 0.000304 seconds
Jan 24 12:09:50 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:09:50 fileserver bootpd[73839]: service time 0.000280 seconds
Jan 24 12:09:54 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:09:54 fileserver bootpd[73839]: service time 0.000264 seconds
Jan 24 12:10:03 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:03 fileserver bootpd[73839]: service time 0.000265 seconds
Jan 24 12:10:11 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:11 fileserver bootpd[73839]: service time 0.000283 seconds
Jan 24 12:10:19 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:19 fileserver bootpd[73839]: service time 0.000291 seconds
Jan 24 12:10:28 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:28 fileserver bootpd[73839]: service time 0.000324 seconds -
WLC 5760 with internal DHCP server, clients no get IP address
Hi all,
I have 2 Cisco 5760 WLC (active-standby) IOS-Xe 03.03.03SE with one WLAN.
sh wlan summary
Number of WLANs: 1
WLAN Profile Name SSID VLAN Status
1 Invitados_ADSL Guest 905 UP
sh vlan
VLAN Name Status Ports
1 default active Te1/0/3, Te1/0/4, Te1/0/5, Te1/0/6, Te2/0/3
Te2/0/4, Te2/0/5, Te2/0/6
100 VLAN0100 active Te1/0/1, Te2/0/1
101 Planta_1 active
905 Internet active Te1/0/2, Te2/0/2
The DHCP server is internal.
Sometimes the clients no get IP address and the DHCP pool has IP addresses available.
The workaround done by me to solve the issue is “clear ip dhcp binding *”.
Some days later the problem appears again.
I see this bug with a similar problem:
NGWC blocks DHCP traffic if wireless broadcast disabled
CSCun88928
Description
Symptom:
Some clients set the BROADCAST flag on the DHCP Discover packet. This requires the DHCP server to reply with a broadcast.
In that case and if you are not using DHCP snooping on the 5760/3850, then the controller will block the return traffic unless you enable "wireless broadcast" which enables broadcast globally (and is thus not always desirable)
Conditions:
Seen on 3.3.2 IOS-XE
Workaround:
Use DHCP snooping with the "ip dhcp snooping wireless bootp-broadcast command"
OR
Enable "wireless broadcast" globally
My DHCP configuration is:
ip dhcp relay information trust-all
ip dhcp snooping vlan 905
ip dhcp snooping
ip dhcp excluded-address 172.16.0.1 172.16.0.19
ip dhcp excluded-address 172.16.1.250 172.16.1.254
ip dhcp pool Invitados
network 172.16.0.0 255.255.254.0
default-router 172.16.0.1
dns-server 212.66.160.2 212.49.128.65
lease 0 8
I see in Cisco documentation (http://www.cisco.com/en/US/docs/wireless/technology/5760_deploy/CT5760_Centralized_Configuration_eg.html) this configuration:
DHCP Snooping and Trust Configuration on CT5760
ip dhcp snooping vlan 100, 200
ip dhcp snooping wireless bootp-broadcast enable
ip dhcp snooping
interface TenGigabitEthernet1/0/1
description Connection to Core Switch
switchport trunk allowed vlan 100, 200
switchport mode trunk
ip dhcp relay information trusted ip dhcp snooping trust
interface Vlan100
description Client Vlan
ip dhcp relay information trusted
My question is,Do I have to add the command "ip dhcp snooping wireless bootp-broadcast enable" to solve the issue?
Thanks in advance.
Regards.
DYes, test it with the command you mentioned
ip dhcp snooping wireless bootp-broadcast enable
HTH
Rasika
**** Pls rate all useful responses ***** -
Static Clients Not Getting IP via DHCP -- Solution?
I set up some static maps to client machines on the LAN and thereafter was having some intermittent problems with their getting IP address. Some did, some didn't. I read this thread:
http://discussions.apple.com/thread.jspa?messageID=660758The solution posted in the quoted thread above works. Need to create an address group for 0.0.0.0 and open the port. Also, make sure that the static IPs are in the specified address range for DHCP handouts.
-
Clients not getting DHCP in VRF
Good morning -
We have devices in the global routing table (not in a VRF) getting DHCP addresses without issue. The SVI is configured as such:
interface Vlan2301
description BLUE
ip address 172.19.68.1 255.255.255.0
ip helper-address 10.4.16.222
interface Vlan2512
description RED
vrf forwarding RED
ip address 10.217.5.1 255.255.255.0
ip helper-address 10.4.16.222
Clients in BLUE are getting DHCP but clients in RED are not. If I statically assign an address I have connectivity and can reach the DHCP server (which is also DNS server; with a static IP in VLAN 2512 I can do name resolutions for example).
I am at a bit of a loss. Is there anything special I need to do for VRF IP HELPER-ADDRESS configuration? A capture on my firewall interface shows the DHCP server is trying to reply - it is like the helper-address is not forwarding the dhcp reply (or is not getting it)
11:11:52.915180 IP (tos 0x0, ttl 254, id 17478, offset 0, flags [none], proto UDP (17), length 337)
10.217.5.1.67 > 10.4.16.222.67: BOOTP/DHCP, Request from xx, length 309, hops 1, xid 0xb53a220c, Flags [none]
Gateway-IP 10.217.5.1
Client-Ethernet-Address xx [|bootp]
11:11:52.918761 IP (tos 0x0, ttl 124, id 28096, offset 0, flags [none], proto UDP (17), length 344)
10.4.16.222.67 > 10.217.5.1.67: BOOTP/DHCP, Reply, length 316, xid 0xb53a220c, Flags [none]
Your-IP 10.217.5.12
Server-IP 10.4.16.222
Gateway-IP 10.217.5.1
Client-Ethernet-Address xx [|bootp]
Any ideas?Good morning -
I have a pair of 6513 in a VS40 (VSS quad sup) connected via L3 MEC to a VSS pair of 4500X. Active to Active and Standby to Standby connected in a L3 MEC port-channel that is also a vnet trunk:
(Core)
interface Port-channel5
description Distribution Uplink
no switchport
vnet trunk
ip dhcp snooping limit rate 100
ip address 172.20.68.1 255.255.255.252
ip ospf message-digest-key 1 md5 XXX
spanning-tree guard root
(4500 Distribution)
interface Port-channel1
description Core Uplink
vnet trunk
ip arp inspection trust
ip address 172.20.68.2 255.255.255.252
ip ospf message-digest-key 1 md5 XXX
The interfaces are all using LACP mode Active inside the channels
On the 4500 we have a global routing table and a vrf. Both have helper addresses pointing to the DHCP server which is extranet service behind the 6513 Core.
interface Vlan2301
description Global Routing Table
ip address 172.19.68.1 255.255.255.0
ip helper-address 10.4.16.222
interface Vlan2512
description VRF
vrf forwarding RED
ip address 10.217.5.1 255.255.255.0
ip helper-address 10.4.16.222
DHCP for the Global Routing Table subnet works. DHCP for the VRF does not.
What is interesting is if we shut down the link that is connected to the standby 4500 (Te2/1/1) DHCP starts to work for the VRF.
Using <debug ip dhcp server packet detail> at the 4500 here is what I am seeing.
When both links are up and DHCP is failing for the VRF:
Mar 10 20:02:02.419: DHCPD: BOOTREQUEST from 0100.1a6b.3a56.13 forwarded to 10.4.16.222.
Mar 10 20:02:10.473: DHCPD: Reload workspace interface Vlan2512 tableid 3.
Mar 10 20:02:10.473: DHCPD: tableid for 10.217.5.1 on Vlan2512 is 3
Mar 10 20:02:10.474: DHCPD: client's VPN is RED.
Mar 10 20:02:10.474: DHCPD: using received relay info.
When I shut the Te2/1/1 link down in the L3 MEC at the 4500 DHCP starts to work for the VRF RED:
Mar 10 20:04:41.354: DHCPD: BOOTREQUEST from 0100.1a6b.3a56.13 forwarded to 10.4.16.222.
Mar 10 20:04:41.369: DHCPD: Reload workspace interface Port-channel1.2002 tableid 3.
Mar 10 20:04:41.369: DHCPD: tableid for 172.20.68.2 on Port-channel1.2002 is 3
Mar 10 20:04:41.369: DHCPD: client's VPN is .
Mar 10 20:04:41.369: DHCPD: forwarding BOOTREPLY to client 001a.6b3a.5613.
Mar 10 20:04:41.369: DHCPD: no option 125
Mar 10 20:04:41.369: DHCPD: broadcasting BOOTREPLY to client 001a.6b3a.5613.
Mar 10 20:04:41.369: DHCPD: no option 125
Mar 10 20:04:44.808: DHCPD: Reload workspace interface Vlan2512 tableid 3.
Mar 10 20:04:44.808: DHCPD: tableid for 10.217.5.1 on Vlan2512 is 3
Mar 10 20:04:44.808: DHCPD: client's VPN is RED.
It is like there is a bug that is treating the L3 MEC as a L2 MEC when both links are present; or the VNET trunk is not being processed correctly.
Has anyone else used a L3 MEC with a VRF and a DHCP helper with success? Is this a bug?
03.05.01.E is the code we are running on the 4500X-32(SPF+)
This is also with TAC but I thought I would share with the community in case anyone else has a similar environment or if Cisco experts want to comment. -
Cisco 891 not getting IP address with DHCP with latest IOS
Hi,
I have a few Cisco 891 routers that are configured as DHCP clients on the WAN interface.
For some reason when I boot the router with a late IOS, the router is not receiving an address.
It works just as expected with the older IOSes.
Any ideas of what changed?
This is how the interface is configured:
interface FastEthernet8
ip address dhcp
no ip redirects
no ip unreachables
no ip proxy-arp
duplex auto
speed auto
no cdp enable
This IOS does not work:
c890-universalk9-mz.154-3.M2.bin
While these do work:
c890-universalk9-mz.150-1.M7.bin
c890-universalk9-mz.151-2.T2.bin
c890-universalk9-mz.152-1.T1.bin
Doing a "show ip interface brief" shows that FastEthernet8 is unassigned with the affected IOS.
With the older IOSes there is an IP address.
I had to downgrade two routers due to this issue, and did not have plenty of time to troubleshoot.
Both of the routers are connected to DSL from the same ISP...
Anyone seen anything like this before?Add another one to the list.
I have a MacBookPro3,1 that connects to WIFI no problem. It used to connect to ethernet when I originally bought it, however I've been using WIFI exclusively for the past 2 years.
Recently I had a need to connect via ethernet and it wouldn't work at home (apple airport router). I next tried connecting via ethernet at a friends house using a linksys WRT54G, no dice either. I have the computer in the lab today (University Network) and I get the same error. 3 different locations, 3 different routers, all same problem. It used to connect to home and university networks ethernet right away.
IP address assigned is 169.xxx.xxx.xxx - subnet - 255.255.0.0
no other info. It's showing up as connecting to the network, but unable to communicate with DHCP. It does work if I enter all of the information in manually.
At first I thought I had messed something up in networking preferences as I tend to play around with things alot. However I did a complete system format, and fresh install of OSX Lion and I still have the same problem, without any of my meddling around to confuse things.
What gives? -
Clients not getting DHCP from external server
Hi,
I have a 4402 (version 7.0.235) working with 10 units of 1121 APs connected to it. The WLC is not configured to work in LAG mode. Physical portt #1 is connected to the Main Switch (trunk). I have 3 WLAN mapped to 3 Different VLAN and Everything (security and internal, external DHCP) is working swell...
Now- I have connected Physical port #2 directly to an ADSL Router (giga port), Configured Port 2 as untaggedwith the proper IP details.
I have configured this interface to receive DHCP from the ADSL Router and for some reason, Clients are not getting addresses.
When I assign a Static address to my laptop I get internet access and all is nice. I tried configuring The WLC internal DHCP server (instead of the ADSL router) and that didn't help. It seems like a DHCP problem but I dont understand the source of the problem of think of the solution.
When turning off the proxy settings I noticed that it helped. Is there anything to do with that? The problem was that after a while the other WLANs starting causing DHCP issues as well.
What is supposed to be configured? Any Expert is the House?
I attached a crappy drawing..Hi Scott,
Thanks for your answer.
So what you are basicly saying is that I have 2 choices: 1 - disable the Proxy option on the WLC and work with external DHCP servers (internal will not work when this is enabled). 2 - Enable the Proxy option and only work with the WLC internal DHCP.
I have installed many WLCs this way, having Different DHCP Servers (external and internal) for multiple WLANs.
What do you think may be different this time? The router that I am using isn't the most expencive but it is providing DHCP to other clients (wired client) with no problems.
Thanks!!! -
Phones not getting IP address via DHCP server on same VLAN
Hello....we have a new series of Cisco SF-200s and one new Cisco SF-300. All switches are operating in layer 2 mode currently. Let's say for all intents and purposes, all ports are in VLAN1....pretty much default setup. There is a fiber backbone between uplink ports...and it is working correctly it appears.
There is a DHCP server allocating addresses 192.168.0.60 thru 192.168.0.79. Subnet mask is 255.255.255.0.
PCs and laptops successfully receive an IP address and can access things.....such as surfing the internet. Tested that from multiple switches....all seems to work just fine.
However, it seems that some newly purchased phones (Digium models) simply will not acquire an IP address like the PCs and laptops do.
Pretty broad question....but just wondering.
Thanks!Hi Greg,
Might be interesting to goto the following sections of the GUI disable the discovery protocols;
1. Administration>Discovery -LLDP >properties
2. Administration>Discovery -CDP >Management interface
3 Smartports >Properties > Admministrative Auto Smartports is disabled.
the switches are real smart and may pre-empt what you are trying to achieve.
regards dave -
Mac OSX NOT GETTING IP ADDRESS BECAUSE OF THE DHCP(FINAL FIX)
You may get some errors when trying to connect to the wireless connection.
LIST OF PROBLEMS:
-Auto-Assigned IP with 255.255.0.0 Subnet Mask and a 169.x.x.x IPV4 Address
-Unable to renew the DHCP beacuse the DHCP doesn't send the IPV4 address to your iMac/MacBook
-No IP
FINAL FIX:
-Log to the Router Configuration page inserting the default gateway address in your browser bar(It should be 192.168.1.1 though my default gateway is 192.168.0.1.....nevermind).
-Go to DHCP tab and make sure that DHCP is ENABLED
-Go to Wireless Settings and set Channel to "1" and the Wireless mode to 802.11 bg(In some routers it's 802.11 bg mixed)instead of 802.11 bgn or 802.11 n.(IN SOME ROUTERS THERE'S ONLY .11 and not 802.11....that's the same s**t though!)
-Reboot your router
-Shut down your machine and unplug the power cables
-When done press once the power button
-Re-Plug the power cables and turn on your MacBook/iMac
-Go to Network Settings,Advanced settings,TCP/IP and set IPV4 address to DHCP
SOFTWARE FIX(FIREWALL CONFLICT):
-Disable ANY non-Apple firewall or network management application such as mDNS responder,etc..Great work, nice info, thanks!
-
Not getting IP from DHCP on 2950
Dear all,
access switch is connected to base switch and base switch is connected to DHCP server, however users are connected to access switch are not getting IP address. Hence i would like to know the solution from experts.
I remember there is a command in CATOS "set port host" by this way we can enhance port to get IP quickly..if there is any command similiar in IOS?
Your assistance will be highly appreciated.
Regards,
Khan.Khan,
The problem of users not getting IP from the DHCP usually happens when 'spanning-tree portfast' is not enabled on access ports. PCs don't wait long enough for DHCP responses and time out.
Can you make sure all the access ports, to which the users are connected to, have spanning tree portfast enabled.
HTH,
Sundar -
LAN was down ie Users are not getting ip from DHCP server after enabling DHCP snooping
Hi All ,
Enclosed file has network connectivity diagram.
1. L3 vlan's ie 2,3,4,5 and 6 are configured on ACC-CR1 and ACC-CR2.
2.Trunk is configured between Core switches ( CR1 and CR2) and access switches .VTP mode is transparent on all switches.L2 vlans are configured on all access switches.
3.DHCP is server is located at different location and is reachable over MPLS.
Without enabling dhcp snooping , users connected to access switches (Sw1,sw2,sw3 and Sw4 ) are getting ip address from DHCP server without any problem and everything is working fine.
But users connected to Sw3 and Sw4 are getting ip address from rouge DHCP server which is not pingable from any one of the switch.
So we have configured DHCP snooping for all vlan's on CR1 , CR2 , SW3 and SW4 and "trusted uplink ports" which are connected to WAN routers from CR1 and CR2 and also "trusted uplink ports " of Sw3 and Sw4 which are connected to CR1 and CR2.
As soon we have enabled DHCP snooping and trusted respective uplink ports , users are not getting ip address from remote DHCP server and even users connected to Sw1 and SW2 are facing same issue.
Note : DHCP snooping is not configured on SW1 and SW2.
Why users are not getting ip address from remote DHCP server as soon as we enabled dhcp snooping on Core switches and two access switches ie sw3 and sw4 ? what could have caused DHCP packets to be dropped ? Any idea would be appreciated .Hi,
as you say: " HSRP is configured between CR1 and CR2 and Vlans are active on CR1" does it mean there are L3 intrefaces configured in each VLAN on your CR switches and ip hepler-address pointing to the remote DHCP server is configured on each of them?
I know it's difficult in a productive environment but IMHO you need to find out where are the DHCP offers dropped.
Either by enabling DHCP debugging or by capturing packets via Wireshark, e.g.
Best regards,
Milan -
Wireless 2504,user not getting dhcp ip address
Hi i have configured wlc 2504 .in that i have configured two interfaces.one is guest, 2nd is internal user,
the pblm when user try to connect with that contain ssid user not getting ip address,
i have connected only one link between core to wlc on port 1.for guest interface i used port 4.but no physical link.
Please help thisThere are multiple ways how the clients can get their IP-address in a WLC deployment.
From the WLC-FAQ:
How does DHCP work with the WLC?
A. The WLC is designed to act as a DHCP relay agent to the external DHCP server and acts like a DHCP server to the client. This is the sequence of events that occurs:
Generally, WLAN is tied to an interface which is configured with a DHCP server.
When the WLC receives a DHCP request from the client on a WLAN, it relays the request to the DHCP server with its management IP address.
The WLC shows its Virtual IP address, which must be a non-routable address, usually configured as 1.1.1.1, as the DHCP server to the client.
The WLC forwards the DHCP reply from the DHCP server to the wireless client with its Virtual IP address.Note: You can also configure the WLC to act as a DHCP server. For more information on how to configure a WLC as a DHCP server, refer to the Configuring DHCP Scopes section of the document Cisco Wireless LAN Controller Configuration Guide Release 5.1.
If you want more in-depth information you should read "DHCP with the WLC":
http://www.cisco.com/en/US/partner/products/ps6366/products_tech_note09186a0080af5d13.shtml
Don't stop after you've improved your network! Improve the world by lending money to the working poor:
http://www.kiva.org/invitedby/karsteni -
DHCP server does not assign IP addresses SG500 firmware 1.3.5
good day collegues
has any of you come across the following issue:
my switch (after upgrading to the newest firmware 1.3.5) does not assign IP addresses to some of the hosts.
after a couple of hours I managed (do not even how) to force my switch to assign IP addresses only to some of the hosts.
still some of them cannot get the IP address and remain with "funny" IP address like i.e. 169.254.100.100
additional info
1. if I boot my switch with the previous version of firmware (1.3.0.6) everything is OK. all my hosts get correct IP addresess
2. the hosts which do not get IP address were perviously entered in stat host table - now removed, ARP cleared, etc, everything many many times rebooted.
I ran out of ideas, could you pleae give me some hints ?
the config below:
config-file-header
SG500
v1.3.5.58 / R750_NIK_1_35_647_358
CLI v1.0
set system mode router queues-mode 4
file SSD indicator encrypted
ssd-control-start
ssd config
ssd file passphrase control unrestricted
no ssd file integrity control
ssd-control-end zzz
no spanning-tree
vlan database
vlan 11,13-14
exit
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
no ip dhcp snooping verify
ip dhcp snooping information option allowed-untrusted
ip dhcp snooping vlan 11
ip dhcp snooping vlan 13
ip dhcp snooping vlan 14
ip arp inspection logging interval infinite
green-ethernet energy-detect
no eee enable
arp timeout 1
ip dhcp server
ip dhcp pool host q409
address 10.10.11.2 255.255.255.0 client-identifier 01:00:08:9b:ac:8f:92
default-router 10.10.11.254
dns-server 10.10.10.1
exit
ip dhcp pool host PCH-100
address 10.10.11.10 255.255.255.0 client-identifier 01:00:06:dc:41:ef:ef
default-router 10.10.11.254
dns-server 10.10.10.1
exit
ip dhcp pool host q209
address 10.10.13.3 255.255.255.0 client-identifier 01:00:08:9b:ac:72:ba
client-name q209
default-router 10.10.13.254
dns-server 8.8.8.8
exit
exit
ip dhcp pool network HOME
address low 10.10.11.1 high 10.10.11.254 255.255.255.0
lease infinite
default-router 10.10.11.254
dns-server 10.10.10.1
exit
ip dhcp pool network GUESTS
address low 10.10.14.1 high 10.10.14.254 255.255.255.0
lease infinite
netbios-node-type b-node
default-router 10.10.14.254
dns-server 10.10.10.1 62.233.233.233
exit
ip dhcp relay address 10.10.10.1
ip dhcp relay address 10.10.11.254
ip dhcp relay address 10.10.13.254
ip dhcp relay address 10.10.14.254
no boot host auto-config
no qos
qos advanced-mode trust dscp
qos wrr-queue wrtd
exit
hostname SG500
line telnet
exec-timeout 0
exit
logging buffered debugging
no logging file
aaa authentication login Telnet local
aaa authentication enable Telnet enable
aaa authentication dot1x default none
line telnet
login authentication Telnet
enable authentication Telnet
password 999 encrypted
exit
no passwords complexity enable
passwords aging 0
username 999 password encrypted 999 privilege 15
ip http timeout-policy 0 http-only
clock timezone " " 1
clock summer-time web recurring eu
clock source sntp
clock source browser
sntp unicast client enable
clock dhcp timezone
ip domain name 999
ip name-server 10.10.10.1 62.233.233.233 8.8.8.8
ip host 999 10.10.13.3
ip telnet server
no service mirror-configuration
no security-suite deny syn-fin
security-suite syn protection mode disabled
interface vlan 1
ip address 10.10.10.254 255.255.255.0
no ip address dhcp
interface vlan 11
name HOME
ip address 10.10.11.254 255.255.255.0
ip dhcp relay enable
interface vlan 13
name DMZ
ip address 10.10.13.254 255.255.255.0
ip dhcp relay enable
interface vlan 14
name GUESTS
ip address 10.10.14.254 255.255.255.0
ip dhcp relay enable
interface gigabitethernet1/10
description "(99) QNAP 409"
switchport trunk native vlan 11
exit
macro auto disabled
macro auto processing type host enabled
macro auto processing type ip_phone disabled
macro auto processing type ip_phone_desktop disabled
macro auto processing type router enabled
mac address-table aging-time 10
ip default-gateway 10.10.10.1
snmp-server set 999 permitHi Andbor, please make a backup config of your file, factory reset the switch.
After this, manually configure a DHCP scope without any other configuration.
Just something simple like this
ip dhcp pool network GUESTS
address low 10.10.14.1 high 10.10.14.254 255.255.255.0
lease infinite
netbios-node-type b-node
default-router 10.10.14.254
dns-server 10.10.10.1 62.233.233.233
Verify your machine receive IP address with no other configuration.
In some ways, I'm afraid some of your connections black listed due to the arp inspection.
-Tom
Please mark answered for helpful posts -
Hi, I have a strange issue with DHCP.
I have a lab environment on a single Hyper-v 2012 Server. AD, DNS & DHCP exist on a single virtual machine, I have a flat network 192.168.1.x, all VM's are on this network. I have authorised DHCP and Setup the scope.
A VM has a legacy adaptor, the legacy nic is configured in the boot order as the first device.
When I boot the machine I do not get a DHCP address, however when the OS boots the Legacy NIC then gets a DHCP address??
I need to use a legacy NIC as I need to PXE boot the VM, however I should get an IP address at boot time, which I don't get.
I have run Wireshark on the DHCP server, I can see the legacy NIC do a "DHCP Discover and the DHCP Server respond with a DHCP Offer" however all communication ends there. I have disable all firewalls and I see no reason for this not to work.
I have done tis before with no issues but I am unable to get this to work on this server!!!!!Hi
According to your description , it is recommended to make sure or do :
In your environment , there is no any other valid DHCP, BOOTP or proxy DHCP offers.
Make sure if the DHCP server is overload.
So suggest to test that creating a new “internal virtual switch” and change the settings of VM which provide DHCP service to connect to the new “virtual switch”.
Then create a new VM use legacy NIC also connect to the new “internal virtual switch” and try to PXE Boot.
Hope this helps.
Best Regards
Elton ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Hi,
When trying to initiate hyper-v replication from the main server i'm getting this error in the event logs.
Hyper-V failed to enable replication for virtual machine 'RECADemo': A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. (0x800B0101). (Virtual Machine ID 561591B6-567C-...)--I'm using certificate based auth and cert is installed/recognized on both machines.Please help.Thanks,Jaffer
JafHi,
This error occurs because the Microsoft Certificate Trust List Publisher certificate expired. A copy of the CTL with an expired signing certificate exists in the CryptnetUrlCache
folder. Please try to renew the Trust List Publisher certificate.
The related KB:
Event ID 4107 or Event ID 11 is logged in the Application log in Windows and in Windows Server
http://support.microsoft.com/kb/2328240
How to Renew the Site Server Signing Certificate (Microsoft Certificate Services)
http://blogs.technet.com/b/configmgrteam/archive/2009/02/11/how-to-renew-the-site-server-signing-certificate-microsoft-certificate-services.aspx
Manage Trusted Publishers
http://technet.microsoft.com/en-us/library/cc733026.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Maybe you are looking for
-
I need help with automator work flows
im having troube adding songs to my itunes with autmator i ke getting error mesaage 1752 ...anyine know how i can resolve this issue ?
-
How to consume Web Service in ABAP WebDynpro
Hi I want to know the entire details about how to consume Web Service in WebDynpro application. regards Piyush
-
Error: Gray Menu Options? PS CC
I seem to be having an issue with Photoshop CC 2014. I'm using Windows 8.1 on an HP 110-017cb. The issue is, I was having problems using the Blending Options when working on a New Document. I solved that by resetting some presets, but now some option
-
Reinstall Adobe Acrobat tool bar in Chrome
I used chrome everyday to surf online. Last week, Adobe Acrobat XI failed to convert some webpages into pdf document, I therefore remove the extension. Could some person advise me how to reinstall the tool bar again so as to bring back the functions
-
Can't find a store with retina, what about the non retina?
I had decided to get a retina MacBook Pro earlier, but I have grown tired of never finding them in the stores. Now I am wondering if the non retina would be the best way to go. Any opinions would be appreciated.