MT LoadMaster Cisco UCS B-Series

 

1Introduction

KEMP Multi-Tenant LoadMaster (MT LoadMaster) is a true multi-tenant application service delivery control point for enterprises and Managed Service Providers (MSPs). Multi-Tenant LoadMaster's flexible virtualized architecture (HyperFlex™) provides the framework for delivering KEMP as well as independent third party virtualized network functions (VNFs) in a single Cisco UCS B-Series platform.

This document describes the steps required to install the KEMP Multi-Tenant LoadMaster software on a Cisco UCS B-Series Blade Server.

PXE and USB booting options are also supported by the LoadMaster installation ISO file.

1.1Pre-requisites

The following pre-requisites are required:

  • A Cisco UCS B-Series Blade Server
  • An ISO image with the Multi-Tenant LoadMaster software
  • For a standalone Multi-Tenant LoadMaster, one IP-address on an untagged LAN is required
  • The local disk on the Cisco UCS B-Series Blade Server should be empty as it will be re-partitioned during the installation of the Multi-Tenant LoadMaster software
  • A minimum of 2GB RAM must be available on the guest environment for the Multi-Tenant LoadMaster
  • The boot order on the B-Series Blade Server should be configured as follows:
    1. Local Disk
    2. CD_ROM

The boot order can be checked and configured within the Boot Order Details section on the General tab of the Cisco Unified Computing Systems (UCS) Manager.

2Create Policies

A number of policies can be created in order to optimize Multi-Tenant LoadMaster performance. The sections below give instructions on how to create these policies in the Cisco Unified Computing System Manager.

2.1Create a QoS Policy

Figure 2‑1: QoS Policies

  1. In the menu on the left, go to Policies > root > QoS Policies.

Figure 2‑2: Add

  1. Click the plus button on the right to create a new policy.

Figure 2‑3: QOS policy

  1. Enter a Name.
  2. Select Platinum as the Priority.
  3. Enter 65535 in the Burst(Bytes) text box.
  4. Enter 40000000 in the Rate(Kbps) text box.
  5. Ensure that Host Control is set to none.
  6. Click OK.
  7. Click OK again.

2.2Create an Adapter Policy

Figure 2‑4: Servers

  1. Select the Servers tab at the top.
  2. Expand Policies.

Figure 2‑5: Adapter Policies

  1. Expand root.
  2. Select Adapter Policies.

Figure 2‑6: Add Policy

  1. Click the plus button on the right.

Figure 2‑7: Resources

  1. In the Resources section, set the field values as follows:

a)Transmit Queues: 1

b)Ring Size: 256

c)Receive Queues: 1

d)Ring Size: 512

e)Completion Queues: 2

f)Interrupts: 4

Figure 2‑8: Policy Options

  1. In the Options section, select Enabled for the following options:

a)Transmit Checksum Offload

b)Receive Checksum Offload

c)TCP Segmentation Offload

d)TCP Large Receive Offload

  1. Select Disabled for Receive Side Scaling (RSS).
  2. Enter 5 in the Failback Timeout (Seconds) text box.
  3. Select MSI X as the Interrupt Mode.
  4. Select Min as the Interrupt Coalescing Type.
  5. Enter 125 as the Interrupt Timer (us).
  6. Click OK.

2.3Create a LAN Connectivity Policy

If you are planning on having a setup containing 4 arms or more, creating a LAN Connectivity Policy will help to reduce complexity. Follow the steps below to create this policy:

  1. Select the LAN tab.
  1. Expand Policies.
  2. Expand root.
  3. Select LAN Connectivity Policies.

Figure 2‑9: Create

  1. Click the plus button on the right to create a new policy.

Figure 2‑10: Create LAN Connectivity Policy

  1. Enter a recognizable Name, for example LM_4vNIC.
  2. Enter a Description.
  3. Click Add to specify a vNIC.
  4. Enter a Name for the vNIC, for example eth 0.
  5. Select the relevant option in the MAC Address Assignment drop-down list.
  6. Select the relevant clients to be on Fabric A.

To maximize input and output it is best to divide the number of client VLANs and server VLANs between Fabric A and Fabric B. For example, if there are 2 clients VLANs – one should be on Fabric A and the other should be on Fabric B. Similarly, if there are 2 server VLANs – one should be on A and the other on B.

  1. Select a Native VLAN.
  2. Set the MTU to 9000.

