Are you running DHCP on your OES 2 server?
Would you like to view the DHCP leases in use?
Well, now you can in OES 2 SP3!

Please contact the ALI TAC to schedule the upgrade and configure DHCP for this feature!


 


 

 

Viewing Dynamic Leases Under The DNS/DHCP Management Console From OES 2

This document (7006450) is provided subject to the disclaimer at the end of this document.

Environment

Novell DHCP Management Console
Novell DNS Management Console
Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3

Situation

Starting with OES 2 SP 3, administrators can view DHCP leases utilizing the DNS/DHCP management console; however, before doing so one of the following errors or messages may be encountered:

Resolution

To address the "DHCP server IP address" portion of the message(s), do the following:

  1. Launch the DNS/DHCP management console and login to the server (NOTE:  Novell Client is no longer needed with the latest versions of the DNS/DHCP Java Management Console)
  2. Click on the 'DHCP (OES Linux) tab toward the top of the console
  3. Find the DHCP Server object at the bottom of the console and select it
  4. Toward the top-right hand side of the console select the GENERAL tab and find the section called DHCP SERVER
  5. Click the ADD button and enter the IP address of the DHCP server
    • NOTE:  If doing this step on OES 2 SP 2 the buttons may be greyed out.  This is due to the schema not being extended.  This option is officially supported on OES 2 SP 3
  6. Click on the SAVE button toward the top, left-hand side of the console (looks like a floppy disk)
To address the "omapi-key" portion of the message(s), do the following:
  1. The first step in addressing this issue is to create a TSIG key if one has not already been created.
    • NOTE:  At the time this TID (Technical Information Document) was created, the secret for the TSIG key must be divisible by four (4).  If it is not DHCP will not load.  For instance, if the key's secret is set to SECRET then DHCP will fail to load as the secret is not divisible by four; however, if SECRET12 is used instead, then DHCP will load as the secret is now divisible by four.
      1. Launch the DNS/DHCP management console and login to the server (NOTE:  Novell Client is no longer needed with the latest versions of the DNS/DHCP Java Management Console)
      2. Click on the 'DHCP (OES Linux) tab toward the top of the console
      3. Highlight the SERVICE object (assuming it has already been created) and click on the CREATE button located at the top, left-hand side of the console (looks like a 3-dimensional box)
      4. Select 'TSIG Key" and assign the KEY NAME and SECRET.  Keep in mind the note above regarding the secret to make sure the number of characters used in the secret is divisible by four
      5. After hitting CREATE on the key the key should show up under the service object that was highlighted
  2. The second step in addressing this issue is to add the omapi-key setting itself
    1. While in the DNS/DHCP management console, and with the 'DHCP (OES Linux)' tab selected, highlight the DHCP SERVER object toward the bottom of the console
    2. Select the SETTINGS tab toward the top, right-hand side of the console (next to the GENERAL tab)
      • NOTE:  At this point the administrator should see a setting for the OMAPI-PORT already configured for port 7911.  If it is not there, the click the MODIFY button, find the setting, add it and assign it a port of 7911 (which is the default)
    3. Click on MODIFY and find the OMAPI-KEY setting (likely at the bottom of the list).  A drop down menu should appear after adding it, and a list of found TSIG keys should be presented.  Select the appropriate key
      • NOTE:  If the key doesn't show up at this point, review the steps above and create the key as specified
    4. Review the settings and make sure there is an OMAPI-PORT and OMAPI-KEY setting, each assigned a valid value
    5. Click on the SAVE button toward the top, left-hand side of the console (looks like a floppy disk)

At this point it may be necessary to hit the TREE REFRESH button located at the top, left-hand side of the console.  It is found next to the SAVE button.  Once the tree refresh is complete, expand the SUBNET and then the POOL to view any current leases that may be assigned out.  If one of the following errors is encountered, it is likely due to the fact that the leases file has not yet been populated with any leases.  This error should resolve itself once there is a lease to be found in the dhcpd.leases file on the server:

NOTE: The 'omapi-port' and 'omapi-key' settings cannot be added, modified, or managed from iManager in any way at the time this TID was written.  This has been reported to Engineering.   The steps described in this TID should be completed from the DNS/DHCP Management Console.