ELS Messages for Internet Packet Exchange (IPX)
- Level:
- P-TRACE
- Class:
- FAKE
- Short Syntax:
- IPX.001 source_net
/ source_node
-> dest_net
/ dest_node
ign
- Long Syntax:
- IPX.001 Packet from source_net
/ source_node
for dest_net
/ dest_node
ignored
- Description:
- An IPX packet arrived on a network. The IPX forwarder is
not in this router load. The packet is discarded.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.002 q ovf source_net
/ source_node
-> dest_net
/ dest_node
nt network ID
- Long Syntax:
- IPX.002 Queue overflow, source_net
/ source_node
-> dest_net
/ dest_node
, net network ID
- Description:
- IPX forwarder input queue has overflowed.
- Cause:
- More packets are being received than the forwarder can forward.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.003 bad hst chksm frm source_net
/ source_node
- Long Syntax:
- IPX.003 Bad host checksum from source_net
/ source_node
- Description:
- This message is generated when a packet arrives for this host
with an incorrect checksum.
- Level:
- U-INFO
- Short Syntax:
- IPX.004 err pkt error_type
frm source_net
/ source_node
- Long Syntax:
- IPX.004 Error packet, errno error_type
, received from source_net
/ source_node
- Description:
- This message is generated when an error packet is received.
- Level:
- U-TRACE
- Short Syntax:
- IPX.005 no hndlr for skt destination_socket
typ packet_type
frm source_net
/ source_node
- Long Syntax:
- IPX.005 No handler for socket destination_socket
type packet_type
from source_net
/ source_node
- Description:
- A packet arrived for an
unknown or unsupported socket or type. The packet was a
broadcast packet.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.006 no hndlr for skt destination_socket
typ packet_type
frm source_net
/ source_node
- Long Syntax:
- IPX.006 No handler for socket destination_socket
type packet_type
from source_net
/ source_node
- Description:
- A packet arrived for an
unknown or unsupported socket or type. The packet was addressed
to the router.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.007 no hst addr set for nt network ID
, not enabled
- Long Syntax:
- IPX.007 no host address set for net network ID
, not enabled
- Description:
- The forwarder was bringing up IPX on the specified serial line
interface, but no host address was set so the interface was
not enabled.
- Cause:
- Serial line enabled without setting host address.
- Action:
- Set IPX host address.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.008 SAP bad typ packet_type
frm source_net
/ source_node
- Long Syntax:
- IPX.008 SAP bad type packet_type
from source_net
/ source_node
- Description:
- This message is generated when a packet is received with a
bad SAP type.
- Level:
- C-TRACE
- Short Syntax:
- IPX.009 SAP gen rply frm source_net
/ source_node
- Long Syntax:
- IPX.009 SAP general reply from source_net
/ source_node
- Description:
- SAP has received a General Reply packet from the specified host.
The data in the packet will be used to update the SAP database.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.010 SAP tbl ovrfl, dsc type service_type
nm [ service_name
]
- Long Syntax:
- IPX.010 SAP table overflow, discarded type service_type
name [ service_name
]
- Description:
- A new entry cannot be added
to the SAP table because it is full. The new entry is
discarded.
- Cause:
- SAP table is smaller than number of services on IPX internet.
- Action:
- Increase the size of the SAP table.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.011 SAP srvc typ service_type
nm [ service_name
] mvd to new_net
/ new_node
- Long Syntax:
- IPX.011 SAP service type service_type
name [ service_name
] moved to new_net
/ new_node
- Description:
- A SAP General Reply was received with a different network/address
pair than is presently in the SAP database.
- Cause:
- Duplicate name assigned for service.
- Action:
- Eliminate duplicated name.
- Cause:
- Service physically moved faster than SAP timeout.
- Action:
- Do not move services so fast.
- Level:
- U-INFO
- Short Syntax:
- IPX.012 SAP del typ service_type
nm [ service_name
]
- Long Syntax:
- IPX.012 SAP deleted type service_type
name [ service_name
]
- Description:
- A SAP table entry has been declared dead. It will be
advertised as unreachable for another 60 seconds, and then
removed from the SAP table.
- Cause:
- No SAP General Reply has been heard containing
data on this service type/name pair in 240 seconds.
- Action:
- None, unless service should be up.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.013 SAP bd nearest qry frm source_net
/ source_node
ln length
- Long Syntax:
- IPX.013 SAP bad length Nearest Service Query from source_net
/ source_node
, len length
- Description:
- A SAP Nearest Service Query was received with an illegal
length.
- Cause:
- Programming error in remote node.
- Level:
- C-TRACE
- Short Syntax:
- IPX.014 SAP nearest qry frm source_net
/ source_node
- Long Syntax:
- IPX.014 SAP nearest query from source_net
/ source_node
- Description:
- A SAP Nearest Service Query was received from the specified
node. It will be answered as appropriate.
- Level:
- C-TRACE
- Short Syntax:
- IPX.015 SAP gen qry frm source_net
/ source_node
- Long Syntax:
- IPX.015 SAP general query from source_net
/ source_node
- Description:
- A SAP General Service Query was received from the specified
node. It will be answered as appropriate.
- Level:
- U-TRACE
- Short Syntax:
- IPX.016 SAP qry sent nt network ID
- Long Syntax:
- IPX.016 SAP General Service Query sent, net network ID
- Description:
- A SAP General Service Query was sent on the specified network.
One is sent on a network when it comes up.
- Level:
- UI-ERROR
- Class:
- OOM
- Short Syntax:
- IPX.017 No mem fr SAP bcst nt network ID
, count
pkts snt
- Long Syntax:
- IPX.017 No memory for SAP General Service Query or Reply, net network ID
, count
packets sent
- Description:
- This message is generated when no buffer is available to send
a SAP General Service Query or Reply packet. Since a General Service
Reply can require multiple packets, the message notes how many
packets were sent on this network before they ran out.
- Level:
- C-TRACE
- Short Syntax:
- IPX.018 SAP gen rply sent nt network ID
, count
pkts
- Long Syntax:
- IPX.018 SAP General Service Reply sent, net network ID
, count
packets
- Description:
- A SAP General Service Reply has just been sent on the specified
network. It took the specified number of packets to send the
complete SAP database.
- Level:
- P-TRACE
- Short Syntax:
- IPX.019 NB brd source_net
/ source_node
-> dest_net
/ dest_node
, nt network ID
, hop_count
hops
- Long Syntax:
- IPX.019 NETBIOS broadcast source_net
/ source_node
-> dest_net
/ dest_node
, net network ID
, hop_count
hops
- Description:
- A NETBIOS emulation multi-network broadcast packet has been
received for forwarding to other IPX networks. The IPX hop
count indicates how many routers it has been through.
- Level:
- U-TRACE
- Short Syntax:
- IPX.020 NB too many hops frm source_net
/ source_node
nt network ID
, ign
- Long Syntax:
- IPX.020 NETBIOS too many hops from source_net
/ source_node
net network ID
, ignored
- Description:
- A NETBIOS emulation broadcast packet has been through more than
8 routers. It will be dropped.
- Cause:
- Normal looping due to multiple paths from source of broadcast packet.
- Action:
- None. This is a normal consequence of the protocol used.
- Cause:
- IPX NETBIOS traffic trying to go across more than 8 hops
(networks) between source and destination.
- Action:
- Reconfigure network.
- Level:
- C-TRACE
- Short Syntax:
- IPX.021 NB frm source_net
/ source_node
nt network ID
, already on connected_network
, ign
- Long Syntax:
- IPX.021 NETBIOS from source_net
/ source_node
net network ID
, already on connected_network
, ignored
- Description:
- This IPX NETBIOS emulation broadcast packet has already been
on one of the directly attached networks. It will not be forwarded,
as that would generate a duplicate.
- Cause:
- This is a normal side effect of the protocol used.
- Level:
- UI-ERROR
- Class:
- OOM
- Short Syntax:
- IPX.022 NB frm source_net
/ source_node
, no mem to cpy
- Long Syntax:
- IPX.022 NETBIOS from source_net
/ source_node
, no memory to copy
- Description:
- No memory available to make working copy of this NETBIOS emulation
packet to send it out multiple interfaces.
- Level:
- CI-ERROR
- Short Syntax:
- IPX.023 NB frm source_net
/ source_node
, non-brd nt network ID
unsupp
- Long Syntax:
- IPX.023 NETBIOS from source_net
/ source_node
, non-broadcast net network ID
unsupported
- Description:
- Attempting to send NETBIOS emulation packet on network
that does not support broadcast. The packet will not be
sent on that network.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.024 NB frm source_net
/ source_node
, un-numbrd nt network ID
unsupp
- Long Syntax:
- IPX.024 NETBIOS from source_net
/ source_node
, un-numbered net network ID
unsupported
- Description:
- Attempting to send NETBIOS emulation packet on a network
with no network number. The packet will not be sent on that
network.
- Cause:
- Serial line network operating without a network number.
- Action:
- If you want to run NETBIOS emulation across a serial line network,
it must have a network number.
- Level:
- UI-ERROR
- Class:
- OOM
- Short Syntax:
- IPX.025 NB frm source_net
/ source_node
, no buf to cpy
- Long Syntax:
- IPX.025 NETBIOS from source_net
/ source_node
, no buffer to copy
- Description:
- No packet buffer available to copy this NETBIOS emulation broadcast
packet into in order to send it on a network.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.026 NB snd dsc, nt network ID
, rsn reason_code
- Long Syntax:
- IPX.026 NETBIOS send discarded, net network ID
, reason reason_code
- Description:
- An outgoing NETBIOS emulation broadcast packet was not successfully
transmitted for the reason indicated by the error code.
- Cause:
- Miscellaneous handler error. (Reason code 1.)
- Action:
- Check for error messages from the handler for network ID.
- Cause:
- Output queue overflow, or other flow control. (Reason code
2.)
- Action:
- Alleviate congestion.
- Cause:
- The network is down. (Reason code 3.)
- Action:
- See why the handler thinks the network is down.
- Cause:
- The handler dropped the packet to avoid looping, or bad broadcast.
(Reason code 4.)
- Action:
- Check your configuration.
- Cause:
- The host is down. (Reason code 5.)
- Action:
- See why the handler thinks the host is down.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.027 bad RIP typ RIP_opcode
frm source_net
/ source_node
- Long Syntax:
- IPX.027 Bad RIP type RIP_opcode
from source_net
/ source_node
- Description:
- RIP packet received which was not a request or response.
- Cause:
- Programming error on remote node.
- Level:
- C-TRACE
- Short Syntax:
- IPX.028 RIP resp frm source_net
/ source_node
- Long Syntax:
- IPX.028 RIP response from source_net
/ source_node
- Description:
- This message is generated when a RIP response packet is
received. It will be parsed, and the data incorporated into
the routing table.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.029 bad net network
in RIP frm source_net
/ source_node
- Long Syntax:
- IPX.029 Bad network network
in RIP from source_net
/ source_node
- Description:
- A RIP response was received with an entry having a network number
of 00000000 or FFFFFFFF. That entry will be ignored.
- Cause:
- Programming error on remote node.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.030 net route table ovrfl, dscrd network
- Long Syntax:
- IPX.030 Network routing table overflow, discarding network
- Description:
- This message is generated when a new network cannot be added
to the routing table because it is full. The entry is discarded.
- Cause:
- Routing table too small.
- Action:
- Reconfigure IPX protocol to make routing table larger.
- Level:
- C-INFO
- Short Syntax:
- IPX.031 RIP route to network
now via router_net
/ router_node
, hop_count
hops
- Long Syntax:
- IPX.031 RIP route to network network
now via router_net
/ router_node
, hop_count
hops
- Description:
- This message is generated when the route to a network changes.
The specified router_net/router_node is now the best route to
this network, with the noted number of hops.
- Cause:
- Newly reachable network (if preceeded by message IPX.055).
- Cause:
- Change in network topology causes best route to a network to
change. This can happen when networks come up, or go down.
- Action:
- Determine what changes in network topology occurred.
- Level:
- U-INFO
- Short Syntax:
- IPX.032 RIP route to network
aged away
- Long Syntax:
- IPX.032 RIP route to network
aged away
- Description:
- This message is generated when a network is declared unreachable
because no routing updates have been heard for it in 240 seconds.
It will be advertised as unreachable for another 60 seconds, and
then deleted from the routing table.
- Cause:
- Intervening router that was advertising this network crashed.
- Level:
- C-TRACE
- Short Syntax:
- IPX.033 Rspnd to RIP rqst frm source_net
/ source_node
- Long Syntax:
- IPX.033 Responding to RIP Request from source_net
/ source_node
- Description:
- This message is generated when a RIP Request packet is being
parsed for a Reply.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.034 RIP rqst frm source_net
/ source_node
shrt, ln packet_length
- Long Syntax:
- IPX.034 RIP Request from source_net
/ source_node
too short, len packet_length
- Description:
- A RIP request packet was received which is too short to contain one
RIP entry. The packet is discarded.
- Level:
- U-TRACE
- Short Syntax:
- IPX.035 RIP qry sent nt network ID
- Long Syntax:
- IPX.035 RIP Query sent, net network ID
- Description:
- A RIP Query has been sent on the specified interface. A Query
is sent on each interface when it comes up.
- Level:
- UI-ERROR
- Class:
- OOM
- Short Syntax:
- IPX.036 No mem for RIP pkt nt network ID
, packet_count
pkts snt
- Long Syntax:
- IPX.036 No memory for RIP packet, net network ID
, packet_count
packets sent
- Description:
- This message is generated when no buffer is available to send a
RIP Query or Response packet.
- Level:
- C-TRACE
- Short Syntax:
- IPX.037 RIP resp sent nt network ID
, packet_count
pkts
- Long Syntax:
- IPX.037 RIP Response sent net network ID
, packet_count
packets
- Description:
- This message is generated when a RIP Response is sent. The response
was sent in the specified number of packets.
- Level:
- U-TRACE
- Short Syntax:
- IPX.038 source_net
/ source_node
-> dest_net
/ dest_node
ign
- Long Syntax:
- IPX.038 Packet from source_net
/ source_node
for dest_net
/ dest_node
ignored
- Description:
- This message is generated when an IPX packet arrives on a
network and the IPX forwarder is not active on that network.
- Level:
- C-TRACE
- Short Syntax:
- IPX.039 RIP delta resp sent nt network ID
, packet_count
pkts
- Long Syntax:
- IPX.039 RIP delta Response sent net network ID
, packet_count
packets
- Description:
- This message is generated when a RIP delta Response is sent.
This response only includes those networks whose data changed in
the last update period. The response
was sent in the specified number of packets.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.040 RIP resp snd dsc, nt network ID
, rsn reason_code
- Long Syntax:
- IPX.040 RIP Response send discarded, net network ID
, reason reason_code
- Description:
- An outgoing RIP response packet was not successfully
transmitted for the reason indicated by the error code.
- Cause:
- Miscellaneous handler error. (Reason code 1.)
- Action:
- Check for error messages from the handler for network ID.
- Cause:
- Output queue overflow, or other flow control. (Reason code
2.)
- Action:
- Alleviate congestion.
- Cause:
- The network is down. (Reason code 3.)
- Action:
- See why the handler thinks the network is down.
- Cause:
- The handler dropped the packet to avoid looping, or bad broadcast.
(Reason code 4.)
- Action:
- Check your configuration.
- Cause:
- The host is down. (Reason code 5.)
- Action:
- See why the handler thinks the host is down.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.041 RIP query snd dsc, nt network ID
, rsn reason_code
- Long Syntax:
- IPX.041 RIP Query send discarded, net network ID
, reason reason_code
- Description:
- An outgoing RIP query packet was not successfully
transmitted for the reason indicated by the error code.
- Cause:
- Miscellaneous handler error. (Reason code 1.)
- Action:
- Check for error messages from the handler for network ID.
- Cause:
- Output queue overflow, or other flow control. (Reason code
2.)
- Action:
- Alleviate congestion.
- Cause:
- The network is down. (Reason code 3.)
- Action:
- See why the handler thinks the network is down.
- Cause:
- The handler dropped the packet to avoid looping, or bad broadcast.
(Reason code 4.)
- Action:
- Check your configuration.
- Cause:
- The host is down. (Reason code 5.)
- Action:
- See why the handler thinks the host is down.
- Level:
- C-TRACE
- Short Syntax:
- IPX.042 SAP gives near reply typ service_type
nm [ service_name
] to source_net
/ source_node
, nt network ID
- Long Syntax:
- IPX.042 SAP giving Nearest Server Reply of type service_type
name [ service_name
] to source_net
/ source_node
, net network ID
- Description:
- A SAP Nearest Service Reply will be sent to the specified
node. The service_type is the type of service, and the
service_name is the name of the service.
- Cause:
- Node sent Nearest Server Request, and the nearest server
of that type is reachable through this router.
- Level:
- C-TRACE
- Short Syntax:
- IPX.043 SAP nearest qry for typ service_type
frm source_net
/ source_node
nt network ID
- Long Syntax:
- IPX.043 SAP Nearest Query for service type service_type
from source_net
/ source_node
, net network ID
- Description:
- A SAP Nearest Service Query was received from the specified
node via the specified interface. If this router is
the best route to the
closest server of the specified service_type, this router
will answer.
- Cause:
- New IPX node booting on an attached LAN, looking for a first file
server (service_type of 4).
- Cause:
- Node attempting to locate a particular server by service type,
such as a communications server or database server.
- Level:
- C-TRACE
- Short Syntax:
- IPX.044 SAP delta gen rply nt network ID
, count
pkts
- Long Syntax:
- IPX.044 SAP delta General Service Reply sent, net network ID
, count
packets
- Description:
- A SAP delta General Service Reply has just been sent on the specified
network. This Reply only includes those services whose data changed
in the last update period. It took the specified number
of packets to send the changes in SAP database.
- Level:
- U-INFO
- Short Syntax:
- IPX.045 SAP new serv typ service_type
nm [ service_name
] via via_net
/ via_node
, hop_count
hops, nt network ID
- Long Syntax:
- IPX.045 SAP new service route to service type service_type
name [ service_name
] via via_net
/ via_node
, hop_count
hops, net network ID
- Description:
- This message is generated when a new service is added to the
SAP table The specified via_net/via_node is the route to
this service, with the noted number of hops.
- Cause:
- New service started on IPX internetwork.
- Cause:
- Existing service becomes reachable, due to change in network
connectivity.
- Level:
- U-TRACE
- Short Syntax:
- IPX.046 SAP nearest qry frm source_net
/ source_node
ignored, nt network ID
- Long Syntax:
- IPX.046 SAP Nearest Query from source_net
/ source_node
ignored, net network ID
- Description:
- A SAP Nearest Service Query was received from the specified
node via the specified interface, but processing of these
packets has been administratively disabled on this interface.
The query will be ignored.
- Cause:
- User has used IPX Config command DISABLE REPLY-TO-GET-NEAREST-SERVER.
- Action:
- If this is the desired action, none. To enable response (the
default), use the IPX Config command ENABLE
REPLY-TO-GET-NEAREST-SERVER.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.047 SAP query snd dsc, nt network ID
, rsn reason_code
- Long Syntax:
- IPX.047 SAP Query send discarded, net network ID
, reason reason_code
- Description:
- An outgoing SAP query packet was not successfully
transmitted for the reason indicated by the error code.
- Cause:
- Miscellaneous handler error. (Reason code 1.)
- Action:
- Check for error messages from the handler for network ID.
- Cause:
- Output queue overflow, or other flow control. (Reason code
2.)
- Action:
- Alleviate congestion.
- Cause:
- The network is down. (Reason code 3.)
- Action:
- See why the handler thinks the network is down.
- Cause:
- The handler dropped the packet to avoid looping, or bad broadcast.
(Reason code 4.)
- Action:
- Check your configuration.
- Cause:
- The host is down. (Reason code 5.)
- Action:
- See why the handler thinks the host is down.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.048 SAP resp snd dsc, nt network ID
, rsn reason_code
- Long Syntax:
- IPX.048 SAP Response send discarded, net network ID
, reason reason_code
- Description:
- An outgoing SAP response packet was not successfully
transmitted for the reason indicated by the error code.
- Cause:
- Miscellaneous handler error. (Reason code 1.)
- Action:
- Check for error messages from the handler for network ID.
- Cause:
- Output queue overflow, or other flow control. (Reason code
2.)
- Action:
- Alleviate congestion.
- Cause:
- The network is down. (Reason code 3.)
- Action:
- See why the handler thinks the network is down.
- Cause:
- The handler dropped the packet to avoid looping, or bad broadcast.
(Reason code 4.)
- Action:
- Check your configuration.
- Cause:
- The host is down. (Reason code 5.)
- Action:
- See why the handler thinks the host is down.
- Level:
- U-TRACE
- Short Syntax:
- IPX.049 SAP no serv typ service_type
for source_net
/ source_node
, nt network ID
- Long Syntax:
- IPX.049 SAP no server of type service_type
for Query from source_net
/ source_node
, net network ID
- Description:
- A SAP Nearest Service Query was received from source_net/source_node,
but the SAP database has no service registered of the
desired service_type. No response will be sent.
- Cause:
- Service of desired service_type is down or unreachable.
- Action:
- Find out why serveice is down or unreachable.
- Cause:
- Workstation looking for non-existent service_type.
- Action:
- Correct query on workstation.
- Level:
- U-INFO
- Short Syntax:
- IPX.050 SAP dead serv typ service_type
nm [ service_name
] from via_net
/ via_node
, nt network ID
- Long Syntax:
- IPX.050 SAP dead service route to service type service_type
name [ service_name
] reported by via_net
/ via_node
has become unreachable, net network ID
- Description:
- This message is generated when a previously reachable
service becomes unreachable, and is marked as Dead in the
SAP table. The specified via_net/via_node is the server or
router that announced the service as being unreachable.
- Cause:
- Server administratively disabled, as with :DOWN command.
- Action:
- None.
- Cause:
- Server crashed.
- Action:
- Find out why server crashed.
- Cause:
- Network on which service is provided has become unreachable.
- Action:
- Use IPX console DUMP command to see if network is reachable.
- Level:
- U-INFO
- Short Syntax:
- IPX.051 RIP route died to network
from router_net
/ router_node
- Long Syntax:
- IPX.051 RIP route died to network network
from router router_net
/ router_node
- Description:
- This message is generated when a previously reachable
network becomes unreachable, and is marked as Dead in the
RIP table. The specified router_net/router_node is the
router that announced the network as being unreachable.
- Cause:
- Remote network, or intervening network, went down.
- Action:
- Find out why remote network went down.
- Cause:
- Network is on router that went down.
- Action:
- Find out why remote router went down.
- Cause:
- Network is connected via File Server that was administratively
taken down.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.052 RIP resp frm wrong net source_net
/ source_node
not local_net
, nt network ID
- Long Syntax:
- IPX.052 RIP response from wrong network source_net
/ source_node
not local network local_net
, nt network ID
- Description:
- This message is generated when a RIP response packet is
received with a source network number that is not
the same as the network number of this interface.
The packet will be ignored.
- Cause:
- Misconfiguration of router on this network.
- Action:
- Correct configuration.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.053 SAP resp frm wrong net source_net
/ source_node
not local_net
, nt network ID
- Long Syntax:
- IPX.053 SAP response from wrong network source_net
/ source_node
not local network local_net
, nt network ID
- Description:
- This message is generated when a SAP response packet is
received with a source network number that is not
the same as the network number of this interface.
The packet will be ignored.
- Cause:
- Misconfiguration of router on this network.
- Action:
- Correct configuration.
- Level:
- C-INFO
- Short Syntax:
- IPX.054 SAP serv typ service_type
nm [ service_name
] now via via_net
/ via_node
, hop_count
hops, nt network ID
- Long Syntax:
- IPX.054 SAP service route to service type service_type
name [ service_name
] is now via via_net
/ via_node
, hop_count
hops, net network ID
- Description:
- This message is generated when the route to a service in the
SAP table changes. The specified via_net/via_node is the new route to
this service, with the noted number of hops.
- Cause:
- Newly reachable service (if proceeded by IPX.045).
- Cause:
- Change in network topology causes best route to a service to
change. This can happen when new networks come up, or go down.
- Action:
- Determine what changes in network topology occurred.
- Level:
- U-INFO
- Short Syntax:
- IPX.055 new RIP net network
via router_net
/ router_node
, hop_count
hops
- Long Syntax:
- IPX.055 New RIP network number network
via router_net
/ router_node
, hop_count
hops
- Description:
- A new route had been added to the routing table
routing table. The new network was advertised by
router_net/router_node, which is now the route to
this network, with the noted number of hops.
- Level:
- U-TRACE
- Short Syntax:
- IPX.056 RIP route to network
garbage coll
- Long Syntax:
- IPX.056 RIP route to network
garbage collected
- Description:
- This message is generated when a network is removed from the RIP
routing table
because no routing updates have been heard for it in 300 seconds.
This normally happens 60 seconds after an IPX.012 message
on the same service.
- Cause:
- Intervening router that was advertising this network went down.
- Level:
- U-INFO
- Short Syntax:
- IPX.057 SAP del typ service_type
nm [ service_name
], nt network ID
down
- Long Syntax:
- IPX.057 SAP deleted type service_type
name [ service_name
], network network ID
down
- Description:
- The specified network interface has gone down, and this SAP
service having a first hop on that network will be placed in the
dead state. It will be
advertised as unreachable for another 60 seconds, and then
removed from the SAP table. However, if there are alternate
routes to the same service, they will be learned about within
60 seconds.
- Cause:
- The network via which we reached this service went down.
- Action:
- Bring up network.
- Level:
- U-TRACE
- Short Syntax:
- IPX.058 SAP typ service_type
nm [ service_name
] garbage coll
- Long Syntax:
- IPX.058 SAP type service_type
name [ service_name
] garbage collected
- Description:
- This message is generated when a network is removed from the SAP
routing table
because no SAP responses have been heard for it in 300 seconds.
- Cause:
- Intervening router that was advertising this service went down.
- Level:
- CE-ERROR
- Short Syntax:
- IPX.059 SAP unreach serv typ service_type
nm [ service_name
] at service_net
/ service_node
from via_net
/ via_node
, nt network ID
- Long Syntax:
- IPX.059 SAP unreachable service type service_type
name [ service_name
] at service_net
/ service_node
from via_net
/ via_node
, net network ID
- Description:
- This message is generated when an advertisement for a service is
received, but that service in on an IPX network (service_net)
that this router has no route to. This advertisement will be
ignored.
- Cause:
- Configuration error on node service_net/service_node.
- Action:
- Correct configuration error.
- Cause:
- Service information for some new service has propogated faster
than the associated routing information.
- Action:
- None needed if service_net becomes reachable shortly, and this
message does not repeat.
- Level:
- C-TRACE
- Short Syntax:
- IPX.060 SAP periodic GSR starting
- Long Syntax:
- IPX.060 SAP periodic General Service Response starting
- Description:
- The SAP protocol is beginning the transmission of SAP General
Service Response packets on all IPX interfaces. This happens
approximately every 60 seconds. It will generally be followed
by IPX.064 messages (if there are any services), followed by
an IPX.061 message.
- Level:
- C-TRACE
- Short Syntax:
- IPX.061 SAP periodic GSR completed, packet_count
pkts
- Long Syntax:
- IPX.061 SAP periodic General Service Response completed, packet_count
packet
- Description:
- The SAP protocol has completed the transmission of the
periodic SAP General
Service Response packets on all IPX interfaces. In doing this,
it attempted to send packet_count packets in total.
- Level:
- UI-ERROR
- Class:
- OOM
- Short Syntax:
- IPX.062 No mem for SAP periodic GSR pkt packet_number
, delaying, nt network ID
- Long Syntax:
- IPX.062 No memory for SAP periodic General Service Response packet packet_number
, delaying, network network ID
- Description:
- There was no packet buffer available to send one packet of the
periodic SAP General Service Response. The response will stall
for half a second, waiting for a buffer to become available.
The packet_number is the count of this packet within the complete
response, starting at 0.
- Cause:
- Temporary packet buffer shortage due to traffic peak.
- Action:
- See if message recurs after half a second.
- Cause:
- Parmanent buffer shortage.
- Action:
- Take dump of router and contact customer service.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.063 SAP periodic GSR snd dsc, nt network ID
, rsn reason_code
- Long Syntax:
- IPX.063 SAP periodic General Service Response send discarded, net network ID
, reason reason_code
- Description:
- An outgoing SAP periodic General Service
Response packet was not successfully
transmitted for the reason indicated by the error code.
General Service Response for the reason the error code indicates.
- Cause:
- Miscellaneous handler error. (Reason code 1.)
- Action:
- Check for error messages from the handler for network ID.
- Cause:
- Output queue overflow, or other flow control. (Reason code
2.)
- Action:
- Alleviate congestion.
- Cause:
- The network is down. (Reason code 3.)
- Action:
- See why the handler thinks the network is down.
- Cause:
- The handler dropped the packet to avoid looping, or bad broadcast.
(Reason code 4.)
- Action:
- Check your configuration.
- Cause:
- The host is down. (Reason code 5.)
- Action:
- See why the handler thinks the host is down.
- Level:
- P-TRACE
- Short Syntax:
- IPX.064 SAP periodic GSR sent, entry_count
entries, nt network ID
- Long Syntax:
- IPX.064 SAP periodic General Service Reply sent, entry_count
entries, net network ID
- Description:
- A SAP periodic General Service Reply packet
has just been sent on the specified network. There were
entry_count services in this packet.
- Level:
- U-INFO
- Short Syntax:
- IPX.065 routing cache cleared
- Long Syntax:
- IPX.065 routing cache cleared
- Description:
- The IPX routing cache has been cleared, probably as the result
of a routing table change.
- Level:
- U-INFO
- Short Syntax:
- IPX.066 routing cache garbage collecting...
- Long Syntax:
- IPX.066 routing cache garbage collecting...
- Description:
- The IPX routing cache is collecting nonsense data. This takes
several passes, and is only done when the cache starts
overflowing.
- Level:
- U-INFO
- Short Syntax:
- IPX.067 cache entry dest_net
/ dest_node
cleared
- Long Syntax:
- IPX.067 routing cache entry for destination dest_net
/ dest_node
cleared
- Description:
- The IPX routing cache entry for the listed destination
has been cleared.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.068 no memory left for IPX local network/node cache entries
- Long Syntax:
- IPX.068 no memory left for IPX local network/node cache entries
- Description:
- The IPX routing local network/node cache needs memory before
it can add a new local network and its table into the IPX cache.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.069 protocol
tbl ovrfl, dst destination_net
- Long Syntax:
- IPX.069 protocol
Table overflow, destination destination_net
- Description:
- This message is generated when a new alternate entry
cannot be made to routing table because alternate entry space
is already full.
- Cause:
- Alternate entry routing table too small.
- Action:
- Increase alternate routing entries for this protocol.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.070 rte ovrfl, dst destination_net
- Long Syntax:
- IPX.070 route overflow, destination destination_net
- Description:
- This message is generated when a new alternate entry
cannot be made to routing table because alternate entry space
for a given route is already full.
- Cause:
- Maximum routes per destination network is too small.
- Action:
- Increase maximum routing entries per destination network for this protocol.
- Level:
- U-INFO
- Short Syntax:
- IPX.071 drop pkt w/ encap_seen
using encap_used
int intnum
- Long Syntax:
- IPX.071 dropped pkt with encaps encap_seen
using encap_used
on interface intnum
- Description:
- This message is generated when an IPX packet is received with
an encapsulation other than that which has been selected for this interface.
- Cause:
- Normal for networks using multiple encapsulations on a single wire.
- Action:
- None needed.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.072 Error building IPXWAN iw_pkttype
on net network ID
- Long Syntax:
- IPX.072 Error building IPXWAN iw_pkttype
on network network ID
- Description:
- An IPXWAN Response is built from a Request. An attempt has been made to build the response without a request.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.073 Name and Node ID must be config'd before IPXWAN can operate
- Long Syntax:
- IPX.073 Router name and Node ID must be configured before IPXWAN can operate
- Description:
- The IPX configuration parameters Name and Node ID must be configured before IPXWAN can operate on any network.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.074 IPXWAN can't operate on net network ID
- unsupported type
- Long Syntax:
- IPX.074 IPXWAN can't operate on network network ID
because it's an unsupported type
- Description:
- IPXWAN has been configured to run on an unsupported interface type.
- Level:
- U-INFO
- Short Syntax:
- IPX.075 IPXWAN is configured but not enabled on net network ID
- Long Syntax:
- IPX.075 IPXWAN is configured but not enabled to run on network network ID
- Description:
- IPXWAN has been configured to run on the interface, but it has been disabled by the user.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.076 IPXWAN iw_pkttype
pkt dropped, rcv'd on net network ID
, unsupported int type
- Long Syntax:
- IPX.076 IPXWAN iw_pkttype
packet dropeed because it was received on an unsupported interface type, network network ID
- Description:
- An IPXWAN packet was dropped because it was received on an unsupported interface type.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.077 IPXWAN iw_pkttype
pkt dropped, rcv'd on disabled net network ID
- Long Syntax:
- IPX.077 IPXWAN iw_pkttype
packet dropped - it was received on network network ID
which is disabled for IPXWAN traffic
- Description:
- An IPXWAN packet was dropped because it was received on an interface which is configured to be disabled for IPXWAN traffic.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.078 IPXWAN iw_pkttype
pkt rejected on net network ID
, confidence id check failed
- Long Syntax:
- IPX.078 IPXWAN iw_pkttype
packet received on network network ID
was rejected due to the confidence ID check failing
- Description:
- An IPXWAN packet was rejected because the confidence ID check failed.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.079 IPXWAN iw_pkttype
pkt rejected on net network ID
, non-unique node id
- Long Syntax:
- IPX.079 IPXWAN iw_pkttype
packet received on network network ID
was rejected because its node id is identical to the local node id
- Description:
- An IPXWAN packet was rejected because the node id reported in it was identical to the local node id.
- Action:
- Reconfigure the local IPX node id with a unique value.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.080 No memory to build IPXWAN packet
- Long Syntax:
- IPX.080 Not able to get a buffer to build an IPXWAN packet
- Description:
- An attempt to get a buffer to build an IPXWAN packet failed.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.081 Failed to send an IPXWAN iw_pkttype
pkt on net network ID
- Long Syntax:
- IPX.081 An attempt to send an IPXWAN iw_pkttype
packet on network network ID
failed
- Description:
- An attempt to send an IPXWAN packet failed.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.082 IPXWAN iw_pkttype,
pkt rejected on net network ID
, seq num mismatch
- Long Syntax:
- IPX.082 IPXWAN iw_pkttype,
packet received on network network ID
was rejected due to a sequence number mismatch
- Description:
- An IPXWAN packet was dropped due to a sequence number mismatch.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.083 IPXWAN iw_pkttype
rejected on net network ID
- opt_type
opt not accepted
- Long Syntax:
- IPX.083 IPXWNA iw_pkttype
rejected on network network ID
- opt_type
option not accepted
- Description:
- An IPXWAN packet was rejected because an option was not accepted by
the other side of the link.
- Level:
- U-INFO
- Short Syntax:
- IPX.084 IPXWAN connection to be retried on net network ID
- Long Syntax:
- IPX.084 IPXWAN connection to be retried on network network ID
- Description:
- A previously timed-out IPXWAN connection is to be retried.
- Level:
- U-INFO
- Short Syntax:
- IPX.085 IPXWAN connection on net network ID
timed-out
- Long Syntax:
- IPX.085 IPXWAN connection on network network ID
timed-out
- Description:
- An IPXWAN connection attempt timed-out.
- Level:
- C-INFO
- Short Syntax:
- IPX.086 IPXWAN iw_pkttype
pkt rcvd on net network ID
- Long Syntax:
- IPX.086 IPXWAN iw_pkttype
packet received on network network ID
- Description:
- An IPXWAN packet was successfully received, accepted, and processed.
- Level:
- C-INFO
- Short Syntax:
- IPX.087 IPXWAN iw_pkttype
pkt sent on net network ID
- Long Syntax:
- IPX.087 IPXWAN iw_pkttype
packet sent on network network ID
- Description:
- An IPXWAN packet was successfully sent on the network.
- Level:
- C-INFO
- Short Syntax:
- IPX.088 IPXWAN connection up on net network ID
- Long Syntax:
- IPX.088 IPXWAN connection has come up on network network ID
- Description:
- An IPXWAN connection is up on the given network.
- Level:
- U-INFO
- Short Syntax:
- IPX.089 IPXWAN connection down on net network ID
- Long Syntax:
- IPX.089 IPXWAN connection has gone down on network network ID
- Description:
- An IPXWAN connection has gone down the given network. This can happen if the link goes down, if the protocol goes down on the link (IPXCP goes down) or if a Timer Request packet is received.
- Level:
- U-TRACE
- Short Syntax:
- IPX.090 SAP no server reply required for typ service_type
for source_net
/ source_node
, nt network ID
- Long Syntax:
- IPX.090 SAP no server reply required for type service_type
for Query from source_net
/ source_node
, net network ID
- Description:
- The router received a SAP Nearest Service Query from
source_net/source_node. The SAP database indicates that a
server exists on the same network as the client. The server
will be allowed to respond for itself.
- Cause:
- There is an eligible server on the client's network that is
capable of replying for itself.
- Action:
- No action is required.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.091 short NB frm source_net
/ source_node
nt network ID
, ign
- Long Syntax:
- IPX.091 short NETBIOS frame from source_net
/ source_node
net network ID
, ignored
- Description:
- A NETBIOS type 20 packet must be at least 62 bytes in length.
It will be dropped.
- Cause:
- Unknown.
- Action:
- None. Fix Novell application sending the packet.
- Level:
- U-INFO
- Short Syntax:
- IPX.092 Add kpalv proxy source_net
/ source_node
. source_socket
<-> dest_net
/ dest_node
. dest_socket
- Long Syntax:
- IPX.092 Add KeepAlive proxy connection source_net
/ source_node
. source_socket
<-> dest_net
/ dest_node
. dest_socket
- Description:
- A new pair of stations has been added to the proxy keepalive table.
- Level:
- U-INFO
- Short Syntax:
- IPX.093 Del kpalv proxy source_net
/ source_node
. source_socket
<-> dest_net
/ dest_node
. dest_socket
- Long Syntax:
- IPX.093 Delete KeepAlive proxy connection source_net
/ source_node
. source_socket
<-> dest_net
/ dest_node
. dest_socket
- Description:
- A pair of stations has been removed from the proxy keepalive table.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.094 no memory for IPX kpalv proxy tbl
- Long Syntax:
- IPX.094 no memory for IPX KeepAlive Proxy connection table
- Description:
- The IPX Keepalive Proxy initialization routine was unable to allocate
memory for its connection table. (IPX KeepAlive Proxy feature will
not be enabled.)
- Level:
- U-INFO
- Short Syntax:
- IPX.095 Serial pkt dropped source_net
/ source_node
-> dest_net
/ dest_node
, nt network ID
- Long Syntax:
- IPX.095 Serial packet dropped source_net
/ source_node
-> dest_net
/ dest_node
, net network ID
- Description:
- The router dropped a Serialization packet because the output network
interface has IPX KeepAlive filtering enabled.
- Level:
- UI-ERROR
- Class:
- OOM
- Short Syntax:
- IPX.096 No mem fr prxy kpalv req/rsp
- Long Syntax:
- IPX.096 No memory for proxy keepalive request or response
- Description:
- No buffer is available to send an IPX keepalive message.
- Level:
- U-INFO
- Short Syntax:
- IPX.097 Proxy kpalv type
source_net
/ source_node
. source_socket
-> dest_net
/ dest_node
. dest_socket
- Long Syntax:
- IPX.097 Sent proxy keepalive type
source_net
/ source_node
. source_socket
-> dest_net
/ dest_node
. dest_socket
- Description:
- The router sent a proxy keepalive packet.
- Level:
- P-TRACE
- Short Syntax:
- IPX.098 RIP RTR flt PASS pkt frm source_net
/ source_node
, nt network ID
- Long Syntax:
- IPX.098 RIP Router filter PASS packet from source_net
/ source_node
, net network ID
- Description:
- A RIP packet has successfully PASSED through the RIP router filter on
the given interface. The RIP router filter is based upon the
source_node in the IPX packet header, which is displayed by the
message.
- Level:
- P-TRACE
- Short Syntax:
- IPX.099 RIP RTR flt DROP pkt frm source_net
/ source_node
, nt network ID
- Long Syntax:
- IPX.099 RIP Router filter DROP packet from source_net
/ source_node
, net network ID
- Description:
- A RIP packet has been DROPPED by the RIP router filter on the
given interface.
The RIP router filter is based upon the source_node in the IPX
packet header, which is displayed by the message.
- Level:
- P-TRACE
- Short Syntax:
- IPX.100 RIP iodir
flt PASS IPX net ipx_network
, nt network ID
- Long Syntax:
- IPX.100 RIP iodir
filter PASS IPX network number ipx_network
, net network ID
- Description:
- A RIP routing information entry for the given IPX network
number has successfully PASSED through the RIP filter on the
given interface in the stated filtering direction, which is either
inbound or outbound.
- Level:
- P-TRACE
- Short Syntax:
- IPX.101 RIP iodir
flt DROP net ipx_network
, nt network ID
- Long Syntax:
- IPX.101 RIP iodir
filter DROP network ipx_network
, net network ID
- Description:
- A RIP routing information entry for the given IPX network
number has been DROPPED by the RIP filter on the given
interface in the stated filtering direction, which is either
inbound or outbound.
- Level:
- P-TRACE
- Short Syntax:
- IPX.102 SAP iodir
flt PASS typ service_type
nm [ service_name
], service_hops
hops, nt network ID
- Long Syntax:
- IPX.102 SAP iodir
filter PASS type service_type
name [ service_name
], hops service_hops
, net network ID
- Description:
- A SAP routing information entry for the given IPX network
number has successfully PASSED through the SAP filter on
the given interface in the stated filtering direction, which
is either inbound or outbound.
- Level:
- P-TRACE
- Short Syntax:
- IPX.103 SAP iodir
flt DROP typ service_type
nm [ service_name
], service_hops
hops, nt network ID
- Long Syntax:
- IPX.103 SAP iodir
filter DROP type service_type
name [ service_name
], hops service_hops
, net network ID
- Description:
- A SAP routing information entry for the given IPX network
number has been DROPPED by the SAP filter on the given interface
in the stated filtering direction, which is either inbound or outbound.
- Level:
- P-TRACE
- Short Syntax:
- IPX.104 IPX iodir
flt PASS typ packet_type
source_net
/ source_node
. source_socket
-> dest_net
/ dest_node
. dest_socket
, service_hops
hops, nt network ID
- Long Syntax:
- IPX.104 IPX iodir
filter PASS type packet_type
, source_net
/ source_node
. source_socket
-> dest_net
/ dest_node
. dest_socket
, hops service_hops
, net network ID
- Description:
- An IPX packet has PASSED through the IPX filter on the given interface
in the stated filtering direction, which is either inbound or outbound.
- Level:
- P-TRACE
- Short Syntax:
- IPX.105 IPX iodir
flt DROP typ packet_type
source_net
/ source_node
. source_socket
-> dest_net
/ dest_node
. dest_socket
, service_hops
hops, nt network ID
- Long Syntax:
- IPX.105 IPX iodir
filter DROP type packet_type
, source_net
/ source_node
. source_socket
-> dest_net
/ dest_node
. dest_socket
, hops service_hops
, net network ID
- Description:
- An IPX packet has been DROPPED by the IPX filter on the given interface
in the stated filtering direction, which is either inbound or outbound.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.106 reserved for possible growth by releases before 16.2
- Long Syntax:
- IPX.106 reserved for possible growth by releases before 16.2
- Description:
- this message is not defunct, room is being left for message growth
- Level:
- UI-ERROR
- Short Syntax:
- IPX.107 reserved for possible growth by releases before 16.2
- Long Syntax:
- IPX.107 reserved for possible growth by releases before 16.2
- Description:
- this message is not defunct, room is being left for message growth
- Level:
- UI-ERROR
- Short Syntax:
- IPX.108 SAP query snd fld, rsn= reason_code
, IPX circuit ID
AP query send failed, reason=%d, %S
- Long Syntax:
- IPX.108 SAP query send failed, reason= reason_code
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A request to send a SAP query packet was rejected and failed
due to the indicated reason.
- Cause:
- Miscellaneous handler error. (Reason code 1.)
- Action:
- Check for error messages from handler for network_name.
- Cause:
- Output queue overflow, or other flow control. (Reason code 2.)
- Action:
- Alleviate congestion.
- Cause:
- Network down. (Reason code 3.)
- Action:
- See why handler thinks network is down.
- Cause:
- Dropped by handler to avoid looping, or bad broadcast.
(Reason code 4.)
- Action:
- Check configuration.
- Cause:
- Host down. (Reason code 5.)
- Action:
- See why handler thinks host is down.
- Level:
- C-INFO
- Short Syntax:
- IPX.109 Periodic SAP done: sap_count
entries in packet_count
pkts, IPX circuit ID
eriodic SAP done: %d entries in %d pkts, %S
- Long Syntax:
- IPX.109 Periodic SAP done: sap_count
entries in packet_count
pkts, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- The periodic SAP broadcast for this circuit has just completed.
The number of SAP entries advertised and packets sent is given.
- Level:
- C-INFO
- Short Syntax:
- IPX.110 Delta SAP done: sap_count
entries in packet_count
pkts, IPX circuit ID
elta SAP done: %d entries in %d pkts, %S
- Long Syntax:
- IPX.110 Delta SAP done: sap_count
entries in packet_count
pkts, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A delta SAP broadcast for this circuit has just completed.
The number of SAP entries advertised and packets sent is given.
- Level:
- C-INFO
- Short Syntax:
- IPX.111 Gen Req SAP done: sap_count
entries in packet_count
pkts, IPX circuit ID
eneral Request SAP done: %d entries in %d pkts, %S
- Long Syntax:
- IPX.111 General Request SAP done: sap_count
entries in packet_count
pkts, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP response to a general request on this circuit
has just completed.
The number of SAP entries and packets sent is given.
- Level:
- U-INFO
- Short Syntax:
- IPX.112 SAP aged out: typ service_type
nm [ service_name
], path router_node
on IPX circuit ID
AP aged out: type %x name [%.48S], path %E on %S
- Long Syntax:
- IPX.112 SAP aged out: type service_type
name [ service_name
], path router_node
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A path for a SAP table entry has aged out. The path was from
the given router node on the given circuit. The age out time
on the circuit is the SAP update interval time
multiplied by the SAP multiplier.
- Cause:
- No SAP response packet from the router_node on the circuit
has refreshed the SAP table entry for the age out time.
- Action:
- None, if the SAP is really unreachable from this router.
If the SAP is really reachable, then an network analysis has to be
done to determine why the SAP response packets are not
getting through to refresh the SAP entry.
SAP update intervals and SAP multipliers are adjustable if the
situation is only a matter of allowing more retries.
- Level:
- U-INFO
- Short Syntax:
- IPX.113 SAP down: typ service_type
nm [ service_name
], from router_node
on IPX circuit ID
AP down: type %x name [%.48S], from %E on %S
- Long Syntax:
- IPX.113 SAP down: type service_type
name [ service_name
], from router_node
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP has been reported as unreachable
by the given next-hop router on the circuit.
- Cause:
- A Server went down.
- Action:
- None.
- Cause:
- The network upon which the server resides may no longer be reachable.
- Action:
- Determine why the network is unreachable.
- Level:
- C-TRACE
- Short Syntax:
- IPX.114 circ down: typ service_type
nm [ service_name
], path router_node
on IPX circuit ID
irc down: type %x name [%.48S], path %E on %S
- Long Syntax:
- IPX.114 circ down: type service_type
name [ service_name
], path router_node
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP table entry, for the given SAP type and name, is no
longer reachable because the underlying circuit of the
the next hop router supplying the SAP information has gone down.
The next hop router's IPX node and circuit are displayed.
- Level:
- C-TRACE
- Short Syntax:
- IPX.115 SAP unreach, SAP's net ipx_network
unreach service_type
nm [ service_name
]
- Long Syntax:
- IPX.115 SAP unreach, SAP's network ipx_network
unreachable, type service_type
name [ service_name
]
- Description:
- This SAP is considered unreachable because the Novell network
location of this SAP is no longer reachable from this router.
- Cause:
- The Novell network, upon which the SAP resides,
is no longer reachable.
- Action:
- Determine why the network became unreachable.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.116 bad SAP opc SAP_opcode
from src_ipx_node
, IPX circuit ID
ad SAP opcode %x from %E, %S
- Long Syntax:
- IPX.116 bad SAP opcode SAP_opcode
from src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP packet was received with an opcode that this router
does not support. The packet is discarded.
- Level:
- C-TRACE
- Short Syntax:
- IPX.117 SAP gen qry from src_ipx_node
, IPX circuit ID
AP general query from %E, %S
- Long Syntax:
- IPX.117 SAP general query from src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP General Service Query has been received and is about
to be processed. If appropriate, this router will answer
the query.
- Level:
- C-TRACE
- Short Syntax:
- IPX.118 SAP gen rsp from src_ipx_node
, IPX circuit ID
AP general response from %E, %S
- Long Syntax:
- IPX.118 SAP general response from src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP General Service Response has been received and is about
to be processed. The data in the packet will be
used to update the SAP database in the router.
- Level:
- C-TRACE
- Short Syntax:
- IPX.119 SAP GNS for typ sap_type
from src_ipx_node
, IPX circuit ID
AP Get Nearest Service for type %x from %E, %S
- Long Syntax:
- IPX.119 SAP Get Nearest Service for type sap_type
from src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP Nearest Service Query packet has been received and is
about to be processed. If appropriate, this router
will answer the query.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.120 SAP GNS bad len from src_ipx_node
, IPX circuit ID
AP Get Nearest Service with bad length from %E, %S
- Long Syntax:
- IPX.120 SAP Get Nearest Service with bad length from src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP Get Nearest Service Query packet was received with
an illegal length. The packet is discarded.
- Level:
- U-TRACE
- Short Syntax:
- IPX.121 SAP GNS qry frm src_ipx_node
ign, IPX circuit ID
AP Get Nearest Service Query from %E ignored, %S
- Long Syntax:
- IPX.121 SAP Get Nearest Service Query from src_ipx_node
ignored, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP Get Nearest Service Query was received, but
but ignored because the replay to get nearest server has been disabed.
- Cause:
- Configuration.
- Level:
- U-TRACE
- Short Syntax:
- IPX.122 SAP GNS no match, typ= sap_type
, from src_ipx_node
, IPX circuit ID
AP GNS no match, type=%x, from %X, %S
- Long Syntax:
- IPX.122 SAP GNS no match, type= sap_type
, from src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP Get Nearest Service Query was received, but no match
was found in the SAP database. No response will be sent.
- Cause:
- Service is unreachable through this router.
- Level:
- U-TRACE
- Short Syntax:
- IPX.123 SAP GNS, service on net, typ= sap_type
, from src_ipx_node
, IPX circuit ID
AP GNS, service on net, type=%x, from %X, %S
- Long Syntax:
- IPX.123 SAP GNS, service on net, type= sap_type
, from src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP Get Nearest Service Query was received, but the closest match
shows that the service is on the same network as the client. The
service, according to Novell, must answer for itself.
No response will be sent.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.124 SAP gen req bad len from src_ipx_node
, IPX circuit ID
AP general request with bad length from %E, %S
- Long Syntax:
- IPX.124 SAP general request with bad length from src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP general request was received with
an illegal length. The packet is discarded.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.125 SAP gen req, no mem, from src_ipx_node
, IPX circuit ID
AP general request, no mem, from %E, %S
- Long Syntax:
- IPX.125 SAP general request, no mem, from src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP general request was received, but the router did not
have memory resources to respond. The packet is discarded.
- Level:
- CE-ERROR
- Short Syntax:
- IPX.126 SAP tbl, net ipx_network
unreach, typ= service_type
nm=[ service_name
]
- Long Syntax:
- IPX.126 SAP tbl, network ipx_network
unreachable, type= service_type
name=[ service_name
]
- Description:
- A SAP table entry was going to be made,
but was disallowed because the IPX network location
of the SAP is not reachable by this router.
- Cause:
- Configuration error on node service_net/service_node.
- Action:
- Correct configuration error.
- Cause:
- Service information for some new service has propogated faster
than the associated routing information.
- Action:
- None needed if service_net becomes reachable shortly, and this
message does not repeat.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.127 SAP tbl, no mem, typ= service_type
nm=[ service_name
]
- Long Syntax:
- IPX.127 SAP table, no mem, type service_type
name [ service_name
]
- Description:
- A new entry cannot be added to the SAP table because
a new SAP table entry can not be allocated. The new entry is
discarded.
- Cause:
- SAP table too small or not enough memory.
- Action:
- Pre-allocate more table entries or increase memory.
- Level:
- U-INFO
- Short Syntax:
- IPX.128 SAP srv: typ= service_type
nm=[ service_name
], hop_count
hops, from via_node
, IPX circuit ID
AP service: type=%x name=[%.48S], %d hops, from %E, %S
- Long Syntax:
- IPX.128 SAP service: type= service_type
name=[ service_name
], hop_count
hops, from via_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A new service has been added to the service table. It was
learned by the SAP protocol. Sap type, sap name, hops are given.
Source ipx_node and circuit are the SAP information is given.
- Cause:
- New service started on IPX internetwork.
- Cause:
- Existing service becomes reachable, due to change in network
connectivity.
- Level:
- U-INFO
- Short Syntax:
- IPX.129 SAP tbl, chg, typ= service_type
nm=[ service_name
], hop_count
hops, from via_node
, IPX circuit ID
AP tbl, chg, type=%x name=[%.48S], %d hops, from %E, %S
- Long Syntax:
- IPX.129 SAP tbl, chg, type= service_type
name=[ service_name
], hop_count
hops, from via_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP table entry, for the given SAP type and name,
has changed in the number of hops to reach
the service. The IPX node address and circuit location
of the next hop router, from which this new service
information has been learned, are given.
- Cause:
- Network connectivity has changed, changing the reachablity
information of the service.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.130 RIP/SAP hops > 16 from src_ipx_node
, IPX circuit ID
IP/SAP hops > 16 from %E, %S
- Long Syntax:
- IPX.130 RIP/SAP hops > 16 from src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP or SAP packet had a hop count greater than 16. The packet is
discarded.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.131 SAP rsp snd fld, rsn= reason_code
, IPX circuit ID
AP response send failed, reason=%d, %S
- Long Syntax:
- IPX.131 SAP response send failed, reason= reason_code
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A request to send a SAP response packet on the circuit
was rejected and failed due to the indicated reason.
The SAP response packet may have been
part of a periodic SAP broadcast, a SAP delta broadcast,
or in response to a general request. See IPX.108 for
detail on failure reason codes.
- Level:
- P-TRACE
- Short Syntax:
- IPX.132 SAP rsp snt, for periodic, entry_count
entries, IPX circuit ID
AP rsp snt, for periodic, %u entries, %S
- Long Syntax:
- IPX.132 SAP rsp snt, for periodic, entry_count
entries, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP response packet has just been sent on the circuit. The
number of SAP entries in the packet is shown. The packet was
part of the periodic SAP broadcast for the circuit.
- Level:
- P-TRACE
- Short Syntax:
- IPX.133 SAP rsp snt, for delta, entry_count
entries, IPX circuit ID
AP rsp snt, for delta, %u entries, %S
- Long Syntax:
- IPX.133 SAP rsp snt, for delta, entry_count
entries, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP response packet has just been sent on the circuit. The
number of SAP entries in the packet is shown. The packet was
part of a delta SAP broadcast for the circuit.
- Level:
- P-TRACE
- Short Syntax:
- IPX.134 SAP rsp snt, for gen req, entry_count
entries, IPX circuit ID
AP rsp snt, for gen req, %u entries, %S
- Long Syntax:
- IPX.134 SAP rsp snt, for gen req, entry_count
entries, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP response packet has just been sent on the circuit. The
number of SAP entries in the packet is shown. The packet was
part of a response to a SAP general request.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.135 SAP rsp frm src_ipx_node
, mismatch net src_ipx_network
, IPX circuit ID
AP response from %E, mismatched network number %X, %S
- Long Syntax:
- IPX.135 SAP response from src_ipx_node
, mismatched network number src_ipx_network
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP response packet was received with a source network
number that is not the same as the network number as this circuit.
The packet is discarded.
- Cause:
- Misconfiguration of the IPX network number.
- Action:
- Correct configuration so that the IPX network number matches
among all routers and servers on the circuit.
- Level:
- P-TRACE
- Short Syntax:
- IPX.136 SAP rsp frm src_ipx_node
, SAP off, IPX circuit ID
AP response from %E, SAP off, %S
- Long Syntax:
- IPX.136 SAP response from src_ipx_node
, SAP off, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- SAP is off. A SAP response packet, received the specified node,
has information about a SAP not on this immediate network.
The information about any SAP not on this immediate network
is ignored if SAP is OFF for the circuit.
- Cause:
- SAP is off because either it has been configured to be OFF or
SAP has been negotiated to be OFF on this IPXWAN circuit.
- Action:
- None, unless this SAP information is important. Otherwise,
you may want to change SAP from OFF to ON or AUTOMATIC
mode for this circuit, or alternatively, upgrade the node
sending this SAP information to use NLSP instead of SAP.
- Level:
- C-TRACE
- Short Syntax:
- IPX.137 SAP GNS rpy: typ service_type
nm [ service_name
] to ipx_node
, IPX circuit ID
AP Get Nearest Server reply of type %x name [%.48S] to %E, %S
- Long Syntax:
- IPX.137 SAP Get Nearest Server reply of type service_type
name [ service_name
] to ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP Get Nearest Service Reply will be sent to the specified
node. The service_type and service name are shown.
- Cause:
- An IPX node sent a Get Nearest Server Request, and this
router is replying with this specific service.
- Level:
- U-TRACE
- Short Syntax:
- IPX.138 SAP qry snt, IPX circuit ID
AP general service query sent, %S
- Long Syntax:
- IPX.138 SAP general service query sent, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP General Service Query is sent on the circuit to
ask for SAP information when the IPX circuit comes up.
- Level:
- C-TRACE
- Short Syntax:
- IPX.139 SAP tbl: del, typ= service_type
nm=[ service_name
]
- Long Syntax:
- IPX.139 SAP tbl: del, type= service_type
name=[ service_name
]
- Description:
- This message is generated when the SAP entry,
for the given SAP type and name, is completely
removed from the SAP routing table.
- Level:
- P-TRACE
- Short Syntax:
- IPX.140 NB brd source_net
/ source_node
-> dest_net
/ dest_node
, hop_count
hops, IPX circuit ID
ETBIOS broadcast %X/%E -> %X/%E, %d hops, %S
- Long Syntax:
- IPX.140 NETBIOS broadcast source_net
/ source_node
-> dest_net
/ dest_node
, hop_count
hops, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A NetBIOS type 20 propagation packet has been
received successfully on the circuit shown
for forwarding to other IPX circuits on the router.
The hop count from the IPX header is displayed and indicates
how many other routers have already forwarded this packet.
- Level:
- U-TRACE
- Short Syntax:
- IPX.141 NB too many hops frm source_net
/ source_node
, IPX circuit ID
ETBIOS too many hops from %X/%E, %S
- Long Syntax:
- IPX.141 NETBIOS too many hops from source_net
/ source_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A type 20 propagation packet, eg NETBIOS, has been through
more than 8 routers, which is the maximum limit for this type
of packet. The packet is discarded.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.142 short NB frm source_net
/ source_node
, IPX circuit ID
hort NETBIOS frame from %X/%E, %S
- Long Syntax:
- IPX.142 short NETBIOS frame from source_net
/ source_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A NETBIOS type 20 packet must be at least 62 bytes in length.
The packet is discarded.
- Level:
- C-TRACE
- Short Syntax:
- IPX.143 NB frm source_net
/ source_node
, already on ipx_network
, IPX circuit ID
ETBIOS from %X/%E, already on %X, %S
- Long Syntax:
- IPX.143 NETBIOS from source_net
/ source_node
, already on ipx_network
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- This IPX NETBIOS emulation broadcast packet has already been
on one of the directly attached networks. The packet is discarded
- Cause:
- This is normal; otherwise, a forwarding loop would occur.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.144 NB frm source_net
/ source_node
, no net num, IPX circuit ID
ETBIOS from %X/%E, not net num, %S
- Long Syntax:
- IPX.144 NETBIOS from source_net
/ source_node
, not net num, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- No network number is available to forward the NetBIOS packet.
The packet is discarded.
- Cause:
- Possibily, a serial line network operating without a network number.
- Action:
- If you want to run NETBIOS emulation across a serial line network,
it must have a network number or you must have an internal
network number defined.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.145 NB snd fld, rsn= reason_code
, IPX circuit ID
etBIOS send failed, reason=%d, %S
- Long Syntax:
- IPX.145 NetBIOS send failed, reason= reason_code
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A request to forward a NetBIOS packet was rejected and failed
due to the indicated reason. See IPX.108 for
detail on failure reason codes.
- Level:
- P-TRACE
- Short Syntax:
- IPX.146 fwd source_net
/ source_node
-> dest_net
/ dest_node
, to next_hop_node
, IPX circuit ID
orwarding %X/%E->%X/%E, to %X, %S
- Long Syntax:
- IPX.146 forwarding source_net
/ source_node
-> dest_net
/ dest_node
, to next_hop_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- An IPX pkt is being forward to an ipx node on the circuit.
The source and destination net/node fields of the packet are shown.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.147 pkt fwding snd fld, rsn= reason_code
, IPX circuit ID
acket forwardind send failed, reason=%d, %S
- Long Syntax:
- IPX.147 packet forwardind send failed, reason= reason_code
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A request to forward an IPX pkt was rejected and failed
due to the indicated reason. See IPX.108 for
detail on failure reason codes.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.148 q ovf source_net
/ source_node
-> dest_net
/ dest_node
, IPX circuit ID
ueue overflow, %X/%E->%X/%E, %S
- Long Syntax:
- IPX.148 Queue overflow, source_net
/ source_node
-> dest_net
/ dest_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- IPX forwarder input queue has overflowed.
- Cause:
- More packets are being received than the forwarder can forward.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.149 pkt frm src_net
/ src_node
, too big, pkt_size
> max_size
, IPX circuit ID
acket from %X/%E, too big, %d > %d, %S
- Long Syntax:
- IPX.149 packet from src_net
/ src_node
, too big, pkt_size
> max_size
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- An IPX packet is too large to send on the circuit.
- Cause:
- Maximum transmission units of networks may need adjustment.
- Action:
- MTU configuration adjustment may be needed either on the
router or on the client or on the server.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.150 short len= length
, frm src_net
/ src_node
, IPX circuit ID
hort len=%u, from %X/%E, %S
- Long Syntax:
- IPX.150 short len= length
, from src_net
/ src_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- An received IPX packet had a length less than the minimum
30 byte IPX header. The packet is discarded.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.151 trunc pkt frm src_net
/ src_node
, ipx= length
phys= length
, IPX circuit ID
runcated packet from %X/%E; ipx=%d, physical=%d, %S
- Long Syntax:
- IPX.151 truncated packet from src_net
/ src_node
; ipx= length
, physical= length
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- An received IPX packet had an IPX length greater than
the physical length of the packet. The packet is discarded.
- Level:
- C-TRACE
- Short Syntax:
- IPX.152 src net chgd, src_net
/ src_node
-> dest_net
/ dest_node
, IPX circuit ID
ource network changed, %X/%E->%X/%E, %S
- Long Syntax:
- IPX.152 source network changed, src_net
/ src_node
-> dest_net
/ dest_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A received IPX packet overwrites the source net of 0 with the network's
number. The source and destination values given reflect the
new value.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.153 hops exceeded, src_net
/ src_node
-> dest_net
/ dest_node
, IPX circuit ID
ops exceeded, %X/%E->%X/%E, %S
- Long Syntax:
- IPX.153 hops exceeded, src_net
/ src_node
-> dest_net
/ dest_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A received IPX packet was received with a hop count exceeded
this router's configured maximum hops. The packet is discarded.
- Level:
- CE-ERROR
- Short Syntax:
- IPX.154 no rte, src_net
/ src_node
-> dest_net
/ dest_node
- Long Syntax:
- IPX.154 no route, src_net
/ src_node
-> dest_net
/ dest_node
- Description:
- A received IPX packet was not forwardable. The packet is discarded.
- Level:
- U-INFO
- Short Syntax:
- IPX.155 circ dwn: del path to nt dest_net
via next_hop
on IPX circuit ID
irc dwn: delete path to network %X via %E on %S
- Long Syntax:
- IPX.155 circ dwn: delete path to network dest_net
via next_hop
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- The path to an IPX network has been deleted because the first hop
circuit for that path has gone down.
- Cause:
- circuit down.
- Action:
- Fix network.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.156 bad RIP opc RIP_opcode
from src_ipx_node
, IPX circuit ID
ad RIP opcode %x from %E, %S
- Long Syntax:
- IPX.156 bad RIP opcode RIP_opcode
from src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP packet was received with an opcode that this router
does not support. The packet is discarded.
- Level:
- C-TRACE
- Short Syntax:
- IPX.157 Rspnd to RIP rqst frm src_ipx_node
, IPX circuit ID
esponding to RIP Request from %E, %S
- Long Syntax:
- IPX.157 Responding to RIP Request from src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP query request packet has been received
on the circuit and is being processed.
- Level:
- C-TRACE
- Short Syntax:
- IPX.158 RIP rsp frm src_ipx_node
, IPX circuit ID
IP response from %E, %S
- Long Syntax:
- IPX.158 RIP response from src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP response has been received on the circuit and is being
processed. The information in the packet, if appropriate, will be
used to update the routing table.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.159 RIP rsp frm src_ipx_node
, mismatch net src_ipx_network
, IPX circuit ID
IP response from %E, mismatched network number %X, %S
- Long Syntax:
- IPX.159 RIP response from src_ipx_node
, mismatched network number src_ipx_network
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP response packet was received with a source network
number that is not the same as the network number as this circuit.
The packet is discarded.
- Cause:
- Misconfiguration of the IPX network number.
- Action:
- Correct configuration so that the IPX network number matches
among all routers and servers on the circuit.
- Level:
- P-TRACE
- Short Syntax:
- IPX.160 RIP rsp frm src_ipx_node
, RIP off, IPX circuit ID
IP response from %E, RIP off, %S
- Long Syntax:
- IPX.160 RIP response from src_ipx_node
, RIP off, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP response packet was received, but RIP is OFF, on this circuit.
The packet is discarded.
- Cause:
- RIP is off because either it has been configured to be OFF or
RIP has been negotiated to be OFF on this IPXWAN circuit.
- Level:
- P-TRACE
- Short Syntax:
- IPX.161 SAP rsp frm NLSP nbr src_ipx_node
, IPX circuit ID
AP response from NLSP nbr %E, %S
- Long Syntax:
- IPX.161 SAP response from NLSP nbr src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP response packet was received from an NLSP neighbor. Since we
are using NLSP to talk to this neighbor, the RIP information
is ignored. The packet is discarded.
- Level:
- P-TRACE
- Short Syntax:
- IPX.162 RIP rsp frm NLSP nbr src_ipx_node
, IPX circuit ID
IP response from NLSP nbr %E, %S
- Long Syntax:
- IPX.162 RIP response from NLSP nbr src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP response packet was received from an NLSP neighbor. Since we
are using NLSP to talk to this neighbor, the RIP information
is ignored. The packet is discarded.
- Level:
- U-TRACE
- Short Syntax:
- IPX.163 RIP qry snt, IPX circuit ID
IP general service query sent, %S
- Long Syntax:
- IPX.163 RIP general service query sent, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP General Service Query is sent on the circuit to
ask for RIP information when the IPX circuit comes up.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.164 RIP query snd fld, rsn= reason_code
, IPX circuit ID
IP query send failed, reason=%d, %S
- Long Syntax:
- IPX.164 RIP query send failed, reason= reason_code
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A request to send a RIP query packet was rejected and failed
due to the indicated reason. See IPX.108 for
detail on failure reason codes.
- Level:
- C-INFO
- Short Syntax:
- IPX.165 Periodic RIP done: sap_count
entries in packet_count
pkts, IPX circuit ID
eriodic RIP done: %d entries in %d pkts, %S
- Long Syntax:
- IPX.165 Periodic RIP done: sap_count
entries in packet_count
pkts, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- The periodic RIP broadcast for this circuit has just completed.
The number of RIP entries advertised and packets sent is given.
- Level:
- C-INFO
- Short Syntax:
- IPX.166 Delta RIP done: sap_count
entries in packet_count
pkts, IPX circuit ID
elta RIP done: %d entries in %d pkts, %S
- Long Syntax:
- IPX.166 Delta RIP done: sap_count
entries in packet_count
pkts, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A delta RIP broadcast for this circuit has just completed.
The number of RIP entries advertised and packets sent is given.
- Level:
- C-INFO
- Short Syntax:
- IPX.167 Gen Req RIP done: sap_count
entries in packet_count
pkts, IPX circuit ID
eneral Request RIP done: %d entries in %d pkts, %S
- Long Syntax:
- IPX.167 General Request RIP done: sap_count
entries in packet_count
pkts, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP response to a general request on this circuit
has just completed.
The number of RIP entries and packets sent is given.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.168 RIP rsp snd fld, rsn= reason_code
, IPX circuit ID
IP response send failed, reason=%d, %S
- Long Syntax:
- IPX.168 RIP response send failed, reason= reason_code
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A request to send a RIP response packet on the circuit
was rejected and failed due to the indicated reason.
The RIP response packet may have been
part of a periodic RIP broadcast, a delta RIP broadcast,
or in response to a general request. See IPX.108 for
detail on failure reason codes.
- Level:
- P-TRACE
- Short Syntax:
- IPX.169 RIP rsp snt, for periodic, entry_count
entries, IPX circuit ID
IP rsp snt, for periodic, %u entries, %S
- Long Syntax:
- IPX.169 RIP rsp snt, for periodic, entry_count
entries, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP response packet has just been sent on the circuit. The
number of RIP entries in the packet is shown. The packet was
part of the periodic RIP broadcast for the circuit.
- Level:
- P-TRACE
- Short Syntax:
- IPX.170 RIP rsp snt, for delta, entry_count
entries, IPX circuit ID
IP rsp snt, for delta, %u entries, %S
- Long Syntax:
- IPX.170 RIP rsp snt, for delta, entry_count
entries, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP response packet has just been sent on the circuit. The
number of RIP entries in the packet is shown. The packet was
part of a delta RIP broadcast for the circuit.
- Level:
- P-TRACE
- Short Syntax:
- IPX.171 RIP rsp snt, for gen req, entry_count
entries, IPX circuit ID
IP rsp snt, for gen req, %u entries, %S
- Long Syntax:
- IPX.171 RIP rsp snt, for gen req, entry_count
entries, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP response packet has just been sent on the circuit. The
number of RIP entries in the packet is shown. The packet was
part of a response to a RIP gneral request.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.172 RIP gen req, no mem, from src_ipx_node
, IPX circuit ID
IP general request, no mem, from %E, %S
- Long Syntax:
- IPX.172 RIP general request, no mem, from src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP general request was received, but the router did not
have memory resources to respond. The packet is discarded.
- Level:
- C-INFO
- Short Syntax:
- IPX.173 circ up, ipx_net
/ ipx_node
, IPX circuit ID
irc up, %X/%E, %S
- Long Syntax:
- IPX.173 circ up, ipx_net
/ ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- The IPX circuit has come up.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.174 no hst addr set, IPX circuit ID
o host address set, %S
- Long Syntax:
- IPX.174 no host address set, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- IPX requires an IPX node address to be defined for a circuit.
This can ususally occurs on WAN circuits.
- Cause:
- Serial line enabled without setting host address.
- Action:
- Set IPX host address.
- Level:
- C-INFO
- Short Syntax:
- IPX.175 circ down, ipx_net
/ ipx_node
, IPX circuit ID
irc down, %X/%E, %S
- Long Syntax:
- IPX.175 circ down, ipx_net
/ ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- The IPX circuit has come down.
- Level:
- U-TRACE
- Short Syntax:
- IPX.176 direct circ path dwn: dest_net
via next_hop
on IPX circuit ID
irect circ path dwn: %X via %E on %S
- Long Syntax:
- IPX.176 direct circ path dwn: dest_net
via next_hop
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- The path to thedirectly attached circuit is no longer
reachable because the underlying circuit went down.
- Cause:
- user requested to disable IPX on the circuit.
- Level:
- U-INFO
- Short Syntax:
- IPX.177 rt cache clrd for network
- Long Syntax:
- IPX.177 routing cache cleared for network
- Description:
- The IPX routing cache has been cleared of entries for the given
IPX network, probably as the result of a routing table change.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.178 alt path disc, for net destination_net
, frm router_node
on IPX circuit ID
lternate path discarded, for net %X, frm %E on %S
- Long Syntax:
- IPX.178 alternate path discarded, for net destination_net
, frm router_node
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- An alternate path to the given IPX destination network is available
from another router. However, it will not be placed into the routing
tables because the number of paths for this IPX network
is already at the maximum number to be kept
per destination IPX network.
- Cause:
- Maximum routes kept per destination network smaller than
number of routes available.
- Action:
- None, if your network is functioning as desired; otherwise
you may want to increase the maximum routing paths
kept per IPX destination network, particularly if parallel
paths are desired.
Novell calls this the maximum splitting degree.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.179 no buf for PING req, IPX circuit ID
o buffer available for PING request, %S
- Long Syntax:
- IPX.179 no buffer available for PING request, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- No packet buffer is available to send an IPX PING packet.
The IPX PING will fail.
- Level:
- UE-ERROR
- Short Syntax:
- IPX.180 malform ping pkt from src_ipx_net
/ src_ipx_node
, IPX circuit ID
alformed Ping packet from %X/%E, %S
- Long Syntax:
- IPX.180 malformed Ping packet from src_ipx_net
/ src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A received IPX Ping packet was malformed in some way. The packet
was shorter than the minimum 40 bytes, or did not have the
PING signature, or had a value for type other than request or reply.
The packet is discarded.
- Level:
- C-TRACE
- Short Syntax:
- IPX.181 ping req, src_net
/ src_node
-> dest_net
/ dest_node
, IPX circuit ID
ing request, %X/%E->%X/%E, %S
- Long Syntax:
- IPX.181 ping request, src_net
/ src_node
-> dest_net
/ dest_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A received IPX ping packet was received on the circuit.
The IPX source and destination values are given. This router
will respond with a ping reply.
- Level:
- C-TRACE
- Short Syntax:
- IPX.182 rt dest_net
is unreach
- Long Syntax:
- IPX.182 rt dest_net
is unreachable
- Description:
- A previously reachable network is now no longer reachable.
- Cause:
- See IPX.032, IPX.051, IPX.155, IPX.0176 messages.
- Level:
- C-TRACE
- Short Syntax:
- IPX.183 SAP typ service_type
nm [ service_name
] is unreach
- Long Syntax:
- IPX.183 SAP typ service_type
nm [ service_name
] is unreachable
- Description:
- A previously reachable SAP is now no longer reachable.
- Cause:
- See IPX.112, IPX.113, IPX.114, IPX.115 messages.
- Level:
- U-INFO
- Short Syntax:
- IPX.184 DIR rt: net ipx_net
, ticks
ticks, hops
hops, via direct_net
/ direct_node
on IPX circuit ID
IR route: network %X, %d ticks, %hops, via %X/%E on %S
- Long Syntax:
- IPX.184 DIR route: network ipx_net
, ticks
ticks, hops
ops, via direct_net
/ direct_node
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A new direct route has been added to the routing table.
A direct route is for a route for a circuit that is directly
attached to the router. The ticks and hops for the
route are shown. The network and node numbers of the
router's directly attached circuit are given.
- Level:
- U-INFO
- Short Syntax:
- IPX.185 stat rt install for net ipx_net
attempt failed, circ not active: user_circuit_id
- Long Syntax:
- IPX.185 static route install for net ipx_net
attempt failed, circuit not active: user_circuit_id
- Description:
- A static route for an IPX network was not installed because the circuit
was not active.
- Cause:
- The route's circuit is not active because the circuit is not defined,
or the circuit is disabled, or the ciruict has not yet come up.
- Level:
- U-INFO
- Short Syntax:
- IPX.186 STAT rt: net ipx_net
, ticks
ticks, hops
hops, via ipx_net
/ ipx_node
on IPX circuit ID
TATIC route: network %X, %d ticks, %hops, via %X/%E on %S
- Long Syntax:
- IPX.186 STATIC route: network ipx_net
, ticks
ticks, hops
ops, via ipx_net
/ ipx_node
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A STATIC route had been added to the routing table
routing table. The ticks and hops for the route are shown.
The network and node numbers of the route's next hop are shown.
The circuit of the next hop route is shown.
- Level:
- U-INFO
- Short Syntax:
- IPX.187 RIP rt: net ipx_net
, ticks
ticks, hops
hops, via ipx_net
/ ipx_node
on IPX circuit ID
IP route: network %X, %d ticks, %hops, via %X/%E on %S
- Long Syntax:
- IPX.187 RIP route: network ipx_net
, ticks
ticks, hops
ops, via ipx_net
/ ipx_node
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP route had been added to the routing table
routing table. The ticks and hops for the route are shown.
The network and node numbers of the route's next hop are shown.
The circuit of the next hop route is shown.
- Level:
- U-INFO
- Short Syntax:
- IPX.188 STAT srv: typ= service_type
nm=[ service_name
], hop_count
hops, from via_node
, IPX circuit ID
TATIC service: type=%x name=[%.48S], %d hops, from %E, %S
- Long Syntax:
- IPX.188 STATIC service: type= service_type
name=[ service_name
], hop_count
hops, from via_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A new service has been added to the service table. The service was
staticly configured.
Sap type, sap name, hops are given.
Source ipx_node and circuit are the SAP information is given.
- Cause:
- Static services were configured for this circuit.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.189 unsupported network/data-link type, circuit-type
: IPX circuit config ID
nsupported network/data-link type, %s:%S
- Long Syntax:
- IPX.189 unsupported network/data-link type, circuit-type
: IPX circuit config ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- The specified IPX circuit failed initialization because
the underlying network type or data-link type is not supported
by IPX. An IPX broadcast circuit is supported on Ethernet,
Token-ring, FDDI. For backwards-compatibilty with previous releases,
an IPX broadcast circuit is also supported on
PPP, Frame Relay, X.25, and Proteon Serial Line.
An IPXWAN circuit supports PPP, Frame Relay, X.25, IP Relay,
and Proteon Serial Line.
- Cause:
- The interface number now maps to a different network type than
it once did. This could possibly happen on routers that have
removable or movable hardware cards. Otherwise this should not
happen.
- Cause:
- Perhaps the data-link type has been changed for the interface to
one unsupported by IPX.
- Level:
- P-TRACE
- Short Syntax:
- IPX.190 RIP gen qry frm src_ipx_node
, RIP off, IPX circuit ID
IP gen qry from %E, RIP off, %S
- Long Syntax:
- IPX.190 RIP gen qry from src_ipx_node
, RIP off, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP general query packet was received,
but RIP is OFF, on this circuit. The packet is discarded.
- Cause:
- RIP is off because either it has been configured to be OFF or
RIP has been negotiated to be OFF on this IPXWAN circuit.
- Action:
- None, if RIP is supposed to off on the circuit.
- Level:
- P-TRACE
- Short Syntax:
- IPX.191 SAP gen qry frm src_ipx_node
, SAP off, IPX circuit ID
AP gen qry from %E, SAP off, %S
- Long Syntax:
- IPX.191 SAP gen qry from src_ipx_node
, SAP off, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP general query packet was received,
but SAP is OFF, on this circuit. The packet is discarded.
- Cause:
- SAP is off because either it has been configured to be OFF or
SAP has been negotiated to be OFF on this IPXWAN circuit.
- Action:
- None, if SAP is supposed to off on the circuit.
- Level:
- P-TRACE
- Short Syntax:
- IPX.192 RIP auto mode: off->on, IPX circuit ID
IP automatic mode: off->on, %S
- Long Syntax:
- IPX.192 RIP automatic mode: off->on, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- RIP automatic mode going from automatic-off to automatic-on.
- Cause:
- RIP automatic mode has detected a node with a need for RIP and
will now send periodic and delta RIP packets until the need
disappears.
- Action:
- None.
- Level:
- P-TRACE
- Short Syntax:
- IPX.193 SAP auto mode: off->on, IPX circuit ID
AP automatic mode: off->on, %S
- Long Syntax:
- IPX.193 SAP automatic mode: off->on, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- SAP automatic mode going from automatic-off to automatic-on.
- Cause:
- SAP automatic mode has detected a node with a need for SAP and
will now send periodic and delta SAP packets until the need
disappears.
- Action:
- None.
- Level:
- P-TRACE
- Short Syntax:
- IPX.194 RIP auto mode: on->off, IPX circuit ID
IP automatic mode: on->off, %S
- Long Syntax:
- IPX.194 RIP automatic mode: on->off, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- RIP automatic mode going from automatic-on to automatic-off.
- Cause:
- RIP automatic mode no longer detects the need for RIP and
is no longer sending periodic and delta RIP packets.
- Action:
- None.
- Level:
- P-TRACE
- Short Syntax:
- IPX.195 SAP auto mode: on->off, IPX circuit ID
IP automatic mode: on->off, %S
- Long Syntax:
- IPX.195 RIP automatic mode: on->off, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- SAP automatic mode going from automatic-on to automatic-off.
- Cause:
- SAP automatic mode no longer detects the need for SAP and
is no longer sending periodic and delta SAP packets.
- Action:
- None.
- Level:
- U-INFO
- Short Syntax:
- IPX.196 NLSP rt: net ipx_net
, ticks
ticks, hops
hops, via ipx_net
/ ipx_node
on IPX circuit ID
LSP route: network %X, %d ticks, %hops, via %X/%E on %S
- Long Syntax:
- IPX.196 NLSP route: network ipx_net
, ticks
ticks, hops
ops, via ipx_net
/ ipx_node
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A new NLSP route to the given network has been added to
the routing table. The ticks and hops for the route are shown.
There may be more than one path, but only one the first one
is displayed by this message.
The network and node numbers of the first paths's next hop are shown.
The circuit of the first path next hop is shown.
- Level:
- U-INFO
- Short Syntax:
- IPX.197 NLSP Xroute: net ipx_net
, ticks
ticks, hops
hops, via ipx_net
/ ipx_node
on IPX circuit ID
LSP Xroute: network %X, %d ticks, %hops, via %X/%E on %S
- Long Syntax:
- IPX.197 NLSP Xroute: network ipx_net
, ticks
ticks, hops
ops, via ipx_net
/ ipx_node
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A new NLSP Xroute to the given network has been added to
the routing table. The ticks and hops for the route are shown.
There may be more than one path, but only one the first one
is displayed by this message.
The network and node numbers of the first paths's next hop are shown.
The circuit of the first path next hop is shown.
- Level:
- U-INFO
- Short Syntax:
- IPX.198 NLSP srv info: typ= service_type
nm=[ service_name
], hop_count
hops, from via_node
, IPX circuit ID
LSP service info: type=%x name=[%.48S], %d hops, from %E, %S
- Long Syntax:
- IPX.198 NLSP service info: type= service_type
name=[ service_name
], hop_count
hops, from via_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A new service has been added to the service table. It was
learned by the NLSP protocol. Sap type, sap name, hops are given.
There may be more than one path, but only one the first one
is displayed by this message.
The node number of the first paths's next hop are shown.
The circuit of the first path next hop is shown.
- Cause:
- New service started on NLSP internetwork.
- Cause:
- Existing service becomes reachable, due to changes in network
connectivity.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.199 max paths exceeded for typ= service_type
nm=[ service_name
] from IPX circuit ID
ax paths exceeded for typ=%x nm=[%.48S] from %S
- Long Syntax:
- IPX.199 max paths exceeded for typ= service_type
nm=[ service_name
] from IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- An alternate path to a given SAP has been found
However, it will not be placed into the routing tables
because the number of paths for this SAP is already at the
maximum number to be kept.
- Cause:
- Maximum routes kept per SAP may be too small.
- Action:
- None, if your network is working properly.
- Action:
- Increase the maximum paths kept per IPX destination network.
This is also called the maximum splitting degree.
- Level:
- U-INFO
- Short Syntax:
- IPX.200 RIP alt rt: net ipx_net
, ticks
ticks, hops
hops, via ipx_net
/ ipx_node
on IPX circuit ID
IP alt route: network %X, %d ticks, %hops, via %X/%E on %S
- Long Syntax:
- IPX.200 RIP alt route: network ipx_net
, ticks
ticks, hops
ops, via ipx_net
/ ipx_node
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- An alternative RIP route had been added to the routing table
routing table. The ticks and hops for the route are shown.
The network and node numbers of the route's next hop are shown.
The circuit of the next hop route is shown.
- Level:
- C-INFO
- Short Syntax:
- IPX.201 RIP rt chg: net ipx_net
, ticks
ticks, hops
hops, via ipx_net
/ ipx_node
on IPX circuit ID
IP route changed: network %X, %d ticks, %hops, via %X/%E on %S
- Long Syntax:
- IPX.201 RIP route changed: network ipx_net
, ticks
ticks, hops
ops, via ipx_net
/ ipx_node
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP route to given IPX network has changed in some way, that is
ticks, hops, or the next hop is different.
The ticks and hops for the route are shown.
The network and node numbers of the route's next hop are shown.
The circuit of the next hop route is shown.
- Level:
- P-TRACE
- Short Syntax:
- IPX.202 RIP qry frm NLSP nbr src_ipx_node
, IPX circuit ID
IP query from NLSP nbr %E, %S
- Long Syntax:
- IPX.202 RIP query from NLSP nbr src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP general query packet was received from a known NLSP neighbor.
Since we are using NLSP to talk to this neighbor, a RIP
response is not sent back to the neighbor. The packet is discarded.
- Level:
- P-TRACE
- Short Syntax:
- IPX.203 SAP qry frm NLSP nbr src_ipx_node
, IPX circuit ID
AP query from NLSP nbr %E, %S
- Long Syntax:
- IPX.203 SAP query from NLSP nbr src_ipx_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A SAP general query packet was received from a known NLSP neighbor.
Since we are using NLSP to talk to this neighbor, a SAP
response is not sent back to the neighbor. The packet is discarded.
- Level:
- U-INFO
- Short Syntax:
- IPX.204 Def exit rt: net ipx_net
, ticks
ticks, hops
hops, via ipx_net
/ ipx_node
on IPX circuit ID
efault exit route: network %X, %d ticks, %hops, via %X/%E on %S
- Long Syntax:
- IPX.204 Default exit route: network ipx_net
, ticks
ticks, hops
ops, via ipx_net
/ ipx_node
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A new NLSP Default exit route has been added to
the routing table. The ticks and hops for the route are shown.
There may be more than one path, but only one the first one
is displayed by this message. This route is derived from
looking at the level 2 flag in the Link State Packets.
The network and node numbers of the first paths's next hop are shown.
The circuit of the first path next hop is shown.
- Level:
- U-INFO
- Short Syntax:
- IPX.205 aged out: path to dest_net
from next_hop
on IPX circuit ID
ged out: path to %X from %E on circ %S
- Long Syntax:
- IPX.205 aged out: path to dest_net
from next_hop
on circ IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A path to an IPX network has aged out.
- Cause:
- No RIP routing updates have been received to refresh this entry
for the age out time. The age out time is the update interval
times the multiplier.
The update interval is usually one minute. The multiplier is
ususally 3 or 4. The update interval and multiplier are configurable
on a circuit basis.
- Level:
- U-INFO
- Short Syntax:
- IPX.206 RIP: path down to dest_net
from next_hop
on IPX circuit ID
IP: path down to %X from %E on %S
- Long Syntax:
- IPX.206 RIP: path down to dest_net
from next_hop
on IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A path to an IPX network is not longer reachable.
- Cause:
- Remote network, or intervening network, went down.
- Action:
- Find out why remote network went down.
- Cause:
- Network is on router that went down.
- Action:
- Find out why remote router went down.
- Cause:
- Network is connected via File Server that was administratively
taken down.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.207 Preallocation failed for structure_name
strucutre
- Long Syntax:
- IPX.207 Preallocation failed for structure_name
strucutre
- Description:
- The router id not have enough memory to
create a private pool of structures. Possible structures are:
- Level:
- UI-ERROR
- Short Syntax:
- IPX.208 Allocation of structure_name
strucutre failed
- Long Syntax:
- IPX.208 Allocation of structure_name
strucutre failed
- Description:
- Allocation of an IPX strucutre failed.
- Level:
- ALWAYS
- Short Syntax:
- IPX.209 FAILURE: internal network number not configured
- Long Syntax:
- IPX.209 failure: internal network number not configured
- Description:
- An IPX internal network number must be defined if IPXWAN or NLSP
is going to be used. An IPX internal network number is also
very useful as a consistent network number to PING when testing
reachability.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.210 no buf for NetBIOS, IPX circuit ID
o buffer available for NETBIOS, %S
- Long Syntax:
- IPX.210 no buffer available for NETBIOS, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- No packet buffer is available to propagate this IPX NETBIOS packet.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.211 no buf for RIP, IPX circuit ID
o buffer available for RIP, %S
- Long Syntax:
- IPX.211 no buffer available for RIP, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- No packet buffer is available to answer a specific RIP query.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.212 no buf for RIP query, IPX circuit ID
o buffer available to send RIP query, %S
- Long Syntax:
- IPX.212 no buffer available to send RIP query, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- No packet buffer is available to send a RIP query.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.213 no buf to make RIP resp, IPX circuit ID
o buffer available to make RIP response, %S
- Long Syntax:
- IPX.213 no buffer available to make RIP response, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- No packet buffer is available to send a RIP response.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.214 no buf to make SAP GNS resp, IPX circuit ID
o buffer available to send a SAP GNS response, %S
- Long Syntax:
- IPX.214 no buffer available to send a SAP GNS response, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- No packet buffer is available to send a SAP Get Nearest Server
response.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.215 no buf to send SAP query, IPX circuit ID
o buffer available to send a SAP query, %S
- Long Syntax:
- IPX.215 no buffer available to send a SAP query, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- No packet buffer is available to send a SAP query.
- Level:
- UI-ERROR
- Short Syntax:
- IPX.216 no buf to make SAP response, IPX circuit ID
o buffer available to make SAP response, %S
- Long Syntax:
- IPX.216 no buffer available to make SAP response, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- No packet buffer is available to send a SAP response.
- Cause:
- Temporary packet buffer shortage due to traffic peak.
- Action:
- None.
- Level:
- P-TRACE
- Short Syntax:
- IPX.217 RIP RTR flt PASS pkt frm source_net
/ source_node
, IPX circuit ID
IP Router filter PASS packet from %X/%E, %S
- Long Syntax:
- IPX.217 RIP Router filter PASS packet from source_net
/ source_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP packet has successfully PASSED through the RIP Router filter
for this circuit.
The RIP Router filter is based upon the source_node in the IPX
packet header, which is displayed by the message.
- Level:
- P-TRACE
- Short Syntax:
- IPX.218 RIP RTR flt DROP pkt frm source_net
/ source_node
, IPX circuit ID
IP Router filter DROP packet from %X/%E, %S
- Long Syntax:
- IPX.218 RIP Router filter DROP packet from source_net
/ source_node
, IPX circuit ID
īzlīzkčīzlhīzkøīzl(īzlXīzlīzlHīzl8
- Description:
- A RIP packet has DROPPED by the RIP Router filter
for this circuit.
The RIP Router filter is based upon the source_node in the IPX
packet header, which is displayed by the message.
- Level:
- P-TRACE
- Short Syntax:
- IPX.219 RIP iodirection
flt PASS net ipx_net
,