IPAM Templates Support

Comments

2 comments

  • Avatar
    susan_in_austin

    The idea here is that templates could be created for specific VLANs, VLAN sizes, initial IP Address allocation for primary, secondary and VRRP ips.  Then the use would just pick a starting CIDR block and the new information would be automatically populated into Device42.

    0
    Comment actions Permalink
  • Avatar
    susan_in_austin

    Similar functionality exists in other IPAM tools.  Documentation is like this:

     

    About IPv4 Range Templates

    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.

    0
    Comment actions Permalink

Please sign in to leave a comment.