Page tree

Contents

When you create an IPv4 network, you can do so from scratch or from a network template that contains predefined properties. When you use a template to create a network, the properties of the template apply to the new network. For information about network templates, see About IPv4 Network Templates. You can also create an IPv4 network from the Tasks Dashboard, as described in Tasks Dashboard.

After you create IPv4 networks, you can combine them into shared networks or create ranges and fixed addresses.

Adding IPv4 Networks

When you configure an IPv4 network, you must assign either Grid members or Microsoft servers to the network. A network cannot be served by a mix of Microsoft and Infoblox DHCP servers. Multiple servers can serve a network, but Grid members and Microsoft servers cannot serve the same network.

A Grid member can serve only one network view. Similarly, a Microsoft server can serve only one network view. Therefore when you assign Grid members to networks, you must assign the members to networks in the same network view. For information, see Managing IPv4 DHCP Data.

If you have enabled support for RIR (Regional Internet Registry) updates and are adding an RIR IPv4 network container or network to NIOS, Grid Manager displays an RIR section in the Add IPv4 Network wizard. You must enter RIR related information in this section in order for NIOS to associate the newly added network with an RIR organization. For more information about RIR address allocation and updates, see RIR Registration Updates.

To add an IPv4 network, complete the following:

  1. From the Data Management tab, select the DHCP tab -> Networks tab.
  2. In the Networks section, expand the Toolbar and click the Add drop-down list and select Network -> IPv4 network or, click the Add icon drop-down list and select IPv4 Network. 
  3. In the Add Network wizard, select one of the following and click Next:
    • Add Network: Click this to add a network from scratch.
    • Add Network using Template: To use a template, click this, and then click Select Template and select a network template. For information, see About IPv4 Range Templates. The appliance populates the template properties in the wizard when you click Next. You can then edit the pre-populated properties, except for Netmask.
  4. Complete the following and then click Next:
    • Regional Internet Registry: This section appears only when support for RIR updates is enabled. For information about RIR, see RIR Registration Updates. Complete the following to create an RIR IPv4 network container or network:
      • Internet Registry: Select the RIR from the drop-down list. The default is RIPE. When you select None, the network is not associated with an RIR organization.
      • Organization ID: Click Select Organization and select an organization from the RIR Organization Selector dialog box.
      • Registration Status: The default is Not Registered. When adding an RIR allocated network, you can change this to Registered and select the Do not update registrations check box below. Note that when you select API as the communication method, the registration status will be updated automatically after the registration update is completed. However, when you select Email as the communication method, the registration status will not be automatically updated. If you are creating a new network and the registration update is completed successfully, the status will be changed to Registered. If the update fails, the status will be changed to Not Registered. The updated status and timestamp are displayed in the Status of last update field in the IPv4 Network Container or IPv4 Network editor.
      • Registration Action: Select the registration action from the drop-down list. When you select Create, the appliance creates the IPv4 network and assigns it to the selected organization. When you select None, the appliance does not send registration updates to RIPE. When you are adding an existing RIR allocated network to NIOS, select None. When you are adding networks to an RIR allocated network (a parent network), select Create. Ensure that the parent network associated with an RIR organization already exists.
      • Do not update registrations: Select this check box if you do not want the appliance to submit RIR updates to RIPE. By default, the appliance sends updates to the RIR database based on the configured communication method.
    • Network View: This appears only when you have multiple network views. From the drop-down list, select the network view in which you want to create the network.
    • Netmask: Enter the netmask or use the netmask slider to select the appropriate number of subnet mask bits for the network. The appliance supports /1 to /32 netmasks. Note that when you use a template that contains a fixed netmask, you cannot adjust the netmask for this network.
      Microsoft servers can serve networks with /1 to /31 netmasks. Infoblox DHCP servers can serve networks with /8 to /32 netmasks.
      Since Infoblox DHCP servers do not support /1 to /7 networks, you can assign these networks to Microsoft DHCP servers only. You can create DHCP ranges and fixed addresses within these subnets.
    • Networks: Do one of the following to add new networks:
      • Click the Add icon to enter a new network. Grid Manager adds a row to the table. Enter the network address in the Network field. Click the Add icon again to add another network.

        Or

      • Click the Next Available icon to have the appliance search for the next available network. Complete the following in the Next Available Networks section:
      • Create new network(s) under: Enter the network container in which you want to create the new network. When you enter a network that does not exist, the appliance adds it as a network container. When you enter a network that is part of a parent network, the parent network is converted into a network container if it does not have a member assignment or does not contain address ranges, fixed addresses, reservations, shared networks, and host records that are served by DHCP. When you enter a network that has a lower CIDR than an existing network, the appliance creates the network as a parent network and displays a message indicating that the newly created network overlaps an existing network. You can also click Select Network to select a specific network in the Network Selector dialog box. For information about how the appliance searches for the next available network, see Obtaining the Next Available.
      • Number of new networks: Enter the number of networks you want to add to the selected network container. Note that if there is not enough network space in the selected network to create the number of networks specified here, Grid Manager displays an error message. The maximum number is 20 at a time. Note that when you have existing networks in the table and you select one, the number you enter here includes the selected network.
      • Click Add Next to add the networks. Grid Manager lists the networks in the table. You can click Cancel to reset the values.

Note

You must click Add Next to add the network container you enter in the Next Available Networks section. If you enter a network in the Next Available Networks section and then use the Add icon to add another network, the appliance does not save the network you enter in the Next Available Networks section until you click Add Next.


  • Comment: Enter useful information about the network, such as the name of the organization it serves.
  • The Sync to MGM drop-down list is available only on the managed Grid when it remains joined with the Multi-Grid Master. Select one of the following from the Sync to MGM drop-down list:
    • Yes: Select this to enable synchronization of networks between the managed Grid and Multi-Grid Master.
    • No: Select this to disable synchronization of networks between the managed Grid and Multi-Grid Master.

Note

If you have selected No at the parent network (disabled synchronization) and if you try to select Yes when adding a child network, the appliance returns an error. This means that you cannot override the settings at the child level if you have already restricted synchronization at the parent network.


    • Use Inherited Setting: Select this is to inherit synchronization settings from the parent object.
  • Automatically Create Reverse-Mapping Zone: This function is enabled if the netmask of the network equals /8, /16, or /24. Select this to have the appliance automatically create reverse-mapping zones for the network. A reverse-mapping zone is an area of network space for which one or more name servers have the responsibility for responding to address-to-name queries. These zones are created in the DNS view assigned to receive dynamic DNS updates at the network view level.
  • Disable for DHCP: Select this if you do not want the DHCP server to provide DHCP services for this network at this time. This feature is useful when you are in the process of setting up the DHCP server. Clear this after you have configured the server and are ready to have it serve DHCP for this network. Note that disabling an IPv4 network may take a longer time to complete depending on the size of the data.

The Cloud section appears when the Cloud Network Automation license is installed on the Grid Master. For information, see Deploying Cloud Network Automation.

To delegate authority for this network, complete the following:

Delegate authority from the Grid Master

  • Delegate To: This field indicates whether the authority for the network you want to create has already been delegated to a Cloud Platform Appliance. Click Select to choose the Cloud Platform Appliance to which you want to delegate authority. The Member Selector displays only Cloud Platform Appliances in the Grid. Click the member, and Grid Manager displays the member name next to this field. This cloud member now assumes authority for this network, and the Grid Master does not have authority anymore. You can also click Clear to remove authority delegation from the selected Cloud Platform Appliance and return authority back to the Grid Master.

5. Click Next and add a Grid member or Microsoft server as a DHCP server for the network. A network can be served by either Grid members or Microsoft servers, but not both at the same time.

    • Click the Add icon and select one of the following options:
      • Add Infoblox Member: Select this option to add a Grid member as a DHCP server for the network. Select the Grid member from the Member Selector dialog box. Keep in mind, DHCP properties for the network are inherited from this member. The network can be served by multiple members, but a member can serve networks in one network view only.

        Or
      • Add Microsoft Server: Select this option to add a Microsoft server as a DHCP server for the network. Select the Microsoft server from the Microsoft Server Selector dialog box.

6. Click Next to associate Active Directory Sites with the network. For more information, see Associating Active Directory Sites with Networks.

7. Click Next to override DHCP properties as described in Configuring DHCP Properties. This only applies if you are adding a network that is served by an Infoblox Grid member.

Or

8. (Applies only with Network Insight) Click Next to initiate or disable discovery of the new network(s). This step is not required for creating a new network. Discovery settings differ based on whether you are defining one network or multiple networks.

