, page 1 The Setup UI is a web interface for installing and configuring the Cisco TetrationOS Software. Before You Begin The switches and servers in the rack must be powered up. Step 1 Click the Run Diagnostic Test button. This might take several minutes to complete. Optionally, you can click the Refresh button until the status indicator (inside the Run Diagnostic Test button) changes to pass or fail. If the diagnostic test passes, the Upload button is enabled. If the status does not change, click Refresh. If a failure occurs, you will see diagnostic information. Use that information and the following table to resolve the problems and then rerun this step. Note If you are an advanced user and understand the consequences, you may bypass a failing diagnostic test by selecting the Override diagnostic test checkbox. This enables the Upload button regardless of the test results. Errors Remedies Unequal Switch Port: Interface1 switch port (%d)!= Interface2 switch port (%d) The cabling and racking document expects you to connect the interfaces to the same Switch Port number on both the leaf switches. If this error shows up then they aren't connected to the same switch port. Connected to the same switch: Both interfaces are connected to the same switch. The cabling and racking document expects you to connect interface1 to leaf1 and interface2 to leaf2. If this error shows up then they are connected to the same leaf switch. 1
Errors Invalid Number of Interfaces: Expected %d Actual %d. Invalid Public Interface port, public interface on port Invalid Disk Type: Expected Disk Type: %s Actual Disk Type: %s Invalid Disk Size: Expected Disk Size: %s Actual Disk size: %s No private-1/2 interface found, check to see at least two 10 G interfaces are connected. Invalid cable to Leaf-1/2, private-1/2 should be less than port:36 actual: %d Remedies The compute servers have three interfaces. Cache servers have two. The first base servers have two and the last four base servers have three interfaces. The first of the three interfaces on the compute servers %d expected to be greater than %d (eth2) needs to be connected to a switch port greater than 40 and the last 4 base servers are expected to be either 37 and 38 on the two leaf switches. The first 16 servers (compute nodes) and the last 12 servers (base nodes) have HDD and the Cache nodes have SDD. If this error shows up then the racking or cabling is incorrect. Servers not racked correctly. Follow the cabling and racking document specification on how the servers are racked and cabled to the leaf switches. Every server needs at least two interfaces to the leaf switches. If you see this error, there are fewer than two cables on the server. If the cables are hooked up, ensure they are inserted all the way in. Private interfaces (eth3 and eth5) should be cabled to the switch port correcponding to the rack position from the top. The top most server goes to switch Eth1/1 and the one at the bottom goes to switch port Eth1/36 on both of the leaf switches. This error is triggered if the private interfaces are connected to a switch port greater than 36. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Click the Upload button. Select a Cisco TetrationOS mother RPM to install. Depending on the speed of your connection, the upload process can take some time to complete. When the upload completes, the RPM is installed. Click Refresh until the Status line shows the new status. Click Continue. The status of all nodes in the cluster is displayed. Initially the nodes have a state of New and the Role and Type columns are blank. The cluster agent runs in the background coordinating role assignment. The state of each node changes to Initialized and the Role and Type are displayed. (Optional) If you want to see more details about a particular node: 1 Click the corresponding View Details button. 2
2 Click the Refresh button until enough nodes are available. Note If you are an advanced user and understand the consequences, you can select the Override checkbox to continue with fewer than the minimum number of nodes. Click the Initialize button to continue. Step 8 On the site configuration page, enter the specifics to customize your cluster and make it accessible within your network. Fill in all of the required fields which are marked with an asterisk (*). Most fields provide an example of the expected input as placeholder text. The following table describes the content needed for each field. Field Site Names* UI Admin Email* Routable Network* Routable Network Mask* Routable Network Gateway* DNS Resolver* DNS Domain* NTP Servers* HTTP Proxy Host HTTP Proxy Port SMTP Server* SMTP Port* UI Hypervisor 1* UI Hypervisor 2* UI App 1* Description A unique name for this cluster. The name should be brief and contain only letters, numbers, underscores (_) and dashes (-). The email address of the individual who will be responsible for administering Tetration within your organization. Carefully ensure this address is correct before proceeding. The routable network in which the Tetration cluster is connected. The mask used to determine the subnet of the routable network. The IP address of the network gateway. A space-separated list of DNS resolver addresses. A search domain that should be used by the cluster. A space-separated list of NTP server names or IP addresses. Deprecated, leave blank. Deprecated, leave blank. The name or IP address of an SNMP server that can be used by Tetration to send email. The port number of the SMTP server provided above. above. above. above. This address will be used by the VIP to provide high-availability to the UI. 3
Field UI App 2* UI VIP* UI VIP VRID* UI FQDN* UI Google Analytics Key UI Airbrake Key Collector Public IPs* Description above. This address will be used by the VIP to provide high-availability to the UI. above. This will be the address of the web frontend. This address should be used when setting up a domain name for this cluster (see UI FQDN below). A unique numeric identifier. The fully qualified domain name that has been (or will be) setup for this cluster. This name should point to the IP address specified above as UI VIP. If you have a Google Analytics account and would like to track usage of the Tetration UI, enter a key here. If you have an Airbrake account and would like to track diagnostic messages geneerated by the Tetration UI, enter a key here. A space-separated list of up to 12 routable IPs that the Tetration sensors will use to communicate with the cluster. Step 9 Step 10 Step 11 Step 12 Step 13 Step 14 Click the Save and Continue button. A consolidated version of the settings provided on the previous page displays. This is the Site File that will be provided to the installation script in the next step. On this page, a background script will begin validating the settings and results will be shown beneath the Results heading. Click the Refresh link until it has finished. (Optional) Review the results for any error messages. To correct issues, click the Back button. Once the script finishes without errors, click Run to continue. The setup script begins running in the background. This process can take some time to complete. Click the Refresh Output button to monitor the installation process. Note If you are an advanced user and understand the consequences, you can halt the installation process by clicking the Kill Background Process button. Once the installation has completed successfully, your cluster is available. Navigate to the VIP UI address provided on the Site Configuration page (be sure to use HTTPS) https://vip-ip Click the Forgot password? link and then enter the UI Admin Email address provided on the Site Configuration page and click the Reset Password button. You will receive an email with a link that you can use to set your password for the first time. You should then be able to sign into the system. 4
5
6