Preface With the business servers in the SX series (abbreviated to: SX servers), Fujitsu Siemens Computers is pursuing its strategy of opening up the BS2000/OSD operating system by making available a modern hardware solution which is based on SPARC64™ technology and represents a future-safe investment for the customer.
Preface All SX series models have the latest processor technology and optional fibre channel interface technology for fibreCAT disk systems with possible SAN integration. These features ensure that SX series models are a future-safe investment. Figure 1: Example of an SX server: SX150 Business Server On the business servers in the SX series suitable redundancy facilities result from the operation of several partitions.
Preface X2000 is based on the Solaris operating system and provides the following functions: ● HAL (Hardware Abstraction Layer) HAL maps the hardware-software interfaces of the /390 mode to equivalent interfaces of the SPARC64 mode. ● /390 firmware The /390 firmware component extends the SPARC64 mode and enables existing customer applications to run object-compatibly on the SX servers under OSD/XC.
Documentation for the SX Series Business Servers Preface 1.1 Documentation for the SX Series Business Servers Extensive documentation is available to help you in your work with SX servers. It can be ordered in printed form as a documentation package. Its exact composition can be found in the Release Notice for OSD/XC.
Preface Documentation for the SX Series Business Servers ● OSD/XC Performance Guidelines User Guide This manual focuses on the principles and measurements involved in evaluating the performance of BS2000/OSD applications which run on SX servers. The performancerelated characteristics of the SX server architecture are described together with the underlying operating sequences.
Documentation for the SX Series Business Servers Preface The following manuals in the core literature have been extended or replaced for OSD/XC: Manual Comment BS2000/OSD-BC Performance Handbook Replaced by: OSD/XC Performance Guidelines BS2000/OSD-BC System Exits Only valid in connection with Special Release i The “OSD/XC Migration Guide” will be discontinued. As of the edition of June 2005 migration to SX servers is described in the “BS2000/OSD-BC Migration Guide” [3].
Preface Target groups 1.2 Target groups This manual is intended for privileged users (operators, system administrators) of the SX series business servers. It is assumed that readers possess a thorough understanding of the operating system and the hardware and have a basic knowledge of the graphical user interface PRIMEPOWER ServerView. 1.3 Summary of contents You will find general information on the operation of an SX server in the chapter “Operating concept of the SX servers”.
Summary of contents Preface The chapter “Dynamic Reconfiguration” describes how Dynamic Reconfiguration can be performed for BS2000 partitions and the requirements for this. This function is available on SX servers as of the SX150 model series. The chapter “Solaris: system administration” gives an overview of the system administration in Solaris with reference to one or two examples. The chapters “What if ...” and “X2000 messages” contain information on the detection and removal of faults.
Preface Notational conventions 1.4 Notational conventions The following fonts and symbols are used in this manual to indicate different types of information: Font/Symbol Indicates Example AaBbCc123 System outputs are written in this typewriter font. RC2000% AaBbCc123 Commands entered by the user are written in typewriter font bold # ls -l Italic text Program interface functions and menus are written like this.
Notational conventions 10 Preface U41272-J-Z385-3-76
2 Operating concept of the SX servers SX servers (with the exception of entry-level models) are operated via the system management console (SMC) as the central console for the hardware and for the BS2000 and – optionally – Solaris operating systems. The business servers of the SX series, with the exception of the entry-level models, are therefore also referred to in the following as “SX servers with SMC”. A concept has been developed for uniform operation of the different operating systems.
Operating concept for SX servers with SMC Operating concept of the SX servers 2.1 Operating concept for SX servers with SMC The figure below shows the operating concept of an SX server with SMC and a BS2000 and Solaris partition, taking the example of an SX130 configuration: System cabinet SX1xx Server BS2000 partition BS2000/OSD (OSD/XC) Solaris partition Solaris X2000 User LAN CCU Modem SCF Switch Switch Router Admin LAN System Control LAN TeleserviceGate V.
Operating concept of the SX servers Operating concept for SX servers with SMC System administration of X2000 functions (and optionally, Solaris functions) can be performed from any client via the PRIMEPOWER ServerView graphical user interface. To do this, you will need a Web browser which has Java support. The SMC server names and the names of all the partitions present on the SX server must be entered in the DNS.
SX server entry-level models (without SMC) Operating concept of the SX servers 2.2 Operating concept for SX server entry-level models (without SMC) SX100 PCI Integrated console BS2000 OSD/XC LAN BS2000 ZASLAN DAT hme0 Teleservicegate V24 DVD Modem SOLARIS / X2000 Customer LAN PC X-Server Browser SINIX-TE opt. 9750-Emu. Figure 4: Operating concept of an SX server without SMC An SX server entry-level model is operated as standard via the integrated console.
Operating concept of the SX servers SX server entry-level models (without SMC) 2.2.1 Operation with integrated console The entry-level models are operated from an integrated console with screen, keyboard and touchpad installed in a rack. The console is a Solaris console device on which the messages of the Solaris and the X2000 carrier system can be monitored when starting up the server (e.g. after switching on). This therefore gives you access to the OpenBoot PROM.
Remote operation via LAN-PC Operating concept of the SX servers The LAN console is available for administering UNIX/Solaris midrange servers and SX server entry-level models from Fujitsu Siemens Computers Gmbh. The LAN console has the following features: ● It supports the installation, configuration, administration and diagnostics management of one or more connected SX server entry-level models, RM servers and PRIMEPOWER servers.
Operating concept of the SX servers Notes on security 2.4 Notes on security With an SX business server you can connect multiple systems to each other to form an operating cluster. Entry-level models in addition to the operating system BS2000/OSD now have the carrier system X2000 available as an additional system. This means that for administration and operating purposes you will require access to a number of different logins.
Notes on security Operating concept of the SX servers However, should it become necessary to work under the root login then it is advisable to set up user-specific logins under which login can be performed. Only then should the user acquire root permissions by means of the su command.
Operating concept of the SX servers Notes on security Separate server administration and partition administration ● Each partition on the SX server can have its own partition administrator. The partition administrator possesses the rights necessary to switch the partition on and off and access the partition's hardware console. For information on setting up a login for a partition administrator, refer to section “User groups and logins” on page 44.
Notes on security Operating concept of the SX servers To connect additional operator terminals via LAN, it is always necessary to enter a password. All the inputs and outputs can be recorded in a logging file and then archived. In the case of high security requirements, the option for both logging and archiving should be set to FORCED.
Operating concept of the SX servers Notes on security If the SSH is to be used on the BS2000 partition (i.e. the product OpenSSH is installed), the rlogin, rsh, rcp, ftp and telnet services offered on the LAN are deactivated automatically and they are replaced by the equivalent SSH interfaces ssh, scp and sftp.
Remote service (Teleservice) Operating concept of the SX servers Components of the SSH The SSH suite comprises the client program ssh which replaces rlogin, rsh and telnet, Secure Copy scp which replaces rcp, and the Secure File Transfer Programm sftp which replaces ftp. The client program ssh is used to set up a connection to a remote system and to execute commands on a remote system.
Operating concept of the SX servers Operating sequences on server switch-on / switch-off An ISDN telephone connection is also required in the vicinity of the system. ● i If no ISDN connection can be provided then an analog modem must be ordered separately. Teleservice Call Management is a central instance in X2000 which makes it possible to automatically report error messages from the Solaris/X2000/BS2000 area of a partition to the Teleservice center.
Operating sequences on server switch-on / switch-off Operating concept of the SX servers 2.6.1 SX server with SMC 2.6.1.1 Switch-on of the SX server and automatic start-up of the operating systems SMC ready ● Power on the server (described in the SX1xx Operating Manual [2]) ● Start up the System Management Console (SMC) (described in the SX1xx Operating Manual [2]) This automatically starts Solaris at the SMC as well as the System Console Software.
Operating concept of the SX servers 2.6.1.2 Operating sequences on server switch-on / switch-off Automatic termination of operating systems and server switch-off An SX server with SMC is switched off in the same way it is switched on, i.e. via the SCS Machine Administration Menu on the SMC.
Operating sequences on server switch-on / switch-off Operating concept of the SX servers 2.6.2 SX server entry-level models 2.6.2.1 Switch-on of entry-level model and automatic start-up of BS2000/OSD Power on of system unit ● Power on the system unit (see SX100 operating instructions [2]) System unit ready ● This starts up the system unit. After the POST (Power On Self Test), X2000 is started automatically.
3 Functions of the Solaris-CDE interface The business servers in the SX series are operated from the console of the server with the Solaris user interface. This user interface is called Common Desktop Environment – abbreviated to CDE. Here, the interface provides not only functions for operating Solaris (or the X2000 carrier system) but is also used for operating BS2000 instances. Details on operation are given in the following section.
CDE interface Functions of the Solaris-CDE interface 3.1 CDE interface Login screen When the system console has been switched on, the following login screen appears (this example is for the SMC): Figure 8: CDE login screen (user name) Ê Enter your user name in the text box (e.g. sxadmin; see the following section). Then click the OK button. A new window appears in which to enter your password: Figure 9: CDE login screen (password) Ê 28 Enter your password in the text box. Then click the OK button.
Functions of the Solaris-CDE interface CDE interface If this is the first time you have logged in, the following windows appear on the system console (this example is for the SMC): Application Manager CDE control panel SCS button File manager with home directory Figure 10: CDE window after the first login on a SMC The next time you log in, the interface will appear in the form it was when you terminated the CDE.
CDE interface Functions of the Solaris-CDE interface The Application Manager of the System Console Software (SCS) from which the functions can be activated looks like this: Figure 11: Application Manager of the System Console Software (SCS) A double-click calls up the functions.
Functions of the Solaris-CDE interface System administration of BS2000 and Solaris (optional) 3.2 System administration of BS2000 and Solaris (optional) In the case of SX servers (not entry-level models) you must access the partitions in order to be able to administer the operating systems in the individual partitions.
Preconfiguring terminals Functions of the Solaris-CDE interface 3.3 Preconfiguring terminals The preconfiguration for accessing the individual functions is based on the creation of an “action” in the CDE interface of the Solaris system on the SMC or on the X2000 carrier system. An icon is assigned to a command sequence. The configured commands can be called up via this icon simply and without a risk of operator error.
Functions of the Solaris-CDE interface Preconfiguring terminals Three entries are important when creating an action: – – – The name of the action (subtitle of the icon) The icon The command which is triggered when the icon is activated (with a double-click) These three entries must be entered in that order in the fields of the window Create Action. Enter the name of the icon in the first input line Action Name (Icon Label).
Preconfiguring terminals Functions of the Solaris-CDE interface Confirm your selection with OK. After returning to the main window, enter the actual command. Do this in the line Command when Action is Opened (Double-clicked).
Functions of the Solaris-CDE interface ● Preconfiguring terminals Integrate the action into the CDE control panel First create a new button in the CDE control panel to do this. Right-click on the position at which the button is to be added. Select Add Icon from the context menu which is displayed. An empty button is then created. The button is assigned the action dragged onto it from the opened file manager with the home directory.
Preconfiguring terminals Functions of the Solaris-CDE interface ● Select a background color with -bg , e.g. -bg grey65. ● This is particularly important with the BS2000 console if the terminal type bs2console is not set, since the called BS2000 KVP program outputs the messages in yellow. All colors that can be selected are listed in the file /usr/openwin/lib/X11/rgb.txt. When selecting a color, ensure that all outputs remain legible.
Functions of the Solaris-CDE interface Preconfiguring terminals 3.3.3 BS2000 console The ID cons0 mentioned in this section represents a predefined KVP ID. Here the relevant KVP ID must be entered, according to the desired IPL console mnemonics (for this see page 164).
Preconfiguring terminals Functions of the Solaris-CDE interface 3.3.
Functions of the Solaris-CDE interface Preconfiguring terminals 3.3.5 PRIMEPOWER ServerView (BS2000 system) SX server (not entry-level models) A CDE action can also be created to call PRIMEPOWER ServerView as an application. The call should be made in the System Management Console. When creating the action, select the icon “WSA” instead of the icon “Dtterm”. The command to be entered should then be: /opt/SMAW/bin/wsa `uname -n` The command locally calls the PRIMEPOWER ServerView-application of the SMC.
Calling terminal instances Functions of the Solaris-CDE interface 3.4 Calling terminal instances The desktop generated in the previous section can have the following appearance: Figure 15: Example of a desktop The generated actions (e.g. BS2000 console) are called either by clicking on the button in the CDE control panel or by activating the submenu of this button (click on the small arrow at the top edge of the icon) and the clicking on the relevant entry.
Functions of the Solaris-CDE interface Calling terminal instances If windows are opened during the current CDE session and the session is terminated with EXIT, these windows will automatically be restarted when you next log in to the CDE interface.
Calling terminal instances 42 Functions of the Solaris-CDE interface U41272-J-Z385-3-76
4 Functions of the System Management Console A PRIMEPOWER250 (up to and including SX140 a PRIMESTATION) is used on SX servers (with the exception of entry-level models) as the System Management Console (SMC): ● The SMC checks the hardware configuration and the operating status of the SX server. ● The SMC partitions the resources and thus enables the processor and memory capacities of the SX server to be shared. ● The SMC supports partition-specific console displays.
User groups and logins Functions of the System Management Console 4.1 User groups and logins The System Console Software supports a graded system of rights to manage the hardware functions of the SX server. The following sections describe how to set up logins for the various administrator roles (server administrator, partition administrator, BS2000 or Solaris administrator, and also administrator of PRIMEPOWER ServerView) with PRIMEPOWER ServerView and the System Console Software (SCS).
Functions of the System Management Console User groups and logins The functionality of the user groups cladmin and clmon and the partition administration groups p0grp, p1grp, etc. described in the sections below is determined by SCS and described in the following table. The user groups mentioned are set in the factory.
User groups and logins Functions of the System Management Console 4.1.1 Server administrator The administrator of the server manages the entire server and the system console. The administrator has root access to the system console. This root authorization allows the administrator to use all available functions of the SCS.
Functions of the System Management Console User groups and logins d) Create a new user (e.g.
User groups and logins – – – Functions of the System Management Console No entries are required in the “Supplementary groups” section for someone who is exclusively an SX server administrator. If PRIMEPOWER ServerView is also to be operated in write mode under this user ID, wsauser must be selected as the secondary user group. The secondary user group wsaruser must be selected for operation in read mode.
Functions of the System Management Console User groups and logins 4.1.2 Partition administrators Partition administrators also use the interface of the System Console Software to manage the hardware of the partition. They have access to the hardware console of the partition assigned to them and are authorized to switch the partition on/off. They do not have rights to any other partitions.
User groups and logins Functions of the System Management Console d) Create a new user (e.g. user name soladmin2) as a member of the user group clmon: Figure 17: PRIMEPOWER ServerView window: “Create user” (clmon) No entries are required in the “Supplementary groups” section for someone who is exclusively an SX server administrator. If PRIMEPOWER ServerView is also to be operated in write mode under this user ID, wsauser must be selected as the secondary user group.
Functions of the System Management Console User groups and logins 2. If necessary, configure a further partition-specific user group with PRIMEPOWER ServerView, e.g. part1grp. i User groups suitable for this have already been configured by default with the name p0grp, p1grp, etc. and are used for the partition administrators bs2admin and soladmin. These groups can be used when configuring further partition administrators. Alternatively, further user groups can also be created for this.
User groups and logins Functions of the System Management Console 4.1.3 BS2000 or Solaris administrators To manage the operating systems of individual partitions, it may be useful to configure user IDs which do not have extended rights relating to the management of the hardware of the server (like server administrators or partition administrators). These user IDs must however be able to read the data of the RC2000 consoles of the partitions.
Functions of the System Management Console User groups and logins 2. Set up the SCS user interface (Terminal in the Application Manager) for the user ID using the following command (which must be executed with root authorization): /opt/FJSVscsl/bin/scslowneradd -h :clmon In the next step you must remove the assignment of administration rights to a partition which was needed temporarily to set up the SCS user interface. Proceed as follows: 3.
User groups and logins Functions of the System Management Console d) Create the new user (e.g. user name pwsvadm) Figure 19: PRIMEPOWER ServerView window:”Create user” (administrator of PRIMEPOWER ServerView) As the user is not to be allocated special SCS privileges, the user must be assigned as a member of the primary user group other. The SMC must be selected as the node.
Functions of the System Management Console User groups and logins 2. After this it may be necessary to adjust the access rights to the applications of PRIMEPOWER ServerView and the nodes of the administration domain. In the following cases such a user ID is automatically assigned the full access rights to all available applications of PRIMEPOWER ServerView and to all nodes of the administration domain: ● Use of PRIMEPOWER ServerView Suite Version < V2.
System console software (SCS) Functions of the System Management Console 4.2 System console software (SCS) The system console menu used to activate the functions looks like this: Figure 20: System console menu Click the system console icon in the toolbar to open the menu.
Functions of the System Management Console System console software (SCS) The table below describes the functions of the tools provided on the system console: Function Description System Console Menu with the functions provided by the system console. Is automatically started after logging in. RC2000 Shows a host browser via which the console windows of the server can be opened. Is automatically started after logging in.
Functions of the System Console Software (SCS) Functions of the System Management Console 4.3 Functions of the System Console Software (SCS) This section describes the SCS functions Machine Administration Menu, RC2000 and Monitoring Messages. 4.3.1 Machine Administration Menu The System Console Machine Administration Menu enables the management and servicing of the system hardware. This menu is available for administrators of the system console or service engineers.
Functions of the System Management Console 4.3.1.1 Functions of the System Console Software (SCS) Functions for switching the server on/off This section describes how the power supply of the server is handled via the system console. The following procedure describes how to access the System/Partition Power Administration Menu: 1. Select System Specific Administration: 1 All available servers are offered for selection.
Functions of the System Console Software (SCS) Functions of the System Management Console 2. Select the required server.
Functions of the System Management Console Functions of the System Console Software (SCS) 3. Select System/Partition Power Administration: 8 This opens the menu System/Partition Power Administration for the selected server (machine0): Figure 23: Machine Administration Menu: “System/Partition Power Administration” The System/Partition Power Administration menu contains the following functions: 1. System Power-On Instruction 2. System Power-Off Instruction 3. Partition Power-On Instruction 4.
Functions of the System Console Software (SCS) Functions of the System Management Console Switching the entire server on The function System Power-On Instruction switches the server on if it is switched off. Switching on the server via this menu item has the same effect as powering on the server via the control panel on the front side of the SX server (see the SX1xx Operating Manual [2]). 1.
Functions of the System Management Console Functions of the System Console Software (SCS) Switching the entire server off The function System Power-Off Instruction switches the server off if it is switched on. 1.
Functions of the System Console Software (SCS) Functions of the System Management Console Switching partitions on The function Partition Power-On Instruction switches on one or more partitions. Switching on a partition starts the operating system in the partition. i 1. Select the function Partition Power-On Instruction from the menu System/Partition Power Administration: 3 The following screen output shows the status of the individual partitions on the selected server.
Functions of the System Management Console Functions of the System Console Software (SCS) Switching partitions off The function Partition Power-Off Instruction powers off one or more partitions. 1. Select the function Partition Power-Off Instruction from the menu System/Partition Power Administration: 4 The following screen output shows the status of the individual partitions on the required server.
Functions of the System Console Software (SCS) 4.3.1.2 Functions of the System Management Console Switching the server on/off on a scheduled basis The automatic power control system (APCS: ) switches the server on or off automatically, on the basis of a series of on/off schedule entries. These entries form the system schedule. Switching on/off thus affects all partitions of the server.
Functions of the System Management Console Ê Functions of the System Console Software (SCS) Select Auto Power Control System (APCS) Administration from System-Specific Administration (see figure 22 on page 60): 11 This opens the APCS Setup Menu: Figure 24: Machine Administration Menu: “APCS Setup Menu” The following actions can be performed using this menu: – – – – – – – – Starting the system schedule Stopping the system schedule Adding an entry to the schedule and deleting an entry Adding a
Functions of the System Console Software (SCS) Functions of the System Management Console Examples a) Setting the power on time: Set Power On Time (Add) Please set the automatic power on time. Press the "RETURN" key if you do not wish to power on the system automatically. Example) Power on at AM 8:00 : Power on at PM 2:00 : 0800 1400 q:quit b:back t:top ---------------------------------------------------------------------Select.(HHMM,q,b,t): Enter the four-digit time and press the Return key.
Functions of the System Management Console Functions of the System Console Software (SCS) c) Setting the schedule: Schedule Setup (Add) Please set the day or days to put into operation. .Specific Day Example) Feb. 1st, 2000 : 20000201 .Specific days in this month Example) From 1st through 10th : 01-10 .To repeat this for several months Example) From 1st through 10th in Feb. through May : 01-10 -r 02-05 .From a specific day through another specific day Example) From Feb. 1st through Jun. 10th : 0201-0610 .
Functions of the System Console Software (SCS) Functions of the System Management Console 3. You can enter holidays with the function Add Holiday: 4 Example Add Holiday Please set the day when schedule entry or entries are to be ignored. Example) Feb. 1st, 2000 : 20000201 q:quit b:back t:top ---------------------------------------------------------------------Please input.(YYMMDD,q,b,t): Enter the six-digit holiday date (YYMMDD). Then press the Return key. 4.
Functions of the System Management Console Functions of the System Console Software (SCS) 6. Select the function Start System Schedule to start the system schedule: 1 7.
Functions of the System Console Software (SCS) Functions of the System Management Console In this application the tasks are preferably executed on the SMC since the System Console Software (SCS) is only directly available there. Example Activating a partition every Monday at 8.00 a.m..
Functions of the System Management Console Functions of the System Console Software (SCS) After the power supply has been switched on the system unit is started up. After the POST (Power On Self Test) the Solaris operating system and, in the BS2000 partitions, the X2000 carrier system is started automatically if the mode selector in the SX server’s control panel is set to LOCK (see figure “Control panel of an SX140 or SX150 server”).
Functions of the System Console Software (SCS) Functions of the System Management Console Switching a partition off A partition is switched off using the following SCS command: /opt/FJSVcsl/bin/node_control -down -pid= Example /opt/FJSVcsl/bin/node_control -down fernando0 -pid=1 In this case any Solaris system which is still running is closed down in an orderly manner and the power supply to this partition is interrupted. This procedure can take about 1 minute.
Functions of the System Management Console 4.3.1.4 Functions of the System Console Software (SCS) Administering the system board’s operating mode In SX140 systems or higher it is possible to define, ascertain or modify the operating mode of any system board located in a cabinet slot. A system board can be operated in the following modes: X for the extended system board (XSB) mode P for the physical system board (PSB) mode On SX130 systems there are only physical system boards.
Functions of the System Console Software (SCS) Functions of the System Management Console The SB Mode Administration menu is opened: Figure 28: SB Mode Administration Menu The current operating mode of each system board in a slot s in cabinet c (presented in the format cs in the Slot column, in other words, for example, 01 for slot 1 and cabinet 0) is displayed in the Mode column of this menu: X The system board is operated in XSB mode. P The system board is operated in PSB mode.
Functions of the System Management Console Functions of the System Console Software (SCS) This menu also enables a system board to be configured or modified. To modify a board you must first select the function m. You can then use the function x in XSB mode and the function p in PSB mode to modify it (see also the Select line in figure 28 on page 76). Ê After a modification you must restart SCS: #/etc/init.
Functions of the System Console Software (SCS) 4.3.1.5 Functions of the System Management Console Configuring and modifying partitions Partitions can be configured for the operating systems and applications which run on them using the physical and/or (from SX140 systems on) the extended system board mode. In this case a partition can, however, only incorporate on type of system board mode.
Functions of the System Management Console Functions of the System Console Software (SCS) Adding a system board to a partition Ê To add a system board to a partition select the menu item System Board Addition to Partition in the Partition and System Board Administration menu: 2 The System Board Addition to Partition menu is opened. This provides information on the division of the system boards to the partitions and their status.
Functions of the System Console Software (SCS) Functions of the System Management Console Removing a system board from a partition Ê To remove a system board from a partition select the menu item System Board Removal from Partition in the menu Partition and System Board Administration: 3 The System Board Removal from Partition menu is opened. This provides information on the division of the system boards to the partitions and their status.
Functions of the System Management Console 4.3.1.6 Functions of the System Console Software (SCS) Configuring/changing the partitioning At least one partition of the SX server is reserved for running BS2000/OSD. These partitions are designated below as BS2000/OSD partitions. In addition to the BS2000/OSD partitions, an SX server can include Solaris partitions. Configuring a Solaris partition and adding or removing system boards of a partition is carried out in the same way as for the PRIMEPOWER servers.
Functions of the System Console Software (SCS) Functions of the System Management Console Now you can call up information on the hardware and partition configuration: ● Server hardware configuration After selecting Hardware Configuration Displays, the following menu is opened.
Functions of the System Management Console Functions of the System Console Software (SCS) Example for SX130: displaying system information (Display System Information) Enter “1”; the server-specific information will be displayed: PRIMEPOWER800 Serial No:23092; System Clock:225 MHz; Operation Panel Switch:Lock; Altitude:0 m; Partition#00 1 System Board; Hostname:bari1; Host ID:80f30766; Partition MAC:00.00.0e.25.07.
Functions of the System Console Software (SCS) 4.3.1.8 Functions of the System Management Console Error notifications The system console SMC detects hardware errors on the server and generates messages when an error occurs.
Functions of the System Management Console Functions of the System Console Software (SCS) You can make the following settings under System Notification Administration: ● Output error messages in a message window on the system console ● Notify the system administrator by e-mail Determine whether the system administrator is to be informed by e-mail about errors which occur. If a notification is to be made, specify further information about the system administrator, e.g. his/her name and e-mail address.
Functions of the System Console Software (SCS) Functions of the System Management Console 4.3.2 Consoles of the partitions with RC2000 This section describes how the RC2000 system (RC = Remote Console) is handled. Activating RC2000 This function is called up by selecting RC2000 from the system console menu (see figure 20 on page 56) or by double-clicking the RC2000 icon in the Application Manager (see figure 11 on page 30): When RC2000 has been activated, a host browser is displayed.
Functions of the System Management Console Functions of the System Console Software (SCS) Activating the console window of partitions Proceed as follows to open the console window: Activating from the menu 1. Select a partition from the host browser (RC2000). 2. Select [Connect] from the Execute menu. The console window of the partition selected in the host browser is then displayed. Activating with a double-click Double-click the partition in the host browser.
Functions of the System Console Software (SCS) 4.3.2.1 Functions of the System Management Console OBP OBP mode only applies to one partition. It is used, for instance, to perform an offline backup. After a partition is switched on or reset, a POST sequence (POST = Power On Self Test) is started. This tests the hardware and checks the hardware configuration. The OBP (OBP = OpenBootTM PROM) is then called up. This checks the PCI devices.
Functions of the System Management Console Functions of the System Console Software (SCS) OBP commands OBP help function {0} ok help A help text on the individual commands is output: {0} ok help go boot boot printenv setenv devalias devalias show-devs Many Other commands are available.
Functions of the System Console Software (SCS) Functions of the System Management Console Diagnostics routines probe-scsi probe-scsi-all Probes SCSI devices on the first SCSI controller Probes SCSI devices on all SCSI controllers Show commands show-post-results show-devs show-disks show-tapes show-nets Show POST result Show all installed devices (including hardware path) Show path of disks Show path of tape devices Show path of networks Showing/setting aliases devalias devalias nvalias <
Functions of the System Management Console 4.3.2.2 Functions of the System Console Software (SCS) Starting Solaris Enter the following command in OBP mode: {0} ok boot disk disk here is the alias of the boot disk. The full command with the physical device name of the boot disk would be, for instance: {0} ok boot /pci@8c,2000/scsi@1/disk@1,0:a Sequence of the boot operation: {0} ok boot ... Boot programs Kernel initialization OBP reads the first 16 blocks from the root disk to load the bootblk program.
Functions of the System Console Software (SCS) Functions of the System Management Console 4.3.3 Monitoring messages If the system console detects a server error, an error message is displayed in the window Monitoring Messages.
Functions of the System Management Console Time synchronization between SMC and partitions 4.4 Time synchronization between SMC and the partitions All instances running on an SX server have their own separate time management system, but all use the same time. This affects: ● The System Management Console ● All partitions (BS2000 and, optionally, Solaris) ● The optional SKP-SR This also applies to the SX series entry-level models (see section “Time cluster with external time servers” on page 131).
Time synchronization between SMC and partitions Functions of the System Management Console The configuration of the SMC as an NTP server and of the partitions as NTP clients as supplied is described below. If an external timer (with an official time reference, i.e. stratum 1) is used, the configuration of the SMC must be changed, so that it operates in addition to its task as an NTP server for the partitions as an NTP client of this external timer.
Functions of the System Management Console Time synchronization between SMC and partitions If the time of the System Management Console is more than 1000 seonds ahead of or behind the time of a partition the time cannot be automatically synchronized via NTP (start of the NTP daemon of the partitions or of the NTP client is suppressed). In this case the times must be synchronized manually. Information on manual time synchronization is provided in the manual “System Console Software User’s Guide (SCS)” [7].
Time synchronization between SMC and partitions Functions of the System Management Console Meaning of the values in the entry: – – – – – – – – Name or address of the peer Reference ID (0.0.0.
Functions of the System Management Console Backing up/restoring the SMC 4.5 Backing up/restoring the SMC If you create data backups at regular intervals, you can restore your data easily in the event of a system crash. The following sections describe the procedures for creating backups and explain which data types must be backed up. A DAT drive is available to the SMC for storing the backed up data.
Backing up/restoring the SMC Functions of the System Management Console 4.5.1 SCS configuration data This section describes how to back up and restore the SCS configuration data. 4.5.1.1 Backing up the configuration data of the System Console Software (SCS) A backup of the configuration data of the System Console Software is of benefit if you wish to replace an incorrect configuration setting with the old configuration. The System Console Software includes the commands needed to create the backup.
Functions of the System Management Console Backing up/restoring the SMC 5. Insert the data cartridge containing the backed up configuration data in the DAT drive. Check beforehand that the data cartridge is write-protected, i.e. that the write protection tab is set at “writeable”. 6. Enter the following command to start restoring the configuration data: SMC# /opt/FJSVscsl/bin/scslrestore -t /dev/rmt/0 7.
Backing up/restoring the SMC Functions of the System Management Console 4.5.2 System drive 4.5.2.1 Backing up the system drive of the SMC This section describes how to back up offline. When the system drive is backed up, all data saved on the hard disks which are installed in the SMC is transferred onto DAT data cartridges. With this procedure, you can back up the data stored on all hard disks.
Functions of the System Management Console Backing up/restoring the SMC 6. When a prompt appears, enter the command format. The system disks available for selection are offered. Example #format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t0d0 /pci@1f,0/pci@1,1/ide@3/dad@0,0 Specify disk (enter its number): Enter the number of the required system disk (in the example 0 for c0t0d0). Close the menu with q (quit). 7.
Backing up/restoring the SMC 4.5.2.2 Functions of the System Management Console Restoring the system drive of the SMC To restore the system drive, you will need: – The DDS4 data cartridges (150 m) with the backed up data of the system drive – The CD-ROM (1 of 2) with the Solaris software for the SMC ! WARNING! The restore procedure explained below should only be carried out by a qualified service engineer. Proceed as follows to restore the system drive: 1. Log on at the SMC as root. 2.
Functions of the System Management Console Backing up/restoring the SMC 7. When a prompt appears, start the restore process by entering the following command: SMC# dd if=/dev/rmt/0 of=/dev/rdsk/c0t0d0s2 bs=1024k When you enter this command, ensure that the value of the bs option (buffer size) is identical to the value used when the backup was created. The restore process for the 8 GB hard disk drive takes approximately one hour. The larger the hard disk capacity, the longer the restore process will take.
Backing up/restoring the SMC Functions of the System Management Console 4.5.3 Configuration data of the CDE interface All settings of the CDE interface for a login are located in the home directory of the user in the subdirectory .dt.
Functions of the System Management Console Backing up/restoring the SMC To include further configuration data with the command scslbackup, proceed as follows: – A new directory must be created in the directory /etc/opt/FJSVscsl/backup (any name, e.g. CDEbackup). – A file with the name printlist must be created in this directory, containing all file names to be saved. As it is too time-consuming to create this manually, the file is created via the script prebackup.
Backing up/restoring the SMC Functions of the System Management Console Backing up and restoring manually If the data is written to a separate DAT tape from the SCS management data, this can be done using the procedure above and the following additional commands: # tar cf /tmp/cde.tar -I /etc/opt/FJSVscsl/backup/CDEbackup/printlist # tar cf /dev/rmt/0 /tmp/cde.tar # rm /tmp/cde.tar The data is restored with the following commands: # tar xf /dev/rmt/0 /tmp/cde.tar # tar xf /tmp/cde.tar # rm /tmp/cde.
Functions of the System Management Console Backing up/restoring systems in the partitions 4.6 Backing up/restoring systems in the partitions This section describes the procedures for backing up and restoring data for the disk on which the operating system of a partition is located (referred to hereafter as the “system disk”). i In BS2000 partitions, use the PSR tool under Tools in PRIMEPOWER ServerView for a convenient backup/restoration of system disks in live operation (see page 218).
Backing up/restoring systems in the partitions Functions of the System Management Console 4.6.2 Data backup This description assumes a system disk of a partition which is backed up using a tape device (DAT drive) which is connected to the system console (SMC). Backing up a file system A file system is backed up with the command ufsdump. The following description shows how the file system is backed up on the tape device of the SMC with ufsdump. Preparations 1.
Functions of the System Management Console Backing up/restoring systems in the partitions Procedure 1. In the partition which is to carry out the data backup the Solaris operating system is now started via the network from the system console: {0} ok boot -s Here is the alias name of the system console LAN controller. The alias names can be checked in OBP using devalias. As of the SX140 model series the alias names net and obp-net can be used by default.
Backing up/restoring systems in the partitions Functions of the System Management Console Example using the Secure Shell Back up local file system /mnt on the tape device of the SMC: # ufsdump 0cf - /mnt | ssh root@ "dd of=/dev/rmt/0 bs=64k" 10. Note the tape number, status, date, system name and file system name on tape labels for every tape and attach these to the relevant tapes. 11.
Functions of the System Management Console – Backing up/restoring systems in the partitions Add the partition name and root to the file /.rhosts of the SMC. As an alternative, keys can be used in the framework of the Secure Shell. Example: root Procedure 1.
Backing up/restoring systems in the partitions Functions of the System Management Console Example Back up local files /dev/dsk/c0t0d0s1 on the tape device of the SMC.
Functions of the System Management Console Backing up/restoring systems in the partitions 4.6.3 Recovery This description assumes a system disk which is restored from a tape device (DAT drive) which is connected to the system console (SMC). Restoring a file system A file system is restored with the command ufsrestore. The following description shows how the file system is restored from the remote tape device of the SMC with ufsrestore. Preparations 1.
Backing up/restoring systems in the partitions Functions of the System Management Console 6. Switch to the temporary mount point: Example: # cd /mnt 7. Secure the tape against write access and insert it in the tape device. 8. Restore the file system from the remote tape device with the command ufsrestore.
Functions of the System Management Console Backing up/restoring systems in the partitions 4. Restart the system: # /usr/sbin/shutdown -y -g0 -i6 Restoring a disk A disk is restored with the command dd. The following describes how data can be restored with the commands dd and rsh (or ssh if the Secure Shell is used). Preparations 1. Enlist the server name and root which execute the restore process in the file /.rhosts of the system console and permit remote access.
Backing up/restoring systems in the partitions Functions of the System Management Console 6. Restore the files from the remote tape device with the commands dd and rsh (or ssh if the Secure Shell is used).
Functions of the System Management Console XSCF 4.7 XSCF 4.7.1 Functionality of XSCF As of the SX150 model series the System Management Console (SMC) on the basis of a PRIMEPOWER250 system is equipped with the Extended System Control Facility (XSCF). XSCF is a system monitoring and control facility which runs on its own processors in the SMC and offers a user interface as long as it is connected to the power cables of the SMC. The options of XSCF can be used on SX systems as of the SX150 model series.
XSCF Functions of the System Management Console 4.7.2 Access options to XSCF The table below provides an overview of the various access options to XSCF. Function Description XSCF Shell – – – Monitors the server. The status of the server can be checked. Server power can be controlled from a remote server Displays the server configuration. The internal configuration of the server can be checked.
Functions of the System Management Console XSCF 4.7.
XSCF Functions of the System Management Console Configuration of XSCF comprises the following steps: 120 ● Network Configuration (mandatory): Definition of the access from XSCF to the network (IP address, XSCF host name, subnet mask, name server, etc.) ● User Account Administration (mandatory): For access to the XSCF shell separate access IDs must be created in XSCF to which a different scope of commands can be made available depending on the group affiliation.
Functions of the System Management Console XSCF 4.7.4 Accesses to XSCF Access to the XSCF shell The connection to the XSCF shell is, for example, set up using Exceed (see the section “Configuration and operation” on page 135) via Telnet port 8010 or SSH port 8810. In this case the last error message is output. At any one time only one connection with write authorization is possible via the LAN or serial port.
XSCF Functions of the System Management Console The help entry requests an overview of the commands of the XSCF shell: Figure 43: Overview of the commands of the XSCF shell Access to the console The remote connection to the XSCF console with write authorization is carried out using, for example, Exceed via Telnet port 23 or SSH port 22. At any one time only one connection with write authorization is possible via the LAN or serial port.
Functions of the System Management Console XSCF Access via Web browser Access to XSCF is implemented in the Web browser at URL https://. The XSCF host name was defined when XSCF was configured. XSCF is assigned a separate network connection with a separate network address and a separate host name. Network access to the SMC is not affected by this. After login an initial screen appears on which the XSCF function can be selected.
XSCF 124 Functions of the System Management Console U41272-J-Z385-3-76
5 Functions of the SX server entry-level models 5.1 Switching on/off functions The SX server entry-level models are switched on and off via the power button on the control panel of the system unit: Ê To switch on, press the power button once. The X2000 carrier system (in the normal setting of the mode selection switch to LOCK) and the operating system BS2000/OSD for activated automatic IPL (see “BS2 KVP” on page 215) are then loaded. Ê To switch off, press the power button twice in succession.
Machine Administration menu Functions of the SX server entry-level models 5.2 Machine Administration menu The machine administration menu is an application in the X2000 carrier system environment. This menu is used for server system operation and maintenance. To call the function in an SX server entry-level model, see also the section “Machine Administration Menu (for entry-level models only)” on page 39 and section “Calling terminal instances” on page 40.
Functions of the SX server entry-level models Machine Administration menu The following screen is displayed: Figure 44: Machine Administration Menu Setting Monitoring Notification Information You can now set the menu as follows: – – Ê Display error messages on the system console (activated as default) Notify the system administrator by e-Mail Establish whether the system administrator is to be notified by e-mail.
Machine Administration menu Functions of the SX server entry-level models 5.2.2 Timed switching on/off of the server The automatic power control system (APCS) automatically switches the server on or off – based on a number of switching on/off schedule entries.These entries form the system schedule. When the server is switched on, the X2000 carrier system is automatically started if the mode selection switch of the system is in the LOCK position (normal mode) (see SX100 Operating Manual [2].
Functions of the SX server entry-level models Integrated console 5.3 Integrated console To use the integrated console, open the rack door and pull out the drawer with the TFT monitor and keyboard. Fold the monitor into the upright position and switch on. When the monitor is in the upright position it is not possible to push in the drawer. i The rack console has two main functions: – When the system is switched on/off the messages from the Solaris carrier system with X2000 can be monitored.
LAN console and RCA Functions of the SX server entry-level models 5.4 LAN console and RCA The operation of the SX server entry-level models via the LAN console and remote communication adapter (RCA) is similar to that of SX servers with SMC. The main difference is in the software used to operate the physical consoles of the system units. The LAN console software xscon for making a connection to the physical console of the SX server entry-level model is installed on the LAN console.
Functions of the SX server entry-level models Time cluster with external time servers 5.5 Time cluster with external time servers In principle, the use of an external time server in BS2000 is not necessary because BS2000 is automatically synchronized with the Solaris time of the X2000 carrier system. When requirements relating to accuracy of the time reference used are tightened, however, the use of an external timer for X2000 is recommended.
Time cluster with external time servers 132 Functions of the SX server entry-level models U41272-J-Z385-3-76
6 Remote operation via PC An SX server is operated centrally via the System Management Console (SMC) or via the integrated console or LAN console. In order to enable separate operation outside the computer center, the user interface of the current console must be made available to the center. This is done via PCs with a LAN connection to the current console (and, where necessary, the server partitions); the PCs have access to the system user interface via an X server.
Recommended hardware and software configuration Remote operation via PC Operating system A PC based on Microsoft Windows® is recommended for operating the SX server. Windows 95, 98, ME, 2000, NT 4.0 and XP are supported as operating systems. No particular version is recommended at this point because the strategy of the customer cannot generally be considered here. Software products The software products mentioned below support the current Windows versions quoted.
Remote operation via PC Configuration and operation 6.2 Configuration and operation This section describes the configuration and operation of Exceed, PRIMEPOWER ServerView, SINIX-TE and the 9750 terminal emulation. Exceed The configuration of the Exceed X server is described below. The X server is used to access the CDE user interface of the current console. The X server is configured using the Xconfig program.
Configuration and operation Remote operation via PC You must make the following entries in the program window: 1. Select Network and Communication. The following window will open: Figure 46: Xconfig: Network and Communication window You make the following entries in this window: Ê Mode = XDMCP-query Ê Display Number = 0 Next, click the Configure... button next to Mode.
Remote operation via PC Configuration and operation Click the OK button or the Validate and Apply Changes button to confirm your entries. Click the OK button to return to the main menu. You have now completed the basic configuration for console access. 2. Optional: Select Display and Video Display and Video can be started in the main menu optional.
Configuration and operation Remote operation via PC This possibility can be restricted to certain servers (only the SMC, the partitions of the SX server, the SKP-SR and the entry-level model). To do this, you must select File under Host Access Control List and edit the file xhosts.txt. In this file, you should enter the server names or IP addresses of servers which are to be authorized to display windows on the X server: Figure 50: Xconfig: Editor Exceed is now fully configured.
Remote operation via PC Configuration and operation After the start screen has been displayed, you see the login screen for the System Management Console: Figure 52: CDE login screen After you have logged in, you can use the CDE desktop in exactly the same way as at the console: Figure 53: CDE desktop after login U41272-J-Z385-3-76 139
Configuration and operation Remote operation via PC PRIMEPOWER ServerView Suite When the PRIMEPOWER ServerView Suite is started, after the user interface is loaded first of all the name of the Management Server is queried on which the PRIMEPOWER ServerView Suite is to be started, and also the user ID with the associated password. You are informed if further applications for PRIMEPOWER ServerView Suite are available for downloading on the server. You are recommended to install these now.
Remote operation via PC Configuration and operation Wherever possible Java Web Start always loads the application from the cache and at the same time performs a background check on the server for updates. If there are updates, the user is informed in a window and the update is automatically loaded at the time of the next start. i You will find more information on operating PRIMEPOWER ServerView in the manual “PRIMEPOWER ServerView Suite V2.2 – System Administration within a Domain” [5]. 3.
Configuration and operation Remote operation via PC SINIX-TE Optional it is possible to use an emulation keyboard to facilitate the operation of the BS2000 dialog functions. It is necessary to run an appropriate terminal emulation to support this keyboard. We recommend that you use SINIX-TE to emulate a 97801 terminal. However, SINIX-TE cannot be deployed in combination with the Secure Shell. To configure the BS2000 dialog, you must use the predefined X2000 login em9750 in the BS2000 partitions.
Remote operation via PC Configuration and operation After you have clicked OK to confirm, the selected connection is opened. Once the connection has been tested to ensure that the server name/IP address has been entered correctly you can save the connection. To do this, open the File menu and select Save as…. You must now enter a file name, which should preferably mirror the connection's server name. In future, you can reactivate the connection without entering this data by choosing File -> Open.
Access with Secure Shell Remote operation via PC 6.3 Access with Secure Shell If you wish to use Secure Shell (SSH) to access SX servers you will first have to make some preparations on the server and client sides. These preparations include installing and configuring the openSSH software on the server side (on the SMC and the partitions).
Remote operation via PC Access with Secure Shell Ê To install the patch 112438-01 first of all check whether it is already installed (using patchadd -p | grep 112438-01). If it is not installed, switch over to the directory /cdrom/cdrom0/products and install the patch using patchadd 112438-01. When you have installed the patch, reboot the system with init 6. Ê To install openSSH, switch over to the directory /cdrom/cdrom0 and call up the graphical installation program with /installer_Open_Software.
Access with Secure Shell Remote operation via PC 6.3.2 Configuring the OpenSSH daemon Before you can use the software just installed you must configure the ssh daemon for X11 forwarding.
Remote operation via PC Access with Secure Shell 6.3.3 Configuring the PC client side Once all the server side preparations for the use of Secure Shell have been completed, the next step is to prepare the administration PC so that the X server can be controlled by Exceed via the Secure Shell protocol.We recommend that you use the PuTTY1 terminal emulator software to build an X11 tunnel or a port forwarding.
Access with Secure Shell Remote operation via PC PuTTY This section describes how to configure PuTTY in order to build an X tunnel to the server and to start the user interface from the server. In the first window which appears when you start PuTTY, enter the server name and the protocol to be used (in this case SSH).
Remote operation via PC Access with Secure Shell Under Category Connection, set the user ID and the terminal type to be used for the PuTTY terminal emulation. Figure 57: PuTTY Configuration: Connection In Category Connection -> SSH, enter the command to start the CDE user interface.
Access with Secure Shell Remote operation via PC In Category Connection -> SSH -> Tunnels, configure the X tunnel and the local DISPLAY to be used. Figure 59: PuTTY Configuration: Tunnels If logon to the server is to be key-protected rather than password-protected, you should set Category Connection -> SSH -> Auth. This will ensure that the key required is generated beforehand and that the public key is set on the server.
Remote operation via PC Access with Secure Shell Once you have completed the connection settings, you can save them in Category Session with -> Save. Figure 60: PuTTY Configuration: Save 6.3.3.2 Using Exceed via Secure Shell 1. Call Exceed to start the X server. 2. Call PuTTY and start the pre-configured connection to the server (double-click on the entry for the connection required). 3.
Access with Secure Shell Remote operation via PC The user interface is similar to the one displayed during operation without Secure Shell (see chapter “Functions of the Solaris-CDE interface” on page 27).
Remote operation via PC Key management for Secure Shell 6.4 Key management for Secure Shell 6.4.1 Generating the keys In SSH authentication and encryption are based on the asymmetrical system of public and private keys. Encryption and decryption are performed with different keys, and it is not possible to derive the key for decryption from that for encryption. For this purpose the user generates a pair consisting of a public and a private key.
Key management for Secure Shell Remote operation via PC Generating the keys Variaous algorithms are available for generating such key pairs. The most familiar are RSA and DSA. In Solaris they can be generated by calling the ssh-keygen command (see http://www.openssh.com). The generation of RSA keys in SSH protocol version 2 is recommended. The minimum key length is 512 bits. 1024 bits are generally regarded as sufficient.
Remote operation via PC Key management for Secure Shell There is no way you can recover a lost pass phrase. If you have lost one, a new key pair must be generated and its public key must be distributed to the communications partners. 6.4.2 Use of SSH agents Use of an SSH agent means that it is not necessary to type in the pass phrase (which is normally long and complex) each time you call the ssh program.
Key management for Secure Shell Remote operation via PC These output commands of the ssh-agent program can be executed using the eval command. When doing so please take into account the reverse quotes (`): eval `ssh-agent ...` The eval command instructs the shell to let the ssh-agent command run and to execute the commands generated by it. Afterward the shell variables SSH_AUTH_SOCK and SSH_AGENT_PID are available. After the eval `ssh-agent` command has been executed the PID of the SSH agent is output.
Remote operation via PC Key management for Secure Shell 6.4.3 PuTTY with PuTTYgen and Pageant This section describes the generation of key pairs and the distribution of the public keys using PuTTY1. PuTTY is a free implementation of Telnet and Secure Shell for Win32 and Unix System-based platforms and is useful in dialog mode.
Key management for Secure Shell Remote operation via PC Authentication agent Pageant PuTTY's authentication agent Pageant1 contains the encrypted private keys in the memory and, as required, generates signatures or deals with the authentication procedure. At the beginning of a Windows session you start Pageant. If you then click on the Pageant icon with the right mouse button a menu opens.
7 Operating BS2000 instances 7.1 Starting BS2000 To start BS2000, you will first need a BS2000 console screen (see the following section “Accessing BS2000 console mode”). When the status bar appears in the first line, use the [F2] key to branch into the Main KVP Function Menu (see page 164). Select SVP commands (see page 169). Now you can select IPL - start BS2000 .
BS2000 console mode Operating BS2000 instances 7.2.1 Accessing BS2000 console mode For the console inputs/outputs you require a KVP. You will find an overview of its configuration in the section “Functions” on page 210. However, the KVP is only responsible for controlling the I/O traffic between X2000 and BS2000. You require the BS2000 console mode described here to display the inputs/outputs.
Operating BS2000 instances BS2000 console mode Click on the relevant icon on the front panel of the CDE interface to automatically open a window in which the functionality of the BS2000 console will be available after authorization (log in with the X2000 login cons0..7) (see also section “Calling terminal instances” on page 40).
BS2000 console mode Operating BS2000 instances Working with terminal type bs2console If you intend working with a light background you must use a different color scheme. Emergency messages/queries: Messages/inputs: KVP messages: red normal normal underlined You are recommended to activate this color scheme via terminal type bs2console.
Operating BS2000 instances BS2000 console mode Protecting access to BS2000 console mode Access to BS2000 console mode is protected as follows: If you log on dynamically, the Solaris welcome screen automatically asks you to enter a valid password. – If the Solaris login has been locked, access to the console is canceled. The login must then first be released using the Solaris user administration (see section “User and group administration” on page 330 and “BS2 Users” on page 211).
BS2000 console mode Operating BS2000 instances Assigning a KVP ID IPL mnemonic console name X2000 ensures that a BS2000 console always exists, even when no-one has opened a BS2000 console screen. The relevant background process always runs under the KVP ID CONS0. The mnemonic console name belonging to CONS0 is then always registered with the BS2000 system as an IPL console. The background process does not respond to any queries.
Operating BS2000 instances BS2000 console mode Use the functions Ë and Ê to select one of the following functions. When you have selected the function, start the function with [ENTER]: 1 – Permit Input You can permit input again. The valid password will be requested. If you supply an incorrect password, the system will wait for approximately 6 seconds. This prevents an automated trial and error attack. 2 – Inhibit Input You can lock your screen against unauthorized inputs.
BS2000 console mode Operating BS2000 instances 5 – Programmable Function Keys You can use this function to call up a menu to edit P keys or F keys: 1 Show Auto Load Unload Edit Delete - Programmable Function Keys View PFKey Files and Contents Start/Stop Automatic Loading of PFKeys Load PFKeys from File Unload PFKeys Create/Update PFKey File Delete PFKeys File(s) A maximum of 14 programmable function keys (P keys or F keys) can be assigned (P7 - P20).
Operating BS2000 instances BS2000 console mode There are two options: – the “start” option: 3 Programmable Function Keys: Options Automatically Load PFKeys start The “start” option immediately loads and activates the selected PFKeys for this session. A restart automatically loads and activates them for all other consoles with the same user ID. This function is only executed for consoles with the same user ID as the console which calls it. A note (-> auto_load.
BS2000 console mode Operating BS2000 instances A rudimentary FMLI editor is available. Another X2000 editor can also be used for longer or more complex processing.
Operating BS2000 instances BS2000 console mode 6 – SVP Commands Selecting this option opens a window in which you can call SVP commands: 1 ipl dipl vipl vmmr iohdump iosdump chinit iorsf param - SVP Commands start BS2000 start BS2000 dump IPL start VM2000 VM monitor restart dump IOH memory dump IOS memory channel initialization report iorsf files report actual default parameters for IPL At the SVP commands ipl, dipl and vipl you can specify a system name for BS2000 in the questionnaires.
BS2000 console mode Operating BS2000 instances Clear BS2000 memory [y|n]: y Clear BS2000 memory n Do not clear BS2000 memory The form is sent by pressing [SAVE]. When the IPL has been started, the console screen is automatically activated. Messages may be output which provide information on the state of the computer or on errors which may have occurred. If the IPL was executed correctly, a message is output with the message code SVR0001 (see page 344): IPL OK.
Operating BS2000 instances BS2000 console mode dipl – start BS2000 dump IPL A form is opened to start BS2000: 2 start BS2000 dump IPL IPL load device: consol device: IORSF level: IPL parameter [d|u]: clear BS2000 memory [y|n]: IPL parameter [d|u]: D1 Z0 d n d SLED startup (default) u UNLOCK 1 For further information, see the command “ipl – Start BS2000” on page 169.
BS2000 console mode Operating BS2000 instances iohdump – dump IOH memory This command creates an IOHDUMP in the directory /var/opt/SMAW/X2000/dump. Name of the file: RMA_R... If no abend code is available, SLD000 is used. The number of IOHDUMPs is limited to ten. When the maximum number has been reached, the oldest file in the directory /var/opt/SMAW/X2000/dump is deleted.
Operating BS2000 instances BS2000 console mode 7 – KVP Administrative Functions A window with the following functions appears: 2 1 2 3 KVP Administrative functions - show / print logging files - create a new logging file - KVP control functions Ê Select the required function. Then press [ENTER] (F3). ● Show/print the logging files The window “System choice” is opened: 5 System choice system HV0 system VM2 Select a system.
BS2000 console mode Operating BS2000 instances – Start time/end time By default, the times of the first and last entries of the logging file are shown. You can specify a shorter time period by entering other times within the specified time frame. The logging file is then filtered by this time period. – Print or show You can specify whether the logging file is to be shown or printed with [CHOICES]. If “Show” is set, press [SAVE] to display the logging file using the tool pg (see below).
Operating BS2000 instances – BS2000 console mode Printer [CHOICES] opens a window in which you can select a printer. If only a small number of printers are available, no new window is opened. In this case, the name of a printer is entered directly in the form. By repeatedly pressing [CHOICES], you can select the required printer. The logging file is then printed on this printer or placed in the queue for this printer.
BS2000 console mode Operating BS2000 instances ● Create a new logging file This function creates a new logging file. The old file is then closed. ● KVP control functions The window “System choice” is opened: 3 System choice system HV0 system VM2 Ê Select a system.
Operating BS2000 instances – BS2000 console mode Show-log – Show logging options You can display the currently valid logging options and the archiving command with this function. When you have selected the function, the information window “Show logging options” appears: 6 LOGGING OPTIONS: Show logging options Virtual machine: Logging requirement: REQUESTED Size of file: 1000000 Bytes Max.
BS2000 console mode Operating BS2000 instances 7.2.3 Structure of the KVP screen The screen is divided as follows in the BS2000 console mode: Line 1 KVP status line Lines 2-24 Dialog area (for dtterm: 2 - n) Line 25 Status line of the operator terminal (for dtterm, this bar is omitted) SYS HV0 CONS0 C0 daphneADM 2005-03-15 11:53 +XAAD-000.114740 SYSTEM: HOST-NAME = *NONE +XAAD-000.114740 SYSTEM-TIMEZONE = +01:00 +XAAD-000.114740 PARAMETER: SEASON = W +XAAD-000.
Operating BS2000 instances BS2000 console mode KVP status line In line 1, the KVP outputs status information. The status line has the following structure: SYS Name User mn Host yyyy-mm-dd hh:mm KVP message INS 1 2 4 6 8 9 No. Meaning 1 Partner SYS (BS2000/OSD) All inputs are sent to the system which is currently running.
BS2000 console mode Operating BS2000 instances 7.2.4 Inputs KVP supports 97801 and dtterm terminals. A BS2000 operator terminal normally operates in output mode. Press a character key to switch to input mode. The cursor is positioned in the input line (line 24 on the screen). If the input line is not large enough, additional input lines are made available. The maximum input length is 256 characters.
Operating BS2000 instances BS2000 console mode 7.2.5 Outputs Outputs are made in the roll-up area (lines 2 through 23 on the screen, for dtterm 2 through n) in the order in which they arrive. You can switch to input mode at any time. Any outputs will then be blocked and output later. If necessary, the output can be stopped on screen with the key combination [CTRL] [S] and then continued with [CTRL] [Q].
EM9750 mode Operating BS2000 instances 7.3 EM9750 mode EM9750 mode makes the local BS2000 system available to you. You can also connect to a BS2000 partner computer. In this case, the communication software of your computer must be configured and loaded. You can work with the BS2000 software which is available (utilities, application programs) in this operating mode. Log in under em9750.
Operating BS2000 instances ● EM9750 mode BS2000 dialog window using SINIX-TE on an administration PC (not possible when the Secure Shell is used) If SINIX-TE is used on the administration PC to display 97801 windows (especially to support Fujitsu Siemens emulation keyboards for BS2000), a corresponding session must be set up to the X2000 of a BS2000 partition by specifying the login em9750.
EM9750 mode ● Operating BS2000 instances List This function outputs a numbered list of pre-defined connections. The required connection is selected by positioning the cursor and pressing the key [CONNECT] (F3). If more pre-defined connections are available than are displayed, a further list is output by pressing the key [n]. The description of how connections can be pre-defined for a user is given in manual “EMDS (SINIX)” [23].
Operating BS2000 instances EM9750 mode You only need to enter the partner in the field “(N5) Personal Name”. Complete the entry with and press the key [CONNECT](F3). The name of the partner must previously have been defined in TNSX (see the manual “CMX V5.1 (Solaris)” [24]).
EM9750 mode Operating BS2000 instances Notes on operation when the emulation is running ● The complete range of functions of the EM9750 emulation is described in the manual “EMDS (SINIX)” [23]. ● The terminal emulation used here is the same as the “Terminal emulation for the alphanumeric workstation” described in that manual. Assignment of the function keys The assignment of the function keys is also described in the manual “EMDS (SINIX)” [23] and may differ according to the terminal emulation used. 1.
Operating BS2000 instances EM9750 mode EMDS function Key (sequence) ... EM1...EM9 ESC e 1 HC ESC h c SC ESC s c ESC e 9 Table 7: MF-II-special key assignments (EMDS) – The EMDS functions EM1 to EM9 perform a change to the relevant terminal emulation. – The EMDS function HC generates a copy of the entire screen via the printing program assigned to the function LA1. – The EMDS function SC generates a screen copy from the write mark onwards. 2.
EM9750 mode Operating BS2000 instances Configuring the 9750 emulation Should additional administration of the terminal stations be necessary, the program emadmin can be used (call under root, see the manual “EMDS (SINIX)” [23]). You should note that the user name of the terminal is re-generated at each call.
Operating BS2000 instances EM9750 mode 7.3.2 BS2000 $DIALOG mode If you wish to work in $DIALOG mode, you must establish a connection to the $DIALOG partner in the target computer. Select the relevant function from the menu to control the connection. The $DIALOG partner of the local BS2000 system is normally preset as the standard partner. You can connect to the local BS2000 system via the name LBS20$DIALOG (LOCLAN).
EM9750 mode Operating BS2000 instances 7.3.3 BS2000 transaction processing mode If you wish to work in transaction processing mode, you must establish a connection to the required application in the target computer. To establish a connection (see page 183), select “Manual Connection” from the menu (see page 184): Ê Enter the name of the application in the field “(N5) Personal Name” (partner name in the form LBS20application). completes the entry.
Operating BS2000 instances EVENT mode 7.4 EVENT mode General Operating tasks can be carried out simply in EVENT mode. Special EVENT commands offer the option of calling up information and storing diagnostics information. Messages output in EVENT mode are listed in the section “EVENT error messages” on page 382. The Solaris system administrator can log on an EVENT screen dynamically from a Solaris shell with the command /opt/SMAW/X2000/bin/event. Otherwise, you can log on under the login event.
EVENT mode Operating BS2000 instances 7.4.1 Possible EVENT commands You can display the valid EVENT commands together with the available parameters on screen: Ê ev.? Ú 7.4.2 Querying the version numbers of the installed X2000/Solaris software You can output the version numbers of the installed X2000/Solaris software: Ê ev.infoË[Ë...][Ë-p] [Ë-f]Ú Meaning: name Name of a software package. If no name is specified, information on the installed software packages CMX and EMDS is output.
Operating BS2000 instances EVENT mode 7.4.4 MTC devices Setting an occupancy option for MTC devices You can specify that an MTC device is also to be occupied whenever the X2000 communication on BS2000 systems which can also use the device is disrupted: Ê sx.bs2mtcfetch Meaning: -f tape-MNÚ Force option -f tape-MN Mnemonic name of the MTC device For further information, see section “Occupying an MTC device when X2000 communication is disrupted” on page 239.
EVENT mode Operating BS2000 instances 7.4.6 Permitting/inhibiting input and changing a password [F2] opens a menu with operating functions: 1 1 2 3 4 - Event Function Menu Permit Input Inhibit Input Change Password Exit The current screen window of the EVENT mode is moved into the background. Any outputs are written to a buffer and output on screen after the menu window has been exited.
8 The X2000 user interface i The section “Notes on configuring PRIMEPOWER ServerView domains“ applies to SX servers with SMC (and not to the SX server entry-level models). The other sections below apply to all SX servers. The installation and operation of the graphical user interface of PRIMEPOWER ServerView are described in the manual “PRIMEPOWER ServerView Suite V2.2 – System Administration within a Domain” [5]. In this chapter we simply present an overview of the available functions.
Starting PRIMEPOWER ServerView Suite The X2000 user interface 8.2 Starting PRIMEPOWER ServerView Suite You can call PRIMEPOWER ServerView Suite in write mode or read mode. You should note that an application (e.g. VConfig or Bs2Devices) can only be called in write mode by one user in the domain at any one time. If other users want to start the same application then they will have to start it in read mode.
The X2000 user interface Starting PRIMEPOWER ServerView Suite The following screen shows calling PRIMEPOWER ServerView on the CDE interface of the SMC: Figure 65: Example: Calling PRIMEPOWER ServerView U41272-J-Z385-3-76 197
Starting PRIMEPOWER ServerView Suite The X2000 user interface Starting on the administration PC Operation via a browser, Java Web Start or PC application is explained in detail in the manual “PRIMEPOWER ServerView Suite V2.2 – System Administration within a Domain” [5]. Only brief instructions on calling are given at this point. i ● Start using the browser Ê Start your browser. Ê Enter on the URL line: http://:8883/ Ê ● Select the relevant link for read or write mode on the page.
The X2000 user interface Starting PRIMEPOWER ServerView Suite Figure 68: Java Web Start Application Manager Ê ● Start as a PC application via the PC’s start menu Ê ● Select the application and click on the “Start” button.
Starting PRIMEPOWER ServerView Suite The X2000 user interface After the PRIMEPOWER ServerView Suite has been loaded first the name of the computer on which PRIMEPOWER ServerView is to be loaded is queried, plus the user ID and the associated password. Enter the data for the SMC here. If a user ID is employed which was created for an administrator role (see the section “User groups and logins” on page 44ff), PRIMEPOWER ServerView runs with root authorization.
The X2000 user interface Privilege concept with Role-Based Access Control 8.3 Privilege concept with Role-Based Access Control The PRIMEPOWER ServerView Suite can be used with a standard user ID of the SX servers such as root, sxadmin, bs2admin or soladmin. However, a special ID without particular SCS rights can also be set up for this purpose. The procedure for setting up such a user ID is described in the section “Administration of PRIMEPOWER ServerView” on page 53.
Privilege concept with Role-Based Access Control The X2000 user interface If the RBAC feature is activated in the PRIMEPOWER ServerView Suite when the user ID is created the user ID is assigned neither access rights to the applications of the PRIMEPOWER ServerView Suite nor to the nodes of the administration domain. User IDs (with the execption of root) which have already been created at this time lose their access rights.
The X2000 user interface Privilege concept with Role-Based Access Control Figure 72: Displaying and modifying authorizations in PRIMEPOWER ServerView U41272-J-Z385-3-76 203
Privilege concept with Role-Based Access Control ● The X2000 user interface Modifying access to individual applications Ê In the Applications table mark the relevant line by clicking in the Access column. A drop-down menu with the possible access rights then appears and you can select the option you require.
The X2000 user interface X2000 BS2Devices main window 8.
X2000 BS2Devices main window The X2000 user interface Menu bar and toolbar You can choose a variety of actions via the menu bar and the toolbar. Some of the functions are context-dependent and are not always available: if an action cannot be executed in a particular context then it is grayed.
The X2000 user interface X2000 BS2Devices main window The toolbar also contains the selection configurator: Figure 75: Example selection configurator Here you can enter regular expressions to restrict the set of objects for output. Hierarchical browser The hierarchical browser helps you to navigate within an administration domain and allows you to select either the entire domain or individual computers within it.
X2000 BS2Devices main window The X2000 user interface The object list is located below the tab bar. The type and number of the attributes it contains depend on the selected tab or subtab as well as on the selections you have made in the hierarchical browser and the selection configurator in the toolbar. A subtab bar may be present in the lower display area. Whether or not this is present depends on the selected tab, as do the type and number of subtabs it contains. 8.4.1 Menu functions 8.4.1.
The X2000 user interface 8.4.1.2 X2000 BS2Devices main window Available functions Whether or not a function is available depends on a number of factors: ● Pull-down or context menu The two menus can show different functions from each other. The functions are dependent on which devices are currently highlighted (see below) and, in some cases, on which subtab has been selected (see below).
X2000 BS2Devices main window The X2000 user interface X2000-specific functions ● These functions are only available in the pull-down menu in the X2000 user interface. Figure 79: Example pull-down menu: “Volumes+Pubsets” Device-specific functions ● These functions apply to specific devices. They can only be called if one or more devices have been highlighted in the object list. These functions are available both in the pull-down menu and in the drop-down menu.
The X2000 user interface X2000 BS2Devices main window X2000 Display and modify of general system information From X2000 V2.5 onwards, the menu items Mirror, CSR and PSR are integrated in the PRIMEPOWER ServerView application Tools and can be activated from this. i Modify (A) Assign processors and main memory to the BS2000 and X2000 systems. Set the VM mode and the number of VM2000 guest systems.
X2000 BS2Devices main window 212 The X2000 user interface ● Create (Aab) Configures a BS2000 disk on a selected disk partition. A disk partition is only proposed if it is unused. This means that it is: – not configured as a BS2000 disk, – not active as Solaris partition, – not mountet as file system – not entered in the configuration file /etc/vfstab, – not active as a swap area. Only those disks can be created which were specified beforehand using the Assign disk selection statement.
The X2000 user interface X2000 BS2Devices main window Volumes+Pubsets Configuration and initialization of pubsets and private disks for use under BS2000 and BS2000 installation Different functions are available depending on the properties of the highlighted objects and the selected subtab: i Figure 82: “Volumes+Pubsets” subtab (a) (b) (c) (d) All Disks Unassigned Disks Pubsets Private Disks ● Overwrite svl lock (Gabcd) The highlighted objects are released for editing.
X2000 BS2Devices main window The X2000 user interface BS2 Tapes Configuration of BS2000 tapes The functions are offered depending on the selected subtab: – – Configured Tapes Not configured Tapes Figure 83: “BS2 Tapes” subtab The BS2000 tape devices supported are described in the online help “BS2 tapes - Creating“ (for MBKs, see also section “Magnetic tape cartridge devices” on page 232). The DVD/CDROM drive (of the SMC or entry-level model) may be used as a tape device.
The X2000 user interface X2000 BS2Devices main window BS2 KVP When the tab BS2-KVP is activated, all configured KVPs (console distribution program) are listed. The KVP is responsible for the BS2 console inputs and outputs. A KVP always consists of 2 devices (write and read path), and in the event of modifications the write path must always be clicked. A new KVP is required if an additional guest system is set up. The KVP is identified by the KVP name which consists of 3 characters.
X2000 BS2Devices main window The X2000 user interface Evaluation of shutdown (X) If Solaris is terminated for any reason, then automatically the first action performed is to terminate BS2000. You can define a command of your choice (default: /shutdown) and a maximum wait time (default: 30 minutes) in this menu.
The X2000 user interface X2000 BS2Devices main window BS2 LAN Ports List of all configured LAN ports ● Create You can configure a BS2000 LAN port. ● Modify The highlighted BS2000 LAN port is displayed and can be modified. ● Delete The highlighted LAN ports are deleted. ● Diagnostics Diagnostic information for selected LAN ports can be displayed.
X2000 BS2Devices main window The X2000 user interface 8.4.2 X2000 tools main window When you click on the X2000 - Tools button the Tools interface appears (see figure 122 on page 332): Clicking on the Tools button offers the following functional areas: Figure 85: Tools button ● Mirror (X) Prepare and configure system disk mirroring ● CSR: back up configuration data (X) Back up and restore the configuration data ● PSR: physical backup (X) PSR is a tool for the physical backup and restoring of data.
The X2000 user interface X2000 BS2Devices main window 8.4.3 Online help Button bar Tab bar Hierarchy window Help text Figure 86: Online help You can call the online help system in two ways: ● by choosing Help -> Contents in the menu ● by clicking the Help button in a window Every function window contains a Help button at the bottom right. When you click this button, the online help window opens (see figure 86).
X2000 BS2Devices main window The X2000 user interface Tab bar The Content and Index tabs are located above the left-hand display window. Depending on the selected tab, different information is displayed in the two output windows: “Contents” tab The left-hand window lists all the PRIMEPOWER ServerView Suite sections and subsections for which relevant information can be found in the online help system. Once you have clicked on the required topic, the help information is output in the help text window.
9 Global X2000 functions 9.1 BS2000 disks: Configuration and BS2000 installation 9.1.1 Internal SCSI disk This chapter explains all the steps required to operate a brand new or partitioned internal SCSI disk as a BS2000 disk. An internal SCSI disk is in principle created as a D3475-8F disk. The points below indicate the possible state of the disk and how to manage it: 1.
BS2000 disks: Configuration and BS2000 installation Global X2000 functions b) The slices on the disk can be configured individually as a BS2000 disk in the tab BS2 disks with the action Create. The format can also be changed individually with this action. ! CAUTION! An import with different formats is not possible later. 4. The slices are configured as BS2000 disks: The entry “none” is shown in the column Possible actions.
Global X2000 functions BS2000 disks: Configuration and BS2000 installation 9.1.2 Fibre Channel disks (RAID systems) Two different disk types can be created on the Fibre Channel disks (for the usage scenarios see section “Rules of usage for disks D3435 and D3475-8F” on page 230).
Mirroring of internal disks in X2000 Global X2000 functions 9.2 Mirroring of internal disks in X2000 As of X2000 V2.5 this function is offered in the Tools application of the PRIMEPOWER ServerView Suite. To increase high availability of system disks, the system disk of the SX server is mirrored. The internal disks are here mirrored with the functions provided by “Solstice Disk Suite”.
Global X2000 functions Mirroring of internal disks in X2000 9.2.1 PRIMEPOWER ServerView Suite interface Ê Click on the tab Tools. Ê Select the function Mirror in the pulldown menu Tools.
Mirroring of internal disks in X2000 Global X2000 functions This menu field has the actions required to administer a mirror boot disk: – Set up a mirror disk – Add a disk to the mirror system (page 227) – Remove a disk from the mirror system (page 227) – Switch a disk from the mirror system to “standby” (page 227) – Synchronize a standby disk (page 227). The following options are available: – Allow larger disk – Serialize resync. 9.2.1.
Global X2000 functions Mirroring of internal disks in X2000 Add a disk to the mirror system To add one or two disks, select one or two free disk and then activate them by clicking Execute change. With the Allow larger disk option disks with a larger capacity than the system disk are also offered. The action must be confirmed in a window for each disk selected. Here the disk is added and the synchronizing process started up. If the Serialize resync.
Mirroring of internal disks in X2000 Global X2000 functions 9.2.2 Error situations 9.2.2.1 Replacing a defective disk After a defective disk is replaced by the service engineer the disk must be logically removed from the mirror configuration then added to it again (see page 227). 9.2.2.2 Disk failure 2-disk configuration A 2-disk configuration will survive the failure of one disk. The error in current operation can be eliminated by replacing the defective disk (see previous section).
Global X2000 functions Additional information for disks 9.3 Additional information for disks 9.3.1 Default partitioning of the root disk There are default partitionings of the system disk already defined for Solaris installations for X2000. The table below shows the division of 36 GB and 72 GB disks: No.
Additional information for disks Global X2000 functions 9.3.2 Rules of usage for disks D3435 and D3475-8F D3475-8F ● An LUN is divided into 1-7 slices of the same size. Here the BS2000 format (KEY, NK2, NK4) may be selected and configured. The disk can be initialized via PRIMEPOWER ServerView for BS2000 operation. Where necessary an IPL-compatible BS2000 can be placed on the disk ● Only this type can be used for internal SCSI disks.
Global X2000 functions Additional information for disks 9.3.3 Change of format from disk D3435 to disk D3475-8F Change of format from D3475-8F to D3435 or from D3435 to D3475-8F: 1. The BS2000 disks in the BS2000 must first be detached. These disks must then be deconfigured (deleted) on all the X2000s by means of BS2 devices or BS2 disks (All). 2. Select the disk concerned under BS2 disks (Mconf). The disk should now be available and the action partition/import should be proposed.
Magnetic tape cartridge devices Global X2000 functions 9.4 Magnetic tape cartridge devices Multiple systems can be granted access to the same magnetic tape cartridge device in a “Storage Area Network” (SAN). Such an environment requires the connected systems to be synchronized.
Global X2000 functions Magnetic tape cartridge devices 9.4.1 Basic conditions for configuration 1. The X2000-based BS2000 systems which are able to access the MTC device in the SAN must be administered via a joint PRIMEPOWER ServerView management server (this means among other things: the DomainAdmin product of the PRIMEPOWER ServerView Suite must be installed on these systems). 2. The MTC device must possess the same device mnemonic in each BS2000 system. 3.
Magnetic tape cartridge devices Global X2000 functions 9.4.2 Configuring an MTC device There are two steps involved in configuring an MTC device in the PRIMEPOWER ServerView application Bs2Devices : 1. The MTC device must be configured as a BS2000 device at each system (= Node in PRIMEPOWER ServerView node) from which it is accessible (BS2 Tapes -> Create): Figure 89: X2000 window for configuring a BS2000 tape device The same mnemonic name must be entered at each BS2000 system.
Global X2000 functions Magnetic tape cartridge devices 2.
Magnetic tape cartridge devices i 236 Global X2000 functions Notes – You are recommended to configure devices before the BS2000 involved are started. If a device is configured while a BS2000 system is in operation, an ATTACH-DEVICE takes place automatically in this syxstem after the first step. This must be undone with a manual DETACH-DEVICE as the second step cannot be performed while the device is in the ATTACHED state.
Global X2000 functions Magnetic tape cartridge devices 9.4.3 Adding a BS2000 system after initial configuration The MTC device may not be used between the physical connection of the new system and completion of configuration. i If you subsequently want to connect an additional BS2000 system in the SAN to the MTC device then you must repeat the two steps described on page 234 in PRIMEPOWER ServerView for the new system. 1.
Magnetic tape cartridge devices Global X2000 functions Case B: X2000 not running ● In PRIMEPOWER ServerView, remove the BS2000 system from the Switched nodes box by using one of the remaining BS2000 systems. Under normal circumstances modifying the configuration in this way is only possible when the system is communicating with all the other BS2000 systems on the list in the Switched nodes box on the X2000 level. The procedure is therefore as follows: 1. Execute the EVENT command sx.
Global X2000 functions Magnetic tape cartridge devices 9.4.5 Occupying an MTC device when X2000 communication is disrupted In normal circumstances an MTC device can only be occupied by a BS2000 system for use when the BS2000 systems in the Switched nodes list can communicate with each other on the X2000 level. The EVENT command described below (see also section “MTC devices” on page 193) can be used to occupy an MTC device even when communication with one or more of the BS2000 systems is disrupted.
Magnetic tape cartridge devices Global X2000 functions 9.4.6 Displaying the occupancy status of an MTC device The following EVENT command (see also section “MTC devices” on page 193) displays the occupancy status of an MTC device for the BS2000 systems on the Switched nodes list: sx.bs2mtcfetch -l tape-MN -l List option. The status information listed below is displayed. tape-MN Mnemonic name of the BS2000 device.
Global X2000 functions Magnetic tape cartridge devices The following abnormal statuses are also reported: – disconnected or permission denied It is not possible to communicate with the BS200 system on the X2000 level. Possible causes: – X2000 is not able to respond within a set time period. – The network connection to the host is defective. – Authorization to administer the system via the PRIMEPOWER ServerView Domain Service cannot be verified. Action: Rectify the problem.
Configuring printers Global X2000 functions 9.5 Configuring printers 9.5.1 Configuring Xprint printers You configure Xprint printers in the Mercator graphical user interface. You can operate Mercator: – via the hardware console (SMC) of the SX server – via a PC with an X user interface i For information on installing and operating the Mercator graphical user interface, see the manual “Xprint Management V6.0A GUI” [22]. Xprint is a licensed product.
Global X2000 functions Configuring printers You now see the welcome screen: Figure 91: Mercator welcome screen After a few seconds the first selection screen for configuration and administration is displayed. i U41272-J-Z385-3-76 You can only perform administrative activities with Mercator if Xprint is running. If it is not, a message at the bottom of the first selection screen informs you that Xprint is not available. Remedy: Start Xprint with the command xpstart.
Configuring printers 9.5.1.2 Global X2000 functions Configuring a new printer Figure 92: Mercator configuration and administration window Ê 244 Left-click on the printer icon.
Global X2000 functions Ê Configuring printers Choose Operations -> New.
Configuring printers Ê Global X2000 functions Click Connection.
Global X2000 functions Ê Configuring printers Click Configuration. You can define the required printer type via the PCL definition: Figure 95: Mercator printer configuration window (Configuration) The table below indicates the printer type, emulation and PCL which can also be used as BS2000 spool printers or emulated TRANSDATA printers (see section “Configuring a BS2000 printer” on page 252).
Configuring printers Global X2000 functions When you click the OK button, the settings are taken over into the Xprint database and the printer is displayed in graphical form in the first selection screen.
Global X2000 functions Ê Configuring printers Double-click the icon corresponding to the new printer. This re-opens the configuration screen (State) in which you can set the printer to active. You can also make changes to the configuration.
Configuring printers Global X2000 functions After this, the printer icon is sharp and the line representing the connection is no longer broken: Figure 98: Mercator window with Xprint database (printer active) 250 U41272-J-Z385-3-76
Global X2000 functions Configuring printers 9.5.2 Configuring the SEH Printserver In SX systems, printers are connected via an adapter produced by the company SEH, the so-called SEH Printserver. This print server may take the form of a separate adapter box (e.g. a pocket adapter with type name IC105) or an integrated LAN card (e.g. in the case of the 9017 printer).
Configuring printers Global X2000 functions 9.5.3 Configuring a BS2000 printer You can create, modify or delete emulated BS2000 printers via the X2000 graphical user interface under PRIMEPOWER ServerView.
Global X2000 functions Configuring printers When you select BS2000 printer, the Create a new BS2000 printer window opens: Figure 100: X2000 window for creating a BS2000 printer Node Computer node on which the BS2000 printer is to be set up. Name Here, you specify the name of a printer which is configured in the UNIX system and which is to be used for print output by the emulation. Type The system displays the printer type corresponding to the printer entered under “Name”.
Configuring printers active Global X2000 functions If you check this box then the emulation is activated immediately. If not, the device is simply declared to the BS2000 system. i An entry is made in the SERSFILE (every minute) if the device is attached in the BS2000 system but not activated. Communication settings Only for serial device connections (not relevant for SX servers). Device node The system displays the IP address and the port number via which the printer is accessed.
Global X2000 functions Configuring printers Node Computer node on which the Transdata printer is to be set up. Name Here, you specify the name of a printer which is configured in the UNIX system and which is to be used for print output by the emulation. Type The system displays the printer type corresponding to the printer entered under “Name”. Workmode buffered: The print job is to be performed via the UNIX spool. unbuffered: The print job is to explicitly occupy the UNIX printer.
Configuring printers Global X2000 functions In the example below, a print station with the name E9017#00, operated in unbuffered mode without character conversion, is set up on the computer bari1. The UNIX printer p9017 is used as the physical device. -seh is specified in the Emulation options. This tells the printer emulation to communicate with the printer via the so-called RSO spool protocol and to use port number 2900 (print security!).
Global X2000 functions Configuring printers 9.5.4 Starting up an emulated BS2000 printer 1.
Configuring printers Global X2000 functions 9.5.5 Using printer-specific functions with the BS2000 printer type LP-EMUL The BS2000 printer type LP-EMUL can be used to operate a number of different physical printer types (needle, ink jet, band and laser printers). In order to use the special characteristics of the connected printer, it is necessary to send not only the print data itself but also the control characters (or control character sequences) designed for precisely this printer type.
Global X2000 functions Configuring printers The following commands are defined: DRAFT Sets draft mode LQ Sets letter quality PORTRAIT Sets portrait format LANDSCAPE Sets landscape format CPI=nn Sets the character width: nn = 10, 12, 15 or 17 CPI = characters per inch LAN=cs Sets a country-specific character set in the printer.
Configuring printers Global X2000 functions 9.5.6 Emulation options for controlling the X2000 printer emulation You can use the emulation options to enable certain functions in the printer emulation. Some of these are required for diagnostic purposes whereas others may be useful or necessary for operation. -seh This switch must be set if the emulation operates a printer which is connected via LAN and SEH Printserver. -trace=n The emulation's trace function is activated (n = 1/2) or deactivated (n = 0).
Global X2000 functions -lan=cs Configuring printers A country-specific character set is selected in the printer. Possible values for cs are: In As De En Da Fr It Es Ni No Sv Fi Cy -spool Standard international Standard Ascii German English Danish French Italian Spanish Dutch Norwegian Swedish Finnish Cyrillic The X2000 printer emulation makes it possible to gather the print data for a print job in a file instead of sending it to a physical printer.
Configuring printers Global X2000 functions Example script #Print data from print file via Xprint to the printer # hpljlan # Print command xpadd with parameter -cp (Xprint creates # copy of file) xpadd -dr $1 -de hpljlan -cp # Delete print data file rm $1 If multiple emulated printers are configured and these are to output their data at different physical printers then the script can be extended as follows: # Determine mnemonic name from file name # (e.g. /var/opt/SMAW/X2000/tmp/EPRINTER_L0.
Global X2000 functions Configuring printers started and the printer is activated. Printer malfunctions are detected if Xprint itself detects a printer fault or if the number of queued print jobs exceeds a user-defined value. If a fault is present or is likely due to the excessive queue length then the RESERVE-CCW is acknowledged with an equipment check error. This results in a spool error message at the BS2 console.
Local and remote communications Global X2000 functions 9.6 Local and remote communications 9.6.1 ATNS The transport system permits both local communications between the BS2000 processor (general processor) and the Solaris processor and network-wide communication via the Solaris processor. The names of the locally communicating applications are automatically set up via the ATNS functions. 9.6.1.
Global X2000 functions ● Local and remote communications BS2000 standard applications The ATNS uses the file /etc/opt/SMAW/X2000/tnsrem_data to create the TNS entries for local BS2000 standard applications. The call is issued automatically after the successful configuration of a local BS2000 communication device (LAN port).
Local and remote communications 9.6.1.2 Global X2000 functions Example of setting up a connection ● After system installation: Connections from the local X2000 system to all the BS2000 standard applications can be established via the preconfigured BS2000 communication devices. – LAN port (LOCLAN) LBS20$DIALOG must be entered as the connection partner in the EMDS.
Global X2000 functions Local and remote communications All LOCLAN connections at the X2000 use the interface SMAWLnet0. The default IP address 192.168.138.12 is assigned to this interface. Any change to the IP address for the interface SMAWLnet0 consequently affects all LOCLAN connections. i If you want to use frame sizes above the standard CSMA-CD size of 1500 bytes then you must configure BCAM accordingly: /BCOPT DEV-LPDU-SIZE-USAGE=*ON /CREATE-LINE ........ /BCACT ...
Local and remote communications 9.6.2.2 Global X2000 functions LOCLAN between guest systems Connections between the local X2000 and the local BS2000 via TCP/IP can be used by means of LOCLAN. This connection is emulated by X2000. If LOCLAN is used, the packet size may be up to 64 kbytes. Under VM2000 this connection also allows a rapid LAN connection between the guest systems and the monitor system via TCP/IP.
Global X2000 functions Local and remote communications Example of VM2 guest system Figure 103: Example of creating a new BS2000 LAN device The same applies to all other guest systems. Configuration in VM2000 The communication devices must be assigned to the appropriate guest system.
Local and remote communications Global X2000 functions The basic SOF file $TSOS.SOF.SX2000, which contains the entries for LOCLAN and LOCSIN, is shipped with the pre-installed standby system. For VM1: /DCOPT HOST=TESTVM1,... /BCOPTION BROADCAST=ON,ARP=ON /CREATE-NODE NODE-NAME=LOCLAN /CREATE-LINE LINE-NAME=LOCLAN,IP-ADDRESS=192.168.138.
Global X2000 functions 9.6.2.3 Local and remote communications ZASLAN You cannot configure any BS2000 ZASLAN device on the onboard LAN controllers hme 0, hme 1, etc. i If you use TCP/IP or ISO-LAN connections via an Ethernet cable between the local BS2000 and other systems then you should set ZASLAN. This is the only way that BS2000 can obtain a direct view of the physical network. You must also configure the ZASLAN device in the local BS2000 system. Example for IP /CREATE-NODE NODE-NAME=...
Local and remote communications Global X2000 functions BS2000 /CREATE-NODE ..... /CREATE-LINE ..... ,L2-PROTOCOL=*CSMACD(...,MAX-LPDU-SIZE=*BY-DEVICE) /CREATE-PROCESSOR ... /CREATE-ROUTE ..... ,L3-PROTOCOL=*IP(...) /BCACT ... i The following restrictions must be borne in mind when operating this configuration. All the network components (switches, routers etc.) and all terminals must be configured with this setting. This configuration is only permitted with the TCP/IP protocol.
Global X2000 functions Local and remote communications ● You must ensure that the device pairs (G4, G5) and (J4, J5) are located on different system boards. ● Meadia monitoring must be activated in X2000 (in PRIMEPOWER ServerView Suite): BS2Devices application --> BS2 LAN Ports tab --> Configuration menu item --> Monitoring tab). This ensures that the removal (or addition) of a LAN route BCAM is signaled and the connection thus retained. 9.6.
Offline PSR Global X2000 functions 9.7 Offline PSR 9.7.1 Scope of function PSR is a tool for the physical backup and restoring of data. Disks or individual slices of these disks can be written onto a backup medium and later read again from it. PSR is operated on-line via PRIMEPOWER ServerView (see section “Functions” on page 210) and off-line via a Curses-based interface. The on-line mode is described in the PRIMEPOWER ServerView help texts. This section gives a guide to the off-line mode only.
Global X2000 functions Offline PSR 9.7.2 Operation of the off-line PSR In the off-line mode PSR is operated via its own Curses-based interface. The operation runs in the English language. 9.7.2.1 Starting the off-line PSR PSR in SX entry-level models Prerequisites: The CD0 of the Solaris installation record is required for off-line operation. A tape device and a prepared PSR tape must also be available. Further tapes may possibly have to be supplied for the backup. Procedure: 1.
Offline PSR Global X2000 functions e) Start PSR off-line with the following command: /tmp/psr The procedure first sets the TERM variable for the SUN console, then calls PSR. PSR logs on with the basic menu. PSR on SX servers with SMC Prerequisites: A correctly installed SMC, with built-in DAT disk drive, is required for the off-line mode. Procedure: 1. Prepare the SMC in the on-line mode. The SMC must be modified in the PSR menu Prepare off-line PSR for the off-line mode.
Global X2000 functions 9.7.2.2 Offline PSR The basic menu PSR-X V3.0A Oct 21 2004 Physical Save & Restore Function Selection >Save Restore Copy Check Label (1) (2) Quit Use CURSOR to move, ENTER to select, CTRL c to abort (3) Figure 104: Basic menu of the off-line PSR In the left field the header (1) contains the version and date of generation of the PSR. The title of the relevant menu appears in the centre. A PSR function may be selected in the selection field (2). To leave PSR, select “Quit”.
Offline PSR 9.7.2.3 Global X2000 functions Save PSR-X V3.0A Oct 21 2004 Disks c0t0d0s0 >c0t1d0s0 Save Disk c0t1d0s0 70086.972 MB >ROOT BS2000 SWAP BS2000 Slices BACKUP BS2000 VAR BOOT Use CURSOR to move, SPACE to select, ENTER to confirm, CTRL c to abort Use TAB to skip between disk & slice menu Figure 105: Slice selection Use the “Save” function to save selected disks or slices to one or more tapes. The saving process starts with an analysis of the system and the connected disk drives.
Global X2000 functions Offline PSR After completion of the disk/slice selection, select the tape device (see figure 106). The backup can then be started. PSR-X V3.0A Oct 21 2004 Save Tape Selection: /dev/rmt/0cn Tapes IBM 3590 15GB >SEAGATE DAT 9SP Use CURSOR to move, ENTER to select, CTRL c to abort Figure 106: Selection of the tape device The backup is carried out by slices.The data is read, the CRC checksum is calculated and written onto tape.
Offline PSR 9.7.2.4 Global X2000 functions Restore Restoring a disk from the tape takes place in the same way as saving, only in the reverse order. The menu for selecting the tape device (see figure 106) is first called. After a device has been selected the tape archive is read and the menu for disk or slice selection displayed (see figure 105). The disks or slices displayed are disks for which there is a backup on the tape.
Global X2000 functions 9.7.2.5 Offline PSR Copy In the off-line mode PSR enables the disk copying; the full content of a hard disk can be copied to another hard disk. To do this, select the hard disk to be copied in the same way as you would if you were saving. This disk is referred to below as the “source disk”. The selection is made with the RETURN key because there is no sub-selection (selection of individual slices) for copying.
Offline PSR 9.7.2.6 Global X2000 functions Check Unlike Restore, the Check function only checks the CRC checksum of the data read. However, there is no rewriting onto the disk. 9.7.2.7 Label The Label function is used to identify backup tapes. Every tape written by PSR is identified by a unique label consisting of the following sections: – – – – 282 a PSR-specific recognition mark, namely the character string “PSR” the PSR version with which the tape was generated (e.g. “3.0A”).
Global X2000 functions Offline PSR 9.7.3 Supported hardware PSR V3.0 can be used on all SX servers. 9.7.3.1 System type SX entry-level model Supported tape drives: Type Supported off-line Remark HP C5683A DAT yes SCSI connection MBK 9084-110 yes SCSI connection 3591 (Magstar) EF no Fibre Channel connection Supported disk drives: All disks which are released for the entry-level models of the SX series are supported in online and offline mode. 9.7.3.
Offline PSR 284 Global X2000 functions U41272-J-Z385-3-76
10 Dynamic Reconfiguration The “Dynamic Reconfiguration” (DR) functionality described in this section exists on BS2000 partitions of SX servers as of the SX150 model series, both native BS2000 and VM2000 being able to run in a BS2000 partition. Dynamic Reconfiguration of Solaris partitions is possible as already on servers of the SX130 and SX140 model series. 10.
Functional scope, concepts and applications Dynamic Reconfiguration The benefits of extended partitioning (XPAR) compared to physical partitioning (PPAR, based on the physical system board mode (PSB mode)) are as follows: ● Greater flexibility The smaller hardware granularity means that greater flexibility is achieved on the SX150 servers in the event of changing utilization of the hardware resources by the partitions.
Dynamic Reconfiguration Functional scope, concepts and applications ● DR-disconnect Disconnection of an XSB with implicit detachment (DETACH) of the CPUs and the I/O ports (exception: UHPS) in BS2000/VM2000. An XSB on which a UHPS is put into operation or on which usable memory is available cannot be removed using DR-disconnect. DR-disconnect is only accepted for an XSB which is either integrated in or assigned to the home partition.
Functional scope, concepts and applications Dynamic Reconfiguration 10.1.
Dynamic Reconfiguration Functional scope, concepts and applications CoD (Capacity on Demand) Capacity on Demand (CoD) makes additional CPU power available when required in the context of purchased licenses. This is possible on the one hand when there are extra CoD-CPUs installed on the XSBs used by the partition in addition to the CPUs purchased. On the other hand, from the SX150 model series on additional XSBs can be added dynamically to the partition and their CPUs used for CoD.
Functional scope, concepts and applications Dynamic Reconfiguration In both cases the same DR method (DR-connect) is used in order to reconnect the XSBs of the repaired or replaced system boards and thus restore the original status. It may be necessary to put the XSBs from the other partitions back into operation.
Dynamic Reconfiguration Functional scope, concepts and applications 10.1.3 The DR concept for BS2000 The DR processes in BS2000 partitions are performed at Solaris level, either from the graphical interface PRIMEPOWER ServerView or using the command interface. DR of XSBs in BS2000 partitions is supported in X2000 and BS2000/VM2000 by functions which relieve the user of many important tasks. DR-connect When an XSB is added to a partition the user’s activities are restricted to the following tasks: 1.
Functional scope, concepts and applications Dynamic Reconfiguration 4. Releasing any “extra” CPUs which are used: – In the case of native BS2000 with /DETACH-DEVICE UNIT=*EXTRA-CPU(*ALL) – In the case of VM2000 with /DETACH-VM-RESOURCE UNIT=*EXTRA-CPU(*ALL) 5. Initiating the DR process (from PRIMEPOWER ServerView or using a command).
Dynamic Reconfiguration Functional scope, concepts and applications 10.1.4 Requirements for DR With the requirements for DR a distinction is made below between the hardware and configuration requirements and the situation-dependent requirements. Hardware and configuration requirements ● Distribution of the XSBs of each partition to 2 physical system boards. The options are model-dependent (for details please also see table 17 on page 403).
Functional scope, concepts and applications ● Dynamic Reconfiguration Redundant connection of the BS2000 devices on both system boards: The XSB may not contain the only or last path to a device – in particular the home pubset must be taken into account here – which cannot be placed in the DETACHED state. This condition is satisfied in the case of a redundant hardware connection and by the use of PowerPath (see also the “PowerPath” manual [34]).
Dynamic Reconfiguration – ● Functional scope, concepts and applications In the case of DR-disconnect no “extra” CPU may be connected in BS2000/VM2000. No parallel actions Configuration measures which are performed in parallel to a DR process can prevent the DR process from running successfully. The same applies for Solaris applications which access the resources of an affected XSB in parallel to a DR process.
Functional scope, concepts and applications Dynamic Reconfiguration 10.1.5 An example of the DR scenarios In this example an SX150 server with one BS2000 and one Solaris partition and a free XSB is used.
Dynamic Reconfiguration Functional scope, concepts and applications System Board 00 CPU 2 X2 4GB 4GB PCI Slots 01234 System Board 01 BS2 BS2 M2 M2 PCI Slots 567 CPU CPU 1 2 M1 M2 PCI Slots 0123456 CPU CPU 1 2 M1 M2 PCI Slots 789 BS2 BS2 4GB 4GB PCI Slots 01234 CPU CPU 1 2 M1 M2 PCI Slots 567 SCSI Port Boot PROM SCSI Port Boot PROM SCSI Port Boot PROM SCSI Port Boot PROM SCSI Port LAN Port Console Port LAN Port Console Port LAN Port Console Port LAN Port Console Port LA
Functional scope, concepts and applications Dynamic Reconfiguration These CoD-XSBs can only be used as CPU-XSBs. To permit dynamic disconnection of the CoD-XSBs from the BS2000 partition later, no-obp-sb, no-mem-sb and no-io-sb must be set for them. For details see the section “Settings relevant to DR” on page 321. Temporary releasing of CPU performance The additional CPU performance added earlier can be released temporarily at any time by disconnecting CPUs of XSB 00-1 or by removing XSB 00-1.
Dynamic Reconfiguration Functional scope, concepts and applications 1. Temporary operation (until online maintenance) with reduced resources The entire procedure is illustrated with the figure below (CPU and memory values relate to BS2000): Normal operation 4 CPUs, 10 GB Restricted operation 1 3 CPUs, 6 GB Failure, reboot, autom.
Functional scope, concepts and applications Dynamic Reconfiguration 2. Temporary operation (until online maintenance) of theCPUs of CoD-XSB The failure of hardware resources can be compensated for in part by puting the CPUs of XSB 01-1 into operation. The entire procedure is illustrated with the figure below: Normal operation 4 CPUs, 10 GB Restricted operation 1 4 CPUs, 6 GB Failure, reboot, autom.
Dynamic Reconfiguration Functional scope, concepts and applications 3. Permanent use of all resources of the CoD-XSB The failure of hardware resources can be compensated for fully by puting XSBs 01-3 into operation with all its resources. The entire procedure is illustrated with the figure below: Normal operation 4 CPUs, 10 GB Normal operation with CoD-XSB 4 CPUs, 10 GB Failure, reboot, autom.
Functional scope, concepts and applications i Dynamic Reconfiguration Important notes – In this scenario the roles of XSBs 00-0 and 01-1 are swapped. – XSB 01-3, which was originally kept in reserve, initially remains in the partition. – The original boot-XSB 00-0 is initially not put into operation; it can take on the role of the CoD-XSB. – At the earliest when Solaris is rebooted can the initial status be restored.
Dynamic Reconfiguration Performing DR 10.2 Performing DR The sections below describe the DR interfaces of the administrative interface PRIMEPOWER ServerView and the DR command interface. These are then followed by a description of further details and constraints relating to DR. The XSB attributes “integrated” and “assigned” The status of an XSB with regard to the partitions of the SX server can be described by the independent attributes integrated and assigned.
Performing DR Dynamic Reconfiguration 10.2.1 Administrative interface PRIMEPOWER ServerView In the administrative interface PRIMEPOWER ServerView the functions required for DR are offered within the VConfig application. Creating an overview of partitions and system boards The assignment of the system boards (XSBs) to the partitions is output by activating the subtab Systemboards DR in the Boards tab of the VConfig application.
Dynamic Reconfiguration Performing DR Initiating the DR process The basic actions DR-connect and DR-disconnect are always performed in the partition for which they apply, and this independently of whether they are initiated in PRIMEPOWER ServerView within the partition or on the SMC.
Performing DR Dynamic Reconfiguration In the example below XSB 01-1 (here named Systemboard_1-1) is removed immediately (Disconnect immediatly option) and not assigned to another partition but to the pool of free XSBs. Figure 115: Removing an XSB (example) Notes ● The Disconnect at next reboot option (alternative to the Disconnect immediatly option) is the equivalent of the -reset parameter in the drc command.
Dynamic Reconfiguration Performing DR ● DR-connect integrates the XSB in this receiving partition. ● The Move action is a cross-partition action comprising one of the simple actions DR-connect and DR-disconnect and is only possible on the SMC in PRIMEPOWER ServerView. The action is started for the partition which releases the XSB.
Performing DR Dynamic Reconfiguration 10.2.2 The command interface The commands described below can only be executed under the root ID and in the partition(s) concerned. Information functions – Partitions, system boards and associated resources 1. /opt/FJSVhwr/sbin/drcstat -board [all] -xpar The drcstat command lists the system boards of the machine and their configuration statuses in the partitions (current partition, next partition after a Partition Solaris reboot).
Dynamic Reconfiguration Performing DR 2. x2prtpci [-v] The x2prtpci command lists, in compact form, the system boards, PCI bus processors (UPA bridges), PCI cards, ports on the PCI cards, and SCSI devices of the home partition. If the -v option is not specified, the list does not include ports and SCSI devices.
Performing DR Dynamic Reconfiguration Example # x2prtpci -v Please wait . . . . . . . . . danteADM(00): 00-0 (80 81) 01-1 (aa) 01-2 (cc cd) 01-3 (ee) (PCIOB#0 at Cabinet#0,SCFA#0) hme 0 /pci@80,4000/network@1,1 (SCFA#0 at Cabinet#0) glm 0 /pci@80,4000/scsi@4 FUJITSU MAP3735NC sd t0 d0 FUJITSU MAP3735NC sd t1 d0 glm 1 /pci@80,4000/scsi@4,1 (PCI#01 at Cabinet#0,SCFA#0) lpfc 0 /pci@80,4000/fibre-channel@2 (PCI#00 at Cabinet#0,SCFA#0) lpfc 1 /pci@80,2000/fibre-channel@1 EMC SYMMETRIX sd t0 d0 ...
Dynamic Reconfiguration Performing DR 3. bs2drstat [sb] The bs2drstat command lists the BS2000 resources which are lost in the partition due to DR-disconnect of the system board and specifies whether the DR-disconnect is possible from the X2000 viewpoint. If the command is called without an argument a menu for selecting the system board is offered. Example 1 CPU-XSB 01-3 can be released with DR-disconnect. # bs2drstat sb01-3 Please wait . . . . . . . . . . . . . . . .
Performing DR Dynamic Reconfiguration Action functions – Initiating the DR process /opt/FJSVhwr/sbin/drc Depending on the parameters specified, the drc command initiates DR-connect or DR-disconnect for the specified XSB.
Dynamic Reconfiguration Performing DR The -reset parameter controls immediate reconfiguration of reconfiguration via a reboot: – If the -reset parameter is not specified, the reconfiguration process is initiated immediately. – If the -reset parameter is specified, the reconfiguration process is planned for the next time Solaris is rebooted. A drc command with the -disconnect and -reset options is canceled again and reversed by a later command for the same XSB with the -connect and -reset options.
Performing DR Dynamic Reconfiguration Dialog with the user In a BS2000 partition a dialog with the user takes place when the -keep option is specified. The following question must be answered here: option is only used for system board hotswap operation. Continue ? [YES]/[NO] Trailer run and delays After the phases described above have been completed a trailer run takes place in the background in which the information about the DR process is distributed over the entire server.
Dynamic Reconfiguration Performing DR Canceling the DR lock In special situations (e.g. in the event of an abnormal shutdown procedure or SETS) BS2000/VM2000 sets a DR lock so that a SLED can be executed after shutdown.
Performing DR Dynamic Reconfiguration 10.2.4 DR runs in BS2000 DR processes are always initiated and executed at Solaris level. In BS2000/VM2000 no measures or actions are needed; the CPUs are automatically disconnected or connected in accordance with the licenses. The start and end and all BS2000 reconfiguration actions of a DR run are reported on the console in BS2000 or VM2000.
Dynamic Reconfiguration Performing DR Further information on BS2000 ● During DR CPUs are attached and detached automatically and implicitly provided the existing licenses permit this. ● CPUs which are licensed in BS2000 but are located on XSBs which are not attached at a point in time are nevertheless reported by X2000 and displayed in BS2000 with the DET(EX)/OFF status. This applies both for normal and “extra” CPUs.
Performing DR Dynamic Reconfiguration ● If a DR action is rejected by BS2000/VM2000, all configuration changes made up to then are automatically undone. Exception: Owing to the length of time it takes separate mirror disks are not resynchronized. ● If during a DR-disconnect action im BS2000 a ZASLAN device is deactivated for which automatic reactivation has been enabled (SLOW-POLL=*ON), this results in constant attempts to reactivate the device.
Dynamic Reconfiguration Performing DR ● Virtual CPUs are implicitly reconfigured by VM2000 when Dynamic Reconfiguration (attachment or detachment of real CPUs) takes place. If for a VM the number of active virtual CPUs has become greater than the number of attached real CPUs in the associated CPU pools, excess virtual CPUs are implicitly detached. By the same token detached virtual CPUs are implicitly attached if the number of attached real CPUs in the CPU pool has been increased by DR.
Performing DR Dynamic Reconfiguration Further information on MSCF As of Version 15.0 (component part of OSD/XC V2.0) HIPLEX MSCF automatically supports Dynamic Reconfiguration. This excludes the possibility of inadvertent failure detection (caused by the absence of the sign-of-life signals during DR). In terms of MSCF DR runs as follows: ● Start of Dynamic Reconfiguration The system requests the “Cluster Recovery Lock” from MSCF (console message MCS1048).
Dynamic Reconfiguration Performing DR 10.2.5 Settings relevant to DR The settings relevant to DR and hardware requirements which are described in the following are set ex works or automatically by the X2000 carrier system and need not be configured by the customer. This description is therefore only intended for information purposes and is restricted to the main aspects. OBP settings of the system board relevant to DR The following OBP settings apply per partition.
Performing DR Dynamic Reconfiguration Examples 1. Specifying a setting for 2 XSBs: eeprom no-mem-sb="01-1 01-2" 2. Resetting the setting for XSB 01-1: eeprom no-mem-sb="01-2" (The OBP parameter is supplied with a value from the Rest list.) 3.
Dynamic Reconfiguration Performing DR In the following example After reboot is set to Off for XSB 01-1 (here named Systemboard_1-1) so that the XSB is not put into operation the next time Solaris is booted. Figure 117: PRIMEPOWER ServerView: Modifying OBP settings Further settings relevant to DR ● The system boards may not be operated in (Memory) Interleave Mode. If necessary, this can be set via the Machine Administration Menu on the SMC of the SX server.
Performing DR 324 Dynamic Reconfiguration U41272-J-Z385-3-76
11 Solaris: system administration 11.1 X2000 partition 11.1.1 System settings Ê After calling PRIMEPOWER-ServerView select the VConfig application. Ê Select the required computer in the object table. Ê Select Modify.
X2000 partition Solaris: system administration A window in which you can define the system settings is displayed.
Solaris: system administration X2000 partition 11.1.2 Locale parameters Ê After calling PRIMEPOWER-ServerView select the VConfig application. Ê Select the required computer in the object table. Ê Select Modify Locale Parameters. A window in which you can define the locale parameters is displayed.
X2000 partition Solaris: system administration – – Currency notation System language In X2000, only German (de_DE.ISO8859-15) and English (en_US.ISO8859-15) are permitted as languages. The only permitted values in LC_MESSAGES are de (for German) and C (for English) and the only permitted values in LANG are de (for German) and en_US (for English).
Solaris: system administration X2000 partition 11.1.3 Recurrent tasks You are able to define tasks which have to be performed with root authorization regularly at a specified interval. A task can be a: – – – command shell procedure executable program Ê After calling PRIMEPOWER-ServerView select the Tasks application. Ê Select Create (pull-down menu only). A window in which you can define the tasks is displayed.
X2000 partition Solaris: system administration 11.1.4 User and group administration You can use this function to administer all the users and groups within the administrative domain. Call Ê After calling PRIMEPOWER-ServerView select the Users application.
Solaris: system administration Solaris partition 11.2 Solaris partition On partionable systems you can create Solaris-only partitions alongside BS2000 partitions. The Solaris operating system developed by SUN Microsystems Inc. (http://www.sun.com/Solaris) is available in full in the Solaris partition. The Solaris functions and their operation are described in the original documentation from Sun (http://www.sun.com/documentation).
PRIMEPOWER ServerView Suite application “Tools” Solaris: system administration 11.3 PRIMEPOWER ServerView Suite application “Tools” The functions “system disk mirror” (Mirror), “configuration data backup” (CSR) and “physical system disk backup” (PSR) have been removed from the PRIMEPOWER ServerView Suite application Bs2Devices for X2000 V2.5 and higher. They can now be found in the independent PRIMEPOWER ServerView Suite application Tools which can be accessed by selecting the “Tools” start button.
Solaris: system administration PRIMEPOWER ServerView Suite application “Tools” The column “CSR last action” shows the date and type (save/restore) of the last CSR action executed. If nothing has been done there are no previous actions and the column therefore shows “-----”. The column “PSR status” shows the current status of the PSR. If no PSR is running the status is “inactive”. If a PSR is running the status is “active”.
PRIMEPOWER ServerView Suite application “Tools” 334 Solaris: system administration U41272-J-Z385-3-76
12 What if ... This chapter describes what to do if a fault occurs at the system unit. It helps you to detect faults, identify their causes and, in some cases, to eliminate such malfunctions immediately. In the case of faults that can only be rectified by service staff, you can perform a preliminary diagnosis and then contact the service staff for further information. Depending on the response of the service staff, you may be able to resume system operation.
sx.diag command What if ... 12.2 sx.diag command You can use this command to generate a Solaris system dump or to activate or deactivate devices. Command call This command is issued in the EVENT screen (see section “EVENT mode” on page 191): sx.diag Call formats sx.diag No action is performed The possible input values are output. sx.diag sinixdump A Solaris system crash is immediately initiated and a dump is generated. ! CAUTION! Only issue this command in exceptional cases.
What if ... Create X2000 diagnostic documents sx.diag sinixatt An attempt is made to deactivate all the bus devices. ! CAUTION! Since all the devices have already been deactivated, there is a risk that BS2000 will crash. sx.diag sinixatt The device with this chn-no./unit-no. is activated. In the case of a dual device (with KVP/LAN), both devices are activated. A corresponding message is output. i The chn/unit-no. must be entered in hexadecimal form. Example: sx.diag sinixatt 0 3d 12.
Create an IOH/IOS dump What if ... 12.4 Create an IOH/IOS dump If an error occurs at a BS2000 device then an IOH or IOS dump can be generated. This is described on page 172 (“iohdump – dump IOH memory” and “iosdump – dump IOS memory”).
13 X2000 messages 13.1 KVP messages The messages issued by the console distribution program (KVP) in UNIX mode begin with the message code KVP. KVP0000 7.500 KVP VERSION (&00) INITIALISED ON (&01) AT (&02) &00 = KVP version number, &01 = Date, &02 = Time KVP0001 KVP PARAMETER FILE ERROR Meaning The KVP parameter file kvpparam contains a syntax error, the file no longer exists or the system has no further available storage space. 1.
KVP messages X2000 messages KVP0002 NEW KVP PARAMETER FILE ACTIVATED KVP0005 CURRENT TRANSLATION TABLES: (&00) &00 = Designation of the line code or the conversion tables Meaning The BS2000 console messages are converted from EBCDIC and ASCII and vice versa on the basis of the specified standards. The default setting is Euro/International ISO 8859-1 (ASCII) to BS2000 EBCDIC.DF.04-1 and vice versa.
X2000 messages KVP0014 KVP messages STATION (&00) REJECTED BY SYSTEM: CONSOLE (&01) IS ALREADY ASSIGNED &00 = User ID, &01 = Mnemonic name of console Meaning Another station is already logged on at the BS2000 system with the specified mnemonic console name. This mnemonic console name is not currently available. KVP0019 SYSTEM IS NOT READY FOR INPUT Meaning BS2000 is not active, the IPL has not terminated or still has to be started.
KVP messages KVP0054 X2000 messages INPUT TO (&00) REJECTED UNTIL LOGGING IS POSSIBLE &00 = Partner (SYS, SVP) Response The original error must be eliminated (see the preceding messages). You can then repeat the input. If it is not possible to eliminate the original error, logging may also be deactivated. KVP0070 NO WORKING-STORAGE AVAILABLE FOR (&00) - ENTER INPUT AGAIN &00 = KVP name (HV0, VM1, VM2 etc.) Response You must repeat the input.
X2000 messages KVP0801 KVP messages FILE-LOGGING FAILED Response The access rights to the file structure /var/opt/SMAW/X2000/log and the file /var/opt/SMAW/X2000/log/log_info should be checked and, if necessary, corrected. This message is also output if archiving is set to FORCED and none of the existing logging files could be archived. The system administrator must make sure that the archiving command can be terminated without errors or the files must be deleted.
SVP emulation messages X2000 messages 13.2 SVP emulation messages The messages issued by the SVP emulation start with the message code SVR. SVR0000 xxxx started with device MM, console NN, iorsf P, BS2-Sys SS xxxx = IPL, DIPL or VIPL Meaning The IPL has been started. BS2000 is loaded from device MM, NN is defined as the console, the IORSF parameter list P is used and SS is defined as the BS2000 system name.
X2000 messages SVR0005 SVP emulation messages START-xxxx aborted (nnnnnn) xxxx = IPL, DIPL or VIPL Meaning IPL was aborted with errors (nnnnnn = cause of error). SVR0006 Incorrect command: xx xx = command entered Meaning An incorrect command has been entered. Response Enter command correctly. SVR0008 xxxx started xxxx = IPL, DIPL or VIPL Meaning An operation has been started. SVR0009 CPU xx not stopped Meaning A CPU was not stopped on sv.ipl.
SVP emulation messages SVR0020 X2000 messages Channel initialization active, please wait Meaning Channel initialization is not yet complete. Response Wait until channel initialization is complete. SVR0021 IOD channel initialization started - please wait Meaning IOD channel initialization has been started. Response Wait until channel initialization is complete. SVR0022 IOD channel initialization finished Meaning IOD channel initialization has been performed correctly.
X2000 messages SVR0030 SVP emulation messages START VIPL aborted - VM not active Meaning The VIPL was aborted because the VM mode was not activated. Response Activate VM-Mode via PRIMEPOWER ServerView Suite. SVR0031 Restart VM Monitor aborted (nnnnnnnn) Meaning The VMMR was aborted (nnnnnnnn = cause of the error). Response Correct the error. The restart is not possible, if the VM-mode is not activated via PRIMEPOWER ServerView Suite.
IOD messages X2000 messages 13.3 IOD messages 13.3.1 Messages referring to bus devices The messages issued by the I/O handler for bus devices begin with the message code IOD0xxx to IOD9xxx. IOD0000 IOD0000 IOD_Vxx RELEASE SL=mmm *** IOD-BUS IMPL READY *** IOD GENERATED ON YYYY/MM/DD AT HH:MM:SS Meaning The IOD (I/O handler for bus devices whose I/Os are performed via X2000) issues this message on every long IPL (=IMPL). It contains the generation date and the version of the employed IOD.
X2000 messages IOD0879 IOD0879 IOD messages IOD_Vxx SL=mmm. * Device configuration request from X2000 * RKF00 PCIB INVALID CHN=y UA=zz - REQUEST REJECTED Meaning A new device has been configured in X2000. The data passed from X2000 is incorrect. CHN: Host connector number ( equivalently to CHPID). Response Repeat configuration in X2000. If this repetition is unsuccessful, an IOHDUMP should be generated and then analyzed or sent to a Support Center. IOD0879 IOD0879 IOD_Vxx SL=mmm.
IOD messages IOD0999 IOD0999 X2000 messages IOD_Vxx SL=mmm *** IOD ABNORMAL END *** *** ERROR CODE=modyyy *** START IMPL! Meaning IOD has detected an error and terminated the system run. On the next system start (IMPL), an IOHDUMP will be generated and saved in the directory /var/opt/SMAW/X2000/dump/. IOD0999 *** ERROR CODE=CPI015 *** START IMPL! Meaning The HAL has not responded to the initialization message within 10 seconds.
X2000 messages IOD0999 IOD messages *** ERROR CODE=IPL005 *** START IMPL! Meaning The RMAssist has not responded to an IOD message within 10 seconds. Response Identify the cause of the error and repeat the IMPL or execute bs2init 0 and bs2init 1. IOD3000 IO-CONFIGURATION ERROR: DEV#/MN xxxx/yyyy NOT UNIQUE Meaning The device with the device number xxx and the mnemonic yyyy is configured both as a bus and as a channel device.
IOD messages X2000 messages 13.3.2 Messages referring to channel devices The messages issued by the I/O handler for channel devices begin with the message codes IODAxxx to IODZxxx. IODC000 IOS0000 IOD CHANNEL STARTUP FINISHED Meaning This message indicates that IOD channel startup has run correctly. IODC002 IODC003 IORSF TITLE: ... IOCFID: .... Meaning These both messages specify the title of the loaded IORSF.
X2000 messages IODE022 IOD messages CHPID xx module error: module stopped Meaning Module stop error handling has been terminated with an error or due to the presence of a persistent error. The module has been stopped and identified as defective. A logout has been stored. Response The error could not be eliminated by the error handling operation. The result of the analysis of the corresponding logout should be evaluated and maintenance undertaken.
IOD messages IODE053 X2000 messages CHPID xx vary offline rejected: hardware error Meaning The MSSF call CHPOFF - vary channel path offline was rejected because of the presence of a hardware error. Appropriate error handling is performed for the hardware error. Response For information on error handling, see the messages relating to module stop error handling (IODE021, IODE022).
X2000 messages IODE062 IOD messages CHPID xx was already online Meaning The module was already in the online state at the time of the MSSF call CHPOFF - vary channel path online. Response No maintenance response is required. IODE063 CHPID xx vary online rejected: hardware error Meaning The MSSF call CHPON - vary channel path online was rejected because of the presence of a hardware error. Appropriate error handling is performed for the hardware error.
IOD messages IODE0E0 X2000 messages Error Code xx: Error detected by IOD-Firmware Meaning The IOD has detected an internal error and has reset the channel subsystem. All installed components of the channel subsystem are initialized and started. Response The error has been eliminated for the present by the error handling operation. There is generally no hardware error present when the IOD detects such an internal error.
X2000 messages IODF007 IOD messages IORSF IDENTIFICATION INVALID Meaning Content error in IORSF. Response Regenerate IORSF. IODF008 IORSF ERROR: INVALID CHANNEL INTERFACE TYPE Meaning Content error in IORSF (possible cause: IORSF was generated for another system). Response Regenerate IORSF. IODF009 IORSF ERROR: Subchannel # less than 1000 Meaning Content error in IORSF. Response Regenerate IORSF. IODF010 NO CHANNELS CONFIGURED Meaning No channel devices in the I/O configuration.
HAL messages X2000 messages 13.4 HAL messages HAL0001 MDEBUG ACTIVE Meaning The master debugger mdebug has been started HAL0002 MDEBUG INCATIVE Meaning The master debugger mdebug has been stopped HAL0140 HAL ABORT GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP Meaning The HAL on this processor has detected an inconsistency and has terminated the processing of BS2000 instructions on all processors. Response Please execute the following commands as ’root’ user in Solaris.
X2000 messages HAL0212 HAL messages MDEBUG STOP GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP BREAK-POINT Meaning A break point set by mdebug has been executed by the given processor. The processing of BS2000 instructions has been halted. Response The mdebug command ’bg’ will restart the processor.
HAL messages HAL0311 X2000 messages BS2000 STOP GPXX SSSSSSSSSSSSSSSS PPPPPPPPPPPPPPPP DISABLED-WAIT Meaning A new PSW has been loaded by the given processor in which the wait bit is set and no interrupts are enabled. As a result, the processing of BS2000 instructions has been halted. This may occur as part of a normal shutdown or may be due to a system crash - SETS.
X2000 messages HAL0350 HAL messages BS2000 ACF GPXX PPPPPPPP EEEEEEEEEEEEEEEE ALIGNMENT ERROR CORRECTED PPPPPPPP = The 4 byte program counter. EEEEEEEEEEEEEEEE = The 8-byte extended address which caused the alignment error. Meaning The executing BS2000 program caused an alignment error when accessing data. The ACF facility then used a slower access method to access the data and enable the program to continue. Response Modify the program to align the data correctly.
X2000 channel connection error messages X2000 messages 13.5 X2000 channel connection error messages 13.5.1 Structure of message numbers 6 7 8 System signature The service function system signature for the X2000 channel connection is preset to “SV”. Process signature The process signature indicates the associated process. The assignment is defined as follows: ..A.... ..D.... ..I.... ..L.... ..M.... ..N.... ..P.... ..S.... ..T.... Program signature 362 9...
X2000 messages X2000 channel connection error messages 13.5.2 Metasyntax A metasyntax is used to avoid burdening the message text with unnecessary lists. Text variable Any text variable is enclosed in angle brackets (e.g. ) and is explained in the associated message description or at the start of the section. If a text variable expression consists of text then this is explicitly stated. 13.5.3 HWA error messages The HWA messages are process-independent. ...A003 mmap failed, .......
X2000 channel connection error messages X2000 messages 13.5.4 HWI messages The HWI messages are process-independent. HWI message code: ... ... ...I003 Buffer start address for HWI opcode List of CHPIDs for the channels in question Selected HWI opcode (four characters) Selected HWI operation (two characters) List of CHPID areas (x0...xF) of affected channels without further specification write access not allowed - opcode: CHPID(s): ...
X2000 messages ...I092 X2000 channel connection error messages ioctl () failed, ....... The system error message is appended to the message. Meaning Software error: The ioctl request has been aborted. ...I093 sscanf() format error ’’ Meaning File error: The file has an invalid format and could not be processed with sscanf. ...I094 fwrite() failed ’’ Meaning File error: The file could not be written.
X2000 channel connection error messages ...I201 X2000 messages hw-configuration changed (channel) - CHPID(s): ... Meaning Configuration message: The channels' hardware configuration has changed. This message is issued following a channel installation/de-installation operation or after a hardware failure. ...I202 conf-file is corrupted ’’ Meaning Software error: The configuration file is corrupt. ...I702 cannot get/create semaphore - key: CHPID range(s): ...
X2000 messages X2000 channel connection error messages 13.5.5 MAIN messages The MAIN message numbers are process-dependent, i.e. the message is only unique if accompanied by a process signature. 13.5.5.1 ciodebug messages ciodebug message code: ..AM001 Channel Path Identification illegal chpid Meaning Software error: The storage area in CASA cannot be allocated because the CHPID is incorrect. 13.5.5.2 ..
X2000 channel connection error messages 13.5.5.3 X2000 messages channel_ipl messages channel_ipl message code: ... ... ..IM001 List of CHPIDs for the channels in question Selected HWI opcode (four characters) List of CHPID areas (x0...
X2000 messages ..IM022 X2000 channel connection error messages CASA init Meaning Runtime message: The CASA shadow memory is being initialized ..IM023 IOCF file iorsf loaded Meaning Runtime message: The IOCF file with the IORSF level has been loaded into the shadow memory. ..IM024 no IOCF file loaded Meaning Runtime message: No IOCF file has been loaded into the shadow memory. Either no IORSF level was specified or the IOCF file with the specified level does not exist. ..
X2000 channel connection error messages ..IM097 X2000 messages fopen() failed ’’ Meaning File error/software error: The file could not be opened. The path rights may have been set incorrectly, the file system may be defective or full or the file may have been deleted. ..IM099 fseek() failed ’’ Meaning File error/software error: The positioning in the file was invalid. The file was not opened or the position was beyond the end-of-file. ..
X2000 messages SVLB000 X2000 channel connection error messages sequence number access error, logout dropped Meaning Error in creating the binary logout file lfxxxx ( = logout sequence number). The logout data cannot be analyzed and cannot be backed up. SVLB001 error create lfxxxx Meaning Error in creating the binary logout file lfxxxx ( = logout sequence number). The logout data cannot be analyzed and cannot be backed up.
X2000 channel connection error messages SVLB008 X2000 messages result compare error Meaning Error in comparing the analysis result with the previous result. No analysis result is backed up, but the basic binary logout is backed up and can be displayed via logging-V3-additional info.
X2000 messages ..MM004 X2000 channel connection error messages ioctl () failed, ....... The system error message is appended to the message. Meaning Software error: The IOCTL request has been aborted. ..MM005 end of channeld by SIGTERM Meaning Runtime message: The daemon was terminated by the signal SIGTERM. ..MM006 : sigaction() failed Meaning Software error: Signal processing sigaction was incorrect in the daemon function . ..
X2000 channel connection error messages ..MM299 X2000 messages fseek() failed ’’ Meaning File error/software error: The positioning in the file was invalid. The file was not opened or the position was beyond the end-of-file. ..MM401 illegal CHPID ; undefined channel group number Meaning Software error: The channel group selection of the channel path identification is incorrect. ..
X2000 messages ..NM020 X2000 channel connection error messages reconfiguration logout saved Meaning Runtime message: A reconfiguration logout was written. ..NM100 ioctl () failed, ....... The system error message is appended to the message. Meaning Software error: The IOCTL request has been aborted. 13.5.5.7 ..PM096 set_spd messages fread() failed Meaning Software error: The configuration file could not be read. ..
X2000 channel connection error messages 13.5.5.8 X2000 messages ctest messages ctest message code: ..TM001 Board type D number (PCB number) Bus identification Cabinet identification Channel path identification (CHPID) Repetition count Slot identification Test number usage description usage : Format: -q -d -k [-t ][ -r ] -l -k [-t ][ -r ] -> 0x80...
X2000 messages ..TM001 X2000 channel connection error messages wrong channel selection (CHPID) The message ..TM001 is also output. Meaning Warning: The formally incorrect CHPID was specified (outside the number ranges 80...8E and 90...FF). ..TM001 no related channel for CHPID The message ..TM001 is also output. Meaning Warning: No channel exists for the specified CHPID . ..TM001 option (-d, -l or -q) will be set twice The message ..TM001 is also output.
X2000 channel connection error messages ..TM001 X2000 messages empty test number The message ..TM001 is also output. Meaning Warning: The -t option but no test number was specified. ..TM001 wrong test number The message ..TM001 is also output. Meaning Warning: The test number is not 0 (all tests) or not in the number range 1...4. ..TM001 test number will be set twice The message ..TM001 is also output. Meaning Warning: A test number has been specified twice. ..
X2000 messages ..TM002 X2000 channel connection error messages error in channel test CHPID CABINET ID: ? BUS ID: ? - , SLOT ??, Meaning A channel test program has detected an error: There is no valid cabinet ID for the current CHPID ; the IOCTL request PCHAN_CHAN_GET_LOC has been acknowledged incorrectly. Response Locate the error. ..TM002 error in channel test CHPID CABINET ID: BUS ID: - , SLOT ,
X2000 channel connection error messages ..SS003 X2000 messages channel initialization timed out Meaning Software error: The cipl script was aborted because initialization of the channel system was not terminated within the predefined period (10 minutes). ..SS101 device occupied by ’’ PID: Meaning Reservation error: The called process is aborted because the device has been reserved by the process with the ID .
X2000 messages X2000 messages to the BS2000 console 13.6 X2000 messages to the BS2000 console If X2000 detects an error in a peripheral component that cannot be reported to BS2000 via an I/O then X2000 sends the following message to the BS2000 console: SNX2000 AN ERROR HAS OCCURRED IN A PERIPHERAL COMPONENT - FOR FURTHER INFORMATION PLEASE CONSULT THE PRIMEPOWER SERVERVIEW APPLICATION DIAGNOSTIC.
EVENT error messages X2000 messages 13.7 EVENT error messages If input errors occur in EVENT mode then the following messages are output in inverse video in line 24. wrong password or timeout Meaning The password was entered incorrectly during input. The previous input is ignored. Response Repeat the operation. input locked - type F2 KEY Meaning Input in EVENT mode has been locked. Response Press the F2 key to release input.
X2000 messages EVENT error messages input rejected, destination invalid Meaning Messages in EVENT mode must be written in the form xx.text (xx=component in question and text=input text). The relevant component has been specified incorrectly. Response Repeat the input correctly. no command files present Meaning The command file from sx.command does not exist. Response Specify the command file correctly in sx.command. The available commands can be listed using sx.? .
EVENT error messages 384 X2000 messages U41272-J-Z385-3-76
14 Appendix 14.1 Hardware features of the SX Series Business Servers Technical highlights of the business servers in the SX series are summarized in the following two sections. You will find further details of features specific to each model range in the section corresponding to the specific model range in the sections below. 14.1.1 The partitioning concept of the SX servers (without the entry-level models) The SX server hardware is based on the hardware of the PRIMEPOWER servers.
Hardware features of the SX Series Business Servers Appendix The basis for the division into physical partitions (PPARs) on SX130 servers is provided by the physical system boards (PSBs) and, as of the SX140 servers, the PSB mode of an SX server’s system boards. A physical partition can contain one or more physical system boards. A system board carries various hardware components such as CPUs, memories and PCI slots.
Appendix Hardware features of the SX Series Business Servers The figure below shows physical partitions based on physical system boards, using the SX130 as an example: Partition 1 Partition 2 BS2000 partition Partition 3 (optional) Solaris partition System board 0 System board 1 System board 2 System board 3 Main memory Main memory Main memory Main memory CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU Crossbar PCI slots PCI slots PCI slots SCSI controller
Hardware features of the SX Series Business Servers Appendix SX series business servers have the following types of partition depending on the operating system being run on the partition: ● BS2000 partition The BS2000/OSD with the X2000 carrier system is installed. X2000 is based on Solaris and mainly provides the runtime environment for BS2000/OSD. Here BS2000/OSD can also run under the VM2000 virtual machine system.
Appendix Hardware features of the SX Series Business Servers 14.1.2 SX server system peripherals The SX series servers optionally provide full Fibre Channel connectivity for the connection of peripheral devices. This permits the SX servers to be seamlessly integrated into an intelligent SAN environment. On a model-specific basis, the SX server for BS2000/OSD also supports an optional channel interface.
Hardware features of the SX Series Business Servers Appendix Channel peripherals on BS2000 partitions Channel peripherals are only possible on SX servers which support the optional channel interface. Channel peripherals are connected to the SX server via the optional channel subsystem (Universal Hot Plug System, UHPS). The channel subsystem is connected to a system board of the BS2000 partition using a corresponding PCI/SCI adapter.
Appendix Hardware features of the SX Series Business Servers Channel Type 2/Type S Peripherals ... Channel Type 2/Type S Peripherals ... UHPS 2 (optional) UHPS 1 (optional) Fibre Channel Peripherals ...
Hardware features of the SX Series Business Servers Appendix The connection possibilities are the same for the other models in the SX series, with the exception of the entry-level models. Operating peripherals in SX servers without SMC SX servers without SMC can be operated via the integrated console or via a LAN console.
Appendix Model ranges 14.2 Model ranges This section describes the features specific to the model ranges of the Business Servers of the SX series. 14.2.1 SX100 Overview ● Designed exclusively for use with BS2000/OSD (does not support partitioning). ● Maximum memory for BS2000/OSD and X2000 combined: 8 GB. ● Optional Fibre Channel connection technology for FibreCAT and Symmetrix disk systems. ● Internally used hard disks and a magnetic tape cartridge changer with LTO drive.
Model ranges Appendix Peripherals of the SX100 system The basic version of the input/output system has two 73 GB hard disks configured as a mirrored system. Alongside the X2000 system partitions on these disks there are two BS2000 volumes, each 17 GB. Optionally it is possible to install an additional DISK subsystem with 4 x 73 GB, which can be extended to a maximum of 14 disks. As a further option a FibreCAT or Symmetrix disk storage system can be connected via the Fibre Channel.
Appendix Model ranges The SX130 Business Server model range (basic configurations) consists of the following: Model Capacity in RPF CPUs for BS2000/OSD CPUs for I/O (X2000) SX130-10A/B/C 35/42/55 1 1 SX130-20A/B/C 63/75/88 2 1 SX130-30C 122 3 1 SX130-40C 155 4 1 SX130-50C 187 5 1 SX130-60C 217 6 2 Table 14: SX130 series model range Servers in the SX130 series model range The basic version of all SX130 series models has two system boards.
Model ranges Appendix Basic version (2 system boards) Full version (4 system boards) BS2000 System board BS2000 System board System board System board System board BS2000 System board System board System board CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU BS2000 Solaris System board System board BS2000 System board System board System board System board Solaris Solaris Sy
Appendix Model ranges The maximum power supply protection can be achieved by using the optional dual power supply. SX130 system peripherals Channel peripherals (type 2 and type S) may be connected to the SX130 server via the optional channel subsystem. The channel subsystem is connected by an SCI controller and occupies a PCI slot of a system board in the BS2000 partition for up to 16 channel connections.
Model ranges Appendix 14.2.3 SX140 Overview ● Maximum equipment: 16 CPUs and 64 GB memory. ● Supports a maximum of 2 system board, each with a maximum of 8 CPUs, 8 memory packages and 8 PCI slots. Also 1 PCI/disk box with 10 PCI slots exists for each physical system board for model SX140-40C and higher. ● Each system board can be operated in PSB or XSB mode. ● Supports extended partitions (XPARs) ● In XSB mode up to 4 extended system boards can be configured for each physical system board (i.e.
Appendix Model ranges The SX140 Business Server model range consists of the following (basic configuration): Model Capacity in RPF CPUs for BS2000/OSD CPUs for I/O (X2000) XSB SX140-10A/B/C 42/58/75 1 1 00-0 SX140-20A/B/C 94/113/133 2 1 00-0, 00-1 SX140-30C 185 3 1 00-0, 00-1 SX140-40C 235 4 1 00-0, 00-1, 00-2 SX140-50C 280 5 1 00-0, 00-1, 00-2 SX140-60C 320 6 1 00-0, 00-1, 00-2, 00-3 Table 16: SX140 series model range Servers in the SX140 series model range The basic v
Model ranges Appendix As default, the first BS2000/OSD instance is installed on XSB00. If the number of processors requires this, XSB00-1, XSB00-2, XSB00-3 are added in the sequence indicated. XSB00-2 and XSB00-3 require a PCI/disk box which is integrated in models SX140-40C,... , -60C.The same applies if XSB01-2 and XSB01-3 are to be used on the second physical system board.
Appendix Model ranges The basic versions of the additional BS2000 partition have the same performance classification as that of the first BS2000 partition. They are equipped with a model-specific number of processors, a model-specific memory capacity, 2 boot disks, power supply and fans so that they can be installed in the system cabinet in addition to the first BS2000/OSD instance. The customer defines which XSBs are included in further partitions. Servers can be upgraded by adding CPUs.
Model ranges Appendix 14.2.4 SX150 Overview ● Maximum equipment: 16 CPUs and 64/128 GB memory. ● Supports a maximum of 2 system boards, each with a maximum of 8 CPUs, 8 memory packages and 8 PCI slots. Expansion by 10 PCI slots is possible using a PCI/disk box. The expansion is required if XSBs 00-2 and 00-3 of the first and/or XSBs 01-2 and 01-3 of the second system board are used. ● Each system board can be operated in PSB or XSB mode. ● Supports extended partitions (XPARs).
Appendix Model ranges The SX150 Business Server model range consists of the following (basic configurations): Model Capacity in RPF CPUs for Memory (GB) SBs X2000 PCI slots 8 1 8 1 0, 1 1 8 1 8 1 0, 1 3 1 12 1 13 2 0, 1 0 4 1 12 2 13 2 0, 1 0 380 5 1 12 2 13 2 0, 1 0 440 6 1 16 2 16 2 0, 1 0, 1 BS21 I/O2 Total3 SX150-10A/B/C 42/75/105 1 1 SX150-20A/C 140/180 2 SX150-30C 250 SX150-40C 320 SX150-50C SX150-60C XSBs on SB 00 SB 01 Table 17: SX
Model ranges Appendix Capacity on Demand (CoD) Use of the Capacity on Demand (CoD) function provides the option of interrupt-free, temporarily limited performance enhancement. This function can be used for different usage periods. Usage of additional CPU performance In addition to the CPUs which are activated by default one or more CoD processors can also be used if this is contractually agreed. When required they are attached or detached during ongoing operation. Modell CPUs Standard CPUs CoD max.
Appendix Model ranges Using XSB mode the hardware resources of a system board listed above can each be divided into 4 independent extended system boards (XSBs). The interface for setting or modifying PSB or XSB mode and its configuration is described in the section “Administering the system board’s operating mode” on page 75. XSBs can then be used as the basis for extended partitions (XPARs). The interface for this function is described in the section “Configuring and modifying partitions” on page 78.
Model ranges Appendix The figure below shows the basic version of the SX150-10C model and some extension possibilities: System board 00 XSB00-0 BS2000 5 PCI slots XSB00-1 BS2/Solaris 3 PCI slot XSB00-2 BS2/Solaris 7 PCI slots XSB00-3 BS2/Solaris 3 PCI slots BS2 CPU 1 X2 CPU 3 CPU 4 CPU 5 CPU 6 CPU 7 4 GB Mem 1 4 GB Mem 3 Mem 4 Mem 5 Mem 6 Mem 7 PCI/disk box necessary System board 01 XSB01-0 BS2/Solaris 5 PCI slots XSB01-1 BS2/Solaris 3 PCI slots XSB01-2 BS2/Solaris 7 PCI slots XSB
Appendix Model ranges FC, Ethernet and SCSI controllers can be replaced during ongoing operation, as can the redundant system components hard disks, power supplies and fans. The reconfiguration options of processors, memory and I/O system means that the SX150 system offers high availability. The maximum power supply protection can be achieved by using the optional dual power supply.
Model ranges Appendix Peripherals of the SX150 system Channel peripherals (of type 2 and/or type S) can be connected to the SX150 server by a maximum of 2 channel chassis in a BS2000 partition. A maximum of 32 channels in total are therefore available on an SX150 in a BS2000 partition. Any combination of channels of type 2 and type S is possible. Each system board has 2 onboard-integrated SCSI controllers for connecting the hard disks and 2 onboard-integrated Ethernet controllers.
Appendix SKP-SR for BS2000 operation 14.3 SKP-SR for BS2000 operation The use of an SKP-SR for the SX130 Business Server is optional. The SKP-SR can be used for the following applications: ● Operation of X2000 instances (e.g. BS2000 console) via LAN using preconfigurable virtual screens (not possible when using the Secure Shell) ● Operation of applications on an SX server with a graphical user interface (e.g.
SKP-SR for BS2000 operation Appendix 14.3.2 Automatic system operation via ATOP The ATOP is connected to the SKP-SR serial ports. One serial connection to the SKP-SR is required for each system to be monitored. The monitor script must first control the SKP-SR login before logging in via LAN to the system login which provides access to the console that is to be monitored (e.g. cons0 for the BS2000 console). 14.3.
Abbreviations APCS Automatic Power Control System ATNS Advanced Transport Name Service CCU Console Connection Unit CDE Common Desktop Environment CHPID Channel Path Identification CoD Capacity on Demand CPU Central Processing Unit DAT Digital Audio Tape DDC DC DC Converter DNS Domain-Name-Service DR Dynamische Rekonfiguration DSSM Dynamic Subsystem Management ESA Enterprise System Architecture ESCoD Enhanced Server Capacity on Demand EM Emulation ESF Enhanced Support Facility
Abbreviations 412 LTO Linear Tape Open MAC Media Access Control MTC Magnetic Tape Controller NTP Network Time Protocol OBP OpenBootTM PROM OS Operating System OSD/XC OSD Extended Configuration PCI Peripheral Component Interconnect PHP PCI Hot Plug PID Partition ID POST Power On Self Test PPAR Physical Partition PPK PuTTY Private Key File (file extension) PRM Print Resource Management PROM Programmable Read Only Memory PSB Physical System Board PSR Physical Save and Restore
Abbreviations TODR Time Of Day Register UA Unit-Adresse VCA Virtual Channel Adapter WAN Wide Area Network XB Crossbar XB-DDC Crossbar DC-DC Converter XPAR Extended Partition XSB Extended System Board WSA Web based System Administration, WebSysAdmin (earlier designation of PRIMEPOWER ServerView) WWPN World Wide Port Name XSCF eXtended System Control Facility U41272-J-Z385-3-76 413
Abbreviations 414 U41272-J-Z385-3-76
Figures Figure 1: Example of an SX server: SX150 Business Server. . . . . . . . . . . . . . . . . . . . 2 Figure 2: Structure of the documentation for the SX Series Business Servers . . . . . . 5 Figure 3: Example of an operating concept for an SX server . . . . . . . . . . . . . . . . . . . 12 Figure 4: Operating concept of an SX server without SMC . . . . . . . . . . . . . . . . . . . . 14 Figure 5: Example of an operating concept for an entry-level model . . . . . . . . . . . . .
Figures Figure 22: Machine Administration Menu: “System-Specific Administration” . . . . . . . . 60 Figure 23: Machine Administration Menu: “System/Partition Power Administration” . . 61 Figure 24: Machine Administration Menu: “APCS Setup Menu”. . . . . . . . . . . . . . . . . . 67 Figure 25: PRIMEPOWER ServerView- window: “Create task” . . . . . . . . . . . . . . . . . . 72 Figure 26: Control panel of an SX140 or SX150 server . . . . . . . . . . . . . . . . . . . . . . . .
Figures Figure 45: Xconfig: Start window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Figure 46: Xconfig: Network and Communication window . . . . . . . . . . . . . . . . . . . . . 136 Figure 47: Xconfig: XDMCP Startup Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Figure 48: Xconfig: Display and Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures Figure 71: Presentation of non-accessible nodes in the hierarchy browser of PRIMEPOWER ServerView. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Figure 72: Displaying and modifying authorizations in PRIMEPOWER ServerView . 203 Figure 73: Modifying access to the individual applications in PRIMEPOWER ServerView. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Figure 74: The Bs2Devices user interface . . . . . . . . . . .
Figures Figure 96: Mercator window with Xprint database (printer inactive) . . . . . . . . . . . . . . 248 Figure 97: Mercator printer configuration window (State) . . . . . . . . . . . . . . . . . . . . . . 249 Figure 98: Mercator window with Xprint database (printer active) . . . . . . . . . . . . . . . 250 Figure 99: X2000 user interface for creating a BS2000 printer. . . . . . . . . . . . . . . . . . 252 Figure 100: X2000 window for creating a BS2000 printer . . . . . . . . . . . . . . . . . . . . . .
Figures Figure 121: Start buttons in PRIMEPOWER ServerView . . . . . . . . . . . . . . . . . . . . . . . 332 Figure 122: “Tools” tab in PRIMEPOWER ServerView . . . . . . . . . . . . . . . . . . . . . . . . . 332 Figure 123: Starting the functions Mirror, CSR and PSR from the drop-down menu . . 333 Figure 124: Example of creation of physical partitions . . . . . . . . . . . . . . . . . . . . . . . . . 387 Figure 125: Example of creation of extended partitions . . . . . . . . . . . . . . . . . . . . . . . .
Tables Table 1: Functionality of the administrator user group in the SCS . . . . . . . . . . . . . . . . . 45 Table 2: Overview of the access options to XSCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Table 3: XSCF functions available via a Web browser . . . . . . . . . . . . . . . . . . . . . . . . . 123 Table 4: Message texts with message code SVR0002 . . . . . . . . . . . . . . . . . . . . . . . . . 170 Table 5: Function keys for the terminal type dtterm . . . . . . . . . . . . . . . . .
Tables 422 U41272-J-Z385-3-76
Related publications The manuals are available as online manuals, see http://manuals.fujitsu-siemens.com, or in printed form which must be payed and ordered separately at http://FSC-manualshop.com. [1] SX Series Business Servers Concepts and Functions User Guide Target group This manual is designed for technical decision-makers who want to find out about the applications of the SX Series Business Servers, and for users who want to familiarize themselves with the operation of the SX servers.
Related publications [3] BS2000/OSD-BC V6.0 Migration Guide User Guide Target group Systems support and system services Contents The Migration Guide summarizes the individual work steps required for a changeover from BS2000/OSD-BC V4.0 or V5.0 to BS2000/OSD-BC V6.0 and offers hints for converting back to the old version. The Migration Guide also describes the migration of S Servers under BS2000/OSD or SR2000-B/-C Business Servers under OSD-SVP to an SX server under OSD/XC.
Related publications [6] PRIMEPOWER ServerView Suite V2.2 Integration in Enterprise Server Management Systems Target group System administrators and customer service staff. Contents This manual describes two products, which allow integrating the PRIMEPOWER ServerView Suite in the two global IT management products CA Unicenter NSM and Tivoli.
Related publications [11] BS2000/OSD-BC Commands, Volumes 1 - 5 User Guide Target group This manual is addressed to nonprivileged users and systems support staff. Contents Volumes 1 through 5 contain the BS2000/OSD commands ADD-... to WRITE-... (basic configuration and selected products) with the functionality for all privileges. The command and operand functions are described in detail, supported by examples to aid understanding.
Related publications [13] BS2000/OSD-BC System Messages, Volumes 1 - 3 User Guide Target group This manual is addressed to systems support staff, operators and users. Contents Chapter 1 deals with message processing in BS2000/OSD. Chapter 2 contains the system messages of the message classes for the basic configuration of the BS2000/OSD operating system. The messages are arranged in alphabetical order by message class and are accompanied by explanatory texts where appropriate.
Related publications [16] Assembler Instructions (BS2000/OSD) Reference Manual Target group BS2000/OSD assembly-language programmers Contents This manual describes in alphabetical order all (nonprivileged) assembler instructions of the CPUs supported by BS2000/OSD. For each instruction the following is described: – its function – its assembler format, i.e. how to write it in assembly language – its machine format, i.e.
Related publications [18] openSM2 (BS2000/OSD) Software Monitor Volumes 1 and 2 User Guide Target group This manual is addressed to users and systems support staff. Contents The monitoring system SM2 supplies users with statistical data on the performance of their DP systems and on resource utilization. Volume 1 of the manual describes operation of the SM2 monitor, the SM2 monitoring programs and the SM2 screen reports.
Related publications [21] BS2000/OSD Softbooks English CD-ROM Target group BS2000/OSD users Contents The CD-ROM "BS2000/OSD SoftBooks English" contains almost all of the English manuals and README files for the BS2000 system software of the latest BS2000/OSD version and also of the previous versions, including the manuals listed here. These Softbooks can also be found in the Internet on our manual server. You can browse in any of these manuals or download the entire manual.
Related publications [24] CMX V5.1 (Solaris) Communications Manager Solaris Operation and Administration User Guide Target group System administrators Contents The manual describes the function of CMX as mediator between applications and the transport system. It contains basic information on configuration and administration of systems in network environments.
Related publications [27] Partition Operation Guide Target group System administrators, administrators, service engineers Contents The manual describes the procedure for the dynamic reconfiguration of the PRIMEPOWER/GP7000F high-performance models (system unit) and the use of the system on the system unit. Only available online: http://manuals.fujitsu-siemens.
Related publications [31] Teleservice (Unix) User Guide Target group The manual is intended for customers and operators of Teleservice Centers. Contents The manual describes the basic technical functioning of the Teleservice software. It also provides guidelines for users and system administrators as well as information on tools and modem validation.
Related publications 434 U41272-J-Z385-3-76
Environmental protection Take-back, recycling and disposal For details on take-back and reuse of devices and consumables within Europe, contact your Siemens branch office/subsidiary or our recycling center in Paderborn: Tel. Fax. +49 5251 8180-10 +49 5251 8180-15 Further information on environmental protection The Siemens AG representative for environmental protection will be pleased to answer any further questions you may have concerning environmental protection.
Environmental protection 436 U41272-J-Z385-3-76
Index $DIALOG mode 189 /390 1 /390 firmware 3 3919 410 3920 410 9750 emulation 134, 143 configuring 188 notes on operation 186 97801 terminal 180 A administrator BS2000 52 partition 49 server 46 Solaris 52 spool 175 Application Manager ATNS 264 ATOP 410 automatic IPL 215 30 B background color 36 backup configuration data 218 physical 218 BCAM, DR-secure connection 272 browser 134, 140 BS2 crypto ports 217 BS2 devices 211 BS2 disks 211 U41272-J-Z385-3-76 BS2 KVP 215 BS2 LAN ports 217 BS2 printers 216 BS2
Index clmon 49 Cluster Recovery Lock 320 CoD (Capacity on Demand) 289 command OBP 89 scslbackup 104 scslrestore 105 shutdown 216 su 18 SVP 159 xlsfonts 35 configuration 2-disk 228 3-disk 228 9750 emulation 188 activating 215 automatic IPL 215 BS2000 devices 257 BS2000 disks 211 displaying 81 dtterm window 35 fjge driver 271 NTP server 94 parameter 89 partition 82 partitioning 81 print server 251 printers 216, 242 private disks 213 protection mechanisms 19 pubsets 213 PuTTY 148 querying 193 server hardware
Index DUMPDIR 326 Dynamic Reconfiguration 285 PRIMEPOWER ServerView 304 E EM9750 mode 182 EMC Powerpath 108, 110 emulation, printer 247 entry model 1 entry-level model 1 environment variable 327 error messages 327 escape sequence 258 establishing connection 183 euro currency symbol 260 EVENT mode, entering the commands 191 Exceed 135 extended system board mode (XSB mode) 285 extended system board operating mode (XSB mode) 75 F Fibre Channel disk 223 file system backup 108 recovery 113 fjgi driver 271 FJS
Index model range SX140 399 model range SX150 403 monitor script 410 MSCF 320 MSCF cluster 169 MTC device configuring 234 displaying the occupancy status 240 exclusive use of 232 occupying when host communication disrupted 239 setting an occupancy option 193 showing occupancy status 193 N Network Configuration 120 next 312 no-io-sb 321 no-mem-sb 321 no-obp-sb 321 normal mode 258 NTP time server 410 number notation 327 O object compatibility 1 object list and table 207 OBP commands 89 setting via PRIMEPOWER
Index resource management, global 288 responses to messages in BS2000 CONSOLE mode 159 restore configuration data 218 rs2k 23 S SCS 56 SCS checkbox 29 SCSI disk 221 security 17 select printer 175 selection configurator 207 server administrator 46 shutdown command 216 SINIX-TE 134, 142 SKP-SR 409 SLED 171 SNMP Administration 120 Solaris 1 Solaris 8 12 Solaris 9 12 Solaris administrator 52 Solaris DR logging file 314 Solaris partition 2, 388 Solstice Disk Suite 108, 110, 224 sort order 327 SPARC64 technology
Index Volumes+Pubsets VSN 213 213 W workload distribution, dynamic wsauser 46, 54 288 X X servers 134 X2000 211 X2000 DR logging file 314 x2prtpci 309 XCS cluster 93 XSB assigned 303 connecting 286 disconnecting 287 failure 287 integrated 303 shifting 307 XSB mode 75, 285 XSB system board pool 285 XSCF (Extended System Control Facility) access via console 122 access via Web browser 123 configuration 119 shell 121 XSCF Web Administration 120 X-Window interface 12, 14 Z ZASLAN 442 117 271 U41272-J-Z3
Contents 1 1.1 1.2 1.3 1.4 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation for the SX Series Business Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . Target groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 3.3.5 3.3.6 3.4 PRIMEPOWER ServerView (BS2000 system) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Machine Administration Menu (for entry-level models only) . . . . . . . . . . . . . . . . . . . . . 39 Calling terminal instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.2 4.3 4.3.1 4.3.1.1 4.3.1.2 4.3.1.3 4.3.1.4 4.3.1.5 4.3.1.6 4.3.1.7 4.3.1.8 4.3.2 4.3.2.1 4.3.2.2 4.3.3 4.4 4.5 4.5.1 4.5.
Contents 5 5.1 5.2 5.2.1 5.2.2 5.3 5.4 5.5 Functions of the SX server entry-level models . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switching on/off functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Machine Administration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notification of the system administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 8 8.1 8.2 8.3 8.4 8.4.1 8.4.1.1 8.4.1.2 8.4.1.3 8.4.1.4 8.4.2 8.4.3 The X2000 user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notes on configuring PRIMEPOWER ServerView domains . . . . . . . . . . . . . . . . . . . . Starting PRIMEPOWER ServerView Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Privilege concept with Role-Based Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 9.6 9.6.1 9.6.1.1 9.6.1.2 9.6.2 9.6.2.1 9.6.2.2 9.6.2.3 9.6.3 9.7 9.7.1 9.7.2 9.7.2.1 9.7.2.2 9.7.2.3 9.7.2.4 9.7.2.5 9.7.2.6 9.7.2.7 9.7.3 9.7.3.1 9.7.3.2 Local and remote communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating the TNS entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 11.3 PRIMEPOWER ServerView Suite application “Tools” . . . . . . . . . . . . . . . . . . . . . . . . . 332 12 12.1 12.2 12.3 12.4 What if ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Self-Loading Emergency Dump - SLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . sx.diag command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 14.3.2 14.3.3 Automatic system operation via ATOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 Use as NTP time server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents U41272-J-Z385-3-76
SX Series Business Servers Operation and Administration Target group The manual is intended for privileged users (operators, system administrators) of the SX Series Business Servers. Contents The manual contains all the information required to ensure that the SX Series Business Servers are ready for use. This includes helpful information on configuring the system and a description of important functions for system operation and administration. Edition: June 2005 File: sx_bv.
Fujitsu Siemens computers GmbH User Documentation 81730 Munich Germany Comments Suggestions Corrections Fax: (++49) 700 / 372 00000 e-mail: manuals@fujitsu-siemens.com http://manuals.fujitsu-siemens.
Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions. This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed. Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions.
