SEB Failure Indicators and Diagnostic Tools
SEB Failure Indicators and Diagnostic Tools
Symptom
These symptoms can indicate that an SEB is failing:
For G06.04 and later: A fabric object (Internal_SvNet_Fabric-X or
Internal_SvNet_Fabric-Y) appears yellow in the tree pane of the Management
window of the OSM Service Connection or the TSM Service Application. A
corresponding alarm calls out an SEB as the most probable failed component.
●
An amber LED indicator light is displayed on an SEB.●
A barrier error (displayed as a Failure Event message in the Event Viewer of
OSM, TSM, or Windows).
●
A CRC error (displayed as a CRC error in the Event Viewer of OSM or TSM).●
Note: SEBs seldom fail. Before replacing an SEB, check to see that SEB cables
are securely connected. Many apparent SEB failure symptoms can be caused by
poorly connected cables.
Version
All
Problem
N.A.
Fix
Use the Replace SEB or MSEB guided procedure. See the Guided
Procedures page for information on this guided procedure.
Diagnostic Tools and Commands
Tool or
Command...
Function... Supported
Versions or
RVUs...
Location...
SCF STATUS
ServerNet
command
To verify the
processor-to-processor
ServerNet status.
All G-series
RVUs.
NonStop Kernel operating system
OSM or TSM
Group
Connectivity
ServerNet Path
Test action
To perform an SP-level path
test for all paths on the
ServerNet fabric between
SPs in the processor groups
and all IOMF groups in the
system.
OSM and
TSM client 7.0
and later.
OSM Service Connection or TSM
Service Application under the
internal ServerNet fabric object.