Sun Open Telecommunications Platform 1.1 Installation and Administration Guide

Chapter 2 Sun Open Telecommunications Platform Hardware and Software Requirements

This chapter provides the Open Telecommunications Platform hardware and software requirements, and the Open Telecommunications Platform plan worksheets that can assist you during installation. The information in this section will help you determine what operating system, hardware, and storage resources must be allocated or acquired to implement the Open Telecommunications Platform system.

This chapter discusses the following topics:

OTP System Hardware and Firmware Requirements

The following table lists the hardware, OS, patch, and firmware requirements for OTP system servers, and for the optional external OTP installation server.

Table 2–1 OTP System Server Hardware, Operating System, Patch, and Firmware Requirements


Type	Management Port	OS	Patch	Firmware
Netra^TM 240	ALOM	Solaris 10 Update 2, 64 bit	121683-04	OBP 4.22.23, POST 4.22.23, OBDIAG 4.22.23
Netra 440	ALOM	Solaris 10 Update 2, 64 bit	121685-02	OBP 4.22.19, POST 4.22.19, OBDIAG 4.22.19
Sun Fire^TM V215	ALOM	Solaris 10 Update 2, 64 bit	121692-02	OBP 4.22.22, POST 4.22.22, OBDIAG 4.22.22
Sun FireV240	ALOM	Solaris 10 Update 2, 64 bit	121683-04	OBP 4.22.23, POST 4.22.23, OBDIAG 4.22.23
Sun Fire V245	ALOM	Solaris 10 Update 2, 64 bit	121692-02	OBP 4.22.22, POST 4.22.22, OBDIAG 4.22.22
Sun Fire V440	ALOM	Solaris 10 Update 2, 64 bit	121685-02	OBP 4.22.19, POST 4.22.19, OBDIAG 4.22.19
Sun Fire V445	ALOM	Solaris 10 Update 2, 64 bit	121690-03, 123485-01	OBP 4.22.24, POST 4.22.24, OBDIAG 4.22.24, 1.0.39
Sun Fire V490	RSC	Solaris 10 Update 2, 64 bit
Sun Fire V890	RSC/ALOM	Solaris 10 Update 2, 64 bit	121688-01	OBP 4.22.19, POST 4.22.19, OBDIAG 4.22.19
Sun Fire T2000	ALOM	Solaris 10 Update 2, 64 bit	124750-03	Sun System Firmware 6.3.2

Note –

The OTP Application Hosting Environment (AHE) components are supported only on these platforms for Network Equipment Providers' (NEP) application development or deployment, or for both.
The Open Telecommunications Platform supports one to eight-host clusters. At least one shared disk is mandatory for installing the Open Telecommunications Platform on a two to eight-host cluster.

The following table lists the minimum OTP system server requirements. Ensure that the external OTP installation server meets the following partitioning requirements as well.

Table 2–2 OTP System Server RAM, Disk, and Connectivity Requirements


Category	Requirement
Minimum physical memory	4 GB
Minimum disk space	External OTP installation server: 32 Gbytes OTP host: 72 GBytes
Ethernet connectivity for management interfaces	10/100 connection
Ethernet connectivity for provisioning and data interfaces	10/100/1000 connection

The following table lists the supported storage hardware and NIC devices by server type.

Table 2–3 OTP System Supported Storage Hardware and NIC Devices


Server	Storage	NIC
Netra 240 and 440	FC 3510 FC 3511 SCSI 3120 JBOD SCSI 3310 JBOD SCSI 3320 JBOD SCSI 3310 RAID SCSI 3320 RAID	On-board GE X4445A QGE X4150A-2 2 GE X4150A GE X4422A-2 combo
Sun Fire V215	FC 3310 FC 3320 FC 3510 FC 6130 SCSI 3320	On-board GE X4445A QGE
Sun Fire V245	FC 3510 FC 3511 FC 6130 SCSI 3120 SCSI 3310 SCSI 3320	On-board GE X4445A QGE
Sun Fire V240, V440, and V890	FC 3510 FC 3511 FC 6130 SCSI 3310 JBOD SCSI 3120 JBOD SCSI 3320 JBOD SCSI 3310 RAID SCSI 3320 RAID	On-board GE X4445A QGE X4150A-2 GE X4150A GE X4422A-2 combo
Sun Fire V445	FC 3510 FC 3511 SCSI 3320	On-board GE X4445A QGE
Sun Fire V490	FC 6130 FC 3511 FC 3510 SCSI 3320 SCSI 3120	On board GE X4422A Combo
Sun Fire T2000	FC 3510 FC 3511 FC 6130 SCSI 3120 JBOD SCSI 3310 JBOD SCSI 3310 RAID	On-board GE (e1000g driver) X4150A-2 2 GE X4150A GE

The following table lists the storage device firmware requirements.

Table 2–4 OTP System Storage Device Firmware Requirements


Type	Patch	Requirement
FC StorEdge^TM 3510	RAID 113723-15, JBOD 113662-01	Version 2.3 of the sccli CLI utility must be installed first.
FC StorEdge 3511	113724-09	Version 2.3 of the sccli CLI utility must be installed first.
SCSI StorEdge 3120	113728-02 Array Controller Firmware	Version 2.3 of the sccli CLI utility must be installed first.
SCSI StorEdge 3310	113722-15	Version 2.3 of the sccli CLI utility must be installed first.
SCSI StorEdge 3320	113730-01	Version 2.3 of the sccli CLI utility must be installed first.
FC StorEdge 6130	118185-15 6130 services Release, 117856-19 6130 Baseline Firmware Release	StorEDGE 6130 Array Firmware Upgrader patch 118185-15 must be installed first.

Note –

The sccli CLI utility is included in the SUNWsscs package which can be downloaded from the Sun Download Center. The sccli CLI utility can also be installed from the optional Sun StorEdge Professional Storage Manager CD.

OTP System Server Considerations

Hard drive capacity and the number of OTP hosts to be managed are the primary considerations for your OTP system.

Hard drive capacity is affected by three factors: the number of OS distributions that are to be provisioned, the management log files generated by Open Telecommunications Platform components, and the size of the applications to be provisioned.
- If you are using the OTP system management service to provision OS distributions, the OS distributions are stored in the /var/js file hierarchy on the first OTP host
- If you are using the OTP application provisioning service to provision OS distributions, the OS distributions are stored in the /var/otp file hierarchy on the first OTP host
System processing is affected by three major factors: The number of additional OTP hosts being managed, the types of monitoring being performed on the additional OTP hosts, and the number of jobs running on the first OTP host.

Open Telecommunications Platform Plan Worksheets

This section provides a description of the Open Telecommunications Platform settings, and provides worksheets to assist you with recording the settings you need to provide when installing the Open Telecommunications Platform on one or more OTP hosts. The settings comprise an installation and configuration plan, which the Open Telecommunications Platform installation process applies to automate the setup and configuration of your OTP hosts.

The following topics are discussed:

OTP System Plan Settings Descriptions

The following list describes each of the OTP system plan settings that are used by the Open Telecommunications Platform graphical user interface installation and configuration process.

Media Directory

The fully-qualified path name to the Open Telecommunications Platform installation source directory. For example:
- /cdrom/otp_11_dvd/otp1.1 for physical media
- The fully qualified path name of NFS-mounted OTP installation directory on the external OTP installation server, for example: /net/otpsource.mycompany.com/otp1.1.
Cluster Name

The name of the clustered OTP system that is assigned to the cluster during the Open Telecommunications Platform installation and configuration process.
hn Enable Auto Configuration of IPMP

Required:
- GUI default value: no, checkbox does not contain the √ symbol
- CLI default value: yes
Valid values: yes, no, checkbox contains a symbol, checkbox does not contain a symbol

