Persistant Solaris 11 dlmpd error messages

UNIX Solaris
1

Hello all, I'm not having much luck figuring out why this machine keeps sending these messages. svcs -xv is clean. Machine was just patched via latest IPS. I would appreciate any help offered.

Jan 21 00:48:54 t4 in.dlmpd[752]: [ID 646763 daemon.debug] dlm_icmp_sock_handler(127.0.0.1/127.0.0.1) incorrect ICMP type 3
Jan 21 00:51:15 t4 in.dlmpd[752]: [ID 581309 daemon.debug] process_rtsock: message 5
Jan 21 01:01:15 t4 last message repeated 1 time
Jan 21 04:00:00 t4 in.dlmpd[752]: [ID 347446 daemon.debug] dlm_icmp_sock_handler(inet)
Jan 21 04:00:00 t4 in.dlmpd[752]: [ID 646763 daemon.debug] dlm_icmp_sock_handler(127.0.0.1/127.0.0.1) incorrect ICMP type 3
Jan 21 04:00:00 t4 in.dlmpd[752]: [ID 347446 daemon.debug] dlm_icmp_sock_handler(inet)
Jan 21 04:00:00 t4 in.dlmpd[752]: [ID 646763 daemon.debug] dlm_icmp_sock_handler(127.0.0.1/127.0.0.1) incorrect ICMP type 3
Jan 21 04:01:14 t4 in.dlmpd[752]: [ID 581309 daemon.debug] process_rtsock: message 5
Jan 21 04:11:14 t4 last message repeated 1 time
Jan 21 06:41:15 t4 in.dlmpd[752]: [ID 581309 daemon.debug] process_rtsock: message 5     

Unusual System Events
=-=-=-=-=-=-=-=-=-=-=
Jan 21 06:41:15 t4 in.dlmpd[752]: [ID 581309 daemon.debug] process_rtsock: message 5 Jan 21 06:44:33 t4 in.dlmpd[752]: [ID 347446 daemon.debug] dlm_icmp_sock_handler(inet) 
Jan 21 06:44:33 t4 in.dlmpd[752]: [ID 847213 daemon.debug] dlm_icmp_sock_handler(143.228.37.129/143.228.37.162) unknown interface 
Jan 21 06:44:38 t4 in.dlmpd[752]: [ID 347446 daemon.debug] dlm_icmp_sock_handler(inet) 
Jan 21 06:44:38 t4 in.dlmpd[752]: [ID 847213 daemon.debug] dlm_icmp_sock_handler(143.228.37.162/143.228.37.162) unknown interface SU 01/21 06:4
2

How is your multipathing set up? These kinds of errors seem to arise when a given protocol - looks like icmp to me - has issues or when there is a hardware problem like a problem NIC. Does not appear to be hardware.

fmadm faulty

will answer the hardware problem.

I would seriously consider the fact that you just patched as being related to your symptoms.

3

Agreed on the patching. I surveyed 4 systems that were patched, half had svc:/network/dlmp:default enabled, half did not. This problem did have it enabled. I disabled it and no more messages. Obviously, I need to research this further.

fmadm faulty is clean and thank you for that reminder, Jim!