- **status**: unassigned --> invalid
- **assigned_to**: Praveen
- **Milestone**: future --> never
- **Comment**:
This configuration is not complete. Association objects are missing for comp2
in SU1 so second csi is not assigned to any component. In SU2 such objects are
totally missing for all the components.
At the same time user has configured 5 SIs. In NPI model only one SI can be
assigned
to one SU.
The raised problem of SG becoming unstable even for such an invalid
configuration is fixed in the below change set. Now AMF is giving enough
warnings in syslog for missing elements. Attached are the logs after successful
validation.
changeset: 5196:c01c6de0bd55
parent: 5193:a23b1c8d0e6c
user: [email protected]
date: Tue Apr 29 11:16:14 2014 +0530
summary: amfd: assign only one csi per component for NPI SU [#856]
changeset: 5195:31544cda639c
branch: opensaf-4.4.x
parent: 5188:87e81f29ed22
user: [email protected]
date: Tue Apr 29 11:15:16 2014 +0530
summary: amfd: assign only one csi per component for NPI SU [#856]
changeset: 5194:f558f34b548e
branch: opensaf-4.3.x
parent: 5185:b7c820c3307f
user: [email protected]
date: Tue Apr 29 11:13:33 2014 +0530
summary: amfd: assign only one csi per component for NPI SU [#856]
---
** [tickets:#411] Unlock-in of 2nd SU leave SG in unstable state containing all
NPI components.**
**Status:** invalid
**Milestone:** never
**Created:** Fri May 31, 2013 05:57 AM UTC by Nagendra Kumar
**Last Updated:** Fri Oct 04, 2013 08:54 AM UTC
**Owner:** Praveen
Migrated from http://devel.opensaf.org/ticket/2734
Changeset : 3586
Configuration : A SG,5SUs with 2Comps each of type NPI(category 8).
5SIs with 2CSIs each.
Scenario:
--------------------------------------------------------------------------------
Unlock-in/unlock of 1st SU is enabling SU and is instantiated and in-service as
well. But when Unlock-in is performed on 2nd SU with command "amf-adm unlock-in
safSu=SU2,safSg=SGTWO,safApp=TWONAPP", the command hangs.
/var/log/messages show
--------------------------------------------------------------------------------
Jul 30 12:19:38 SLES11-SLOT-2 osafamfd[5489]: SG state is not stable
Jul 30 12:19:39 SLES11-SLOT-2 osafamfd[5489]: SG state is not stable
Jul 30 12:19:40 SLES11-SLOT-2 osafamfd[5489]: SG state is not stable
Jul 30 12:19:41 SLES11-SLOT-2 osafamfd[5489]: SG state is not stable
Jul 30 12:19:42 SLES11-SLOT-2 osafamfd[5489]: SG state is not stable
Jul 30 12:19:43 SLES11-SLOT-2 osafamfd[5489]: SG state is not stable
Jul 30 12:19:44 SLES11-SLOT-2 osafamfd[5489]: SG state is not stable
when /etc/init.d/opensafd/ stop is performed, the logs show:
Jul 30 12:20:19 SLES11-SLOT-2 opensafd: Stopping OpenSAF Services
Jul 30 12:20:19 SLES11-SLOT-2 osafamfnd[5499]: Waiting for
'safSi=SI22,safApp=TWONAPP' (state 2)
Jul 30 12:21:19 SLES11-SLOT-2 osafamfnd[5499]: AMF director unexpectedly crashed
Jul 30 12:21:19 SLES11-SLOT-2 osafamfnd[5499]: Rebooting OpenSAF NodeId? =
131599 EE Name = , Reason: local AVD down(Adest) or both AVD down(Vdest)
received
Jul 30 12:21:19 SLES11-SLOT-2 osafimmnd[4215]: Implementer locally
disconnected. Marking it as doomed 3 <14, 2020f> (safAmfService)
Jul 30 12:21:19 SLES11-SLOT-2 osafimmnd[4215]: Implementer disconnected 3 <14,
2020f> (safAmfService)
Jul 30 12:21:19 SLES11-SLOT-2 kernel: TIPC: Disabling bearer <eth:eth4>
Jul 30 12:21:22 SLES11-SLOT-2 kernel: md: stopping all md devices.
Console output after SU1 is unlocked.
--------------------------------------------------------------------------------
safSu=SU1,safSg=SGTWO,safApp=TWONAPP
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=SU2,safSg=SGTWO,safApp=TWONAPP
saAmfSUAdminState=LOCKED-INSTANTIATION(3)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=UNINSTANTIATED(1)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
Console output after unlock-in of SU2:
--------------------------------------------------------------------------------
safSu=SU1,safSg=SGTWO,safApp=TWONAPP
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=SU2,safSg=SGTWO,safApp=TWONAPP
saAmfSUAdminState=LOCKED-INSTANTIATION(3)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=UNINSTANTIATED(1)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
Changed 10 months ago by surenderk
■attachment logs_npi.tgz added
Changed 10 months ago by surenderk ¶
■description modified (diff)
Changed 9 months ago by hafe ¶
AMF should probably correct saAmfSGMaxActiveSIsperSU from "no limit" to 1 if
the SUs in the SG are non-preinstantiable
Changed 9 months ago by hafe ¶
■owner changed from ravisekhar to hafe
■status changed from new to accepted
■version changed from 4.2.2 to 4.2.1
■milestone changed from future_releases to 4.2.2
Changed 9 months ago by hafe ¶
■patch_waiting changed from no to yes
Changed 9 months ago by hafe ¶
■status changed from accepted to closed
■resolution set to fixed
■patch_waiting changed from yes to no
changeset: 3729:83fbba5a881e
branch: opensaf-4.2.x
parent: 3727:031e46c854b8
user: Hans Feldt <hans.feldt@…>
date: Thu Sep 13 13:48:16 2012 +0200
summary: avsv: set saAmfSGMaxActiveSIsperSU to one(1) for NPI SUs (#2734)
changeset: 3730:bb453e687d27
tag: tip
parent: 3728:3ba10af8e49b
user: Hans Feldt <hans.feldt@…>
date: Thu Sep 13 13:48:16 2012 +0200
summary: avsv: set saAmfSGMaxActiveSIsperSU to one(1) for NPI SUs (#2734)
remote: rev 83fbba5a881e5e3f8a9c3775c968d946b5e7350f sent
remote: rev bb453e687d27f85a1f27742535487f07e3936583 sent
Changed 3 months ago by manu ¶
■status changed from closed to reopened
■resolution fixed deleted
Changed 3 months ago by manu ¶
Changeset : 3696
Configuration : A SG,5SUs with 2Comps each of type NPI(category 8).
5SIs with 2CSIs each.
To reproduce the scenario:-
1) Make the above configuration.
2) Unlock-in/unlock the SU1 (Su is instantiated and in- service)
3) But when Unlock-in is performed on 2nd SU with command "amf-adm unlock-in
safSu=SU2,safSg=AmfDemo?,safApp=AmfDemo?", the command hangs.
/var/log/messages snippet:-
Feb 27 17:48:31 SLES_NEW1 osafamfd[15253]: WA SG state is not stable
Feb 27 17:48:32 SLES_NEW1 osafamfd[15253]: WA SG state is not stable
Feb 27 17:48:33 SLES_NEW1 osafamfd[15253]: WA SG state is not stable
Feb 27 17:48:34 SLES_NEW1 osafamfd[15253]: WA SG state is not stable
Feb 27 17:48:35 SLES_NEW1 osafamfd[15253]: WA SG state is not stable
Changed 3 months ago by manu
■attachment messages.tgz added
Changed 3 months ago by manu
■attachment AppConfig-2N_NPI.xml_2734 added
Changed 2 months ago by hafe ¶
■milestone changed from 4.2.2 to future_releases
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
