deploying ovf and ova tasks import VApp upload disk update options

Deploy BIG-IP VE on ESXi

To create a Large-IP^® VE virtual appliance, download a template from F5^® and deploy it in your surround.

1. In a browser, open the F5 Downloads page (https://downloads.f5.com) and log in.
2. On the Downloads Overview folio, select Observe a Download.
3. Under Product Line, select Large-IP v13.x/Virtual Edition.
4. Nether Name, select Virtual-Edition.
5. If the End User Software License is displayed, read it and so click I Accept.
6. Download i of the files that ends with scsi.ova.
7. Kickoff the vSphere client and log in.
8. From the vSphere File menu, choose Deploy OVF Template.
9. Browse to the .ova file and click Side by side.

   The template is verified.

10. Click Next and complete the wizard. Annotation the following.

    Section	Details
    Configuration	Choose from the available configurations. You can change CPU or RAM later.
    Storage	If you decide to increment storage later on, y'all must as well accommodate the Big-IP directories to use the actress storage space. See Increasing disk space for Big-IP® VE for details.
    Datastore	Choose Thick for production environments. Sparse is sufficient for lab environments.
    Source Networks	The sorcerer leads y'all through creating four networks: internal, external, management, and high availability (HA).
    Fix to Complete	If you want to deploy with the four default networks, and then select the Power on after deployment bank check box. If you want a single NIC deployment, practise not select this bank check box.

11. Click Finish.
12. For a single NIC deployment, edit the virtual machine'south backdrop and remove Network adapter two, three, and 4.

The virtual machine is created, too as two user accounts.

• The root account provides access locally, using SSH, or the F5 Configuration utility. The root account countersign is default.
• The admin account provides access through the web interface. The admin account countersign is admin.

You should modify passwords for both accounts before bringing a organization into production.

If you lot need to create a redundant configuration, place the 2 BIG-IP VE virtual appliances (the active-standby pair) on split up physical hosts. You can reach this in one of two ways:

• Manually create a virtual machine peer on each host.
• If you lot are using VMware Dynamic Resource Scheduler (DRS), create a DRS rule with the Split up Virtual Auto option that includes each Large-IP VE in the pair.

Setting the BIG-IP VE management IP address and passwords

When yous deploy BIG-IP VE:

• If you lot accept DHCP in your environment, a management IP accost is assigned.
• If yous practice not take DHCP, a generic direction IP address (192.168.1.245) is assigned.
• A password is assigned to the default accounts: root (default) and admin (admin).

In ESXi 5.v u2, 6.0, 6.5, and after, in Big-IP VE thirteen.one.0.two and later, you can specify a specific management IP address (IPv4 or IPv6) and unlike default passwords.

There are many different ways to practice this.

• Earlier deploy, by editing the OVA file'south properties:
  • By using the Common OVF Tool (COT)
  • By editing the OVA descriptor file, or
  • By using the VMware OVF tool
  • By using the tool of your option
• During deploy, by using the API of your choice to ready the vApp properties
• After deploy:
  • By manually updating the vApp properties
  • Past using a Custom Specification
  • Past using the Large-IP direction config tool

Important: This functionality is supported in a multi-NIC environment only.

Use Common OVF Tool to set management IP address and default passwords

You tin edit the OVA (template) properties so that when you deploy Large-IP VE, you can specify values for the management IP address and default passwords.

To edit the OVA, you lot can use the Common OVF Tool (COT).

For more than information about COT, meet http://cot.readthedocs.io/en/latest.

1. Copy the OVA to a machine with enough free infinite (at least ii times the OVA file size).
2. Run a command similar the following:

   cot edit-properties <source filename>.ova -p net.mgmt.addr=""+cord -p net.mgmt.gw=""+string -p user.root.pwd=""+string -p user.admin.pwd=""+string -u -o <destination filename>.ova

The OVA properties are updated.

Then, when you deploy the OVA file, y'all tin specify the values.

Note: After you lot set the IP address and password, if y'all want to set it again, y'all must starting time delete this file on Big-IP: /shared/vadc/.ve_cust_done

OVA properties file for setting management IP address and default passwords

You can edit the OVA (template) properties and so that when yous deploy Large-IP VE, y'all tin can specify values for the management IP accost and default passwords.

Before deploy, you tin extract the contents of the OVA file to edit the OVF properties directly.

Modify the OVF file and add together the post-obit properties to the <ProductSection> area of the descriptor file.

<Category>Network properties</Category>     <Holding ovf:primal="net.mgmt.addr" ovf:type="string" ovf:value="" ovf:userConfigurable="true">         <Label>mgmt-addr</Label>         <Description>F5 Large-IP VE'due south management address in the format of "IP/prefix"</Description>     </Belongings>     <Property ovf:key="net.mgmt.gw" ovf:type="string" ovf:value="" ovf:userConfigurable="true">         <Label>mgmt-gw</Characterization>         <Description>F5 BIG-IP VE's management default gateway</Clarification>     </Holding> <Category>User backdrop</Category>     <Holding ovf:key="user.root.pwd" ovf:type="cord" ovf:value="" ovf:userConfigurable="true">         <Label>root-pwd</Label>         <Clarification>F5 BIG-IP VE's SHA-512 shadow or plain-text password for "root" user</Description>     </Property>     <Holding ovf:cardinal="user.admin.pwd" ovf:type="cord" ovf:value="" ovf:userConfigurable="true">         <Label>admin-pwd</Label>         <Description>F5 Big-IP VE'due south SHA-512 shadow or plainly-text countersign for "admin" user</Description>     </Property>                

OVF tool for setting management IP address and default passwords

You can edit the OVA (template) properties so that when you deploy BIG-IP VE, you lot tin specify values for the direction IP address and default passwords.

Using VMware'due south OVF tool, hither is an example of code yous would employ to deploy BIG-IP VE with these settings.

ovftool --sourceType=OVA \ --acceptAllEulas \ --noSSLVerify \ --diskMode=sparse \ --skipManifestCheck \ --X:logToConsole \ --X:logLevel=verbose \ --datastore='mylab' \ --name='vmname' \ --vmFolder='myfolder' \ --deploymentOption='dualcpu' \ --internet:"Internal=Internal" \ --net:"Direction=Management" \ --net:"HA=HA" \ --net:"External=External" \ --Ten:injectOvfEnv \ --prop:internet.mgmt.addr="ten.ten.10.124/22" \ --prop:net.mgmt.gw="ten.10.11.254" \ --prop:user.root.pwd="mypassword" \ --prop:user.admin.pwd="mypassword" \ <path_to_bigip.ova> \ "vi://user[@userdomain]:countersign@domain.com/<datacenter-name>/host/<esxi-host>"                

Edit vApp to set the management IP address and default passwords

Afterward you deploy a VM running BIG-IP VE, you tin manually assign a management IP address and root and admin passwords. Utilize this procedure if y'all want to set these values one time on a specific VM.

Notation: These instructions may differ slightly, based on your version of vSphere.

1. Stop the VM.
2. Right-click the VM and choose Edit Settings.
3. Click the vApp Options tab.
4. In the Authoring department, aggrandize the Properties area.
5. Click New.
6. On the Edit Belongings Settings window, consummate the fields.

   Category	Label	Key ID	Type
   Big-IP VE	admin-pwd	user.admin.pwd	String

   Of import: The countersign tin be patently text or SHA-512 encrypted.

7. Click OK.
8. Create three more properties, using these values:

   Category	Characterization	Central ID	Type
   Big-IP VE	root-pwd	user.root.pwd	Cord
   BIG-IP VE	mgmt-addr	net.mgmt.addr	Cord
   Large-IP VE	mgmt-gw	net.mgmt.gw	String

   Important: The Key ID must be the verbal value shown in the table.

9. Roll upward and you should at present have these settings available:

   

10. Populate these fields and click OK.
11. Outset the VM. The properties are applied.

Afterward y'all set the IP address and password, if you want to fix information technology again, you must first delete this file: /shared/vadc/.ve_cust_done

Employ Customization Specification to set management IP address

You tin prompt the user to enter an IP accost and mask after Large-IP VE is deployed. To do this, you can create a VMware Custom Specification that y'all can use over and over on multiple VMs.

Notes:

• These instructions may differ slightly, based on your version of vSphere.
• This procedure is for setting the management IP address; non for setting default passwords.
• You can do this process after you deploy, not during.

1. Ensure the BIG-IP VE example is powered off.
2. Create a Custom Specification policy.
   1. Open up the vSphere Client Dwelling house page.
   2. In the Navigator pane, under Policies and Profiles, click Customization Specification Managing director.
   3. Click Create a new specification.

      Page	Setting	Value
      Specify Properties	Target VM Operating System	Linux
      Prepare Calculator Name	Use the virtual machine name	Recommended
      Prepare Computer Name	Domain	Your domain
      Fourth dimension Zone	Expanse	Your area/time zone
      Configure Network	Manually select custom settings	Create iv NICs (management, internal, external, HA). For the management NIC, click Edit the selected adapter. Then for IPv4 or IPv6, click Prompt the user for an address when the specification is used and click OK. If you enter static values, they are applied. However, if you desire to re-use this Custom Spec, yous probable want to prompt the user. Annotation: For IPv6, yous must gear up values for both IPv4 and IPv6.
      Enter DNS and Domain Settings		Not supported. You may accept to enter a value to motility by this page.

3. Edit the VM to apply this policy.
   1. Right-click the VM and choose .
   2. Select your specification from the list and click Next.
   3. Enter the IP address and mask and click Terminate.

Notation: After you ready the IP accost and password, if you want to fix information technology again, yous must offset delete this file: /shared/vadc/.ve_cust_done

Utilize Big-IP Configuration utility tool to ready management IP address

If your network has DHCP, an IP address is automatically assigned to BIG-IP^® VE during deployment. You can utilise this address to access the BIG-IP VE Configuration utility or tmsh command-line utility.

If no IP address was assigned, you can assign i past using the Big-IP Configuration utility tool.

1. Connect to the virtual car by using the hypervisor'southward console.
2. At the login prompt, type root.
3. At the password prompt, type default.
4. Type config and press Enter.

   The F5 Management Port Setup screen opens.

5. Click OK.
6. Select No and follow the instructions for manually assigning an IP address and netmask for the direction port.

You can use a hypervisor generic statement, such as tmsh show sys direction-ip to confirm that the management IP address was set properly.

Y'all can now log into the Big-IP VE Config utility, and license and provision Big-IP VE.

Configure SR-IOV on the guest

Before you can consummate these steps, you must have configured Single Root I/O Virtualization (SR-IOV) on the hypervisor.

Afterward deploying BIG-IP^® VE, to configure SR-IOV on the guest, yous must add three PCI device NICs and map them to your networks.

1. In vSphere, delete the existing Source Networks for External, Internal, and HA.

   Important: Leave the Source Network for Management.

2. Edit the settings for the virtual machine to add a PCI device.

   If your hypervisor was ready up correctly, there volition be xvi virtual functions on each port (05:ten.x and 05:xi:x).

3. Map the new device to the VLAN for your internal subnet.
4. Echo steps 2 and three for the external and HA VLANs.
5. When all iv destination networks are correctly mapped, click Next.

   The Ready to Complete screen opens.

harwardbacturter46.blogspot.com

Source: https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-ve-setup-vmware-esxi-13-1-0/3.html

Share this post