/mcpPlus feature. Examine the switch and the reject message (negative acknowledgement) for any information relating to the reason for the refusal Error Message %UC_PHONE-6-LastOutOfServiceInformation: %[DeviceName=String][DeviceIPv4Address=String] [IPv4DefaultGateway=String][DeviceIPv6Address=String][IPv6DefaultGateway=String] [ModelNumber=String][NeighborIPv4Address=String][NeighborIPv6Address=String] [NeighborDeviceID=String][NeighborPortID=String][VoiceVLAN=String][UnifiedCMIPAddress=String] [LocalPort=String][TimeStamp=String][LastProtocolEventSent=String] [LastProtocolEventReceived=String][DHCPv4Status=Enum][DHCPv6Status=Enum] [TFTPCfgStatus=Enum][DNSStatusUnifiedCM1=Enum][DNSStatusUnifiedCM2=Enum] [DNSStatusUnifiedCM3=Enum][DNSv6StatusUnifiedCM1=Enum][DNSv6StatusUnifiedCM2=Enum] [DNSv6StatusUnifiedCM3=Enum][ReasonForOutOfService=Enum][AppID=String][ClusterID=String] [NodeID=String]: Information related to the last out-of-service event Explanation The device has lost communication with Unified CM, due to a reason such as a network connectivity issue, Unified CM outage, configuration error, and in some cases, a normal unregistration event. A device can go out-of-service for many reasons, both intentional such as manually resetting the device after a configuration change, and unintentional such as loss of network connectivity. Other causes for this alarm could include a device being registered to a secondary node and then the primary node coming online, which causes the device to re-home to the primary Unified CM node. Other error conditions include lack of a KeepAlive being returned from the Unified CM node to which this device was registered, and so on. Recommended Action A Actions to take vary depending on the reason specified in this alarm for why the device went out of service. If the device being out of service is expected (normal occurrence), such as during a manual devie reset, no action is required. Reason codes 18-23 are all normal reason codes. Other reason codes should be investigated to determine why Unified CM is not running or whether a network problem or configuration error exists. In the case of a network connectivity problem or loss of KeepAlives, use network diagnostic tools, the Real-Time Monitoring Tool, and the Cisco Unified CM Reporting tool to evaluate and correct any reported network or Unified CM system errors. In the case of a device re-homing to the primary Unified CM node, watch for a successful registration of the device on the primary node. Also, refer to the reason code descriptions for recommended actions DHCPv4Status - DHCPv4Status Enum Definitions - DHCPv4Status Value Definition 0 1 Successful - DHCPv4 configuration completed without error 2 Successful - DHCPv4 configuration completed without error 5/24/26, 3:34 AM System Error Messages for Cisco Unified Communications Manager 15 - Cisco https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/15_x/ccmalarms15.html 326/343