2_x:datamodel:subnet-blocks
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 2_x:datamodel:subnet-blocks [2023/04/13 09:57] – [Listing Subnet Blocks] cnaud | 2_x:datamodel:subnet-blocks [2026/01/21 09:08] (current) – [Modifying a Subnet Block] cnaud | ||
|---|---|---|---|
| Line 16: | Line 16: | ||
| | Allocation date | Date (year-month-day) | No | | | Allocation date | Date (year-month-day) | No | | ||
| | **Automation**||| | | **Automation**||| | ||
| - | | Allow automatic subnet creation | Possible values: | + | | Allow automatic subnet creation | Possible values: |
| | **Delegation Information** ||| | | **Delegation Information** ||| | ||
| | Delegated from | Foreign key to a(n) Organization | No | | | Delegated from | Foreign key to a(n) Organization | No | | ||
| Line 41: | Line 41: | ||
| ==== Listing Subnet Blocks ==== | ==== Listing Subnet Blocks ==== | ||
| - | The Subnet Blocks shortcuts under the IP Management menu display all the IPv4 or IPv6 subnet blocks of the selected organization or all IPv4 or IPv6 subnet blocks registered in the application if no organization is selected. | + | The Subnet Blocks shortcuts under the **IP Management** menu display all the IPv4 or IPv6 subnet blocks of the selected organization or all IPv4 or IPv6 subnet blocks registered in the application if no organization is selected. |
| {{ classlist_ipv4subnetblock-3x.png }} | {{ classlist_ipv4subnetblock-3x.png }} | ||
| Line 54: | Line 54: | ||
| ==== Displaying Tree ==== | ==== Displaying Tree ==== | ||
| - | Display can be switch | + | Display can be switched |
| {{ details-popup-menu-blockdisplaytree-3x.png }} | {{ details-popup-menu-blockdisplaytree-3x.png }} | ||
| Line 62: | Line 62: | ||
| {{ classtree_ipv4subnetblock-3x.png }} | {{ classtree_ipv4subnetblock-3x.png }} | ||
| - | Display can be switched back to the listing view through the "Display List" | + | Display can be switched back to the listing view through the **Display List** action available in the **Other Actions** |
| {{ details-popup-menu-blockdisplaylist-3x.png }} | {{ details-popup-menu-blockdisplaylist-3x.png }} | ||
| Line 76: | Line 76: | ||
| * 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, | ||
| - | * Automatic subnet creation within the block, through the IP request module, can be deactivated if required, | ||
| * 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 block** is automatically computed when **First IP** and **Last IP** are defined. | * If not set, **Parent block** is automatically computed when **First IP** and **Last IP** are defined. | ||
| Line 106: | Line 105: | ||
| Only a few parameters can be changed here: Name, Type, Note, Requestor, Allocation date, Locations, Contacts and Documents. | Only a few parameters can be changed here: Name, Type, Note, Requestor, Allocation date, Locations, Contacts and Documents. | ||
| + | ==== Deleting a Subnet Block ==== | ||
| + | A subnet block can be deleted only in the case where **no subnet** is directly attached to it. Should it be required to delete such subnet block anyway, without deleting its child subnets, the following workarounds can be applied: | ||
| + | - 1. Shrink the block until it does not contain any subnet. | ||
| + | - 2. Create one or several child blocks that will contain all the subnets. | ||
| + | Once done, deletion of the original block is possible. Indeed, in the case where a subnet block only contains child blocks, the child blocks are automatically attached to the parent of the deleted block, during the deletion operation. | ||
| + | ==== Navigating between adjacent Subnet Blocks ==== | ||
| + | TeemIp provides an easy and efficient way to navigate between adjacent blocks. If the action is enabled, the left and rights arrows of the object menu {{navigate-icon.png? | ||
| + | |||
| + | < | ||
| + | ' | ||
| + | ... | ||
| + | ' | ||
| + | ' | ||
| + | ' | ||
| + | ), | ||
| + | ... | ||
| + | ), | ||
| + | |||
| + | </ | ||
| + | |||
| + | ^ Parameter | ||
| + | | enabled| Enable or disable the function | | ||
| + | | within_block_only| Limit the navigation to the parent block that the block belongs to or not | | ||
| ==== Other Actions ==== | ==== Other Actions ==== | ||
| Next to standard actions, a set of specific actions can be applied to subnet blocks. These can be found in the **Other Actions** menu available from the details page. | Next to standard actions, a set of specific actions can be applied to subnet blocks. These can be found in the **Other Actions** menu available from the details page. | ||
2_x/datamodel/subnet-blocks.1681379866.txt.gz · Last modified: by cnaud