Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[SBR] The cluster node is attempting to connect to the cluster via the wrong IP address



Article ID: KB26921 KB Last Updated: 08 Mar 2017Version: 3.0
This article describes the issue of the cluster node attempting to connect to the cluster via the wrong IP address.
SBR faiis to start, with the following error message being generated, when SBR is started via the SSR cluster; which is configured with an IPMP Virtual IP address:
Configuration error: Error : Could not alloc node id at port 5235: Connection with id 101 done from wrong host ip, expected
In certain cases, the IPMP configuration will use the source IP of the interface, rather than the IPMP Virtual IP, when making an outgoing request. This will cause the NDB management node to reject the node connection to the cluster, when the IPMP address is used to configure the nodes.
You can configure the bind-address parameter in the connect string for all the nodes that face this issue.

For SBR nodes, add the bind-address parameter in the <RADIUS_DIRECTORY>dbclusterndb.gen file:
ManagementNode = bind-address=<IPMP_VIP>,<Management_node1>:5235,<Management_node2>:5235;nodeid=<ID>
After making the change to the dbclusterndb.gen file, restart Radius to activate the changes.

For the Management, MySQL, and Data nodes, edit the <hadm>/my.cnf file as follows:
ndb-connectstring = bind-address=<IPMP_VIP>,<Management_node_IP>:5235

ndb-connectstring = bind-address=<IPMP_VIP>,<Management_node1>:5235,<Management_node2>:5235;nodeid=<ID>

# The following #sbrd comments are actually live configuration for sbrd
# If ndbd is not run as root, then the hadm user must be granted PRIV_PROC_LOCK_MEMORY
sbrd-ndb-connectstring = bind-address=<IPMP_VIP>,<Management_node1>:5235,<Management_node2>:5235;nodeid=<ID>
After editing the my.cnf file, perform a rolling restart of the cluster to activate the changes.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search