Note –
You should configure all physical interfaces of a multipathing group with a test IP address. Test addresses are required to detect failures.

For more information about IPMP, see System Administration Guide: IP Services

If you set Enable Auto Configuration of IPMP=yes, then you must also specify the following values:
- hn Secondary interface for failover
  
  The name of the network adapter failover (NAFO) network adapter to be added to an IP Network Multipathing group along with the primary network adapter. This interface is used as the failover interface if a fault is detected on the primary interface. Examples: cd1, bge1, hme1, eri1
- hn Secondary IP
  
  The IP address of the secondary interface secondary IP interface that is used for failover.
- hn Test Address for IPMP
  
  An unused IP address that is to be assigned as a routable, no-failover, and deprecated test IP address to the adapter. IP Network Multipathing uses test addresses to detect network path failures, switch port faults, and partial network equipment outages. For additional information on configuring test IP addresses, see System Administration Guide: IP Services
hn Sponsoring Node

The name of the first OTP host in a clustered OTP system. The first OTP host is the sponsoring note for additional OTP host n. Required when installing the Open Telecommunications Platform on a two or more host clustered OTP system.
hn Host Name

The name of the additional OTP host n in a two host or more cluster. Required when installing the Open Telecommunications Platform on a two or more host clustered OTP system.
hn Physical IP Adddress

The IP address of the additional OTP host n in a two host or more cluster. Required when installing the Open Telecommunications Platform on a two or more host clustered OTP system.
hn Private Interface 1

The first physical interface on additional OTP host n, for example bge0 or ce0.
hn Private Interface 2

The second physical interface on additional OTP host n, for example bge1 or ce1.
hn Transport Type Interface 1

Required value is dlpi, do not change.

The transport type of the first private interconnect adapter on additional OTP host n
hn Transport Type Interface 2

Required value is dlpi, do not change.

The transport type of the second private interconnect adapter on additional OTP host n
hn Quorum Auto Configuration

Note –
Quorum automatic configuration applies only to two-host clusters.

Required, default value: yes, checkbox selected, and contains the √ symbol

Valid values: yes, no, checkbox contains a symbol, checkbox does not contain a symbol

Quorum autoconfiguration provides an option to enable or disable auto configuration of the quorum device in a two-host only clustered OTP system.

Note –
If this value is set to no, a manual administrative procedure is required to configure the quorum disk in a two-host clustered OTP system. The cluster must be manually reset from install mode to normal mode. For details on how to configure quorum disks, refer to the scconf command documentation in scconf(1M)
Logical Host

A unique host name assigned to the OTP high availability framework
Logical IP Address

An unused IP address on the same subnet as the first OTP host, assigned to the logical host
Install All Patches

Required, default value: yes, checkbox selected, and contains the √ symbol. All patches are to be installed.

Valid values: yes, no, checkbox contains a symbol, checkbox does not contain a symbol. Only mandatory patches are to be installed.

To install all Open Telecommunications Platform patches, specify yes.

To install mandatory patches only, specify no.
Management Interface

The name of the network interface used for OTP system management services. The name of the interface depends on the platform type. For example:

bge0, ce0, cd0, hme0, or eri0.
Manager Host Name

The name of the first OTP host in the clustered OTP system, for example, cluster01manager.
Manager Physical IP Address

The IP address of the first OTP host in the clustered OTP system.
Manager Node Authentication

Required value is sys, do not change.
Manager Private Interface 1

The first physical interface on the OTP host, for example bge0 or ce0.
Manager Private Interface 2

The second physical interface on the OTP host, for example bge1 or ce1.
Manager Transport Type Interface 1

Required value is dlpi, do not change.
Manager Transport Type Interface 2

Required value is dlpi, do not change.
Manager Autoconfig IPMP

Set managerAutoConfigureIPMP=no if you do not want to set up IPMP.

To set up IPMP, set managerAutoConfigureIPMP=yes, and add the following three lines:
- managerSecondaryInterface=Ethernet interface 2, for example bge1
- managerSecondaryIPMP=111.112.113.114 where 111.112.113.114 is the IP address of Ethernet interface 2.
- managerTestIPAddress=111.112.113.222 where 111.112.113.222 is the IP address used for IPMP configuration.
Node Authentication

Required value is sys, do not change.

This option establishes the authentication policies for hosts that are to be added to a clustered OTP system configuration.
Private Interface 1

The network adapter connected to private interconnect.
Private Interface 2

The network adapter connected to private interconnect.
Provisioning Interface

The name of the network interface used for operating system and applications provisioning. The name of the interface depends on the platform type. For example, bge0, ce0, cd0, hme0, or eri0.
Target Host Physical Name

The name to be assigned to the OTP host
Target Host Physical IP

The IP address to be assigned to the standalone OTP host.
Transport Type 1

Required value is dlpi, do not change.

The transport type of the private interconnect adapters.
Transport Type 2

Required value is dlpi, do not change.

The transport type of the private interconnect adapters.

Standalone OTP Host Plan Worksheet

The following table lists the plan settings that you need to provide during installation and configuration of the Open Telecommunications Platform on a standalone OTP host. Plan setting names used in the graphical user interface installation are listed in bold text.

Tip –

Print the following table and then fill out the required information to use while installing and configuring the Open Telecommunications Platform on the standalone OTP host.

Table 2–5 Standalone OTP Host System Settings Worksheet


Setting Name	Example	Setting Value
Media Directory (GUI) `mediaDirectory` (CLI)	`/cdrom/otp_11_dvd/otp1.1` `/net/external OTP installation server/otp1.1` `/otp1.1`	____________________________________
Target Host Physical Name (GUI) `targetHostPhysicalName` (CLI)	OTPstandalone OTPhost01	____________________________________
Target Host Physical IP (GUI) `targetHostPhysicalIP` (CLI)		____________________________________
Cluster Name (GUI) `clusterName` (CLI)	`standalone-cluster-name`	____________________________________
Enable Auto Configuration of IPMP (GUI) `autoConfigureIPMP` (CLI)		`yes` `no`
Secondary Interface for failover (GUI) `secondaryInterface` (CLI)	`cd1,` `bge1,` `hme1,` `eri1`	____________________________________
Secondary IP (GUI) `secondaryIP` (CLI)		____________________________________
Test Address for IPMP (GUI) `testIPAddress` (CLI)		____________________________________
Logical Host (GUI) `logicalHost` (CLI)	`host–01–logical`	____________________________________
Logical IP Address (GUI) `logicalIPAddress` (CLI)		____________________________________
Install All Patches (GUI) `allPatches` (CLI)		`yes` `no`
Management Interface (GUI) `managementInterface` (CLI)	`bge0`, `ce0`, `cd0`, `hme0`, `eri0`	____________________________________
Provisioning Interface (GUI) `provisioningInterface` (CLI)	`bge0`, `ce0`, `cd0`, `hme0`, `eri0`	____________________________________

Clustered OTP Host Plan Worksheet

The following table lists the plan settings that you need to provide for each host during installation and configuration of the Open Telecommunications Platform on a clustered OTP system. Plan setting names used in the graphical user interface installation are listed in bold text.

Tip –

Print a copy of the following table for each host and then fill out the required information to use when installing and configuring the Open Telecommunications Platform on a clustered OTP system.

Table 2–6 Clustered OTP System System Settings Worksheet


