Hi Tony ,
Please check my response tagged with [AVM]
On 11/20/2013 6:52 PM, Tony Hart wrote:
> The nid_tipc script reads and checks the CHASSIS_ID value but then does not
> use it when constructing the TIPC_NODEID. Is there a reason behind this ?
[AVM] CHASSIS_ID is used to construct Controller/payload
node_id(/var/lib/opensaf/node_id)
"printf "00%02x%02x%02x\n" $CHASSIS_ID $SLOT_ID $SUBSLOT_ID >
$pkglocalstatedir/node_id "
>
> A related question would be what is the status of TIPC versus TCP as the
> transport for OpenSAF, looking through some of the bug tickets seems to
> suggest that in future TCP would be the default transport ?
[AVM] Please check below user list mail with subject : [users] MDS over
TCP is the default transport in default staging branch (for upcoming 4.4)
================================================================================================================================
On 10/16/2013 3:18 PM, A V Mahesh wrote:
> Hi All,
>
> Please note that from change-set 4540 onwards TCP is the default
> transport in the default staging branch(for upcoming 4.4).
> Refer ticket #232 raised to improve usability by not having the overhead
> to build/download/install TIPC and as a kernel module.
>
> (A) The default behavior is that OpenSAF is built for TCP, i.e one just
> has to follow the usual steps as below :
>
> Build steps:
>
> Step 1 ./bootstrap.sh
> Step 2 ./configure (TIPC [default=no] )
> Step 3 make rpm or make install
>
> Configuration Steps to use TCP:
>
> Step 1 Update DTM_NODE_IP=<> with ip address of the local
> node in /etc/opensaf/dtm.conf
>
> (B) To build OpenSAF binaries with capability for both TCP and TIPC, use
> the --enable-tipc option as below:
>
> Build steps:
>
> Step 1 ./bootstrap.sh
> Step 2 ./configure --enable-tipc (TIPC [enable=yes] )
> Step 3 make rpm or make install
>
> Configuration Steps to use TIPC:
>
> Step 1 set MDS_TRANSPORT=TIPC in /etc/opensaf/nid.conf
> Step 2 Change TIPC_ETH_IF to your network interface name, e.g.
> eth3 in /etc/opensaf/nid.conf
> Step 3 Change TIPC_NET_ID to your TIPC net-id ,e.g 4711 in
> /etc/opensaf/nid.conf
>
>
> NOTE: Configuration of TIPC network id and interface name, have been
> moved from "/etc/opensaf/nodeinit.conf" to "/etc/opensaf/nid.conf"
> OpenSAF users that use SMF for middleware upgrades should update their
> upgrade scripts to backup theTIPC Network interface name
> TIPC net-id from "/etc/opensaf/nodeinit.conf" and restore them to
> "/etc/opensaf/nid.conf" .
>
> Please also check the `README` ,`INSTALL`, `00-README.conf` &
> `00-README.debug` for details.
>
>
> Thanks,
> AVM.
================================================================================================================================
_AVM
>
> thanks,
> --
> tony
>
>
> ------------------------------------------------------------------------------
> Shape the Mobile Experience: Free Subscription
> Software experts and developers: Be at the forefront of tech innovation.
> Intel(R) Software Adrenaline delivers strategic insight and game-changing
> conversations that shape the rapidly evolving mobile landscape. Sign up now.
> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
> _______________________________________________
> Opensaf-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensaf-users
------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
