NonStop S-Series System Expansion and Reduction Guide
Table Of Contents
- NonStop S-Series System Expansion and Reduction Guide
- What’s New in This Guide
- About This Guide
- 1 The Resizing Process
- 2 Planning System Expansion
- 3 Planning System Reduction
- 4 Reducing a System Online
- 1.Prepare the Donor System for Reduction
- 2.Record Information About the Donor System
- 3.Prepare Both ServerNet Fabrics
- 4.Inventory Enclosures to Be Removed
- 5.Prepare and Stop Devices and Processes
- 6.Ensure Devices and Processes Are Stopped
- 7.Delete Devices and Processes If Necessary
- 8.Prepare Enclosures for Removal
- 9.Finish the Reduction
- 10.Remove Other Cables From Powered-Off Enclosures
- 11.Physically Remove Enclosures From the System
- Adding Enclosures to Another System
- 5 Reducing a System Offline
- 6 Expanding a System Online
- Preparation for Online Expansion
- 1.Prepare Target System for Expansion
- 2.Record Information About Target System
- 3.Prepare Target System for Addition of Block
- 4.Save Current Target System Configuration
- 5.Copy SP Firmware File From the Target System to the System Console
- 6.Finish Gathering Information
- 7.Connect a System Console to the Enclosure
- 8.Change Group Number of Enclosure to 01
- 9.Power On Enclosure
- 10.Verify Connection Between System Console and Enclosure
- 11.Configure System Console and Enclosure
- 12.Verify SP Firmware Is Compatible
- 13.Update SP Firmware in Enclosure If Necessary
- 14.Configure Topology of Enclosure If Necessary
- 15.Power Off Enclosure
- 16.Repeat Steps 6 Through 15 If Necessary
- 17.Assemble Enclosures Into a Block
- 18.Change Group Numbers of Block to Fit Target System
- 19.Disconnect System Console From Block
- 20.Power On Added Block
- 21.Cable Block to Target System
- 22.Verify Resized Target System
- 23a.Update Firmware and Code in Block (Using TSM)
- 23b.Update Firmware and Code in Block (Using OSM)
- 24.Reload Processors in Block If Necessary
- 25.Verify Operations in Added Block
- 26.Configure CRUs in Added Block
- 7 Troubleshooting
- A Common System Operations
- Determine the Processor Type
- Determine the ServerNet Fabric Status
- Determine the Product Versions of the OSM Client Software
- Determine the Product Version of the TSM Client Software
- Move the System Console
- Stop the OSM or TSM Low-Level Link
- Start a Startup TACL Session
- Start the OSM or TSM Low-Level Link
- Start the OSM Service Connection or TSM Service Application
- B ServerNet Cabling
- C Checklists and Worksheets
- D Stopping Devices and Processes
- Safety and Compliance
- Glossary
- Index
Glossary
G-Series Common Glossary
Glossary-65
node
node. (1) A uniquely identified computer system connected to one or more other computer
systems in a network. See also Expand node
and ServerNet node. (2) An endpoint in a
ServerNet fabric, such as a processor or ServerNet addressable controller (SAC).
node number. A number used to identify a member system in a network. The node number
is usually unique for each system in the network. See also node
and ServerNet node
number.
node-numbering agent (NNA). A field-programmable gate array (FPGA) in a single-mode
fiber-optic (SMF) plug-in card (PIC) that translates the node number of each ServerNet
packet entering or exiting the external ServerNet fabrics.
node-numbering agent (NNA) plug-in card (PIC). A plug-in card (PIC) for the modular
ServerNet expansion board (MSEB) that supports the node-numbering agent (NNA)
interface.
node routing ID. See ServerNet node routing ID.
noncanonical input mode. For an Open System Services (OSS) process, a terminal input
mode in which data is made available to the process when a timer expires or when a
certain number of characters have been entered. Noncanonical data is not grouped
into logical lines of input. This mode is sometimes called block mode or transparent
mode. Contrast with canonical input mode
.
nonclustered. Lacking the quality of belonging to a cluster.
nonconfigured object. An object that comes into existence after Subsystem Control
Facility (SCF) is running and that was created in response to activity outside the SCF
environment. An SCF STATUS command can display the name of a nonconfigured
object, but its state is UNKNOWN.
nondedicated (public) LAN. A local area network (LAN) connected to the Ethernet ports
on an Ethernet 4 ServerNet adapter (E4SA), Fast Ethernet ServerNet adapter (FESA),
or Gigabit Ethernet ServerNet adapter (GESA). Unlike a dedicated service LAN, a
public LAN supports the connection of many types of servers and workstations.
System consoles can be connected to a public LAN, but such system consoles cannot
use all the OSM or TSM client applications. See also dedicated service LAN
.
nonessential firmware. Code that is used for support routines such as self-test diagnostics
and that can be overwritten during flash programming without affecting the next
power-up operation. Contrast with essential firmware
.
nonexact point. A code location within an accelerated object file that is between memory-
exact points. The mapping between the TNS program counter and corresponding
RISC instructions is only approximate at nonexact points, and interim changes to
memory might have been completed out of order. Breakpoints cannot be applied at
nonexact points. Contrast with memory-exact point
and register-exact point.