ISG with DHCP Option 82 sessions
Greetings, I'm looking to roll out a GPON deployment using the ISG as our BRAS with DHCP-based sessions but we are experience some problems with session restart. Were using an external DHCP server and RADIUS. Sessions come up fine the first time, but if there is an existing session and the CPE node is rebooted the session get's "stuck". To clear the session we turn off the CPE device, clear the state in the GPON shelf and wait for more than 5 minutes. Doing some debug shows the SG-DPM process thinking there is an existing DHCP lease that seems to clear out after five minutes of "silence". I'd like to get this five minutes down to something in the less than 60 seconds range. Anybody know of any knobs to tweak this?
Dec 2 12:49:19.642 EST: SG-DPM: getting the context for mac_address = 0024.c823.7322
Dec 2 12:49:19.642 EST: SG-DPM: input override for mac_address = 0024.c823.7322
Dec 2 12:49:19.642 EST: SG-DPM: null input interface from dhcp,returning access interface GigabitEthernet0/3.300
Dec 2 12:49:19.642 EST: SG-DPM: DHCP Offer notification from client, mac_address = 0024.c823.7322
Dec 2 12:49:19.642 EST: SG-DPM: getting the context for mac_address = 0024.c823.7322
Dec 2 12:49:19.642 EST: SG-DPM: Aborting update. IP address: 10.2.2.162 hasn't changed
Running 12.2 (31) SB19 with the following code snippet:
aaa authorization subscriber-service USER_LOGON group radius
policy-map type control USER
class type control always event session-start
20 authorize aaa list USER_LOGON password blablabla identifier circuit-id
30 service disconnect
interface GigabitEthernet0/3.300
encapsulation dot1Q 300
ip dhcp relay information trusted
ip address 10.1.1.1 255.255.255.224
ip helper-address 10.10.10.10
no cdp enable
service-policy type control USER
ip subscriber l2-connected
initiator dhcp
Try...
If the session is still un an unauthenticated state setting the unauthe timer will help:
class type control always event session-start
25 set-timer IP_UNAUTH_TIMER 6
But if the session is authenticated then it is suggested to set a idle timeout value like this:
policy-map type service IDLE_TIME_SERVICE
class type traffic IDLE_TIME
timeout idle 600
class type control always event session-start
24 service-policy type service name IDLE_TIME_SERVICE
Shelley.
Similar Messages
-
Low cost router with DHCP option 66
I am trying to find the lowest cost Cisco router with option 66. I use the router in conjunction with spa50x phones and need to be able to have them config at boot up.
I was using the srp521. It was suggested to use the isa550, but that just got an EOL. Do any of the RV routers support it, I did not find it on a rv110 and I know its not on the rv042. It seems to me that this is a functionality that should be on a router aimed at a small business.
SageDear Sage,
Thank you for reaching the Small Business Support Community.
Unfortunately none of the Small Business routers were intended to provide DHCP option 66 for IP Phones configuration via TFTF server. I suggest you to look for a enterprise device for that matter, like an ASA for example, and you can also inquire about a low cost option from their community support forum.
My job role in Cisco, among several, is to identify business opportunities and product enhancements for the Small Business products so I am definitely going to suggest this option 66 feature for future firmware releases.
Please do not hesitate to reach me back if there is anything I may assist you with in the meantime.
Kind regards,
Jeffrey Rodriguez S. .:|:.:|:.
Cisco Customer Support Engineer
*Please rate the Post so other will know when an answer has been found. -
Before I updated the latest version of Firefox, every time the browser shuts down in error, I would get the System Restore feature which was really nice. Now, this no longer happens and when I went to configure this ability, it does not even provide me with the option to select to show windows and tabs from the last session. How can I get the restore session feature working again?
Make sure that you do not run Firefox in permanent Private Browsing mode.
*https://support.mozilla.com/kb/Private+Browsing
*You enter Private Browsing mode if you select: Tools > Options > Privacy > History: Firefox will: "Never Remember History"
*To see all History and Cookie settings, choose: Tools > Options > Privacy, choose the setting <b>Firefox will: Use custom settings for history</b>
* Deselect: [ ] "Permanent Private Browsing mode"
* http://kb.mozillazine.org/Session_Restore
* https://support.mozilla.com/kb/Session+Restore -
Can I use Time Capsule to share a public ip within a network with DHCP enabled?
Hi I have a router with 8 public ip's which is doing DHCP for the public ip's I own. What I am trying to do is to give a static public IP to my Time Capsule and then the time capsule should create another network (both wired and wireless) with private IP (eg. 192.168.1.xxx) and do DHCP to the connected to time capsule devices.
I tried to select the option SHARE A PUBLIC IP but it is not working.
Any help?
ArmandosI am assuming that the static IP address that you are attempting to assign the WAN-side of the Time Capsule is one of the eight Public IP addresses available to you ... correct?
If so, then you should be able to configure the TC's WAN port for either: 1) Use the "Using DHCP" option to grab one of these Public IP addresses from the upstream router's DHCP server, or 2) Use the "Manually" option, and then, enter the appropriate IP addresses in their appropriate fields.
With the Connection Sharing = Share a public IP address selected, the TC's NAT & DHCP services will be enabled and they should be able to provide a Private LAN behind it.
Are either or neither the TC's WAN or LAN sides working properly? -
Multiple domains via DHCP (option 15)
It seems Mac OS X (I use 10.4.10 but I suspect it affects many versions) is incompatible with receiving multiple domain names in a single string over DHCP Option 15.
If DHCP returns Option 15 with "exampledomain.com eng.exampledomain.com", then any lookup (using dig, ping, Microsoft Entourage, etc.) of a non-fully qualified domain name will fail.
You can see this in the /etc/resolv.conf file, which contains:
domain exampledomain.com eng.exampledomain.com
nameserver 10.X.X.1
nameserver 10.X.X.2
I know that putting multiple domains within the same "domain" option in DHCP is a proprietary hack but some networks still use this. Has anybody run into this and have they found a good resolution to make Mac OS X work with multiple domains?While a single mailbox can be configured to receive on multiple addresses (called "proxy addresses" or "aliases"), the mailbox is configured with only one primary SMTP address (outbound address). So if your requirement is to send
as the received address, you would not be able to do that with a single mailbox through normal means.
Some people have developed a workaround to the above limitation by configuring Outlook to use multiple POP3 accounts for a single mailbox. See this link for additional details:
http://blogs.technet.com/b/hot/archive/2012/04/26/how-to-add-an-alias-to-an-office-365-account-and-how-to-set-up-outlook-to-send-email-messages-as-this-alias.aspx
I would also be sure to look at the client requirements for Exchange Online. The supported version of Outlook is going to be Outlook 2010 SP2. Older versions may work but would not be supported. Outlook 2003 would at best possibly
connect via POP3.
Joseph Palarchio http://www.itworkedinthelab.com -
As default, SPA122 and SPA112 have DHCP Options 66, 160, 159 and 150 turned on.
Our pre-provisioning process includes adding our default profile rule to our provisioning server for the device to pull its configuration files once the device has been added to an account.
However, it seems like some customers have had problems with the device downloading the definite configuration file and manually turning off option Option 66 in the provisioning tab in the device solves this issue.
Is there any option we could add to our pre-provisioning file so that it removes 66 from the "DHCP Option to Use" field in the provisioning tab?
Please advise...Thanks Dan,
I didn't know the dhcp server could serve different options to different classes of clients, I'll have to look that up!
Moises
so if your provisioning file has this line below (this is from a spa5xx config I had in my temp folder, so use the line from your provisioning file, or use the SPC tool to create a new default config for that device type)
<DH<DHCP_Option_To_Use group="Provisioning/Configuration_Profile">66,160,159,150,60,43,125</DHCP_Option_To_Use>
change it to
<DH<DHCP_Option_To_Use group="Provisioning/Configuration_Profile">160,159,150,60,43,125</DHCP_Option_To_Use>
Hope it helps,
Provisioning guide is here
Cisco IP Telephony Devices Provisioning Guide - Cisco Support Community
Dan -
DHCP Option Tags are not being applied...
Hi,
About to loose my mind... basically we are working towards a small WYSE Thin Client deployment in our environment. The WYSE clients require to receive certain DHCP Option Tags to find the WCM server of which they receive their configuration from. Same
applies to the WDM Server as well. The problem is no matter what we do, our test client is not receiving the custom option tags we've defined in our DHCP server.
DHCP Servers:
vlan41
10.40.1.206
10.40.1.207
Test Client:
vlan46 - ip helpers defined on the switch
Set to receive the same ip address from the DHCP server through the reservation route.
Option Tags:
186 - WDM Server - 10.40.1.184
195 - WCM Server - 10.40.1.185
196 - WCM Path - /
I've installed Wire Shark on the test client to monitor the DHCP activity. The above custom options tags are not being pushed on to the client.
The Router, DNS Server and Domain Tags are being pushed. So it's working but also not working????!!!
Anybody with some insight to this problem?Hi hpaul_p
In all fairness I'm about to give up... the vendor is not coming up with a solution and constantly blaming Microsoft. To further test and confirm this wasn't a network issue, I've setup a secondary test environment using a 4 port switch, a client and
a DHCP server. Same results!!! I'm really running out of time, so my work around is this: I've setup a SRV records pointing to the WCM server... in your case this would be SRV record for the WDM server. I've disabled the auto
discovery functionality of the WDM Agent, for some reason it seems to be clashing with the WCM agent. Since you will be using WDM only, don't disable auto discovery, tick the DNS SRV record from the Discovery Settings under the client agent.
I'm going to add the clients to the WDM server manually through their ip addresses so don't need auto discovery. From what I gather from the manuals the WCM searches for the repository or conifg servers in this order: 1. SRV 2.DNS (A record)
3.DHCP (Options), I bet it's the same with WDM. Though SRV and DNS methods has their limitations, if you will be using the default paths and credentials it shouldn't be a problem. This is all I have have. Steven Song I've forwarded you the
DHCP database, if you find any problems with it please let me know. -
Dnsmasq sends out its own ip as dns-server dhcp option
Hi,
i have a gateway / dns server on 192.168.1.1
I have a dhcp server on 192.168.1.2 (dnsmasq)
I configured dnsmasq to look into /etc/resolv.conf (well, that's actually default behavior) and use that to specify dns server when replying to client dhcp requests.
However, it sends out its own ip instead, which is *not cool*.
# cat /etc/resolv.conf
nameserver 192.168.1.1
#nameserver 127.0.0.1
#nameserver 212.71.0.33
# edpnet
nameserver 212.71.0.33
# grep -v ^# /etc/dnsmasq.conf | grep -v '^$'
domain-needed
bogus-priv
dhcp-range=192.168.1.5,192.168.1.255,12h
dhcp-host=q700
dhcp-host=dieter-ws
dhcp-host=dieter-dellD620-arch
dhcp-host=gibran
dhcp-host=hilde-compaq-arch
dhcp-host=hilde-vbox-win
dhcp-host=BRN_0441B3
dhcp-option=option:router,192.168.1.1
log-dhcp
# cat /etc/hosts
# /etc/hosts: static lookup table for host names
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost
192.168.1.2 dieter-p4sci-arch server
192.168.1.3 q700
192.168.1.5 dieter-ws
192.168.1.6 dieter-dellD620-arch
192.168.1.7 dieter-delle5410-arch gibran
192.168.1.8 hilde-compaq-arch
192.168.1.9 hilde-vbox-win
192.168.1.10 BRN_0441B3 hl5250
178.79.146.162 dieter-linode1
# End of file
here's what I see in /var/log/daemon.log, when I start dnsmasq and do a dhcp request.
Note the discrepancy between what it says as "using nameserver" and what it actually tells clients.
Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: started, version 2.55 cachesize 150
Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: compile time options: IPv6 GNU-getopt no-DBus no-I18N DHCP TFTP
Feb 12 18:10:50 dieter-p4sci-arch dnsmasq-dhcp[2168]: DHCP, IP range 192.168.1.5 -- 192.168.1.255, lease time 12h
Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: reading /etc/resolv.conf
Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: using nameserver 212.71.0.33#53
Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: using nameserver 192.168.1.1#53
Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: read /etc/hosts - 10 addresses
Feb 12 18:10:56 dieter-p4sci-arch dnsmasq-dhcp[2168]: 2764941049 available DHCP range: 192.168.1.5 -- 192.168.1.255
Feb 12 18:10:56 dieter-p4sci-arch dnsmasq-dhcp[2168]: 2764941049 DHCPRELEASE(eth0) 192.168.1.5 80:ee:73:09:fa:94
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 available DHCP range: 192.168.1.5 -- 192.168.1.255
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 client provides name: dieter-ws
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 vendor class: dhcpcd-5.2.10:Linux-2.6.37-ARCH:i686:GenuineIntel
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 DHCPDISCOVER(eth0) 80:ee:73:09:fa:94
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 DHCPOFFER(eth0) 192.168.1.5 80:ee:73:09:fa:94
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 1:netmask, 121:classless-static-route, 33:static-route,
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 3:router, 6:dns-server, 12:hostname, 15:domain-name,
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 26:mtu, 28:broadcast, 42:ntp-server, 51:lease-time,
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 54:server-identifier, 58:T1, 59:T2, 119:domain-search
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 tags: known, eth0
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 next server: 192.168.1.2
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 1 option: 53:message-type 02
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 54:server-identifier 192.168.1.2
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 51:lease-time 00:00:a8:c0
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 58:T1 00:00:54:60
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 59:T2 00:00:93:a8
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 1:netmask 255.255.255.0
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 28:broadcast 192.168.1.255
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 6:dns-server 192.168.1.2
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 3:router 192.168.1.1
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 available DHCP range: 192.168.1.5 -- 192.168.1.255
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 client provides name: dieter-ws
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 vendor class: dhcpcd-5.2.10:Linux-2.6.37-ARCH:i686:GenuineIntel
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 DHCPREQUEST(eth0) 192.168.1.5 80:ee:73:09:fa:94
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 DHCPACK(eth0) 192.168.1.5 80:ee:73:09:fa:94 dieter-ws
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 1:netmask, 121:classless-static-route, 33:static-route,
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 3:router, 6:dns-server, 12:hostname, 15:domain-name,
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 26:mtu, 28:broadcast, 42:ntp-server, 51:lease-time,
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 54:server-identifier, 58:T1, 59:T2, 119:domain-search
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 tags: known, eth0
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 next server: 192.168.1.2
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 1 option: 53:message-type 05
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 54:server-identifier 192.168.1.2
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 51:lease-time 00:00:a8:c0
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 58:T1 00:00:54:60
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 59:T2 00:00:93:a8
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 1:netmask 255.255.255.0
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 28:broadcast 192.168.1.255
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 6:dns-server 192.168.1.2
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 9 option: 12:hostname dieter-ws
Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 3:router 192.168.1.11 yes, the dhcp server who's scope is full will not do a dhcp
'offer'
2 dhcp that answers fastest with a 'offer' will win. A delay is configurable (but changes nothing
about the root scenario were the fastest will win)
Note that if the scopes overlap on the servers, they might not lease out all the addresses in the scope.
I would enlarge the scope as you will want to fence against unavailability of one of the servers (or a network connection for that matter). you currently have more addresses leased out than any set of two of your servers can offer.
MCP/MCSA/MCTS/MCITP -
The DHCP option 100 "Middle Tier server" is configured and
added on the scope under "Other DHCP Options".
The values set for option 100 are two operable IP-addresses, reflecting
two running Middle Tier servers
Problem:
When a client gets it's DHCP-address, the registry values for
the Middle Tier server is corrupted.
The registry keys hosting the values are (reference TID 10092121 for
details):
HKLM\Software\Novell\ZENworks\<dword> MiddleTierDHCPOptionNumber
(we use decimal value 100 as Option number)
HKLM\Software\Novell\ZENworks\<string> MiddleTierAddress
(we use 192.168.1.4 and 192.168.1.5 in the DHCP-scope)
But the Middle Tier login fails after DHCP delivery.
Looking at the registry on the client, the string values for the
MiddleTierAddressis corrupted. Instead of showing the two correct
IP-addresses, it shows just messed up characters like squares,
bars and other cryptical signs at the end of the enrty.
Without a DHCP delivery, things works ok, if the ZfD Agent is configured
with the Middle Tier DNS name.
The registry key holding the DHCP-distributed Middle Tier address is:
HKLM\Software\Novell\ZENworks\<string> MiddleTierAddress
After DHCP-distribution, in the Middle Tier login dialog, the squares
appears like bold vertical bars. Middle Tier login then fails.
Also found a related TID # 10089967.See:
"Workstation receives corrupted middle tier address when middle tier address
is"
http://support.novell.com/cgi-bin/se...i?10099553.htm
I'm sure Shaun or one of the SysOps could tell you the status of this issue.
Regards
Rolf Lidvall
Swedish Radio (Ltd) -
How to give user Compiling with debug option, i have try to by giving grant debug any procedure and debug connect session but it failed.
Any ideas?
Edited by: rootsman on Jul 15, 2010 12:00 AMPost the error screenshot..
eg:
grant DEBUG CONNECT SESSION to username;
grant DEBUG ANY PROCEDURE to username;
Check the below explanation:
DEBUGGING:
DEBUG CONNECT SESSION
Connect the current session to a debugger that uses the Java Debug Wire Protocol (JDWP).
DEBUG ANY PROCEDURE
Debug all PL/SQL and Java code in any database object; displayinformation on all SQL statements executed by the application
Note: Granting this privilege is equivalent to granting the DEBUG object privilege on all applicable objects in the database. -
If DHCP option 82 is supported, how can I add it to my server?
Thanks, I upgraded software to newest 1.3.0.59, then rebooted. After configuring ( only option 82 - no relay agent ) there is still no 82 option in dhcp discover packets.
Wireshark with captured dhcp discover broadcast packet. Dhcp part:
As You can see - there is no 82 option.
All interfaces are trusted (dhcp snooping).
Should I configure anything else to make it work ?
regards, -
MDT/WDS PXE Deployment - DHCP Options for both x64 and x86
Alright, I've found out the option 66 & 67 information, as what to set for each. The problem I'm trying to figure out is what to use for the boot file for option 67. So far all the info I've found says this:
Configure DHCP option 67 with the right boot image file.
For 32-bits systems \boot\x86\wdsnbp.com
For 64-bits systems \boot\x64\wdsnbp.com
I want to be able to use this for both 32 and 64 bit Windows clients, but cannot find anywhere that specifies how I would be able to do both.DHCP Options (specifically 067) can have a significant impact on which NBP your client can access. If you specify \Boot\x86\Wdsnbp.com you are forcing the client to the 32bit NBP.
If you specify \Boot\x64\Wdsnbp.com you are forcing the client to the 64bit NBP.
Niether option is an ideal solution, especially if you have a varied environment.
I would take a look at the following article and see if it sheds some light on your question:
PXE booting with WDS – DHCP Scope vs IP Helpers -
ISG not create a session for specific pepoles
Hi All;
I have an ASR 1k running as ISG and DHCP server.
I used an initiator for the session as MAC address.
Today I found unexpected behavior as for some users used to work before to have IP address and no session created.
this configuration on the interface :-
interface Port-channel1.12
encapsulation dot1Q 112
ip address 10.0.0.1 255.255.255.0
service-policy type control EAP-AP
ip subscriber l2-connected
initiator unclassified mac-address
Any help in That.
Thanks
AbdelGalil FaridHi,
you can create new DISABLED monitor in new management pack.
After that you will enable this monitor for specific servers using overrides. -
I would love to just post in this thread:
http://discussions.apple.com/thread.jspa?threadID=2347065
But Apple likes to lock old threads and force you to start over...
The indication in that thread is people did get this to work, but there is no final note of exactly how. So far we are finding it does not function properly. We're trying to set up a Fog server, but using the Mac server for DHCP. Unfortunately it fails to actually forward the client to the Fog server as needed. Here is what we have done:
on the Mac server (10.6.4) edit the /etc/bootpd.plist
below the array for dhcpdomainsearch and above the dhcp_router key, we insert the following:
<key>dhcpoption66</key>
<data>
krp+CQ==
</data>
<key>dhcpoption67</key>
<data>
cHhlbGludXguMA==
</data>
These values are obtained using the DHCP Option Code Utility posted in the above thread with these inputs:
Option Code Number: 66
Option Code Type: IP
Option Code Value: 146.186.126.9
Option Code Number: 67
Option Code Type: String
Option Code Value: pxelinux.0
When those didn't work, because the info in the noted thread was not clear, we also tried:
Option Code Number: 66
Option Code Type: String
Option Code Value: 146.186.126.9
Which gave us:
<key>dhcpoption66</key>
<data>
MTQ2LjE4Ni4xMjYuOQ==
</data>
This also did not work. In every case the TFTP times out indicating option 66 is not defined or is not being followed correctly. It's a shame that unlike Microsoft, Apple has not included these common option controls in their server interface. We're hoping someone who has actually gotten this to work will see this and be able to clear up what Apple needs for input to make it actually work right.
Thanks for any help!Hi, I am the author of the DHCP Option Code Utility and therefore the unofficial worldwide expert on Apple's DHCP Server
If you go to http://www.sustworks.com/site/prodipmxoverview.html you can download a copy of IPNetMonitorX which includes a feature to test DHCP option codes. For example, you could test option 66 on a different make of DHCP Server (one that works) to see what exactly it returns, and then do the same test against Apple's DHCP Server and see if it is returning exactly the same result. Obviously if it returns a different result there is a problem.
Note: IPNetmonitorX shows all DHCP option code results as decimal numbers (you need verbose logging turned on), you may therefore need to translate these to hex or ASCII values. One decimal number equals one hex number or one ASCII character.
I can tell you that using DHCP Option Code Utility to generate the values, Apple's DHCP server works fine for many users needing to do this to support VoIP phone systems which also need to advertise a TFTP server.
I have looked at your message and as far as I can see, your entry for Option67 is what I would believe to be correct. Obviously this field is not an Integer, nor is it an IP address, so using the String option is the only logical choice. For Option66, like your post, two choices spring to mind, the first being to use the IP address choice and the second the string choice. Again your examples are what I would use with my first choice being the IP address one.
However there is one thing I can mention that may (or may not) help. An IP address for humans is written as 146.186.126.9 that is four decimal integers between 0 and 255 each separated by a full stop, if we break this down we have the following decimal integers
146
186
126
9
in hexadecimal the above translates to
92
BA
7E
9
Now the way Apple's DHCP Server actually stores IP addresses (ignoring the encoding you see) is actually as four hexadecimal bytes so if you use my utility to encode
92 BA 7E 09
as hexadecimal, you will find it results in the identical krp+CQ== result. Now apart from giving you some background which may help if/when you use IPNetMonitorX to test DHCP server option codes, what this also allows you to consider is that it maybe that some systems want these bytes in a different order. This relates to 'little endian' vs. 'big endian' see http://www.cs.umass.edu/~verts/cs32/endian.html
I am somewhat doubtful of this, as all the VoIP systems I have dealt with use the same order equivalent to 146 186 126 9
If your able to use IPNetMonitorX to query FOG's own DHCP server and give me the result, I can see what difference it is doing.
Note: You should only have one DHCP server on a network at a time, so you should do this test on a standalone network or when you will not interfere with your live network.
Note: You need to stop and start the Apple DHCP server in Server Admin to get it to re-read /etc/bootpd.plist and use your new settings. You should therefore stop the DHCP server while editing the file.
UPDATE - NEWSFLASH
Just retested my own Mac OS X 10.6.4 DHCP Server which has four DHCP option codes defined which were previously working. When I tried adding a copy of your option66, even with supposedly my DHCP Server 'stopped' it kept overwriting the changes I made. It maybe your server is also almost immediately overwriting and losing your option codes. Try doing it in single user mode or even booting from another disk and of course double check your bootpd.plist still lists your option codes. -
SCCM 2012 R2 PXE not working because DHCP Option 43 is configured to AVAYA
Hello!
We are having some issues with PXE and OS Deployment with some computers.
We tested computers DELL, PXE and DHCP works without any issues. But we tested some HP computers and we received the error PXE-E77 Bad or missing discovery server list
We investigate that error and found that is related with the Option 43 Vendor Specific Info is enable on the DHCP Server, the solution that we tested and works as expected is create a new scope on the DHCP and without enable the Option 43.
That was a temporary solution for the issue, nevertheless we need to use PXE over our network, and we cannot remove the Option 43 on the DHCP configured for AVAYA, so we need a solution that can coexist with PXE and Option 43 on the DHCP.
We will apreciate any advice on this issue.
Thank in advance.
Manuel
Manuel´s Microsoft Forums ThreadsThe easiest way to deal with this problem is not to use DHCP scope options. Implement IP Helpers instead. It is straightforward to configure and is the only MS supported way anyway.
http://www.gerryhampsoncm.blogspot.ie/2013/02/sccm-2012-sp1-step-by-step-guide-part_9487.html
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson
Maybe you are looking for
-
What is the white horizontal line and red vertical line on my brand new ipad mini?
Bought a brand new ipad mini 2 for my sons Christmas, took it out the box and it was during the set up process, ie entering his iTunes and icloud account, a white horizontal line and a red vertical line appeared on the screen and is there all the tim
-
Hello I have a big problem with my Xsan Admin. Yesterday by mistake my configuration of xsan admin from Application Support are gone. Only config files from /Library/Filesystems/Xsan/config survive, but without one client in config.plist Now i cant m
-
Scan on one machine and print to a different device
Hi - I have a PSC 2179 All-in-1. I've been told that it is possible to use the built-in scanner to copy a document and send the output directly to a different printer. Does anyone know if this is true ? If it is, presumably the 2 devices need to be n
-
How do I correct a typo on my id address?
How do I correct a typo on the ID address?
-
MView refresh error on 10gR2..(unique constraint error)
Hi. all. The database is 2-node RAC 10gR2 on SunOS. Today morining, I got the following error. EXEC dbms_refresh.refresh('"ODSFAB"."CURRENTWIP"'); ORA-12008: error in materialized view refresh path ORA-00001: unique constraint (ODSFAB.CURRENTWIP_GLAS