Three-step DHCP basic configuration on a router

-
Basic configuration of DHCP on a router-
By deafult, DHCP server and relay agent service is enabled on a router, hence, we do not need to start it.
1. Instead of mentioning the range which should be assigned as IP address for the devices using your DHCP server, we mention the address it should exclude to assign to the devices-
R1(conf)#ip dhcp excluded-address <range of IP address>

 example
R1(conf)#ip dhcp excluded-address 142.100.10.20 142.100.10.50
R1(conf)#ip dhcp excluded-address 142.100.10.80 142.100.10.254

 This means only range 142.100.10.1-10 and 142.100.10.51-79 is available for the devices.
2. Configure the DHCP Pool
R1(conf)#ip dhcp pool POOL1  ---- define the name of the pool
R1(dhcp-config)#network 142.100.10.0 255.255.255.0 -- define the IP&mask of the DHCP pool's network
R1(dhcp-config)#default router 142.100.10.20  -- define default gateway
R1(dhcp-config)#option 150 142.100.10.20 -- define TFTP address
3. Configure IP helper Address
This command is configured on the interface that is connected to the broadcast domain in which you
wish to provide DHCP IP addresses example Vlan interface or ethernet interface which is connected with l2 switch.
This command is not required if your phones are hooked on the router on HWIC POE card.
R1(conf)#int gig0/0.202
R1(Conf)#ip helper address <DHCP server IP address>

Comments

Post a Comment

Popular posts from this blog

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Admin...
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C...
Read more