Manually clearing DHCP leases on NAC, CAM, CAS implementation?

Hello,
I have a NAC implementation consisting of CAM 4.6.1, CAS 4.6.1 and NGS 2.0.3. This was implemented to replace the defunct Cisco BBSM.
This is used exclusively for handling guest access, primarily wireless. It is in-line, passing all guest traffic. The CAS currently handles seven guest subnets varying in size from /24 to /22. Some subnets utilize the NAC's web login and some utilize WLC's web-auth. The CAS also provides all DHCP for these subnets.
My 1st question: Is there a way to manually clear DHCP leases either through GUI or CLI?
Thanks!

Hello,
Please note that in VG mode both CAS interfaces have the same IP with VLAN mapping enabled in CAS.
There was a very good Power Point Presentation on Cisco website by Alok Agrawal once upon the time. Don't have a link, but it was cisco NAc Appliance Chalktalk series, maybe you can still find it.
hope it helps a little bit
Dorota

Similar Messages

NAC CAM/CAS Temporary Certificate expired

Hello Guys,
I have a high availability pairs of NAC(CAM/CAS), Last 3 months I generate temporary certificate and now it is expired.
Do I need to generate again a new temporary certificate and delete the old one? Is there any certificate that can give me lifetime certificate?

Hi,
Yes, 4.8 has been out for a bit now. Download it here: http://bit.ly/dwaXlc
Release notes, including the new features, the bug fixes and the upgrade instructions for 4.8 are here: http://bit.ly/9inkeW
HTH,
Faisal
If you find this post helpful, please rate so others can find the answer easily

Clear dhcp lease in WLC internal server WLC 6.0.199

Hi,
How to clear dhcp lease in WLC 6.0.199 from the IP leased from internal server?
merci,
arun

In 7.0 You can use the cli command (might be there in later 6.0 but I can't test ATM)
Config dhcp clear-lease then either the up address or all
Config dhcp clear-lease 192.168.100.0
Or
Config dhcp clear-lease all
If not the only way to clear the leases is a reboot of the WLC.
Steve
Sent from Cisco Technical Support iPhone App

Installing and configuring NAC/CAM/CAS/COLLECTOR

Hi everybody,
I have been new to this community and I just joined this.
I need some help regarding CISCO Nac profiler.
I have 3 cisco nac appliances as below.
1. 3355
2. 3315
3. 3315.
My question is that when I power on these devices CAS is pre-configured in it but I have to install profiler, CAS, CAM.
Got 5 hardware total of cisco which are as follows.
1. CISCO NAC 3355.
2. CISCO NAC 3315
3. CISCO NAC 3315.
4. CISCO Router.
5. CISCO Switch.
I have to installed these devices into a network.
But the confusion is that whom to make profiler server, CAM, CAS and Collector.
Please help me on this if you have a simple document describing about NAC profiler server, NAC profiler collector, CAS, CAM and how to configure these devices.
Please help me on this its urgent

Abuzar,
Welcome.
As for your questions, you can install the Profiler, CAM and CAS on any of these devices. Which ever device you make the CAS can act as a collector also. I would suggest making the biggest box you have (3355) the Profiler, and putting CAM/CAS on the 3315s.
As for a simple document, I'm afraid no such thing exists. NAC installations are complex by nature and you really have to have a very good idea of what you're looking to accomplish before you even touch the first piece of hardware.
HTH,
Faisal

Clear dhcp bindings (leases) at WLC

Hello all,
could anybody tell me how I could clear the dhcp bindings at a WLAN-Controller 7.0? I looked at 'configuration guide' and 'command reference', but I found nothing.
Thanks and regards
Holger

Hi Holger,
Thanks for the response!!
if you are running 7.0 and above then its possible.. just now checked the same on my WLC.. the command is..
(WiSM-slot2-2) >config dhcp clear-lease ?
Enter the IP address.
all Clear all Leases.
let me know how this works out for you!!
Regards
Surendra

Self-assigned IP after trying to renew DHCP lease for former network

Hi all,
MacBook Pro 15" purchased in Februrary 2008, currently running 10.5.5, up-to-date with patches as of yesterday, 10/20/2008.
For a few weeks now, I've been consistently unable to connect to wireless networks (secured or unsecured, public or private) after changing networks (i.e. going from home to a coffee shop).
I have control over my home network router, and its logs show that upon connecting to the network, OS X tries to renew a DHCP lease for the previous network it was on. Upon receiving the "bad network" DHCP reply, instead of releasing the lease and obtaining a new one, the AirPort interface is immediately assigned an IPV4LL address (from 169.254.0.0/16) and no combination of changing network settings, changing AirPort settings, or rebooting will eliminate the old DHCP lease.
The end result is that my MBP is entirely nonfunctional on some wireless networks that other clients (both Windows and Mac) seem to have no trouble accessing. The problem is quite annoying because I can't connect to access points that (previously) worked fine and whose configurations haven't changed.
In any case where this problem occurs, an old DHCP lease for a different network (10.0.0.0/8 when trying to get on 192.168.0.0/24 or vice versa) is present, so I strongly suspect a DHCP problem. In all cases, I have perfect connectivity to the access point itself, so problems with the wireless connection parameters (including encryption), or those troublesome problems with 802.11b/g/n interoperation seem highly unlikely.
One of two things would help me:
1) Please tell me how to clear the DHCP lease cache. Deleting files from /var/db/dhcpclient/leases does nothing (they appear again upon reboot, identical save for timestamps even after changing network environments, so the cache must be read at boot time and written at shutdown). Selecting "Renew DHCP lease" from the "TCP/IP" tab in the advanced network settings merely attempts to renew the existing lease (for an invalid IP address); it does not appear to release invalid leases.
2) If this is really how the DHCP client is behaving, change the DHCP client so that upon receiving the "Bad network" response, it releases (or simply abandons) the lease and obtains a new one, rather than immediately assigning an IPV4LL address to the AirPort interface.
Additionally, is there any documentation on the Apple DHCP client? Under Linux, I could alter dhcpcd parameters to diagnose things like this. I could find no documentation about the Apple DHCP client outside of Mac Help, which wasn't really any help in this case.
Finally, I do not suspect that this is an instance of the problem discussed in http://discussions.apple.com/thread.jspa?threadID=1352518&tstart=0 as my connection is rock-solid if it can get an IP address when it connects. I've never even seen it hiccup.
Thanks,
Matt Z.