The MTU must have the same value as it does in the Priority of the selected QoS Policy.

  1. Expand the Operational Parameters section.
  2. Select the relevant Adapter Policy.
  3. Select the relevant QoS Policy.
  4. Click OK.
  5. Click OK again.
  6. Add the remaining vNICs needed.

2.4Create a BIOS Policy

To create a BIOS policy:

  1. Select the Servers tab at the top.
  2. Expand Policies.
  3. Expand root.
  4. Select BIOS Policies.

Figure 2‑11: Create

  1. Click the plus button to create a new policy.

Figure 2‑12: Main BIOS Properties

  1. Enter a Name.
  2. Set the options as follows:

a)Reboot on BIOS Settings Change: Disabled

b)Quiet Boot: enabled

c)Post Error Pause: disabled

d)Resume Ac On Power Loss: last-state

e)Front Panel Lockout: disabled

Figure 2‑13: Advanced Processor options

  1. In the Advanced > Processor tab, set the options as follows:

a)Turbo Boost: enabled

b)Enhanced Intel Speedstep: enabled

c)Hyper Threading: disabled

d)Core Multi Processing: all

e)Execute Disabled Bit: Platform Default

f)Virtualization Technology (VT): Platform Default

g)Direct Cache Access: enabled

h)Processor C State: disabled

i)Processor C1E: disabled

j)Processor C3 Report: disabled

k)Processor C6 Report: disabled

l)Processor C7 Report: disabled

m)CPU Performance: hpc

n)Max Variable MTRR Setting: Platform Default

Figure 2‑14: Advanced Intel Directed IO options

  1. In the Advanced > Intel Directed IO tab, set all of the options to Platform Default.

Figure 2‑15: RAS Memory

  1. In the Advanced > RAS Memory tab, set the options as follows:

a)Memory RAS Config: maximum-performance

b)NUMA: enabled

c)LV DDR Mode: performance-mode

  1. Click OK.

3Installing Multi-Tenant LoadMaster on the Cisco UCS Blade

The following steps must be completed in order to install the Multi-Tenant LoadMaster software on the Cisco B-Series Blade Server. These steps must be completed on the jump host, where the Multi-Tenant LoadMaster installation ISO image is located.

3.1Open the KVM console for the B-series server

  1. Select the Servers tab in the navigation pane.
  1. Within the expandable tree view select the relevant server.
  2. Select the General tab in the main pane.

Figure 3‑1: KVM Manager

  1. Click the KVM console option within the Actions section.
  2. This will open a KVM console window from which the installation can be completed.

3.2Create a Virtual CD-ROM

In the KVM console window complete the following steps:

  1. Select the Virtual Media tab.
  1. Click the Add Image button to open a file-selector window.
  2. Select the Multi-Tenant LoadMaster installation image.
  3. Click the Open button.
  4. Click the Mapped button.

The Virtual Media tab of the KVM console should now correspond with Figure 32.

3.3Boot the Server

The server is now ready to be booted to complete the installation procedure.

If the local disk is empty, that is contains no valid boot partition, simply click the Boot Server option on the KVM console. The server is booted from the previously mapped virtual CD.

If the local disk does contain a valid bootable partition you can explicitly select the virtual CD from the servers boot menu by completing the following steps:

  1. Press F6 when the boot process reaches the point illustrated inFigure 33.
  2. The Boot Menu Screen, as illustrated byFigure 34, appears

Figure 3‑4 The Boot Menu Screen

  1. Select the Cisco Virtual CD/DVD option and press Enter.

The server should boot from the virtual CD.

3.4Install the Multi-Tenant LoadMaster

Once the server boots from the virtual CD, as described in Section 0, the Multi-Tenant LoadMaster installation process automatically begins.

For further information on the different boot options that are available, refer to the Bare Metal Boot Options, Technical Note.

The serial number should be automatically pulled from the Multi-Tenant LoadMaster. If it is not, please enter it when prompted.

Figure 3‑5: Select disk/partition

  1. Select disk/partition and press OK.

Figure 3‑6: Select the target disk

  1. Select the target disk for installation and press OK.

Figure 3‑7: Delete existing partition(s)

  1. Select delete existing partition(s) and press OK.

Figure 3‑8: Start installation

  1. Select start installation and press OK.
  2. Press OK.

