Supporng FastIron Soware Release 08.0.95

CONFIGURATION GUIDE

RUCKUS FastIron DHCP

Conguraon Guide, 08.0.95

Part Number: 53-1005654-01

Publicaon Date: 11 September 2020

Copyright, Trademark and Proprietary Rights Informaon

©

2020 CommScope, Inc. All rights reserved.

technology subject to export control:

These items are controlled by the U.S. Government and authorized for export only to the country of ulmate desnaon for use by the ulmate

consignee or end-user(s) herein idened. They may not be resold, transferred, or otherwise disposed of, to any other country or to any person other

than the authorized ulmate consignee or end-user(s), either in their original form or aer being incorporated into other items, without rst

obtaining approval from the U.S. government or as otherwise authorized by U.S. law and regulaons.

Disclaimer

THIS CONTENT AND ASSOCIATED PRODUCTS OR SERVICES ("MATERIALS"), ARE PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND,

WHETHER EXPRESS OR IMPLIED. TO THE FULLEST EXTENT PERMISSIBLE PURSUANT TO APPLICABLE LAW, COMMSCOPE DISCLAIMS ALL

WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, FREEDOM FROM COMPUTER VIRUS, AND WARRANTIES ARISING FROM COURSE OF DEALING

IN NO EVENT SHALL COMMSCOPE, COMMSCOPE AFFILIATES, OR THEIR OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, SUPPLIERS, LICENSORS AND

THIRD PARTY PARTNERS, BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, PUNITIVE, INCIDENTAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES, OR

ANY DAMAGES WHATSOEVER, EVEN IF COMMSCOPE HAS BEEN PREVIOUSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, WHETHER IN AN

ACTION UNDER CONTRACT, TORT, OR ANY OTHER THEORY ARISING FROM YOUR ACCESS TO, OR USE OF, THE MATERIALS. Because some jurisdicons

do not allow limitaons on how long an implied warranty lasts, or the exclusion or limitaon of liability for consequenal or incidental damages,

some of the above limitaons may not apply to you.

Trademarks

ARRIS, the ARRIS logo, COMMSCOPE, RUCKUS, RUCKUS WIRELESS, the Ruckus logo, the Big Dog design, BEAMFLEX, CHANNELFLY, FASTIRON, ICX,

SMARTCELL and UNLEASHED are trademarks of CommScope, Inc. and/or its aliates. Wi-Fi Alliance, Wi-Fi, the Wi-Fi logo, Wi-Fi Cered, the Wi-Fi

CERTIFIED logo, Wi-Fi Protected Access, the Wi-Fi Protected Setup logo, Wi-Fi Protected Setup, Wi-Fi Mulmedia and WPA2 and WMM are

Document Convenons.............................................................................................................................................................................................. 7

Notes, Cauons, and Safety Warnings............................................................................................................................................................... 7

Command Syntax Convenons.................................................................................................................................................................................. 7

Document Feedback.................................................................................................................................................................................................. 8

RUCKUS Product Documentaon Resources............................................................................................................................................................. 8

Online Training Resources.......................................................................................................................................................................................... 8

Contacng RUCKUS Customer Services and Support................................................................................................................................................. 9

What Support Do I Need?.................................................................................................................................................................................. 9

Open a Case....................................................................................................................................................................................................... 9

Self-Service Resources........................................................................................................................................................................................9

DHCP Client.............................................................................................................................................................................................................. 17

DHCP Client Behavior on a Layer 3 Device....................................................................................................................................................... 18

DHCP Over Default Virtual Ethernet Port (Layer 3 Devices)............................................................................................................................. 18

Default Virtual Ethernet Port Creaon (Layer 3 Devices)................................................................................................................................. 18

Possible Reasons for Failure of Virtual Ethernet Port Creaon........................................................................................................................ 18

Enabling the DHCP Client for a Specic VE Port............................................................................................................................................... 19

