Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from this space and version 7.2.0

...

In ProVision, the IP assignment lifecycle starts with an available block which is free to be assigned to any IPAM-enabled resource holder.  There are multiple methods that may be used to assign a block to a resource holder: Smart Assign, Direct Assign, or Manual Assign (Smart Browse).

Once an IP block is assigned, blocks can be further subassigned via the same methods if desired. When an assigned block is un-assigned it proceeds into the Holding Tank: a special resource where blocks are held until either a set time has elapsed or until they are manually reclaimed to 'available' status. 

...

Working with IP Blocks

IPAM Administration

 


IP Management

IP Management is comprised of four basic functions: adding aggregates into ProVision, managing those aggregate blocks, assigning them to a resource, and deleting the aggregates.

...

Importing Your Data

Import Aggregate Blocks

 


Peering 

ProVision versions 7.0.0 and later:

In ProVisionInitially, ASNs and Peering DB information will need to be entered into ProVision to enable Peering functionality. After the, Peering starts with designating Routers. Routers may be added through the Resource system under a router Section, but the simpler approach is to add a new router via the from the "Add Router" button under the Peering Tab Routers sub-tab. Through this dialogOnce a router has been created, Peer Groups may be added at the same time.from the Router Details page or the Peer Group Gadget. 

After the router(s) and Peer Groups have been created in ProVision, Sessions need to be added. Sessions may be added manually through the "Add Session" dialog in the Peering v2 tab, or Imported from a router (requires ProVision Admin permissions).

Once a session has been created, it can be configured and managed through the Sessions list and Session details page (using 1-click Config or Config Management), or selected and multiple sessions may be configured for a specific Peer via the "Configure Multiple Sessions" option, which will provide options to either "Config Now" or "Schedule Config" for a later time.

Managing Peer Communications is done primarily from the Exchange → Communications menu, sending requests and marking peers as existing / not qualified / approved, etc. If desired, a corporate Peering email account may be associated with ProVision under the Peering → Emails subtab, allowing for peering requests to be viewed from ProVision and associated with Peers. 

Image Added 


ProVision versions 6.2.1 and ProVision versions 6.2.1 and earlier:

Expand
Image Modified

For more information on performing tasks under Peering, see the following documentation sections:

...

Peering Sessions

Import Peering Sessions

...


VLAN Manager

The VLAN Manager allows Admin users to add domains and VLANs to their ProVision instance, and associate them with IP Blocks. Optionally, VLAN tags may be associate with ranges or individual VLANs under a domain, to help limit VLAN search results when enabling VLANs. 

...

Next, VLANs must be enabled and added to the domain. This is done under the IPAM Tab -> VLAN section of ProVision. Add VLANs to the domains by clicking "Add", searching for the desired range of VLANs to enable from the standard / extended pool, and selecting the desired VLANs to enable. Once enabled, VLANs may be edited or have IP blocks associated with that VLAN. Editing VLANs and Direct / Smart Browse / Search IPs functions for adding blocks to VLANs are available from the Domain/ VLAN list under under the IPAM Tab -> VLAN section of ProVision. IP blocks may also be edited individually through the IPAM gadget, IPAM Manage, and VLAN Manage areas to add domain and VLAN information to the block. 

Image Removed

...

to add domain and VLAN information to the block. 

Image Added

DHCP 

ProVision versions 7.0.0 and later:


Info

ProVision 7.0.0+ includes many updates to the DHCP module, including the introduction of DHCP Groups, updated interface, improved permissions control, and simplified pool management. The DHCP Tab contains areas for managing both admin and non-admin tasks together for DHCP Groups, DHCP Servers, and DHCP Pools. 

DHCP Groups allow you to create, view, and manage groups of DHCP Servers and Pools. Using groups, you can configure and push selected combinations of zones at one time. DHCP pools may be gathered under DHCP Groups, and servers attached to those Groups. Pools, attached servers, and failovers are managed at a per-Group level. Users can then view and manage Groups, individual pools, failover values, attach servers, and perform pushes all on the same page.

Additionally, starting in ProVision 7.0.0, any IPAM aggregate or block may be used for DHCP pools - provided it meets the specified criteria when creating a DHCP Pool. If assigning a pool out from a specific resource, ensure ahead of time that the resource contains suitable blocks with subassignments enabled. 


The DHCP Workflow begins with adding DHCP Servers into ProVision and creating an additional DHCP Groups as needed. 

New DHCP servers may be added from the DHCP Tab - DHCP Servers subtab by clicking "Add Server" (requires Admin access). Type in the server information, select the service, and choose the resource to which the DHCP server belongs if applicable. This creates a hierarchical relationship, with the server as a child resource under the selected parent, and affects how permissions are handled for the server and pools. Then, enter any service-specific or advanced settings for the server. You may also choose which DHCP group to associate with the server if the group already exists, but you may also add that setting later. 

