| Component | Message | Cause |
|---|---|---|
| IGMP/MLD | MGMD Protocol Heap Memory Init Failed; Family - xxx. | MGMD Heap memory initialization Failed for the specified address family. This message appears when trying to enable MGMD Protocol. |
| IGMP/MLD | MGMD Protocol Heap Memory De-Init Failed; Family - xxx. | MGMD Heap memory de-initialization Failed for the specified address family. This message appears when trying to disable MGMD (IGMP/MLD) Protocol. As a result of this, the subsequent attempts to enable/disable MGMD will also fail. |
| IGMP/MLD | MGMD Protocol Initialization Failed; Family - xxx. | MGMD protocol initialization sequence Failed. This could be due to the non-availability of some resources. This message appears when trying to enable MGMD Protocol. |
| IGMP/MLD | MGMD All Routers Address - xxx Set to the DTL Mcast List Failed; Mode - xxx, intf - xxx. | This message appears when trying to enable/disable MGMD Protocol. |
| IGMP/MLD | MGMD All Routers Address - xxx Add to the DTL Mcast List Failed. | MGMD All Routers Address addition to the local multicast list Failed. As a result of this, MGMD Multicast packets with this address will not be received at the application. |
| IGMP/MLD | MGMD All Routers Address - xxx Delete from the DTL Mcast List Failed. | MGMD All Routers Address deletion from the local multicast list Failed. As a result of this, MGMD Multicast packets are still received at the application though MGMD is disabled. |
| IGMP/MLD | MLDv2 GroupAddr-[FF02::16] Enable with Interpeak Stack Failed; rtrIfNum - xxx, intf - xxx. | Registration of this Group address with the Interpeak stack failed. As a result of this, MLDv2 packets will not be received at the application. |
| IGMP/MLD | MGMD Group Entry Creation Failed; grpAddr - xxx, rtrIfNum - xxx. | The specified Group Address registration on the specified router interface failed. |
| IGMP/MLD | MGMD Socket Creation/Initialization Failed for addrFamily - xxx. | MGMD Socket Creation/options Set Failed. As a result of this, the MGMD Control packets cannot be sent out on an interface. |
| Component | Message | Cause |
|---|---|---|
| IGMP-Proxy/MLD-Proxy | MGMD-Proxy Protocol Initialization Failed; Family - xxx. | MGMD-Proxy protocol initialization sequence Failed. This could be due to the non-availability of some resources. This message appears when trying to enable MGMD-Proxy Protocol. |
| IGMP-Proxy/MLD-Proxy | MGMD-Proxy Protocol Heap Memory De-Init Failed; Family - xxx. | MGMD-Proxy Heap memory de-initialization is Failed for the specified address family. This message appears when trying to disable MGMD-Proxy Protocol. As a result of this, the subsequent attempts to enable/disable MGMD-Proxy will also fail. |
| IGMP-Proxy/MLD-Proxy | MGMD Proxy Route Entry Creation Failed; grpAddr - xxx, srcAddr - xxx, rtrIfNum - xxx. | Registration of the Multicast Forwarding entry for the specified Source and Group Address Failed when MGMD-Proxy is used. |
Table 67:
| Component | Message | Cause |
|---|---|---|
| PIMSM | Non-Zero SPT/Data Threshold Rate - xxx is currently Not Supported on this platform. | This message appears when the user tries to configure the PIMSM SPT threshold value. |
| PIMSM | PIMSM Protocol Heap Memory Init Failed; Family - xxx. | PIMSM Heap memory initialization Failed for the specified address family. This message appears when trying to enable PIMSM Protocol. |
| PIMSM | PIMSM Protocol Heap Memory De-Init Failed; Family - xxx. | PIMSM Heap memory de-initialization Failed for the specified address family. This message appears when trying to disable PIMSM Protocol. As a result of this, the subsequent attempts to enable/disable PIMSM will also fail. |
| PIMSM | PIMSM Protocol Initialization Failed; Family -xxx. | PIMSM protocol initialization sequence Failed. This could be due to the non-availability of some resources. This message appears when trying to enable PIMSM Protocol. |
| PIMSM | PIMSM Protocol De-Initialization Failed; Family - xxx. | PIMSM protocol de-initialization sequence Failed. This message appears when trying to disable PIMSM Protocol. |
| PIMSM | PIMSM SSM Range Table is Full. | PIMSM SSM Range Table is Full. This message appears when the protocol cannot accommodate new SSM registrations. |
| PIMSM | PIM All Routers Address - xxx Delete from the DTL Mcast List Failed for intf - xxx. | PIM All Routers Address deletion from the local multicast list Failed. As a result of this, PIM Multicast packets are still received at the application though PIM is disabled. |
| PIMSM | PIM All Routers Address - xxx Add to the DTL Mcast List Failed for intf - xxx. | PIM All Routers Address addition to the local multicast list Failed. As a result of this, PIM Multicast packets with this address will not be received at the application. |
| PIMSM | Mcast Forwarding Mode Disable Failed for intf - xxx. | Multicast Forwarding Mode Disable Failed. As a result of this, Multicast packets are still received at the application though no protocol is enabled. |
| PIMSM | Mcast Forwarding Mode Enable Failed for intf - xxx. | Multicast Forwarding Mode Enable Failed. As a result of this, Multicast packets will not be received at the application though a protocol is enabled. |
| PIMSM | PIMSMv6 Socket Memb'ship Enable Failed for rtrIfNum - xxx. | PIMSMv6 Socket Creation/options Set with Kernel IP Stack Failed. As a result of this, the PIM Control packets cannot be received on the interface. |
| PIMSM | PIMSMv6 Socket Memb'ship Disable Failed for rtrIfNum - xxx. | PIMSMv6 Socket Creation/options Disable with Kernel IP Stack Failed. As a result of this, the PIM Control packets are still received on the interface at the application though no protocol is enabled. |
| PIMSM | PIMSM (S,G,RPt) Table Max Limit - xxx Reached; Cannot accommodate any further routes. | PIMSM Multicast Route table (S,G,RPt) has reached maximum capacity and cannot accommodate new registrations anymore. |
| PIMSM | PIMSM (S,G) Table Max Limit - xxx Reached; Cannot accommodate any further routes. | PIMSM Multicast Route table (S,G) has reached maximum capacity and cannot accommodate new registrations anymore. |
| PIMSM | PIMSM (*,G) Table Max Limit - xxx Reached; Cannot accommodate any further routes. | PIMSM Multicast Route table (*,G) has reached maximum capacity and cannot accommodate new registrations anymore. |
| Component | Message | Cause |
|---|---|---|
| PIMDM | PIMDM Protocol Heap Memory Init Failed; Family - xxx. | PIMDM Heap memory initialization Failed for the specified address family. This message appears when trying to enable PIMDM Protocol. |
| PIMDM | PIMDM Protocol Heap Memory De-Init Failed; Family - xxx. | PIMDM Heap memory de-initialization Failed for the specified address family. This message appears when trying to disable PIMDM Protocol. As a result of this, the subsequent attempts to enable/disable PIMDM will also fail. |
| PIMDM | PIMDM Protocol Initialization Failed; Family -xxx. | PIMDM protocol initialization sequence Failed. This could be due to the non-availability of some resources. This message appears when trying to enable PIMDM Protocol. |
| PIMDM | PIMDM Protocol De-Initialization Failed; Family - xxx. | PIMDM protocol de-initialization sequence Failed. This message appears when trying to disable PIMDM Protocol. |
| PIMDM | PIM All Routers Address - xxx Delete from the DTL Mcast List Failed for intf - xxx. | PIM All Routers Address deletion from the local multicast list Failed. As a result of this, PIM Multicast packets are still received at the application though PIM is disabled. |
| PIMDM | PIM All Routers Address - xxx Add to the DTL Mcast List Failed for intf - xxx. | PIM All Routers Address addition to the local multicast list Failed. As a result of this, PIM Multicast packets with this address will not be received at the application. |
| PIMDM | Mcast Forwarding Mode Disable Failed for intf - xxx. | Multicast Forwarding Mode Disable Failed. As a result of this, Multicast packets are still received at the application though no protocol is enabled. |
| PIMDM | Mcast Forwarding Mode Enable Failed for intf - xxx. | Multicast Forwarding Mode Enable Failed. As a result of this, Multicast packets will not be received at the application though a protocol is enabled. |
| PIMDM | PIMDMv6 Socket Memb'ship Enable Failed for rtrIfNum - xxx. | PIMDMv6 Socket Creation/options Set with Kernel IP Stack Failed. As a result of this, the PIM Control packets cannot be received on the interface. |
| PIMDM | PIMDMv6 Socket Memb'ship Disable Failed for rtrIfNum - xxx. | PIMDMv6 Socket Creation/options Disable with Kernel IP Stack Failed. As a result of this, the PIM Control packets are still received on the interface at the application though no protocol is enabled. |
| PIMDM | PIMDM FSM Action Invoke Failed; rtrIfNum - xxx Out of Bounds for Event - xxx. | The PIMDM FSM Action invocation Failed due to invalid Routing interface number. In such cases, the FSM Action routine can never be invoked which may result in abnormal behavior. The failed FSM-name can be identified from the specified Event name. |
| PIMDM | PIMDM Socket Initialization Failed for addrFamily - xxx. | PIMDM Socket Creation/options Set Failed. As a result of this, the PIM Control packets cannot be sent out on an interface. |
| PIMDM | PIMDMv6 Socket Memb'ship Enable Failed for rtrIfNum - xxx. | Socket options Set to enable the reception of PIMv6 packets Failed. As a result of this, the PIMv6 packets will not be received by the application. |
| PIMDM | PIMDMv6 Socket Memb'ship Disable Failed for rtrIfNum - xxx. | PIMDMv6 Socket Creation/options Disable with Kernel IP Stack Failed. As a result of this, the PIMv6 Control packets are still received on the interface at the application though no protocol is enabled. |
| PIMDM | PIMDM MRT Table Max Limit - xxx Reached; Cannot accommodate any further routes. | PIMDM Multicast Route table (S,G) has reached maximum capacity and cannot accommodate new registrations anymore. |
| Component | Message | Cause |
|---|---|---|
| DVMRP | DVMRP Heap memory initialization is Failed for the specified address family. | This message appears when trying to enable DVMRP Protocol |
| DVMRP | DVMRP Heap memory de-initialization is Failed for the specified address family. | This message appears when trying to disable DVMRP Protocol. As a result of this, the subsequent attempts to enable/disable DVMRP will also fail. |
| DVMRP | DVMRP protocol initialization sequence Failed. | This could be due to the non-availability of some resources. This message appears when trying to enable DVMRP Protocol. |
| DVMRP | DVMRP All Routers Address - xxx Delete from the DTL Mcast List Failed for intf - xxx. | DMVRP All Routers Address deletion from the local multicast list Failed. As a result of this, DVMRP Multicast packets are still received at the application though DVMRP is disabled. |
| DVMRP | Mcast Forwarding Mode Disable Failed for intf - xxx. | The Multicast Forwarding mode Disable Failed for this routing interface. |
| DVMRP | DVMRP All Routers Address - xxx Add to the DTL Mcast List Failed for intf - xxx. | DMVRP All Routers Address addition to the local multicast list Failed. As a result of this, DVMRP Multicast packets with this address will not be received at the application. |
| DVMRP | Mcast Forwarding Mode Enable Failed for intf - xxx. | The Multicast Forwarding mode Enable Failed for this routing interface. As a result of this, the ability to forward Multicast packets does not function on this interface. |
| DVMRP | DVMRP Probe Control message Send Failed on rtrIfNum - xxx. | DVMRP Probe control message send failed. This could mostly be because of a Failure return status of the socket call sendto(). As a result of this, the DVMRP neighbor could be lost in the neighboring DVMRP routers. |
| DVMRP | DVMRP Prune Control message Send Failed; rtrIfNum - xxx. | Neighbor - %s, SrcAddr - %s, GrpAddr - %s DVMRP Prune control message send failed. This could mostly be because of a Failure return status of the socket call sendto(). As a result of this, the unwanted multicast traffic is still received and forwarded. |
| DVMRP | DVMRP Probe Control message Send Failed on rtrIfNum -xxx. | DVMRP Probe control message send failed. This could mostly be because of a Failure return status of the socket call sendto(). As a result of this, the DVMRP neighbor could be lost in the neighboring DVMRP routers. |