DHCP Client in Connuous Discovery Mode (Layer 2 and Layer 3 Devices).....................................................................................................19

DHCP Client as a New Device........................................................................................................................................................................... 19

DHCP Client Behavior aer Reboot.................................................................................................................................................................. 21

BootP and DHCP relay parameters...........................................................................................................................................................................21

DHCP Auto-Provisioning Using the Manifest File Opon......................................................................................................................................... 26

DHCP Auto-Provisioning Enhancements.................................................................................................................................................................. 27

Conguring DHCP Auto-Provisioning Enhancements...............................................................................................................................................29

DHCP auto-provisioning opons.............................................................................................................................................................................. 30

Disabling or re-enabling the DHCP client ................................................................................................................................................................ 30

DHCP auto-provisioning on Layer 2 and Layer 3 devices......................................................................................................................................... 31

Scenario 1: DHCP auto-provisioning on a Layer 3 device................................................................................................................................. 32

Scenario 2: DHCP auto-provisioning with a TFTP server in a dierent network.............................................................................................. 33

Scenario 3: DHCP client connected through a DHCP snooping device.............................................................................................................33

Scenario 4: DHCP client opon 12................................................................................................................................................................... 34

Flash Image Download and Update ................................................................................................................................................................ 37

Auto-Provisioning Download and Update ....................................................................................................................................................... 37

Disabling or re-enabling auto-provisioning.............................................................................................................................................................. 38

Dynamic DHCP opons conguraon processing.................................................................................................................................................... 38

Discovery of SZ based on DHCP Opon 43 ..............................................................................................................................................................38

Conguraon notes and feature limitaons.................................................................................................................................................... 39

Verifying dynamic DHCP opons for a switch.......................................................................................................................................................... 40

Verifying dynamic DHCP opons for a router.......................................................................................................................................................... 42

DHCP Servers........................................................................................................................................................................................................... 45

Disabling or re-enabling the DHCP server on the management port.......................................................................................................................54

Seng the wait me for ARP ping response............................................................................................................................................................55

DHCP relay agent informaon support (opon 82) ................................................................................................................................................ 55

Enabling relay agent informaon (opon 82).......................................................................................................................................................... 55

Conguring the IP address of the DHCP server........................................................................................................................................................ 56

Conguring the boot image..................................................................................................................................................................................... 56

Deploying an address pool conguraon to the server........................................................................................................................................... 56

Specifying default router available to the client...................................................................................................................................................... 57

Specifying DNS servers available to the client......................................................................................................................................................... 57

Conguring the domain name for the client............................................................................................................................................................ 57

Vendor specic informaon (opon 43 and opon 60) conguraons................................................................................................................... 60

Conguring vendor details and vendor specic informaon (opon 43 and opon 60) ................................................................................ 60

Enabling stac IP to MAC address mapping............................................................................................................................................................. 61

Conguring Avaya IP telephony (opons 176 and 242)........................................................................................................................................... 62

Conguring WPAD (opon 252)............................................................................................................................................................................... 64

Displaying DHCP server informaon........................................................................................................................................................................ 65

DHCPv4 overview..................................................................................................................................................................................................... 67

DHCP Assist conguraon........................................................................................................................................................................................ 67

How DHCP Assist works................................................................................................................................................................................... 68

Disabling Syslog Messages for DAI................................................................................................................................................................... 75

Displaying ARP Informaon..............................................................................................................................................................................76

Conguring DAI to Support Mul-VRF............................................................................................................................................................. 76

Enabling Trust on a Port for a Specic VRF.......................................................................................................................................................77

DHCP Snooping........................................................................................................................................................................................................ 77

How DHCP Snooping Works............................................................................................................................................................................. 77

System Reboot and the Binding Database....................................................................................................................................................... 79

Conguraon Notes and Feature Limitaons for DHCP Snooping................................................................................................................... 79

Conguring DHCPv4 Snooping for Mul-VRF...................................................................................................................................................83

