---
title: "Configuring a Network Automation Appliance for IPv4 and IPv6"
canonical: "https://docs.infoblox.com/space/IIGFNA1A/14647382/Configuring%20a%20Network%20Automation%20Appliance%20for%20IPv4%20and%20IPv6"
format: markdown
---
If Network Automation uses DHCP, make a note of the IP address assigned to Network Automation, and then use the Setup Wizard as described in <span style="color: #000000">*Configuring Network Automation Using the Setup Wizard*</span> in the *Network* *Automation* *Administrator's* *Guide*.

---

**Note:** The Network Automation appliance supports dual-stack connectivity for reachability on both IPv4 and IPv6 networks. You can use either or both.

---

Otherwise, configure IP addresses as follows:

1. At the CLI (command line interface) command prompt, enter **configure** **server**, and specify the following:
2. Enter the new Database Name and press Enter.

`Database Name is a descriptive name for this deployment. It is used in reports titles, headers, etc.`

`Recommended: Begin name with uppercase letter.`

`Database Name []: ``Corp100_west`

3. For the first-time installation, you can choose to generate a new HTTPS certificate.

`Do you want to generate a new HTTPS Certificate? (y/n) [n]: ``y`

4. Enter the local domain name in which the controller resides. This value is used for truncating device names in Network Automation data sets throughout the system.

`Domain Name 1 (e.g., example.com) []: ``corp100.com`

`Domain Name 2 (optional) []:`

5. Enter the time server IP address if one is available or is necessary:

`Time Server [us.pool.ntp.org]:`

6. Enter the time zone region by typing in the suggested numeric value from the list.

`Enter choice (0-47) [0]: 45`

7. Enter the time zone location by typing in the suggested numeric value from the list:

`Choose a location within your time zone.`

|  |  |  |  |  |  |
| --- | --- | --- | --- | --- | --- |
| `0.` | `Alaska` | `1.` | `Aleutian` | `2. Arizona` | `3. Central` |
| `4.` | `East-Indiana` | `5.` | `Eastern` | `6. Hawaii` | `7. Indiana-Starke` |
| `8.` | `Michigan` | `9.` | `Mountain` | `10. Pacific` | `11. Samoa` |

`Enter choice (0-11) [0]: 10`

8. Follow the steps for configuring the management port IP settings:

`+++ Configuring Management Port Settings`

`You must configure an IPv4 or IPv6 address/mask on the management port.`

`Network Automation can perform analysis from the management port or a separate`

`scan port.`

`IP Address (optional) []: 10.120.25.212`

`Subnet Mask (optional) []: 255.255.255.0`

`IPv6 Address (optional) []:`

`IPv6 Prefix (optional):`

`You must provide either an IPv4 gateway, an IPv6 gateway, or both.`

`IPv4 Default Gateway (optional) []: 10.120.25.1`

`IPv6 Default Gateway (optional) []:`

---

**Note**: You must provide either an IPv4 or IPv6 gateway address, or both, depending on the Network Automation IP address.

---

The configure server command then requests configuration of the Scan port if you are running two-port configuration:

`Do you want to configure the Scan Port? <y/n> [n]:`

Entering **N** instructs the configure server command to skip IP configuration for the Scan port.

---

**Note**: The Network Automation appliance uses active Ethernet ports labeled MGMT, LAN1 and LAN2. The LAN1 port corresponds to the Scan port referred to in the configure server command. When you define the Scan port settings in configure server, it is the LAN1 port IP connectivity you are defining for the appliance. In two-port configurations, this interface is used to connect to the networks being scanned and managed by Network Automation. You can also configure the LAN2 port as a another scan interface through the Network Automation UI.

---

9. Enter **n** to continue. This enforces single-port appliance configuration, and displays the appliance DNS Server settings:

`DNS Servers are used to map hostnames to IP addresses.`

`You may enter up to 2 name servers below.`

`DNS Server 1 (IP) []: 10.102.3.50`

`DNS Server 2 (optional) []: 10.102.3.10`

`DNS server 1 and DNS Server 2:`

10. Enter the IP addresses of the DNS servers that Network Automation will use.

> Macro (legacy-content)

`Current settings:`  
`Database Name: rgraceDev`  
`Server Name: rgrace-dev`  
`Domain Name 1: inca.infoblox.com`  
`Domain Name 2: inmd.infoblox.com`  
`Time Server: us.pool.ntp.org`  
`Time Region: US`  
`Time Location: Pacific`  
`Mgmt Port IP Address: 10.120.25.212`  
`Mgmt Port Subnet Mask: 255.255.255.0`  
`Mgmt Port IPv6 Address:`  
`Mgmt Port IPv6 Prefix:`  
`Mgmt Port IPv4 Default Gateway: 10.120.25.1`  
`Mgmt Port IPv6 Default Gateway:`  
`Scan Port IP Address:`  
`Scan Port Subnet Mask:`  
`Scan Port IPv6 Address:`  
`Scan Port IPv6 Prefix:`  
`Scan Port IPv4 Default Gateway:`

`Scan Port IPv6 Default Gateway:`

`DNS Server 1: 10.102.3.50`

`DNS Server 2: 10.102.3.10`


`— Edit these settings? <y/n> [n]:`

11. If you accept the settings, enter **n**.

`— Configure the system with these settings? <y/n> [y]:`

12. Enter **y** to configure the server with the settings you entered. Wait while Network Automation configures the network and sets the web interface to use the new IP address.

13. Network Automation automatically reboots if you change its default time zone. Otherwise, a reboot is not necessary.

14. Enter **exit** to log out.

15. Shut down the Network Automation unit and physically install it in the global network. The unit is now reachable on its global static IP address for further CLI configuration and UI access.

16. Configure Network Automation software using the Setup Wizard, as described in *Configuring Network Automation Using the Setup Wizard* in the *Network Automation Administrator's **Guide*.