Network Configuration for Cisco UCS Director Baremetal Agent

Transcription

1 Network Configuration for Cisco UCS Director Baremetal Agent This chapter contains the following sections: About the Network Configuration Options, page 1 Single Network for Management and PXE, page 1 Separate Networks for Management and PXE, page 5 Configuring Cisco UCS Director Baremetal Agent as a DHCP Server, page 11 Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address, page 11 About the Network Configuration Options You can choose between the following network configuration options for Cisco UCS Director Baremetal Agent: Single network for management and PXE Separate networks for management and PXE You should choose the network configuration option that best meets the requirements of your environment. Single Network for Management and PXE We recommend that you choose this network configuration option if your environment permits the following to be hosted on the same network interface and layer 2 network: Services provided by Cisco UCS Director Baremetal Agent, such as DHCP, TFTP, and HTTP OL

2 Prerequisites and Assumptions for a Single Network Configuration Network Configuration for Cisco UCS Director Baremetal Agent Management traffic between Cisco UCS Director Baremetal Agent and Cisco UCS Director or other devices and appliances Figure 1: Sample Topology for a Single Network Prerequisites and Assumptions for a Single Network Configuration If you plan to configure Cisco UCS Director Baremetal Agent with a single network configuration, ensure that your environment meets the following prerequisites and assumptions: Cisco UCS Director has been installed and the network interface configured, as described in the appropriate Cisco UCS Director installation guide. Cisco UCS Director is reachable through a web browser and you can log in. Cisco UCS Director Baremetal Agent has been installed, as described in the Cisco UCS Director Baremetal Agent Installation and Configuration Guide and no additional configuration has been performed. The required single Management and PXE VLAN is provisioned and available as a virtual port group or port profile that VMs can be attached to or leverage. 2 OL

3 Network Configuration for Cisco UCS Director Baremetal Agent Configuring Cisco UCS Director Baremetal Agent for a Single Network Configuring Cisco UCS Director Baremetal Agent for a Single Network Note This procedure assumes that the VMs have been created in the VMware vsphere 5.1 hypervisor. Although configurations on other releases of VMware vsphere or on other hypervisors may vary slightly, the required steps are applicable to all supported hypervisors and supported releases. Step 1 Step 2 Step 3 Step 4 Step 5 If necessary, power on the Cisco UCS Director Baremetal Agent VM. Open the VMware vsphere VM Console for the Cisco UCS Director Baremetal Agent VM. When prompted, configure the network interface as necessary. By default, this interface is set to use DHCP as described in Configuring Cisco UCS Director Baremetal Agent as a DHCP Server, on page 11. However, you can configure a static IP address, if required, as described in Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address, on page 11 After the network is configured and the Cisco UCS Director Baremetal Agent VM has completely booted up, close the VMware vsphere VM Console. The VM is fully booted up when you see a screen that prompts with the following text: To manage this VM browse to where IP_address represents the IP address of the Cisco UCS Director Baremetal Agent VM. Open an SSH session to the IP Address for the Cisco UCS Director Baremetal Agent VM, and use the following default credentials if you have not already changed them: User name root Password pxeboot Step 6 Step 7 Step 8 Step 9 Use ifconfig to verify that the network interface eth0 is configured properly and make a note of the IP address. Navigate to the /opt/infra/networkservices/ directory. In the run.sh file, enter the IP address of the Cisco UCS Director Baremetal Agent eth0 interface for the following parameters: -DpxeServer.ip= -DpxeServer.mgmt_vlan_ip= Open a new SSH session to the IP address for the Cisco UCS Director VM. Note In a multi-node setup, you need to open the SSH session to the VM for the Inventory database node. The following default credentials for this VM might have been changed during the configuration of Cisco UCS Director: User name shelladmin Password changeme Step 10 In the shelladmin, do the following to add the Cisco UCS Director Baremetal Agent hostname and IP address: a) From the menu, choose the option for Add Cisco UCS Director Baremetal Agent Hostname/IP and press Enter. OL

