- **status**: review --> fixed
- **Comment**:
changeset: 5890:de1deaac6a51
branch: opensaf-4.3.x
parent: 5886:c352bd7d1505
user: [email protected]
date: Mon Sep 22 15:46:38 2014 +0530
summary: amf : disable oper state of faulty comp if SU is disabled [#1035]
changeset: 5891:45b6e541f183
branch: opensaf-4.4.x
parent: 5887:2f65a1f78ccd
user: [email protected]
date: Mon Sep 22 15:47:04 2014 +0530
summary: amf : disable oper state of faulty comp if SU is disabled [#1035]
changeset: 5892:963b82000665
branch: opensaf-4.5.x
parent: 5888:ebbcf11d5a8f
user: [email protected]
date: Mon Sep 22 15:47:19 2014 +0530
summary: amf : disable oper state of faulty comp if SU is disabled [#1035]
changeset: 5893:87cc4facabdb
tag: tip
parent: 5889:db4e59d1aef0
user: [email protected]
date: Mon Sep 22 15:47:27 2014 +0530
summary: amf : disable oper state of faulty comp if SU is disabled [#1035]
[staging:de1dea]
[staging:45b6e5]
[staging:963b82]
[staging:87cc4f]
---
** [tickets:#1035] component operation state is not moved to disabled even if
SU is disabled**
**Status:** fixed
**Milestone:** 4.3.3
**Created:** Mon Sep 01, 2014 11:02 AM UTC by surender khetavath
**Last Updated:** Fri Sep 05, 2014 05:01 AM UTC
**Owner:** Praveen
changeset : 5608
model : 2n
configuration : 1App,1SG,2SUs with 2comps each, 1SIs with 1 CSI each
si-si deps configured as SI1 is sponsor to SI2,3,&4.
SU1 is active, SU2 is standby.
SU1 is mapped to sc-2 and SU2 to pl-3
saAmfSGAutoRepair=0(False)
SuFailover=1(True)
Test:
1. Bring up a configuration say 2n Model.
2. Rename/Move the instantiation script.
3. lock/lock-in and unlock-in the SU1
4. Ensure the Component instantiation fails and it
presence state becomes termination-Failed.
5. Ensure the SU's Operational state goes to DISABLED
6. Repair the SU using SA_AMF_ADMIN_REPAIR
SU1 moved to proper state but one component didn't move to disabled state
safSu=2nAdminRepair_SU_1,safSg=2nAdminRepair_SG,safApp=2nAdminRepair
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=DISABLED(2)
saAmfSUPresenceState=TERMINATION-FAILED(7)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
safSu=2nAdminRepair_SU_2,safSg=2nAdminRepair_SG,safApp=2nAdminRepair
saAmfSUAdminState=LOCKED-INSTANTIATION(3)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=UNINSTANTIATED(1)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
safComp=2nAdminRepair,safSu=2nAdminRepair_SU_1,safSg=2nAdminRepair_SG,safApp=2nAdminRepair
saAmfCompOperState=ENABLED(1)
saAmfCompPresenceState=UNINSTANTIATED(1)
saAmfCompReadinessState=OUT-OF-SERVICE(1)
safComp=2nAdminRepair_1,safSu=2nAdminRepair_SU_1,safSg=2nAdminRepair_SG,safApp=2nAdminRepair
saAmfCompOperState=ENABLED(1)
saAmfCompPresenceState=TERMINATION-FAILED(7)
saAmfCompReadinessState=OUT-OF-SERVICE(1)
---
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.------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
