Troubleshooting dhcp configuration – Brocade Communications Systems RFS6000 User Manual

Page 542

Advertising
background image

540

Brocade Mobility RFS4000, RFS6000 and RFS7000 CLI Reference Guide

53-1001931-01

Configuring the DHCP server using controller CLI

17

Troubleshooting DHCP Configuration

1. The DHCP Server is disabled by default. Use the following command to enable the DHCP

Server:

RFController(config)#service dhcp

This command administratively enables the DHCP server. If the DHCP configuration is
incomplete, it is possible the DHCP server will be disabled even after the execution of this
command.

2. Use the

network

command to map the network pool to interface.

network 192.168.0.0/24

In the above example, 192.168.0.0/24 represents the L3 interface. When you execute this
command, no check is performed to endorse whether an interface (with the specified
IP/Netmask) exists. The verification is not performed because you can create a pool and map
it to non existing L3 interface.

When you add a L3 interface and assign an IP address to it, the DHCP server gets
enabled/started on this interface. If you have a pool for network 192.168.0.0/24, but the L3
interface is 192.168.0.0/16, DHCP is not enabled on 192.168.0.0/16, since it is different
from 192.168.0.0/24.

3. A network pool without any include range is as good as not having a pool. Add a include range

using the

address range

command.

address range 192.168.0.30 192.168.0.30

4. To work properly, a host pool should have the following 3 items configured:

client-name (CLI is

client-name <name>

)

fixed-address CLI is

host <ip>

)

hardware-address/client-identifier

The hardware address is

hardware-address <addr>

The client-identifier is

client-identifier <id>

If you use

client-identifier

instead of

hardware-address

, a DHCP client sends the

client-identifier when it requests for IP address. The Client - identifier has to be configured in
the DHCP Client as an ASCII value and the same has to be used in the DHCP server option (for
example, the Client- identifier option).

5. A host pool should have its corresponding network pool configured, otherwise the host pool is

useless. The fixed IP address configured in the host pool must be in the subnet of the
corresponding network pool.

6. If you create a pool and map it to an interface, it automatically gets enabled, provided DHCP is

enabled at a global level. Use the

no network

command to disable DHCP on a per

pool/interface basis.

7. To set a newly created pool as a network pool, use one of the following commands:

network (for example, network 192.168.0.0/24)

address range (for example, address range 192.168.0.30 192.168.0.50)

8. To set a newly created pool as a host pool, use one of the following commands:

host (for example, host 192.168.0.1)

Advertising
This manual is related to the following products: