Large number of ulcm_sctp messages

Hi,

I am running Solaris-10 sparc and I am seeing large number of messages related to ulcm_sctp .

I tried to google, what these messages are and how it should be fixed, but I am not getting much information about it. Can somebody please some pointer or suggestion ?

Sep 24 07:04:23 prod01-sspp2 kernel: ulcm_sctp: [ID 702911 kern.warning] WARNING: Verification Tag mismatch... packet dropped.
Sep 24 07:04:23 prod01-sspp2 kernel: ulcm_sctp: [ID 702911 kern.warning] WARNING: Verification Tag mismatch... packet dropped.
Sep 24 07:19:38 prod01-sspp2 kernel: ulcm_sctp: [ID 702911 kern.warning] WARNING: Received OOTB packet... responding with an ABORT
Sep 24 07:19:38 prod01-sspp2 kernel: ulcm_sctp: [ID 702911 kern.warning] WARNING: Received OOTB packet... responding with an ABORT

Thanks

Please tell us what exactly is this process and what process is the parent of this process:

ulcm_sctp

If you do not know the answer, please run:

ps -ef

and, using CODE tags, cut-and-paste the output of the above command in your reply.

Thanks.

I think, I should have checked it more carefully

I thought, it is some OS process. But it is an application running by application team. I will check with them, what is causing it. Thanks for the pointer.

No worries.

We are always here to help.

Actually the message is issued by a kernel driver for the sctp network protocol.

SCTP
SctpChannel (SCTP API )

Perhaps this particular message is caused by multiple interfaces and asymmetric routing, where an expected answer packet is received on the wrong interface.

This page might also be useful:

Stream Control Transmission Protocol -
Oracle(R) Solaris 11.3 Programming Interfaces Guide

Oh.. I was about to throw it to application team.

I tried to understand from pages mentioned by you, but I am not getting clue, what must be failing. Here is config for this server, if you can see something helpful and suggest.

bash-3.2# ps -ef | grep -i ulcm
    root  1417     1   0   Mar 21 ?        7463:54 /opt/ulcm/bin/DFdaemon
    root  1420     1   0   Mar 21 ?           1:13 /usr/sbin/sctpd -omni_home /opt/ulcm
    root 29870     1   0   Dec 06 ?         238:58 /opt/ulcm/bin/slan /opt/ulcm/conf/slan.cf -sctp
  appadm 20326     1   0   Apr 18 ?         732:09 /bin/bash -p /opt/ulcm/bin/go.omni
    root 29929     1   0   Dec 06 ?          91:28 /opt/ulcm/bin/port_daemon -f portConf.100
    root 23587 23567   0 10:00:25 pts/2       0:00 grep -i ulcm
  appadm 21062 20326   0   Apr 18 ?           0:00 /opt/ulcm/bin/nrplinker
bash-3.2# cat /opt/ulcm/conf/slan.cf
dpserv-icp1-prod dpserv-icp2-prod none
dpserv-icp2-prod none dpserv-icp1-prod
bash-3.2#
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
e1000g0: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 2
        inet 172.30.68.208 netmask fffffe00 broadcast 172.30.69.255
        groupname data
        ether 0:21:28:44:7:d6
e1000g0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.30.64.208 netmask ffffff00 broadcast 172.30.64.255
e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
        inet 172.30.96.208 netmask ffffff00 broadcast 172.30.96.255
        ether 0:21:28:44:7:d7
e1000g3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
        inet 1.1.1.1 netmask fffffffc broadcast 1.1.1.3
        ether 0:21:28:44:7:d9
nxge3: flags=69040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,STANDBY,INACTIVE> mtu 1500 index 5
        inet 172.30.69.208 netmask fffffe00 broadcast 172.30.69.255
        groupname data
        ether 0:21:28:4b:57:31
bash-3.2# netstat -nr

Routing Table: IPv4
  Destination           Gateway           Flags  Ref     Use     Interface
-------------------- -------------------- ----- ----- ---------- ---------
default              172.30.64.1          UG        1    6624951
1.1.1.0              1.1.1.1              U         1      51480 e1000g3
10.0.0.0             172.30.96.1          UG        1      42652
172.30.64.0          172.30.64.208        U         1        126 e1000g0:1
172.30.68.0          172.30.69.208        U         1       9550 e1000g0
172.30.68.0          172.30.69.208        U         1       9629 nxge3
172.30.68.210        172.30.68.210        UGH       1         20
172.30.68.211        172.30.68.211        UGH       1          0
172.30.68.212        172.30.68.212        UGH       1          1
172.30.69.210        172.30.69.210        UGH       1          1
172.30.69.211        172.30.69.211        UGH       1          1
172.30.69.212        172.30.69.212        UGH       1          1
172.30.96.0          172.30.96.208        U         1      35786 e1000g1
172.30.96.0          172.30.96.1          UG        1        300
172.30.99.0          172.30.96.1          UG        1     100602
172.30.160.0         172.30.96.1          UG        1          0
192.168.64.0         172.30.96.1          UG        1        738
192.168.110.0        172.30.96.1          UG        1        396
192.168.115.0        172.30.96.1          UG        1          0
192.168.201.0        172.30.96.1          UG        1          0
192.168.202.0        172.30.96.1          UG        1          0
224.0.0.0            172.30.64.208        U         1          0 e1000g0:1
127.0.0.1            127.0.0.1            UH       53   78379273 lo0
bash-3.2#

That depends.

Are you sure that sctp is required for the application and not some remnant or rouge process which is not necessary?

If it is deemed not necessary, just kill it and move on. That's the first step, I think.... confirm that the applications on the server require this service.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.