The installation then completes.

3.5Boot the Installed Multi-Tenant LoadMaster

The server is now ready to be rebooted with the Multi-Tenant LoadMaster software installed on the local disk. Within the KVM console, select the Ctrl-Alt-Del option from the Macros drop-down menu.

The server should now begin to boot from the local disk.

Figure 3‑9: Finished booting

The Multi-Tenant LoadMaster should obtain an IP address via DHCP, please note this value.

If the Multi-Tenant LoadMaster does not obtain an IP address via DHCP then the Multi-Tenant LoadMaster must be manually configured using the KVM console once the license key has been obtained.

Please refer to Section 4 for further information regarding manually configuring the Multi-Tenant LoadMaster.

3.6Configure the Multi-Tenant LoadMaster

The Multi-Tenant LoadMaster must now be configured to operate within the network configuration.

  1. In an internet browser, enter the IP address that was previously noted in Section 3.5.

Ensure to enter https:// before the IP address.

  1. A warning may appear regarding website security certificates. Please click the continue/ignore option.

Figure 3‑10: License Required

  1. If using the Online licensing method, fill out the fields and click License Now.

If you are starting with a trial license, there is no need to enter an Order ID. If you are starting with a permanent license, enter the KEMP Order ID# if this was provided to you.

If using the Offline Licensing method, select Offline Licensing, obtain the license text, paste it into the License field and click Apply License.

For detailed instructions on how to register for a KEMP ID and license the Multi-Tenant LoadMaster, refer to the Licensing, Feature Description.

  1. The Multi-Tenant LoadMaster End User License Agreement screen appears.

Please read the license agreement and, if you are willing to accept the conditions therein, click on the Agree button to proceed.

  1. A screen will then appear asking if you are OK with the Multi-Tenant LoadMaster regularly contacting KEMP to check for updates and other information. Click the relevant button to proceed.

C:\Users\kgaffney\Dropbox (Kemp Technologies)\ongoing projects\Reskin\2fourall_password_cropped.PNG

Figure 3‑11 Change password screen

  1. The Change Password screen appears. Enter a password for the bal user in the Password input field and retype it in the Retype Password input field.
  2. The login screen appears again, enter the bal user name and the new password as defined in the previous step.
  3. In the screen informing you that the password has changed, press the Continue button
  4. If your machine has shipped with a temporary license you should get a warning informing you that a temporary license has been installed on your machine and for how long the license is valid.

Figure 3‑12 Temporary license warning

Click the OK button.

  1. You should now connect to the Appliance Vitals screen of the Multi-Tenant LoadMaster.

Figure 3‑13 Appliance Vitals screen

  1. Click the System Configuration menu option.
  2. Click the eth0 menu option within the Interfaces section.

Figure 3‑14 Network Interface screen

  1. In the Network Interface 0 screen, enter the IP address of the eth0 interface, the network facing interface of the Multi-Tenant LoadMaster, in the Interface Address input field.
  2. Click the Set Address button
  3. Click the eth1 menu option within the Interfaces section
  4. In the Network Interface 1 screen, enter the IP address of the eth1 interface, the farm-side interface of the Multi-Tenant LoadMaster, in the Interface Address input field.
  5. Click the Set Address button

This interface is optional, depending on the network configuration.

  1. Click the Local DNS Configuration > Hostname Configuration menu option.

Figure 3‑15 Set Hostname screen

  1. In the Hostname Configuration screen, enter the hostname into the Current Hostname text box.
  2. Click the Set Hostname button.
  3. Select the Local DNS Configuration > DNS Configuration menu option.

Figure 3‑16 DNS configuration screen

  1. In the DNS Configuration screen, enter the IP address(es) of the DNS Server(s) which will be used to resolve names locally on the Multi-Tenant LoadMaster into the DNS NameServer text box.
  2. Click the Add button.
  3. Enter the domain name that is to be prepended to requests to the DNS nameserver into the DNS Search Domains text box.
  4. Click the Add button.
  5. Go to System Configuration > Network Setup > Default Gateway in the main menu.

Figure 3‑17 Default gateway screen

  1. In the DNS configuration screen, enter the IP address of the default gateway into the IPv4 Default Gateway Address input field.
  2. Click the Set IPv4 Default Gateway button.

