test

Sun Open Telecommunications Platform 1.1 Installation and Administration Guide

Preparing the OTP System Management Service to Provision the Solaris OS

This section provides the procedures for preparing the OTP system management service to provision the Solaris 10 Update 2 OS to a new standalone OTP host or to clustered OTP hosts.

Before you can use an existing OTP system to install the Open Telecommunications Platform to one or more OTP hosts, you must first perform the following tasks:

ProcedureTo Create the OS Image

  1. Log in as root to the OTP master server.

  2. Type /opt/sun/n1gc/bin/n1sh to open the OTP command shell. For example:


    # /opt/sun/n1gc/bin/n1sh
N1-ok>

  3. Create the Solaris 10 Update 2 OS image.

    In the OTP command shell, type create os os name file path to iso image where os name is the name of the image to create, and path to iso image is the path to the Solaris 10 Update 2 ISO image you created and NFS-mounted in To Download and Uncompress the OTP and Solaris OS Installation Zip Files.

    For example, if:

    • The name of the OS image to be created is to be sol10u2

    • The name of the server on which you created the ISO image is otpsource

    • The ISO image sol10u2-ga-sp-dvd.iso was created in the NFS-mounted directory /otp-download

    you would then type:


    N1-ok> create os sol10u2 file /net/otpsource/otp-download/sol10u2-ga-sp-dvd.iso
    Note –

    A job is submitted to create the OS image, and a job ID is displayed. The create os command can take up to 60 minutes to complete.

    To check for job completion, type show job job ID. When the job has completed, type show os to list the OS images.

Next Steps

Create the XML discovery file as described in the next section.

ProcedureProvisioning Bare Metal Systems Using Manual Discovery

To discover, manage, and provision an OS to a bare metal (no operating system installed) OTP host or hosts, you must create an XML discovery file that lists the host name, model number, and MAC address for each new OTP host.

  1. Log in as root to the OTP master server.

  2. Create the XML discovery file.

    For example, vi /tmp/discovery-mac-addresses.

  3. Add the system name, model number, Ethernet port address, and MAC address for each host to be discovered.

    The file format is:

    <!xml version='1.0' encoding='utf-8'?>
<servers>
    <server name="otpclient1" model="model name">
        <ethernetPort name="GB_0" mac="mac address"/>
    </server>
    <server name="otpclient2" model="model name">
        <ethernetPort name="GB_0" mac="mac address"/>
    </server>
</servers>

    Where otpclient1 is the name to be assigned to the host, model name is the model name listed in the following table, and mac address is the MAC address of the host.

    Host Type 

    Model Type for Bare Metal Discovery 

    Sun Netra 240 

    NETRA-240 

    Sun Netra 440 

    NETRA-250 

    Sun Fire V240 

    SF-V240 

    Sun Fire V440 

    SF-V440 

    Sun Fire V890 

    SF-V890 

    Sun Fire T2000 

    SF-T2000 

    For example:

    <!xml version='1.0' encoding='utf-8'?>
<servers>
    <server name="otpclient1" model="NETRA-240">
        <ethernetPort name="GB_0" mac="0:3:ba:19:c5:b"/>
    </server>
    <server name="otpclient2" model="SF-V20">
        <ethernetPort name="GB_0" mac="0:7:3c:12:b6:a"/>
    </server>
    <server name="otpclient3" model="SF-T2000">
        <ethernetPort name="GB_0" mac="0:14:4f:25:5e:78"/>
    </server></servers>

  4. Save and close the file.

Next Steps

ProcedureTo Create the DHCP Relay for Deploying to New OTP Hosts On Different Subnets

If you are going to deploy the Solaris 10 Update 2 to new OTP hosts on a different subnet using the OTP system management service, you must set up a DHCP relay on each subnet as described in this procedure before you can discover and subsequently deploy the OS to the hosts.

The examples in the following procedure assume:

  1. Log in as root to a Solaris OS SPARC server on the 10.1.30 subnet.

    The server must not be a standalone OTP host or a clustered OTP host.

  2. Type the ps -ef | grep dhcp to verify that the DHCP service has started.


    # ps -ef | grep dhcp
oot 24992     1   0 18:20:53 ?           0:00 /usr/lib/inet/in.dhcpd

  3. Type dhcpconfig -R production OTP hostIP address,otpclient1 IP address ..., otpclientn IP address.

    For example:


    # dhcpconfig -R 10.1.15.1,10.1.30.5, 10.1.30.6,10.1.30.7,10.1.30.8,\
10.1.30.9,10.1.30.10,10.1.30.11,10.1.30.12

  4. Log in as root to the OTP master server.

  5. Type /opt/sun/n1gc/bin/n1sh to open the OTP command shell.


    # /opt/sun/n1gc/bin/n1sh
N1-OK>

  6. Set up the OTP DHCP service.

    In the OTP command shell, type create dhcpconfig DHCP configuration name network IP address of base network netmask netmask value defaultgw gateway IP address domain domain name where:

    • DHCP configuration name is the name you assign to the OTP DHCP configuration

    • IP address of base network is the base address of the target subnet

    • netmask value is the netmask value of the target subnet

    • gateway IP address is the IP address of the target subnet gateway

    • domain name is your corporate domain name

    For example:


    N1-ok> create dhcpconfig test network 10.11.55.0 netmask 255.255.255.0 
defaultgw 10.11.55.1 domain mycompany.com
    Note –

    The above example was split into two lines to fit on the page. When typing the create dhcpconfig command, type the full command as a single line.

Next Steps

Prepare and deploy the OS as described in the next section.