Setting Name	Example	Setting Value
Media Directory (GUI) `mediaDirectory` (CLI)	`/cdrom/otp_11_dvd/otp1.1` `/net/external OTP installation server/otp1.1`	____________________________________
Cluster Name (GUI) `clusterName` (CLI)	`otp-cluster-name`	____________________________________
Secondary Interface for failover (GUI) `secondaryInterface` (CLI)	`cd1,` `bge1,` `hme1,` `eri1`	____________________________________
Secondary IP (GUI) `secondaryIP` (CLI)		____________________________________
Test Address for IPMP (GUI) `testIPAddress` (CLI)		____________________________________
Install All Patches (GUI) `allPatches` (CLI)		`yes` `no`
Enable Auto Configuration of IPMP (GUI) `hn_autoConfigureIPMP` (CLI)		`yes` `no`
Sponsoring Node (GUI) `hn_sponsorNode` (CLI) This is the name that is to be assigned to the first OTP host for additional OTP host `n`.	OTPfirsthost h1_sponsorNode=OTPfirsthost … h`n`_sponsorNode=OTPfirsthost	____________________________________
Host Name (GUI) `hn_hostName` (CLI) This is the name that is to be assigned to additional OTP host `n`.	OTPhost1 h1_hostName=OTPhost1 … h`n`_hostName=OTPhost`n`	____________________________________
Physical IP Address (GUI) `hn_physicalIPAddress` (CLI)	`10.20.30.10` h1_physicalIPAddress=10.20.30.10 … h`n`_physicalIPAddress=10.20.30.11	____________________________________
Private Interface 1 `hn_privateInterface1` (CLI)	`bge0`, `ce0`, `cd0`, `hme0`, `eri0` h1_privateInterface1=bge0 … h`n`_privateInterface1=bge0	____________________________________
Private Interface 2 `hn_privateInterface2` (CLI)	`bge1`, `ce1`, `cd1`, `hme1`, `eri10` h1_privateInterface2=bge0 … h`n`_privateInterface2=bge0	____________________________________
Transport Type Interface 1 (GUI) `hn_transportTypeInterface1` (CLI)	dlpi	dlpi
Transport Type Interface 2 (GUI) `hn_transportTypeInterface2` (CLI)	dlpi	dlpi
Quorum Auto Configuration (GUI) `hn_quorumAutoConfiguration` (CLI)		Default:`yes` `no` Note – Quorum automatic configuration applies only to two-host clustered OTP systems. If you disable quorum automatic configuration on a two-host cluster by choosing `no`, you must manually configure the quorum for the two-host cluster and reset the cluster configuration as described in Installing the Open Telecommunications Platform on a Clustered OTP System.
Logical Host (GUI) `logicalHost` (CLI)	`host–01–logical`	____________________________________
Logical IP Address (GUI) `logicalIPAddress` (CLI)		____________________________________
Manager Host Name (GUI) `managerHostName` (CLI)	`cluster01manager`	____________________________________
Manager Physical IP Address (GUI) `managerPhysicalIPAddress` (CLI)		____________________________________
Manager Node Authentication (GUI) `managerNodeAuthentication` (CLI)	sys	sys
Manager Private Interface 1 (GUI) `managerPrivateInterface1` (CLI)	`bge0`, `ce0`, `cd0`, `hme0`, `eri0`	____________________________________
Manager Private Interface 2 (GUI) `managerPrivateInterface2` (CLI)	`bge1`, `ce1`, `cd1`, `hme1`, `eri1`	____________________________________
Manager Transport Type Interface 1 (GUI) `managerTransportTypeInterface1` (CLI)	dlpi	dlpi
Manager Transport Type Interface 2 (GUI) `managerTransportTypeInterface2` (CLI)	dlpi	dlpi
Manager Management Interface (GUI) `managerManagementInterface` (CLI)	`bge0`, `ce0`, `cd0`, `hme0`, `eri0`	____________________________________
Manager Provisioning Interface (GUI) `managerProvisioningInterface` (CLI)	`bge0`, `ce0`, `cd0`, `hme0`, `eri0`	____________________________________
Number of Nodes (GUI) `noOfNodes` (CLI)		____________________________________