---
title: "Configuring IPv4 Fixed Addresses"
canonical: "https://docs.infoblox.com/space/nios85/35482262/Configuring%20IPv4%20Fixed%20Addresses"
format: markdown
---
A fixed address represents a persistent link between an IP address and one of the following:

- MAC address
- Client identifier
- Circuit ID or remote ID in the DHCP relay agent option (option 82)

You can create fixed addresses as described in *<span style="color: #0000ff">[Adding](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26478175)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26478175)*<span style="color: #0000ff">[IPv4](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26478175)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26478175)*<span style="color: #0000ff">[Fixed](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26478175)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26478175)*<span style="color: #0000ff">[Addresses](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26478175)</span>* or from the Tasks Dashboard. For information about the Tasks Dashboard, see *<span style="color: #0000ff">[The](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35384239)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35384239)*<span style="color: #0000ff">[Tasks](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35384239)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35384239)*<span style="color: #0000ff">[Dashboard](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35384239)</span>*. You can also create a fixed address when you create a host record or when you convert an active, dynamically leased address to a fixed address. For more information, see *<span style="color: #0000ff">[Adding](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35384949/About+Host+Records#bookmark1217)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35384949/About+Host+Records#bookmark1217)*<span style="color: #0000ff">[Host](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35384949/About+Host+Records#bookmark1217)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35384949/About+Host+Records#bookmark1217)*<span style="color: #0000ff">[Records](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35384949/About+Host+Records#bookmark1217)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35384949/About+Host+Records#bookmark1217) and *<span style="color: #0000ff">[Converting](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784275/Managing+IPv4+and+IPv6+Addresses#ManagingIPv4andIPv6Addresses-bookmark1289)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784275/Managing+IPv4+and+IPv6+Addresses#ManagingIPv4andIPv6Addresses-bookmark1289)*<span style="color: #0000ff">[DHCP](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784275/Managing+IPv4+and+IPv6+Addresses#ManagingIPv4andIPv6Addresses-bookmark1289)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784275/Managing+IPv4+and+IPv6+Addresses#ManagingIPv4andIPv6Addresses-bookmark1289)*<span style="color: #0000ff">[Leases](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784275/Managing+IPv4+and+IPv6+Addresses#ManagingIPv4andIPv6Addresses-bookmark1289)</span>*.  
When you create a fixed address, you must define a host identifier that the DHCP server uses to match the DHCP client. Every time the DHCP client with the matching identifier requests an IP address, the DHCP server assigns it the same address.  
When a DHCP client sends a DHCPDISCOVER, it can include the MAC address or a unique client identifier as option 61 in the DHCP section of the packet. Using a client identifier is especially useful for virtualized server processes that might be moved to different hardware platforms. For information about option 61, refer to *RFC2132,* *DHCP* *Options* *and* *BOOTP* *Vendor* *Extensions*. You can select either the MAC address or client identifier as the host identifier in a fixed address. The DHCP server matches the option 61 value in the client request using either the MAC address or client identifier, depending on your configuration. When a DHCP client renews an IP address using a matching MAC address or client identifier, the DHCP server tracks the allocation of IP addresses and reserves the same IP address for the client.  
When you enter a MAC address, you can use one of the following form> Macro (anchor)

ats:

- aa:bb:cc:dd:ee:ff — Six groups of two hexadecimal digits separated by colons (:)
- aa-bb-cc-dd-ee-ff — Six groups of two hexadecimal digits separated by hyphens (-)
- aabb.ccdd.eeff — Three groups of four hexadecimal digits separated by periods (.)
- aabbcc-ddeeff — Two groups of six hexadecimal digits separated by a hyphen (-)
- aabbccddeeff — One group of 12 hexadecimal digits without any separator

After you save the entry, the appliance displays the MAC address in the AA:BB:CC:DD:EE:FF format.  
When a DHCP client requests an IP address through a DHCP relay agent, the agent adds either the circuit ID or remote ID <span style="color: #3e3f40">or both, </span>to the DHCP relay agent information option (option 82). For information, see *<span style="color: #0000ff">[About](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)*<span style="color: #0000ff">[the](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)*<span style="color: #0000ff">[DHCP](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)*<span style="color: #0000ff">[Relay](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)*<span style="color: #0000ff">[Agent](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)*<span style="color: #0000ff">[Option](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)*<span style="color: #0000ff">[(Option](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)*<span style="color: #0000ff">[82)](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818/About+IPv4+DHCP+Options#AboutIPv4DHCPOptions-bookmark2275)</span>*. When you select the DHCP relay agent option (circuit ID or remote ID) as the host identifier in a fixed address, the DHCP server matches the DHCP client request using either the circuit ID or the remote ID, depending on your configuration. When a DHCP client renews an IP address using a matching relay agent ID, the DHCP server tracks the allocation of IP addresses and reserves the same IP address for the client. Note that leases are not renewed at the standard renewal time (T1) when option 82 information is not available as a unicast renewal. Instead, leases are renewed at the rebinding time (T2) when renewals are sent as broadcasts to the relay agents and contain option 82 information. For information about how to configure the lease time, see *<span style="color: #0000ff">[Configuring](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784910)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784910)*<span style="color: #0000ff">[General](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784910)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784910)*<span style="color: #0000ff">[IPv4](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784910)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784910)*<span style="color: #0000ff">[DHCP](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784910)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784910)*<span style="color: #0000ff">[Properties](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784910)</span>*.

# > Macro (anchor)

> Macro (anchor)

> Macro (anchor)

Adding IPv4 Fixed Addresses

For Cloud Network Automation, you can create IPv4 fixed addresses within the delegation authority of a Cloud Platform Appliance. The newly created fixed address is forwarded to the Cloud Platform Appliance. For information, see *<span style="color: #0000ff">[About](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35979476)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35979476)*<span style="color: #0000ff">[Authority](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35979476)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35979476)*<span style="color: #0000ff">[Delegation](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35979476)</span>*.  
To add an IPv4 fixed address:

1. Navigate to the network to which you want to add a fixed address, and then select **Fixed** **Address** from the Add drop-down menu.  
or  
From any panel in the **DHCP** tab, expand the Toolbar and click **Add** -> **Fixed** **Address** -> **IPv4**.
2. In the *Add** IPv4** Fixed** Address* wizard, select one of the following and click **Next**:
  - **Add**** Fixed**** Address**   
or
  - **Add ****Fixed**** Address**** using**** Template**

Click **Select** **Template** and select the template that you want to use. Note that when you use a template to create a fixed address, the configurations of the template apply to the new address. The appliance automatically populates the fixed address properties in the wizard. You can then edit the pre-populated properties.

> Macro (legacy-content)

> ⚠️ **Note**
> ⚠️ 
> ⚠️ You cannot use the same circuit ID or remote ID for different fixed addresses if the addresses are in the same network or the same shared network.


d.** Name**: Enter a name for the Fixed Address. This field is required if the network is served by a Microsoft server. For information, see *<span style="color: #0000ff">[Adding](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849349/Managing+Synchronized+DHCP+Data#ManagingSynchronizedDHCPData-bookmark2726)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849349/Managing+Synchronized+DHCP+Data#ManagingSynchronizedDHCPData-bookmark2726)*<span style="color: #0000ff">[Fixed](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849349/Managing+Synchronized+DHCP+Data#ManagingSynchronizedDHCPData-bookmark2726)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849349/Managing+Synchronized+DHCP+Data#ManagingSynchronizedDHCPData-bookmark2726)*<span style="color: #0000ff">[Addresses/Microsoft](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849349/Managing+Synchronized+DHCP+Data#ManagingSynchronizedDHCPData-bookmark2726)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849349/Managing+Synchronized+DHCP+Data#ManagingSynchronizedDHCPData-bookmark2726)*<span style="color: #0000ff">[Reservations](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849349/Managing+Synchronized+DHCP+Data#ManagingSynchronizedDHCPData-bookmark2726)</span>*[.](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849349/Managing+Synchronized+DHCP+Data#ManagingSynchronizedDHCPData-bookmark2726)

e.** Comment:** Optionally, enter additional information about the fixed address.

f.** Disabled:** Select this if you do not want the DHCP server to allocate this IP address at this time.

The **Cloud** section appears when the Cloud Network Automation license is installed on the Grid Master. For information, see *<span style="color: #0000ff">[Deploying](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35881011)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35881011)*<span style="color: #0000ff">[Cloud](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35881011)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35881011)*<span style="color: #0000ff">[Network](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35881011)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35881011)*<span style="color: #0000ff">[Automation](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35881011)</span>*. This section displays the following information:

- **Cloud** **Usage**: This field indicates whether this object is associated with any specific cloud extensible attributes or within a scope of delegation. It can be one of the following:
  - **Cloud** **from** **adapter**: Indicates that this object has been created by a cloud adapter and it may or may not be within a scope of delegation at the moment.
  - **Cloud** **from** **delegation**: Indicates that this object is within the scope of delegation or the object itself defines a scope of authority delegation, and it is not created by a cloud adapter.
  - **Used** **by** **cloud**: Indicates that this network or network container is associated with the extensible attribute **Is** **External** or **Is** **Shared** and the value is set to True, which implies the network is a private or shared network managed by the CMP, and it is not **Cloud** **from** **adapter** or **Cloud** **from** **delegation**.
  - **Non-cloud**: The object is a regular NIOS object and is not within the scope of any authority delegation nor is it associated with any of these extensible attributes: **Cloud** **API** **Owned,** **Is** **External** or **Is** **Shared**. NIOS admin users can modify this object based on their permissions.
- **Owned** **By**: A cloud object can be owned by the Grid Master or the cloud adapter. When the object is created by the Grid Master, this shows **Grid**. If the object is created by the cloud adapter, this shows **Adapter**.

**Delegate** **authority** **from** **the** **Grid** **Master**

> Macro (legacy-content)

4. (Optional) Click **Next** to configure or override DHCP options as described in *<span style="color: #0000ff">[About](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818)*<span style="color: #0000ff">[IPv4](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818)*<span style="color: #0000ff">[DHCP](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818)*<span style="color: #0000ff">[Options](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35946818)</span>*.

5. (*Applies** only** to** Network** Insight*) *This** step** is** not** required** for **creating** a** new** Fixed** Address*. In the following Wizard step, you can optionally define the following identification values and settings for the new object's port reservation:

> Macro (legacy-content)

6. Click **Next** to initiate or disable discovery of the new Fixed Address. (*Applies* *only* *to* *Network* *Insight*) *This* *step* *is* *not* *required* *for* *creating* *a* *new* *Fixed* *Address*.

> Macro (legacy-content)

> ⚠️ **Note**
> ⚠️ 
> ⚠️ For descriptions of SNMP credentials for discovery, see the section *<span style="color: #0000ff">[Configuring](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1415)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1415)*<span style="color: #0000ff">[SNMP1/v2](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1415)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1415)*<span style="color: #0000ff">[Credentials](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1415)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1415)*<span style="color: #0000ff">[for](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1415)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1415)*<span style="color: #0000ff">[Polling](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1415)</span>* and *<span style="color: #0000ff">[Configuring](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1417)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1417)*<span style="color: #0000ff">[SNMPv3](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1417)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1417)*<span style="color: #0000ff">[Properties](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1417)</span>*. These Grid-based values are inherited, by default, by each new object you create.


- For the new object, you can check the **Override** **CLI** **Credentials** checkbox to override the inherited set of CLI credentials taken from the Grid level. This set of credentials may be used for the device that is directly associated with the new object in its port reservation.
- You can also click **Test**** CLI**** Credentials** to enter and test a set of CLI login credentials against a device based on its IP address.  
Port control operations require CLI credentials for the involved devices. (If you are not using port control for the new object, usage of CLI credentials is optional.) Because some IPAM and DHCP objects will use port control features as part of object creation, CLI credentials are automatically leveraged as part of discovery. Ensure you have the correct sets of CLI credentials for devices in your network. For more information, see the section *<span style="color: #0000ff">[Configuring](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1419)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1419)*<span style="color: #0000ff">[CLI](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1419)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1419)*<span style="color: #0000ff">[Discovery](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1419)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1419)*<span style="color: #0000ff">[Properties](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark1419)</span>*.
- SSH is the default for CLI operations. Check the **Allow** **Telnet** checkbox if you know the device involved in the object assignment may support Telnet but may not support SSH, or if you want Telnet as an option.

7. Click **Next** to define port connectivity for the device port that will be associated with the new object. *This** step** is** not** required** for** creating** a** new** Fixed** Address*. This feature set is also termed *port**control* in the NIOS/Grid Manager system. The device whose interface the new Fixed Address will be associated should already be discovered by Network Insight.

> Macro (legacy-content)