Or

    • Configuring more than one network: If the networks are child networks, they automatically inherit the settings of the parent network, including discovery settings and the discovery member. Discovery is disabled for any parent networks. These settings will not appear in the wizard page. For discovery of multiple networks, you can only enable or disable Immediate Discovery.

9. Assign VLAN objects to the network. For more information, see VLAN Management.

10. As part of creating a network in IPAM or DHCP, you can provision the network on an actual device (switch, router, or switch-router), that is discovered and managed through the Grid Manager.

    • Begin by checking the Enable Network Provisioning check box, and clicking the Select Device button. Choose your device from the Device Selector dialog. Click Clear to remove the setting. For more information, see the section Using the Device Selector.
    • If you performed DHCP configuration in the previous step of the Add Network Wizard, the Router IP value will automatically be populated with the DHCP Router IP address value. Otherwise, you enter the standard router IP address.
      • For example, if Grid Manager discovers and manages a router 172.16.22.1, the IP value 172.16.22.1 should be entered in the Router IP field.
    • F required for the newly provisioned network to ensure that attached devices receive DHCP auto-configuration, enable the DHCP Forwarding check box. For this setting, if a DHCP Failover was previously configured, the IP addresses defined for DHCP failover are automatically used for the DHCP forwarding configuration.
    • You will also need to choose an interface on the selected device on which to provision the network by selecting it from the Interface drop-down menu. Grid Manager ensures that only those interfaces that can support provisioning, and are available for provisioning (that do not have an Operation Status of Up), appear in the drop-down menu.
    • Otherwise, when creating networks and provisioning them on managed devices, you can create a VLAN on which to provision the network by clicking the Create VLAN option and entering the VLAN Name and VLAN ID. Ensure that the VLAN ID value you enter is appropriate for the application. Do not create a new VLAN and provision a network for a VLAN value that is already actively carrying traffic for another routing domain.
      If a selected device does not support VLANs, the Create VLAN option will not appear.

11. Click Next to enter values for required extensible attributes or add optional extensible attributes. For information, see Managing Extensible Attributes.

If you are adding an RIR network, the RIR network attribute table appears. For information about these attributes and how to enter them, see RIR Network Attributes. You can preview the information before the appliance submits updates to the RIPE database. To preview registration updates, click Preview RIR Submissions. For more information, see Previewing Registration Updates.

Note

You cannot leave an optional RIR attribute value empty. If you do not have a value for an RIR attribute, you must delete it from the table. You can enter up to 256 characters for all RIR attributes.

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

12. As the final step in the Add IPv4 Network wizard, you define when Grid Manager provisions the new network by scheduling it. You also schedule when the associated port control task executes (if a port configuration has been specified).

    • To create the new network and its associated port configuration immediately, select Now. Grid Manager synchronizes the port control task to take place at the same time as the creation of the new network.
    • You can choose to have Grid Manager execute the port control task at a later time by selecting Later.
    • Choose a Selected time by entering or selecting a Start Date (click the calendar icon to choose a calendar date) and a Start Time, and choose a Time Zone.

     13. Choose one of the following from the Save & ... drop-down menu:

  • Click Save & Close to add the new network and close the wizard (this is the default).
  • Click Save & Edit to add the new network and launch the editor.
  • Click Save & New to add the new network and launch the wizard again to add another network.

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 Scheduling Tasks.


After you create a network, you can perform the following:

  • Use the split network feature to create subnets for the network. For information, see Splitting IPv4 Networks into Subnets.
  • Use the join networks feature to create a parent network that encompasses multiple subnets into a larger network. For information, see Joining IPv4 Networks. You can also create a shared network for subnets that are on the same network segment.

Networks served by Microsoft servers do not support the split and join functions.

Viewing Networks

You can view IPv4 networks from the IPAM tab -> Net Map and List panels. The Net Map panel provides a graphical view of your networks and the List panel displays the networks in table format. For more information, see IPv4 Network Map and IPAM Home.

You can also view a list of IPv4 and IPv6 networks in the DHCP tab -> Networks tab -> Networks panel. This panel displays all IPv4 and IPv6 networks.

In any of these panels, you can use filters or the Go to function to navigate to a specific network. You can also create a quick filter to save frequently used filter criteria. For information, see Using Quick Filters. You can add, delete, or edit a network. You can also monitor the DHCP utilization of a selected network.