4 Configuring Cisco UCS Director Baremetal Agent for a Single Network Network Configuration for Cisco UCS Director Baremetal Agent Step 11 Step 12 Step 13 Step 14 Step 15 Step 16 b) When prompted, enter the IP Address and Hostname of the Cisco UCS Director Baremetal Agent VM. In the shelladmin, do the following to enable the database for Cisco UCS Director Baremetal Agent: Note In a multi-node setup, you need to perform this step on the Inventory database node. a) From the menu, choose the option for Enable Database for Cisco UCS Director Baremetal Agent and press Enter. b) Enter y for yes. c) When prompted, enter the IP Address or Hostname of the Cisco UCS Director Baremetal Agent VM. From the shelladmin menu, choose the option for Quit and exit the console. Return to the SSH console for the Cisco UCS Director Baremetal Agent VM. Navigate to the /etc/ directory. Copy the dhcpd.conf.sample file, as follows: cp./dhcpd.conf.sample./dhcpd.conf Edit the dhcpd.conf file to set up the DHCP services that are required for PXE booting. The following sample dhcpd.conf file includes the DHCP services. Note The next-server line is required and must include the IP address of the Cisco UCS Director Baremetal Agent VM. # # DHCP Server Configuration file. # see /usr/share/doc/dhcp*/dhcpd.conf.sample # ddns-update-style interim; ignore client-updates; subnet netmask { option routers ; option subnet-mask ; option nis-domain "domain.org"; option domain-name "domain.org"; option domain-name-servers ; option time-offset ; # Eastern Standard Time range dynamic-bootp ; default-lease-time 21600; max-lease-time 43200; allow booting; allow bootp; next-server ; # IP of my PXE server filename "/pxelinux.0"; } 4 OL

5 Network Configuration for Cisco UCS Director Baremetal Agent Separate Networks for Management and PXE Step 17 Step 18 Step 19 Step 20 Step 21 At the prompt, enter service dhcpd restart to restart the DHCP services. If DNS is not configured on Cisco UCS Director Baremetal Agent, add the hostname and IP address of Cisco UCS Director to the /etc/hosts file to ensure DNS hostname to IP address resolution. Navigate to the /opt/infra/ directory. Run the configure.sh script and, when prompted, provide the IP address of Cisco UCS Director as a parameter. Note In a multi-node setup, you need to perform this step on the Inventory database node. In a web browser, navigate to the IP address for Cisco UCS Director and verify that Cisco UCS Director Baremetal Agent is available and active, as follows: a) Login as a user with admin privileges. b) From the menu bar, choose Administration > Physical Accounts. c) Click the Network Services Agent tab. d) Verify that the list includes Cisco UCS Director Baremetal Agent and that the status is Active. e) If you do not see Cisco UCS Director Baremetal Agent in the list, click Refresh to add it to the list of available network services agents. Separate Networks for Management and PXE We recommend that you choose this network configuration option if your environment does not permit the following to be hosted on the same network interface and layer 2 network: On the PXE network, services provided by Cisco UCS Director Baremetal Agent, such as DHCP, TFTP, and HTTP OL

6 Prerequisites and Assumptions for a Separate Network Configuration Network Configuration for Cisco UCS Director Baremetal Agent On the Management network, traffic between Cisco UCS Director Baremetal Agent and Cisco UCS Director or other devices and appliances Figure 2: Sample Topology for Separate PXE and Management Networks Prerequisites and Assumptions for a Separate Network Configuration If you plan to configure Cisco UCS Director Baremetal Agent with a separate network configuration, ensure that your environment meets the following prerequisites and assumptions: Cisco UCS Director has been installed and the network interface configured, as described in the appropriate Cisco UCS Director installation guide. Cisco UCS Director is reachable through a web browser and you can log in. Cisco UCS Director Baremetal Agent has been installed, as described in the Cisco UCS Director Baremetal Agent Installation and Configuration Guide, no additional configuration has been performed and the VM is powered off. The following networks are provisioned and available as a virtual port group or port profile that VMs can be attached to or leverage: Management (MGMT) network Used for traffic between Cisco UCS Director Baremetal Agent and Cisco UCS Director PXE network Used for PXE services traffic, such as DHCP, HTTP, and TFTP 6 OL

