CA Client Automation

  • Private Community

  • 1.  One of my Scalabilities fail the communication only with the domain

    Posted Jun 23, 2015 05:47 PM

    Hi dudes,

     

    My teammate is having a problem with a Scalability.

     

    The communication with the Scalability and its domain, work properly but suddenly stop to respond the caf ping and camping.

     

    We uninstall the McAfee antivirus to prevent that the antivirus was blocking the communication.

     

    It's weird because the domain communicate successfully with other Scalability.

     

    I found these lines:

     

     

    000000|NOTIFY | command line: "caf" "ping" "172.16.65.53"

    230615-14:35:13.4189869L|000216|00001008|CAF_CMD   |CcnfAgentApi    |CCcnfAgentApi.cpp 

    |000087|NOTIFY | New CCcnfAgentApi 0x353238, instcount 1, sesscount 0

     

    230615-14:35:13.4191579L|000216|00001008|CAF_CMD   |CcnfAgentApi    |CCcnfAgentApi.cpp 

    |000206|NOTIFY | CCcnfAgentApi::Init() 0x353238, instcount 1, sesscount 0

     

    230615-14:35:13.5275955L|000216|00001008|CAF_CMD   |cfCafApi         

    |000000|ERROR  | CFSmMessenger::setHostInfo: SmGetSecFlags: (0x33001) Session messaging has not been properly initialized by calling SmInitialize.

     

    230615-14:35:13.5543373L|000216|0000075c|CAF_CMD   |CFSMCAPI     

    |000000|NOTIFY | ReaperThread : Polling every 60 seconds for sessions that have been inactive for 1200 seconds

     

    230615-14:35:14.2421360L|000216|00001008|CAF_CMD   |CFSMCAPI 

    |000000|NOTIFY | SMEVENT : New Endpoint. Handle 0x00357ff0 Name CAI000216-00000

     

    230615-14:35:14.2427730L|000216|00001008|CAF_CMD   |CFSMCAPI   

    |000000|NOTIFY | SMEVENT : New Session. Target = (172.16.65.53) 172.16.65.53\U-CAF. LID = 00d80001. SH = 00363640

     

    230615-14:35:44.2579225L|000216|00001008|CAF_CMD   |CFSMCAPI     

    |000000|ERROR  | SmiSession::FindEndpoint : failed with 0x0003300C

     

    230615-14:35:44.2580399L|000216|00001008|CAF_CMD   |CFSMCAPI     

    |000000|ERROR  | SmiSession::SConnect : caught SMSTATUS=0x0003300C

     

    230615-14:35:44.2629170L|000216|00001008|CAF_CMD   |cfCafApi 

    |000000|ERROR  | CFSmMessenger::sendAndGetReply: msg send failed: The specified operation has expired. The timeout is usually a client supplied value.

     

    230615-14:35:44.2630058L|000216|00001008|CAF_CMD   |cfCafApi   

    |000000|ERROR  | CFMessenger::sendCmd: failed: The specified operation has expired. The timeout is usually a client supplied value.

     

    230615-14:35:45.7874051L|000216|00001008|CAF_CMD   |CFSMCAPI           

    000000|NOTIFY | SMEVENT : New Session. Target = (172.16.65.53) 172.16.65.53\U-CAF. LID = 00d80002. SH = 00363640

     

    230615-14:36:15.8017075L|000216|00001008|CAF_CMD   |CFSMCAPI           

    |000000|ERROR  | SmiSession::FindEndpoint : failed with 0x0003300C

     

    230615-14:36:15.8018113L|000216|00001008|CAF_CMD   |CFSMCAPI           

    |000000|ERROR  | SmiSession::SConnect : caught SMSTATUS=0x0003300C

     

    230615-14:36:15.8020742L|000216|00001008|CAF_CMD   |cfCafApi             

    |000000|ERROR  | CFSmMessenger::sendAndGetReply: msg send failed: The specified operation has expired. The timeout is usually a client supplied value.

     

    230615-14:36:15.8021529L|000216|00001008|CAF_CMD   |cfCafApi       

    |000000|ERROR  | CFMessenger::sendCmd: failed: The specified operation has expired. The timeout is usually a client supplied value.

     

    230615-14:36:17.3154415L|000216|00001008|CAF_CMD   |CFSMCAPI       

    |000000|NOTIFY | SMEVENT : New Session. Target = (172.16.65.53) 172.16.65.53\U-CAF. LID = 00d80003. SH = 00369f98

     

     

     

    Thanks in advance.



  • 2.  Re: One of my Scalabilities fail the communication only with the domain
    Best Answer

    Broadcom Employee
    Posted Jun 24, 2015 03:32 AM

    Hi Oscar,

     

    The problem seems to be a CAM communication problem.

    By default CAM communication is made with UDP 4104 port.

    You could check which port CAM is using for communication with the DOMAIN in result of command "camstat -n"

     

     

    Maybe there is a router or firewall blocking the UDP 4104 communication between the SS and DOMAIN ?

     

    You could check if CAM communication is working in both direction :

    From SS try :

    camping domainname

     

    From Domain try :

    camping ssname

     

     

    If camping does not work with UDP 4104 It is possible to configure CAM communication with TCP 4105. The port TCP 7163 should also be opened :

     

    On SS execute this :

    camconfig PATHS "domainname protocol=tcp port=4105"

     

    On DOMAIN execute this :

    camconfig PATHS "ssname protocol=tcp port=4105"

     

    and try again the camping commands.

     

     

     

    If communication is working fine with TCP 4105 then you could make it permanent by adding this line in file %CAI_MSQ%\cam.cfg on SS and DOMAIN :

     

    SS:

    *PATHS

    domainname protocol=tcp port=4105

     

     

    DOMAIN :

    *PATHS

    SSname protocol=tcp port=4105

     

     

    Remark : If file %CAI_MSQ%\cam.cfg does not exist you could generate it with this command :

    camsave explicit

     

     

    Thanks.

    Regards,

    Jean-Yves



  • 3.  Re: One of my Scalabilities fail the communication only with the domain

    Posted Jun 24, 2015 10:31 AM

    Hi Jean,

     

    I executed the camstat -n, please see the result:

     

             

    ApplicationprotostateportQlenm/sentm/recvretrydischold
    ----------------------------------------------------------------
    CAI002552-00000tcpCON4105125010060
    CAI005924-00034tcpCON4105012130060
    CAI001512-00075tcpCON41050010060
    CAI001512-00074tcpCON41050000060
    CAI005280-00000tcpCON4105018180060
    SD_SERVER_LWAtcpCON41050000060
    SD_SERVER_WRKRtcpCON41050110060
    SD_SERVER_MGRtcpCON41050000060
    SD_SERVER_CSVRtcpCON41050000060
    SD_SERVERtcpCON410501731440060
    SD_SERVER_IMtcpCON41050000060
    SD_SERVER_FTtcpCON41050100060
    SD_AG_REQUESTtcpCON41050000060
    CAI005924-00001tcpCON41050000060
    CAITRMAGENTtcpCON41050000060
    CFNOTIFYtcpCON41050000060
    CAI005924-00000tcpCON41050020060
    U-CFCERTEXtcpCON41050660060
    DTSDTA-NOTIFYtcpCON41050010060
    TNGDTA-PtcpCON41050000060
    TNGDTA-AtcpCON41050000060
    TNGDTA-TtcpCON41050000060
    DTSDTA-PtcpCON41050000060
    DTSDTA-AtcpCON41050000060
    DTSDTA-TtcpCON41050000060
    CAI003368-00000tcpCON41050000060
    RCMANAGERtcpCON41050990060
    RCSERVERtcpCON410502732820060
    CA_ITRM_METERtcpCON41050000060
    $U-CSMSERVERtcpCON410501330060
    U-CSMSERVERtcpCON410501671060060
    $U-CSMAGENTtcpCON41050360060
    U-CSMAGENTtcpCON41050000060
    U-NStcpCON41050000060
    U-NSCtcpCON41050000060
    U-SECTOR_SRVtcpCON41050237223720060
    CAITRM_CSERVERMtcpCON41050660060
    CA_ITRM_CSERVERtcpCON410504794790060
    U-CAFtcpCON41050000060
    U-SMtcpCON410502722720060
    CAIRTSALITEBtcpCON41050000060
    CAIRTSALITEtcpCON41050000060

     

    Hosts 111 - 0 cots (0 active), 111 udp, total queued 1, ave qlen 0.0

    Applications 42 (42 active), total queued 125, ave qlen 3.0

    Load average (m/s): send 15.77, 0.00, 16.63, receive 15.72, 0.00, 16.52

    Total messages: sent 8465, received 8408

    Supported Protocols: UDP, TCP

     

    CAM seems to be working with TCP port and not with UDP, because I executed the same command in other SS and within the results, there was UDP 4104 port lines.

     

    There's no communication between the servers, nor cam nor caf ping.

     

    Do you know another way to check why is it happening?

     

    Thanks alot for your help.

     

    Thanks in advance.

     

    Regards.



  • 4.  Re: One of my Scalabilities fail the communication only with the domain

    Broadcom Employee
    Posted Jun 24, 2015 11:04 AM

    Can you check the cam logs are there any:      reversed identity with proxy messages ?

     

    Do you have a cam.cfg file on that SS ?  What does it look like  ?     what is DM name ?

     

    Can you CAMPING or CAF PING from DM to SS ?



  • 5.  Re: One of my Scalabilities fail the communication only with the domain

    Broadcom Employee
    Posted Jun 25, 2015 03:04 AM

    Hi Oscar,

     


    In output of camstat -n command there are 2 parts : Host and Application.

    In your message we could see only the Application part.

    CAM queues for Application are always using TCP 4105.

     

    But in Host part (beginning of camstat -n output), we could see the port used for communication with remote machines.

    Please could you check which port (UDP 4104 ou TCP 4105) are used for communication with DOMAIN ?

     

    Thanks.

    Jean-Yves



  • 6.  Re: One of my Scalabilities fail the communication only with the domain

    Broadcom Employee
    Posted Jun 25, 2015 05:34 AM

    Hi Oscar

     

    You can also try the ITCM Network Diagnostic tool.

     

    This will check most aspects and help to determine the cause of the issue

     

    regards

    Rich



  • 7.  Re: One of my Scalabilities fail the communication only with the domain

    Broadcom Employee
    Posted Jun 29, 2015 06:57 AM

    HI Oscar

     

    Did you have any luck on this issue?

    regards

    Rich



  • 8.  Re: One of my Scalabilities fail the communication only with the domain

    Posted Jun 29, 2015 06:56 PM

    Hi Rich.

     

    We followed this tips:

     

    On SS execute this :

    camconfig PATHS "domainname protocol=tcp port=4105"

     

    On DOMAIN execute this :

    camconfig PATHS "ssname protocol=tcp port=4105"



    provieded by JY GUILBET and it's working by the moment.

     

    Thanks!



  • 9.  Re: One of my Scalabilities fail the communication only with the domain

    Posted Jun 29, 2015 06:57 PM

    We thought that, the port 4104 was blocked for these two servers.