I have had wireless problems intermittently for a year, and seriously for 6 weeks. Apple denied the issue and was no help in spite of many tens of thousands of people on their own discussions complaining. I found a post suggesting a couple of things which fixed the problem. I don't know if both are necessary, but the first by itself does not solve the problem.
Lock the channel of your router to channel 1, apparently Apple and 802.11n don't play well together on higher channels. When this becomes a standard this will be resolved I hope.
Open your network preferences, select 'airport' and advanced. Delete unused networks. Select your network.
Open TCP/IP and write down all the settings, configure iPv4 manually. Enter the settings manually. Turn off IpV6.
Open DNS and write down your DNS server. Delete it and re-enter it manually.
This has worked on 2 macbooks and an iMac for the last 3 weeks with no network drops.
Joe Shea
Philadelphia

How do I revoke a DHCP lease in the 10.8.4 server app?

Hello Everyone,
I have some devices (security cameras) that have successfully requested a DHCP lease. Since then I went ahead and manually created a static reservation for them with a MAC hardware address in the DHCP. For whatever reason they are not switching over to the reserved address. The leases were originally for 1 day. It has been 5 days now. After the first day I switched my lease time to 1 hour. I have done everything short of leaving the devices off for 24 hours.
In Lion server, I could revoke the lease via the gui. No such luck now. My call to Applecare resulted in a "there is no way in 10.8.4 to do this". They said it would switch to the new reserved address after the initial lease period timed out, so I'm hoping the representative was wrong twice. They mentioned a complete lease wipe, but couldn't say if this would cause me to lose my list of reserved static addresses, which isn't an option.
It seems crazy that such a basic feature wouldn't make it into this release of the DHCP service. Any help would be greatly appreciated!

