This flow control mechanism is based on a common "window"
mechanism.
The basic concept is that the number of outstanding
messages that are associated with a Socket ID in the transmit or
receive ring cannot exceed a predefined number, "application
threshold". Note that the mechanism is based on the number of
messages per application rather than the number of buffers per
application.
FLOWa first flow control hit starts a 128ms timer to allow one more try
FLOWb second flow control hit requests the sending of
OK_TO_SEDN_REQ message via a logged SSD message to
MSDL loadware. Start the 128ms timer
FLOWc third flow control hit asks the data socket to be resynchronized by
MSDL
loadware. Start the 128ms timer
FLOWd fourth flow control hit starts a 128ms timer such that the link is
forced to disable after time out
MSDL local loopback test (NT6D80)
Before beginning this test, the D-channel must be in test state:
ENL TEST x, where x is the logical DCH number
.
To start the local loopback test on the Multi-purpose Serial Data Link (MSDL) card, use the
ENL LLB x command, where x is the logical DCH number.
Then perform the following test:
TEST LLB x
The test checks both MSDL expedited and normal (ring) interfaces.
The response for the expedited interface that carries urgent signaling and maintenance
messages between the system CPU and the MSDL MPU follows:
DCH : X XDU TEST CONFIRM TIME : <time of day> TEST : PASS (or FAIL)
X is the DCH logical number XDU is the expedient message sent around the loop.
The response for the ring interface that transmits operation data between the system CPU and
the MSDL MPU follows:
DCH : X DU TEST CONFIRM TIME : <time of day> TEST : PASS (or FAIL)
D-channel maintenance
68 ISDN Primary Rate Interface Maintenance November 2011
Comments? infodev@avaya.com
To Next Page
Loading...
