ELS Messages for Routing Information Protocol (RIP)
- Level:
- UE-ERROR
- Short Syntax:
- RIP.001 bd ver version_number
frm hst source_IP_address
- Long Syntax:
- RIP.001 bad version version_number
received from host source_IP_address
- Description:
- The version field in the RIP header did not match the current
version.
- Cause:
- This is probably caused by an error in the source host.
- Action:
- Contact the manufacturer of the source host and report the problem.
- Level:
- U-TRACE
- Short Syntax:
- RIP.002 rq frm source_IP_address
- Long Syntax:
- RIP.002 request received from host source_IP_address
- Description:
- A RIP routing table request was received from another host. A
routing table update will be sent to it.
- Level:
- U-INFO
- Short Syntax:
- RIP.003 trc on tracing_file
frm source_IP_address
- Long Syntax:
- RIP.003 trace on to tracing_file
received from host source_IP_address
- Description:
- A request from a host to turn RIP tracing on to a given log
file was received. The router ignores this request.
- Level:
- U-INFO
- Short Syntax:
- RIP.004 trc off frm source_IP_address
- Long Syntax:
- RIP.004 trace off received from host source_IP_address
- Description:
- A request from a host to turn RIP tracing off was received.
The router ignores this request.
- Level:
- C-TRACE
- Short Syntax:
- RIP.005 rsp frm source_IP_address
- Long Syntax:
- RIP.005 response received from host source_IP_address
- Description:
- A RIP routing table update was received. Note that it may take
more than one response packet to transmit the entire routing
table, especially if the routing table is large.
- Level:
- UE-ERROR
- Short Syntax:
- RIP.006 bd cmd command_code
frm source_IP_address
- Long Syntax:
- RIP.006 bad command code command_code
received from host source_IP_address
- Description:
- A RIP message was received with an unrecognized command code.
- Cause:
- This is probably caused by an error or out of date software in
the source host.
- Action:
- Contact the manufacturer of the source host and report the problem.
- Level:
- UE-ERROR
- Short Syntax:
- RIP.007 rsp frm off nt source_IP_address
- Long Syntax:
- RIP.007 response received from off network host source_IP_address
- Description:
- A RIP routing update response was received from a machine which
was not directly attached to the network the response came in on.
The packet is discarded.
- Cause:
- Since normal RIP software is generally written to send data only
to connected nets, this is probably indicative of a hostile event.
- Action:
- Examine audit trails and other information to determine the
original source host.
- Level:
- UE-ERROR
- Short Syntax:
- RIP.008 sbnt rt destination_IP_network
non-subnt intfc hst next_hop_IP_address
- Long Syntax:
- RIP.008 subnet route destination_IP_network
on non-subnetted interface from host next_hop_IP_address
- Description:
- An apparent subnet route (i.e. the 'rest' field of the Internet
address contained non-zero data) was received over an interface
that is not marked as subnetted in the router.
- Cause:
- This is probably caused by incorrect configuration, either in
the router or in the host sending the traffic.
- Action:
- Correct the incorrect configuration.
- Level:
- U-TRACE
- Short Syntax:
- RIP.009 dyn rt to destination_IP_network
frm next_hop_IP_address
dis
- Long Syntax:
- RIP.009 dynamic route to destination_IP_network
from next_hop_IP_address
disallowed
- Description:
- A dynamic route was received but is being ignored because the
configuration of RIP on the router does not allow dynamic routes
except for those in a table, and this route was not in that table.
- Level:
- U-INFO
- Short Syntax:
- RIP.010 nt destination_IP_address
unrch via next_hop_IP_address
, del
- Long Syntax:
- RIP.010 network destination_IP_address
now unreachable via router next_hop_IP_address
, deleted
- Description:
- An incoming RIP update from the router that was previously
listed as the next hop to the destination network has announced
that the destination is unreachable (i.e. at metric 'infinity').
The RIP route to that destination is being deleted.
- Level:
- U-INFO
- Short Syntax:
- RIP.011 updt nt destination_IP_network
hps metric
via next_hop_IP_address
- Long Syntax:
- RIP.011 update route to net destination_IP_network
at metric metric
hops via router next_hop_IP_address
- Description:
- A new (better) route to the given destination has been learned
via RIP and has been installed.
- Level:
- C-TRACE
- Short Syntax:
- RIP.012 snd rqst source_IP_address
- Long Syntax:
- RIP.012 send request from address source_IP_address
- Description:
- The router is sending a RIP request from each of the addresses
associated with an interface which has just come up.
- Level:
- C-TRACE
- Short Syntax:
- RIP.013 snd brd to destination_IP_address
packet_count
pkts number_of_routes
rtes
- Long Syntax:
- RIP.013 sending broadcast response to address destination_IP_address
in packet_count
packets with number_of_routes
routes
- Description:
- The router is sending a normal RIP broadcast update (triggered either
by a timer or a change in the routing table) to the specified
address.
- Level:
- C-INFO
- Short Syntax:
- RIP.014 snd to destination_IP_address
packet_count
pkts number_of_routes
rtes, net network
- Long Syntax:
- RIP.014 sending response to address destination_IP_address
in packet_count
packets with number_of_routes
routes, network network
- Description:
- The router is sending a RIP update (triggered by a request
from another host) to the specified address.
- Level:
- CI-ERROR
- Short Syntax:
- RIP.015 cnt all pkt
- Long Syntax:
- RIP.015 cannot allocate packet for transmission
- Description:
- When RIP went to allocate a packet for transmission (either for
a request or reply), none was available.
- Level:
- C-TRACE
- Short Syntax:
- RIP.016 snd pkt destination_IP_address
, net network
- Long Syntax:
- RIP.016 sending packet to destination_IP_address
, network network
- Description:
- A RIP packet (either a routing table update, or when an interface
first comes up, a request) was sent.
- Level:
- UI-ERROR
- Short Syntax:
- RIP.017 err output_error_code
sndng pkt nt network
- Long Syntax:
- RIP.017 error code output_error_code
when sending packet out net network
- Description:
- An outgoing reply packet was dropped as the result of some
problem in the router.
- Cause:
- There are many potential causes of this problem, such as an overloaded
output queue, a down network, etc.
- Action:
- Consult logging output from the relevant network subsystem
for more information.
- Level:
- U-INFO
- Short Syntax:
- RIP.018 nt rt to destination_IP_address
tmd out
- Long Syntax:
- RIP.018 network route to destination_IP_address
timed out
- Description:
- A route to a destination via some other router in the routing
database has not been heard from for a while and is now being
marked as unreachable.
- Level:
- U-INFO
- Short Syntax:
- RIP.019 nt rt to destination_IP_address
del
- Long Syntax:
- RIP.019 network route to destination_IP_address
deleted
- Description:
- A route to a destination via some other router in the routing
database has not been heard from for a while, has been marked
unreachable, and is now being deleted.
- Level:
- U-INFO
- Short Syntax:
- RIP.020 prot act/deact
on IP_address
, net network
- Long Syntax:
- RIP.020 the protocol is act/deact
ive on IP_address
, net network
- Description:
- The RIP protocol is either active or deactive on the specified
interface.
- Level:
- UE-ERROR
- Short Syntax:
- RIP.021 auth fail from IP_source
, cmd RIP_command
- Long Syntax:
- RIP.021 packet authentication failure from IP_source
, command RIP_command
- Description:
- A RIP packet is discarded because it has failed to authenticate.
1; Request, 2; Response, 3; Traceon, 4; Traceoff
- Level:
- U-INFO
- Short Syntax:
- RIP.022 pkt source_ip_address
-> destination_ip_address
dsc, net network
- Long Syntax:
- RIP.022 packet from source_ip_address
for destination_ip_address
discarded, network network
- Description:
- A RIP packet is discarded either because the interface is not
active, or the receive option is set to not receive packets.
- Level:
- C-TRACE
- Short Syntax:
- RIP.023 snd mcast to destination_IP_address
, packet_count
pkts number_of_routes
rtes
- Long Syntax:
- RIP.023 sending multicast response to address destination_IP_address
in packet_count
packets with number_of_routes
routes
- Description:
- The router is sending a normal RIP multicast update (triggered
either by a timer or a change in the routing table) to the
specified address.
- Level:
- U-INFO
- Short Syntax:
- RIP.024 nbr destination_IP_address
del, net network
- Long Syntax:
- RIP.024 neighbor destination_IP_address
deleted on net network
- Description:
- The specified neighbor has not been heard from for a while.
Hence the neighbor is being deleted from the database.
- Level:
- CI-ERROR
- Short Syntax:
- RIP.025 mem alloc fld, neighbor/interface
IP_address
- Long Syntax:
- RIP.025 failed to allocate memory for neighbor/interface
IP_address
- Description:
- RIP has failed to allocate memory for the neighbor from whom
we have just received an update. Hence the update will not
be processed.
Or
RIP has failed to allocate either static or dynamic memory for
the interface structure. Hence RIP will not be run on the
specified interface address.
- Level:
- C-INFO
- Short Syntax:
- RIP.026 bad next hop nexthop_IP_address
from source_IP_address
- Long Syntax:
- RIP.026 non existent next hop nexthop_IP_address
is received from source_IP_address
- Description:
- The router has neither a RIP route, nor a direct route to the
specified next hop for the advertised net/subnet. Hence, rather
than rejecting the advertised route, the route is installed with
the source IP address as the next hop.
- Level:
- C-TRACE
- Short Syntax:
- RIP.027 rcv trig pkt_type
frm source_IP_address
, fl flush_bit
, seq seq_number
- Long Syntax:
- RIP.027 received triggered pkt_type
from source_IP_address
, flush flush_bit
, seqno seq_number
- Description:
- A RIP routing table update "request/response/acknowledge" was
received with the specified sequence number and the flush bit.
- Level:
- C-TRACE
- Short Syntax:
- RIP.028 snd trig pkt_type
to dest_IP_address
, fl flush_bit
, seq seq_number
, rtes routes
, net network
- Long Syntax:
- RIP.028 sending triggered pkt_type
to dest_IP_address
, fl flush_bit
, seq seq_number
, rtes routes
, net network
- Description:
- A RIP routing table update "request/response/acknowledge" was
sent with the specified sequence number and the flush bit.
- Level:
- CI-ERROR
- Short Syntax:
- RIP.029 bad flush/seq in req frm IP_address
- Long Syntax:
- RIP.029 bad flush or sequence field in the request from IP_address
- Description:
- The received request from the specified neighbor does not
have zero flush or sequence field. Hence the request will
not be processed.
- Level:
- CI-ERROR
- Short Syntax:
- RIP.030 unexp flush rcvd in trig response_or_acknowledge
frm IP_address
- Long Syntax:
- RIP.030 unexpected flush received in triggered response_or_acknowledge
from IP_address
- Description:
- The flush bit in the triggered update response or acknowledge
is set, which was never expected. Hence the update response or
acknowledge will not be processed.
- Level:
- CI-ERROR
- Short Syntax:
- RIP.031 flush not rcvd in trig pkt_type
frm IP_address
- Long Syntax:
- RIP.031 flush not received in triggered pkt_type
from IP_address
- Description:
- The expected flush bit in the triggered update response or
acknowledge is not set. Hence the update response or
acknowledge will not be processed.
- Level:
- CI-ERROR
- Short Syntax:
- RIP.032 unexp seq seqno
rcvd in trig pkt_type
, expecting expected_seqno
frm IP_address
- Long Syntax:
- RIP.032 unexpected sequence seqno
received in triggered pkt_type
, expecting expected_seqno
from IP_address
- Description:
- The sequence number in the received triggered update response is
different than what we were expecting. Hence the response will
not be processed.
- Level:
- C-INFO
- Short Syntax:
- RIP.033 add sub-opt rte IP_address
via nexthop_IP_address
, cost cost
, asnum asnumber
, net Network
- Long Syntax:
- RIP.033 add sub-optimal route IP_address
via nexthop_IP_address
, cost cost
, asnum asnumber
, net Network
- Description:
- Add a sub-optimal route entry for the specified route with
with specified hop count, AS number and next hop address.
- Level:
- CI-ERROR
- Short Syntax:
- RIP.034 insuf mem for sub-opt rte IP_address
frm Neighbor_IP_address
, net Network
- Long Syntax:
- RIP.034 insufficient memory for sub-optimal route IP_address
from Neighbor_IP_address
, net Network
- Description:
- We have failed to allocate memory for a sub-optimal route received
from a triggered RIP neighbor. RIP may refuse to acknowledge the
received update response so the neighbor can try sending the response
again.
- Level:
- C-INFO
- Short Syntax:
- RIP.035 del sub-opt rte IP_address
, net Network
- Long Syntax:
- RIP.035 delete sub-optimal route IP_address
, net Network
- Description:
- Delete a sub-optimal route that can be reached via the
specified network.
- Level:
- U-INFO
- Short Syntax:
- RIP.036 recl sub-opt rt to network
via next-hop_addr
, net Network
- Long Syntax:
- RIP.036 recall sub-optimal route to net network
via next-hop_addr
, net Network
- Description:
- This message is generated when a sub-optimal route to a network
is brought back into use.
- Level:
- CI-ERROR
- Short Syntax:
- RIP.037 rej trig rip snd opt on IP_address
, net Network
- Long Syntax:
- RIP.037 reject triggered RIP send option on IP_address
, net Network
- Description:
- Triggered RIP is not legal on a non-point-to-point type interface;
The RIP send mode is changed to RIPv1 only if the send mode
was TrigV1, or to RIPv2 only if the send mode was TrigV2.
- Level:
- CI-ERROR
- Short Syntax:
- RIP.038 rej trig rip cmd on IP_address
, net Network
- Long Syntax:
- RIP.038 reject triggered RIP command received on IP_address
, net Network
- Description:
- The triggered RIP command has been rejected either because it was
received on a non-serial interface or because the send options
on that interface are not set to send triggered commands.
- Level:
- U-INFO
- Short Syntax:
- RIP.039 rej req on IP_address
, net Network
- Long Syntax:
- RIP.039 reject request received on IP_address
, net Network
- Description:
- A request to send all routes is received on an interface configured
to send only triggered commands. Hence, the request is rejected.
- Level:
- UE-ERROR
- Short Syntax:
- RIP.040 bd rip_packet_type,
, err= formatting_error
frm hst source_IP_address
- Long Syntax:
- RIP.040 bad rip_packet_type,
, error= formatting_error
frm host source_IP_address
- Description:
- A RIP packet (request), is badly formatted, and is discarded,
or the routing entry is discarded.
For rsp (response) packets, the possible formatting errors are:
(1) length, in which case the length of the RIP part of the packet
was greater than 512, or the length was not a multiple
of the RIP routing entry size (20 bytes); (2) srcport, which means
that the source UDP port was not 520, (3) must-be-zero, which means
version 1 updates must-be-zero fields were not zero.
For rq (request) packets, the possible formatting errors are:
(1) metric, in which case the metric was not 16.
- Cause:
- This is probably caused by an error in the source host.
- Action:
- Contact the manufacturer of the source host and report the problem.
- Level:
- UE-ERROR
- Short Syntax:
- RIP.041 lost trig peer peer_IP_address,
on IP_address
- Long Syntax:
- RIP.041 lost triggerd peer peer_IP_address,
on IP_address
- Description:
- Contact with the peer router involved in triggered RIP has
been lost. The routes learned from triggered RIP, which are
normally not aged out, will now be subject to aging.
- Cause:
- The interface has come down or the peer is not responding to our
triggerd RIP messages.
- Panic
- ripudperr
- Short Syntax:
- rip udp port not avail
- Description:
- Another application registered previously with rip's UDP port.
- Action:
- Contact customer service.