4.
5.
6.
7.
1.
2.
3.
4.
5.
6.
7.
8.
shortcut menu.
In the dialog box, select in the Network Components list, andLocal Area Connection Properties Internet Protocol Version 4 (TCP/IPv4)
then click .Properties
In the dialog box, select Use the following IP address, and then fill in the andInternet Protocol (TCP/IP) Properties IP address Subnet m
fields using the IP address and subnet mask .ask 169.254.1.5 255.255.255.0
Click in the and dialog boxes. (Depending on your operatingOK Internet Protocol (TCP/IP) Properties Local Area Connection Properties
system, you might need to reboot your computer.)
Note: This address change is necessary only for the initial setup of Network Automation. Once the setup is complete, return your workstation to
its prior configuration.
8. Click Close in the dialog box.Local Area Connections Status
9. Temporarily disconnect the Network Automation appliance from the network by unplugging the Ethernet cable from the MGMT port of the
appliance.
10. Obtain an Ethernet cross-over cable and connect your computer to the MGMT port using the cross-over cable.
11. Use an SSH client to access Network Automation at the IP address 169.254.1.1.
12. Log in with user name and password .admin admin
13. Continue the configuration by following the instructions described in Configuring a Network Automation .Appliance for IPv4 and IPv6
Notes on Windows IPv6 Configuration
Of course, users can manage Network Automation on an IPv6 network. The Network Automation Management port has its own factory default
link-local IPv6 address that is unique on its connected subnet. The default IPv6 address derives from the Ethernet MAC address of the
Management interface (MGMT).
You must use a Windows 7 system to configure Network Automation to run on an IPv6 network, because Windows 7 natively supports IPv6.
To configure a new Infoblox Network Automation appliance to be managed through IPv6, do the following:
Reboot Windows 7, ensure that it is enabled for IPv6 networking, and connect it to the management (MGMT) port of the Network
Automation appliance, using a standard Ethernet cable.
On the Windows 7 system, open a DOS command line window and run .ipconfig
Check the listing in the Local Area Connection section of the ipconfig listing, and make a note of the interface number associated with the
PC's IPv6 Link Local address. The IPv6 value will have an fe80: prefix and end with a %* designator, such as fe80:505:ac3b:49b7:d
. The value 15 in this example is the interface number, which will vary with each client.c38%15
In a Windows command line, run the following command:
netsh interface ipv6 show neighbor
Find the Interface *: Local Area Connection section (the * corresponds to the interface number for your PC system's IPv6 address). No
entry should be present in this category for any address starting with the fe80: prefix.
In the Windows PC's command line, run a multicast IPv6 ping to all nodes on the subnet where the Management port is running. This
executes a multicast IPv6 ping to the Network Automation management port connected to the PC.
In the Windows command prompt, run the following command:
ping -6 -n 5 ff02::1
Allow the command to complete whether or not responses occur.
In the Windows PC's command line, run the following command a second time:
netsh interface ipv6 show neighbor
The MGMT port IPv6 link-local address should now appear in the neighbor table under the Interface xx: Local Area Connection section,
similar to the following:
fe80::230:48ff:febc:97da 00-30-48-bc-97-da Reachable
This is the link-local address of the Network Automation appliance management port (MGMT).
Open an SSH client session to the Network Automation CLI at the IPv6 address shown in Step 6 along with the interface number. Log in
with the factory default username/password admin/admin.
Next, you assign a globally routable static IPv6 address on the management port.
Proceed with appliance configuration as described in .Configuring a Network Automation Appliance for IPv4 and IPv6
Configuring a Network Automation Appliance for IPv4 and IPv6
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 in the .Configuring Network Automation Using the Setup Wizard 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: