Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30




Download 17.11 Kb.
NameSoftware release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30
A typeDocumentation
manual-guide.com > manual > Documentation
SOFTWARE RELEASE DOCUMENT ---------------------------------------------------------------------------- Product Name Integrity XC System NonStop Clusters for SCO UnixWare Product Number T5649D10IPM30 Part Number 422340-001 Softdoc Date 16 April 1999 ---------------------------------------------------------------------------- Release Summary This release of NonStop Clusters� for SCO� UnixWare� is an update to the D10IPM20 release of the Tandem� single system image (SSI) UNIX� clustering technology. This release includes features such as: * Support for YEAR 2000 in NonStop Clusters for UnixWare. Product Table of Contents This document contains descriptions of the following product components. Comp T Number Product Component Comp T Number Product Component T5649D10IPM30 NonStop Clusters Superseded IPMs None Requisite IPMs This IPM requires previous installation of D10, D10IPM10, and D10IPM20. Required Hardware None Required Firmware Version TPN 131790 A03-03 of the ServerNet SAN Switch. Required Software T5649D10 NonStop Clusters for SCO UnixWare operating system. T5649D10IPM10 NonStop Clusters for SCO UnixWare operating system. T5649D10IPM20 NonStop Clusters for SCO UnixWare operating system. T5649D10IPM30 NonStop Clusters for SCO UnixWare operating system. SCO UnixWare 2.1.2 (supplied with the original factory shipment) Required Disk Space Minimum 2 GB Manuals The manuals associated with this product are defined in the following table. Part Number Manual Title 422296-001 NonStop Clusters for SCO UnixWare (jewel case document) Migration Considerations None Installation Considerations Refer to this softdoc for D10IPM30 installation instructions, and to the "Known Problems" section of this softdoc for installation considerations. General Notes 1. An on-line version of this softdoc will be updated as new information is available about the product. The current softdoc for this product is viewable on the World Wide Web and is accessed from a link on the softdoc index page: https://www.austx.tandem.com/softdocs/ These pages are password-protected. At the prompts, enter "Tandem" for the userID and "!ntegr1ty" for the password. The server is case-sensitive, so note the uppercase T in the userID and the exclamation point and number 1 in the password. Trademarks Compaq, ProLiant, the Compaq logo, Tandem, Integrity, NonStop, registered in the United States Patent and Trademark Office NonStop-UX, ServerNet, and ServerWare are trademarks of Compaq Computer Corporation. Oracle is a registered trademark, and Oracle 7 is a trademark of Oracle Corporation. SCO, The Santa Cruz Operation, UnixWare, and the SCO logo are trademarks or registered trademarks of Santa Cruz Operation Incorporated in the United States and/or other countries. INFORMIX is a registered trademark and ONLINE Dynamic Server is a trademark of Informix Software Incorporated. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. NFS is a registered trademark of Sun Microsystems, Inc. Veritas, VxFS, and VxVA are registered trademarks of Veritas Software Corporation. UniSoft is a registered trademark of UniSoft Corporation. All other brand and product names are trademarks or registered trademarks of their respective companies. Copyright Notice Copyright (c) 1998, 1999 Compaq Computer Corporation. All rights reserved. The computer program listings, specifications and documentation herein are the property of Compaq Computer Corporation or a third party supplier and shall not be reproduced, copied, disclosed, or used in whole or in part for any reason without the prior express written permission of Compaq Computer Corporation. ---------------------------------------------------------------------------- Product Component: NonStop Clusters - T5649D10IPM30 ---------------------------------------------------------------------------- Description This is the D10IPM30 release of the NonStop Clusters for SCO UnixWare operating system for Compaq ProLiant Intel based PCs of the single-system image, distributed operating system. Contents The following packages belong to this component: Package Version Package Description D10IPM30 D10IPM30 NonStop Clusters software D10I30doc D10IPM30 NonStop Clusters software release document Notes (for further Notes about NonStop Clusters, please refer to the softdocs for the following prerequisite releases: D10, D10IPM10, D10IPM20) 1. For installation instructions for D10IPM30, please refer to the NonStop Clusters for SCO UnixWare document (the document found in the jewel case). This document also has instructions on installing this softdoc from the D10IPM30 CD. 2. Enabling Syslogd In base UnixWare, the syslogd is NOT started at boot time by default. If you would like syslogd to be started in the cluster, as super-user, type the following from a shell prompt: ln /etc/init.d/syslogd /etc/rc2.d/S00syslogd This will start syslogd before other daemons when the system goes to run-level 2 at system boot. The /etc/init.d/syslogd script has been modified so that syslogd will be re-started by keepalive if a root failover occurs. 3. Enabling Load_leveld The Load leveling daemon is off by default. To start the load_leveld, the man pages currently suggests the following: /sbin/spawndaemon -o -r ka_load_leveld /usr/sbin/load_leveld -v -k However, this configuration should be changed to: /sbin/spawndaemon -o -r ka_load_leveld /usr/sbin/load_leveld -v -k -n The -n option disables migration, so the load balancing will get done via rexec's only. This is now recommended since not all processes can be migrated, and the effects of migrating a customer's application processes are undetermined. 4. Problems Migrating Processes using Sockets If a process that is using sockets is migrated between the time it has listened on a socket and the time it accepts connections, it will hang. It is suggested that applications that use sockets and are being used in a load leveled environment (see the load_leveld man page) be added to the load levelers exclusion list or that the load leveler be started as documented above. 5. Extraneous Floppy Boot Messages When the dependent node is booted off the floppy, the following errors may occur due to the fact that the dependent node's /stand/ has not been mounted yet. At this stage, the dependent node is not in a normal state, and these errors do not apply and may be ignored. /sbin/metreg: getksym error = 154 UX:dst_sync: ERROR: /stand/2/boot: No such file or directory 6. Ignorable Load_leveld warning The following message is a normal output message that gets displayed on the dependent node when the load_leveld is not running. Load_leveld is off by default. /usr/sbin/load_leveld: HALT: load-leveler is not running 7. Harmless token warning The following message is harmless, and may occasionally occur during a failover: WARNING: tok_giveback: GIVEBACK undo! 8. Ignorable lockd error Failover for NFS lockd is not supported, so the following message is generated when the EREMOTE error is returned, and can be ignored: talk_to_lockmgr: clnt_tli_kcreate: 66 9. Known CLMS race condition The following message is harmless and may also be ignored. The node that is coming-up missed its window in which to join the cluster. In a few seconds, the node will try to join the cluster again and should succeed WARNING: clms_master_nodeup_daemon: ics_nodeup() for new node 2 failed with error 11 10. Mount command will not show all mounted file systems Sometimes after newly installing D10IPM30, the only mounted file systems shown after executing the "mount" command is "/" (root) and all the dependent nodes. /stand/1 will not be shown as mounted. To correct this problem, reboot the whole cluster. This will correct the mnttab file and everything will be mounted correctly. The following known problem has a workaround: 1. cnet Adapter Check causes the whole cluster to hang (PTS 38666). Symptom: When installing Oracle, if the Oracle installation scripts are run on a node different from where the destination disk is mounted, or if the Oracle installation scripts are run on a node different where the Oracle distribution CD is mounted, the following error may occur: WARNING: cnet: unit 0: Adapter Check interrupt 100002! Interface 0 in slot 16 has failed. Attempting to restart. When this happens, the cluster may hang. Workaround: Ensure that the Oracle install program execution, the Oracle distribution CD, and the destination disk drive are all on the same node. For example, if you want to install Oracle on a disk which is mounted on node 2, mount the Oracle CD in the CD ROM drive on node 2, and run the Oracle install script on node 2 using the following command: onnode -p 2 ./orainst /c The node where a file system is mounted can change if it is part of a RAID system. To determine which node a file system is currently attached to, use the following command: where /my_file_system For performance reasons, it is a good idea for Oracle application programs and disk drives containing the database to be on the same node. However, there are no known problems if they are not. For a list of other known issues and workarounds for NonStop Clusters, please refer to the softdoc for the D10IPM20 release of NonStop Clusters. New Features The following new features are supported with the NonStop Clusters D10IPM30 release: * Support for Year 2000 in NonStop Clusters for UnixWare. Problems Corrected 1. Problem with data loss over Unix Domain Sockets under NSC for Unixware 2.1.2. (PTS 40342, TPR 990127 1609 16102, Severity 2) 2. The D10IPM30 release of NonStop Clusters includes SCO PTF3391a. For a description of corrected symptoms and fixes contained in SCO PTF3391a, please see the SCO Tech Article: What is SLS PTF3391A, the Year 2000 Supplement for SCO UnixWare 2.1.1 and 2.1.2? (http://www.sco.com/cgi-bin/ssl_reference?109998) This is a general explanation of what SCO PTF3391a addresses. What is contained in SCO PTF 3391a: 1. CMOS RAM byte 0x32 is defined to hold the century (as binary coded decimal). UNIX makes no use of that byte, and has not in the past maintained it. But a few machines have a BIOS which does make use of that byte. On such a machine, changing the year from 19YY to 20YY or back under UNIX, then running System Setup, DOS or Windows on reboot, can cause the system date to be wrongly reset. The UNIX Real Time Clock driver in this PTF maintains the CMOS century byte consistent with the year, to avoid such problems (as far as is possible under UNIX: some such problems may lie in the machines BIOS itself). 2. For compatibility with System Setup, DOS or Windows, UNIX maintains the Real Time Clock in local time, and so it must be adjusted when entering or leaving Daylight Savings Time. If you arbitrarily set the system date forward or backward (as you might when testing Year 2000 issues), into or out of Daylight Savings Time, then /stand/boot TZ_OFFSET may lose synch with the date, causing the hour to advance or retard each time UNIX is rebooted. The dst_sync program in this PTF keeps /stand/boot TZ_OFFSET and the kernels difference between UNIX system time and RTC in synch with the local time according to /etc/TIMEZONE TZ. It is run at startup and shutdown, and by daily cron(1M) job. The at(1) job is no longer used. /usr/lib/dstime/dst_sync could also be run by a privileged user, to synchronize after changing date or Time Zone, but the daily cron job or shutdown script will soon make the necessary correction automatically. 3. The at(1) permitted the date Feb 29 only when the current year is a leap year, whatever the year for the at(1) job itself; and (at one point) treated the year 2000 as not a leap year, scheduling jobs for Mar 1, 2000 to Dec 31, 2000. But neither of these errors occurred when using the -t time syntax, nor when using the environment variable DATEMSK (typically DATEMSK=/etc/datemsk) to parse the date. The atrm(1) did not have a Year 2000 problem, but it was liable to fail with the message Segmentation Fault - core dumped. This fix is also included since it is used by the installation of this PTF to replace the at job by a daily cron job. 4. Accounting programs acctcms(1M), acctcon(1M) and acctcon1, acctprc(1M) and acctprc1 divide time spent into prime time and non-prime (out- of-hours or holiday) time, according to the entries (inserted by the administrator) in /etc/acct/holidays. Year 2000 was accepted, but years 2001 onward were rejected. Accountings daily LAST LOGIN report could never advance from a 99-MM-DD login to a 00-MM-DD login, fixed and sorted (but 00-00-00 accounts never logged in are now omitted). 5. NetWare servers Admin_Tools/Networking/DS_Repair (Directory Services Repair) program showed year 20YY as 1YY, now shows YY. NetWare UNIX clients Admin_Tools/Networking/NetWare_Access program showed login year 20YY as 191YY, now shows 20YY.1 6. The lp/model banners, and sv .437 locales, showed year 20YY as 19YY. The lp/model scripts all have a regular expression fix from standard. 7. The ftpd(1M) responded to modtime with modification year 191YY for 20YY. The ftp(1) newer ignored modtime century, often misjudged whether newer. The ftp(1) newer and modtime now allow for an uncorrected ftpd(1M) modtime response, correcting its 191YY to 20YY. 8. The uucico(1M) and uuxqt(1M) logged times to /var/uucp/.Admin/perflog showing year as 1YY, now YY; uustat(1C) -t processed perflog times as if year 99 came after year 00, now as if year 99 before year 00. 9. The auditrpt(1M) -s and -h rejected time YY 00-69, now rejects 38-69. The prt(1BSD) -c and -r rejected cutoff YY 00-69, now rejects 38-69. 10. Taking the year 2000 itself as an example: passwd(1) -s showed year of last password change as 100, now shows 00. The smtpd(1M) Received: from line showed year as 100, now shows 00. The w(1BSD) showed year of week-old login time as 100, now shows 00. The whodo(1M) -l showed year of week-old login as 0, now shows 00. The UDK 7s /udk/usr/ccs/bin/prs -d:Dy: showed year as 100, now shows 00. 11. The uptime(1BSD) is a copy of w(1BSD). The touch(1) had been fixed in UW2.1.1, but its acp package link to settime(1XNX) broken. 12. In libc: getdate(3C) and strptime(3C) now interpret years 69-99 as 1969-1999, years 00-68 as 2000-2068 - according with the UNIX98 standard, and allowing user account administration menus to accept expiry years 00 onwards. But note that getdate(3C), like touch(1), rejects UTC times which cannot be stored in 31 bits: the first few weeks of 2038, and the final hours of 1969 in a timezone West of GM, are accepted; but most times before 1970 or after 2037 are rejected. 13. Additional fixes to libcs time handling, unrelated to the year 2000: mktime(3C)s normalization of out-of-range tm fields was incorrect near a leap year; mktime(3C)s decision on tm_isdst (daylight savings) could go wrong; strftime(3C) went wrong on times before 1970 due to bad leap day calculations; and strftime(3C)s %E era-specific handling depended incorrectly on the %O modifier. 14. Also fixed in libc: possibility of buffer overflow in catopen(3C); and possibility of coredump when memory exhausted from malloc(3C). Known Problems Remaining For a list of Known Problems in NonStop Clusters, please see the softdoc for release D10IPM20. End of Softdoc

Share in:

Related:

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 icon© 2008 Microsoft Corporation. This document is developed prior to...

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconGovernment Product/Service Accessibility Template for Application/Operating System Software

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconWelltech Product Release Note

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconProduct maintenance release bulletin

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconProduct maintenance release bulletin

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconThank you for choosing this TeckNet product. To ensure optimum performance...

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconEnvironmental declaration product, brand name, item no., etc.: Dorma...

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconDate: New Product Update Total Number of Products: 36

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconDate: New Product Update Total Number of Products: 36

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconDate: New Product Update Total Number of Products: 51

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconDate: New Product Update Total Number of Products: 27

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconDate: New Product Update Total Number of Products: 33

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconDate: New Product Update Total Number of Products: 39

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconCertification Requirements The NonStop Advanced Application Design...

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconThis document covers the functional description, specification and...

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconSpecifications of the Equipments to be procured: In this specification,...

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconSpecifications of the Equipments to be procured: In this specification,...

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconValidation Test Plan: Running [Software Product] on vmware Infrastructure

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconProduct Overview 6 Questions and Answers 13 SmartStart Scripting...

Software release document product Name Integrity xc system NonStop Clusters for sco unixWare Product Number T5649D10ipm30 iconThis product is manufactured by a firm whose quality system is in...




manual




When copying material provide a link © 2017
contacts
manual-guide.com
search