Messages related to PIM operation

These messages appear in the Event Log and, if syslog debug is configured, in the designated Debug destinations.

NOTE:

The [counter] value displayed at the end of each PIM Event Log message (and SNMP trap messages, if trap receivers are configured) indicates the number of times the switch has detected a recurring event since the last reboot. See the Management and Configuration Guide for your switch.

Message	Meaning
`alpha-string` pkt, src IP `ip-addr` vid `vlan-id` (not a nbr) (`counter`)	A PIM packet arrived from another router for which no neighbor was found. May indicate a misconfiguration between the sending and receiving router. May also occur if a connected router is disconnected, then reconnected.
Bad TTL in State Refresh pkt from IP `source-ip-addr` (`counter`)	The switch detected a TTL of 0 (zero) in the PIM portion of a state-refresh packet. (This is not the IP TTL.)
Failed alloc of HW `alpha-str` for flow `multicast-address` , `source-address` (`dup-msg-cnt`)	There are more than 2046 active flows. The switch routes the excess through software, which processes traffic at a slower rate. If this will be an ongoing or chronic condition, transfer some of the flows to another router.
Failed to alloc a PIM `data-type` pkt (`counter`)	The router was unable to allocate memory for a PIM control packet. Router memory is oversubscribed. Reduce the number of VLANs or increase the hello delay and/or the override interval to reduce the number of simultaneous packet transmissions. If the number of flows exceeds 2046, the excess flows are routed in software, which reduces the number of packet transmissions. In this case, reducing the number of flows by moving some clients to other routers can help.
Failed to initialize `text-str` as a call back routine (`counter`)	Indicates an internal error. Report the incident to your customer care center and reinstall the router software.
I/F configured with IP `ip-address` on vid `vlan-id` (`counter`)	Indicates that the interface (VLAN) has been configured with the indicated IP address. At boot-up or when an IP address is changed, the switch generates this message for each PIM-configured VLAN.
I/F removal with IP `ip-addr` on vid `vlan-id` (`counter`)	Indicates that a PIM interface (VLAN) has been removed from the router as a result of an IP address change or removal.
MCAST flow `multicast-address` `source-address` not rteing (rsc low) (`counter`)	The indicated multicast flow is not routing. The routing switch is low on memory resources as a result of too many flows for the number of configured VLANs. Remedies include one or more of the following: Reduce the number of configured VLANs by moving some VLANs to another router. Free up system resources by disabling another feature, such as one of the spanning-tree protocols or either the RIP or the OSPF routing protocol. (Unless you are using static routes, you will need to retain a minimum of one unicast routing protocol.) Another option that may help is to reduce the number of configured QoS filters. Move some hosts that create multicast demand to another router.
MCAST MAC add for `mac-address` failed (`counter`)	Indicates a hardware problem. Check the cabling and router ports.
Multicast Hardware Failed to Initialize (`counter`)	Indicates a hardware failure that halts hardware processing of PIM traffic. The software will continue to process PIM traffic at a slower rate. Contact your customer care center.
No IP address configured on VID `vlan-id` (`dup-msg-cnt`)	PIM has detected a VLAN without an IP address. Configure an IP address on the indicated VLAN.
Pkt dropped from `ip-address` , ( `cause` ) vid `vlan-id` (`counter`)	A PIM packet from `ip-address` was dropped because of one of the following causes: No PIM interface on the VLAN Bad packet length Bad IP header length Bad IP total length
Pkt rcvd with a cksum error from `ip-addr` (`counter`)	A packet having a checksum error was received from ip-address. Check the cabling and ports on the local and the remote routers.
Rcvd incorrect hello from `ip-addr` (`counter`)	Indicates receipt of a malformed hello packet. (That is, the packet does not match the current specification.) Ensure that compatible versions of PIM-DM are being used.
Rcvd `text-str` pkt with bad len from `ip-addr` (`counter`)	A peer router may be sending incorrectly formatted PIM packets.
Rcvd hello from `ip-address` on vid `vlan-id` (`counter`)	Indicates a misconfiguration where two routers are directly connected with different subnets on the same connected interface.
Rcvd pkt from rtr `ip-address`, unkwn pkt type `value` (`counter`)	A packet received from the router at `ip-address` is an unknown PIM packet type. (The `value` variable is the numeric value received in the packet.)
Rcvd pkt ver# `ver-num`, from `ip-address`, expected `ver-num` (`counter`)	The versions of PIM-DM on the sending and receiving routers do not match. Differing versions are typically compatible, but features not supported in both versions will not be available.
Rcvd unkwn addr fmly `addr-type` in `text-str` pkt from `ip-addr` (`counter`)	The router received a PIM packet with an unrecognized encoding. As of February 2004, the router recognizes IPv4 encoding.
Rcvd unkwn opt `opt-nbr` in `text-string` pkt from `ip-addr` (`counter`)	The router received a PIM packet carrying an unknown PIM option. The packet may have been generated by a newer version of PIM-DM or is corrupt. In most cases, normal PIM-DM operation will continue.
Send error( `failure-type` ) on `packet-type` pkt on VID `vid` ( `counter`)	Indicates a send error on a packet. This can occur if a VLAN went down right after the packet was sent. The message indicates the failure type, the packet type, and the VLAN ID on which the packet was sent.
Unable to alloc `text-str` table (`counter`)	The router was not able to create some tables PIM-DM uses. Indicates that the router is low on memory resources. Remedies include one or more of the following: Reduce the number of configured VLANs by moving some VLANs to another router. Free up system resources by disabling another feature, such as one of the spanning-tree protocols or either the RIP or the OSPF routing protocol. (Unless you are using static routes, you will need to retain a minimum of one unicast routing protocol.) Another option that may help is to reduce the number of configured QoS filters. Move some hosts that create multicast demand to another router.
Unable to alloc a buf of size `bytes` for `data-flow` (`counter`)	Multicast routing is unable to acquire memory for a flow. Router memory is oversubscribed. Reduce the number of VLANs or the number of features in use. Remedies include one or more of the following: Reduce the number of configured VLANs by moving some VLANs to another router. Free up system resources by disabling another feature, such as one of the spanning-tree protocols or either the RIP or the OSPF routing protocol. (Unless you are using static routes, you will need to retain a minimum of one unicast routing protocol.) Another option that may help is to reduce the number of configured QoS filters. Move some hosts that create multicast demand to another router.
Unable to alloc a msg buffer for `text-message` (`counter`)	Multicast routing is unable to acquire memory for a flow. Router memory is oversubscribed. Reduce the number of VLANs or the number of features in use. Remedies include one or more of the following: Reduce the number of configured VLANs by moving some VLANs to another router. Free up system resources by disabling another feature, such as one of the spanning-tree protocols or either the RIP or the OSPF routing protocol. (Unless you are using static routes, you will need to retain a minimum of one unicast routing protocol.) Another option that may help is to reduce the number of configured QoS filters. Move some hosts that create multicast demand to another router.