When viewing networks, you can choose to view them in one of the following views:

  • Click Toggle Hierarchical View to view networks hierarchically in a parent-child structure (networks in a network container). You can view detailed information about the networks by clicking the network link and drilling down to the lowest hierarchical level, and then opening a network. To go back to a previous hierarchical view, click the link of the corresponding level in the breadcrumb. The hierarchical view is the default view.
  • Click Toggle Flat View to display a flat list of all networks and network containers. The parent and child networks are listed separately in the flat view.

Depending on where you view your networks, Grid Manager displays some of the following information by default. You can also select specific information for display.

  • Network: The network address.

The network is displayed in one of the following colors:

    • Yellow: The network is unmanaged.
    • Blue: The selected network.
    • Gray: The network is currently not available as a NIOS network object.
  • Comment: The information you entered about the network.
  • IPAM Utilization: This information is available for IPv4 networks only. It displays the percentage based on the IP addresses in use divided by the total addresses in the network. For example, in a /24 network, if there are 25 static IP addresses defined and a DHCP range that includes 100 addresses, the total number of IP addresses in use is 125. Of the possible 256 addresses in the network, the IPAM utilization is about 50% for this network. The appliance updates the IPAM utilization data immediately for a network container, but for a network, it is updated every 15 minutes.
    The IPAM utilization data is displayed in one of the following colors:
    • Red: The IPAM utilization percentage is above the configured Trigger value.
    • Blue: The IPAM utilization percentage is below the configured Trigger value.
  • Site: The site to which the network belongs. This is one of the predefined extensible attributes.
  • Protocol: Displays whether the network is an IPv4 or IPv6 network.
  • Disabled: Indicates if the network is disabled. You can double-click a row and select the check box in this column to disable the network. Grid Manager displays a warning message when you select the check box. Click Yes to confirm or No to cancel. Note that disabling an IPv4 network may take a longer time to complete depending on the size of the data.
  • Leaf Network: Indicates whether the network is a leaf network or not. A leaf network is a network that does not contain other networks.
  • IPv4 DHCP Utilization: This information is available for IPv4 networks only. It displays the percentage of the total DHCP usage of theIPv4 network. This is the percentage of the total number of DHCP hosts, fixed addresses, reservations, and active leases in the network divided by the total number of IP addresses (excluding IP addresses in the exclusion range) and all DHCP objects in the network. Note that only enabled addresses are included in the calculation. It does not include abandoned addresses or leases. The appliance updates the utilization data approximately every 15 minutes. The utilization data is displayed in one of the following colors:
    • Red: The DHCP resources are 100% utilized.
    • Yellow: The DHCP utilization percentage is over the effective high-water mark threshold.
    • Blue: The DHCP utilization percentage is below the effective low-water mark threshold.
    • Black: The DHCP utilization percentage is at any number other than 100%, or it is not above and below any threshold.

You see the following when RIR is enabled (for more information, see RIR Registration Updates):

  • RIR Organization: This appears only if support for RIR updates is enabled. This displays the name of the RIR organization to which the network is assigned.
  • RIR Organization ID: This appears only if support for RIR updates is enabled. This displays the ID of the RIR organization to which the network is assigned.
  • RIR Registration Status: This appears only if support for RIR update is enabled. This field displays the RIR registration status. This can be Registered or Not Registered. Registered indicates that the network has a corresponding entry in the RIPE database.
  • Last Registration Updated: Displays the timestamp when the last registration was updated. The displayed timestamp reflects the timestamp used on the Grid Master.
  • Status of Last Registration Update: Displays the registration status and communication method of the last registration update. The status can be Pending, Sent, Succeeded, or Failed. Each time you send a registration update to create, modify, or delete a network container or network, the updated status will be displayed here. If you have selected not to send registration updates, the previous status is retained.

You see the following only with Network Insight (For information, see Infoblox Network Insight):

  • Discovery Enabled: Indicates whether discovery is allowed on the network container or the network.
  • Managed: Indicates whether the network is set to Managed status under NIOS.
  • First Discovered: The date and timestamp of the first occasion that NIOS discovered the network.
  • Last Discovered: The date and timestamp of the last occasion that NIOS performed discovery on the network.

You see the following when the Cloud Network Automation license is installed on the Grid Master (For information, see Deploying Cloud Network Automation):

  • Cloud Usage: This field indicates whether this object is associated with any specific cloud extensible attributes or within the 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 Cloud Platform member, this shows Grid. If the object is created by the cloud adapter, this shows Adapter.
  • Delegated To: This tells you whether a cloud object has been delegated to a Cloud Platform Appliance or not. If the cloud object has a parent object and the parent has been delegated, this field shows the parent delegation and you cannot modify the field.
  • Extensible attributes (Building, Country, Region, State, and VLAN): You can select the extensible attributes such as Building, Country, Region, State, and VLAN for display. When you enable other features such as RIR, Network Insight, and Cloud Network Automation, you can select additional attributes for display.

You can sort the list of networks in ascending or descending order by certain columns. For information about customizing tables in Grid Manager, see Customizing Tables.

You can also modify some of the data in the table. Double-click a row of data, and either edit the data in the field or select an item from a drop-down list. Note that some fields are read-only. For more information about this feature, see Modifying Data in Tables. You can edit values of inheritable extensible attributes by double-clicking on the respective row. If an extensible attribute has an inherited value, then the cell is highlighted in blue when you perform an inline editing. The Descendant Actions dialog box is displayed when you click Save. For information, see Managing Inheritable Extensible Attributes at the Parent and Descendant Level. If you delete the value of an inheritable extensible attribute at the parent level, you can choose to preserve the descendant value or remove it. For information, see Deleting Inheritable Extensible Attributes Associated with Parent Objects.

Viewing Network Details

You can view detailed information about a specific network by clicking the network link. Grid Manager displays the objects in the network, including DHCP ranges, hosts, fixed addresses and roaming hosts. It displays the following information about the network:

  • IP Address: The IP address of a DHCP object, such as a DHCP range, fixed address, reservation, host configured for DHCP, or roaming host with an allocated IP address. For a DHCP range, this field displays the start and end addresses of the range. For a host that has multiple IP addresses, each IP address is displayed separately. Note that the appliance highlights all disabled DHCP objects in gray.
    The IP address is displayed in one of the following colors:
    • Yellow: The IP address is unmanaged.
    • Blue: The IP address is excluded.
    • Pink: Indicates IP address conflicts.
    • Gray: The IP address is currently not available as a NIOS object.
  • Type: The DHCP object type, such as DHCP Range or Fixed Address.
  • Name: The object name. For example, if the IP address belongs to a host record, this field displays the host name.
  • Comment: The information you entered for the object.
  • IPv4 DHCP Utilization: The percentage of the total DHCP usage of a DHCP range. This is the percentage of the total number of fixed addresses, reservations, hosts, and active leases in the DHCP range divided by the total IP addresses in the range, excluding the number of addresses in the exclusion ranges. Note that only enabled objects are included in the calculation. It does not include abandoned addresses or leases.
  • Site: The site to which the DHCP object belongs. This is one of the predefined extensible attributes. You can select the following additional columns for display:
  • Static Addresses: Indicates whether the IP address is a static address.
  • Dynamic Addresses: Indicates whether the IP address is a dynamically assigned address.
  • Disabled: Indicates whether the object is disabled. You can double-click a row and select the check box in this column to disable the network. Grid Manager displays a warning message when you select the check box. Click Yes to confirm or No to cancel. Note that disabling an IPv4 network may take a longer time to complete depending on the size of the data.
  • Priority: Displays the priority of a DHCP range when NAC filters are applied.
  • Available extensible attributes.

You can also perform the following in this panel:

  • Modify some of the data in the table. Double-click a row, and either modify the data in the field or select an item from a drop-down list. Click Save to save the changes. Note that some fields are read-only. You can edit values of inheritable extensible attributes by double-clicking on the respective row. If an extensible attribute has an inherited value, then the cell is highlighted in blue when you perform inline editing. The Descendant Actions dialog box is displayed when you click Save. For information, see Managing Inheritable Extensible Attributes at the Parent and Descendant Level. If you delete the value of an inheritable extensible attribute at the parent level, you can choose to preserve the descendant value or remove it. For information, see Deleting Inheritable Extensible Attributes Associated with Parent Objects.
  • Sort the displayed data in ascending or descending order by column.
  • Click Go to IPAM View to view information about the object in the IPAM tab.
  • Add new objects, such as DHCP ranges, to the network.
  • Delete or schedule the deletion of a selected object or multiple objects.
  • Use filters and the Go to function to narrow down the list. With the autocomplete feature, you can just enter the first few characters of an object name in the Go to field and select the object from the possible matches.
  • Create a quick filter to save frequently used filter criteria. For information, see Using Quick Filters.
  • Print or export the data.