DHCP Relay Agent Informaon and Opon 82 Inseron......................................................................................................................................... 83

Conguraon Notes for DHCP Opon 82......................................................................................................................................................... 84

DHCP Opon 82 Sub-opons........................................................................................................................................................................... 85

DHCP Opon 82 Conguraon.........................................................................................................................................................................86

IP Source Guard........................................................................................................................................................................................................ 91

Conguraon Notes and Feature Limitaons for IP Source Guard.................................................................................................................. 92

Enabling IP Source Guard on a Port or Range of Ports..................................................................................................................................... 93

Dening Stac IP Source Bindings.................................................................................................................................................................... 94

Enabling IP Source Guard for a VLAN............................................................................................................................................................... 94

DHCPv6 Relay Agent Prex Delegaon Nocaon limitaons.....................................................................................................................102

Upgrade and downgrade consideraons....................................................................................................................................................... 102

Conguring DHCPv6 Relay Agent Prex Delegaon Nocaon................................................................................................................... 102

Enabling DHCPv6 Relay Agent Prex Delegaon Nocaon on an interface...............................................................................................103

Assigning the administrave distance to DHCPv6 stac routes..................................................................................................................... 103

Displaying DHCPv6 relay agent and prex delegaon informaon................................................................................................................ 104

Conguring the Stateless DHCPv6 Server on Layer 2 Soware Images......................................................................................................... 115

Conguring the Stateful DHCPv6 Server on Layer 2 Soware Images........................................................................................................... 118

Displaying DHCPv6 Server Informaon.......................................................................................................................................................... 120

Vericaon of DHCPv6 Server Status............................................................................................................................................................. 121

Vericaon in Linux Mode............................................................................................................................................................................. 122

Prex Delegaon............................................................................................................................................................................................ 122

Prex Delegaon for ICX DHCPv6 Servers in Layer 3 Soware Images.......................................................................................................... 122

Contacng RUCKUS Customer Services and Support

RUCKUS products, including:

Using these resources will help you to resolve some issues, and will provide TAC with addional data from your troubleshoong analysis if you sll

require assistance through a support case or RMA. If you sll require help, open and manage your case at hps://support.ruckuswireless.com/

case_management.

• DHCP Auto-Provisioning .......................................................................................................................................................... 24

• Auto-Provisioning Using the booile.bin Opon..................................................................................................................... 25

• DHCP Auto-Provisioning Using the Manifest File Opon......................................................................................................... 26

• Dynamic DHCP opons conguraon processing.................................................................................................................... 38

• Discovery of SZ based on DHCP Opon 43 .............................................................................................................................. 38

• Verifying dynamic DHCP opons for a switch.......................................................................................................................... 40

• Verifying dynamic DHCP opons for a router...........................................................................................................................42

DHCP Client

A host on an IP network can use BOOTP or DHCP to obtain its IP address from a BOOTP or DHCP server. To obtain the address, the client sends a

BOOTP or DHCP request.

The request is a subnet-directed broadcast and is addressed to UDP port 67. A limited IP broadcast is addressed to IP address 255.255.255.255 and

is not forwarded by the RUCKUS Layer 3 switch or other IP routers. When the BOOTP or DHCP client and server are on the same network, the server

receives the broadcast request and replies to the client. However, when the client and server are on dierent networks, the server does not receive

response from more than one server, the client acknowledges the rst response received, which is the default behavior.

obtained IP address is leased seamlessly. If the DHCP server responds in the negave, the previously obtained IP address will be released, and the

If the soware version is Layer 3, when the DHCP client comes up aer a reboot with a previously obtained IP address, the DHCP client sends the

DHCP request packets only on the ports where the DHCP client was enabled previously on the device.

BootP and DHCP relay parameters

The following parameters control the Layer 3 switch forwarding of BootP and DHCP requests:

requests from the client. The Layer 3 switch cannot forward a request to the server unless you congure a helper address for the server.

