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

Planning System Reduction
HP NonStop S-Series System Expansion and Reduction Guide—522465-009
3-7
Example Using the ServerNet Worksheets
1. Choose and Copy the Appropriate Worksheets
This figure shows Worksheets 10 and 11 for a Tetra 16 system.
If the system topology is … Copy these worksheets from Appendix C
Tetra 8 ServerNet Worksheet 9
Tetra 16 ServerNet Worksheets 10 and 11
SEB
54
SEB
52
Group 05
1
2
3
4
6
5
654321
Group
55
55
55
Group
56
55Group
57
55
Group
58
55
Group
59
55
Group
51
Group
Group
15
Group
14
Group
13
Group
12
Group
11
Group
81
Group
82
55
Group
45
Group
44
Group
43
Group
42
Group
41
55
Group
89
55
Group
88
55
Group
87
55
Group
86
55
Group
85
Group 08
1
2345 6
PMF 55
SEB
54
SEB
52
1
2
3
4
6
5
PMF 55
Note 1: This
illustration shows
the maximum
possible number
of I/O
enclosures. Your
service provider
can tell you the
number of I/O
enclosures
supported by
your RVU.
VST392.vsd
ServerNet Communication Pathways: Tetra 16 Topology, Y Fabric
With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration.
With a pen, black out the CRU you plan to remove.
If you are removing a PMF CRU, check this box. Then, on the worksheet for the Y fabric, black out the PMF CRU in slot 55 in the corresponding
enclosure to indicate that this PMF CRU will lose access to the X fabric as well.
On this worksheet, trace pathways of communication through all routers and ServerNet cables that connect to the CRU you plan to remove.
Circle all components and enclosures that will be affected by that CRU removal.
Worksheet 11
Group
21
50
Group
22
Group
23
Group
24
Group
25
50
50
50
50
5
4
6
1
2
3
6
5
4
32
1
Group
02
SEB
53
SEB
51
Group
35
50
Group
34
Group
33
Group
32
Group
31
50
50
50
50
5
4
6
1
2
3
6
5432
1
Group
03
SEB
51
SEB
53
Group
74
50
Group
73
50
Group
72
50
Group
71
50
Group
79
50
Group
78
50
Group
77
50
Group
76
50
Group
75
50
1
2
3
4
6
5
6543
2
1
Group 07
PMF 50
SEB
51
SEB
53
50
Group
64
50
Group
63
50
Group
62
50
Group
61
Group
65
50
Group
66
Group
67
Group
68
Group
69
50
50
50
50
Group 06
654321
SEB
53
SEB
51
5
6
4
3
2
1
SEB
53
SEB
51
Group 05
1
2
3
4
6
5
654321
Group
55
50
50
Group
56
50
Group
57
50
Group
58
50
Group
59
50
Group
51
50
Group
52
50
Group
53
50
Group
54
SEB
53
Group
01
65
4321
50
Group
15
50
Group
14
50
Group
13
50
Group
12
50
Group
11
Group
81
50
Group
82
50
Group
83
50
Group
84
50
50
Group
45
50
Group
44
50
Group
43
50
Group
42
50
Group
41
1
23
4
56
5
6
4
1
2
3
Group
04
SEB
53
SEB
51
50
Group
89
50
Group
88
50
Group
87
50
Group
86
50
Group
85
Group 08
1
2
3456
PMF 50
SEB
53
SEB
51
1
2
3
4
6
5
1
2
3
4
6
5
SEB
51
PMF 50PMF 50
PMF 50
PMF 50 PMF 50
PMF 50
ServerNet Communication Pathways: Tetra 16 Topology, X Fabric
With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration.
With a pen, black out the CRU you plan to remove.
If you are removing a PMF CRU, check this box. Then, on the worksheet for the Y fabric, black out the PMF CRU in slot 55 in the corresponding
enclosure to indicate that this PMF CRU will lose access to the X fabric as well.
On this worksheet, trace pathways of communication through all routers and ServerNet cables that connect to the CRU you plan to remove.
Circle all components and enclosures that will be affected by that CRU removal.
VST387.vsd
Note 1: This
illustration shows
the maximum
possible number
of I/O
enclosures. Your
service provider
can tell you the
number of I/O
enclosures
supported by
your RVU.
Worksheet 10
Remove Enclosures: