Appendix

Rack Cisco HyperFlex Nodes

For details on the HyperFlex cluster and node limits, see Cisco HX Data Platform Storage Cluster Specifications in the latest version of the Release Notes for Cisco HX Data Platform.

For details on the installation of Cisco HyperFlex nodes, refer to respective links from the following table:

Type of Node To Be Installed

Reference

Converged Nodes

HyperFlex HX220c M5 Nodes

Cisco HyperFlex HX220c M5 Node Installation Guides

HyperFlex HX240c M5 Nodes

Cisco HyperFlex HX240c M5 Node Installation Guides

Note

Hyper-V is only supported on M5 servers.

Setting Up the Fabric Interconnects

Configure a redundant pair of fabric interconnects for high availability. Connect the two fabric interconnects directly using Ethernet cables between the L1 and L2 high availability ports. Connect Port L1 on fabric interconnect A to port L1 on fabric interconnect B, and Port L2 on fabric interconnect A to port L2 on fabric interconnect B. This allows both the fabric interconnects to continuously monitor the status of each other.

Verify and obtain the following information before connecting the fabric interconnects.

Item

Description

Verify the physical connections of the fabric interconnects.

  • Console port for the first fabric interconnect must be physically connected to a computer or console server.

  • Management Ethernet port (mgmt0) must be connected to an external hub, switch, or router.

  • L1 ports on both the fabric interconnects must be directly connected to each other.

  • L2 ports on both the fabric interconnects must be directly connected to each other.

Verify console port parameters on the computer terminal.

  • 9600 baud

  • 8 data bits

  • No parity

  • 1 stop bit

Obtain information for initial setup.

Collect the following information for initial setup:

  • System name

  • Password for admin account

  • Three static IP addresses

  • Subnet mask for three static IP addresses

  • Default gateway IP address

  • DNS server IP address

  • Domain name for the system

Both fabric interconnects must go through the same setup process. Set up the primary fabric interconnect and enable for cluster configuration. When you use the same process to set up the secondary fabric interconnect, it detects the first fabric interconnect as a peer.

Configure the Primary Fabric Interconnect Using GUI

You can either follow the procedure below for configuring the primary fabric interconnect or watch Cisco UCS Manager Initial Setup part 1.


Attention
IPv4 addressing is required for HyperFlex.

Procedure

Step 1

Power up the fabric interconnect.

You will see the power on self-test messages as the fabric interconnect boosts.

Step 2

If the system obtains a lease, go to step 6, otherwise, continue to the next step.

Step 3

Connect to the console port.

Step 4

At the installation method prompt, enter gui.

Step 5

If the system cannot access a DHCP server, you are prompted to enter the following information:

  • IPv4 address for the management port on the fabric interconnect.

  • IPv4 subnet mask for the management port on the fabric interconnect.

  • IPv4 address for the default gateway assigned to the fabric interconnect.

Step 6

Copy the web link from the prompt into a web browser and go to the Cisco UCS Manager GUI launch page.

Step 7

On the Cisco UCS Manager GUI launch page, select Express Setup.

Step 8

On the Express Setup page, select Initial Setup and click Submit.

Step 9

In the Cluster and Fabric Setup area:

  1. Click the Enable Clustering option.

  2. For the Fabric Setup option, select Fabric A.

  3. In the Cluster IP Address field, enter the IPv4 address that Cisco UCS Manager will use.

Step 10

In the System Setup area, complete the following fields:

Field

Description

System Name field

The name assigned to the Cisco UCS domain.

In a standalone configuration, the system adds "-A" to the system name. In a cluster configuration, the system adds "-A" to the fabric interconnect assigned to fabric A, and "-B" to the fabric interconnect assigned to fabric B.

Admin Password field

The password used for the Admin account on the fabric interconnect.

Choose a strong password that meets the guidelines for Cisco UCS Manager passwords. This password cannot be blank.

Confirm Admin Password field

The password used for the Admin account on the fabric interconnect.

Mgmt IP Address field

The static IPv4 address for the management port on the fabric interconnect.

Mgmt IP Netmask field or Mgmt IP Prefix field

The IPv4 subnet mask prefix for the management port on the fabric interconnect.

Note

 

The system prompts for a Mgmt IP Netmask or a Mgmt IP Prefix based on what address type you entered in the Mgmt IP Address field.

Default Gateway field

The IPv4 address for the default gateway assigned to the management port on the fabric interconnect.

Note

 

The system prompts for a Default Gateway address type based on what type you entered in the Mgmt IP Address field.

DNS Server IP field

The IPv4 address for the DNS Server assigned to the fabric interconnect.

Domain Name field

The name of the domain in which the fabric interconnect resides.

Step 11

Click Submit.

A page displays the results of your setup operation.

Configure the Subordinate Fabric Interconnect Using GUI

You can either follow the procedure below for configuring the subordinate fabric interconnect or watch Cisco UCS Manager Initial Setup part 2.

Procedure

Step 1

