Installing Additional Software - Kubernetes

Kubernetes Appliance Software Installation Guide

prodname
Kubernetes
created_date
June 2018
category
Installation
featnum
B035-6103-068K
  • The SM3G node software must be installed before installing the BYNET software to ensure proper PMA ID and node type assignment.
  • The most recent Server Management Web Services software is ins on the system.
Make sure you have downloaded the latest Stacki OS, Infra, and KubeOS carts from the Teradata Software Server or Artifactory Stable Repository. For information about Teradata Software Server, see: http://tssprod.teradata.com:8080/TSFS/
  1. Verify that the /etc/opt/teradata/sm3g/smainfo file is on the server. The smainfo file is generated by server management and must exist before installing the BYNET driver. The smainfo file must contain the following:
    • A unique PMAID (PMA)
    • Unique BYNET IP addresses for BYNET Domain 0 (BYNETIP and BYNETMASK entries)
    • Unique BYNET IP addresses for BYNET Domain 1 (BYNET1IP and BYNET1MASK entries)
    Example smainfo file:
    PMA 7364 
    BYNETIP 39.0.8.11 
    BYNETMASK 255.240.0.0 
    BYNET1IP 39.64.8.11 
    BYNET1MASK 255.240.0.0
    SYSTEM 1
  2. To create the /etc/opt/teradata/bynet directory, type the following command: mkdir -p /etc/opt/teradata/bynet
    All nodes, managed servers, and managed storage servers in a system must use BYNET version 3.7.4.1 or later. The BYNET version on the nodes and servers must be compatible. To be compatible, the first three numbers must match, but the patch number can be different. For example, 3.7.4.1 and 3.7.4.2 are compatible.
  3. Create an /etc/opt/teradata/bynet/netdev file.
  4. In the netdev file, specify local loopback for BYNET Domain 0 and the network interfaces to be used for BYNET Domain 1. For example:
    lo domain 0 
    mlx4_0_1 domain 1 
    mlx4_0_2 domain 1
  5. Install software packages using the PUT Install and Upgrade Software operation:
    • If PUT does not autoselect the latest package for installation, manually select it.
    • Choose non-VM&F for an initial installation.
    1. At the Media Sources step, choose /var/opt/teradata/pkgs This includes all the subdirectories.
    2. Install the following InfiniBand software packages:
      • BYNET driver
      • InfiniBand utilities
      • Adapter firmware
    3. Install KubeOS packages.
    4. Upgrade all other packages, as applicable.
    5. Reboot the node when prompted by PUT.
  6. Verify both InfiniBand adapter ports are functioning properly: ibinfo -d local_status For example:
    channel                                   logical  physical    link
                name        guid        port     lid     state     state   speed
           =========  ================ =====  ======  ======== =========   =====
              mlx4_0  e41d2d03000a50f1     1     0xa    ACTIVE    LinkUp 4XFDR10
              mlx4_0  e41d2d03000a50f2     2     0xa    ACTIVE    LinkUp 4XFDR10
  7. Type bam -s to verify:
    • Domain 0 row: The Net name column contains lo, which identifies a server using local loopback for BYNET Domain 0.
    • Domain 1 rows: The Nodes column equals the number of routes in the Routes column, showing the correct number of nodes and servers on each BYNET network interface of BYNET Domain 1.
    For example:
    Version information:
          03.07.04.00 BLM commands
          03.07.04.00 BLM driver
          17.03.09.09 BLM protocol
        
          Node is running in protocol emulation mode.
        
          Domain  System  State
          0       1       attached
          1       -       attached
        
          Domain  Nodes   Routes  Net name
          0       1       1       lo
          1       10      10      mlx4_0_1
          1       10      10      mlx4_0_2
  8. Verify that the BYNET Domain 0 (byn0) and BYNET Domain 1 (byn1) interfaces on the server are configured with the IP address and netmask defined in the /etc/opt/teradata/sm3g/smainfo file: # ifconfig byn0 # ifconfig byn1 For example:
    # ifconfig byn0 
    byn0 Link encap:Ethernet HWaddr 00:00:27:40:10:c1 
         inet addr:39.0.8.11 Bcast:39.15.255.255 Mask:255.240.0.0 
         inet6 addr: fe80::200:27ff:fe40:10c1/64 Scope:Link 
         UP BROADCAST RUNNING MTU:65520 Metric:1 
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 
         collisions:0 txqueuelen:1000 
         RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) 
    # ifconfig byn1 
    byn1 Link encap:Ethernet HWaddr 00:00:27:20:08:01 
         inet addr:39.64.8.11 Bcast:39.79.255.255 Mask:255.240.0.0 
         inet6 addr: fe80::200:27ff:fe20:801/64 Scope:Link 
         UP BROADCAST RUNNING MTU:65520 Metric:1 
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 
         collisions:0 txqueuelen:1000 
         RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
  9. Ping every node and server on the BYNET Domain 1 (byn1) interface: ping -c 1 IP address For example:
    # ping -c 1 39.0.8.12 
    PING 39.0.8.12 (39.0.8.12) 56(84) bytes of data. 
    64 bytes from 39.0.8.12: icmp_seq=1 ttl=64 time=0.011 ms 
    --- 39.0.8.12 ping statistics--- 
    1 packets transmitted, 1 received, 0% packet loss, time 1 ms 
    rtt min/avg/max/mdev = 0.029/3.590/7.151/3.561 ms
  10. As appropriate, add BYNET entries to the /etc/hosts file. For example:
    39.0.8.8 uda001-8 
    39.0.8.9 uda001-9 
    39.0.8.10 uda001-10 
    39.0.16.8 uda002-8 
    39.0.16.9 uda002-9 
    39.0.16.10 uda002-10
    The /etc/hosts changes take effect immediately.