Site Preparation Task List - Appliance for Hadoop

Appliance for Hadoop 5 Platform Product and Site Preparation Guide

Product
Appliance for Hadoop
Published
February 2018
Language
English (United States)
Last Update
2018-05-03
dita:mapPath
pgm1471885501602.ditamap
dita:ditavalPath
hadoop5.ditaval.ditaval
dita:id
axw1471650877780
Product Category
Hardware

The Teradata representative uses the following checklist as a guideline to discuss and complete the required tasks for site preparation.

Site Preparation Task List
Done Task Comments and Reference
  Initiate customer site prep discussion/meeting  
  Remote connectivity discussion
At a minimum, Teradata ServiceConnect is required for remote support and maintenance. For customers with additional security and/or privacy requirements, Teradata ServiceConnect Enhanced is available.
Customers without Teradata ServiceConnect or Teradata ServiceConnect Enhanced will not have access to Critical System Management and Business Critical services and will receive limited reactive maintenance and support service.
Engage the customer on issues of remote connectivity, including:
  • Confirmation of Teradata ServiceConnect or Teradata ServiceConnect Enhanced remote connectivity acceptance.
    Server Management Web Services (SMWeb) requires Teradata ServiceConnect or Teradata ServiceConnect Enhanced.
  • If Teradata ServiceConnect or Teradata ServiceConnect Enhanced is not being implemented:
    1. Confirm that the customer has signed the ServiceConnect Decline letter and Maintenance & Support Contract Non-Compliance Acknowledgement documents.
    2. Confirm that no remote connectivity, or non-standard remote connectivity has been approved by:

      CS Region Vice President

      Region Operations Director or Area Director

      GSO Vice President

      GTS Director

    Important: All four levels of approval are required.

    For more information about non-standard support policies, see: Non Standard support process and policy.

  • Confirmation that there is outbound network access for FTP
  • Verification of security settings

For information on remote connectivity requirements, go to: Remote Connectivity Guidelines.

Connection from the product to an outside network (customer LAN, public LAN, and so on) must be done with a shielded cable (unless optical Ethernet is used). Failure to use a shielded cable may invalidate the regulatory compliance of the product.
  Power capacity

What is the total calculated power in watts or kilowatts for the whole system?

What is the total power capacity at the site?

Is there a power plan with regard to adequate power capacity and power redundancy?

Has the power capacity issue been discussed with the customer?

For power requirement calculation, refer to Power Consumption.

  Power receptacles

Does the customer have the appropriate type and number of receptacles for all of the system cabinets?

Refer to Input Power Plugs and Receptacles .

  Site ID created or verified

For information on Site IDs, go to: Site ID Creation Guidelines.

  Final system configuration

For new or expansion systems, need to provide for adequate space, power, AC, and security.

For a replacement system, determine if new system can swap in to the existing system's place. If not, is an upgrade required, or is there a need to provide additional space, power, AC, and security.

  Plan for expansion

Is expansion anticipated in the near future? If yes, refer to Physical Specifications for Site Planning for the anticipated system size.

Future systems generally require more space (ft 2/cabinet) than the current one.
  Servicing clearances

What are the front and rear clearances?

Refer to 42-U Cabinet Footprint and Clearances .

  Floor loading

What is the floor tile capacity?

What is the weight limit?

Is the floor loading adequate for the system?

Refer to Weight and Floor Loading.

  Unloading, uncrating, and entry route considerations

Is dock/delivery access adequate?

Is a liftgate truck or raised dock required to unload the system?

Is there an area large enough to uncrate the systems near the delivery dock?

Is there open access to the system floor (doors/ramps/elevators/appropriate floor covering)?

Is the access path to the system floor unobstructed, large enough, and strong enough (floor loading) to accommodate system cabinets?
No ramp steeper than 10°.

Will a pallet jack be available to move the crates?

Are there arrangements for crate disposal or return?
Usually, the carrier will take the crates and packing.

Refer to Delivery and Installation.

  Tile cutouts for cables

Does the customer have adequate tiles with appropriate cutouts?

Are tile cutouts large enough to accommodate cables?

Are cutout edges protected to prevent cable damage?
Cutout size must be minimal, and brush sealed tile cutouts are strongly recommended to prevent cold air from coming through.
  Cooling requirements in BTU/hr

Refer to Site Environmental Planning for measurements.

  Floor plan: Environmental

Refer to Site Environmental Planning.

  Floor plan: Power

Does the customer have multiple power feeds? The system requires multiple power feeds for redundancy.

