Refer to the exhibit. A collaboration engineer using the Show eigrp service-family External-client IOS command, noticed that a CUCM failed to register as an external SAF Client on Cisco IOS router named Site CRTR. The engineer has collected snippets of the IOS configuration screenshots and CUCM trace shown in the exhibit.
What is the reason for the registration failure?
A. Password mismatch between CUCM and Router SAF configuration
B. Sf-interface loopback0 command missing under service-family ipv4 autonomous-system 1
C. SIP trunk IP address pointing to a different address than SAF Forwarder address
D. Name mismatch between SAF Forwarder name info field and external-client name on router
E. IP multicast-routing command missing on router configuration
A is correct.
Error 431 — SAF_INTEGRITY_CHECK_FAILURE – A message failed to pass SAF Forwarder security validation. This can occur because of misconfiguration, a potential attack, or more commonly by incorrect provisioning of the password on the Forwarder and SAF client. Reprovision the password and keep a watch on further SAF INTEGRITY CHECK FAILURE alarms. If you receive a persistent number of SAF INTEGRITY CHECK FAILURE alarms, close the interface between SAF Forwarder and Unified CM and investigate the source of the IP packets.