8. Click **Next** to enter values for required extensible attributes or add optional extensible attributes. For information, see *<span style="color: #0000ff">[Using](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)*<span style="color: #0000ff">[Extensible](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)*<span style="color: #0000ff">[Attributes](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>*. When you create a new fixed address whose authority is delegated to a Cloud Platform Appliance, the required cloud extensible attributes and their values are automatically populated.

You need to assign a **Subscriber Member Site** to add subscriber service related extensible attribute in order to populate Subscriber Cache.

9. As the final step in the Add Fixed Address wizard, you define when Grid Manager creates the new object by scheduling it. You also schedule when the associated port control task executes (if a port configuration is specified).

> Macro (legacy-content)

     10. Choose one of the following from the **Save****&****...** drop-down button menu:

> Macro (legacy-content)

> ⚠️ **Note**
> ⚠️ 
> ⚠️ At any step during the wizard, you can click **Schedule** **for** **Later** to schedule the task. In the *Schedule* *Change* panel, enter a date, time, and time zone. For information, see *<span style="color: #0000ff">[Scheduling](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35446174)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35446174)*<span style="color: #0000ff">[Tasks](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35446174)</span>*[.](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35446174) You cannot schedule this task when you are creating an object that is within a delegated scope.
> ⚠️ 
> ⚠️ For information on viewing fixed addresses and other DHCP objects, see *<span style="color: #0000ff">[Viewing](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35850146)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35850146)*<span style="color: #0000ff">[IPv4](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35850146)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35850146)*<span style="color: #0000ff">[DHCP](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35850146)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35850146)*<span style="color: #0000ff">[Objects](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35850146)</span>*.

#   
> Macro (anchor)

> Macro (anchor)

> Macro (anchor)

Modifying IPv4 Fixed Addresses

To modify the settings of a fixed address:

1. From the **Data** **Management** tab, select the **DHCP** tab -> **Networks** tab -> **Networks** section -> *network* ->* fixed_address* checkbox, and then click the Edit icon.
2. The *Fixed* *Address* editor contains the following tabs from which you can modify settings:

> Macro (legacy-content)

     3. Optionally, you can click **Toggle ****Advanced**** Mode** to display the following tabs from which you can modify advanced data.

> Macro (legacy-content)

Note that Grid Manager displays both the basic and advanced tabs the next time you log in to the GUI.

     4. Save the configuration and click **Restart** if it appears at the top of the screen.

> ⚠️ **Note**
> ⚠️ 
> ⚠️ At any step during the wizard, you can click **Schedule** **for** **Later** to schedule the task. In the *Schedule* *Change* panel, enter a date, time, and time zone. For information, see *<span style="color: #0000ff">[Scheduling](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35446174)</span>*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35446174)*<span style="color: #0000ff">[Tasks](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35446174)</span>*[.](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35446174) You cannot schedule this task when you are creating an object that is within a delegated scope.


# > Macro (anchor)

> Macro (anchor)

> Macro (anchor)

Deleting Fixed Addresses

To delete a fixed address within the DHCP range:

1. From the **Data** **Management** tab, select the **DHCP** tab -> **Networks** tab -> **Networks** section -> *network* -> *fixed_address* checkbox or checkboxes. You cannot delete multiple fixed addresses at the same time if the authority for one of the fixed addresses is delegated to a Cloud Platform Appliance.
2. Select **Delete** from the **Delete** drop-down list.
3. In the *Delete* *Confirmation* dialog box, do the following:

> Macro (legacy-content)

> ⚠️ **Note**
> ⚠️ 
> ⚠️ NIOS removes all the static leases associated with a fixed address when you delete a fixed address out of the DHCP range, regardless of the selection of the **Delete**** associated ****leases**** with**** the ****fixed**** address ****(selected**** fixed ****IP ****address)** checkbox in the *Delete** Confirmation* dialog box.


To schedule the fixed address deletion:

1. From the **Data** **Management** tab, select the **DHCP** tab -> **Networks** tab -> **Networks** section -> *network* ->* fixed_address* checkbox.
2. Select **Schedule** **Delete** from the **Delete** drop-down list.
3. In the *Schedule* *Deletion* dialog box, complete the following:
  - **Delete** **Now**: Select this to delete the object upon clicking **Delete** **Now**.
  - **Delete** **Later**: Select this to schedule the deletion at a later date and time. Complete the following:
    - **Date**: Enter the date in YYYY-MM-DD (year-month-day) format. The appliance displays today's date. You can also click the calendar icon to select a date from the calendar widget.
    - **Time**: Enter the time in hh:mm:ss AM/PM (hours:minutes:seconds AM or PM) format. You can also select a time from the drop-down list by clicking the time icon.
    - **Time** **Zone**: Select a time zone for the scheduled date and time from the drop-down list. This field displays the time zone of the browser that the admin uses to log in to Grid Manager.
  - **Delete** **associated** **leases** **with** **the** **fixed** **address**: Select this checkbox to delete all the leases associated with the fixed address.
4. Click **Schedule** **Deletion**.

The appliance performs the deletion at the scheduled date and time, and puts all deleted objects in the Recycle Bin, if enabled. You can restore the objects if necessary.