Page Comparison

...

When you create an IPv4 range template, the start and end address fields are based on the specified offset from the network start address and the number of IP addresses in the range. After you create a DHCP range template, you can configure additional properties such as exclusion ranges and DHCP filters, as described in Modifying IPv4 Range Templates. Then when you use the template to create a DHCP range, the range inherits the properties of the template. You can also include a DHCP range template in a network template to automatically create a DHCP range when you use that network template.
If you have deployed the Cloud Network Automation license on the Grid Master, you can configure range templates for cloud delegation. When you select a default Cloud Platform Appliance for a template, all ranges you create using this template will delegate authority to the same Cloud member. Note that when a Cloud member is removed from the Grid, the delegation will also be removed from the template. For information about Cloud Network Automation, see Deploying Cloud Network Automation.

Anchor
bookmark2405 bookmark2405

Anchor
bookmark2406 bookmark2406

Adding IPv4 Range Templates

...

The Cloud section appears when the Cloud Network Automation license is installed on the Grid Master. For information, see Deploying Cloud Network Automation. To configure this template for cloud delegation, complete the following:
Use for cloud delegation: Select this check box to enable cloud delegation for this template.

...

You can use an IPv4 fixed address/reservation template to create fixed addresses, reservations and roaming hosts.
When you create an IPv4 fixed address/reservation template, you can specify an offset and number of addresses. This is used when you include the template in a network template. When you include a fixed address/reservation template in a network template, the DHCP server automatically creates reservations based on the offset and number of addresses you specified in the fixed/address reservation template. It does not create fixed addresses.
After you create a fixed address/reservation template using the wizard, you can configure additional properties as described in Modifying IPv4 Fixed Address/Reservation Templates. Then when you use the template to create a fixed address, it inherits the properties of the template.
If you have deployed the Cloud Network Automation license on the Grid Master, you can configure fixed address templates for cloud delegation. When you configure a template for cloud delegation, all fixed addresses you create using this template will inherit authority delegations from their parent objects. For information about Cloud Network Automation, see Deploying Cloud Network Automation.

Anchor
bookmark2410 bookmark2410

Anchor
bookmark2411 bookmark2411

Adding IPv4 Fixed Address/Reservation Templates

...

You can create IPv4 network templates to facilitate network configuration. You can use network templates to create networks in any network view. When you create a network template, you do not specify a network address. You enter the network address when you create an actual network from the template. You can specify a netmask or allow the user to define the netmask when they create the actual network.
A network template is useful for setting up a network with fixed addresses and DHCP ranges already defined. You can add DHCP range or fixed address/reservation templates to a network template. Once the fixed address and DHCP range information is set up, the network template contains a range template list and a fixed address/reservation template list.
When you enable support for RIR updates, you can create IPv4 network templates specific for RIR associated networks. For information about RIR updates, see RIR Registration Updates.
If you have deployed the Cloud Network Automation on the Grid Master, you can configure network templates for cloud delegation. When you select a default Cloud Platform Appliance for a template, all networks you create using this template will delegate authority to the same Cloud member. If you want to associate any range or fixed address templates with a network template, ensure that you enable "User for cloud delegation" for the network, range, and fixed address templates. Note that when a Cloud member is removed from the Grid, the delegation will also be removed from the template. For information about Cloud Network Automation, see Deploying Cloud Network Automation.

Anchor
bookmark2416 bookmark2416

Anchor
bookmark2417 bookmark2417

Adding IPv4 Network Templates

...

1. From the Data Management tab, select the DHCP tab -> Templates section.
2. Click the Add drop-down list and select IPv4 Network Template.
3. In the Add IPv4 Network Template wizard, do the following:
   • RegionalInternetRegistry: This section appears only when support for RIR updates is enabled. For information about RIR, see RIR Registration Updates. Complete the following to create a network template for an RIR IPv4 network container or network:
     • Internet Registry: Select the RIR from the drop-down list. The default is RIPE. When you select None, the network is not associated with an RIR organization.
     • Organization ID: Click Select Organization and select an organization from the RIROrganizationSelector dialog box.
     • Registration Status: The default is Not Registered. When using this template to add an RIR allocated network, you can change this to Registered and select the Do not update registrations check box below. Note that when you select API as the communication method, the registration status will be updated automatically after the registration update is completed. However, when you select Email as the communication method, the registration status will not be automatically updated. If you are creating a new network and the registration update is completed successfully, the status will be changed to Registered. If the update fails, the status will be changed to Not Registered.
     • Registration Action: Select the registration action from the drop-down list. When you select Create, the appliance creates the IPv4 network and assigns it to the selected organization. When you select None, the appliance does not send registration updates to RIPE. When you use this template to add an existing RIR allocated network to NIOS, select None. When you use this template to add networks to an RIR allocated network (a parent network), select Create. Ensure that the parent network associated with an RIR organization already exists.
     • Do not update registrations: Select this check box if you do not want the appliance to submit RIR updates to RIPE. By default, the appliance sends updates to the RIR database based on the configured communication method.
   • Name: Enter a name that helps identify the network template. For example, you can enter Class C if you want to configure the template for creating Class C networks.
   • Netmask: Select one of the following options:
     • Fixed: Select this and adjust the netmask slider to a fixed netmask for this network template. When you select this option, users cannot specify another netmask when they use this template to create a network. For example, if you select /24 as the fixed netmask, all networks created using this template have a /24 netmask.
     • Allow User to Specify Netmask: Select this to allow users to specify the subnet mask when creating networks using this template.
   • Comment: Optionally, enter additional information about the template.
   • Automatically Create Reverse-Mapping Zone: This function is enabled if the fixed netmask of the template equals /8, /16, and /24, or if you select the Allow User to Specify Netmask option. Select this if you want the appliance to automatically create the corresponding reverse-mapping zone for the networks created using this template. A reverse-mapping zone is an area of network space for which one or more name servers have the responsibility for responding to address-to-name queries. These zones are created in the DNS view assigned to receive dynamic DNS updates at the network level.

The Cloud section appears when the Cloud Network Automation license is installed on the Grid Master. For information, see Deploying Cloud Network Automation. To configure this template for cloud delegation, complete the following:
Use for cloud delegation: Select this check box to enable cloud delegation for this template.

...

• First address 192.168.2.1 is reserved for the router
• Next 10 addresses (192.168.2.2 to 192.168.2.11) reserved for servers
• Next 10 addresses (192.168.2.12 to 192.168.2.21) reserved for printers
• Next 10 addresses (192.168.2.22 to 192.168.2.31) assigned as fixed addresses
• 100 addresses (192.168.2.32 to 192.168.2.131) reserved for workstations. The appliance assigns these dynamically.
• 10 addresses (192.168.2.42 to 192.168.2.51) are in an exclusion range. If you assigned static addresses to certain hosts in the middle of an address range template, you can exclude the addresses from the address range template so the appliance does not assign these IP addresses to clients

Figure 28.

...

1 illustrates the configurations of the 192.168.2/24 network using the network template you create:

Figure 28.1 Creating a Network Using a Template

Place for Fig. 28.1

Use the following steps to create the sample network template (shown in Figure 28.1).

...