...
Expand | ||
---|---|---|
| ||
For a simplified example of the how Netblock Tree View displays compared to Block View, we will be using an example aggregate of of 19.20.30.0/24 (assigned to "'Available"'). The standard Block View for this aggregate shows it has been split to contain a /25, a /26, and two /27s. The /26 and one of the /27s have been assigned to different resources. in In Block View, we only see the lowest child blocks that exist in ProVision: When we switch to Netblock Tree View (by clicking "Netblock Tree") we see only /26s in the top level of the view. This is because 19.20.30.0/26, assigned to '01 Telecom', is the first assigned block encountered. Netblock Tree View will ignore 19.20.30.0/25 and 19.20.30.128/25 because they are assigned to the same resource as 19.20.30.0/24 ('Available').
There are no ( different ) assignments under this 19.20.30.0/26. Thus, when you expand it you will see only /32 addresses. As these /32s have not yet been created in ProVision → Block View, they only exist as "theoretical" blocks and are not editable, but aid in viewing the totality of available addresses under that prefix.
If you would like these addresses to be assigned or editable in ProVision, you may split the /26 down to the desired number of /32 addresses using templates or manual splits. This will create the addresses in ProVision and allow those addresses to be edited.
Under those branches display individual /32 addresses, because the /27 is assigned.
However, if 19.20.30.128/25 is split into two /26s in ProVision, the previously theoretical blocks of 19.20.30.128/26 and 19.20.30.194/26 become 'real' objects, and will display as expandable and editable. |
...