DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
Maintenance Object Repair Procedures
9-1218PGATE-PT (Packet Gateway Port)
9
connected to the p ort. This problem can be c aused by cab ling, data set,
or transmission facility faults. For an RS423 connection, exec ute the test
port UUCSSpp long command and see the rep air procedures for Packet
Gateway Port Remote Loop-Around Test #611.
If the port speed is ad ministered as a switched port then the CTS will
always be high but the DCD will b e low only if there are transmission
problems with the far-end. If this oc curs, execute the test port UUCSSpp
long command and see the rep air procedures for Packet Gateway
Switched Port Loop-Around Test #599.
d. This error occurs when the port receives an i nvalid frame. A frame is
invalid if it is greater than the maximum leng th, contains CRC errors, or
violates the link level protocol. If this error oc curs repeatedly, an off-board
WARNING alarm is raised against the port. The Packet Gateway Port
Remote Loop-Around Test (#611) can be used to isolate the p roblem.
Before executing the test port UUCSSpp long command , refer to the
repair procedures for test # 611 for special instructions reg arding the
execution of this test. Once the rep air has been verified as desc ribed in
the repair procedures for test #611, the alarm can be c leared by executing
the test port UUCSSpp long clear command.
e. These errors occur when an X.25 Restart packet is received or sent by the
switch due to a Local Proced ure error or Network Congestion. Restarts are
sent to initialize the packet layer interface and cause all calls on the
interface to be cleared . A Local Procedure error usually indic ates that one
side of the interface has d etected a protocol procedural error. Network
Congestion normally indic ates that the attached network is severely
overloaded and has taken a control measure which entails restarting the
X.25 interface. The value of the X.25 diagnostic c ode (0 to 255) contained
in each packet is used to offset the base (1024) to prod uce unique error
types. The auxiliary data value ind icates the cause of the error and
whether the error was sent or received. The auxiliary d ata value is
encoded as follows:
f. These errors are reported for processor/hop channels and is consistent
with the 1984 CCITT X.25 Recommendation. This error is reported when
an X.25 reset packet is received d ue to an DTE Originated Error (i.e.,
cause value). The value of the diagn ostic code (1 to 255) c ontained in
each packet is used to offset the base (2048) to produc e unique error
types. Note the diagnostic code of "0" (No Additional Information) is not
logged as this is c onsidered a normal resetting c ircumstance. Only
0 Local Procedure Error received.
3 Network Congestion rec eived.
35768 Local Procedure Error sent.
35771 Network Congestion sent .