(→UDP without Auto IP address assignment) |
|||
Line 76: | Line 76: | ||
ASP_UDP_USE_EXISTING_IP=true | ASP_UDP_USE_EXISTING_IP=true | ||
ASP_UDP_LINK_NAME=<link name, for example 'eth0'> | ASP_UDP_LINK_NAME=<link name, for example 'eth0'> | ||
+ | |||
+ | '''clTransport.xml''' should add static IP addresses for cluster: | ||
+ | |||
+ | <peerAddresses port="6789"> | ||
+ | <peer addr="192.168.56.101" slot="1"/> | ||
+ | <peer addr="192.168.56.102" slot="2"/> | ||
+ | </peerAddresses> | ||
+ | |||
== UDP without Node Discovery (Multicast) == | == UDP without Node Discovery (Multicast) == | ||
Line 96: | Line 104: | ||
<retries>4</retries> | <retries>4</retries> | ||
</heartbeat> | </heartbeat> | ||
− | < | + | <peerAddresses port="6789"> |
− | + | <peer addr="192.168.56.101" slot="1"/> | |
− | + | <peer addr="192.168.56.102" slot="2"/> | |
− | </ | + | </peerAddresses> |
</multixport> | </multixport> | ||
</version> | </version> |
Revision as of 09:54, 23 May 2013
Contents |
From Model
Step 1
- Using IDE open your model, upgrade your model, a xport configure file clTransport.xml will be generated in <your model>/config/clTransport.xml
<?xml version="1.0" encoding="UTF-8"?> <openClovisAsp> <version v0="4.0.0"> <multixport xmlns="multixport.ecore"> <config> <default>TIPC</default> </config> <xports> <xport> <type>TIPC</type> <plugin>libClTIPC.so</plugin> </xport> </xports> </multixport> </version> </openClovisAsp>
Step 2
Edit content clTransport.xml with UDP default:
<?xml version="1.0" encoding="UTF-8"?> <openClovisAsp> <version v0="4.0.0"> <multixport xmlns="multixport.ecore"> <xports> <xport> <type>UDP</type> <plugin>libClUDP.so</plugin> </xport> </xports> <multicast address="226.0.1.1" port="9595" /> <heartbeat> <interval>3000</interval> <intervalLocal>3000</intervalLocal> <retries>5</retries> </heartbeat> </multixport> </version> <openClovisAsp>
UDP use multicast to notification component arrival and departure.
Step 3
Add 2 env variables into <model_dir>/src/target.env:
export ASP_UDP_SUBNET=<IP Range>/Length export ASP_UDP_LINK_NAME=<your interface>
- Example:
export ASP_UDP_SUBNET=192.168.57.0/24 export ASP_UDP_LINK_NAME=eth0
Step 4
Before running ASP, should export/setenv 2 below variables:
export ASP_UDP_SUBNET=192.168.57.0/24 export ASP_UDP_LINK_NAME=eth0
UDP without Auto IP address assignment
To use the UDP transport with the IP address, 'already configured' on a link, set these variables in your environment before starting SAFplus:
ASP_UDP_USE_EXISTING_IP=true ASP_UDP_LINK_NAME=<link name, for example 'eth0'>
clTransport.xml should add static IP addresses for cluster:
<peerAddresses port="6789"> <peer addr="192.168.56.101" slot="1"/> <peer addr="192.168.56.102" slot="2"/> </peerAddresses>
UDP without Node Discovery (Multicast)
To use the UDP transport without node discovery, you must explicitly configure the static addresses and define variable environments ASP_UDP_USE_EXISTING_IP=true and ASP_UDP_LINK_NAME for getting ip addresses below.
<?xml version="1.0" encoding="UTF-8"?> <openClovisAsp> <version v0="4.0.0"> <multixport xmlns="multixport.ecore"> <xports> <xport> <type>UDP</type> <plugin>libClUDP.so</plugin> </xport> </xports> <heartbeat> <interval>1000</interval> <intervalLocal>1000</intervalLocal> <retries>4</retries> </heartbeat> <peerAddresses port="6789"> <peer addr="192.168.56.101" slot="1"/> <peer addr="192.168.56.102" slot="2"/> </peerAddresses> </multixport> </version> </openClovisAsp>
From Image
Create a clTransport.xml like step 2 & 3 above and retarball your images.
Q&A
- Q: Is the SAFplus able to run as a user other than root?
- A: Only pre-requisites, configure interface name (ASP_UDP_LINK_NAME) with IP address (ASP_UDP_SUBNET.DEFAULT_NODEADDR) (Use DEFAULT_NODEADDR settings from asp.conf file)
Example: root:#ifconfig eth0 192.168.57.1 user:#export ASP_UDP_SUBNET=192.168.57.0/24 user:#export ASP_UDP_LINK_NAME=eth0 user:#./etc/init.d/safplus start