Power up the fabric interconnect.

You will see the power-up self-test message as the fabric interconnect boots.

Step 2

It the system obtains a lease, go to step 6, otherwise, continue to the next step.

Step 3

Connect to the console port.

Step 4

At the installation method prompt, enter gui.

Step 5

If the system cannot access a DHCP server, you are prompted to enter the following information:

  • IPv4 address for the management port on the fabric interconnect

  • IPv4 subnet mask for the management port on the fabric interconnect

  • IPv4 address for the default gateway assigned to the fabric interconnect

Step 6

Copy the web link from the prompt into a web browser and go to the Cisco UCS Manager GUI launch page.

Step 7

On the Cisco UCS Manager GUI launch page, select Express Setup.

Step 8

On the Express Setup page, select Initial Setup and click Submit.

The fabric interconnect should detect the configuration information for the first fabric interconnect.

Step 9

In the Cluster and Fabric Setup Area:

  1. Select the Enable Clustering option.

  2. For the Fabric Setup option, make sure Fabric B is selected.

Step 10

In the System Setup Area, enter the password for the Admin account into the Admin Password of Master field.

The Manager Initial Setup Area is displayed.

Step 11

In the Manager Initial Setup Area, complete the following:

Field

Description

Peer FI is IPv4 Cluster enabled. Please Provide Local Fabric Interconnect Mgmt0 IPv4 Address field

Enter an IPv4 address for the Mgmt0 interface on the local fabric interconnect.

Step 12

Click Submit.

A page displays the results of your setup operation.

How to upload the iso and img file to the installer VM using WinSCP

You may choose to use the Installer VM as host for the ISO and IMG files to install Hyper-V. To accomplish that you need to upload the Windows ISO and the Cisco HyperFlex driver image to the installer.

For the purpose of this guide we will use WinSCP, you can use whatever SCP client you have available.

Procedure

Step 1

Download a SCP client for Windows. It could be WinSCP (https://winscp.net/eng/download.php) and install it on your workstation.

Step 2

Connect to your installer VM from WinSCP. Username root and password Cisco123

Important

 

Systems ship with a default password of Cisco123 that must be changed during installation. You cannot continue installation unless you specify a new user supplied password.

Step 3

Accept the key and add to the cache.

Step 4

Once connected browse to the folder /var/www/localhost/images/ on the installer. Browse to where to local files are located on your machine.

Step 5

Transfer the files. File names can be copied if you access the URL in a browser: http://<controller_IP>/images/

DNS Records

Refer to the list below for the DNS records that must be added to your environment.

Add-DnsServerResourceRecordA -Name "" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername
Add-DnsServerResourceRecordA -Name "" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername
Add-DnsServerResourceRecordA -Name "" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername
Add-DnsServerResourceRecordA -Name "" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername
Add-DnsServerResourceRecordA -Name "" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername
Add-DnsServerResourceRecordA -Name "" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername
Add-DnsServerResourceRecordA -Name "" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername
Add-DnsServerResourceRecordA -Name "" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername
Add-DnsServerResourceRecordA -Name "" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername
Add-DnsServerResourceRecordA -Name "" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername
Add-DnsServerResourceRecordA -Name "" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername
Add-DnsServerResourceRecordA -Name "-CNTL" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername
Add-DnsServerResourceRecordA -Name "-CNTL" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername
Add-DnsServerResourceRecordA -Name "-CNTL" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername
Add-DnsServerResourceRecordA -Name "-CNTL" -ZoneName "Ciscolab.dk" -AllowUpdateAny -IPv4Address "" -TimeToLive 01:00:00 -CreatePtr -computername

Updating HX Service Account Username and Password

A new password must be updated within an HX Cluster if the password expired or was changed voluntarily. Perform the following step to update the Cisco HX Service Account Password.

Note

The access to VMs and datastores will still continue to work without the new password. However, the cluster will experience some issues with the Alert, Systems Status, Support Bundle and Datastore Access reporting.

Before you begin

Ensure that the Cisco HX Service Account User Name is in the following format:

username@domain.com

Procedure

Step 1

Run the resethypervcred -u command from one of the Storage Controller node within the cluster.

Example:

The following is an example of the command with sample output:
root@cvmhv1:~# resethypervcred -u
Enter service admin name:<hx-service-account>@domain.com
Enter service admin passwd:
Enter local admin name:administrator
Enter local admin passwd:
Hyperv creds updated successfully

Log into each controller vm as the root user and run restart hxHyperVSvcMgr.

After you have completed the reset and service restarts, then log into HX Connect as the HX Service Account User to verify your login works and HX Connect is displaying the cluster information.

Step 2

To change the HX Service Account username, run the resethypervcred -u command.

Example:

root@cvmhv1:~# resethypervcred -u
Enter service admin name:hxadmin@domain.com
Enter service admin passwd:
Enter local admin name:administrator
Enter local admin passwd:
Hyperv creds updated successfully