If desired, you may create additional DHCP Groups to organize certain pools and associated DHCP servers together to push concurrently, with the option of a common failover value. A common scenario is using separate DHCP Groups per server, or separate Groups for IPv4 vs. IPv6 pools. A new DHCP Group may be created from the DHCP Groups subtab "Add Group" button. Enter the Group Name and parent resource. Once created, you may attach a DHCP server to the Group, associate a failover, and add pools to it. 

Next, you may add/assign DHCP pools. Before assigning pools, ensure that you have suitable IP aggregates created in ProVision meeting your desired parameters to assign to the pool (such as desired RIR, region, VLAN, or allocated to a specific Resource). If assigning a pool out from a specific resource, ensure ahead of time that the resource contains suitable blocks that have subassignments enabled. 

To add a pool to a DHCP Group, click the "Add Pool" button for that group. You may also add a pool from the DHCP Pools subtab without associating the pool with a DHCP Group. From the "Create New Pool" dialog, select the pool type ("Subnet" or "Host), enter in the relevant information, and select to either Direct Assign a specific block, or have ProVision Smart Assign a block based on provided filter criteria - such as assigned resource, region, rule, or VLAN. Click "Save" to complete the Pool assignment. 

Once servers, groups, and pools have been created, you may complete management tasks such as pushing configs on either a server, group, or individual pool level, schedule pushes, update reservations or assignment ranges, and change group/server associations as needed.  

Image Added


For ProVision versions 6.2.1 and earlier:

Expand

The DHCP Workflow in ProVision begins with denoting the DHCP IP Aggregate(s) from the IPAM Tab -> "Add Aggregate".  When creating DHCP aggregates, ensure that the block is designated as 1918 space, and has the check boxes next to "DHCP Aggregate" and "Allow Sub-assignment" selected. This will ensure the block is automatically added to the DHCP Available Resource, and is usable when defining DHCP Pools.

Separately, ensure that the DHCP server is added into ProVision. New DHCP servers may be added from the DHCP Tab "Add DHCP Server" button. Type the server name, then choose the resource to which the DHCP server belongs. This creates a hierarchical relationship, with the server as a child resource under the selected parent. 

Once the server has been created in ProVision, click on the server name in the DHCP server list to go to the server's Entry Page. If the server was created through the DHCP Tab, the DHCP Management Gadget will already be enabled for the DHCP server. If created elsewhere, the DHCP Gadget may need to be enabled by simply selecting the "On" radio toggle next to "DHCP Services", and clicking the "Update" button. Next, add in the connection configuration and server details for the DHCP server in the DHCP Gadget. 

Now that the DHCP server is set up and DHCP aggregates created, DHCP Pools may be created and managed. Pools may be created by subnet or host. Creating by subnet allows for a block to either be directly assigned manually, or for ProVision to SmartAssign a block based on the provided criteria. Creating by host requires providing a host and MAC address, and then likewise may have an IP directly assigned or Smart Assigned. DHCP Pools, once created, are managed by linking or unlinking to the DHCP server. IP assignments and pool details may be changed at any time by clicking on the pool name, editing the details as desired, then clicking "Save". 


Image Modified

For more information on working with DHCP in ProVision, see the DHCP Tab documentation.

For more information on DHCP tasks, see the following sections:

DHCP Tab

Working with DHCP Groups

Working with DHCP Pools

Working with DHCP Gadgets

DHCP Administration

Working with DHCP Servers 


DNSv3 Workflow

DNSv3 revolves around Groups. Zones are gathered under Groups, servers attached to Groups, and pushes may be done on a per Group level. Thus, the first workflow step in DNSv3 is to set up one or more DNS Groups. A "Default Group" is automatically provided in ProVision, but other Groups may be desired to organize zones and default values.

...

  1. Submitter makes an action (either by action type or DNS Family) that requires approval
  2. Submitter is notified that their action is pending approval
  3. The requested change is sent to the Approvals Tab Pending Approvals list, and also to the DNS Resources Awaiting Approval module (the submitter may see their own submitted action under "Resources awaiting approval", but only Approvers can take approve/reject actions)

    Expand
    titlePending Approvals List...

    The Pending Approvals list is under the Approvals Tab. It shows Approvals events (change requests) for which the user has the ability to Approve or Deny - it does not show approval requests for all of ProVision or those for other users.


    Expand
    titleResource Awaiting Approval Module...

    A "Resources Awaiting Approval" module will display in selected DNSv3 pages to Users with Admin / Approval permissions, if a change has been submitted on that page that is pending approval by the User's Approval Group. 


  4. The Approver reviews the change in either their Approvals Tab Pending Approvals list, or the DNSResources Awaiting Approval module, and chooses to Approve or Reject the change:

    Expand

    1. If Approved, and no other groups need to approve it, then the change executes and is saved. A status change notification email is sent, if enabled. 
    2. If Approved, and is waiting approval from an additional User Group, the change continues to be held as Pending, until the other group responds (Both groups must "Approve" for the change to execute). A status change notification email is sent, if enabled, stating that the change is awaiting another Group.
    3. If Rejected, the change is not executed. A status change notification email is sent, if enabled. 


    Example Notification Email:



    See the following areas for more information on Approvals and using Approvals with DNS:

 

...