The Multi-Tenant LoadMaster is now fully installed and ready to be used. For further information on how to configure and implement the Multi-Tenant LoadMaster, please refer to the Multi-Tenant LoadMaster documentation which can be downloaded from the http://kemptechnologies.com/documentation page.

4Configuring the Multi-Tenant LoadMaster via the KVM Console

If the Multi-Tenant LoadMaster does not automatically obtain an IP address using DHCP as described in Step 4, Section 3.6, or if you prefer to configure the Multi-Tenant LoadMaster via the KVM console, then the following configuration steps must be completed before starting the Multi-Tenant LoadMaster.

  1. Login into the Multi-Tenant LoadMaster via the KVM-console using the default settings:

lb100 login: bal

Password: 1fourall

  1. If required, change the Multi-Tenant LoadMaster password (for the bal user) when prompted to within the KVM console.
  2. If required, click OK within the dialog box informing of the password change
  3. Click OK within Quick Setup Help dialog box.
  4. Enter the IP address of the eth0 interface, the network facing interface of the Multi-Tenant LoadMaster, in the input field within the Network Side Interface Address dialog box.

This value must be configured from within the KVM console.

  1. Click OK.
  2. Enter the IP address of the eth1 interface in the input field within the Farm Side Interface Address dialog box. The eth1 interface is only configured if you have a two-armed configuration.

This interface can be configured at a later date using the Multi-Tenant LoadMaster WUI if preferred.

  1. Click OK.
  2. Enter the hostname (you can accept the default value of ‘KEMP’) into the input field of the Multi-Tenant LoadMaster Hostname dialog box.
  3. Click OK.
  4. Enter the IP address(es) of the DNS Server(s) which will be used to resolve names locally on the Multi-Tenant LoadMaster into the input field of the Name Server IP Addresses dialog box.

This interface can be configured at a later date using the Multi-Tenant LoadMaster WUI if preferred.

  1. Click OK.
  2. Enter the domain name that is to be prepended to requests to the DNS nameserver in the input field of the Domain List dialog box.

This interface can be configured at a later date using the Multi-Tenant LoadMaster WUI if preferred

  1. Click OK.
  2. Enter the IP address of the default gateway in the input field of the Default Gateway dialog box.

This value must be configured from within the KVM console.

  1. Click OK.

Figure 4‑1 Default Gateway

  1. Press Yes within the Reboot screen when requested.
  2. In your internet browser enter the IP address of the eth0 inter you entered in Step 6.

Ensure you place ’https://’ before the IP address.

  1. You may get a warning regarding website security certificates. Please click on the continue/ignore option.
  2. The End User License Agreement screen appears.

Please read the license agreement and, if you are willing to accept the conditions therein, click on the Agree button to proceed.

  1. If your machine has shipped with a temporary license you should get a warning informing you that a temporary license has been installed on your machine and for how long the license is valid.

Click OK.

Figure 4‑2: Appliance Vitals

  1. You should now connect to the Multi-Tenant LoadMaster Manager Vitals screen of the Multi-Tenant LoadMaster.

The Multi-Tenant LoadMaster is now fully installed and ready to be used. For further information on how to configure and implement the Multi-Tenant LoadMaster, please refer to the Multi-Tenant LoadMaster documentation which can be downloaded from the http://kemptechnologies.com/documentation page.

5References

Unless otherwise specified, the below documents can be found at www.kemptechnologies.com/documentation.

Licensing, Feature Description Bare Metal Boot Options, Technical Note

Document History

Date

Change

Reason for Change

Version

Resp.

July 2014

Initial draft of the document

Initial draft of the document

1.0

LB

Jan 2015

Release updates

Updated for 7.1-24 release

1.1

LB

Mar 2015

Minor update

Enhancement made

1.2

LB

June 2015

Minor update

Enhancement made

1.3

LB

June 2015

Release updates

Updated for 7.1-28 release

1.4

LB

Sep 2015

Screenshot updates

LoadMaster WUI reskin

3.0

KG

Nov 2015

Release updates

Updated for MT_7.1-30 release

4.0

LB

Dec 2015

Minor update

Enhancement made

5.0

LB

Jan 2016

Minor update

Updated

6.0

LB

Mar 2016

Minor update

Enhancement made

7.0

LB

Was this article helpful?

0 out of 0 found this helpful

Comments