Lucent Technologies Release 7 Manual Do Utilizador
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-1218
PGATE-PT (Packet Gateway Port)
9
connected to the port. This problem can be caused by cabling, data set,
or transmission facility faults. For an RS423 connection, execute the test
port UUCSSpp long command and see the repair procedures for Packet
Gateway Port Remote Loop-Around Test #611.
or transmission facility faults. For an RS423 connection, execute the test
port UUCSSpp long command and see the repair procedures for Packet
Gateway Port Remote Loop-Around Test #611.
If the port speed is administered as a switched port then the CTS will
always be high but the DCD will be low only if there are transmission
problems with the far-end. If this occurs, execute the test port UUCSSpp
long command and see the repair procedures for Packet Gateway
Switched Port Loop-Around Test #599.
always be high but the DCD will be low only if there are transmission
problems with the far-end. If this occurs, execute the test port UUCSSpp
long command and see the repair procedures for Packet Gateway
Switched Port Loop-Around Test #599.
d. This error occurs when the port receives an invalid frame. A frame is
invalid if it is greater than the maximum length, contains CRC errors, or
violates the link level protocol. If this error occurs 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 problem.
Before executing the test port UUCSSpp long command, refer to the
repair procedures for test #611 for special instructions regarding the
execution of this test. Once the repair has been verified as described in
the repair procedures for test #611, the alarm can be cleared by executing
the test port UUCSSpp long clear command.
violates the link level protocol. If this error occurs 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 problem.
Before executing the test port UUCSSpp long command, refer to the
repair procedures for test #611 for special instructions regarding the
execution of this test. Once the repair has been verified as described in
the repair procedures for test #611, the alarm can be cleared 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 Procedure 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 indicates that one
side of the interface has detected a protocol procedural error. Network
Congestion normally indicates 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 code (0 to 255) contained
in each packet is used to offset the base (1024) to produce unique error
types. The auxiliary data value indicates the cause of the error and
whether the error was sent or received. The auxiliary data value is
encoded as follows:
sent to initialize the packet layer interface and cause all calls on the
interface to be cleared. A Local Procedure error usually indicates that one
side of the interface has detected a protocol procedural error. Network
Congestion normally indicates 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 code (0 to 255) contained
in each packet is used to offset the base (1024) to produce unique error
types. The auxiliary data value indicates the cause of the error and
whether the error was sent or received. The auxiliary data 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 due to an DTE Originated Error (i.e.,
cause value). The value of the diagnostic code (1 to 255) contained in
each packet is used to offset the base (2048) to produce unique error
types. Note the diagnostic code of "0" (No Additional Information) is not
logged as this is considered a normal resetting circumstance. Only
an X.25 reset packet is received due to an DTE Originated Error (i.e.,
cause value). The value of the diagnostic code (1 to 255) contained in
each packet is used to offset the base (2048) to produce unique error
types. Note the diagnostic code of "0" (No Additional Information) is not
logged as this is considered a normal resetting circumstance. Only
0
Local Procedure Error received.
3
Network Congestion received.
35768
Local Procedure Error sent.
35771
Network Congestion sent.