Gateway Address eld (somemes called the Router ID eld). When the server responds to the request, the server sends the response as

a unicast packet to the IP address in the Gateway Address eld. (If the client and server are directly aached, the Gateway ID eld is

empty, and the server replies to the client using a unicast or broadcast packet, depending on the server.)

The BootP/DHCP hop count is not the TTL parameter.

Conguring an IP helper address

device# configure terminal

2. Enter the interface conguraon mode.

device(config)# interface ethernet 1/1/2

3. Add a helper address for the server.

device(config-if-1/1/2)# ip helper-address 1 10.95.7.6

The commands in the example above add a helper address for server 10.95.7.6 to the port. If the port receives a client request for any of

the applicaons that the Layer 3 switch is enabled to forward, the Layer 3 switch forwards the client request to the server.

Conguring the BOOTP and DHCP reply source address

You can congure the device so that a BOOTP/DHCP reply to a client contains the server IP address as the source address instead of the router IP

address.

1. Enter the global conguraon mode by issuing the congure terminal command.

device# configure terminal

device(config)# ip helper-use-responder-ip

Changing the IP address used for stamping BootP and

DHCP requests

When a Layer 3 switch forwards a BootP or DHCP request, the Layer 3 switch "stamps" the Gateway Address eld.

device(config)# interface ethernet 1/1/1

3. Change the BootP or DHCP stamp address for requests received on port 1/1/1 to 10.157.22.26.

device(config-if-1/1/1)# ip bootp-gateway 10.157.22.26

The previous example changes the BootP or DHCP stamp address for requests received on port 1/1/1 to 10.157.22.26. The Layer 3 switch

will place this IP address in the Gateway Address eld of BootP or DHCP requests that the Layer 3 switch receives on port 1/1/1 and

forwards to the BootP or DHCP server.

device# configure terminal

device(config)# interface ethernet 1/1/1

device(config-if-1/1/1)# ip bootp-gateway 10.157.22.26

Changing the maximum number of hops to a BootP relay

You can change the maximum number of hops the Layer 3 switch allows for forwarded BootP or DHCP requests.

The BootP and DHCP hop count is not the TTL parameter.

device# configure terminal

2. Modify the maximum number of BootP or DHCP.

device(config)# bootp-relay-max-hops 10

The example allows the Layer 3 switch to forward BootP or DHCP requests that have passed through ten previous hops before reaching

the Layer 3 switch. Requests that have traversed 11 hops before reaching the switch are dropped. Since the hop count value inializes at

zero, the hop count value of an ingressing DHCP Request packet is the number of Layer 3 routers that the packet has already traversed.

DHCP Auto-Provisioning

DHCP auto-provisioning using the booile.bin uses the following process.

1. Once a lease is obtained from the server, the device uses the informaon from the DHCP server to contact the TFTP server to update the

image le.

switchover for auto-provisioning to start.

server is congured as manifest.txt.

name is congured, the client ignores the server IP address.

reachable. If the TFTP server is reachable, the DHCP client contacts the TFTP server only once.

example, if the DHCP client with a Layer 3 image downloads an updated Layer 2 image using opon 67, the conguraon download fails.

values specied in the string. However, these values cannot be used and the DHCP client behavior will not change based on the opon 67

conguraons.

stores the values specied in the string. However, these values cannot be used and the DHCP client behavior will not change based on the

opon 67 conguraons.

formaon once DHCP auto-provisioning is completed.

provisioning does not work because the DHCP client expects only a specied le type. Opon 67 must be recongured on the DHCP

server for the format supported for the parcular release.

High Availability and 802.1BR Consideraons

In an ICX stack, aer switchover between acve and standby devices, the DHCP process re-acquires IP addresses and follows the upgrade process.

DHCP is supported on 802.1BR-enabled devices as a normal stacking device. In a Campus Fabric (SPX) conguraon, the DHCP client is able to send

