msdp Messages

msdp Messages

This chapter describes messages generated by the msdp subsystem.

Major
Message: Failed to aquire a valid Router Id.
Meaning: MSDP failed to acquire a router ID. Any MSDP protocol communication with the outside world has been halted.

Action: Contact Avici customer support.
Message: Failed to process type <TLV type> message from peer <IP1>.<IP2>.<IP3>.<IP4>. Resetting peering session.
Meaning: The TLV could not be processed successfully. This results in resetting the current peering session to make way for a fresh TCP connection. If this is the Passive side of the TCP connection, it waits for a new connection from its peer; else it actively connects to re-establish the connection.

Action: Since this an envelope message, the reason for the error should be investigated in concert with other related log messages.
Message: Failed to read type <TLV type> message from peer<IP1>.<IP2>.<IP3>.<IP4>. Resetting peering session.
Meaning: A read failed, because attempts to read the remaining bytes, in order to form the complete TLV after reading the type, failed. If the peer is passive, the connection is terminated, then we terminate, otherwise the connection is re-established.

Action: Except for the case when the packet type is invalid, the event indicates that there was an error while reading out a TLV. A more specific error cause may be indicated by related log messages preceding this one such as: - an invalid length specified in the TLV : this case may be preceded by LS_MSDP_RCVBIGMSG if it was too long. - socket read failure - indicated by LS_MSDP_EOFERR(info log) or LS_MSDP_READERRNO(info log). If the type received was unknown, this log would be preceded by LS_MSDP_UNKNWNTYPE. Contact Avici customer support.
Message: MSDP initialisation FAILED. Error : <error string>
Meaning: The MSDP master task failed because of the following possible errors. error 1 => task alloc failure, error 2 => task create failure, error 3 => task block malloc failure, error 4 => MSDP mrt create failure, error 5 => MSDP hbt malloc failure, error 6 => MSDP sacache malloc failure. MSDP will not be functional in the router.

Action: If the problem persists, Contact Avici Customer Support.
Message: Message rcvd from peer <IP1>.<IP2>.<IP3>.<IP4> exceeds max msg size ver <MSDP version>, type <TLV type>, size <size of message received>, maxsize <maximum size of message>
Meaning: The reception of an SA TLV with size greater than maximum size of a SA TLV has occurred. The maximum allowed size depends on the version configured: V13 = 9192; V6 = 1400.

Action: This event can indicate that version6 is communicating with version13. Make sure both ends run the same version. Under rare circumstances, this event could indicate a corruption of the packet that escaped checksum verification. If the issue persists, contact Avici customer support.
Message: Send Trap msdpBackwardTransition for peer <IP1>.<IP2>.<IP3>.<IP4> (newState : <reason>).
Meaning: A trap has been sent to indicate that a backward transition for the specified peer has occurred due to a change in the local interface.

Action: No action required.
Message: Socket read error or unexpected remote TCP connection close by the peer <IP1>.<IP2>.<IP3>.<IP4>. Resetting peering session.
Meaning: MSDP failed to read the TLV 'type' byte because of a socket read error.

Action: Since this is an envelope message, the reason for the failure should be investigated in concert with other related log messages: LS_MSDP_EOFERR(info log) or LS_MSDP_READERRNO(info log). If this event occurs on an infrequent basis, there may not be any issue requiring attention. If the event persists, contact Avici customer support.

Minor
Message: Communication between PIM and MSDP failed.
Meaning: Communication between PIM and MSDP failed because the PIM register message failed. MSDP tried to register more than once with PIM.

Action: This event may or may not be significant. PIM may have tried to register more than once. If PIM-SM is configured on any up interface, try to see if MSDP and PIM are still communicating. PIM-SM and MSDP effectively interact only when the router acts as an RP for one or more groups. Contact Avici customer support.
Message: Failed to send data to peer <IP1>.<IP2>.<IP3>.<IP4>. Resetting peering session.
Meaning: An attempt to flush out the spooled data failed, and is not ready to write for the specified peer. The session will be reset.

Action: Contact Avici customer support.
Message: Out SA message job not started
Meaning: A failure to create an out-sa-messages job which forwards SA messages recieved from peers occurred. There will be more attempts to create the job.

