It looks like the node with TIPC address 1.1.10 is a system controller.
Is this expected? Please check that you have configured at most two
nodes as system controllers (i.e. check the IMM configuration as well as
the file /etc/opensaf/node_type). I don't remember in what version we
implemented support for more than two system controllers, but I don't
think it in such an old version of OpenSAF.
regards,
Anders Widell
On 11/23/2017 09:12 AM, Ashish Kumar34 wrote:
Hi All,
I am new to opensaf . I am using opensaf 4.6.2 On windRiver 4.3.
I am facing difficulties to start opensaf on Standby controller.
Getting the below logs at /var/log/messages.
Nov 22 17:14:00 localhost opensafd: Starting OpenSAF Services (Using TIPC)
Nov 22 17:14:00 localhost kernel: TIPC: Activated (version 1.7.7 compiled Sep
2 2016 22:58:00)
Nov 22 17:14:00 localhost kernel: NET: Registered protocol family 30
Nov 22 17:14:00 localhost kernel: TIPC: Started in single node mode
Nov 22 17:14:00 localhost kernel: TIPC: Started in single node mode
Nov 22 17:14:00 localhost kernel: TIPC: Started in network mode
Nov 22 17:14:00 localhost kernel: TIPC: Own node address <1.1.1>, network
identity 1244
Nov 22 17:14:00 localhost kernel: TIPC: Enabled bearer <eth:base>, discovery domain
<1.1.0>, priority 10
Nov 22 17:14:00 localhost kernel: TIPC: Established link
<1.1.1:base-1.1.2:base> on network plane A
Nov 22 17:14:00 localhost kernel: TIPC: Established link
<1.1.1:base-1.1.10:base> on network plane A
Nov 22 17:14:00 localhost kernel: TIPC: Established link
<1.1.1:base-1.1.5:base> on network plane A
Nov 22 17:14:00 localhost kernel: TIPC: Established link
<1.1.1:base-1.1.5:base> on network plane A
Nov 22 17:14:00 localhost osafrded[4966]: Started
Nov 22 17:14:00 localhost /etc/wrs-lsb/lsb_start_daemon: osafrded startup - OK
Nov 22 17:14:00 localhost osafrded[4966]: NO Peer rde@a0a0f has standby state
=> possible fail over, waiting...
Nov 22 17:14:00 localhost /etc/wrs-lsb/lsb_log_message: - OK
Nov 22 17:14:01 localhost osafrded[4966]: NO Peer rde@a0a0f has standby state
=> possible fail over, waiting...
Nov 22 17:14:02 localhost osafrded[4966]: NO Peer rde@a0a0f has standby state
=> possible fail over, waiting...
Nov 22 17:14:03 localhost osafrded[4966]: NO Peer rde@a0a0f has standby state
=> possible fail over, waiting...
Nov 22 17:14:04 localhost osafrded[4966]: NO Peer rde@a0a0f has standby state
=> possible fail over, waiting...
Nov 22 17:14:05 localhost osafrded[4966]: NO Peer rde@a0a0f has standby state
=> possible fail over, waiting...
Nov 22 17:14:06 localhost osafrded[4966]: NO Peer rde@a0a0f has standby state
=> possible fail over, waiting...
Nov 22 17:14:07 localhost osafrded[4966]: NO Peer rde@a0a0f has standby state
=> possible fail over, waiting...
Nov 22 17:14:08 localhost osafrded[4966]: NO Peer rde@a0a0f has standby state
=> possible fail over, waiting...
Nov 22 17:14:09 localhost osafrded[4966]: NO Peer rde@a0a0f has standby state
=> possible fail over, waiting...
Nov 22 17:14:10 localhost osafrded[4966]: NO Peer rde@a0a0f has standby state
=> possible fail over, waiting...
Nov 22 17:14:11 localhost osafrded[4966]: NO Peer rde@a0a0f has standby state
=> possible fail over, waiting...
However opensaf working fine in Active Controller.
Below is the opensafd status output from Active controller :
atcafs-n10s2:~# /etc/init.d/opensafd status
safSISU=safSu=n10s2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=n10s5\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed10,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU-n10s5\,safSg=HenbGw-SG\,safApp=HenbGwApp_PL_n10s5,safSi=HenbGw,safApp=HenbGwApp_PL_n10s5
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=n10s10\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU-n10s10\,safSg=HenbGw-SG\,safApp=HenbGwApp_PL_n10s10,safSi=HenbGw,safApp=HenbGwApp_PL_n10s10
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU-n10s2\,safSg=HenbGw-SG\,safApp=HenbGwApp,safSi=HenbGw,safApp=HenbGwApp
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=n10s2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
atcafs-n10s2:~#
Please help. I am struggling to fix the problem.
Thanks in advance.
Regards,
Ashish
============================================================================================================================
Disclaimer: This message and the information contained herein is proprietary and
confidential and subject to the Tech Mahindra policy statement, you may review the policy
at http://www.techmahindra.com/Disclaimer.html
<http://www.techmahindra.com/Disclaimer.html> externally
http://tim.techmahindra.com/tim/disclaimer.html
<http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra.
============================================================================================================================
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