packets through all CB and PE ports. PE ports can be members of the VE.

Upgrade Consideraons

When upgrading from FastIron 08.0.60 or previous releases to FastIron 08.0.61 or later, if the rules to create the default VE are met, the default VE

is created, the DHCP client is enabled over the default VE, and the IP address is acquired.

How DHCP Client-Based Auto-Provisioning and Flash Image Update Works

or has been leased to another device, it is automacally rejected, and the device receives a new IP address from the server. If the exisng

address is valid, the lease connues.

4. If the exisng address is stac, the device keeps it and the DHCP client process is ended.

When the lease expires, the dynamic IP address is removed and the device contacts the DHCP server for a new address.

Flash Image Download and Update

proceeds with downloading the conguraon les.

image to ash memory. In a stacking conguraon, the device copies the ash image to ash in all stack member units.

The code determines which ash (primary or secondary) to use based on how the device is booted. In a stacking conguraon, the member units

use the same ash as the Acve Controller. Once the ash is updated with the newer ash image, the device is reloaded, and any member units in a

stacking conguraon are reloaded as well. If auto-provisioning is enabled, the DHCP client then proceeds to download the conguraon les.

Auto-Provisioning Download and Update

During auto-provisioning, the device requests the conguraon les from the TFTP server in the following order.

1. booile name provided by the DHCP server (if congured).

2. hostnameMAC-cong.cfg (for example: ICX001p-Switch0000.005e.4d00-cong.cfg).

download process ends.

Disabling or re-enabling auto-provisioning

DHCP auto-provisioning is enabled by default. You can disable or re-enable DHCP auto-provisioning on a switch or a router.

device# configure terminal

device(config)# no ip dhcp-client auto-update enable

device(config)# ip dhcp-client auto-update enable

Dynamic DHCP opons conguraon processing

It is not possible to manually congure the dynamic opon. If you aempt to congure a dynamic opon manually, an error is displayed stang

“Manual conguraon is not allowed for this opon."

If a stac IP Address is congured manually for the device aer obtaining a dynamic IP Address and DHCP opons from the DHCP server,

all DHCP opons are released along with the dynamic IP Address.

Discovery of SZ based on DHCP Opon 43

Beginning with SmartZone release 5.0, the administrator can monitor and manage switches and routers in the ICX 7000 series switches running

FastIron version 08.0.80 or above. ICX (the DHCP client) can parse the value of DHCP opon 43 containing SZ IP addresses received from the DHCP

server and connect to Smartzone.

This feature works in the following manner:

addresses are not passed to the FSM API.

subnet 192.168.12.0 netmask 255.255.255.0 {

range 192.168.12.100 192.168.12.199;

option routers 192.168.12.1;

option subnet-mask 255.255.255.0;

option broadcast-address 192.168.12.255;

option ntp-servers 192.168.11.22;

class "Ruckus AP" {

match if option vendor-class-identifier = "Ruckus CPE";

option vendor-class-identifier "Ruckus CPE";

default-lease-time 86400;

than lls the VSI opon data in the oer packet that is sent to client in response.

than 128 characters, the DHCP client does not save or process the received data.

corresponding data is in IP addresses format with commas (,) separang the IP addresses.

Verifying dynamic DHCP opons for a switch

device> show running-config

module 2 icx7250-sfp-plus-8port-80g-module

!

!

!

vlan 1 name DEFAULT-VLAN by port

!

!

!

hostname TestHostName dynamic

ip address 10.10.10.2 255.255.255.0 dynamic

device> show configuration

device(config)# clear ip dhcp-server binding *

The asterisk used in the example above clears all the IP addresses.

A FastIron device congured as a DHCP server can support up to 500 DHCP clients.

Where a FastIron device is congured as a DHCP server, you can congure DHCP opons. These opons are passed to the connected DHCP clients

and allow conguraon of parameters such as default router, host name, and domain name server.

The list of supported DHCP opons is shown in the following table: