NonStop NS1200 Planning Guide

ContentsSection
This chapter describes the guidelines for implementing
the modular hardware.
Chapter 4 (page 51)
This chapter shows recommended locations for hardware
enclosures in the modular cabinet.
Chapter 5 (page 63)
This chapter describes the connectivity options for
maintenance and support of an Integrity NonStop NS1200
system.
Chapter 6 (page 67)
This appendix identifies the cables used with the Integrity
NonStop NS1200 hardware.
Appendix A (page 77)
This appendix describes how to use the OSM applications
to manage an Integrity NonStop NS1200 system.
Appendix B (page 79)
This appendix describes the default startup charactistics
for an Integrity NonStop NS1200 server.
Appendix C (page 83)
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.
[ ] Brackets
Brackets enclose optional syntax items. For example:
Notation Conventions 11