Are there any DHCP queries from the cameras? Check the DHCP server log via Console.app or Server.app (or Terminal.app) for details. (I don't know the 10.8 path to the DHCP logs offhand.)
According to a FAQ over at the Vivotek site, the following is the setup sequence for various recent cameras; the boxes start up in the "I don't have an IP address" self-allocated address block oddly enough, and apparently don't ask for a DHCP address? (You may well be aware of all of this, but this is the block that DHCP clients use when they first communicate with DHCP servers.)
If you are using our new product such as IP7138 / IP7139 / FD7131 / VS7100… etc, no matter your network environment is what, you can always find the camera by Installation Wizard II with the IP address 169.254.x.y.
And then, please double click the camera found by Installation Wizard II or directly type the IP address to your Internet Explorer URL box to access your camera (you do not need to change your PC's IP address). After access your camera, please go to "Network" page to configure proper network settings.
See if the devices are available via mDNS, as well; download the Bonjour Browser and have a look around your LAN. (If you're very lucky, the cameras might be visible and chatting on mDNS.)
Might also try resetting one of the cameras back to factory defaults, and seeing if you can get them to re-ask the DHCP server.
(I've had issues with some HP printers and DHCP clients and IP address assignment, but that's fodder for another discussion. And I also wouldn't rule out a rogue DHCP server, either. I've seen all sorts of unexpected stuff connected to networks over the years...)

Cisco 867VAE drops connection on DHCP lease timeout

Hey!
We have a very annoying problem on our hands. I'm no IOS expert, but I make do.
We've got a Telia DSL connection that has a 20 minute DHCP lease timer. Every 20 minutes when it shakes hand again, the connection drops for about 5 seconds. This because the Cisco thinks that administratively shutting down the interface is a good idea....
How do I stop this behavior? I've tried manually setting <ip dhcp client lease 1 0 0> (for 1 day lease) but it completely disregards that.
Best would obviously be to stop it shutting down the interface every time, but worst case scenario I'll take a solution with a longer DHCP lease since the address rarely changes.
<snip from log>
*Aug 1 01:44:43.514 PCTime: %DHCP-6-ADDRESS_ASSIGN: Interface ATM0.1 assigned DHCP address 81.230.xxx.xx, mask 255.255.255.0, hostname elsa
*Aug 1 02:04:48.498 PCTime: %DHCP-5-RESTART: Interface ATM0.1 is being restarted by DHCP
*Aug 1 02:04:56.106 PCTime: %DHCP-6-ADDRESS_ASSIGN: Interface ATM0.1 assigned DHCP address 81.230.xxx.xx, mask 255.255.255.0, hostname elsa
*Aug 1 02:25:01.050 PCTime: %DHCP-5-RESTART: Interface ATM0.1 is being restarted by DHCP
</snip>
It's running firmware c860vae-ipbasek9-mz.153-2
I'm attaching the current running-config as well.
Thank you in advance!
Best Regards
Daniel

I'm sorry for not reporting in. The case is closed at Cisco and they simply couldn't do anything. The router does, according to the debug logs, send dhcp renew requests, but the ISP doesn't reply to them. If they get lost on the way, or if there's an incompatability with the ISP, I dunno. I heavily doubt it, since Telia (Swedish ISP) used Cisco gear for pretty much everything.
Also, Telia will not reply to anything like this, since they don't support equipment they don't supply.
So I'm completely at a loss, and will remain there until I stumble across something.
I've received an 887M router though, which I'm gonna test. But I'm currently stuck with the fact that it's not supported anymore, and therefor I can't seem to download new IOS software (it uses a very old one).
This is the last reply I got before they closed my case:
*Aug 27 14:56:15.751 PCTime: DHCP Ack Message
*Aug 27 14:56:15.751 PCTime: DHCP: Lease Seconds: 1200
*Aug 27 14:56:15.751 PCTime: DHCP: Server ID Option: 213.66.241.86
*Aug 27 14:56:18.751 PCTime: DHCPD: IP address change on interface ATM0.1
*Aug 27 14:56:18.751 PCTime: DHCPD: IP address change on interface ATM0.1
*Aug 27 14:56:18.751 PCTime: DHCP: Releasing ipl options:
*Aug 27 14:56:18.751 PCTime: DHCP: Applying DHCP options:
*Aug 27 14:56:18.751 PCTime:   Setting default_gateway to 81.230.121.65
*Aug 27 14:56:18.751 PCTime:   Adding default route 81.230.121.65
*Aug 27 14:56:19.751 PCTime:   Adding route to DHCP server 213.66.241.86 via ATM0.1 81.230.121.65
*Aug 27 14:56:19.751 PCTime:   Adding DNS server address 195.67.199.39
*Aug 27 14:56:19.751 PCTime:   Adding DNS server address 195.67.199.40
*Aug 27 14:56:19.751 PCTime: DHCP: Sending notification of ASSIGNMENT:
*Aug 27 14:56:19.751 PCTime:   Address 81.230.121.83 mask 255.255.255.192
*Aug 27 14:56:19.751 PCTime: DHCP Client Pooling: ***Allocated IP address: 81.230.121.83
*Aug 27 14:56:19.803 PCTime: Allocated IP address = 81.230.121.83 255.255.255.192
*Aug 27 14:56:19.803 PCTime: %DHCP-6-ADDRESS_ASSIGN: Interface ATM0.1 assigned DHCP address 81.230.121.83, mask 255.255.255.192, hostname elsa
*Aug 27 14:56:25.751 PCTime: DHCP: Client socket is closed
*Aug 27 15:06:18.759 PCTime: DHCP: Client socket is opened
*Aug 27 15:06:19.759 PCTime: DHCP: QScan: Bound..T1 fired..Renewing
*Aug 27 15:06:19.759 PCTime: DHCP: SRequest attempt # 1 for entry:
*Aug 27 15:06:19.759 PCTime: Temp IP addr: 81.230.121.83 for peer on Interface: ATM0.1
*Aug 27 15:06:19.759 PCTime: Temp sub net mask: 255.255.255.192
*Aug 27 15:06:19.759 PCTime:    DHCP Lease server: 213.66.241.86, state: 7 Renewing
*Aug 27 15:06:19.759 PCTime:    DHCP transaction id: 914
*Aug 27 15:06:19.759 PCTime:    Lease: 1200 secs, Renewal: 600 secs, Rebind: 1050 secs
*Aug 27 15:06:19.759 PCTime: Temp default-gateway addr: 81.230.121.65
*Aug 27 15:06:19.759 PCTime:    Next timer fires after: 00:03:46
*Aug 27 15:06:19.759 PCTime:    Retry count: 1   Client-ID: cisco-d48c.b524.7b17-AT0.1
*Aug 27 15:06:19.759 PCTime:    Client-ID hex dump: 636973636F2D643438632E623532342E
*Aug 27 15:06:19.759 PCTime:                        376231372D4154302E31
*Aug 27 15:06:19.759 PCTime:    Hostname: elsa
*Aug 27 15:06:19.759 PCTime: DHCP: SRequest - ciaddr: 81.230.121.83
*Aug 27 15:06:19.759 PCTime: DHCP: SRequest: 293 bytes
*Aug 27 15:06:19.759 PCTime: DHCP: SRequest: 293 bytes
*Aug 27 15:06:30.759 PCTime: DHCP: Client socket is closed
*Aug 27 15:10:04.759 PCTime: DHCP: Client socket is opened
*Aug 27 15:10:05.759 PCTime: DHCP: QScan: Renewal..Retrying
*Aug 27 15:10:05.759 PCTime: DHCP: SRequest attempt # 2 for entry:
*Aug 27 15:10:05.759 PCTime: Temp IP addr: 81.230.121.83 for peer on Interface: ATM0.1
*Aug 27 15:10:05.759 PCTime: Temp sub net mask: 255.255.255.192
*Aug 27 15:10:05.759 PCTime:    DHCP Lease server: 213.66.241.86, state: 7 Renewing
*Aug 27 15:10:05.759 PCTime:    DHCP transaction id: 914
*Aug 27 15:10:05.759 PCTime:    Lease: 1200 secs, Renewal: 600 secs, Rebind: 1050 secs
*Aug 27 15:10:05.759 PCTime: Temp default-gateway addr: 81.230.121.65
*Aug 27 15:10:05.759 PCTime:    Next timer fires after: 00:01:53
*Aug 27 15:10:05.759 PCTime:    Retry count: 2   Client-ID: cisco-d48c.b524.7b17-AT0.1
*Aug 27 15:10:05.759 PCTime:    Client-ID hex dump: 636973636F2D643438632E623532342E
*Aug 27 15:10:05.759 PCTime:                        376231372D4154302E31
*Aug 27 15:10:05.759 PCTime:    Hostname: elsa
*Aug 27 15:10:05.759 PCTime: DHCP: SRequest - ciaddr: 81.230.121.83
*Aug 27 15:10:05.759 PCTime: DHCP: SRequest: 293 bytes
*Aug 27 15:10:05.759 PCTime: DHCP: SRequest: 293 bytes
*Aug 27 15:10:16.759 PCTime: DHCP: Client socket is closed
*Aug 27 15:11:57.759 PCTime: DHCP: Client socket is opened
*Aug 27 15:11:58.759 PCTime: DHCP: QScan: Renewal..Retrying
*Aug 27 15:11:58.759 PCTime: DHCP: SRequest attempt # 3 for entry:
As pointed to you in my previous mails renews/packets are being sent and as router is not getting back any reply, lease is timing out and that’s the reason why the interface is getting flapped. You need to find with ISP why the renews and rebind packets are not responded to by Providers DHCP server.
Hope this clarifies your query.
Thanks and regards,
Lijesh

How do I fix that I constantly having to renew dhcp lease?

I am constantly having to renew my dhcp lease. Can anyone help resolve this issue?

I was having this problem the other night after I finished doing a massive upgrade to our Home Network (New Router, Modem, Cabling, Etc)
I had to reset my DHCP lease every few minutes, in the end I found it was the IP Address kept setting itself to other items on the Network, I have some items coming through on wired (ethernet) and some were checking in on WiFi (Airport Extreme) the Mac Mini would grab an IP address that it thought was available and then we would have a clash.
I was watching the items on my Routers Attached devices screen, The Mac Mini would show up on the page with its new address (after hitting the DHCP Renewal button) then something elese would check in with that exisiting IP Address, clash and the Mac Mini would need the DHCP lease renewed again.
I'll be the first to admit my Networking knowledge is limited (and I'm learning more all the Time) but I simply went into the preferences panel and set the IP address manually.
1. I went into preferences and selected Network
2. Set Configure IPV4 to: using DHCP with manual address
Now it helped I had my NetGear Routers "Attached devices" Page open here so I could see the address of everything else on my network (I went and switched everything on that was web connected so it would be logged in and running on the network) I looked at the last digit or 2 of every item on my network and then set my new IP address.
3. To ensure I wouldn't have any more clashes I set my new IP address far away from the the others* your only changing the last digit or 2 of the IP address, so in the case of my Mac Mini it went from xxx.xxx.02 to xxx.xxx.0.52 (note the x's are normally your IP address numbers)
*I originally set it to xxx.xxx.09 but I since found the TV had that IP address (The one thing I forgot to check the previous night) so I this is when I decided to set it far away from the rest of the bunch by setting it to .52 (Note: 52 was just the 1st number to pop into my head)
Now that was over a week ago and since then I have had no more issues on my Network, so far everything is running smooth and fast.
This is probably not the ideal way to fix this issue, but so far it is working, hopefully someone with quality networking experience can chime in with a more permanent solution.

Release 4.9 CAM/CAS/Agent Compatibility

Hi All,
I have a NAC platfom with CAM/CAS - 4.7.2 and Agents - Windows - 4.7.2.10 and MAC - 4.7.2.507.
I want to upgrade to NAC 4.9 on the CAM/CAS and but want to know if CAM/CAS 4.9 will be compatible with agents Win/MAC 4.7.2.10/4.7.2.507 pending when I upgrade the agents on the Client machines. For certain reasons we do not want to do the Agent upgrade yet.
I have gone through the NAC 4.9 CAM/CAS/Agent Compatibility Matrix in the NAC 4.9 release notes but I am still not clear on this.
Any answer will be highly appreciated.
Regards,

Hello All,
Ok the CAM running 4.9 will support the NAC agent 4.7.2 no problem.
What will happen is that the cam will upgrade the agent but what you can do is download the agent from cisco.com
And upload it to the cam by going to Clean access > Clean Access agent distribution and upload the file and then also make sure to uncheck the option that says and current nac agent is a mandatory upgrade.

Does anyone else have to renew their DHCP Lease every 30 seconds when using the internet?

Everytime I want to use the internet for surfing the web or browsing iTunes etc I have to go into System Preferences and navigate through to a button that says "Renew DHCP Lease". If watching catch-up TV online I have to click this button every 30 seconds or so because the programme freezes, and if I'm surfing the web or browsing iTunes I have to click it every time I want to update the content of the page. Does anybody know what my problem might be?

This Fix has got things working for me.
I have reprinted this response from another thread I have made (Repost) A number of people were asking me about my fix, so I have expanded my response to hopefully offer a little more clarity.
I was having this problem the other night after I finished doing a massive upgrade to our Home Network (New Router, Modem, Cabling, Etc)
I had to reset my DHCP lease every few minutes, in the end I found Mac Mini's IP Address kept setting itself to other items on the Network, I have some items connected on wired (ethernet) and some were connected on WiFi (Airport Extreme) after clicking the DHCP Lease Renew the Mac Mini would grab an IP address that it thought was available but then another item on my network would "check in" then we would have a clash, The Mac Mini was grabbing what it thought was an available IP address, the DHCP Renew button was not setting the Mac Mini's IP number far enough away to stop the clash.
I was watching the items on my Routers Attached devices screen, The Mac Mini would show up on the page with its new address (after hitting the DHCP Renewal button) then something else would check in with that exisiting IP Address, clash and the Mac Mini would need it's DHCP lease renewed again.
My Network consists of:
- Mac Mini (Wired)
- Acer Laptop (Wired)
- PS3 (1) (wired)
- Apple TV (wired)
- Airport Extreme (wired and looking ater WiFi duties throughout the house)
- PS3 (2) (WiFi)
- TV (WiFi)
- iPad (WiFi)
- Nexus 7 (WiFi)
- Printer (WiFi)
I'll be the first to admit my Networking knowledge is limited (and I'm learning more all the Time) but I simply went into the preferences panel and set the IP address manually.
1. I went into Preferences and selected Network
2. Set Configure IPV4 to: using DHCP with manual address
Now it helped I had my NetGear Routers "Attached devices" Page open here so I could see the address of everything else on my network (I went and switched everything on that was web connected so it would be logged in and running on the network) I looked at the last digit or 2 of every item on my network and then set my new IP address.
3. To ensure I wouldn't have any more clashes I set my new IP address far away from the the others* your only changing the last digit or 2 of the IP address, so in the case of my Mac Mini it went from
xxx.xxx.02 to xxx.xxx.0.52 (note the x's are normally your IP address numbers)
*I originally set it to xxx.xxx.09 but I since found the TV had that IP address (The one thing I forgot to check the previous night) so I this is when I decided to set it far away from the rest of the bunch by setting it to .52 (No specific reason for 52, that was just the 1st number to pop into my head)
Now that was over a week ago and since then I have had no more issues on my Network, so far everything is running smooth and fast. (It has now been over 3 weeks since I posted this, and everything is still working perfectly, I suggested this solution to 2 friends having the same issue and it also fixed there problems as well)
I'm not saying this is the be all and end all to the problem, there must be a more permanent solution out there, but this is working for me so far.

GR?IR Manual Clearing

Dear expert,
We want to clear of some the GR/IR that has differences, because there will be no subsequent delivery or invoices for this purchasea order.
I run the following steps:
1. Run MR11 : System automatically create a posting that will result in zero balance GR/IR for the purchase order and line item.
Eg: Before I run the MR11:
GR/IR credit balance : -1000 (from goods receipt) PO: 8000005002 Line Item: 10
GR/IR debit balance : 950 (from invoice)                PO: 8000005002 Line Item: 10
Since there will be no further invoice for the remaining qty, we need to manually clear the above GR/IR.
I run MR11: system post the following:
Dr Purchase PRice Variance : 50
    CR GR/IR                        : -50            PO: 8000005002 Line Item: 10
Now the GR/IR balance for the PO: 8000005002 Line Item: 10 is net off to zero.
However the status of this GR/IR is still open.
2. Because the status is still open, I run the F.13 automatic clearing. However system didn't clear the above PO: 8000005002 Line Item: 10 GR/IR.
Is there any misssing steps or configuration? How to enable the clearing of GR/IR for above cases?
Thank you very much in advance for your kind assisstance

Hi Rama, Thks for the reply
I test the F-03 to manually clear the GR/IR, but system prevents manual clearing of GR/IR. Here is the error message: "GR/IR clearing account cannot be manually cleared"
kind rgds,
Dahlia Tan

MDT 2013 - A Connection to the deployment share could not be made - DHCP Lease was not obtained

First, let me give you some context:
Framework: MDT 2013 with MS SDK 7.1
Task Sequence: Standard Client TS with sysprep and capture.
Target workstation (build workstation): VM Guest on ESX 5.5 host, 8 vCPU, 8GB RAM, LSI Logic SAS Controller, E1000 NIC, SSD DAS
Behavior: The VM loads and installs the OS fine in PE, VM boots into OS successfully and resumes the TS, after the first system reboot, the error message occurs and it reads:
A connection to the deployment share (\\*********\DeploymentShare$) could not be made. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection. Retry:...... Cancel:.....
While observing this error, I didn't notice the NIC hadn't completely initialized and obtained an IP yet (network adapter icon in systray), additionally hitting retry after the NIC was initialized resumed the TS.
This behavior reoccurs with several subsequent reboots until a few more applications (Citrix Receiver, VMware Tools) with services are installed which seem to then slow the system boot-up time and then allows the TS to start after the NIC has initialized.
From several posts I've read on this forum, this particular behavior was alleviated by a "wait for IP lease" mechanism built into the TS engine which was introduced in MDT 2010 SP1, I wasn't able to find any other confirmation whether
this mechanism is still in effect with MDT 2013. Another point worth mentioning from several other posts I was able to find is that this behavior appears to manifested itself on target workstations with SSDs, which would somewhat explain the faster
TS load time vs waiting for an IP lease. I've also tried to replicate this behavior in a non-SSD and low-performance VM environment and I wasn't able to replicate it.
My question: Does anyone else have experienced this behavior with MDT 2013 and if so, how did you resolve it? Or is this a bug?

I have this issue intermittently as well. For us, it coincided with the deployment of IP phones, which meant PoE switches all around. However, the problem persisted even after we turned off PoE to the ethernet ports from which we normally PXE
boot.
As this issue has been intermittent, I've backburnered it. When it does happen, I just wait for the lease to arrive then rerun the wizard.
Thanks for the feedback, that's true the TS can be resumed manually once the lease has occured but it defeats the purpose of an automated TS if I have to keep an eye on it and intervene if I need to.
The network guys here recommended putting wireshark or network monitor on it and figuring out just what the heck is going on. Basically, what Keith Garner said. They also disabled PortFast awhile back to see if that made any difference, and it did
not.

Manual clearing f-03/f-32/f-44

Dear all,
What is the purpose of manual clearing f-03/f-32/f-44? Please explain me with an example.
I will award maximum points.
Thanks in advance,
Regards,
Ar

Let s take the example of advance and invoice from a vendor and the same to a customer.
When we pay/receive advance from vendor/customer, they will be acting as spl cust/vendor. and
When we receive or raise invoice against advance, they will be acting as gen cust/vendor.
As of this case, when we view fbl1n and fbl5n.. the net effect will be zero. But the system shows two line items as open status. Because, the customer / vendor is the same in the both line items. But their status is spl and general.
Hence we need to clear them manually....Regards..SK

Manually clearing for consignment liability account

Hi all,
we have to manually do a FI posting to clear the consignment liability account, but there are 2000 line items, so I'm wondering if there is any automatic clearing process like GR/IR clearing ( MR11) for consignment liability account? Or can we run a program to clear this account?
please advise.

Hi Anand,
I havn't got any solution on that, based on SAP notes 487162, the solution is:
In this case, you either must not use such taxes or you must carry out a manual clearing between the consignment liabilities account and a suitable account in FI using Transaction FB01 or FB60.
so I think this is our solution for now,I'll keep u update if we found a better solution.

Manually clearing DHCP leases on NAC, CAM, CAS implementation?

Similar Messages

Maybe you are looking for