You can use the interfaces
configuration to configure IP addresses for
interfaces, including bonding interfaces and static routes.
Configuring interface IP addresses
#cloud-config
bluecat_service_config:
payload: |
{
"version": "1.3.0",
"services": {
"interfaces": {
"configurations": [
{
"interfacesConfiguration": {
"networkInterfaces": [
{
"eth0": {
"physical": {
"active": true,
"description": "eth0cloudinit",
"v4addresses": [
{
"ip4": "172.12.0.174",
"cidr": 16
}
],
"v6addresses": []
}
}
}
],
"routes": [],
"dedicatedManagement": false
}
}
]
}
}
}
networkInterfaces
—enter the network interfaces that you would like to configure. You can configure ethernet interfaces (eth
) or bonding interfaces (bond
).For more information on configuring bonding interfaces, refer to Configuring bonding interfaces.
active
—set to true to activate the specified interface; set to false to deactivate the specified interface.description
—enter a description for the specified interface. You can enter up to 80 alphanumeric characters including spaces, but excluding special characters.v4addresses
—enter the IPv4 addresses that you would like to configure for the interface.ip4
—enter the IPv4 address of the specified interface.cidr
—enter the CIDR of the IP space for the specified interface.
v6addresses
—enter the IPv6 addresses that you would like to configure for the interface.ip6
—enter the IPv6 address of the specified interface.cidr
—enter the CIDR of the IP space for the specified interface.
routes
—enter the static route information.For more information on static route configuration, refer to Configuring static routes.
dedicatedManagement
—set to false. Dedicated management is only supported for DNS/DHCP Servers.
Configuring bonding interfaces
You can configure network redundancy through port bonding.
Supported bonding modes
Address Manager supports network redundancy through Active/Backup NIC bonding on Address Manager appliances.
- Address Manager network redundancy is supported on Address Manager appliances only. For customers running Address Manager virtual machines, BlueCat recommends using the virtual server’s infrastructure redundancy mechanism for physical interfaces.
- Address Manager network redundancy requires that the eth0 and eth1 interfaces be physically connected to the same subnet.
- Network redundancy through Active/Active NIC bonding is not supported on Address Manager appliances.
#cloud-config
bluecat_service_config:
payload: |
{
"version": "1.3.0",
"services": {
"interfaces": {
"configurations": [
{
"interfacesConfiguration": {
"networkInterfaces": [
{
"bond0": {
"mode": "activeBackup",
"physical": {
"active": true,
"description": "BONDcloudinit",
"v4addresses": [
{
"ip4": "192.168.1.10",
"cidr": 24
}
],
"v6addresses": []
}
}
},
{
"eth0": {
"physical": {
"active": true,
"description": "eth0cloudinit",
"v4addresses": [],
"v6addresses": []
}
}
},
{
"eth1": {
"physical": {
"active": true,
"description": "eth1cloudinit",
"v4addresses": [],
"v6addresses": []
}
}
}
],
"routes": [],
"dedicatedManagement": false
}
}
]
}
}
}
bond
—enter the network interfaces that you would like to configure.mode
—enter a value ofactiveBackup
to indicate Active/Backup NIC bonding.active
—set to true to activate the specified interface; set to false to deactivate the specified interface.description
—enter a description for the specified interface. You can enter up to 80 alphanumeric characters including spaces, but excluding special characters.v4addresses
—enter the IPv4 addresses that you would like to configure for the interface.ip4
—enter the IPv4 address of the specified interface.cidr
—enter the CIDR of the IP space for the specified interface.
v6addresses
—enter the IPv6 addresses that you would like to configure for the interface.ip6
—enter the IPv6 address of the specified interface.cidr
—enter the CIDR of the IP space for the specified interface.
routes
—enter the static route information.For more information on static route configuration, refer to Configuring static routes.
dedicatedManagement
—set to false. Dedicated management is only supported for DNS/DHCP Servers.
Configuring static routes
Add static routes in to indicate where the system should send packets intended for certain IP addresses.
Packets to be sent to hosts on the same subnet as the Address Manager server can be routed directly to that subnet. The same procedures can be used to manage either IPv4 or IPv6 routes.
#cloud-config
bluecat_service_config:
payload: |
{
"version": "1.3.0",
"services": {
"interfaces": {
"configurations": [
{
"interfacesConfiguration": {
"networkInterfaces": [
{
"eth0": {
"physical": {
"active": true,
"description": "eth0cloudinit",
"v4addresses": [
{
"ip4": "172.24.0.174",
"cidr": 16
}
],
"v6addresses": []
}
}
}
],
"routes": [
{
"cidr": 24,
"gateway": "172.24.0.200",
"network": "10.0.0.0"
},
{
"cidr": 0,
"gateway": "172.24.0.1",
"network": "default"
}
],
"dedicatedManagement": false
}
}
]
}
}
}
networkInterfaces
—enter the network interfaces of the existing configuration. You can configure ethernet interfaces (eth
), loopback interface (lo
), or bonding interfaces (bond
).For more information on the network interface configuration, refer to Configuring bonding interfaces and Configuring interface IP addresses.
routes
—enter the static route information that you would like to configure.network
—enter the IP address of the network. If you are configuring a default gateway, set the value todefault
gateway
—enter the IP address of the gateway (via-address).cidr
—enter the CIDR of the IP space for the specified network. If you are configuring a default route, set the value to0
.
dedicatedManagement
—set to false. Dedicated management is only supported for DNS/DHCP Servers.