Gigabit Ethernet ServerNet Adapter Installation and Support Guide

Introduction to the Gigabit Ethernet ServerNet
Adapter (GESA)
Gigabit Ethernet Adapter Installation and Support Guide—523628.005
1-8
Diagnostic Subsystem Interface (Serial Maintenance
Bus)
Diagnostic Subsystem Interface (Serial Maintenance Bus)
The diagnostics subsystem interface is supported by the serial maintenance bus
(SMB). The maintenance subsystem contains the circuitry required to meet the
maintenance system requirements of an active-logic CRU, which includes:
•
Dual-multiplexed SMB ports
•
An MROUTER, which provides redundant access to the maintenance-system
features of the CRU. The maintenance and diagnostic system allow you to:
°
Power the adapter on or off
°
Identify the type, configuration, and revision of the adapter
°
Run scan diagnostics IEEE 1149.1 (JTAG) on JTAG components
°
Initialize the adapter for access to or from the ServerNet
°
Control the adapter’s standard LEDs
•
A serial EEPROM (SEEROM) that provides:
°
Hardware identification (part number and revision)
°
Manufacturing tracking (serial) number
°
MAC addresses
°
CRU visual indicators
°
Power control to the GESA
Power Interface
The GESA receives power through a shielded, high-density, metric connector module.
The connector module consists of two 72-pin blocks and a blade power block. The
connector module also provides attachments to the two SMBs and the two ServerNet
fabrics.
Relationship to the SLSA Subsystem
GESAs are configured and managed through the Subsystem Control Facility (SCF)
interface to the ServerNet LAN Systems Access (SLSA) subsystem. The SLSA
subsystem is preinstalled and preconfigured on NonStop S-series servers and is
started during the system-load sequence.
During the system-load sequence, the persistence manager ($ZPM) starts the primary
and backup LAN Manager (LANMAN) processes ($ZZLAN) in processors 0 and 1. The
LANMAN process then starts the LAN Monitor (LANMON) processes in each
processor of the system and attempts to assign the SAC on a GESA to a LANMON
process. Each LANMON process then initializes the SAC, physical interface (PIF), and