Modifying IPv4 Networks

You can modify existing network settings and override the Grid or member DHCP properties, with the exception of the network address and netmask.

To modify an IPv4 network, perform the following:

  1. From the Data Management tab, select the DHCP tab -> Networks tab -> Networks section -> network check box, and then click the Edit icon.

    Or

    From the Data Management tab, select the IPAM tab -> network check box, and then click the Edit icon.
  2. The IPv4 Network editor contains the following basic tabs from which you can modify data:
    • Genera Basic: You can modify the following fields:
      • Comment: The information you entered for the network.
      • Disabled: This field is displayed only if the selected network is a network without a child network under it. You can disable and enable existing networks instead of removing them from the database, if the selected network does not have a child subnet. This feature is especially helpful when you have to move or repair the server for a particular network. Note that disabling an IPv4 network may take a longer time to complete depending on the size of the data.

Restricting synchronization of a network

      • Disable sync to MGM: Select this check box to disable synchronization of a network from the managed Grid to the Multi-Grid Master. This check box is available only on the managed Grid when it remains joined with the Multi-Grid Master.

When the Cloud Network Automation license is installed on the Grid Master, Grid Manager displays the following information in the Cloud section: Cloud Usage, Owned By, and Delegated To. You cannot modify these fields. For more information, see Viewing Networks.

    • Member Assignment: Add or delete a Grid member that provides DHCP services for this network. For information, see Adding IPv4 Networks.
    • IPv4 DHCP Options: Keep the inherited DHCP properties or override them and enter unique settings for the network. For information, see Defining IPv4 DHCP Options.
    • Discovery: Checking the Enable Discovery check box informs NIOS to begin discovering the network after you click Save and Close. You manage discovery polling settings local to each network from this page. For a complete overview of features on this page, see Discovering Devices and Networks and its subsections.
    • Discovery Exclusions: IP Addresses and IP ranges can be locally excluded from discovery by clicking the Add icon and selecting Add IP Address or Add IP Range. These IP addresses or IP ranges are selected from within the chosen network. For related information, see Excluding IP Addresses from Discovery and its subsections.
    • Discovery Blackout: Define extended time periods and regularly scheduled times when discovery and/or Port Configuration tasks will not take place on a network. Editing a network under DHCP, blackout settings apply only to the specified network. You also specify the scheduled time when the blackout period begins, and the duration of the blackout period. By default, the network inherits its discovery blackout settings from the Grid level. For related information, see Defining Blackout Periods and its subsections.

      Note

      Discovery blackout settings also can be defined for DHCP ranges.

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

4. Save the configuration or click the Schedule icon at the top of the wizard to schedule this task. In the Schedule Change panel, enter a date, time, and time zone. For information, see Scheduling Tasks.

Deleting IPv4 Networks

When you delete a network, all of its data, including all DHCP records, subnets, and records in its subnets, is deleted from the database. Due to the potentially large loss of data that can occur when you delete a network, the appliance stores the deleted network in the Recycle Bin. You can restore a deleted network from the Recycle Bin, if enabled. You can also disable a network instead of deleting it. 

To delete a network, perform the following:

  1. From the Data Management tab, select the DHCP tab -> Networks tab -> Networks section -> network check box, and then select Delete or Schedule Delete from the Delete drop-down menu.
  2. To delete the network now, in the Delete Confirmation dialog box, click Yes. Grid Manager displays a warning message. Click Yes to continue or No to cancel the process. To schedule the deletion, see Scheduling Deletions.

The appliance puts the deleted network in the Recycle Bin, if enabled. Click Restore in the Recycle Bin to recover the deleted data. Click Yes in the Restore Item dialog box to restore or No to cancel the process. 

Note

  • Any Port reservation associated with the deleted network will also be deleted without user intervention. 
  • Deleting and restoring an IPv4 network may take a longer time to complete depending on the size of the data.
  • You cannot delete a network that has a VLAN object assigned to it. For more information, see Assigning VLANs to a Network.

This page has no comments.