 |
» |
|
|
|
|  | |
zx25d 500 The X.25
subsystem is not up! Unable to process msg. - Explanation:
An X.25 related event message or a request from
an application program (as a result of a call to one of the zx25...()
routines) has arrived on the X.25 Protocol driver's event
handler, however, the X.25 subsystem is currently shutdown or has
not been initialized. Therefore, the event message has been discarded. - Action:
No action is necessary. This is an informational message.
However, you may want to make sure an entry exists in the /opt/acc/cfg/zmasterd_list file to schedule
the zx25d_init program.
zx25d 501 Message
received from an illegal X.25 link ZLU (<#>)! - Explanation:
An event message arrived on the X.25 driver's
inbound event handler but the event did not correspond to any of
the known X.25 link ZLUs. Most likely a user application has inadvertently
used the wrong program ZLU when setting up a receiver for status
and/or data messages. - Action:
No action is necessary. This is an informational message.
zx25d 502 Unknown
msg type (<#>) received from ZLU <#>! - Explanation:
The ZCOM message header returned to the X.25 protocol
driver contained a message type value (in the mid.mstype field)
that is unexpected or unknown. Most likely a user application has
inadvertently sent a message to the wrong ZCOM program ZLU. - Action:
No action is necessary. This is an informational message.
zx25d 503 No Logical
Channel Number configured for PVC ZLU <#>. An
LCN will be dynamically selected for this PVC. - Explanation:
During the initialization of an X.25 link, the X.25 protocol
driver detected a PVC ZLU entry that was incorrectly configured
and did not contain a Logical Channel Number in the Poll word. The
X.25 driver will automatically assign an unused LCN to this PVC
ZLU (if available). Note that the ZCOM utility zmntr can
be used to examine the LCN configured for each PVC ZLU. - Action:
No action is necessary. This is an informational message.
However, it is recommended that you correct the configuration for
this PVC.
zx25d 504 Duplicate
LCN (<#>) configured for PVC ZLU <#>.
A new LCN will be dynamically selected for this PVC. - Explanation:
During the initialization of an X.25 link, the X.25 protocol
driver detected a PVC ZLU entry that was incorrectly configured
and contained the same Logical Channel Number in the Poll word as
another PVC ZLU on the same X.25 link. The X.25 driver will automatically
assign an unused LCN to the indicated PVC ZLU (if available). Note
that the ZCOM utility zmntr can
be used to examine the LCN configured for each PVC ZLU. - Action:
No action is necessary. This is an informational message.
However, it is recommended that you correct the configuration for
this PVC.
zx25d 505 There are
more PVCs configured (<#>) than subscribed to (<#>)
for the X.25 Link ZLU <#>. - Explanation:
During the initialization of an X.25 link, the X.25 protocol
driver detected that there were more PVC ZLU terminal entries defined
than were specified in the X.25 subscription parameters. That is,
the value of the last_pvc parameter
is less than the total number of PVC ZLUs defined. The PVC ZLUs
definitions that exceed the last_pvc parameter
value will not be available for use. - Action:
No action is necessary. This is an informational message.
However, it is recommended that you correct the TTGEN configuration
file.
zx25d 506 There are
more two-way SVCs configured (<#>) than subscribed
to (<#>) for the X.25 Link ZLU <#>. - Explanation:
During the initialization of an X.25 link, the X.25 protocol
driver detected that there were more two-way (x25.svc.io) SVC ZLU
terminal entries defined than were specified in the X.25 subscription
parameters. That is, the value of the (last_svc
- first_svc) is less than the total number of two-way
SVC ZLUs defined. Some of the SVC ZLUs may not be usable during
run-time operation. - Action:
No action is necessary. This is an informational message.
However, it is recommended that you correct the TTGEN configuration
file.
zx25d 507 There are
more one-way incoming SVCs configured (<#>) than
subscribed to (<#>) for the X.25 Link ZLU <#>. - Explanation:
During the initialization of an X.25 link, the X.25 protocol
driver detected that there were more one-way incoming (x25.svc.in)
SVC ZLU terminal entries defined than were specified in the X.25
subscription parameters. That is, the value of the (last_insvc - first_insvc) is less
than the total number of one-way incoming SVC ZLUs defined. Some
of the SVC ZLUs may not be usable during run-time operation. - Action:
No action is necessary. This is an informational message.
However, it is recommended that you correct the TTGEN configuration
file.
zx25d 508 There are
more one-way outgoing SVCs configured (<#>) than
subscribed to (<#>) for the X.25 Link ZLU <#>. - Explanation:
During the initialization of an X.25 link, the X.25 protocol
driver detected that there were more one-way outgoing (x25.svc.out)
SVC ZLU terminal entries defined than were specified in the X.25
subscription parameters. That is, the value of the (last_outsvc - first_outsvc) is less
than the total number of one-way outgoing SVC ZLUs defined. Some
of the SVC ZLUs may not be usable during run-time operation. - Action:
No action is necessary. This is an informational message.
However, it is recommended that you correct the TTGEN configuration
file.
zx25d 509 Link <#>:
Call collision on VC ZLU <#> (LCN <#>)
occurred. The inbound call has been ignored. Mux= <#>,
Port= <#>, Subchannel= <#>. - Explanation:
An Incoming CALL packet arrived with the same LCN as
an outbound CALL Request just sent. This condition is known as a call collision and as required by
the ITU-T specification, the inbound call has been discarded (ignored).
This message is only logged if the X.25 link is a DTE. - Action:
No action is necessary. This is an informational message.
zx25d 510 Link <#>:
Call collision on VC ZLU <#> (LCN <#>)
occurred. The outbound call has been lost. Mux= <#>,
Port= <#>, Subchannel= <#>. - Explanation:
An Incoming CALL packet arrived with the same LCN as
an outbound CALL Request just sent. This condition is known as a call collision and as required by
the ITU-T specification, the outbound call has been discarded (ignored)
and the Incoming CALL is being processed normally. This message
is only logged if the X.25 link is a DCE. - Action:
No action is necessary. This is an informational message.
zx25d 511 Link <#>:
Call packet received on PVC ZLU <#> (LCN <#>)! The
PVC has been reset. Check your subscription. Mux= <#>,
Port= <#>, Subchannel= <#>. - Explanation:
An Incoming CALL packet arrived with a Logical Channel
Number (LCN) that the X.25 link subscription parameters have configured
as a PVC LCN. A Reset Request has automatically been generated in
response. This indicates that the local system or DXE is incorrectly
configured. Both sides of the link must have matching X.25 subscription
parameters. - Action:
Correct the X.25 subscription parameters, either locally
or at the remote DXE.
zx25d 512 Link <#>:
Call received on SVC ZLU <#> (LCN <#>)
in improper state (<state string>). The inbound
call has been ignored. - Explanation:
An Incoming CALL packet arrived on an LCN whose current
state indicates that this packet is not valid. For example, if an
Incoming CALL arrived and was followed by a second Incoming CALL
with the same LCN value, the second Incoming CALL packet would be
invalid. The <state string> parameter indicates
the current state that the LCN is in. Possible state
string values are: - Unusable=
The ZLU/LCN is not available. - Disabled=
The ZLU/LCN is currently disabled. - Enabled=
The ZLU/LCN is enabled but not usable (Link is down). - Idle=
The ZLU/LCN is idle (e.g. no call in progress). - Clear Req=
A Clear Request has been sent on this ZLU/LCN. - Clear Ind=
A Clear Indication has been received on this ZLU/LCN. - Call Req=
A Call Request has been sent on this ZLU/LCN. - Call Ind=
An Incoming Call has been received on this ZLU/LCN. - Call Collision=
A Call Collision has occurred on this ZLU/LCN. - Xfer Read=
Ready to transfer data on this LCN. - Reset Req=
A Reset Request has been sent on this ZLU/LCN. - Reset Ind=
A Reset Indication has been received on this ZLU/LCN. - Abort=
Error recovery for inbound packet on unassigned
LCN.
- Action:
No action is necessary. This is an informational message.
zx25d 513 Link <#>:
Call confirm received on Idle LCN <#>. A clear has
been issued on the SVC. - Explanation:
An inbound Call Connected packet arrived on an LCN that
had not sent a Call Request packet. That is, this was a spurious
packet on a Logical Channel that was not currently in use. A Clear
Request has been automatically sent in response as required by ITU-T. - Action:
No action is necessary. This is an informational message.
zx25d 514 Link <#>:
Invalid packet received on PVC ZLU <#> (LCN <#>)!
The PVC has been reset. Packet type = <#>. - Explanation:
An X.25 level 3 packet type arrived on a PVC ZLU
that is not allowed for PVCs. Usually this is a packet related to
call establishment. A Reset Request has automatically been sent
in response as required by ITU-T. Note: This may be due to an incorrect/mis-matched
X.25 subscription configuration between the DXE and the local X.25
link. The packet types are as follows: type 35 = Call Request
type 36 = Call Connected
type 37 = Clear Indication
type 38 = Clear Confirmation - Action:
No action is necessary. This is an informational message.
zx25d 515 Link <#>:
X.25 Timeout occurred during restart exchange. Mux= <#>,
Port= <#>, Subchannel= <#>. - Explanation:
A Restart Request was transmitted, however, the remote
DXE did not respond with a Restart Confirmation or Restart Indication
packet within the time allowed (timer T10/T20). Most likely, the
remote DXE is currently powered down or has not been enabled/initialized.
The X.25 protocol driver will continue to retry the Restart Request
until disabled or the remote DXE responds. - Action:
No action is necessary. This is an informational message.
zx25d 516 Link <#>:
Abnormal event (<#>) for L2 state (<#>)!
Event has been ignored! - Explanation:
The X.25 protocol driver received an event type
that is abnormal for the current state of the X.25 link. Most likely
this is due to a minor defect in the X.25 driver. - Action:
In most cases, this message can be ignored. However,
if this message occurs frequently or abnormal behavior is observed,
you should contact your HP support personnel.
zx25d 517 Link <#>:
VC ZLU <#> enable failed. - Explanation:
The X.25 driver received an unsolicited status message indicating
that an application enable of an X.25 VC ZLU has failed. Most likely,
this is due to an internal defect in the X.25 MUX card firmware. - Action:
In most cases, this message can be ignored. However,
if this message occurs frequently or abnormal behavior is observed,
you should contact your HP support personnel.
zx25d 518 Link <#>:
Buffer shortage on port. Mux= <#>, Port= <#>, Subchannel= <#>. - Explanation:
The MUX firmware was unable to find a free buffer
to hold an inbound X.25 protocol packet or could not find a free
buffer to transmit a protocol packet (e.g. RR). The packet has been
lost. This may cause severe operational problems on the X.25 link.
This problem can occur if one or more of the link option words has the IRX and/or NTX bits
set to zero, or the Port-Limit was
set too large, or an application is sending a very large contiguous
message in a single zsend call. - Action:
Make sure that both the IRX and NTX bits are set
in all X.25 link option words. If the Port-Limit parameter value
is larger than 20,000, you might try slightly reducing this value.
Make sure that applications break large messages into smaller chunks
(not to exceed 4096 bytes) and transmit the smaller chunks using
the M-bit as appropriate.
zx25d 519 Link <#>:
zsetql() failed with error <#>! - Explanation:
The zsetql routine
to set the queue limits for the X.25 link ZLU has unexpectedly failed.
This error is ignored by the X.25 driver and the X.25 link can be
used in a normal fashion. - Action:
Examine the specific reason for the failure and
take corrective action if possible. In most other cases, this error
can be safely ignored. However, if the message "transmit
queue limit exceeded" is seen for an X.25 link ZLU, then
a serious error has occurred. If the problem persists and you are
unable to correct it, contact your HP support representative.
zx25d 520 Link <#>:
Call accept received on SVC ZLU <#> (LCN <#>) in
improper state (<state string>). - Explanation:
An inbound Call Connected packet arrived on an LCN whose
current state indicates that this packet is not valid. For example,
if an Incoming CALL arrived and was followed by a Call Connected
packet with the same LCN value, the Call Connected packet would
be invalid. The <state string> parameter indicates
the current state that the LCN is in. Possible state
string values are described in message 512. - Action:
No action is necessary. This is an informational message.
zx25d 521 Link <#>:
Clear confirm received on SVC ZLU <#> (LCN <#>)
in improper state (<state string>). - Explanation:
An inbound Clear Confirmation packet arrived on
an LCN whose current state indicates that this packet type is invalid.
This would be true any time a Clear Confirmation packet arrived
when a Clear Request has not been sent. The <state string> parameter
indicates the current state that the LCN is in. Possible state string values are described
in message 512. - Action:
No action is necessary. This is an informational message.
zx25d 522 Link <#>:
Reset received on SVC ZLU <#> (LCN <#>)
in improper state (<state string>). - Explanation:
An inbound Reset Indication packet arrived on an
LCN whose current state indicates that this packet is not valid.
For example, if an Incoming CALL arrived and was followed by a Reset
Indication packet with the same LCN value, the Reset Indication
packet would be invalid. The <state string> parameter
indicates the current state that the LCN is in. Possible state string values are described
in message 512. - Action:
No action is necessary. This is an informational message.
zx25d 523 Link <#>:
Reset confirm received on SVC ZLU <#> (LCN <#>)
in improper state (<state string>). - Explanation:
An inbound Reset Confirmation packet arrived on
an LCN whose current state indicates that this packet type is invalid.
This would be true any time a Reset Confirmation packet arrived
when a Reset Request has not been sent. The <state string> parameter
indicates the current state that the LCN is in. Possible state string values are described
in message 512. - Action:
No action is necessary. This is an informational message.
zx25d 524 Link <#>:
Illegal packet received! Diagnostic = <#>. Packet = 0x<#>
Pkt length = <#>. - Explanation:
An illegal X.25 level 3 protocol packet has been received
on the indicated link ZLU. That is, a protocol packet whose type
is unknown, unsupported, or contains a format error, or has an illegal
Logical Channel Number. When this occurs, a ITU-T standard diagnostic
code is displayed indicating the reason the packet is illegal, the
first four bytes of the input buffer is dumped (in hex), and the
total length of the packet is displayed. - Action:
No action is necessary. This is an informational message.
zx25d 525 Link <#>:
Facilities data too long (<#> bytes) on inbound call
for SVC zlu <#> (LCN=<#>). Call
cleared! - Explanation:
An Incoming CALL packet arrived with facilities
data that exceeded the maximum permissible size of 109 bytes. The
call has been automatically cleared as required by ITU-T. - Action:
No action is necessary. This is an informational message.
zx25d 526 Link <#>:
Call user data too long (<#> bytes) on inbound call
for SVC zlu <#> (LCN=<#>). Call
cleared! - Explanation:
An Incoming CALL packet arrived with Call User data that
exceeded the maximum permissible size of 128 bytes. The call has
been automatically cleared as required by ITU-T. - Action:
No action is necessary. This is an informational message.
zx25d 527 Link <#>:
Call user data too long (<#> bytes) on inbound call
for SVC zlu <#> (LCN=<#>). No
Fast-Select, call cleared! - Explanation:
An Incoming CALL packet arrived with Call User data that
exceeded the maximum permissible size of 16 bytes for calls without
the Fast-Select facility. The call has been automatically cleared
as required by ITU-T. - Action:
No action is necessary. This is an informational message.
zx25d 528 Link <#>:
Outbound call on zlu <#> (LCN=<#>)
specified Restricted Fast-Select. Call accept not allowed; call
cleared. - Explanation:
An inbound Call Connected packet arrived on a VC whose
outbound Call Request specified the facility Restricted
Fast-Select. When this facility has been specified, it
is illegal for that call to be connected. That is, it is mandatory
for a Clear Request to be transmitted in response to this type of
inbound call. A Clear Request has been sent automatically as required by
ITU-T. - Action:
No action is necessary. This is an informational message.
zx25d 529 Link <#>:
Facilities data too long (<#> bytes) in call accept for
SVC zlu <#> (LCN=<#>). Call
cleared! - Explanation:
An inbound Call Connected packet arrived with facilities
data that exceeded the maximum permissible size of 109 bytes. The
call has been automatically cleared as required by ITU-T. - Action:
No action is necessary. This is an informational message.
zx25d 530 Link <#>:
Call user data too long (<#> bytes) in call connected
for SVC zlu <#> (LCN=<#>). Call
cleared! - Explanation:
An inbound Call Connected packet arrived with Call User
data that exceeded the maximum permissible size of 128 bytes. The
call has been automatically cleared as required by ITU-T. - Action:
No action is necessary. This is an informational message.
zx25d 531 Link <#>:
Call user data not allowed in call connected packet for SVC zlu <#> (LCN=<#>).
Call cleared! - Explanation:
An inbound Call Connected packet arrived that specified
Call User data. However, the original Call Request did not specify
the facility Fast-Select which prohibits
the DXE from sending Call User data in the Call Connected packet.
The call has been automatically cleared as required by ITU-T. - Action:
No action is necessary. This is an informational message.
zx25d 532 Link <#>:
Facilities data too long (<#> bytes) in clear
packet for SVC zlu <#> (LCN=<#>).
Clear req issued. - Explanation:
An inbound Clear Indication packet arrived with facilities
data that exceeded the maximum permissible size of 109 bytes. A
Clear Request has automatically been issued as required by ITU-T. - Action:
No action is necessary. This is an informational message.
zx25d 533 Link <#>:
Call user data too long (<#> bytes) in clear packet for
SVC zlu <#> (LCN=<#>). - Explanation:
An inbound Clear Indication packet arrived with
Call User data that exceeded the maximum permissible size of 128
bytes. A Clear Request has automatically been issued as required
by ITU-T. - Action:
No action is necessary. This is an informational message.
zx25d 534 Link <#>:
Call user data not allowed in clear packet for SVC zlu <#> (LCN=<#>).
Clear request issued. - Explanation:
An inbound Clear Indication packet arrived that specified
Call User data. However, the original Call Request did not specify
the facility Fast-Select which prohibits
the DXE from sending Call User data in the Clear Indication packet.
The call has been automatically cleared as required by ITU-T. - Action:
No action is necessary. This is an informational message.
zx25d 535 Link <#>:
Interrupt pkt on SVC ZLU <#> (LCN <#>)
in improper state (<state string>). Reset or Clear
has been issued. - Explanation:
An inbound Interrupt packet arrived on an LCN whose current
state indicates that this packet type is invalid. For example, if
an Incoming CALL arrived and was followed by a Interrupt packet
with the same LCN value, the Interrupt packet would be invalid.
The <state string> parameter indicates the current
state that the LCN is in. Possible state
string values are described in message 512. - Action:
No action is necessary. This is an informational message.
zx25d 536 Link <#>:
Interrupt confirm pkt on SVC ZLU <#> (LCN <#>) in
improper state (<state string>). Reset or Clear
has been issued. - Explanation:
An inbound Interrupt Confirmation packet arrived
on an LCN whose current state indicates that this packet type is
invalid. This would be true any time an Interrupt Confirmation packet
arrived when an Interrupt packet had not been sent. The <state
string> parameter indicates the current state that the
LCN is in. Possible state string values
are described in message 512. - Action:
No action is necessary. This is an informational message.
zx25d 537 Link <#>:
Invalid Option word for SVC ZLU <#>. Option word
indicated calls can not be sent or received. ZLU will be set to
an SVC.IO in the option word. - Explanation:
The option word for a configured VC indicates where the
VC is an SVC or a PVC. For SVCs, it also indicates if the SVC can
place outbound calls and/or receive inbound calls. This message
indicates that the VC was configured as an SVC that is not allowed
to either receive or send calls. This is illegal. The SVC has automatically
been reconfigured to allow both inbound and outbound calls. - Action:
Correct the configuration of the virtual circuit
ZLU.
|
Printable version
