6-34
Catalyst 4500 Series Switch, Cisco IOS Software Configuration Guide - Cisco IOS XE 3.9.xE and IOS 15.2(5)Ex
Chapter 6 Programmability
Sample Configuration and Reference Information
;LogLevel=None
;LogLevel=Normal
;LogLevel=All
;LogLevel=Debug
[REPLICATION_SERVERS]
#You can have 2 instances of Open DHCP Servers in a network. Open DHCP Server sends
#replicated inform messages to the other instance of the Open DHCP server and replicates
#leases. The IP address alloted by one server is not realotted by the other server to
another host. Further when one server goes down, the other can renew the leases, without
NAK and DISCOVER. You must specify the primary and secondary servers for replication to
#work.Ensure that the primary & secondary server entries are identical on both servers.
#You may copy the entire ini file on both servers and change the
#LISTEN_ON on individual servers, if needed.
;Primary=192.0.2.253
;Secondary=192.0.2.254
[HTTP_INTERFACE]
#This is http interface to display the lease status. By default, this is the fist
#interface, port 6789. You can change it to any network interface.
;HTTPServer=192.51.100.1:6789
#To limit client access, you can specify up to 8 HTTP client IPs here. If no client IPs
#are specified then clients can access the HTTP interface.
#You can also change the title of the HTML page
;HTTPTitle=example-httpserver-url.com
#Sections below are other DHCP Sections. You can allot clients addresses dynamically from
#the DHCP Range or statically. For static addresses, client section must be created for
#each static client against its MAC Address. BOOTP clients are always static. DHCP Ranges
#are grouped into [RANGE_SET]s, so that range specific options can be specified for a
#group of ranges in one place. The total ranges in all [RANGE_SET]s is also 125 and you
#can also have a maximum of 125 [RANGE_SET]s.
#You can specify one or more ranges in each [RANGE_SET] section, in the specified format.
#Open DHCP Server allots addresses from these ranges. Static Hosts and BootP clients do
#not require ranges. You do not have to specify a [RANGE_SET] or a DHCP_Range if all
#clients are Static.
#The dynamic address allocation policy is -
#1)Look to see if a MAC address is specified as static DHCP Client and use that IP
#2)If not found, look for an old, expired or active address of the same host
#3)If not found, look at the requested IP address and check if available
#4)If not found, allot an unused IP address, if available
#5)If not found, allot the expired IP address of the other host.
#From 2) to 6), requests from different interfaces look for matching DHCP ranges
#of interface IP, and requests from relay agents look for matching range to
#relay agent IP.
#All the ranges in a [RANGE_SET] section can be further restricted with Filter_Mac_Range,
#Filter_Vender_Class and Filter_User_Class. For example, if a MAC range is specified, then
#this section's ranges will only be available to hosts, who’s MAC address falls in this
#range. Also if any host has a matching Filter_Mac_Range in any DHCP_RANGE section, then
#other DHCP range sections without a Filter_Mac_Range or without a matching MAC range will
#not be available to it. Each Manufacturer has a fixed MAC Range. The same Mac ranges can
#repeat in many DHCP_RANGE sections.
#For Filter_Vendor_Class (option 60) and Filter_User_Class filter (option 77),
#the range is available only to a matching value of Filter_Vender_Class
#and Filter_User_Class sent in the client request. If the Filter_Vender_Class and
#the Filter_User_Class values do match in one or more ranges, other ranges with missing
#or non-matching values are not available to such clients. You can specify upto 32
#Filter_Mac_Range, Filter_Vender_Class and Filter_User_Class in each [RANGE_SET].
To Next Page
Loading...
Need help?
General
