ServerNet/FX Adapter Configuration and Management Manual
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Overview of the ServerNet/FX Adapter Subsystem
- 2 Configuring the ServerNet/FX Adapter Subsystem
- 3 Managing the ServerNet/FX Adapter Subsystem
- 4 ServerNet/FX Adapter Subsystem SCF Commands
- 5 Troubleshooting
- A SCF Command Summary
- B Error Messages
- C ServerNet/FX Adapter Self-test Codes
- Glossary
- Index

ServerNet/FX Adapter Subsystem SCF Commands
ServerNet/FX Adapter Configuration and Management Manual—426872-002
4-45
STATUS SUBNET Command
No Neighbor Available No ServerNet/FX adapter has been started along the path. This
occurs if the serial links from the local cluster are physically
broken or disconnected.
Poor Quality Of the 10,000 special control packets transmitted to test line
quality, less than 9990 arrived. The serial link in this direction
failed.
Wired To Wrong Bus The neighbor’s X adapter has been accidentally connected to
the local Y ServerNet/FX adapter or the neighbor’s Y adapter
has been accidentally connected to the local X ServerNet/FX
adapter; reconnect the adapter.
Wired To Wrong Side The neighbor’s left or right link has been accidentally connected
to the local right or left side; reconnect the links properly.
Dropped Data Frames More than 4 data frames were dropped over the last poll. The
link may be going bad. It will be declared usable after 10
minutes. Check the Ring Topology field to see where the break
in the ring occurred. If the Ring Topology field lists no cluster
along the path for $ZZFOX.#X or $ZZFOX.#Y, check that the
local ServerNet/FX adapter is started by using the STATUS
LBU command.
Dropped Sync Frames More than 2 sync frames were dropped over the sample
interval. Either the link or the neighbor is about to fail. Check
the Ring Topology field to see where the break in the ring
occurred. If the Ring Topology field lists no cluster along the
path for $ZZFOX.#X or $ZZFOX.#Y, check that the local
ServerNet/FX adapter is started by using the STATUS LBU
command.
Transient Spike Event More than three spikes occurred in 100 status polls. A spike is
any of the following events:
Squelch
Invalid neighbor
Neighbor changed
Dropped sync frames
The link is declared usable when fewer than three spikes
occurred during the last 100 status polls.
Protocol Timeout The low-level FOX monitor process ($ZZFOX) has timed out.
This usually occurs when a neighbor declares the link down.
The link is declared usable when the local cluster receives FOX
monitor protocol packets again.
Table 4-6. Ring Termination States of the FOX Ring Subnetwork (page 2 of 3)
Ring Termination Status Description