5 Preface The Sun Open Telecommunications Platform Release Notes contain information and problem details that are specific to the Open Telecommunications Platform 1.1 software. Who Should UseThis Book This guide is intended for system administrators who are responsible for installing the Open Telecommunications Platform software and hardware, and for personnel who use the Open Telecommunications Platform product. Product Documentation This guide is part of a two-volume implementation reference set. Read the release notes and the installation guide before installing the Open Telecommunications Platform. Sun Open Telecommunications Platform 1.1 Release Notes Sun Open Telecommunications Platform 1.1 Installation and Administration Guide Related Documentation Solaris 10 1/06 Release and Installation Documentation (http://docs.sun.com/app/docs/coll/1236) Sun Cluster 3.1 Update 4 Software Collection for Solaris OS, SPARC Platform Edition (http://docs.sun.com/app/docs/coll/1124.4) Sun N1 System Manager (http://docs.sun.com/app/docs/coll/1283.6) Sun N1 Service Provisioning System (http://docs.sun.com/app/docs/coll/1119.6) Sun N1 Service Provisioning System User s Guide for OS Provisioning Plug-In 3.1 5

6 Preface RelatedThird-PartyWeb Site References Third-party URLs are referenced in this document and provide additional, related information. Note Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused or alleged to be caused by or in connection with use of or reliance on any such content, goods, or services that are available on or through such sites or resources. Accessing Sun Resources Online The docs.sun.com web site enables you to access Sun technical documentation online. You can browse the docs.sun.com archive or search for a specific book title or subject. Books are available as online files in PDF and HTML formats. Both formats are readable by assistive technologies for users with disabilities. To access the following Sun resources, go to Downloads of Sun products Services and solutions Support (including patches and updates) Training Research Communities (for example, Sun Developer Network) Accessibility Features for PeopleWith Disabilities To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. For information on Sun's commitment to accessibility, visit (http://sun.com/access). 6 Sun OpenTelecommunications Platform 1.1 Release Notes May 2007

7 Preface Documentation, Support, andtraining The Sun web site provides information about the following additional resources: Documentation (http://www.sun.com/documentation/) Support (http://www.sun.com/support/) Training (http://www.sun.com/training/) Typographic Conventions The following table describes the typographic conventions that are used in this book. TABLE P 1 Typographic Conventions Typeface Meaning Example AaBbCc123 AaBbCc123 The names of commands, files, and directories, and onscreen computer output What you type, contrasted with onscreen computer output Edit your.login file. Use ls -a to list all files. machine_name% you have mail. machine_name% su Password: aabbcc123 Placeholder: replace with a real name or value The command to remove a file is rm filename. AaBbCc123 Book titles, new terms, and terms to be emphasized Read Chapter 6 in the User's Guide. A cache is a copy that is stored locally. Do not save the file. Note: Some emphasized items appear bold online. Shell Prompts in Command Examples The following table shows the default UNIX system prompt and superuser prompt for the C shell, Bourne shell, and Korn shell. 7

8 Preface TABLE P 2 Shell Prompts Shell C shell C shell for superuser Prompt machine_name% machine_name# Bourne shell and Korn shell $ Bourne shell and Korn shell for superuser # Sun Welcomes Your Comments Sun is interested in improving its documentation and welcomes your comments and suggestions. To share your comments, go to and click Send Comments. In the online form, provide the full document title and part number. The part number is located on the book's title page and in the document's URL. For example, the name of this book is Sun Open Telecommunications Platform Release Notes, and the part number of this book is Sun OpenTelecommunications Platform 1.1 Release Notes May 2007

9 1C HAPTER 1 What's New in Sun Open Telecommunications Platform 1.1 The Open Telecommunications Platform 1.1 Media Kit containing the product and documents is available on DVD, which can be shipped to you for a small fee. The Open Telecommunications Platform Media Kit part number is OTP-B-Media. For Open Telecommunications Platform download and installation media preparation procedures, see Downloading and Uncompressing the OTP and Solaris OS Software in Sun Open Telecommunications Platform 1.1 Installation and Administration Guide. Supported Features This product supports the following features: Installation and configuration of the integrated product High availability framework Application provisioning service Operating system provisioning System management service System monitoring service For a list of the specific combinations of the latest supported hardware, software, and firmware, see the Qualification Hardware Matrix (QHM) at Sun Open Telecommunications Platform components are supported only on these platforms for network equipment provider (NEP) application development and deployment. 9

10 10

11 2 CHAPTER 2 Release Notes This chapter describes the Open Telecommunications Platform (OTP) issues that are known to be problems. The following topics are discussed: Open Telecommunications Platform 1.1 Limitations on page 11 Installation and Configuration Issues on page 12 Integration Issues on page 15 OpenTelecommunications Platform 1.1 Limitations The following are known limitations of Open Telecommunications Platform 1.1: OTP software uninstall is not supported in this release. Checkpoint support is not provided, that is, you cannot restart from where installation failed. If the installation fails and you need to reinstall, the entire installation process must be repeated. Installation of OTP on hardware platforms and operating systems not listed in section OTP System Hardware and Firmware Requirements in Sun Open Telecommunications Platform 1.1 Installation and Administration Guide is not supported. OTP supports only IPv4. IPv6 is not supported. OTP supports NFS version NFS v3. NFS v4 is not supported. OTP supports only Solaris DHCP. ISC DHCP is not supported. 11

12 Installation and Configuration Issues Installation and Configuration Issues This section describes known Open Telecommunications Platform installation and configuration issues. Deletion of the OTP Plug-in Requires the Deletion of All Hosts ( ) Before you can delete the OTP plug-in from an external OTP installation server or a production OTP host, you must first delete all hosts for which you ran plans. 1. Log in to the server from which you ran the Plans to add additional OTP hosts. 2. Delete all of the target hosts only for each host for which you ran Plans from the OTP plug-in. 3. Delete the OTP plug-in. Resource Groupotp_system_group and Resource N1SPSMS-HA Fails Under Heavy System Load ( ) During load test on memory, the resource group otp_system_group fails with the error message Error--stop failed, and the resource N1SPSMS-HA fails with the error message Stop failed Faulted. Workaround: 1. Log in as root on the clustered OTP host on which the OTP system management service is installed and running. 2. Restart the remote agent by typing /etc/init.d/n1spsagent restart. If the remote agent is not restarted, then the service provisioning service on the first OTP host will not work properly. 3. Type /usr/cluster/bin/scrgadm -c -g otp-system-rg -y RG_system=false to set the system property for the otp-system-rg resource group to false. 4. Type /usr/cluster/bin/scswitch -F -g otp-system-rg to take the remote group offline. 5. Type the following commands in the sequence shown to disable cluster resources. a. /usr/cluster/bin/scswitch -n -j otp-spsms-rs b. /usr/cluster/bin/scswitch -n -j otp-spsra-rs c. /usr/cluster/bin/scswitch -n -j otp-sps-hastorage-plus d. /usr/cluster/bin/scswitch -n -j otp-lhn 12 Sun OpenTelecommunications Platform 1.1 Release Notes May 2007

13 Installation and Configuration Issues 6. Type /usr/cluster/bin/scswitch -u -g otp-system-rg to put the remote group into the unmanaged state. 7. Type /usr/cluster/bin/scrgadm -c -j otp-spsra-rs -x Stop_signal="15" to change the Stop_signal property of the remote agent resource to Type /usr/cluster/bin/scrgadm -c -j otp-spsms-rs -x Stop_signal="15" to change the Stop_signal property of the management service resource to Type /usr/cluster/bin/scswitch -o -g otp-system-rg to put the remote group into the managed state. 10. Type /usr/cluster/bin/scswitch -Z -g otp-system-rg to bring the remote group back online. 11. Type /usr/cluster/bin/scrgadm -c -g otp-system-rg -y RG_system=true to set the system property for the otp-system-rg resource group to true. OTP Does Not Validate All User Input During Installation ( ) When you enter invalid inputs during OTP installation, installation might succeed. However, OTP services might not be properly configured. Workaround: Make certain that you provide valid values when entering OTP plan information. The Sun Open Telecommunications Platform 1.1 Installation and Administration Guide provides OTP Plan worksheets for you to record installation information for each host prior to the installation process, which you should then use during installation to ensure the data you provide is correct. Print a worksheet for each host and then record and verify the information for each host prior to installing OTP. Installation of OTP Fails If IPMP Is Not Correctly Configured ( ) OTP installation fails at the OTP System Management and Provisioning Service step. There are two types of IPMP configurations: Link-based failure detection and Probe-based failure detection. OTP supports only probe-based failure detection. The installation fails if IPMP is configured in the link-based failure detection mode. Workaround: Before installing OTP, make sure that IPMP is configured in the probe-based failure detection mode. If you want to configure IPMP in the link-based failure detection mode, you can do it after OTP installation. Chapter 2 Release Notes 13

14 Installation and Configuration Issues OTP Installation From External Server Through GUI Displays an Error Message ( ) Service Management Facility (SMF) is registered with the old calendar service rpc After applying the patch, SMF gets registered with the new calendar service. This registration happens only after the first reboot. Due to this registration, when you install OTP from external server through GUI, you might see an error message as follows: Failed to update state of instance svc:/network/rpc _1/rpc_tcp:default in repository: entity not found This error message appears only once during the first reboot. Warning Messages on Console During OSP Installation ( ) During OSP installation, you might see some warning messages on the console. These messages do not affect the functionality of the OSP plug-in and can be ignored. Solaris: Configuring JumpStart boot for target node Starting SMF services for JumpStart Solaris: Configure DHCP build Adding install client WARNING: JS_DHCP_VENDOR is not defined in jumpstart.conf WARNING: This value a space separated list of the uname -i WARNING: outputs of the machines you want to install. WARNING: Supporting SUNW.i86pc by default. OS Installation Fails After the Initial Reboot ( ) Assume that you have done a initial setup as follows: Installed the master server of OTP Application Provisioning Service Loaded the OSP plug-in of OTP Application Provisioning Service Prepared the OSP server and JET Boot/Install server If you reboot the host after this initial setup, OSP and Jet directories become unavailable. Hence, OS installation fails after the initial reboot. Workaround: Run the following command after the initial reboot. # /usr/sbin/svcadm enable network/nfs/server 14 Sun OpenTelecommunications Platform 1.1 Release Notes May 2007

15 Integration Issues Integration Issues This section describes known Open Telecommunications Platform integration issues. OSP Deployment Plan Completes Before OS Is Installed ( ) When the OSP plan is run to install the OS, the plan completes before the OS is installed. Hence, the OS installation will still be in progress after the OSP plan completes. Workaround: Monitor the progress of OS installation using the following steps. 1. In the Common Tasks section of the GUI, select OS Provisioning. 2. On the OS Provisioning Common Tasks page, click Status in the OS Provisioning Administration Tasks section. 3. On the Plans Details page, click Run. 4. On the Plan Details Run page, select the target host on which you provisioned the OS. 5. Click Run Plan (includes preflight). 6. Follow the Details links to view the status. OSP Plug-in Cannot Import Two OS Images Simultaneously ( ) The OSP plug-in does not import two OS images simultaneously. If you try to import two OS images simultaneously, the following message appears: Connect and lock hosts Workaround: Wait for the first OS image to be imported before importing the second OS image. OSP Plug-in Does NotTake a Shared File System as OS Image Path ( ) The OSP plug-in is not highly available. Hence, OSP plans fail if a shared file system is given as OS image path. Due to this issue, you cannot place OS images on the shared disks. Error Message: Chapter 2 Release Notes 15

16 Integration Issues osp_create_solaris_image.sh: targetnode/export/home/solaris10u2 /var/otp/osp_image/solaris10_u2_sparc 10 Solaris10_u2_sparc /opt/sunwjet Created loopback device /dev/lofi/1 for target node/export/home/solaris10u2/sol-10-u2-ga-sparc-dvd.iso Failure in mounting /var/otp/osp_image/3047/slices/s0 Filesystem does not appear to be mounted. removing device /dev/lofi/1 removing directory /var/otp/osp_image/3047 osp_create_solaris_image.sh: ERROR -- copy_solaris_media failed cfgadm Does Not Warn if Metaset Is Used ( ) The cfgadm command provides configuration administration operations on dynamically reconfigurable hardware resources. The cfgadm command on the OTP cluster node does not warn if the metaset is being used and unconfigures the controller, which results in unstable OTP Services. Hosts Cannot Be Deleted From the Hosts List of External Server ( ) When you try to delete hosts from the hosts list of external server through GUI, you might get the following error message: Unable to delete the host At least one delete operation failed Workaround: Restart the master server on the specific node and remove the host. OSP ALOM Create Plan Does NotValidate the Password ( ) OSP ALOM create plan does not verify whether the admin password entered is correct or not. The plan succeeds with any password. OSP Uses the IP Address of Installation Server as the Default Router ( ) If you do not explicitly specify the IP address of the default router in the Provision OS profile, OSP will use the IP address of installation server to create a /etc/defaultrouter file. 16 Sun OpenTelecommunications Platform 1.1 Release Notes May 2007

17 Integration Issues Workaround: Specify the IP address of the default router in the Provision OS Profile or modify the /etc/defaultrouter file to make it point to the correct router information and reboot the system. EIS compliance requires the /etc/defaultrouter file to be present. Messages On ConsoleWhen Host Reboots ( ) Runtime error messages are displayed on the console when the host reboots. Error snippet: libpkcs11: Unable to contact kcfd: Bad file number libpkcs11: /usr/lib/security/pkcs11_softtoken.so unexpected failure in ELF signature verification. System may have been tampered with. Cannot continue parsing /etc/crypto/pkcs11.conf com.sun.hss.domain.persistentmbeanserver.loadmbeans : Error loading MBeans from persistent store com.sun.cacao.element.elementsupport.setadministrativestate : caught throwable when starting : RuntimeException thrown in postregister method These messages are completely harmless and can be safely ignored. Chapter 2 Release Notes 17

Solaris 9 Installation Roadmap This document is a guide to the DVD, CDs and documents involved in installing the Solaris 9 software. Unless otherwise specified, this document refers to both DVDs and CDs

RAID Controller PCI Card for the Sun Fire V60x and V65x Servers Release Notes CAUTION: Read this document before installing the RAID Controller PCI Card. Failure to use the correct firmware version with

Important Note on New Product Names As part of Sun s new developer product strategy, we have changed the names of our development tools from Sun WorkShop to Forte Developer products. The products, as you