Probing BRM (CM) With TCP Packets From Cisco Load Balancer (Doc ID 945011.1)

Last updated on MAY 04, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 to 7.3.1.0.0 [Release 7.3.0 to 7.3.1]
Information in this document applies to any platform.
**Checked for relevance on 05-Nov-2012***
***Checked for relevance on 30-May-2014***

Goal

Probing BRM (i.e. the CM) with TCP packets from Cisco load balancer is causing rapid growth of cm.pinlog, with following  large amount of error messages.

E Tue Sep 22 17:57:18 2009  <m/c>  cm2:18535  cm_login_pw001.c(20):145 1:<m/c>:cm2:17851:-146577184:0:1253659063:0
        bad 1st pcp_receive, err 50
E Tue Sep 22 17:57:18 2009  <m/c>  cm2:18535  cm_child.c(108):2560 1:<m/c>:cm2:17851:-146577184:0:1253659063:0
        CM bad login attempt from ip_addr=<ip addr>:6183, err=50(PIN_ERR_STREAM_EOF), field=0(0)
E Tue Sep 22 17:57:23 2009  <m/c>  cm2:18536  pcp_xdrst.c(51):3075 1:<m/c>:cm2:17851:-146577184:0:1253659063:0
        received PIN_ERR_STREAM_EOF, closing socket
E Tue Sep 22 17:57:23 2009  <m/c>  cm2:18536  cm_login_pw001.c(20):145 1:<m/c>:cm2:17851:-146577184:0:1253659063:0
        bad 1st pcp_receive, err 50
E Tue Sep 22 17:57:23 2009  <m/c> cm2:18536  cm_child.c(108):2560 1:<m/c>:cm2:17851:-146577184:0:1253659063:0
        CM bad login attempt from ip_addr=<ip addr>:7975, err=50(PIN_ERR_STREAM_EOF), field=0(0)
E Tue Sep 22 17:57:28 2009  <m/c>  cm2:18540  pcp_xdrst.c(51):3075 1:<m/c>:cm2:17851:-146577184:0:1253659063:0
        received PIN_ERR_STREAM_EOF, closing socket
E Tue Sep 22 17:57:28 2009  <m/c>  cm2:18540  cm_login_pw001.c(20):145 1:<m/c>:cm2:17851:-146577184:0:1253659063:0
        bad 1st pcp_receive, err 50
...

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms