MTM Events

The following are the events related to MTM.

Event ID: 2000 (Severity: Fatal)

Message
Unable to alloc a buf of size <MLDIGroup|MldIGPort|MldIGPSrc> for <MODULE>
Platforms K, KA, KB, RA, WB, WC, YA, YB, YC
Category MTM
Severity Fatal
Description This log event informs the user that MTM could not allocate memory

Event ID: 2001 (Severity: Fatal)

Message
Unable to alloc a msg buffer for <MODULE>
Platforms K, KA, KB, RA, WB, WC, YA, YB, YC
Category MTM
Severity Fatal
Description This log event informs the user that a message buffer could not be allocated

Event ID: 2002 (Severity: Warning)

Message
Unexpected state/event STATE/EVENT ID in <EVENT ID STATE> statemach
Platforms K, KA, KB, RA, WB, WC, YA, YB, YC
Category MTM
Severity Warning
Description MTM received an event type in a state that was not expected

Event ID: 2003

Message
Rcvd unkwn addr fmly <ADDRESS TYPE> in pkt
Platforms K, KA, KB, RA, WB, WC, YA, YB, YC
Category MTM
Severity Information
Description This log event informs the user that a MTM packet with an unknown address family was received

Event ID: 2004 (Severity: Fatal)

Message
Failed to register IPAM call back routine
Platforms K, KA, KB, RA, WB, WC, YA, YB, YC
Category MTM
Severity Fatal
Description This log event informs the user that the ipam MTM callback routine failed to initialize.

Event ID: 2005 (Severity: Fatal)

Message
Failed to register IFM call back routine
Platforms K, KA, KB, RA, WB, WC, YA, YB, YC
Category MTM
Severity Fatal
Description This log event informs the user that the IFM MTM callback routine failed to initialize.

Event ID: 2006 (Severity: Warning)

Message
Subsystem <MODULE_NAME> api <API_NAME> failed
Platforms K, KA, KB, RA, WB, WC, YA, YB, YC
Category MTM
Severity Warning
Description This log event informs the user that an api in a subsystem is failed

Event ID: 2007 (Severity: Warning)

Message
Internal api <API_NAME> failed: <FAILED_REASON>
Platforms K, KA, KB, RA, WB, WC, YA, YB, YC
Category MTM
Severity Warning
Description This log event informs the user that an api in MTM has failed

Event ID: 2008

Message
IPv6 mcast filter allocation failure:  <FILTER_ALLOC_FAILURE>
Platforms K, KA, KB, RA, WB, WC, YA, YB, YC
Category MTM
Severity Information
Description This log event informs the user that the device has used all mcast filters for ipv6

Event ID: 2009

Message
An IPv6 multicast filter moved to a non-multicast client: <CLIENT_NAME>. Due to this some IPv6 multicast flows may flood.
Platforms K, KA, KB, RA, WB, WC, YA, YB, YC
Category MTM
Severity Information
Description This log event informs the user that the ipv6 filter has been migrated to non mcast client

Event ID: 2010

Message
An IPv4 multicast filter moved to a non-multicast client: <CLIENT_NAME>. Due to this some IPv4 multicast flows may flood.
Platforms K, KA, KB, RA, WB, WC, YA, YB, YC
Category MTM
Severity Information
Description This log event informs the user that the ipv4 filter s been migrated to non mcast client

Event ID: 2011

Message
Per VLAN unknown Data filter for VLAN <VLAN_ID> moved to non multicast client: <CLIENT_NAME> This VLAN now uses shared Unknown Data Filter
Platforms K, KA, KB, RA, WB, WC, YA, YB, YC
Category MTM
Severity Information
Description This log event informs the user that the per vlan DD filter has been migrated to non mcast client

Event ID: 2012

Message
A non-multicast client: <CLIENT_NAME>- is registered with client ID:  <CLIENT_ID>
Platforms K, KA, KB, RA, WB, WC, YA, YB, YC
Category MTM
Severity Information
Description This log event informs the user that Non multicast client has been registered with MTM

Event ID: 2013

Message
A non-multicast client: <CLIENT_NAME>- with client ID: CLIENT-ID got unregistered
Platforms K, KA, KB, RA, WB, WC, YA, YB, YC
Category MTM
Severity Information
Description This log event informs the user that Non multicast client has been Unregistered with MTM