NonStop NS1000 Planning Guide (H06.08+)

ContentsSection
This chapter introduces the Integrity NonStop NS1000
system.
Chapter 4 (page 37)
This chapter includes topics to consider when you are
planning or upgrading the installation site.
Chapter 5 (page 49)
This chapter describes the guidelines for implementing
the modular hardware.
Chapter 6 (page 75)
This chapter shows example configurations of the
Integrity NonStop NS1000 modular hardware.
Chapter 7 (page 93)
This appendix identifies the cables used with the Integrity
NonStop NS1000 hardware.
Appendix A (page 107)
This appendix introduces the control, configuration, and
maintenance tools used in a Integrity NonStop NS1000
system.
Appendix B (page 109)
This appendix lists the manuals that support the Integrity
NonStop NS1000 server.
Appendix C (page 123)
Notation Conventions
General Syntax Notation
This list summarizes the notation conventions for syntax presentation in this manual.
UPPERCASE LETTERS
Uppercase letters indicate keywords and reserved words. Type these items exactly as shown.
Items not enclosed in brackets are required. For example:
MAXATTACH
Italic Letters
Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed
in brackets are required. For example:
file-name
Computer Type
Computer type letters indicate:
• C and Open System Services (OSS) keywords, commands, and reserved words. Type
these items exactly as shown. Items not enclosed in brackets are required. For example:
Use the cextdecs.h header file.
• Text displayed by the computer. For example:
Last Logon: 14 May 2006, 08:02:23
• A listing of computer code. For example
if (listen(sock, 1) < 0)
{
perror("Listen Error");
exit(-1);
}
Bold Text
Bold text in an example indicates user input typed at the terminal. For example:
ENTER RUN CODE
?123
CODE RECEIVED: 123.00
The user must press the Return key after typing the input.
Notation Conventions 11