7 Network Configuration for Cisco UCS Director Baremetal Agent Configuring Cisco UCS Director Baremetal Agent for Separate Networks Note The PXE network/vlan must be configured as the native, or default, VLAN on the server. For example, for a Cisco UCS server, edit the vnic template associated with the server and choose the PXE network/vlan as the native VLAN. You can perform this configuration in Cisco UCS Manager or Cisco UCS Director. Configuring Cisco UCS Director Baremetal Agent for Separate Networks Note This procedure assumes that the VMs have been created in the VMware vsphere 5.1 hypervisor. Although configurations on other releases of VMware vsphere or on other hypervisors may vary slightly, the required steps are applicable to all supported hypervisors and supported releases. Step 1 Step 2 Step 3 Step 4 In the VMware vsphere Client interface, right-click the Cisco UCS Director Baremetal Agent VM and choose Edit Settings. On the Hardware tab of the Virtual Machine Properties dialog box, click Add. On the Device Type page of the Add Hardware dialog box, choose Network Adapter and click Next. The network adapter option might read Ethernet Adapter. On the Network Type page of the Add Hardware dialog box, do the following: a) From the Type drop-down list, choose an adapter type. You can accept the default value of Flexible. b) From the Network Label drop-down list, choose the network/vlan associated with PXE traffic to which you want to connect this network interface. c) Click Next. Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Review the summary and click Finish to add the network adapter to the VM. Click OK to close the Virtual Machine Properties dialog box for the VM. Power on the Cisco UCS Director Baremetal Agent VM. Open the VMware vsphere VM Console for the Cisco UCS Director Baremetal Agent VM. When prompted, configure the network interface as necessary. By default, this interface is set to use DHCP as described in Configuring Cisco UCS Director Baremetal Agent as a DHCP Server, on page 11. However, you can configure a static IP address, if required, as described in Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address, on page 11 After the network is configured and the Cisco UCS Director Baremetal Agent VM has completely booted up, close the VMware vsphere VM Console. The VM is fully booted up when you see a screen that prompts with the following text: To manage this VM browse to where IP_address represents the IP address of the Cisco UCS Director Baremetal Agent VM. Open an SSH session to the IP Address for the Cisco UCS Director Baremetal Agent VM, and use the following default credentials if you have not already changed them: OL

8 Configuring Cisco UCS Director Baremetal Agent for Separate Networks Network Configuration for Cisco UCS Director Baremetal Agent User name root Password pxeboot Step 12 Step 13 Step 14 Step 15 Use ifconfig to verify that the network interface eth0 is configured properly and make a note of the IP address. Navigate to the etc/sysconfig/nework-scripts/ directory. Copy the ifcfg-eth0 file to ifcfg-eth1, as follows: cp./ifcfg-eth0./ifcfg-eth1 Edit the ifcfg-eth1 file to set up the PXE traffic interface. The following sample ifcfg-eth1 file shows the values that you need to update in the file. Note If you defined the GATEWAY variable for the eth0 interface, do not define that variable for the eth1 interface. DEVICE=eth [number] BOOTPROTO=[static or DHCP] ONBOOT=yes IPADDR=[if static] GATEWAY=[if static] NETMASK=[if static] TYPE=Ethernet PEERDNS=yes USERCTL=no IPV6INIT=no Step 16 Step 17 At the prompt, enter ifup eth1 to bring the eth1 interface online. Use ifconfig to verify that the network interfaces are configured properly. The following example shows correctly configured network interfaces: eth0 Link encap:ethernet HWaddr F0:50:56:AB:26:45 inet addr: Bcast: Mask: inet6 addr: fb80::250:56ff:faeb:2654/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:20264 errors:0 dropped:0 overruns:0 frame:0 TX packets:2318 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes: (1.7 KiB) TX bytes: (541.0 KiB) Interrupt: 59 Base address:0x2024 eth1 Link encap:ethernet HWaddr 00:50:56:AB:61:1D inet addr: Bcast: Mask: inet6 addr: fb80::250:56ff:faeb:611d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:109 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1296 (1.2 KiB) TX bytes:22248 (21.7 KiB) Interrupt: 67 Base address:0x20c4 lo Link encap:local loopback inet addr: Mask: inet6 addr: ::1/128 Scope:Host 8 OL

9 Network Configuration for Cisco UCS Director Baremetal Agent Configuring Cisco UCS Director Baremetal Agent for Separate Networks UP LOOPBACK RUNNING MTU:1636 Metric:1 RX packets:75 errors:0 dropped:0 overruns:0 frame:0 TX packets:75 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25479 (24.8 KiB) TX bytes:25479 (24.8 KiB) Step 18 Step 19 Step 20 Navigate to the /opt/infra/networkservices/ directory. In the run.sh file, enter the IP address of the Cisco UCS Director Baremetal Agent eth0 interface for the following parameters: -DpxeServer.ip= -DpxeServer.mgmt_vlan_ip= Open a new SSH session to the IP address for the Cisco UCS Director VM. Note In a multi-node setup, you need to open the SSH session to the VM for the Inventory database node. The following default credentials for this VM might have been changed during the configuration of Cisco UCS Director: User name shelladmin Password changeme Step 21 Step 22 Step 23 Step 24 Step 25 Step 26 Step 27 In the shelladmin, do the following to add the Cisco UCS Director Baremetal Agent hostname and IP address: a) From the menu, choose the option for Add Cisco UCS Director Baremetal Agent Hostname/IP and press Enter. b) When prompted, enter the IP Address and Hostname of the Cisco UCS Director Baremetal Agent VM. In the shelladmin, do the following to enable the database for Cisco UCS Director Baremetal Agent: Note In a multi-node setup, you need to perform this step on the Inventory database node. a) From the menu, choose the option for Enable Database for Cisco UCS Director Baremetal Agent and press Enter. b) Enter y for yes. c) When prompted, enter the IP Address or Hostname of the Cisco UCS Director Baremetal Agent VM. From the shelladmin menu, choose the option for Quit and exit the console. Return to the SSH console for the Cisco UCS Director Baremetal Agent VM. Navigate to the /etc/ directory. Copy the dhcpd.conf.sample file, as follows: cp./dhcpd.conf.sample./dhcpd.conf Edit the dhcpd.conf file to set up the DHCP services that are required for PXE booting. The following sample dhcpd.conf file includes the DHCP services. Note The next-server line is required and must include the IP address of eth1, the PXE interface, for the Cisco UCS Director Baremetal Agent VM. # # DHCP Server Configuration file. # see /usr/share/doc/dhcp*/dhcpd.conf.sample # OL

