00-README.conf | 81 +++++++++++++++++++++++++---------------- 00-README.debug | 75 ++++++++++++++++++++++++++++---------- INSTALL | 6 ++- README | 41 +++++++++----------- osaf/services/saf/immsv/README | 2 +- 5 files changed, 128 insertions(+), 77 deletions(-)
diff --git a/00-README.conf b/00-README.conf --- a/00-README.conf +++ b/00-README.conf @@ -27,17 +27,64 @@ 10) chgrp -R opensaf /var/log/opensaf Following is the brief description of each such configuration file. ******************************************************************************* +dtmd.conf + +This file contains MDS/TCP configuration parameters. +This file has to be edited only when you chose TCP as the mode of transport. + +The variable DTM_NODE_IP should be set to IP address of that local node + +******************************************************************************* nid.conf This file contains low level global configuration for OpenSAF. Normally this file does not have to be changed unless: -- TIPC is controlled outside OpenSAF: change OPENSAF_MANAGE_TIPC to "no" +- TIPC is selected as MDS transport: change MDS_TRANSPORT to "TIPC" -- TCP is selected as MDS transport: change MDS_TRANSPORT to "TCP" +- TIPC is selected as MDS transport : TIPC network interface name ( TIPC_ETH_IF ) default set to eth0. + This can be changed ,if user wish to configure other network interface name, e.g. eth3 + +- TIPC is selected as MDS transport : TIPC network Id ( TIPC_NET_ID ) is default set to 1234. + This can be changed ,if user wish to configure other network Id, e.g. 7878 + + This TIPC_NET_ID and TIPC_ETH_IF has to be edited only when you chose TIPC as the mode of transport. + + NOTE: The interface name and network id are avalible as `exported` Variable to the `configure_tipc` script + with default values. Please change this accordingly to reflect your correct interface(s) and network-id information. + + The interface name (TIPC_ETH_IF) and network id (TIPC_NET_ID) arguments to the configure_tipc.in + entry in nid.conf would get installed with default values. Please change this accordingly to + reflect your correct interface(s) and network-id information. + + Example 1, single interface: + TIPC_ETH_IF=eth0 + TIPC_NET_ID=1234 + + Example 2, dual interfaces: + TIPC_ETH_IF=eth0,eth1 + TIPC_NET_ID=4321 + + In the above line, eth0 and eth1 refers to the interface information and 1234 + refers to a sample tipc network id. Please change them accordingly. This + tipc-network id should be the same across all system controllers and payloads + in that OpenSAF cluster. The Ethernet interfaces is a comma separated list as + shown in the example 2 or just the name of a single interface as in + example 1. + + Please note that OpenSAF recommend users to run TIPC on two separate bearers + and let TIPC do the link aggregation. A bonded interface is not recommended. + + Also see http://tipc.sourceforge.net/doc/tipc_2.0_users_guide.html + + A bonded interface is not recommended. However OpenSAF does not currently + support managing two separate TIPC bearers. The missing support is logged in + ticket http://devel.opensaf.org/ticket/1948 + - OpenSAF should run as a different UNIX group and user than the default 'opensaf' -group/user. + group/user. + If OpenSAF was built with the flags "CFLAGS=-DRUNASROOT", then change OPENSAF_GROUP and OPENSAF_USER to root i.e. for old (<4.2) behaviour. @@ -66,34 +113,6 @@ opensaf services startup. <node_type> stands for 'controller' or 'payload' -The interface name and network id arguments to the nid_tipc entry -in nodeinit.conf.<node_type> would get installed with default values. Please change this -accordingly to reflect your correct interface(s) and network-id information. - -Example 1, single interface: -/usr/lib/opensaf/nid_tipc:TIPC:S:/usr/lib/opensaf/nid_tipc:4000::2:1:start eth0 1234:stop - -Example 2, dual interfaces: -/usr/lib/opensaf/nid_tipc:TIPC:S:/usr/lib/opensaf/nid_tipc:4000::2:1:start eth0,eth1 1234:stop - -In the above line, eth0 and eth1 refers to the interface information and 1234 -refers to a sample tipc network id. Please change them accordingly. This -tipc-network id should be the same across all system controllers and payloads -in that OpenSAF cluster. The Ethernet interfaces is a comma separated list as -shown in the example 2 or just the name of a single interface as in -example 1. - -Please note that OpenSAF recommend users to run TIPC on two separate bearers -and let TIPC do the link aggregation. A bonded interface is not recommended. - -Also see http://tipc.sourceforge.net/doc/tipc_2.0_users_guide.html - -Please note that OpenSAF recommend users to run TIPC on two separate bearers -and let TIPC do the link aggregation. -A bonded interface is not recommended. However OpenSAF does not currently -support managing two separate TIPC bearers. The missing support is logged in -ticket http://devel.opensaf.org/ticket/1948 - By default `make install' will install pre-configured for a controller node, i.e. the node_type file would contain the value 'controller'. On a payload node, the node_type must be a changed to 'payload' diff --git a/00-README.debug b/00-README.debug --- a/00-README.debug +++ b/00-README.debug @@ -4,31 +4,48 @@ Troubleshooting OpenSAF System Controller Checklist =========================== -1. Did TIPC installation fail? The following error "FATAL: Error inserting +1. If TIPC is chosen as the mds transport , did TIPC installation fail? + The following error "FATAL: Error inserting tipc (<kernel_modules_dir>/tipc.ko): Invalid module format" indicates that user had not compiled TIPC with proper kernel files. Compile TIPC with appropriate kernel header files (e.g. They are different for an smp kernel type, etc.) -2. Have you checked the TIPC configuration? The following TIPC configuration - parameters should be set appropriately in nodeinit.conf.controller: +2. If TIPC is chosen as the mds transport , have you checked the TIPC configuration? + The following TIPC configuration parameters should be set appropriately in nodeinit.conf: + + a. TIPC network_id should be the same as ACTIVE system controller's + network_id. + b. The interface information is set with default values. This has + to be set correctly to ensure connectivity between the system + controller and payload nodes. + Also, the TIPC zone_id and cluster_id values are currently hard-coded. + These have to be checked for correctness as below if zone_id and + cluster_id are changed: + c. zone_id should be the same as ACTIVE system controller's zone_id. + d. cluster_id should be the same as ACTIVE system controller's cluster_id. - a. TIPC network_id should be the same as ACTIVE system controller's - network_id. - b. The interface information is set with default values. This has - to be set correctly to ensure connectivity between the system - controller and payload nodes. - Also, the TIPC zone_id and cluster_id values are currently hard-coded. - These have to be checked for correctness as below if zone_id and - cluster_id are changed: - c. zone_id should be the same as ACTIVE system controller's zone_id. - d. cluster_id should be the same as ACTIVE system controller's cluster_id. +3. If TCP is chosen as the mds transport with IPv6, have you checked the system configuration? + + a. The kernel should be ipv6 compiled. + The following commands should succeed : + - ls /proc/net/if_inet6 + - modprobe ipv6 + - lsmod |grep -w 'ipv6' && echo "IPv6 module successfully loaded" + b. For communication between ipv6 m/c's, firewall should be disabled. + c. If there is any router in between the m/c's, the router should be ipv6 enabled. + d. kernel should assign ipv6 link-local ip address automatically for the interface available. -3. Have you checked the slot_id? +4. If TCP is chosen as the mds transport , have you checked the TCP configuration? + The following TCP configuration parameters should be set appropriately in dtmd.conf: + + a. DTM_NODE_IP should be configured same as system IP address. + +5. Have you checked the slot_id? The slot_id should be unique and different from any other node. The system controllers. -4. Have you checked the open source packages installation? +6. Have you checked the open source packages installation? Ensure that the following open source packages are installed (make install or the rpm packages are installed): @@ -39,10 +56,10 @@ 4. Have you checked the open source pac available. In cases of rpm installation, make sure the devel package is installed. -5. Have you checked the chassis_id? The chassis_id should be the same as +7. Have you checked the chassis_id? The chassis_id should be the same as ACTIVE system controller. -6. Have you checked the node_name. It should contain the same name as the +8. Have you checked the node_name. It should contain the same name as the value specified in the nodes.cfg file while generating the imm.xml. "Unconfigured CLM nodes are not allowed to join the cluster if the node_names dont match and CLMNA will not allowed to be initialized". @@ -52,13 +69,13 @@ NOTE: Also check for /var/log/messages f Payload Node Checklist ====================== -1. Did TIPC installation fail? The following error "FATAL: Error inserting +1. If TIPC is chosen as the mds transport ,did TIPC installation fail? The following error "FATAL: Error inserting tipc (<kernel_modules_dir>/tipc.ko): Invalid module format" indicates that user had not compiled TIPC with proper kernel files. Compile TIPC with appropriate kernel header files (e.g. They are different for an smp kernel type, etc.) -2. Have you checked the TIPC configuration? +2. If TIPC is chosen as the mds transport , have you checked the TIPC configuration? The following TIPC configuration parameters should be set appropriately in nodeinit.conf.payload: @@ -72,10 +89,26 @@ 2. Have you checked the TIPC configurat c. zone_id should be the same as the system controllers's zone_id. d. cluster_id should be the same as the system controllers's cluster_id. -3. Have you checked the chassis_id? The chassis_id should be the same as +3. If TCP is chosen as the mds transport with IPv6, have you checked the system configuration? + + a. The kernel should be ipv6 compiled. + The following commands should succeed : + - ls /proc/net/if_inet6 + - modprobe ipv6 + - lsmod |grep -w 'ipv6' && echo "IPv6 module successfully loaded" + b. For communication between ipv6 m/c's, firewall should be disabled. + c. If there is any router in between the m/c's, the router should be ipv6 enabled. + d. kernel should assign ipv6 link-local ip address automatically for the interface available. + +4. If TCP is chosen as the mds transport , have you checked the TCP configuration? + The following TCP configuration parameters should be set appropriately in dtmd.conf: + + a. DTM_NODE_IP should be configured same as system IP address. + +5. Have you checked the chassis_id? The chassis_id should be the same as ACTIVE & STANDBY system controllers. -4. Have you checked the node_name. It should contain the same name as the +6. Have you checked the node_name. It should contain the same name as the value specified in the nodes.cfg file while generating the imm.xml. "Unconfigured CLM nodes are not allowed to join the cluster if the node_names dont match and CLMNA will not allowed to be initialized". diff --git a/INSTALL b/INSTALL --- a/INSTALL +++ b/INSTALL @@ -45,7 +45,11 @@ of `autoconf'. The simplest way to compile this package is: 1. `cd' to the directory containing the package's source code and type - `./configure' to configure the package for your system. + `./configure' to configure the package MDS/TCP as messaging protocol + for your syste. + + `./configure --enable-tipc' to configure the package both MDS/TCP + and/or MDS/TIPC as messaging protocols for your system . Running `configure' might take a while. While running, it prints some messages telling which features it is checking for. diff --git a/README b/README --- a/README +++ b/README @@ -252,10 +252,6 @@ Prerequisites The following software is required to build OpenSAF: - * The Linux Kernel with TIPC development support (This is not required when the opensaf is - build with option --disable-tipc). OpenSAF works with TIPC version 1.5 onwards. But it - is strongly adviced to use TIPC 1.6.2 and above, to get the TIPC service unsubscribe - feature(Cancellation to a Subscription). * libxml2-dev (Development files for the GNOME XML library) * automake * m4 @@ -266,6 +262,11 @@ The following software is required to bu * GNU make * python-dev(el) * Optionally: + * The Linux Kernel with TIPC development support. This is required when opensaf is + built with the option --enable-tipc. OpenSAF works with TIPC version 1.5 onwards. But it + is strongly adviced to use TIPC 1.6.2 and above to get the TIPC service unsubscribe + feature(Cancellation to a Subscription). + * When PLM is enabled, an HPI implementation (e.g. OpenHPI) * When IMM PBE feature is enabled, sqlite3 @@ -283,7 +284,8 @@ Building `OpenSAF' Some features needs to be configured at build time but don't have configure support, these are explained here. -1) Configure a non flat MDS addressing scheme (optional) +1) Configure a non flat MDS addressing scheme (optional) when TIPC is chosen +as the transport In the default (from 4.3) addressing scheme, TIPC node addresses looks like 1.1.1, 1.1.2 etc. @@ -329,6 +331,8 @@ steps before trying to `configure' (i.e. OR % ./configure && make rpm +By default, OpenSAF is built with TCP as the transport. + By default, all 'OpenSAF' services are enabled to be built and `OpenSAF' will assume the following `configure' options by default: @@ -346,15 +350,13 @@ are available w.r.t enabling/disabling t --enable-python enable the Python AIS bindings [default=yes] --enable-java enable the Java AIS interface mapping [default=no] --enable-am4j enable the AM4J agent [default=no] - --disable-tipc disable building the TIPC [default=no] + --enable-tipc enable building the TIPC [default=no] --enable-tests enable building the OpenSAF testing programs [default=no] --enable-imm-pbe enable the IMM Persistent Backend Interface [default=yes] --enable-ntf-imcn enable the NTF Information Model Notification producer [default=no] - --disable-tipc disable building the TIPC as the transport for MDS - [default=no] --disable-ais-ckpt disable building the SAI-AIS-CKPT service [default=no] --disable-ais-evt disable building the SAI-AIS-EVT service @@ -428,6 +430,12 @@ the user thinks he's not using a specifi dependency and the user still needs to tell the build system to be using the proper CPPFLAGS/CFLAGS/CXXFLAGS where to find a dummy <SaHpi.h> +By using `./configure --enable-tipc', you are building OpenSAF to support TIPC +also as the transport. Upon enabling this option, the OpenSAF binaries +support both TIPC and TCP as the transport and to use TIPC, you have to +change the variable MDS_TRANSPORT to TIPC in the +nid.conf file (see nid.conf in 00-README.conf). + By using `./configure --enable-java', you are enabling the Java AIS mapping support in the build system. Specials M4 macros will be used to autodetect what `JDK' and `Ant' program you are using. By default this options is @@ -453,19 +461,6 @@ By using `./configure --disable-rpm-targ target, some build systems provide their own `make rpm` rule, it would then be clashing with the OpenSAF rule. -By using `./configure --disable-tipc', you are building the MDS with the TCP as -the only transport of the OpenSAF(MDS transports supported are TCP and TIPC). - -If user wants to use TCP as the transport of MDS, build the opensaf with `--disable-tipc` option, -and update the variable DTM_NODE_IP to self node IP address in the `/etc/opensaf/dtmd.conf` -before starting the opensaf. - -If opensaf is built with default option, MDS is built to support both TIPC and TCP, -with TIPC selected as default transport. -If user wants to use TCP as the transport with default built image, user needs -to change the variables MDS_TRANSPORT to TCP in the `/etc/opensaf/nid.conf` file -and update the variable DTM_NODE_IP to self node IP address in the `/etc/opensaf/dtmd.conf`. - Building `OpenSAF' RPMs ======================= @@ -662,7 +657,7 @@ The `OpenSAF' SysV init script is instal Commands to Start OpenSAF When PLM is disabled: =============================================== After a minimum configuration of - - slot_id, nodeinit.conf.controller, node_name, imm.xml(Generated) and nid_tipc(if needbe), for the controller + - slot_id, nodeinit.conf.controller, node_name, imm.xml(Generated) and configure_tipc(if needbe), for the controller (OR) - slot_id, nodeinit.conf.payload and node_name, for the payload. @@ -674,7 +669,7 @@ Commands to Start OpenSAF When PLM is en ============================================== After a minimum configuration of - - slot_id, nodeinit.conf.controller, node_name, imm.xml(Generated) and nid_tipc(if needbe) and the plmcd.conf, + - slot_id, nodeinit.conf.controller, node_name, imm.xml(Generated) and configure_tipc(if needbe) and the plmcd.conf, for the controller (OR) - slot_id, nodeinit.conf.payload, node_name and the plmcd.conf, for the payload diff --git a/osaf/services/saf/immsv/README b/osaf/services/saf/immsv/README --- a/osaf/services/saf/immsv/README +++ b/osaf/services/saf/immsv/README @@ -48,7 +48,7 @@ AMF. A crash of any director process, su restart of the active controller, which of course implies a fail-over of the directors for all services. -The active IMMD tracks the cluster membership (using MDS/tipc) and controls +The active IMMD tracks the cluster membership (using MDS) and controls which nodes/IMMNDs currently can provide access to the IMM service. Note: the current implementation of IMM does not use the SAF CLM service. That service is only at the node level. The cluster that is tracked by the IMMD ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
