K-Series to S-Series Differences The S-series servers are supported by G-series RVUs, which introduce the following enhancements: ● Graphical user interface with extensive online help ● Online configuration ● Integrated software products See a comparison diagram of K-series and S-series servers. S-Series Software Package and Management Tools The following software is included with the S-series servers. Click on the links for general information about how you can use these software packages.
Install Installs new operating system or SPR and configures software Distributed Systems Management/Software Configuration Manager (DSM/SCM) Multilan Server Accesses NonStop resources from LAN workstations NetBIOS (NBT) NetBIOS over NonStop IPX/SPX (NBX) product Peripheral Utility Program Manages storage Subsystem Control Facility (PUP) devices, including disks (SCF) and tapes Remote Console Process Provides a remote OSM or TSM software (RCP) system console Remote Maintenance Loads processors, OSM or
documentation that supports them, see Sources of Information. Note: G-series RVUs support S-series servers and D-series RVUs support NonStop K-series servers.
Comparison Diagram of K-Series and S-Series Servers Map: K-Series to S-Series Differences.
The Distributed Systems Management/Software Configuration Manager (DSM/SCM) Map: K-Series to S-Series Differences. The Distributed Systems Management/Software Configuration Manager (DSM/SCM) provides tools for centralized planning, management, and installation of software on distributed (target) systems. Caution: DSM/SCM is preconfigured. Exercise care when changing $AUDIT and $DSMSCM disk names to prevent DSM/SCM from becoming unusable.
OSM and TSM Packages Map: K-Series to S-Series Differences. The OSM and TSM packages provide troubleshooting, maintenance, and service tools. Both packages require that you use the HP NonStop System Console. Beginning with the G06.21 RVU, OSM can be used instead of TSM to perform system management and monitoring tasks. Also beginning with the G06.21 RVU, support for new products and new functions are provided by OSM only.
NonStop System Console Map: K-Series to S-Series Differences. The HP NonStop system console provides a preconfigured workstation for the purpose of control, status, monitoring, and remote access of one or more S-series systems. The system console provides OSM or TSM user interface applications for system maintenance and serviceability. User interfaces are also provided for system operator functions and for retrieving online documents.
Subsystem Control Facility (SCF) Map: K-Series to S-Series Differences. The Subsystem Control Facility (SCF) configures system, peripheral, and communication devices and subdevices and also configures processes and several system variables. SCF configures and manages over 40 subsystems. Several of these subsystems use the system configuration database.
Initial Configuration of an HP NonStop S-Series Server Map: K-Series to S-Series Differences. For G-series RVUs, many configuration tasks are completed by HP before the NonStop S-series server arrives at your site. HP provides you with the initial system configuration required to load the NonStop Kernel operating system, including: ● The system configuration database, $SYSTEM.ZSYSCONF.
● ● ● files. ❍ $AUDIT Volume - contains DSM/SCM archive files and TMF audit trail files. Software Products and Documentation ❍ Manufacturing installs customer-ordered software on NonStop S-series servers using DSM/SCM. To view the software products and documentation installed, use the DSM/SCM Planner Interface, as described in the DSM/SCM User's Guide. ❍ Includes RVU README files, Softdocs, software in the archive, and information about target software configurations.
Example: SCF0000 File for G06 This example is based on a four processor NonStop S-series server with one I/O enclosure and one ServerNet wide area network (SWAN) concentrator. ========================================================================= == S7000/S70000 Configuration File == == This file contains the necessary SCF commands to configure this == system as delivered from HP Manufacturing.
OUTFILE $ZHOME, STARTUPMSG "; AUTOSTOP -1" ========================================================================= == CLCI TACL ========================================================================= ADD PROCESS #CLCI-TACL, NAME $CLCI, PRIORITY 199, AUTORESTART 10, & PROGRAM $SYSTEM.SYSTEM.TACL, PRIMARYCPU 0, BACKUPCPU 1, TYPE OTHER, & STARTMODE MANUAL, HOMETERM $YMIOP.#CLCI, INFILE $YMIOP.#CLCI, & OUTFILE $YMIOP.#CLCI, STARTUPMSG "" == Start QIO, WAN Manager, etc.
START PROCESS $ZZKRN.TSM-ZTCP0 ADD PROCESS $ZZKRN.TSM-ZTCP1, & AUTORESTART 0, & DEFAULTVOL $SYSTEM.ZSERVICE, & HIGHPIN ON, & HOMETERM $ZHOME, & NAME $TSMM1, & CPU 1, & PRIORITY 150, & PROGRAM $SYSTEM.SYSTEM.TACL, & INFILE $SYSTEM.ZTSM.INIT1, & STARTMODE SYSTEM, & STARTUPMSG "0", & USERID SUPER.SUPER START PROCESS $ZZKRN.TSM-ZTCP1 == This section adds the TSM processes themselves that need to be == started at boot time. == ADD $ZLOG to SCF database and issue command to start process ADD PROCESS $ZZKRN.
HOMETERM $ZHOME, & NAME $ZTSMS, & PRIORITY 150, & PROGRAM $SYSTEM.SYSTEM.SNMPAGT, & OUTFILE $ZHOME, & STARTUPMSG "TCPIP^PROCESS^NAME $ZTCP0, SUBAGENT^TIMEOUT 12", & STARTMODE SYSTEM START PROCESS $ZZKRN.TSM-SNMP == Add $ZTSM tsm process to SCF database and issue start command ADD PROCESS $ZZKRN.TSM-SRM, & AUTORESTART 5, & CPU FIRST, & DEFAULTVOL $SYSTEM.ZSERVICE, & HIGHPIN ON, & HOMETERM $ZHOME, & NAME $ZTSM, & PRIORITY 150, & PROGRAM $SYSTEM.SYSTEM.
AUTORESTART 0, & CPU FIRST, & DEFAULTVOL $SYSTEM.ZSERVICE, & HIGHPIN ON, & HOMETERM $ZHOME, & NAME $TSMRD, & PRIORITY 150, & PROGRAM $SYSTEM.SYSTEM.TACL, & INFILE $SYSTEM.ZTSM.INITRD, & STARTMODE APPLICATION, & TYPE OTHER, & USERID SUPER.SUPER START PROCESS $ZZKRN.ROUTING-DIST == Configuring SNMP for the Primary HSSC TSM clients ASSUME PROCESS $ZTSMS ADD PROFILE $ZTSMS.#TSMPRI, HOSTADDR "192.231.36.1", ACCESS READWRITE, & COMMUNITY "tsm192.231.36.1" START PROFILE $ZTSMS.#TSMPRI ADD TRAPDEST $ZTSMS.
ADD DISK $D0213, PRIMARYLOCATION (02,1,13), MIRRORLOCATION (02,1,14) ADD DISK $D0215, PRIMARYLOCATION (02,1,15), MIRRORLOCATION (02,1,16) ADD DISK $D0217, PRIMARYLOCATION (02,1,17), MIRRORLOCATION (02,1,18) ==********************************************************************** == == Group 11 == ==********************************************************************** ADD DISK $D1101, PRIMARYLOCATION (11,1,1), MIRRORLOCATION (11,1,2) ADD DISK $D1103, PRIMARYLOCATION (11,1,3), MIRRORLOCATION (11,1,4) ADD DIS
== == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == == Once a customer system has been installed, these names can be changed to fit the needs of the customer. Special attention should be placed on systems using the sockets library to interface to TCP/IP. Unless specifically named, the default TCP/IP process name is $ZTC0.
== 52 2 6 == 52 3 7 == 53 0 8 == 53 1 9 == 53 2 A == 53 3 B == 54 0 C == 54 1 D == 54 2 E == 54 3 F == == = incremental number from 00-99 == ========================================================================= ========================================================================= == Add an E4SA ADAPTER to slot 01.1.
== so. == Sierra Naming Convention for Manufacturing == ------------------------------------------------------------== The new symbolic process names being proposed are as follows : == 1. $ZZKRN.SWAN-SNMP ( SNMP agent symbolic process name) == 2. $ZTMX (SNMP agent symbolic process name) == 3. $ZZWAN.
PROGRAM $SYSTEM.SYSTEM.SNMPAGT, & OUTFILE $ZHOME, & STARTUPMSG "TCPIP^PROCESS^NAME $ZB018", & STARTMODE SYSTEM START PROCESS $ZZKRN.SWANA-SNMP ========================================================================= == Configure a SNMP Trap multiplexor for the SWAN TCPIP's. This is == to catch SWAN hardware event traffic that is to be routed to TSM. ========================================================================= ADD PROCESS $ZZWAN.#ZTMX1 ,IOPOBJECT $SYSTEM.SYS00.
ADD DEVICE $ZZWAN.#S1S2, PROFILE ATPTERM, & IOPOBJECT $SYSTEM.SYS00.OATPCSS, & CPU 00, ALTCPU 01, TYPE (53,00), RECSIZE 80, CLIP 2, LINE 1, & ADAPTER S01, STARTDOWN ADD DEVICE $ZZWAN.#S1P3, PROFILE ATPTERM, & IOPOBJECT $SYSTEM.SYS00.OATPCSS, & CPU 00, ALTCPU 01, TYPE (53,00), RECSIZE 80, CLIP 3, LINE 0, & ADAPTER S01, STARTDOWN ADD DEVICE $ZZWAN.#S1S3, PROFILE ATPTERM, & IOPOBJECT $SYSTEM.SYS00.
Sources of Information for K-Series to S-Series Differences This is part of the K-Series to S-Series Differences procedure.
Configuring new hardware For G06.21 and later: NonStop S-Series Hardware Installation and FastPath Guide For G06.20: NonStop S-Series Hardware Installation Guide For G06.17, G06.18, and G06.19: NonStop S-Series Planning and Configuration Guide For G06.16 and earlier: Himalaya S-Series Planning and Configuration Guide Determining power requirements, cooling, For G06.17 and later: NonStop S-Series and other installation considerations Planning and Configuration Guide For G06.
Verifying the functions of the operational environment For G06.20 and later: NonStop S-Series Hardware Installation and FastPath Guide For G06.20: NonStop S-Series Hardware Installation Guide For G06.17, G06.18, and G06.19: NonStop S-Series Planning and Configuration Guide For G06.16 and earlier: Himalaya S-Series Planning and Configuration Guide Falling back to the previous G-series RVU Gxx.
K-Series to S-Series Migration Considerations Map: K-Series to S-Series Differences. Sources of Information for K-Series to S-series Differences refers you to NonStop publications that provide details on performing migration-related tasks. The following information is only a summary of some of the more critical aspects of migrating a system.
sequence, you can create additional startup files for the system, subsystems, system software, processes, communication lines, and applications. For examples of startup files: ● For G06.21 and later, see the NonStop S-Series Hardware Installation and FastPath Guide. ● For G06.20, see the NonStop S-Series Hardware Installation Guide. ● For G06.19 and earlier, see the NonStop S-Series Planning and Configuration Guide.
After the first system load using the START SYSTEM action in OSM or TSM, you must use the SCF Kernel subsystem to change the initial values to values appropriate for your site for these system attributes: System Attribute SYSTEM_NAME SYSTEM_NUMBER DAYLIGHT_SAVINGS_TIME TIME_ZONE_OFFSET Initial Value \NONAME 254 NONE 0:00 Caution: After you have named your system, you should avoid renaming it later because a name change affects many products. For example, changing the system name affects your SQL database.
Recommended Software Product Revisions (SPRs) Map: K-Series to S-Series Differences. Note: Use our Feedback form to let us know of other considerations about SPRs that you would like for us to add to this page. SPRs provide new features between release version updates (RVUs) or correct software problems from a previous RVU. You must apply any fallback SPRs on the RVU you might have to fall back to. Caution: Many SPRs supported for D-series RVUs will not function properly on a G-series system.
Fallback Considerations Map: K-Series to S-Series Differences. Note: Use our Feedback form to let us know of other fallback considerations that you would like for us to add to this page. Fallback procedures help you work with system limitations you might encounter when installing software or falling back to your previous release version update (RVU). Source for General Instructions For general upgrade installation instructions and fallback alerts, see the Gxx.
5 Stop applications and then stop the system by halting the system processors (you do not need to power down). 6 Load the system from a saved system configuration database.
