- **status**: accepted --> review
- **Part**: - --> nd
- **Comment**:
Though a patch for 5.0.x and default has been publuished because the following
command was not working:
amf-adm lock safSu=SC-2,safSg=NoRed,safApp=OpenSAF
amf-adm lock-in safSu=SC-2,safSg=NoRed,safApp=OpenSAF
amf-adm unlock-in safSu=SC-2,safSg=NoRed,safApp=OpenSAF
But the use case described in the ticket is not supported as per README since
there is no as such use case:
README:
Admin Operations on OpenSAF SUs
===============================
From OpenSAF release 4.4 onwards, the AMF admin operations lock, lock-in,
unlock, unlock-in is allowed to be performed on the OpenSAF SUs (i.e.
safSu=<nodename>,safSg=2N,safApp=OpenSAF
safSu=<nodename>,safSg=NoRed,safApp=OpenSAF) However, these commands should be
restrictively used, like running them from a SMF campaign. When running this
from an SMF campaign, OpenSAF shall support the behaviour only when used under
the supported usecases of OpenSAF. At this point of time, there is no evident
usecase to support this. Also note that locking of the 2N SU is currently not
supported when the system is configured with more than two system controller
nodes.
As such, this is invalid ticket because once you lock NoRed, then component
will not be able to read configuration from Immnd during unlock of 2N SU,
because Immnd is not available because it is locked-in.
---
** [tickets:#369] Performing admin unlock-in operation on standby MW SU,
standby controller rebooted due to RDE component got instantiation failed.**
**Status:** review
**Milestone:** 5.1.FC
**Created:** Fri May 31, 2013 03:46 AM UTC by Nagendra Kumar
**Last Updated:** Wed Jun 29, 2016 12:11 PM UTC
**Owner:** Nagendra Kumar
**Attachments:**
- [logs.tar](https://sourceforge.net/p/opensaf/tickets/369/attachment/logs.tar)
(433.5 kB; application/x-gzip-compressed)
Migrated from http://devel.opensaf.org/ticket/2312
Setup: 4 Node SUSE 11, PC-Setup, 64Bit
Changeset : 3032
Scenario:
1. Brought up 4 nodes SC-1 as active , SC-2 as standby and PL-3, PL-4 as
payloads.
2. On active controller, perfomed the below operations:-
# amf-adm lock safSu=SC-2,safSg=2N,safApp=OpenSAF
# amf-adm lock-in safSu=SC-2,safSg=2N,safApp=OpenSAF
# amf-adm lock safSu=SC-2,safSg=NoRed?,safApp=OpenSAF
# amf-adm lock-in safSu=SC-2,safSg=NoRed?,safApp=OpenSAF
States after step 2 are as shown below:-
inux-xc76:~ # amf-state su
safSu=PL-4,safSg=NoRed?,safApp=OpenSAF
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=PL-3,safSg=NoRed?,safApp=OpenSAF
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=SC-1,safSg=2N,safApp=OpenSAF
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=SC-1,safSg=NoRed?,safApp=OpenSAF
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=SC-2,safSg=2N,safApp=OpenSAF
saAmfSUAdminState=LOCKED-INSTANTIATION(3)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=UNINSTANTIATED(1)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
safSu=SC-2,safSg=NoRed?,safApp=OpenSAF
saAmfSUAdminState=LOCKED-INSTANTIATION(3)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=UNINSTANTIATED(1)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
On Standby , ps -ef | grep osaf output :-
==========================
linux-xc76:~ # ps -ef | grep osaf
root 4442 1 0 14:25 ? 00:00:00 /usr/lib64/opensaf/osafamfd —tracemask=0xffffffff
root 4452 1 0 14:25 ? 00:00:00 /usr/lib64/opensaf/osafamfnd
—tracemask=0xffffffff
root 4599 2989 0 14:26 pts/1 00:00:00 grep osaf
3. Performed admin unlock-instantiation of MW standby SU , which fails with
SA_AIS_ERR_TIMEOUT.
amf-adm unlock-in safSu=SC-2,safSg=2N,safApp=OpenSAF
error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: SA_AIS_ERR_TIMEOUT (5)
After step3, observed that standby controller went down due to instantiation
failed for RDE component.
SC-2 /var/log/messages:-
========================
Nov 16 14:37:10 linux-cgbm osafamfnd[4370]:
'safSu=SC-2,safSg=2N,safApp=OpenSAF' Presence State UNINSTANTIATED =>
INSTANTIATING
Nov 16 14:37:10 linux-cgbm osafamfnd[4370]: Instantiation of
'safComp=RDE,safSu=SC-2,safSg=2N,safApp=OpenSAF' failed
Nov 16 14:37:10 linux-cgbm osafamfnd[4370]: Reason:'Exec of script success, but
script exits with non-zero status'
Nov 16 14:37:10 linux-cgbm osafamfnd[4370]: Exit code: 7
Nov 16 14:37:10 linux-cgbm osafrded[4670]: Started
Nov 16 14:37:10 linux-cgbm osafrded[4670]: rde@2010f has active state =>
Standby role
Nov 16 14:37:20 linux-cgbm osafamfnd[4370]: Instantiation of
'safComp=RDE,safSu=SC-2,safSg=2N,safApp=OpenSAF' failed
Nov 16 14:37:20 linux-cgbm osafamfnd[4370]: Reason: component registration
timer expired
Nov 16 14:37:20 linux-cgbm osafamfnd[4370]:
'safComp=RDE,safSu=SC-2,safSg=2N,safApp=OpenSAF'got Inst failed
Nov 16 14:37:20 linux-cgbm osafamfnd[4370]: Rebooting OpenSAF NodeId? = 131599
EE Name = , Reason: NCS component Instantiation failed
=====================================
Amfd, amfnd logs for both the controllers are attached.
Changed 19 months ago by sathyush
■attachment logs.tgz added
Changed 19 months ago by hafe ¶
All the "NID" started processes that at the same time are AMF components
(RDE, FM, CLMD, LOG, IMMD, NTFD, ?) cannot be started by AMF which is the case
here. They are not designed for that. Could be fixed but what is the use case?
Changed 19 months ago by sathyush ¶
■milestone changed from 4.2.1 to future_releases
The usecase tested here is, to lock, lock instantiate of MW SU's followed by
unlock instantiation, unlock of middleware SU's and verify that all the
middleware SU's are brought up successfully.
Changed 19 months ago by sathyush ¶
The above admin operations when performed on standby controller, had a
different behaviour.
On SC-2, performed the below operations and their output is as follows:
===========================================================================
# amf-adm lock safSu=SC-2,safSg=2N,safApp=OpenSAF
# amf-adm lock-in safSu=SC-2,safSg=2N,safApp=OpenSAF
# amf-adm lock safSu=SC-2,safSg=NoRed?,safApp=OpenSAF
# amf-adm lock-in safSu=SC-2,safSg=NoRed?,safApp=OpenSAF
The first 3 operations were successful but lock-in of NoRed? SU's gave
SA_AIS_ERR_BAD_HANDLE
===================================================
amf-adm lock-in safSu=SC-2,safSg=NoRed?,safApp=OpenSAF
error - saImmOmAdminOperationInvoke_2 FAILED: SA_AIS_ERR_BAD_HANDLE (9)
amf-state su
error - saImmOmInitialize FAILED: SA_AIS_ERR_TRY_AGAIN (6)
# ps -ef | grep saf
root 13246 1 0 Nov16 ? 00:00:02 /bin/bash /usr/lib/opensaf/nid_tipc start eth0
7788
root 13346 1 0 Nov16 ? 00:00:06 /usr/lib/opensaf/osafamfd —tracemask=0xffffffff
root 13356 1 0 Nov16 ? 00:00:07 /usr/lib/opensaf/osafamfnd —tracemask=0xffffffff
root 29803 3205 0 09:47 pts/0 00:00:00 grep saf
=========================================================
---
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.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
