You may provision networks and remove or de-provision networks from individual devices. You can also provision networks when creating a network in IPAM (for more information, see Adding IPv4 and IPv6 Network Containers and Networks). Network provisioning and de-provisioning comprises the second type of port control tasks under Network Insight. Provisioning a network involves creating a new network and adding it to the list of networks in IPAM, and also involves changes to device configuration.
...
- From the Data Management tab, select the Devices tab.
- Click the Next Page and Last Page icons to locate the device whose interfaces you want to provision.
- Click the Name of the device. The Devices page displays the five tabs of information associated with the device.
- Click the Networks tab.
- The Networks page lists all discovered networks (highlighted in grey), unmanaged networks (highlighted in yellow), and any managed networks (highlighted in white, showing Yes in the Managed column) present on the selected device.
- Open the vertical toolbar and click Provision Network. The Provision network wizard appears.
- Click Select Network to choose the network the you want to provision. If only one managed network is available on the device, that network value is populated after clicking the button.
If more than one managed network is available under IPAM, the Network Selector dialog opens, listing all networks managed under IPAM. - Choose the network to provision onto the device and click OK.
- Enter the Router IP Address. This required field may be pre-populated with the DHCP router IP address if the device already has a DHCP configuration. If not, enter the gateway router IP address for the current device.
- If necessary, check the DHCP Forwarding checkbox. Check this checkbox to enable DHCP forwarding for the newly provisioned network. If a DHCP failover is already present, the IP addresses from that failover are used for DHCP forwarding information.
- For choosing the Interface, you can choose one out of two options:
- Interface drop down list: If you are provisioning the network directly onto an interface, select it from this list. Only interfaces that are available for provisioning on the chosen device appears on this list; interfaces that are already active in a network do not appear;
–or– - For a switch-router, select Create VLAN, and specify the VLAN Name and its new VLAN ID. Ensure that the VLAN ID is not one that is already provisioned on the device.
Figure15.15
Provisioning a VLAN on a Switch-Router
- Interface drop down list: If you are provisioning the network directly onto an interface, select it from this list. Only interfaces that are available for provisioning on the chosen device appears on this list; interfaces that are already active in a network do not appear;
Click Next to go to the second step in the Provision Network wizard, in which you define whether to provision the configuration now or to schedule it.
To immediately provision the new network on the chosen device, select Now.
You can choose to have Grid Manager create the network at a later time. To do so, select 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.
Click Save & Close when finished.
...
...
De-Provisioning Networks
| Note | ||
|---|---|---|
| ||
De-provisioning a network changes the device configuration. As such, a separate task is created for the action under Task Manager. However, you cannot schedule the de-provisioning of a network–once you confirm the de-provisioning action in Grid Manager, the action takes place. Each managed and unmanaged device under Grid Manager provides a Permissions page (DataManagement–>Devices–> Select Device –> click Edit–>Permissions tab). By default, no admin group or Role is assigned to managed devices. Infoblox recommends using caution when assigning rights to users that may be able to access devices and change device configurations. |
De-provisioning networks is a relatively straightforward task that can be performed for any selected network, whether it is a non-NIOS network (a network that cannot be configured in IPAM), an unmanaged network, or a managed network.
...
| title | Note |
|---|
...
Note that if the network is also managed under IPAM, de-provisioning the network from a device does not delete the network from IPAM.
If you are deleting a network from the main IPAM page, any devices that have endpoints provisioned on that network are also de-provisioned for that network.
...
| title | Note |
|---|
...
Note that a network may not be de-provisioned until after you set the interface for the network on the device(s), to Down in Admin Status.
- From the Data Management tab, select the Devices tab.
- Click the Next Page and Last Page icons to locate the device through which you want to locate the interfaces to convert.
- Click the Name of the device. The Devices page displays the five tabs of information associated with the device.
- Click the Networks tab for the chosen device. The Network page lists all discovered networks (highlighted in grey), unmanaged networks (highlighted in yellow), and managed networks (highlighted in white) present on the selected device.
- Click the Next Page and Last Page icons to locate the network that you wish to de-provision.
- Click the Action icon
next to the network you want (this automatically selects it) and select De-Provision Network. The dialog box appears, listing the device name, the device's IP address, the interface to which the network is currently bound, and the network's endpoint IP address on the current device.Figure 15.16 De-Provisioning a Network from a Device
- Click Yes to confirm the de-provisioning action.
...
By default, when you delete the network, all devices that connect to the network, that are also managed by IPAM, are part of the new de-provisioning port control task created by Grid Manager. If you do not want the network
de-provisioned from all devices, clear the De-provision network from all interfaces checkbox or simply cancel out from the Delete Confirmation dialog.
...
Troubleshooting Port Control Tasks
...
Issues can occur when attempting to define port configurations on devices. When you define port configurations through Network Insight, you are defining a port control task that can be viewed, investigated, and run again when necessary. You do so by using the Task Manager (Administration –> Workflow –> Task Manager) and looking for tasks that show a Type of Port Control. Each Port Control task provides an Execution Log and the ability to re-run a task that has failed for any reason.
The Task Manager page provides an Action icon column with a series of menu options for features related to Grid Manager tasks to manage task execution, scheduling and approval. Menu choices change based upon the context and the current state of tasks in the table; features available in the Action menu include the following:
Figure 15.17 Task Manager Action menu
- Approve: Enables admins to approve a pending job.
- Reject: Enables admins to reject a pending job, immediately cancelling it.
- Execution Log: Opens a completed task's execution log window. the Execution Log lists the complete communications sequence sent to a device to perform a port control task.
- Execute Now: Force a selected pending task to execute immediately.
- Re-Execute: Allows you to re-run the selected task. Combined with the Execution Log, this process can aid in troubleshooting a failed port control task.
- Reschedule: Opens the Reschedule window for the selected task. To immediately execute this task, click Now. Or, in the Reschedule panel, click Later, and then specify a date, time, and time zone. You can reschedule the task if you have the applicable permissions. Click Save to commit the changes.
- Delete: Deletes the pending task.
- View: Opens the Task Viewer to the currently selected task. For related information, see Using the Task Viewer to View Job Logs and Approve Jobs.
...