10 Configuring Cisco UCS Director Baremetal Agent for Separate Networks Network Configuration for Cisco UCS Director Baremetal Agent ddns-update-style interim; ignore client-updates; subnet netmask { option routers ; option subnet-mask ; option nis-domain "domain.org"; option domain-name "domain.org"; option domain-name-servers ; option time-offset ; # Eastern Standard Time range dynamic-bootp ; default-lease-time 21600; max-lease-time 43200; allow booting; allow bootp; next-server ; # IP of my PXE server filename "/pxelinux.0"; } Step 28 Step 29 Step 30 Step 31 Step 32 Step 33 Navigate to the /etc/sysconfig/ directory. Edit the dhcpd file to add eth1 to the DHCPDARGS= parameter. At the prompt, enter service dhcpd restart to restart the DHCP services. Navigate to the /opt/infra/ directory. Run the configure.sh script and, when prompted, provide the IP address of Cisco UCS Director as a parameter. Note In a multi-node setup, you need to perform this step on the Inventory database node. In a web browser, navigate to the IP address for Cisco UCS Director and verify that Cisco UCS Director Baremetal Agent is available and active, as follows: a) Login as a user with admin privileges. b) From the menu bar, choose Administration > Physical Accounts. c) Click the Network Services Agent tab. d) Verify that the list includes Cisco UCS Director Baremetal Agent and that the status is Active. e) If you do not see Cisco UCS Director Baremetal Agent in the list, click Refresh to add it to the list of available network services agents. 10 OL

11 Network Configuration for Cisco UCS Director Baremetal Agent Configuring Cisco UCS Director Baremetal Agent as a DHCP Server Configuring Cisco UCS Director Baremetal Agent as a DHCP Server Perform this task if you want to use Cisco UCS Director Baremetal Agent as a DHCP server and did not configure it during installation. Step 1 Step 2 Step 3 Step 4 Step 5 Log in to Cisco UCS Director Baremetal Agent. In the shelladmin, navigate to the /etc directory. cd /etc Copy the dhcpd.conf.sample file to dhcpd.conf so that the existing file can be overwritten. cp /etc/dhcpd.conf.sample /etc/dhcpd.conf When you are prompted to overwrite dhcpd.conf, enter yes. Edit the dhcpd.conf file, using vi or another editor. Example: vi dhcpd.conf Step 6 Edit the following parameters to match your network: Option router Subnet mask Domain name server Dynamic-bootp range Step 7 Start the DHCP server. /etc/init.d/dhcpd start Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address Perform this task if you want to use a static IP address and did not configure it when you installed Cisco UCS Director Baremetal Agent. Step 1 Step 2 Step 3 In VMware vcenter, right-click on the Cisco UCS Director Baremetal Agent VM and choose Open Console. Navigate to the etc/sysconfig/nework-scripts/ directory. Edit the ifcfg-interface_number file with the static IP address you want to assign. OL

12 Configuring Cisco UCS Director Baremetal Agent to Use a Static IP Address Network Configuration for Cisco UCS Director Baremetal Agent The following sample ifcfg-eth1 file shows the configuration for a static IP address. DEVICE=eth1 BOOTPROTO=none ONBOOT=yes TYPE=Ethernet PEERDNS=yes USERCTL=no IPV6INIT=yes IPV6ADDR=2001:0db8:2f6a:4c03::4/63 #IPV6_AUTOCONF=no IPADDR= NETMASK= GATEWAY= BROADCAST= Step 4 When you are prompted about whether to configure a static IP address, enter yes and then enter the following information: IP address Gateway Netmask 12 OL