Smarts IP / SAM: Runnng Brcontrol From 8.1.4 Installation Against a 9.1.or Newer Broker generates Error Messages
Article ID: 332219
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
Customers trying to attach 8.1.4.x domains to a Smarts 9.1 or newer broker will need to follow the resolution below to run brcontrol commands from the 8.1.4.x installation successfully. This is also needed to allow the 8.1.4 domains to attach to the 9.1.x or newer broker.
Customers with 8.1.4 Smarts installations trying run a brcontrol command from the 8.1.4.x installation to a 9.1 or newer broker may find the following error message embedded in the error response.
Two examples of errors you may see in the logs are below
1: SYS_MSG-*-LOGOUT-Logout by BrokerNonsecure from [email protected]:59944 session 45921
2: After reading "CI_FlowTCP_U" bytes of "0" maximum <SYS>-ECONNRESET-Connection reset by peer
An example of the error message presented in by using the brcontrol command from an 8.1.4 installation on a SAM 9.3.0.10 broker.
brcontrol -b host:426
[April 22, 2015 1:17:35 PM GMT+00:00 +363ms] t@4265280368 <Primary Thread>
CI-E-EWHILE-While executing function "fillRead"
CI-EFLOWID-For flow CI_FlowBufferedHead_U [Remote API connection] HEAD|BUFFERED @0x000000000b2e8280
. Read buffer, 0 bytes available of 2145
. ?3?0000000000000000 0000000000000000 <^|0000000000000000 0000000000000000
. Write buffer, 0 bytes written of 2048
. ?3?[^504F5354202F496E 4368617267652F56 312E302F646D736F 636B65742F646F6D
. ->CI_FlowTCP_U [Remote API connection] IN_FLOW|PHYSICAL @0x000000000b2d88c0
. gtinms36:426 KS N/A, KR N/A
. Open fd=11, conn April 22, 2015 1:17:35 PM GMT+00:00, disc April 22, 2015 1:17:35 PM GMT+00:00,
. 204.27.36.143:52348 -> 204.27.36.149:426, tmo 0 00:05:00 N/S 1/0
CI-EWHILEREAD-After reading "CI_FlowTCP_U" bytes of "0" maximum
<SYS>-ECONNRESET-Connection reset by peer; in file "/work/tancurrent/DMT-9.0.4.0/11/smarts/clsapi/ci_flow.c" at line 2608
[April 22, 2015 1:17:35 PM GMT+00:00 +365ms] t@4265280368 <Primary Thread>
SM-E-EIO-Fatal I/O error; in file "/work/tancurrent/DMT-9.0.4.0/11/smarts/skclient/client/sm_redom.c" at line 1247
Error attaching to broker: host:426!
Customers trying to attach 8.1.4.x domains to a Smarts 9.1 or newer broker will need to follow the resolution below to run brcontrol commands from the 8.1.4.x installation successfully. This is also needed to allow the 8.1.4 domains to attach to the 9.1.x or newer broker.
Customers with 8.1.4 Smarts installations trying run a brcontrol command from the 8.1.4.x installation to a 9.1 or newer broker may find the following error message embedded in the error response.
Two examples of errors you may see in the logs are below
1: SYS_MSG-*-LOGOUT-Logout by BrokerNonsecure from [email protected]:59944 session 45921
2: After reading "CI_FlowTCP_U" bytes of "0" maximum <SYS>-ECONNRESET-Connection reset by peer
An example of the error message presented in by using the brcontrol command from an 8.1.4 installation on a SAM 9.3.0.10 broker.
brcontrol -b host:426
[April 22, 2015 1:17:35 PM GMT+00:00 +363ms] t@4265280368 <Primary Thread>
CI-E-EWHILE-While executing function "fillRead"
CI-EFLOWID-For flow CI_FlowBufferedHead_U [Remote API connection] HEAD|BUFFERED @0x000000000b2e8280
. Read buffer, 0 bytes available of 2145
. ?3?0000000000000000 0000000000000000 <^|0000000000000000 0000000000000000
. Write buffer, 0 bytes written of 2048
. ?3?[^504F5354202F496E 4368617267652F56 312E302F646D736F 636B65742F646F6D
. ->CI_FlowTCP_U [Remote API connection] IN_FLOW|PHYSICAL @0x000000000b2d88c0
. gtinms36:426 KS N/A, KR N/A
. Open fd=11, conn April 22, 2015 1:17:35 PM GMT+00:00, disc April 22, 2015 1:17:35 PM GMT+00:00,
. 204.27.36.143:52348 -> 204.27.36.149:426, tmo 0 00:05:00 N/S 1/0
CI-EWHILEREAD-After reading "CI_FlowTCP_U" bytes of "0" maximum
<SYS>-ECONNRESET-Connection reset by peer; in file "/work/tancurrent/DMT-9.0.4.0/11/smarts/clsapi/ci_flow.c" at line 2608
[April 22, 2015 1:17:35 PM GMT+00:00 +365ms] t@4265280368 <Primary Thread>
SM-E-EIO-Fatal I/O error; in file "/work/tancurrent/DMT-9.0.4.0/11/smarts/skclient/client/sm_redom.c" at line 1247
Error attaching to broker: host:426!
Environment
VMware Smart Assurance - SMARTS
Cause
Smarts 8.1.4 and earlier versions use the Smarts keepalive process for broker communication and this is no longer used in 9.1.x and newer versions.
Resolution
In the 9.1.X or newer broker you will need to add the following parameter to the local/conf runcmd_env.sh in the Installation folder that the 9.1.x or newer broker is running.
1. Find the runcmd_env.sh in the local\conf folder that the broker brstart command is using in the 9.1.x or newer installation of Smarts.
2 Add the following line to the runcmd_env.sh SM_NO_TLS=TRUE
3. Restart the broker.
4. To have the 8.1.4.x domains connect to the newer 9.1.x broker you can restart the 8.1.4.x domains or follow the instructions in KB article
https://support.emc.com/kb/167325
For additional information with regard to ACM 2.4 and Smarts SAM version 9.3.0.10 and 9.4.x connection to SAM and OI domains,and security protocols, the connectivity issue may be resolved by including the
1. Find the runcmd_env.sh in the local\conf folder that the broker brstart command is using in the 9.1.x or newer installation of Smarts.
2 Add the following line to the runcmd_env.sh SM_NO_TLS=TRUE
3. Restart the broker.
4. To have the 8.1.4.x domains connect to the newer 9.1.x broker you can restart the 8.1.4.x domains or follow the instructions in KB article
https://support.emc.com/kb/167325
For additional information with regard to ACM 2.4 and Smarts SAM version 9.3.0.10 and 9.4.x connection to SAM and OI domains,and security protocols, the connectivity issue may be resolved by including the
SM_ALLOW_LEGACY_CRYPTO=TRUE in the runcmd_env.sh file instead of disabling TLS in step 2 above.
https://support.emc.com/kb209284Feedback
Yes
No
Powered by
