Clarity PPM1

Expand all | Collapse all

CA PPM - Multicast Works with jGroups but not with Tower Shell

Jump to Best Answer
  • 1.  CA PPM - Multicast Works with jGroups but not with Tower Shell

    Posted 03-29-2018 05:52 AM
      |   view attached

    Hi All,

     

    Long time I haven't posted here.

     

    Another problem regarding Multicast on CA PPM 15.3 (Patch 2).
    I have 3 servers on the same subnet as01, web01 and web02 (IP 10.114.12.130,131,132).

     

    No Database Connection has been set yet, it's a fresh install.

     

    Multicast works correctly between servers with jGroups Library (see logs below).
    But admin tower returns randomly either no server, either localhost server.

     

    I reviewed every step mentioned in the very good articles :

    kb000023660

    kb000048555

     

    I even tried increasing Xms/Xmx parameters on beacon service in .setup/script/commondeploy.xml.
    But still no luck.

     

    Could there be a problem with UPD Ports ?

     

    Thk,
    David

     

    Test on Multicast Adress 239.0.0.1 and 9090.

    Version OS
    [adkodapp@silabs-as01-prod ~]$ more /etc/redhat-release
    Red Hat Enterprise Linux Server release 7.4 (Maipo)

    Version CA PPM
    [adkodapp@silabs-as01-prod ~]$ version
    # Full version number
    version=15.3.0.200
    # Clarity-specific additional information
    display.version=${version}
    release=15.3.0
    package.id=15.3.0.2.16
    package.number=02
    package.build=16
    package=15.3.0.2.16
    build=16
    package.ref.version=15.3.0.2.16
    package.ref.release=15.3.0.2

    Master as01
    [adkodapp@silabs-as01-prod ~]$ export CLASSPATH=$NIKU_HOME/lib/jgroups-all.jar
    [adkodapp@silabs-as01-prod ~]$ java org.jgroups.tests.McastSenderTest -mcast_addr 239.0.0.1 -port 9090 -bind_addr 10.114.12.132
    Socket #1=0.0.0.0/0.0.0.0:9090, ttl=32, bind interface=/10.114.12.132
    > Test
    > Pour
    > SiLABS
    >

    Slave web01
    [adkodapp@silabs-web01-prod ~]$ export CLASSPATH=$NIKU_HOME/lib/jgroups-all.jar
    [adkodapp@silabs-web01-prod ~]$ java org.jgroups.tests.McastReceiverTest -mcast_addr 239.0.0.1 -port 9090 -bind_addr 10.114.12.130
    Socket=0.0.0.0/0.0.0.0:9090, bind interface=/10.114.12.130
    Test [sender=10.114.12.132:9090]
    Pour [sender=10.114.12.132:9090]
    SiLABS [sender=10.114.12.132:9090]

    Slave web02
    [adkodapp@silabs-web02-prod ~]$ export CLASSPATH=$NIKU_HOME/lib/jgroups-all.jar
    [adkodapp@silabs-web02-prod ~]$ java org.jgroups.tests.McastReceiverTest -mcast_addr 239.0.0.1 -port 9090 -bind_addr 10.114.12.131
    Socket=0.0.0.0/0.0.0.0:9090, bind interface=/10.114.12.131
    Test [sender=10.114.12.132:9090]
    Pour [sender=10.114.12.132:9090]
    SiLABS [sender=10.114.12.132:9090]

    --> Multicast is OK with jGroups

    Admin Tower as01
    [adkodapp@silabs-as01-prod scripts]$ admin tower
    -------------------------------------------------------------------
    GMS: address=silabs-as01-prod-33076, cluster=CLRTY-SA, physical address=10.114.12.132:59665
    -------------------------------------------------------------------
    > refresh
    > list clients
    Discovered Clients:
    --------------------------
    None
    --------------------------
    > refresh
    > list clients
    Discovered Clients:
    --------------------------
    1) silabs-as01-prod:9091 [silabs-as01-prod-55658]
    --------------------------
    > list clients
    Discovered Clients:
    --------------------------
    1) silabs-as01-prod:9091 [silabs-as01-prod-55658]
    --------------------------
    > refresh
    > list clients
    Discovered Clients:
    --------------------------
    1) silabs-as01-prod:9091 [silabs-as01-prod-55658]
    --------------------------
    >

    Admin Tower web01
    [adkodapp@silabs-web01-prod scripts]$ admin tower
    -------------------------------------------------------------------
    GMS: address=silabs-web01-prod-36400, cluster=CLRTY-SA, physical address=10.114.12.130:44607
    -------------------------------------------------------------------
    > refresh
    > list clients
    Discovered Clients:
    --------------------------
    None
    --------------------------
    > list clients
    Discovered Clients:
    --------------------------
    None
    --------------------------
    > list clients
    Discovered Clients:
    --------------------------
    None
    --------------------------
    > list clients
    Discovered Clients:
    --------------------------
    1) silabs-web01-prod:9091 [silabs-web01-prod-8454]
    --------------------------
    >

    Admin Tower web02
    [adkodapp@silabs-web02-prod G02R00C00]$ admin tower
    -------------------------------------------------------------------
    GMS: address=silabs-web02-prod-55567, cluster=CLRTY-SA, physical address=10.114.12.131:41728
    -------------------------------------------------------------------
    > refresh
    > list clients
    Discovered Clients:
    --------------------------
    None
    --------------------------
    > list clients
    Discovered Clients:
    --------------------------
    None
    --------------------------
    >
    list clients
    Discovered Clients:
    --------------------------
    None
    --------------------------
    > list clients
    Discovered Clients:
    --------------------------
    1) silabs-web02-prod:9091 [silabs-web02-prod-17958]
    --------------------------
    >

    Attachment(s)



  • 2.  Re: CA PPM - Multicast Works with jGroups but not with Tower Shell

    Posted 04-04-2018 06:14 AM

    Hi,

     

    Further test with admin tower command. Feature Trace (ON/OFF) can send messages between servers but  I still cannot see all servers in CSA UI or in admin tower > "list clients"...

     

    Env as01 as Master
    > refresh
    > list clients
    Discovered Clients:
    --------------------------
    1) silabs-as01-prod:9091 [silabs-as01-prod-7593]
    --------------------------
    > trace
    Trace 1 sent on 239.0.0.1:9090...
    Trace 2 sent on 239.0.0.1:9090...
    Trace 3 sent on 239.0.0.1:9090...
    Trace 4 sent on 239.0.0.1:9090...
    Trace complete.
    > trace
    Trace 1 sent on 239.0.0.1:9090...
    Trace 2 sent on 239.0.0.1:9090...
    Trace 3 sent on 239.0.0.1:9090...
    Trace 4 sent on 239.0.0.1:9090...
    Trace complete.
    >

     

    Env web01 as Slave
    > refresh
    > list clients
    Discovered Clients:
    --------------------------
    1) silabs-web01-prod:9091 [silabs-web01-prod-34666]
    --------------------------
    > trace on
    Tracing ON
    > RECEIVED from silabs-web02-prod-30030 -> Beacon/Client [10.114.12.131:9091:silabs-web02-prod]
    RECEIVED from silabs-as01-prod-54890 -> Trace 1
    RECEIVED from silabs-web01-prod-34666 -> Beacon/Client [10.114.12.130:9091:silabs-web01-prod]
    RECEIVED from silabs-as01-prod-54890 -> Trace 2
    RECEIVED from silabs-as01-prod-54890 -> Trace 3
    RECEIVED from silabs-as01-prod-54890 -> Trace 4
    RECEIVED from silabs-web02-prod-30030 -> Beacon/Client [10.114.12.131:9091:silabs-web02-prod]
    RECEIVED from silabs-web01-prod-34666 -> Beacon/Client [10.114.12.130:9091:silabs-web01-prod]
    RECEIVED from silabs-web02-prod-30030 -> Beacon/Client [10.114.12.131:9091:silabs-web02-prod]
    RECEIVED from silabs-web01-prod-34666 -> Beacon/Client [10.114.12.130:9091:silabs-web01-prod]
    RECEIVED from silabs-web02-prod-30030 -> Beacon/Client [10.114.12.131:9091:silabs-web02-prod]
    RECEIVED from silabs-web01-prod-34666 -> Beacon/Client [10.114.12.130:9091:silabs-web01-prod]

     

    In $NIKU_HOME/logs/app-ca.log, I have logs like :

    WARN 2018-04-05 10:27:43,633 [Incoming-1,CLRTY-SA,silabs-as01-prod-23421] niku.nsa (none:none:none:none) Client failure: silabs-web01-prod:9091 at 10.114.12.130:9091. Ignoring until next manual refresh. Cause: Exception creating connection to: 10.114.12.130; nested exception is:
    java.net.NoRouteToHostException: No route to host (Host unreachable)
    WARN 2018-04-05 10:27:34,284 [Incoming-1,CLRTY-SA,silabs-web01-prod-56593] niku.nsa (none:none:none:none) Client failure: silabs-as01-prod:9091 at 10.114.12.132:9091. Ignoring until next manual refresh. Cause: Exception creating connection to: 10.114.12.132; nested exception is:
    java.net.NoRouteToHostException: No route to host (Host unreachable)

    The problem seems to be at network level.

    Which protocols are needed on ports 9090 and 9091 ? UDP (for Multicast) and TCP (for Unicast) ?

     

    Any idea ?

     

    Thx,

    David



  • 3.  Re: CA PPM - Multicast Works with jGroups but not with Tower Shell
    Best Answer

    Posted 04-12-2018 03:27 AM

    Hi again,

     

    Ultimately, I added rules at firewall level on OS where CA PPM is installed :

     

    - 7500 : UDP

    - 9090-9091 : UDP and TCP

    32768-60999 : UDP and TCP

     

    The port range is found in file /proc/sys/net/ipv4/ip_local_port_range

     

    The article Clarity: Fact Sheet: Clarity Beacon with Multicast - CA Knowledge speaks about the possibility to define port range for multicast functionality (Q8). I think it would be really nice to have this feature. My network contact found very strange for a service called "NSA", that we could not define it at software level 

     

    Regards,

    David