ClearPath IX Systems Installation and Configuration Guide
ClearPath IX Systems Installation and Configuration Guide ClearPath IX Systems Installation and Configuration Guide
Installation Checklists and Tips Changing SPO Aliases The SPO aliases listed in Table 2–2 are automatically assigned to some host names for predefined SPO/HMP Console configurations. If you must change an alias for some reason, perform the steps described in 16.4 to modify the SPO/HMP Console default configurations. For example, if you have a second ClearPath IX server on the same LAN as another ClearPath IX server, you could change the names for the second ClearPath IX server as described in 16.4. Configuring CMS 1100 Sites must configure CMS 1100 to define LAN connections for Intel nodes, IP addresses for OS 2200 nodes and system consoles, Simple Network Management Protocol (SNMP) Agent communities for SysAdmin, and at least one TCP/IP path to each OS 2200 node so that Integration Expert can be used to further customize the configuration. See 16.1 for more information. Changing Passwords Following Installation Throughout the installation procedures, predefined passwords are used to simplify initial installation of the software, or they are supplied for preinstalled software. To prevent unauthorized access to data or programs, the site must change those passwords following hardware RFU. Modifying Windows NT/2000 Server Network Settings after Installation Network settings that you enter during installation can be modified later. (There are two exceptions; see below.) If you are unsure of a particular value while you are installing a server, you can enter what you believe is correct and change it later if you discover an error. If you expect to make such changes, it is recommended that you do not connect the server to the client’s network until you have made the corrections. Otherwise you risk disrupting the client’s network operation. Two items cannot be changed without a reinstallation: • A server’s operation mode (stand-alone server, primary domain controller, or backup domain controller). • A server’s DNS domain. IIS does not register changes to this value after installation. 2.4. Additional Site Requirements Additional requirements sites should plan for include • Obtaining workstation hardware to support DEPCON (2.4.1). • Planning for a network if they do not currently have one (2.4.2). • Planning to integrate with an existing SPO server (optional), if they already have one (2.4.3). 2–10 Version 009B (Web Only) 7850 5104–009
2.4.1. DEPCON Workstation Requirements Installation Checklists and Tips Sites must provide a workstation on which to run DEPCON. Requirements are listed below. Note: If your ClearPath IX server includes a Windows NT node, you may wish to use that node to provide this capability. • Windows 2000, Windows 95, Windows 98, or Windows NT 3.51 or higher • Minimum processor required for the Windows operating system • 3-1/2-inch diskette drive or access to a network for installation • Minimum memory required for the Windows operating system • A hard disk with a minimum of 6 MB available for the DEPCON software (25MB for a full installation) and enough space for the files you want to print • A monitor with a minimum display resolution of 800 x 600 pixels Refer to the DEPCON Application Configuration and Operations Guide for detailed information. Note: You can connect block multiplexer channel (BMC) printers to the DEPCON workstation only on Windows NT and Windows 2000, not Windows 95 or Windows 98. 2.4.2. Planning for ClearPath IX Server Installation as a Private Network Note: For additional guidance on the use of Internet addresses, read the Internet Engineering Task Force (IETF) Request for Comments (RFC) 1918, which can be found on the Web. A site without an existing TCP/IP network can initially set up a private network by selecting IP numbers reserved by the IANA for private Internets (from 192.168.1.xxx to 192.168.255.xxx—excluding the range used by Unisys for the internal FDDI LAN). Using addresses reserved for private networks is an easy way to get started. But to later connect to the external Internet the site must get official IP addresses and reconfigure all server components with the official addresses. 7850 5104–009 Version 009B (Web Only) 2–11
- Page 9 and 10: Contents 4.4. Installing and Config
- Page 11 and 12: Contents 8.4. Installing the UnixWa
- Page 13 and 14: Contents 11.6. Configuring the FTP
- Page 15 and 16: Contents 14.4. Installing DSPER ...
- Page 17 and 18: Appendix D. Configuring the FDDI In
- Page 19 and 20: Figures 1-1. ClearPath IX Server Co
- Page 21 and 22: Tables 1-1. Operating System Levels
- Page 23 and 24: Examples 14-1. A Minimum CMS 1100 C
- Page 25 and 26: About This Guide Purpose Scope This
- Page 27 and 28: How to Use This Guide About This Gu
- Page 29 and 30: About This Guide Section 15. Instal
- Page 31 and 32: About This Guide ClearPath HMP IX S
- Page 33 and 34: About This Guide This guide gives c
- Page 35 and 36: About This Guide OS 2200 Exec Syste
- Page 37 and 38: Notation Conventions About This Gui
- Page 39 and 40: Section 1 Introduction and Installa
- Page 41 and 42: Table 1-2. ClearPath IX Server Comp
- Page 43 and 44: 1.2.2. Installation Procedure Overv
- Page 45 and 46: Introduction and Installation Overv
- Page 47 and 48: • Configure a resilient 2200 node
- Page 49 and 50: External Communications Interface O
- Page 51 and 52: Section 2 Installation Checklists a
- Page 53 and 54: Table 2-1. General Installation Inf
- Page 55 and 56: Component Windows 2000 or Windows N
- Page 57 and 58: 2.3. Installation Tips Caution Inst
- Page 59: Finding Correct UnixWare and EBRS L
- Page 63 and 64: Caution Installation Checklists and
- Page 65 and 66: Installation Checklists and Tips 3.
- Page 67 and 68: Section 3 Installing Windows 2000 A
- Page 69 and 70: Installing Windows 2000 Advanced Se
- Page 71 and 72: Installing Windows 2000 Advanced Se
- Page 73 and 74: Installing Windows 2000 Advanced Se
- Page 75 and 76: Installing Windows 2000 Advanced Se
- Page 77 and 78: Installing Windows 2000 Advanced Se
- Page 79 and 80: Installing Windows 2000 Advanced Se
- Page 81 and 82: Installing Windows 2000 Advanced Se
- Page 83 and 84: Installing Windows 2000 Advanced Se
- Page 85 and 86: Installing Windows 2000 Advanced Se
- Page 87 and 88: Installing Windows 2000 Advanced Se
- Page 89 and 90: Installing Windows 2000 Advanced Se
- Page 91 and 92: Installing Windows 2000 Advanced Se
- Page 93 and 94: Installing Windows 2000 Advanced Se
- Page 95 and 96: Section 4 Installing Windows NT Ser
- Page 97 and 98: Installing Windows NT Server, Enter
- Page 99 and 100: Installing Windows NT Server, Enter
- Page 101 and 102: Installing Windows NT Server, Enter
- Page 103 and 104: Installing Windows NT Server, Enter
- Page 105 and 106: Installing Windows NT Server, Enter
- Page 107 and 108: Installing Windows NT Server, Enter
- Page 109 and 110: Installing Windows NT Server, Enter
<strong>Installation</strong> Checklists <strong>and</strong> Tips<br />
Changing SPO Aliases<br />
The SPO aliases listed in Table 2–2 are automatically assigned to some host names for<br />
predefined SPO/HMP Console configurations. If you must change an alias for some<br />
reason, perform the steps described in 16.4 to modify the SPO/HMP Console default<br />
configurations. For example, if you have a second <strong>ClearPath</strong> <strong>IX</strong> server on the same LAN as<br />
another <strong>ClearPath</strong> <strong>IX</strong> server, you could change the names for the second <strong>ClearPath</strong> <strong>IX</strong><br />
server as described in 16.4.<br />
Configuring CMS 1100<br />
Sites must configure CMS 1100 to define LAN connections for Intel nodes, IP addresses for<br />
OS 2200 nodes <strong>and</strong> system consoles, Simple Network Management Protocol (SNMP) Agent<br />
communities for SysAdmin, <strong>and</strong> at least one TCP/IP path to each OS 2200 node so that<br />
Integration Expert can be used to further customize the configuration.<br />
See 16.1 for more information.<br />
Changing Passwords Following <strong>Installation</strong><br />
Throughout the installation procedures, predefined passwords are used to simplify initial<br />
installation of the software, or they are supplied for preinstalled software. To prevent<br />
unauthorized access to data or programs, the site must change those passwords following<br />
hardware RFU.<br />
Modifying Windows NT/2000 Server Network Settings after <strong>Installation</strong><br />
Network settings that you enter during installation can be modified later. (There are two<br />
exceptions; see below.) If you are unsure of a particular value while you are installing a<br />
server, you can enter what you believe is correct <strong>and</strong> change it later if you discover an<br />
error. If you expect to make such changes, it is recommended that you do not connect the<br />
server to the client’s network until you have made the corrections. Otherwise you risk<br />
disrupting the client’s network operation.<br />
Two items cannot be changed without a reinstallation:<br />
• A server’s operation mode (st<strong>and</strong>-alone server, primary domain controller, or backup<br />
domain controller).<br />
• A server’s DNS domain. IIS does not register changes to this value after installation.<br />
2.4. Additional Site Requirements<br />
Additional requirements sites should plan for include<br />
• Obtaining workstation hardware to support DEPCON (2.4.1).<br />
• Planning for a network if they do not currently have one (2.4.2).<br />
• Planning to integrate with an existing SPO server (optional), if they already have one<br />
(2.4.3).<br />
2–10 Version 009B (Web Only) 7850 5104–009