Hi Nivrutti, That’s a typo. I was trying not to use our real SG names and keep it generic. I meant to replace all references to ‘DVN’ with ‘SG-A’.
Thanks, David From: Nivrutti Kale [mailto:nk...@brocade.com] Sent: Monday, October 17, 2016 2:38 PM To: David Hoyt <david.h...@genband.com>; opensaf-users@lists.sourceforge.net Subject: RE: both SUs within a 2N Service Group appear as STANDBY ________________________________ NOTICE: This email was received from an EXTERNAL sender ________________________________ Hi David, safApp name in two command is not consistent. Are you sure you looking at right output? In the later one safApp name is "safApp=DVN". Correct State: safSISU=safSu=SU1\,safSg=SG-A\,safApp=SG-A,safSi=SG-A,safApp=SG-A Wrong State: safSISU=safSu=SU2\,safSg=SG-A\,safApp=DVN,safSi=SG-A,safApp=SG-A Thanks, Nivrutti -----Original Message----- From: David Hoyt [mailto:david.h...@genband.com] Sent: Monday, October 17, 2016 11:46 PM To: opensaf-users@lists.sourceforge.net<mailto:opensaf-users@lists.sourceforge.net> Subject: [users] both SUs within a 2N Service Group appear as STANDBY Hi all, I'm encountering a scenario where opensaf shows the HA state of both SUs within a 2N redundancy Service Group as standby. Setup: - Opensaf 4.6 running on RHEL 6.6 VMs with TCP - 2 controllers, 4 payloads - SC-1 & SC-2 are the VMs with the controller nodes (SC-1 is active) - PL-3 & PL4 have SU1 & SU2 from SG-A (2N redundancy) - PL-5 & PL-6 have SU1 & SU2 from SG-B (2N redundancy) - Server-1 has three VMs consisting of SC-1, PL-3 and PL-5 - Likewise, server-2 has SC-2, PL-4 and PL-6 I reboot server 1 and shortly afterwards, the SG-A SUs begin to failover. SU2 on PL-4 goes active. Around the same time, the opensaf 2N SUs failover. After the dust has settled, and server-1 comes back as well as the VMs, all appears fine except the SG-A SUs. They both have a standby HA state. Is there any way to correct this? Is there some audit that periodically checks the validity of the HA states? Now, when SG-A, SU1 recovers, I did swact the SUs and it corrected the HA state. However, if server-1 goes down for an extended period, the HA state of SG-A, SU2 will appear as Standby, when it's actually running as active. Before the reboot: [root@sc-2 ~]# amf-state siass | grep -A 2 OpenSAF | grep -A 1 safSg=2N safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) -- safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=STANDBY(2) [root@jenga-56-sysvm-1 ~]# [root@sc-2 ~]# amf-state siass | grep -A 1 SG-A safSISU=safSu=SU2\,safSg=SG-A\,safApp=SG-A,safSi=SG-A,safApp=SG-A saAmfSISUHAState=STANDBY(2) -- safSISU=safSu=SU1\,safSg=SG-A\,safApp=SG-A,safSi=SG-A,safApp=SG-A saAmfSISUHAState=ACTIVE(1) [root@sc-2 ~]# [root@sc-2 ~]# amf-state siass | grep -A 1 SG-B safSISU=safSu=SU2\,safSg=SG-B\,safApp=SG-B,safSi=SG-B,safApp=SG-B saAmfSISUHAState=STANDBY(2) -- safSISU=safSu=SU1\,safSg=SG-B\,safApp=SG-B,safSi=SG-B,safApp=SG-B saAmfSISUHAState=ACTIVE(1) [root@sc-2 ~]# After the reboot: [root@sc-2 ~]# amf-state siass | grep -A 2 OpenSAF | grep -A 1 safSg=2N safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=STANDBY(2) -- safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) [root@sc-2 ~]# [root@sc-2 ~]# amf-state siass | grep -A 1 SG-A safSISU=safSu=SU1\,safSg=SG-A\,safApp=SG-A,safSi=SG-A,safApp=SG-A saAmfSISUHAState=STANDBY(2) -- safSISU=safSu=SU2\,safSg=SG-A\,safApp=DVN,safSi=SG-A,safApp=SG-A saAmfSISUHAState=STANDBY(2) [root@sc-2 ~]# [root@sc-2 ~]# amf-state siass | grep -A 1 SG-B safSISU=safSu=SU2\,safSg=SG-B\,safApp=SG-B,safSi=SG-B,safApp=SG-B saAmfSISUHAState=ACTIVE(1) -- safSISU=safSu=SU1\,safSg=SG-B\,safApp=SG-B,safSi=SG-B,safApp=SG-B saAmfSISUHAState=STANDBY(2) [root@sc-2 ~]# ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DQICAg&c=IL_XqQWOjubgfqINi2jTzg&r=8oj2Tn7_JuMy90N67rXExkWsx29-JTWbXUkT3IIi99w&m=BaG3BbO8jb9Kb25-YUeviPLDBOneLUA9eCdRL_aGGCY&s=w8V8KD0t_dVvVP5_XfZyk-p6mEg5GVrYRPepDNhx6NA&e= _______________________________________________ Opensaf-users mailing list Opensaf-users@lists.sourceforge.net<mailto:Opensaf-users@lists.sourceforge.net> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_opensaf-2Dusers&d=DQICAg&c=IL_XqQWOjubgfqINi2jTzg&r=8oj2Tn7_JuMy90N67rXExkWsx29-JTWbXUkT3IIi99w&m=BaG3BbO8jb9Kb25-YUeviPLDBOneLUA9eCdRL_aGGCY&s=gnAd8SOolRZjOJpW5NKwOr8soOHd7vXnsrQWa5xpSWk&e= ------------------------------------------------------------------------------ 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 Opensaf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-users