Action: If the problem persists, Contact Avici Customer Support.
Message: Sent Trap msdpEstablished for peer <IP1>.<IP2>.<IP3>.<IP4> (numEstabTrans <# of transitions to establised state>).
Meaning: A new passive session has been establised and a trap has been sent.

Action: No action required.

Warning
Message: (S,G) Deletion Event received for (<IP1>.<IP2>.<IP3>.<IP4>/<mask>, <IP5>.<IP6>.<IP7>.<IP8>) which does not exist in MSDP MRT which is learned from PIM.
Meaning: PIM is attempting to delete an entry which is not in the MSDP database.

Action: There may be two cases: - PIM tried to delete SG more than once, which may not have an adverse impact, or there may be an inconsistency between the PIM and MSDP databases. Contact Avici customer support.
Message: Bad RP (martian, zeronet or multicast) addr (<IP1>.<IP2>.<IP3>.<IP4>) recvd in SA from <IP5>.<IP6>.<IP7>.<IP8>. Rejecting.
Meaning: The RP address received in the SA message is incorrect. The SA will be rejected.

Action: Use show ip msdp peer <address> advertised-sa on the PEER router to verify the SGs (along with associated RPs) being advertised. If the problem persists, contact Avici customer support.
Message: Bad group address (<IP1>.<IP2>.<IP3>.<IP4>) received in SA-Request from <IP5>.<IP6>.<IP7>.<IP8>. Rejecting.
Meaning: The group address in an SA request from the specified peer is incorrect.

Action: Avici does not send out any SA Request messages. A non-Avici router at the other end may not be encoding the correct address. Under rare circumstances it could indicate a corrupt packet that escaped checksum verification. If the problem persists, contact Avici customer support.
Message: Bad group address for (S,G) (<IP1>.<IP2>.<IP3>.<IP4>, <IP5>.<IP6>.<IP7>.<IP8>) received in SA from <IP9>.<IP10>.<IP11>.<IP12>. Rejecting S,G
Meaning: The group address in the received SA is incorrect. The S,G will be deleted from SA message. This SA will be forwarded without the rejected S,G. The connection to the peer will be reset.

Action: Use the show ip msdp peer <address> advertised-sa command on the PEER router to verify the SGs being advertised. If the problem remains unresolved, contact Avici customer support.
Message: Bad mask length (<length>) recevied in SA for source <IP1>.<IP2>.<IP3>.<IP4> from <IP5>.<IP6>.<IP7>.<IP8>. Rejecting.
Meaning: The mask length of the source is incorrect. The SA will be rejected. The connection will be reset.

Action: Use the show ip msdp peer <address> advertised-sa command on the PEER router to verify the SGs being advertised. In very rare cases it could indicate a packet corruption that escaped checksum verification. If the problem remains unresolved, contact Avici customer support.
Message: Bad source address (<IP1>>.<IP2>.<IP3>.<IP4>) received in SA from <IP5>.<IP6>.<IP7>.<IP8>. Rejecting.
Meaning: A bad source address has been received in an SA message.

Action: Use the show ip msdp peer <address> advertised-sa command on the PEER router to verify the SGs being advertised. If the problem remains unresolved, contact Avici customer support.
Message: Call to accept connection from <IP1>.<IP2>.<IP3>.<IP4> failed. ERROR: <error string>
Meaning: An incoming call on the MSDP socket failed.

Action: Contact Avici customer support.
Message: Connect attempt to <IP1>.<IP2>.<IP3>.<IP4> failed. Will retry.
Meaning: The connection attempt to the specified peer failed. A retry will occur.

Action: This event indicates a failure to connect to the remote peer. It may not be a problem if it happens infrequently. However, if it continues to happen for the same peer, - check the MSDP peer configuration on both the routers and make sure they are compatible - make sure the configured peer address on one router is the same as the configured local address on the other router. - make sure that both the interfaces bearing the end point addresses of the intended MSDP sessions are UP. - make sure that there exists end to end route for the end points to reach each other. If these checks do not resolve the problem, contact Avici customer support.
Message: Connection attempt failed from local address <IP1>.<IP2>.<IP3>.<IP4> for peer <IP5>.<IP6>.<IP7>.<IP8> due to Error: = <socket error string>.
Meaning: A connection attempt to the specified peer has failed due to the error displayed. There will be more connection attempts.

Action: If the error persists, contact Avici customer support.
Message: Creation of SG-Creation-Send-Job failed.
Meaning: An error creating the job which sends S,G in MSDP MRT to a new PIM component occurred. Multicast packets will not be sent or received across this PIM domain.

Action: The system may be overloaded or there may be memory utilization issues. The memory usage on the server may be monitored using show memory server <server_id> [group | bucket-size | verbose] command. If the problem persists, contact Avici customer support.
Message: Disassociation event received for unassociated PIM component, <task name>
Meaning: MSDP received a disassociation event for an unassociated PIM component.

Action: This event may or may not be significant. PIM may have tried to de-register more than once. If PIM-SM is configured on any up interface, try to see if MSDP and PIM are still communicating. PIM-SM and MSDP effectively interact only when the router acts as an RP for one or more groups. Contact Avici customer support.
Message: Extraction of local IP address failed
Meaning: An attempt to extract a local address from the socket failed. The session will not be established.

Action: Contact Avici customer support.
Message: Failed to create (S,G) entry for (<IP1>.<IP2>.<IP3>.<IP4>/<mask>, <IP5>.<IP6>.<IP7>.<IP8>) learned from PIM-SM.
Meaning: The (S,G) creation learned from PIM-SM failed. It may get created later.

Action: If the problem persists, contact Avici customer support.
Message: Failed to create (S,G) for (<IP1>.<IP2>.<IP3>.<IP4>, <IP5>.<IP6>.<IP7>.<IP8>). Rejecting SA TLV from <IP9>.<IP10>.<IP11>.<IP12>.
Meaning: A failure creating an S,G entry learned from SA TLV occurred. The SA TLV is being rejected. Failure may be due to problems creating MSDP MRT entry.

Action: If the problem persists, contact Avici customer support.
Message: Failed to create Listener task for session with peer <IP1>.<IP>.<IP3>.<IP4>. ERROR : <error string>
Meaning: The listener task creation for the specified peer has failed due to the error displayed. The connection attempt by the peer failed.

Action: If the problem persists, contact Avici customer support.
Message: Failed to create SA flush Timer
Meaning: A failure to create an out-sa-messages timer occurred. This timer is used to forward SA Messages which were not forwarded initially. There will be more attempts to create the timer.

Action: If the problem persists, Contact Avici Customer Support.
Message: Failed to setup active peer from local <IP1>.<IP2>.<IP3>.<IP4> to remote <IP5>.<IP6>.<IP7>.<IP8> Error = <Socket error string>
Meaning: There was an error setting up the active peer. It could be because of problems in creating peer task or some socket errors. There will be no further connection attempts.

Action: Delete the MSDP peer configurations and add them back again. Contact Avici Customer Support, if the problem persists.
Message: Incoming connection invalid due to getpeername failure. ERROR: <error string>
Meaning: IPriori was unable to obtain the address of the remote end of the accepted TCP connection. MSDP session request was rejected.

Action: Contact Avici customer support.
Message: Incoming connection invalid due to getsockname failure. ERROR: <error string>
Meaning: An incoming MSDP connection request failed. MSDP was unable to obtain the local address of an accepted TCP connection. Assure that the peer specified the correct (as configured on the local router) destination address. Peer's session request is rejected.

Action: Contact Avici customer support.
Message: Listener initialization failed. ERROR: <error string>
Meaning: An MSDP Listener task creation failure occurred with the error displayed.

Action: If this problem persists, contact Avici Customer Support.
Message: Local & Remote IPs are the same local: <IP1>.<IP2>.<IP3>.<IP4> remote: <IP5>.<IP6>.<IP7>.<IP8>.
Meaning: An error adding a new MSDP peer occurred, because the local and remote IP address are the same. This is a possible configuration error. Make sure that the peer address configured using the ip msdp peer <peer_address> command is not the same as any of the locally configured addresses.

Action: Check the configuration for an address error.
Message: Local SA, (S,G) got filtered, but could not be removed from the periodic advertisement Q, SA Adv. Q Deq Fail, Yes PIM filter : (<IP1>.<IP2>.<IP3>.<IP4>, <IP5>.<IP6>.<IP7>.<IP8>), RP : <IP9>.<IP10>.<IP11>.<IP12>
Meaning: This event will only occur while the user updates the policy filter at the PIM - MSDP interface using CLI ip msdp redistribute command. Local SA, (s,g) was filtered, but could not be removed from the periodic advertisement queue. This S,G will be included in all the periodic SAs.

Action: This event may indicate a PIM-MSDP database inconsistency. PIM-SM and MSDP effectively interact only when the router acts as an RP for one or more groups. Contact Avici customer support.
Message: MSDP -> PIMSM (S,G) not added : (<IP1>.<IP2>.<IP3>.<IP4>/<source mask>, <IP5>.<IP6>.<IP7>.<IP8>), I am NOT RP.
Meaning: An (S,G) entry learned by MSDP was not added to the PIM-SM MRT because it is not the RP for the group.

Action: If MSDP is running on a non-RP intermediate router or the router is not the RP for given group, this is just informational and no action needs to be taken. If the router is the RP for the group, and this log comes once in a while, it is probably because of the RP convergence delay - no action needs to be taken in this case. If the message comes out consistently, check the RP configuration on the router to make sure it indeed is working as the RP. If no configuration issue is seen, contact Avici customer support.
Message: MSDP HA Max Wait timer fired. Starting MSDP peers
Meaning: MSDP waits for the NSR® transition to complete to make sure that interfaces, routes, etc., are up before it attempts to establish TCP connections with its peers. This message is logged when MSDP does not receive the NSR® complete event before a predefined wait period expires. IPriori will attempt to establish connections.

Action: Use show ip msdp peer summary command to find out if the connections are established. If the sessions are not established, wait for some time and check again. If problem persists, enable debug command 'debug ip msdp all' to know more about the reason for connection failure. Contact Avici customer support if the problem persists.
Message: Memory allocation for session info failed
Meaning: A memory allocation failure occurred while trying to allocate memory for the session bucket. The session will not come up.

Action: The system may be overloaded or there may be memory utilization issues. The memory usage on the server may be monitored using show memory server <server_id> [group | bucket-size | verbose] command. If the problem persists, contact Avici customer support.
Message: Mesh group creation failed. Non unique mesh group id created. Mesh group = <mesh group name>, ID = <mesh group id>
Meaning: The specified mesh group ID creation failed. RPF check may fail and SA messages may not be processed.

Action: Contact Avici customer support.
Message: New SA msg buf info not allocated. Dropping SA message
Meaning: A Memmory allocation for storing PIM context failed. The PIM context is used later when the MSDP MRT entries expire due to MSDP refresh timeouts from its peers.

Action: The system may be overloaded or there might be memory utilization issues. The memory usage on the server may be monitored using the show memory server <server_id> [group | bucket-size | verbose] command. Contact Avici customer support.
Message: Notification rcvd : <notification information>
Meaning: Information is provided about a received notification.

Action: A notification message is sent by the peer when it detects some error with the MSDP session. The sender may or may not reset the session. Also, the Notification message may direct the receiver to reset the session. The error condition (code and subcode) can be interpreted from the IETF MSDP spec - draft-ietf-msdp-spec-06 or draft-ietf-msdp-spec-13 depending on the configured version. If the issue is not well understood, contact Avici customer support.
Message: Notification received from peer : <IP1>.<IP2>.<IP3>.<IP4>, Type of Notification : <notification type> <error and subcode>>
Meaning: A notification message was received from the specified peer. The type of notification, error code, and suberror code are displayed.

Action: The error condition (code and subcode) can be interpreted from the IETF MSDP spec - draft-ietf-msdp-spec-06 or draft-ietf-msdp-spec-13 depending on the configured version.
Message: Out SA Msg Dropped: src <IP1>.<IP2>.<IP3>.<IP4>, dst <IP5>.<IP6>.<IP7>.<IP8>, length = <SA length in bytes> bytes, SG count = <# of SGs>, RP = <IP9>.<IP10>.<IP11>.<IP12>
Meaning: An out SA message with the specified source address was dropped. This problem could be because of a task block allocation failure or task memory alloction failure. MSDP will attempt to send the SA message again to the peer.

Action: If the problem persists, contact Avici customer support.
Message: PIM component block allocation failed
Meaning: A memory allocation failure occurred for a new PIM component. There will not be communication any between the new PIM component and MSDP.

Action: The system may be overloaded or there may be memory utilization issues. The memory usage on the server may be monitored using show memory server <server_id> [group | bucket-size | verbose] command. If the problem persists, contact Avici customer support.
Message: PIMSM got encap. data from MSDP, send error on <interface name> (<IP1>.<IP2>.<IP3>.<IP4>), ERROR :<error string>
Meaning: A send error has occured while forwarding the encapsulated data from MSDP.

Action: If this issue persists, contact Avici customer support.
Message: Peer index HBT peer_node memory allocation failed
Meaning: A memory allocation failure occurred while trying to allocate memory for HBT block. The session will not come up.

Action: The system may be overloaded or there might be memory utilization issues. The memory usage on the server may be monitored using show memory server <server_id> [group | bucket-size | verbose] command. If the problem persists, contact Avici customer support.
Message: Periodic SA response Tx could not be sent, write to peer <IP1>.<IP2>.<IP3>.<IP4> failed (<message string>)
Meaning: A socket write failure occurred during the SA Response process. The connection will be reset.

Action: This event is a socket write error. It may not be a problem if it happens infrequently. If the issue persists, contact Avici customer support.
Message: RP node memory allocation failed
Meaning: PIM failed to add an SG to MSDP while allocating memory for a constituent RP structure.

Action: The system may be overloaded or there may be memory utilization issues. The memory usage on the server may be monitored using show memory server <server_id> [group | bucket-size | verbose] command. If the problem persists, contact Avici customer support.
Message: Read error occurred while receiving a KeepAlive from <IP1>.<IP2>.<IP3>.<IP4>.
Meaning: A read error occurred while receiving a Keepalive from the peer. This may be because the received message size is too large or short. The connnection is reset.

Action: The log indicates that there was an error while reading out a TLV. A more specific error cause may be indicated by related log messages preceding this one such as: an invalid length specified in the TLV : this case may be preceded by LS_MSDP_RCVBIGMSG if it was too long. - socket read failure - indicated by LS_MSDP_EOFERR(info log) or LS_MSDP_READERRNO(info log). It may not be a problem if it happens infrequently. If the issue persists, contact Avici customer support.
Message: Read error occurred while receiving a Notification from <IP1>.<IP2>.<IP3>.<IP4>.
Meaning: A read error occurred while reading a notification from peer. The session is now reset.

Action: The log indicates that there was an error while reading out a TLV. A more specific error cause may be indicated by related log messages preceding this one such as: - an invalid length specified in the TLV : this case may be preceded by LS_MSDP_RCVBIGMSG if it was too long. - socket read failure - indicated by LS_MSDP_EOFERR(info log) or LS_MSDP_READERRNO(info log). If the issue persists, contact Avici customer support.
Message: Read error occurred while receiving an SA from peer <IP1>.<IP2>.<IP3>.<IP4>.
Meaning: A read error occured while reading an SA message. The session will be reset.

Action: This is a generic log indicating that there was an error while reading out a TLV. A more specific error cause may be indicated by related log messages preceding this one like ..- an invalid length specified in the TLV : this case may be indicated by LS_MSDP_RCVBIGMSG if it was too long. - socket read failure - indicated by LS_MSDP_EOFERR(info log) or LS_MSDP_READERRNO (info log). If the problem persists, contact Avici customer support.
Message: Read error occurred while receiving an SA-Response from <IP1>.<IP2>.<IP3>.<IP4>.
Meaning: A read error occurred while receiving an SA-Response from the specified peer. This may be because the message did not have enough bytes to read. The connection is reset.

Action: The log indicates that there was an error while reading out a TLV. One of the following more specific errors may be indicated by related log messages preceding this one such as: an invalid length specified in the TLV : this case may be preceded by LS_MSDP_RCVBIGMSG if it was too long. - socket read failure - indicated by LS_MSDP_EOFERR(info log) or LS_MSDP_READERRNO(info log). If the issue persists, contact Avici customer support.
Message: Removal of (<IP1>.<IP2>.<IP3>.<IP4>/<mask>, <IP5>.<IP6>.<IP7>.<IP8>, <IP9>.<IP10>.<IP11>.<IP12>) from the periodic SA queue failed.
Meaning: The attempt to remove an S,G from the periodic SA queue failed.

Action: PIM tried to remove a non-existent entry from the MSDP database. This may not be a problem if it attempted to do it more than once. But it may indicate PIM-MSDP database inconsistency. Contact Avici customer support.
Message: SA Adv. Q Enq Fail, Local SA could not be added to that adv Q, PIM filter removed : (<IP1>.<IP2>.<IP3>.<IP4>, <IP5>.<IP6>.<IP7>.<IP8>), RP : <IP9>.<IP10>.<IP11>.<IP12>
Meaning: This event only occurs while the user updates the policy filter at the PIM - MSDP interface using CLI ip msdp redistribute command. A failure to add SA entries to advertisement queue occurred. The local SA could not be added to that advertisement queue. This (S,G) will not be advertised.

Action: A memory allocation failure may have occurred. The system may be overloaded or there might be memory utilization issues. The memory usage on the server may be monitored using the show memory server <server_id> [group | bucket-size | verbose] command. If the problem persists, contact Avici customer support.
Message: SA Cache insertion of (<IP1>.<IP2>.<IP3>.<IP4>, <IP5>.<IP6>.<IP7>.<IP8>, <IP9>.<IP10>.<IP11>.<IP12>) that learned from PIM failed.
Meaning: MSDP failed to add an SG into its database because of memory allocation failure.

Action: The system may be overloaded or there might be memory utilization issues. The memory usage on the server may be monitored using the show memory server <server_id> [group | bucket-size | verbose] command. If the problem persists, contact Avici customer support.
Message: SA process SG, RP node memory allocation failed
Meaning: MSDP failed to add an SG learned from an SA message received from a peer to its cache. The failure happened while allocating memory for a constituent RP structure.

Action: The system may be overloaded or there may be memory utilization issues. The memory usage on the server may be monitored using show memory server <server_id> [group | bucket-size | verbose] command. If the problem persists, contact Avici customer support.
Message: SA received from <IP1>.<IP2>.<IP3>.<IP4> too short. Rejecting.
Meaning: The SA received from the specified peer is too short. The SA will be rejected.

Action: This event may indicate two different MSDP versions (version 6 and version 13) trying to communicate with each other. Make sure both ends run the same version. If the problem remains unresolved, contact Avici customer support.
Message: SA response to an SA request could not be sent, write to peer <IP1>.<IP2>.<IP3>.<IP4> failed (<message string>)
Meaning: A socket write failure occurred during the SA Request process. The session will be reset.

Action: This event is a socket write error. If the issue persists, contact Avici customer support.
Message: SA-Request received from <IP1>.<IP2>.<IP3>.<IP4> too long. Size is <SA size>. Rejecting.
Meaning: The SA-request from the specified peer is too long. The SA-Request will be rejected.

Action: This event may indicate two different MSDP versions (version 6 and version 13) trying to communicate with each other. Make sure both ends run the same version.
Message: SG src memory allocation failed
Meaning: A memory allocation failure occurred while creating a new data block for an SG in the MSDP MRT. There will not be an MRT entry for the S,G.

Action: The system may be overloaded or there may be memory utilization issues. The memory usage on the server may be monitored using show memory server <server_id> [group | bucket-size | verbose] command. If the problem persists, contact Avici customer support.
Message: Session reference memory allocation failed
Meaning: A memory allocation failure occurred while trying to allocate memory for inserting session reference info into a list. The session will not come up.

Action: The system may be overloaded or there might be memory utilization issues. The memory usage on the server may be monitored using show memory server <server_id> [group | bucket-size | verbose] command. If the problem persists, contact Avici customer support.
Message: Socket creation failure. Session could not be established to peer <IP1>.<IP2>.<IP3>.<IP4>.
Meaning: The attempt to create a socket failed. The session to the specified peer could not be established. There will be more attempts to create this session.

Action: This event indicates failure to create a socket or to set options on it. This is an unexpected system error. It could indicate that the system ran out of resources, because it is overloaded or suffers from a resource utilization issue. Contact Avici customer support.
Message: TLV of type <TLV type> from <IP1>.<IP2>.<IP3>.<IP4> too long. Discarding <TLV length> bytes.
Meaning: The received SA TLV is too long. The message is discarded and notification is sent.

Action: This event may indicate two different MSDP versions (version 6 and version 13) trying to communicate with each other. Make sure both ends run the same version. Contact Avici customer support if the problem remains unresolved.
Message: Unable to create (S,G) entry (<IP1>.<IP2>.<IP3>.<IP4>, <IP5>.<IP6>.<IP7>.<IP8>). Memory allocation failure.
Meaning: A memory allocation failure occurred. The attempt to create an (S,G) entry was discarded

Action: The system may be overloaded or there may be memory utilization issues. The memory usage on the server may be monitored using show memory server <server_id> [group | bucket-size | verbose] command. If the problem persists, contact Avici customer support.
Message: Unknown message type (<message type>) received from <IP1>.<IP2>.<IP3>.<IP4>.
Meaning: An unknown message type was received from the specified peer. The session is reset.

Action: Inform Avici customer support of the new message type.
Message: Validation of incoming connection failed.
Meaning: The validation of an incoming connection request failed.

Action: In most cases this event signifies a configuration error, especially if this is logged repeatedly. In general, this event can happen because of the following reasons: - One of the following events occurred preceding this log: LS_MSDP_GETSOCKNAMEFAIL, LS_MSDP_SOCK2GATEDFAIL, LS_MSDP_GETPEERNAMEFAIL, LS_MSDP_SESSIONEXISTS. Or a configuration error occurred: check the MSDP peer configuration on both the routers and make sure they are compatible. The configured peer address on one router must be same as the configured local address on the other router and vice versa.
Message: Write failed (Host or Net Unreachable), Retrying write to <task name> Number of attempts <# of attempts>
Meaning: An error occured while flushing the peer's spool.

Action: May not indicate a service affecting problem if seen infrequently. If the problem persists, contact Avici customer support.
Message: Write to peer <IP1>.<IP2>.<IP3>.<IP4> failed (<message string>)
Meaning: A socket write failure has occurred while sending an MSDP KeepAlive message. The session will be reset.

Action: This event is a socket write error. If the issue persists, contact Avici customer support.

Information
Message: Forwarding SA Msgs to peers [(src -> dst) = <IP1>.<IP2>.<IP3>.<IP4> -> <IP5>.<IP6>.<IP7>.<IP8>]
Meaning: An SA message has been forwarded to its peer

Action: No action required.
Message: <message string>
Meaning: The results of the RPF check for the MSDP peer are displayed.

Action: No action required.
Message: (S,G) Creation Event received for (<IP1>.<IP2>.<IP3>.<IP4>/<mask>, <IP5>.<IP6>.<IP7>.<IP8>) learned from PIM-SM which already exists in MSDP MRT.
Meaning: PIM has sent notification of a new source but this entry has already been learned from its peer by MSDP.

Action: No action required.
Message: (S,G) Creation event received from PIM task, <IP1>, for (<IP2>.<IP3>.<IP4>.<IP5>/<IP6>.<IP7>.<IP8>.<IP9>.<IP10>) for RP <IP11>.<IP12>.<IP13>.<IP14>.
Meaning: MSDP has received a local (S,G) creation request from PIM-SM.

Action: No action required.
Message: Allocating PeerHold Timer for peer <IP1>.<IP2>.<IP3>.<IP4>.
Meaning: The hold timer for the specified peer is being created.

Action: No action required.
Message: Association Event received for component <task name> which is already associated.
Meaning: MSDP received an association event from a pim component which already exists in the MSDP PIM component set.

Action: No action required.
Message: Bad RP (local) addr (<IP1>.<IP2>.<IP3>.<IP4>) recvd in SA from <IP5>.<IP6>.<IP7>.<IP8>. Rejecting.
Meaning: The RP address received in an SA from the specified peer is incorrect. The SA will be rejected

Action: No action required.
Message: Cleaning up SA in SSM (S,G) (<IP1>.<IP2>.<IP3>.<IP4>,<IP5>.<IP6>.<IP7>.<IP8>).
Meaning: The process of cleaning SA entries that are inconsistent with the new SSM configuration is occuring

Action: No action required.
Message: Cross Mesh Grp Fwd., MSDP v13, mesh-grp-id Rx=<mesh-group-ID Rx> RPF=<RPF mesh-group-ID> Tx=<mesh-group-ID Tx>
Meaning: A Cross Mesh Group Forwarding has occurred.

Action: No action required.
Message: Data not encapsulated, exceeds max size. Data len <data length> max size <maximum size>
Meaning: The data was not encapsulated and exceeds the maximum size.

Action: No action required.
Message: Deleting ConnectRetry Timer for peer <IP1>.<IP2>.<IP3>.<IP4>.
Meaning: The connection retry timer for a peer has been deleted, since there are no more connection attempts.

Action: No action required.
Message: Hold Timer expires for SA cache (S,G,RP):(<IP1>.<IP2>.<IP3>.<IP4>/<mask>, <IP5>.<IP6>.<IP7>.<IP8>, <IP9>.<IP10>.<IP11>.<IP12>).
Meaning: An SA cache entry (S,G,RP) expired because the entry was not refreshed by the receipt of an SA message.

Action: No action required.
Message: Ignoring hold timer expiry for peer <IP1>.<IP2>.<IP3>.<IP4>. Socket has <rxbuffer size> bytes to read.
Meaning: Socket connected to specified peer has some bytes to be read. So holdtimer will be ignored and connection will not be closed.

Action: No action required.
Message: Incoming connection from <IP1>.<IP2>.<IP3>.<IP4> invalid. Session already exists.
Meaning: An incoming MSDP connection request failed due an already existing session with the specified peer.

Action: No action required.
Message: KeepAlive Tx [(src -> dst) = <IP1>.<IP2>.<IP3>.<IP4> -> <IP5>.<IP6>.<IP7>.<IP8>]
Meaning: A keepalive has been sent from the specified source to the specified destination.

Action: No action required.
Message: Keepalive Received [(src -> dst) = <IP1>.<IP2>.<IP3>.<IP4> -> <IP5>.<IP6>.<IP7>.<IP8>]
Meaning: A keepalive message has been received.

Action: No action required.
Message: MSDP -> PIMSM (S,G) : (<IP1>.<IP2>.<IP3>.<IP4>/<source mask>, <IP5>.<IP6>.<IP7>.<IP8>), No valid upstream intf to Src.
Meaning: PIM-SM learned an S,G from MSDP, but the upstream interface for the source is not available. The S,G entry will be added in the MRT.

Action: No action required.
Message: MSDP -> PIMSM (S,G) not added : (<IP1>.<IP2>.<IP3>.<IP4>/<source mask>, <IP5>.<IP6>.<IP7>.<IP8>), No (*,G) entry in PIM MRT.
Meaning: PIM learned an S,G from MSDP, but did not add the entry to MRT because there are no receivers (no *,G entry).

Action: No action required.
Message: MSDP HA task created
Meaning: The MSDP high availability task has been created.

Action: No action required
Message: MSDP HA, notification : ' <notification message> ' recvd from Server State task.
Meaning: MSDP received an HA notificaton from the server.

Action: No action required.
Message: Mesh-grp id Rx=<mesh group id>, RPF check Passed for SA received from <IP1>.<IP2>.<IP3>.<IP4> for RP <IP5>.<IP6>.<IP7>.<IP8>.
Meaning: The RPF check for a received SA with the specified mesh-group ID has passed.

Action: No action required.
Message: New (S,G) entry (<IP1>.<IP2>.<IP3>.<IP4>,<IP5>.<IP6>.<IP7>.<IP8>) created.
Meaning: A new S,G entry in the MSDP MRT has been created.

Action: no action required.
Message: Normal Mesh Grp Fwd., MSDP v6, mesh-grp-id Rx=<mesh-group-ID Rx> Tx=<mesh-group-ID Tx>
Meaning: A normal mesh group was forward.

Action: No action required.
Message: Not forwarding the Encapsulated Data Pkts as TTL =<TTL value>, lower than threshold = <threshold value>, peer <IP1>.<IP2>.<IP3>.<IP4>, (S,G) (<IP5>.<IP6>.<IP7>.<IP8>, <IP9>.<IP10>.<IP11>.<IP12>)
Meaning: The Encapsulated Data packets are not being forwarded because the TTL value of the packet is lower than the configured TTL value.

Action: No action required.
Message: Notification Received [(src -> dst) = <IP1>.<IP2>.<IP3>.<IP4> -> <IP5>.<IP6>.<IP7>.<IP8>]
Meaning: A notification has been received from a peer.

Action: No action required.
Message: PIMSM -> MSDP Add new (S,G) : (<IP1>.<IP2>.<IP3>.<IP4>/<source mask>, <IP5>.<IP6>.<IP7>.<IP8>), RP : <IP9>.<IP10>.<IP11>.<IP12>
Meaning: PIM-SM learned a new (S,G) from MSDP and has added it to its MRT.

Action: No action required.
Message: PIMSM -> MSDP Delete (S,G) : (<IP1>.<IP2>.<IP3>.<IP4>/<source mask>, <IP5>.<IP6>.<IP7>.<IP8>)
Meaning: An S,G has timed out in the PIM MRT and PIM is informing MSDP about this time out.

Action: No action required.
Message: PIMSM got (S,G) create from MSDP : (<IP1>.<IP2>.<IP3>.<IP4>/<source mask>, <IP5>.<IP6>.<IP7>.<IP8>)
Meaning: PIM-SM received an S,G create from MSDP.

Action: No action required.
Message: PIMSM got (S,G) delete from MSDP : (<IP1>.<IP2>.<IP3>.<IP4>/<source mask>, <IP5>.<IP6>.<IP7>.<IP8>)
Meaning: PIM-SM received an S,G delete from MSDP.

Action: No action required.
Message: PIMSM got encap. data from MSDP, Tx on <interface name> (<IP1>.<IP2>.<IP3>.<IP4>)
Meaning: PIM-SM received encapsulated data from MSDP.

Action: No action required.
Message: Peer <IP1>.<IP2>.<IP3>.<IP4> reset by user.
Meaning: the user has manually reset the specified peer.

Action: No action required.
Message: PeerHold Timer expired for peer <IP1>.<IP2>.<IP3>.<IP4>. Closing connection.
Meaning: The timer holding the specified peer has expired. Since no keep alives have been received, the connection will be closed.

Action: No action required.
Message: RP AS number changed. <RP address, old AS #, new AS #>
Meaning: The RP AS number has changed.

Action: No action required.
Message: RPF check Failed for SA received from <IP1>.<IP2>.<IP3>.<IP4> for RP <IP5>.<IP6>.<IP7>.<IP8>.
Meaning: The RPF check for an SA received from the peer has failed. See RPF rules to know more about the failure. The entire SA message is rejected.

Action: No action required.
Message: RPF check Passed for SA received from <IP1>.<IP2>.<IP3>.<IP4> for RP <IP5>.<IP6>.<IP7>.<IP8>.
Meaning: The RPF check passed for a received SA.

Action: No action required.
Message: Read from peer <IP1>.<IP2>.<IP3>.<IP4> returned ERROR : <error string>
Meaning: An error occurred while reading from the specified peer. The error is indicated by the error string. The session will be reset.

Action: No action required.
Message: Read from peer <IP1>.<IP2>.<IP3>.<IP4> returned NETUNREACH or HOSTUNRACH. ERROR: <error string>.
Meaning: An error occurred while reading from the specified peer. This error returned host or net unreachable. This will cause the session to be reset.

Action: No action required.
Message: Received SA in SSM for (S,G) (<IP1>.<IP2>.<IP3>.<IP4>,<IP5>.<IP6>.<IP7>.<IP8>). Ignoring SA TLV entry from <IP9>.<IP10>.<IP11>.<IP12>.
Meaning: An SA received in the SSM range has been rejected, but this will be forwarded if out filters allow.

Action: No action required.
Message: SA Msg Received: src <IP1>.<IP2>.<IP3>.<IP4>, dst <IP5>.<IP6>.<IP7>.<IP8>, length = <SA message length> bytes, SG count = <SG count>, RP = <IP9>.<IP10>.<IP11>.<IP12>
Meaning: An SA message has been received.

Action: No action required.
Message: SA Request Received [(src -> dst) = <IP1>.<IP2>.<IP3>.<IP4> -> <IP5>.<IP6>.<IP7>.<IP8>]
Meaning: An SA request has been received from a peer.

Action: No action required.
Message: SA Request filtered : peer <IP1>.<IP2>.<IP3>.<IP4>, Grp = <IP5>.<IP6>.<IP7>.<IP8>
Meaning: An SA Request from the specified peer for the group has been filtered.

Action: No action required.
Message: SA not sent, mesh-grp-id Rx=<mesh-group-ID Rx> Tx=<mesh-group-ID Tx> : local <IP1>.<IP2>.<IP3>.<IP4>, peer <IP5>.<IP6>.<IP7>.<IP8>
Meaning: An SA message was not forwarded to the specified peer because the peer was in the same mesh group.

Action: No action required.
Message: Sending out SA Msgs to peers [(src -> dst) = <IP1>.<IP2>.<IP3>.<IP4> -> <IP5>.<IP6>.<IP7>.<IP8>]
Meaning: An SA message has been sent to the peer.

Action: No action required.
Message: Socket recv buffer of peer <IP1>.<IP2>.<IP3>.<IP4> is empty (rxbuffer = <recv buffer size>).
Meaning: The receiver buffer of socket connecting to the peer is less than or equal to zero. So the connection will be closed.

Action: No action required.
Message: Unexpected EOF during read from peer <IP1>.<IP2>.<IP3>.<IP4>.
Meaning: An unexpected error occurred while reading from the specified peer. The number of bytes read was zero. The SA message is discarded and the connection is reset.

Action: No action required.
Message: ioctl to get rxbuffer for peer <IP1>.<IP2>.<IP3>.<IP4> failed (errno = <ioctl errno>).
Meaning: The ioctl to obtain socket receive buffer size has failed. The connection will be closed.

Action: No action required.

   Source File Name: msdp.fm
    HTML File Name: msdp.html
    Last Updated: 09/26/06 at 14:21:31

msdp Messages

Major

Minor

Warning

Information

Please email suggestions and comments to: doc@avici.com