Documentation

User Tools

Site Tools

Trace:
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 revisionPrevious revision
Next revision		Previous revision
2_x:datamodel:subnet-blocks [2023/04/13 12:06] – [Listing Subnet Blocks] cnaud2_x:datamodel:subnet-blocks [2024/03/27 16:06] (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: Yes, No | Yes | +| Allow automatic subnet creation | Possible values: yes, no \\ Brought by the [[extensions:teemip-request-mgmt|IP Request Management]] extension | No |
 | **Delegation Information** ||| | **Delegation Information** |||
 | Delegated from | Foreign key to a(n) Organization | No | | Delegated from | Foreign key to a(n) Organization | No |
Line 54: Line 54:
  
 ==== Displaying Tree ==== ==== Displaying Tree ====
-Display can be switch from the listing view to tree view through the **Display Tree** action in the **Other Actions** menu.+Display can be switched from the listing view to tree view through the **Display Tree** action in the **Other Actions** menu.
  
 {{ details-popup-menu-blockdisplaytree-3x.png }} {{ details-popup-menu-blockdisplaytree-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.
  
 +==== 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?nolink|Navigate icon}} will bring you to the previous or next registered subnet block in TeemIp. This action is driven by default parameters that can be overwritten in the configuration file.
  
 +<code>
 + 'teemip-ip-mgmt' => array (
 + ...
 + 'bloc_navigation' => array (
 +   'enabled' => true,
 +   'within_block_only' => false,
 + ),
 +                ...
 +        ),
 +
 +</code>
 +
 +^  Parameter  ^  Description  ^
 +| 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.1681380366.txt.gz · Last modified: 2023/04/13 12:06 by cnaud

Page Tools