Not supported by SBC SWe Lite in this release.
For the SBC 1000/2000 to function as a DHCP server, it must be enabled and have a DHCP pool configured on the at least one of its interfaces. The SBC 1000/2000 only performs DHCP server functionality on those interfaces that have a DHCP pool associated with them.
The SBC 1000/2000 DHCP Server supports serving up to a maximum of 20 address pools. A DHCP pool typically consists of a name, an IP address range, netmask, default router, and other various network parameters, allowing the SBC 1000/2000 to serve as a DHCP server to multiple connected subnets. It also allows the SBC 1000/2000 to provide different DHCP parameters to different pools of clients (e.g. SIP phones, engineering workstations, VPN users, etc.).
To create or to modify an existing DHCP Pool:
- In the WebUI, click the Settings tab.
From the left navigation pane, go to Protocols > IP > DHCP > Pools.
DHCP Pools
Modifying a DHCP Pool
- Click the expand (
) Icon next to the entry you wish to modify. - Edit the entry properties as required, see details below.
Enabling an Entry in a DHCP Pool
- Select the check box next to the entry you wish to enable.
- Click the Enable (
) icon at the top of the table.
Disabling an Entry in a DHCP Pool
- Select the check box next to the entry you wish to disable.
- Click the Disable (
) icon at the top of the table.
Creating a DHCP Pool
From the DHCP Pools window, click on the ( 
) at the top of the screen.
Create DHCP Pool Entry
Pool Attributes - Field Definitions
Pool Name
Specifies the name of the DHCP pool.
Pool Interface
Specifies the interface with which this pool is associated. This drop down list is populated with the interfaces configured in Logical Interfaces.
Pool IP Start
Specifies the beginning address for the range of addresses in the DHCP pool (the pool from which the DHCP clients will get their IP addresses).
Pool IP End
Specifies the ending address for the range of addresses in the DHCP pool (the pool from which the DHCP clients will get their IP addresses).
Lease Lifetime
Specifies whether the duration of the lease is infinite or a specified value. Valid values: Set (lease is set to a specific value, see Lease Lifetime Value) or Never Expires (there is no expiration time on lease).
Lease Lifetime Value
Specifies the duration of the lease, in minutes. Valid entry: 2 - 525600 minutes. Visible only when Set is selected from the Lease Lifetime drop down list.
Options - Field Definitions
Default Router
Specifies the default router used for DHCP Clients. Must be an IPv4 address.
DNS Server
Specifies the DNS server used for DHCP Clients. Must be an IPv4 address.
Domain Name
Specifies the domain name for DHCP clients to use when connecting to the pool.
SIP Server Present
Specifies whether or not the node uses a SIP server attached to an available network.
Primary SIP Server
Specifies the Primary SIP server to be used by the DHCP client. Must be an IPv4 address. Visible only when Yes is selected in the SIP Server Present list box.
Secondary SIP Server Present
Specifies whether or not the node uses a SIP server attached to an available network. Visible only when Yes is selected in the SIP Server Present list box.
Secondary SIP Server
Specifies the Secondary SIP server to be used by the DHCP client. Must be an IPv4 address. Visible only when Yes is selected in the Secondary SIP Server Present list box.
NTP Server Present
Specifies whether or not the node uses an NTP server attached to an available network.
Primary NTP Server
Specifies the Primary NTP server to be used by the DHCP client. Must be an IPv4 address. Visible only when Yes is selected in the NTP Server Present list box.
Secondary NTP Server Present
Specifies whether or not the node uses a Secondary NTP server attached to an available network. Visible only when Yes is selected in the NTP Server Present list box.
Secondary NTP Server
Specifies the Secondary NTP server to be used by the DHCP client. Must be an IPv4 address. Visible only when Yes is selected in the Secondary NTP Server Present list box.
TFTP Server
Specifies the TFTP server to be used by the DHCP client. May be any server name or IP address
Bootfile
Specifies the bootfile used by the DHCP client.
Vendor Options - Overview
Vendor Options allows the SBC 1000/2000 to provide vendor parameters for different pools of clients (i.e, SIP phones, engineering workstations, VPN users, etc.). The configuration values are specific to the phone or device being configured. For valid values, consult the manual that accompanied the phone/device.
The Vendor Specific Information is for Dynamic Host Configuration Protocol (DHCP) option 43 (defined here: http://tools.ietf.org/html/rfc2132#section-8.4). These options indicate the vendor type, and the DHCP client pool and server to exchange vendor specific information.
The Vendor-Identifying Vendor Options are DHCP option 124/125 (defined here: http://tools.ietf.org/html/rfc3925).
Vendor Specific Information - Field Definitions
Vendor Name
Specifies the vendor name for the Vendor Specific Information. Used to match against the client's vendor name and send the vendor attribute if a match occurs. Maximum length: 64 characters.
Code
Specifies the Vendor Specific Information option code sent. Valid entry: 0 - 254 characters.
Value
Specifies the Vendor Specific Information user data sent to the matching DHCP client. This is dependent upon the option code used, and can be an ASCII string or hex string of the 00:aa:bb format. Valid entry: maximum length of 64 characters.
Vendor-Identifying Vendor Options - Field Definitions
Enterprise Number
Specifies the vendor enterprise number for the Vendor-Identifying Vendor Options. Used to match against the client's vendor enterprise number and send a vendor attribute if a match occurs.
Code
Specifies the Vendor-Identifying Vendor Option code to be sent.
Data
Specifies the Vendor-Identifying Vendor Option data to be sent. A valid entry can be either an ascii string of the attribute or a hex string in the aa:bb:cc format. Maximum length: 64 characters.
Overview
Content Tools