infoblox_ipv4_network Resource
- Jyothi KP
This resource enables you to perform create, update, and delete operations on IP networks. Network resources support the next available network feature when you use the allocate_prefix_len parameter listed in the below table.
The following table describes the parameters you can define in a network resource block:
Parameter | Required/ | Description |
|---|---|---|
network_view | Optional | Specifies the network view in which to create the network. |
cidr | Required only if parent_cidr is not set | Specifies the network block to use for the network, in CIDR notation. |
parent_cidr | Required only if cidr is not set | Specifies the network container from which the network must be dynamically allocated. |
allocate_prefix_len | Required only if parent_cidr or filter_params is set | Defines the length of the network part of the address for a network that should be allocated from a network container, which in turn is determined by |
gateway | Optional | Defines the IP address of the gateway within the network block.
For more information, see Limitations. |
object | Optional | Specifies the type of object from which to allocate the network.
|
filter_params | Optional | Specifies the extensible attributes of the parent network or network container that must be used as filters to retrieve the next available network for creating the network object. |
comment | Optional | Describes the network. |
ext_attrs | Optional | Specifies the set of NIOS extensible attributes that will be attached to the network. |
Additionally, define the following parameter for the infoblox_ipv4_network resource:
Parameter | Required/ | Description |
|---|---|---|
| Optional | Specifies the number of IPv4 addresses that you want to reserve in the IPv4 network. |
Note
- Either
cidr,the combination ofparent_cidrandallocate_prefix_len, or the combination offilter_paramsandallocate_prefix_lenis required. The rest of the parameters are optional. - Once a network object is created, the
reserve_ipgateway, andfilter_paramsparameter values cannot be changed by performing an update operation.. - IP addresses that are reserved by setting the
reserve_ipfield are used for network maintenance by the cloud providers. Therefore, Infoblox does not recommend using these IP addresses for other purposes.
Examples of the Network Block
// statically allocated IPv4 network. Example with minimal set of parametersresource "infoblox_ipv4_network" "net1" { cidr = 10.0.0.0/16}
//full set of parameters for a statically allocated IPv4 networkresource "infoblox_ipv4_network" "net2" { cidr = 10.1.0.0/24 network_view = "nondefault_netview" reserve_ip = 5 gateway = "10.1.0.254" comment = "small network for testing" ext_attrs = jsonencode({ "Site" = "Nevada" })}
//full set of parameters for a dynamically allocated IPv4 networkresource "infoblox_ipv4_network" "net3" { parent_cidr = infoblox_ipv4_network_container.v4net_c1.cidr // reference to the resource from another example allocate_prefix_len = 26 # 24 (existing network container) + 2 (new network), prefix network_view = "default" # optional parameter reserve_ip = 2 gateway = "none" # no gateway defined for this network comment = "even smaller network for testing" ext_attrs = jsonencode({ "Site" = "Nevada" })}
//full set of parameters for dynamically allocated IPv4 network using next-available network based on extensible attributes tagresource "infoblox_ipv4_network" "ipv4network1" { allocate_prefix_len = 28 network_view = "nondefault_netview" comment = "IPV4 NW within a NW container" filter_params = jsonencode({
"*Site": "Blr" }) ext_attrs = jsonencode({ "Site" = "UK" })
object = "networkcontainer"
})}