Lucent Technologies Stinger, Administration Manual

Page: 297 / 374

Diagnostic Testing
OAM testing
Stinger® Administration Guide 12-9
Total Active Oam Channels=1
Continuity check and monitoring
F4 and F5 OAM continuity tests can be initiated as follows:
Locally, using the command-line interface (CLI).
Remotely, a network peer can send activation/deactivation requests to initiate a
continuity test.
You can start an OAM continuity test locally using the command-line interface by
using the
oam -c|C + command or by setting the parameters in the atm-oam profile.
Locally initiated continuity tests only configure the Stinger system to generate
continuity cells. For both continuity check and OAM defects, events are reported by
way of SNMP traps.
Continuity checks started by a remote peer are not associated with the command-line
interface or a profile. For both continuity check and OAM defects, events are
reported via SNMP traps.
Continuity check implementation
Stinger systems implement the standard OAM continuity check protocol. Note,
however, that any remote deactivate request is accepted by the Stinger unit
regardless of the direction indicated by remote peer. A remote activate request is
accepted only if its specified directions is compatible with local settings (see “While in
the default direction state, what happens when a Stinger unit receives an activation
request” on page 12-9 for details).
When a connection is created, the OAM flow(s) associated with a connection have
their continuity check direction set to
default . The default direction indicates that the
system generates no continuity check cells and does not monitor continuity check
cells. The system also does not send any activation or deactivation requests to the
remote.
Stinger systems support the generation of continuity cells towards the remote peer.
When you start a test using the
oam command or the atm-oam profile, from the
perspective of the Stinger unit, the generation of continuity cells towards the remote
peer is in the A-to-B direction. The A-to-B direction means that the Stinger unit
sends an activate request to the remote peer. Stopping the test resets the direction to
default.
While in the default direction state, what happens when a Stinger unit
receives an activation request
When a Stinger unit is in the default direction and a remote peer sends a continuity
check activate request, the Stinger unit accepts any direction that the remote peer
specifies. The default direction is compatible with any direction sent by the peer. The
A-to-B direction is only compatible when the B-to-A direction is specified by the
remote peer.