Does the customer have site UPS units or street power?

Does the floor plan show electrical outlets?

Processing/storage cabinet: Will AC feeder boxes be connected to different power sources?

InfiniBand switch cabinet: Will the orange and blue AC boxes be connected to different power sources?

Will the power sources be connected to different PDU panels?

Does the floor plan show how dual power is connected to each cabinet?

Refer to Site Wiring Options for Dual AC.

  Floor plan: Cabling

Does the floor plan show cabling scheme and cable routing?

Refer to Cables and the Cabling appendix in the Hardware Installation Guide for your system.

Cable lengths need to be calculated before actual cabling.
  Cabling considerations

What is the customer’s cabling scheme?

Does the customer use cable trays? If yes, can we use the same trays? Teradata does not provide cable trays.

Do we know where we are laying cables?

Do we need to avoid certain areas or other cables?

Is the sub-floor area clean and free from obstructions? Inspect under raised floor; if necessary, have customer clean before installation.

Are we providing adequate cable lengths?

Refer to Cables and the Cabling appendix in the Hardware Installation Guide for your system.

  Host Channel Adapter (HCA) connectivity

Does the customer require a mainframe connection?

The customer must be told where to connect to the Teradata system, cable lengths, and how many connections. The customer is required to purchase cables. Refer to Network Cables and Hardware.

Determine/provide host channel connection information (CUAs), if applicable. The customer will need to make sure they plan to define the IOGEN and MVS devices.

  LAN connectivity
For new systems, unique IP ranges must be allocated for server management and BYNET IP address ranges:
  • Use the IP Address Configuration tool in Server Management 11.01 and later to verify that the addresses assigned within the allocated ranges in the system are unique.
  • Also verify that the addresses assigned within the allocated ranges in the system are not allocated elsewhere on the customer network.

Is the Customer LAN (CLAN) prepared for connectivity to Teradata Appliance for Hadoop 5 systems?

Network connectivity for Teradata Appliance for Hadoop 5 platforms is covered in the following guides:

  • CDH 5.4 or higher: Cloudera Distribution for Hadoop for Teradata Administrator Guide, B035-6049.
  • HDP 2.3 or higher: Hortonworks Data Platform for Teradata Administrator Guide, B035-6035.
  • In addition, log in to https://access.teradata.com and search for KAP314E352. This knowledge article provides networking recommendations for Teradata Appliance for Hadoop 5 systems.

Is a broadband connection in and out of the building available for Teradata’s use? Determine/provide customer LAN IP addresses, subnet mask, and aliases to be used at installation. Include router information. This information is also needed for the private LAN for the BAR solution, if applicable.

  Public IP address access to nodes Obtain public IP addresses for the following nodes and for the following uses:
  • Public IP address for the queen node to enable Aster client tools and client applications to connect and run queries
  • Public IP address for the loader node to stream data to the loader and to enable tools access
  • (If this installation includes an expansion cabinet) One public IP address for one node in the expansion cabinet to enable debugging and, if needed, installation of a backup queen
  Spare parts location/space

On-site spare parts are optional. Consult with the TSC (Teradata Sales Consultant).

Are additional site spares ordered?

Teradata provides the spare parts storage cabinet. Does the customer have any issue with Teradata providing this cabinet?

  Customer replacement of disk array storage drives, disk array power supplies, and node power supplies
Will the customer replace failed storage drives, disk array power supplies, or node power supplies? If yes, the CS installation team must train the customer on how to replace the failed components. Use the appropriate Customer Guide for Hardware Replacement as a reference. Items that must be covered:
  • Identification of system components (for example, cabinets, chassis, drive trays, disk drives, LEDs)
  • Overview of SMWeb, up to the component replacement procedure starting point
  • Practice run of the end-to-end replacement procedure
  • Reinforcement of the cautions and warnings for replacing failed components (detailed in the Customer Guide for Hardware Replacement document.
  Customer replacement of node storage drives and node power supplies
Will the customer replace failed node storage drives or node power supplies? If yes, the CS installation team must train the customer on how to replace the failed components. Use the appropriate Customer Guide for Hardware Replacement as a reference. Items that must be covered:
  • Identification of system components (for example, cabinets, chassis, disk drives, LEDs)
  • Overview of SMWeb, up to the component replacement procedure starting point
  • Practice run of the end-to-end replacement procedure
  • Reinforcement of the cautions and warnings for replacing failed components (detailed in the Customer Guide for Hardware Replacement document).