BladeCluster Solution Manual

BladeCluster Software (H06.20 and J06.09 RVUs)
All of the required software shown in this table is included in the H06.20 and J06.09 RVUs and
can be installed on H06.14/J06.04 and later RVUs without requiring a system load.
Table 5 Software Requirements for BladeClusters (H06.20 and J06.09 RVUs)
Software Process Revision (SPR)Software Component
T0509H01 AAGExpand/ServerNet profile
T0502H01 ABASANMAN
1
T0294H01 ABBSNETMON/MSGMON
2
T4805A01 AAHME Firmware
NonStop BladeSystems (J-series RVUs only)
T0815H01 AAAServerNet Switch FPGA Firmware
NonStop BladeSystems (J-series RVUs only)
T2805A01 AASME Firmware
NonStop NS16000 Series Systems (H-series RVUs only)
T5808H01 ABJSP to NSK Event Translator
T6522H01 AAPNSK Service Processor I/O Library (SPIOLIB)
T0633G07 ABHOSM Low-Level Link
T0682H02 ACCOSM Service Connection Suite
3
T0988H01BladeCluster License File
4
T0999H01Interzone License File
5
1
CAUTION: You should neither configure nor start the $ZZSMN (SANMAN) process unless the BladeCluster will be
connected to a 6700 series ServerNet cluster. The SANMAN process supports 6770 or 6780 ServerNet cluster switches
and is not useful unless these switches are present.
2
A newer SNETMON/MSGMON SPR provides support for multi-zone BladeCluster/6700 configurations in which the
zones are connected only along the 6700 cluster fabrics. For details, refer to “Important Considerations for Multi-Zone
Topologies” (page 17).
3
A newer OSM SPR provides an alarm suppression feature and is supported on this BladeCluster release. For more
information, refer to “Using OSM to Suppress BladeCluster Alarms” (page 83).
4
The BladeCluster Solution Base License (T0988H01) is not required for 6700 series ServerNet clusters that only connect
to 6700 series fabrics.
5
The interzone license file is required only in anchor nodes of multi-zone BladeCluster topologies with inter-zone distances
up to 25 km.
Software Requirements for Previous Releases of BladeCluster 25