User Tools

Site Tools


2_x:datamodel:subnet-blocks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
2_x:datamodel:subnet-blocks [2019/10/15 16:50]
cnaud [Delegate]
2_x:datamodel:subnet-blocks [2021/03/27 13:56] (current)
cnaud [Displaying a Subnet Block]
Line 10: Line 10:
 | **General Information** ||| | **General Information** |||
 | Organization | Foreign key to a(n) Organization | Yes | | Organization | Foreign key to a(n) Organization | Yes |
-| Delegated from | Foreign key to a(n) Organization | No | 
-| Parent | Foreign key to a(n) Subnet Block | No | 
 | Name | Alphanumeric string  | Yes | | Name | Alphanumeric string  | Yes |
 | Type | Alphanumeric string  | No | | Type | Alphanumeric string  | No |
Line 17: Line 15:
 | Requestor | Foreign key to a(n) Person | No | | Requestor | Foreign key to a(n) Person | No |
 | Allocation date | Date (year-month-day) | No | | Allocation date | Date (year-month-day) | No |
 +| **Delegation Information** |||
 +| Delegated from | Foreign key to a(n) Organization | No |
 +| Origin | Possible values*: RIR, LIR, Other | No |
 +| Registrar | Foreign key to a(n) Organization | No |
 | **IP Information** ||| | **IP Information** |||
 +| Parent | Foreign key to a(n) Subnet Block | No |
 | First IP | IPv4 or IPv6 Address | Yes | | First IP | IPv4 or IPv6 Address | Yes |
 | Last IP | IPv4 or IPv6 Address | Yes | | Last IP | IPv4 or IPv6 Address | Yes |
  
 +<note> 
 +Origin of a block can be a RIR (Regional Internet Registry like ARIN or RIPE), a LIR (Local Internet Registry like an internet provider that delegates public space to its customers) or Other (to cover all other cases). 
 +</note>
 ==== Tabs ==== ==== Tabs ====
 ^  Tab  ^  Description  ^ ^  Tab  ^  Description  ^
Line 27: Line 32:
 | Contacts | All the contacts for this IP Object | | Contacts | All the contacts for this IP Object |
 | Documents | All the documents linked to this IP Object | | Documents | All the documents linked to this IP Object |
 +| Notifications | List of related notifications - Present if a notification trigger exists for that class |
 | Child Blocks | Subnet blocks strictly contained within the block | | Child Blocks | Subnet blocks strictly contained within the block |
 | Subnets | Subnets belonging to the subnet block | | Subnets | Subnets belonging to the subnet block |
 +| History | History of all changes made to the subnet block |
  
 ==== Listing Subnet Blocks ==== ==== Listing Subnet Blocks ====
Line 35: Line 41:
  
 {{ classlist_ipv4subnetblock.png }} {{ classlist_ipv4subnetblock.png }}
 +
 {{ classlist_ipv6subnetblock.png }} {{ classlist_ipv6subnetblock.png }}
  
Line 64: Line 71:
  
 An implicit but intuitive set of rules must be followed when a subnet block is created: An implicit but intuitive set of rules must be followed when a subnet block is created:
-  * A subnet block belongs to a unique organization +  * A subnet block belongs to a unique organization, 
-  * A subnet block can be delegated from a given organization to an organization. Once donethe block will still appear in the parent organization but will be managed from the child organization. +  * A subnet block can be fully contained within another subnet block. We talk, then, about child block or parent block, 
-  * A subnet block can be fully contained within another subnet block. We talk, then, about child block or parent block. +  * Two blocks cannot share the same name, 
-  * Two blocks cannot share the same name +  * Two blocks cannot share common IP space unless one is fully contained within the other
-  * Two blocks cannot share common IP space unless one is fully contained within the other. +  * If not set, "Parent" is automatically computed when "First IP" and "Last IP" are defined, 
-  * Minimum size of a subnet block is defined by the global parameter "Minimum size of IPv4 / IPv6 Subnet Blocks"+  * Minimum size of a subnet block is defined by the global parameter "Minimum size of IPv4 / IPv6 Subnet Blocks",
   * According to the global parameter “Align IPv4 / IPv6 Subnet Blocks to CIDR”, a subnet block needs to be CIDR aligned or not.   * According to the global parameter “Align IPv4 / IPv6 Subnet Blocks to CIDR”, a subnet block needs to be CIDR aligned or not.
  
-At creation time, global settings “Minimum size of IPv4 / IPv6 Subnet Blocks” and “Align IPv4 / IPv6 Subnet Blocks to CIDR” can be overwritten. Note that a change on these parameters, if any, only applies to the current creation and don’t affect the value of the global parameters. If it is required to change them globally, these can be changed through the [[2_x:datamodel:ip-settings|Global IP Settings]] menu of the Data Administration module. +At creation time, global settings “Minimum size of IPv4 / IPv6 Subnet Blocks” and “Align IPv4 / IPv6 Subnet Blocks to CIDR” can be overwritten. Note that a change on these parameters, if any, only applies to the current creation and don’t affect the value of the global parameters. If it is required to change them globally, these can be changed through the [[2_x:datamodel:ip-settings|Global IP Settings]].
- +
-<note> +
-Global IP Settings being unique for each organization, the "Global Settings" tab will appear only if an organization has been selected at the top of the explorer menu. +
-</note>+
  
 <note tip> <note tip>
 For IPv6 blocks, a simple autocompletion mechanism is used to help typing the Last IP: its first 64 bits are copied from the first IP and its last 64 bits are set to 1... which can, of course, be manually changed by the user. For IPv6 blocks, a simple autocompletion mechanism is used to help typing the Last IP: its first 64 bits are copied from the first IP and its last 64 bits are set to 1... which can, of course, be manually changed by the user.
 </note> </note>
 +==== Displaying a Subnet Block ====
 +In a list of blocks, select the item you are interested in:
 +
 +{{ classdetails_ipv4block.png }}
 +
 +The **Child Blocks** tab displays the blocks that are directly or indirectly attached to the displayed block. Two filters can be applied to that list. Display may contain:
 +  * Only the child blocks that are directly attached to the block,
 +  * The whole child blocks hierarchy under the block.
 +
 +These filters are selected directly in the Child Blocks tab: 
 +
 +{{ classdetails_child_ipv4block_tab.png }}
 ==== Modifying a Subnet Block ==== ==== Modifying a Subnet Block ====
 From the detailed view of a subnet block, click on the "Modify" button. From the detailed view of a subnet block, click on the "Modify" button.
Line 96: Line 111:
  
 ==== Delegate ==== ==== Delegate ====
-A block belonging to an organization can be delegated to another organization. This can only be done once the blocks already exists. Delegation is not available at creation time anymore. Conditions to delegate a subnet block are:+A block belonging to an organization can be delegated to another organization. This can only be done if the block already exists. Delegation is not available at creation time anymore. Conditions to delegate a subnet block are:
   * The block doesn't contain any child block nor subnet   * The block doesn't contain any child block nor subnet
   * The block doesn't collide with any other subnet block already created in the target organization   * The block doesn't collide with any other subnet block already created in the target organization
  
-By default, a block can only be delegated to a child organization. However, this restriction can be lifted through the [[2_x:datamodel:ip-settings|Global IP Settings]].+By default, a block can only be delegated to a child organization. However, this restriction can be lifted by the "Delegate blocks to children organizations only" parameter defined in the [[2_x:datamodel:ip-settings|Global IP Settings]].
  
  
Line 183: Line 198:
 {{ classlistspace_ipv4subnetblock.png }} {{ classlistspace_ipv4subnetblock.png }}
  
-<note>+<note tip>
 Details of child objects (subnet blocks or subnets) can be displayed by simply clicking on their name. Details of child objects (subnet blocks or subnets) can be displayed by simply clicking on their name.
 </note> </note>
Line 204: Line 219:
 </note> </note>
  
 +===== Use cases =====
 +==== Internet Provider - Delegate Space to your customers ====
 +Not only TeemIp offers the possibility to document the space that a Regional Internet Registry has given to your organisation but it provides to Internet Providers (called as well Local Internet Registries) an easy way to delegate part of that space to your customers. This can be done in very few steps. Let's see how:
 +
 +=== 1. Document RIR space ===
 +First of all, document the public IP space given to you by your RIR.
 +
 +{{ classdisplay_rir_subnetblock.png }}
 +
 +=== 2. Find and allocate space ===
 +Look for the space you need in the block and assign it directly to a customer organization. Note that in a RIR block, only subnet blocks and no subnet can be allocated. 
 +
 +{{ rir-delegation-step1.png }}
 +
 +=== 3. Block and subnets are created ===
 +At creation time, new block is set with LIR Origin and a child subnet of same size of the block is created. This subnet belongs to the customer organization and can therefore be managed by members of it.
 +
 +{{ rir-delegation-step2.png }}
 +
 +<note warning>
 +For that process, IP configuration may need to be adjusted for both the Internet provider and the customer.
 +  * Minimum size of IP Subnet blocks may need to be lowered below 256 IPs,
 +  * IPv4 Subnet blocks have to be CIDR aligned so that child subnet can be created at the same time,
 +  * It may be needed to allow delegation to all organizations and not to children organization only.
 +</note>
2_x/datamodel/subnet-blocks.1571151015.txt.gz · Last modified: 2019/10/15 16:50 by cnaud