[tickets] [opensaf:tickets] #1945 AMF: Refactoring for 5.1

2016-08-09 Thread Gary Lee 



---

** [tickets:#1945] AMF: Refactoring for 5.1**

**Status:** unassigned
**Milestone:** 5.1.FC
**Created:** Wed Aug 10, 2016 05:37 AM UTC by Gary Lee
**Last Updated:** Wed Aug 10, 2016 05:37 AM UTC
**Owner:** nobody


This is the 5.1 ticket to continue code re-factoring of the AMF service. The 
ticket for 5.0 was #1520.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1725 AMF: Recover transient SUSIs left over from headless

2016-08-09 Thread Minh Hon Chau 
Hi Praveen,

I guess I will update the naming of new attribute in next version soon.
I have just realized that the failing test 144 in headless mode is because 
AVD_SU::su_switch affects on si-swap sequence, and it's not stored in IMM 
together with the other new attrs. I think I will float this change of 
su_switch after I receive first round comment.

Thanks,
Minh


---

** [tickets:#1725] AMF: Recover transient SUSIs left over from headless**

**Status:** review
**Milestone:** 5.1.FC
**Created:** Wed Apr 06, 2016 07:16 AM UTC by Minh Hon Chau
**Last Updated:** Tue Aug 09, 2016 05:35 AM UTC
**Owner:** Minh Hon Chau


This ticket is more likely an enhancement that targets on how AMFD detect and 
recover the transients SUSI left over from headless. There are three major 
situations:
(1) - Cluster goes headless, su/node failover on any payloads can happen, or 
any payloads can be hard rebooted/powered off by operator, then cluster recover
(2) - issue admin op on any AMF entities, cluster goes headless. During 
headless, the middle HA assignments of whole admin op sequence between AMFND 
and components could be:
(2.1) The assignment completes, component returns OK with csi callback, 
then cluster recover
(2.2) The assignment is under going, then cluster recover. The assignment 
afterward could complete, or csi callback returns FAILED_OPERATION or error can 
also happen

At the time cluster recover, amfd has collected all assignments from all 
amfnd(s). These assignments can be in assigned or assigning states whilst its 
HA states do not conform its SG redundancy. Any of (1) (2.1) (2.2) can happen 
in a combination, which means while issuing admin op (2), cluster go headless 
and any kinds of failover (1) can happen during headless.  



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1938 AMFD: Incorrect setting SU readiness state

2016-08-09 Thread Minh Hon Chau 
- **status**: assigned --> review



---

** [tickets:#1938] AMFD: Incorrect setting SU readiness state**

**Status:** review
**Milestone:** 5.0.1
**Created:** Mon Aug 08, 2016 08:01 AM UTC by Minh Hon Chau
**Last Updated:** Mon Aug 08, 2016 08:01 AM UTC
**Owner:** Minh Hon Chau


In SU repair scenario, the SU's readiness state is currently set to IN_SERVICE 
in avd_data_update_req_evh()

case saAmfSUOperState_ID:
TRACE("oper pres state");
if 
(n2d_msg->msg_info.n2d_data_req.param_info.value_len == sizeof(uint32_t)) {
l_val = ntohl(*((uint32_t 
*)_msg->msg_info.n2d_data_req.param_info.value[0]));
su->set_oper_state(l_val);
}

if (su->is_in_service() == true) {

su->set_readiness_state(SA_AMF_READINESS_IN_SERVICE);
}

And later on, avd_su_oper_state_evh() set SU's readiness state back to 
OUT_OF_SERVICE. 

if (avd_cb->scs_absence_max_duration > 0 &&
su->saAmfSUPresenceState == 
SA_AMF_PRESENCE_UNINSTANTIATED &&
su->saAmfSUPreInstantiable == false) {
// this is to allow non NPI SUs to be repaired 
if
// headless mode is enabled. Otherwise, the code
// following will assume the SU is already in 
service
// when it failed to instantiate while headless

if (cb->init_state == AVD_APP_STATE) {
LOG_NO("Setting NPI SU '%s' to OOS 
after headless state", su->name.value);

su->set_readiness_state(SA_AMF_READINESS_OUT_OF_SERVICE);
}
}

This logic is redundant and SU's readiness state should not be set while 
updating SU' oper state to align with non-headless's logic consistency


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1642 AMF: Support DNs longer than 255 bytes

2016-08-09 Thread Praveen 
Hi Gary,
Patch looks fine. I will rerun some failed test cases.

Thanks,
Praveen


---

** [tickets:#1642] AMF: Support DNs longer than 255 bytes**

**Status:** review
**Milestone:** 5.1.FC
**Created:** Tue Dec 15, 2015 09:52 AM UTC by Long HB Nguyen
**Last Updated:** Tue Aug 09, 2016 04:34 AM UTC
**Owner:** Long HB Nguyen


Ticket [#191] introduced generic support in OpenSAF for DNs longer than 255 
bytes. Each individual OpenSAF service will also have to be adapted to support 
long DNs. This ticket is for AMF to support this feature.
Moreover, this ticket also contains some enhancements:
1) Refactor internal SaNameT to std::string in amfd, amfnd.
2) Refactor PATRICIA trees to std::map in amfnd.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1634 smfd: NG lock and unlock in single step upgrade

2016-08-09 Thread elunlen 
- **status**: review --> fixed
- **assigned_to**: elunlen -->  nobody 
- **Comment**:

changeset:   7846:31417997c82f
tag: tip
user:Lennart Lund 
date:Tue Aug 09 12:08:48 2016 +0200
summary: smf: Lock nodes in parallel [#1634]

rev: 31417997c82fc34e1a7e438ed44e09612d6e2ad3



---

** [tickets:#1634] smfd: NG lock and unlock in single step upgrade**

**Status:** fixed
**Milestone:** 5.1.FC
**Created:** Mon Dec 14, 2015 08:23 AM UTC by Ingvar Bergström
**Last Updated:** Fri Jun 17, 2016 03:10 PM UTC
**Owner:** nobody


In single step upgrades, locking and unlocking are made in serial for the 
affected activation and deactivation units (AU/DU).
If the AU/DU is on node level it could be possible to use the node group (NG) 
lock/unlock mechanism to minimize upgrade time.
The “keep state” configure option i.e. the admin state of the AU/DU shall be 
kept after unlock, must be possible to use also in case NG lock/unlock is used.



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #316 SI Assignments are not removed for a SU in Nway redundancy model

2016-08-09 Thread Praveen 
This issue is observed in one more case related to SU lock along with 
su-failover recovery.
Attached quiesced.tgz contains conf and traces.
steps to reproduce:
1)Bting up the configuration.
2)Lock active SU.
3)The Su that is becoming active because of lock operation should fault with 
su-failover reocvery.
4)Amfd will not remove quiesced assignments from locked SU:

after lock assignments are:
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=QUIESCED(3)



Attachments:

- 
[quiesced.tgz](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/0143c687/43d6/attachment/quiesced.tgz)
 (45.3 kB; application/x-compressed)


---

** [tickets:#316] SI Assignments are not removed for a SU in Nway redundancy 
model**

**Status:** accepted
**Milestone:** 4.7.2
**Created:** Fri May 24, 2013 08:39 AM UTC by Nagendra Kumar
**Last Updated:** Wed May 04, 2016 07:20 PM UTC
**Owner:** Praveen
**Attachments:**

- [logs.tar](https://sourceforge.net/p/opensaf/tickets/316/attachment/logs.tar) 
(2.5 MB; application/x-gzip-compressed)
- [osafamfd](https://sourceforge.net/p/opensaf/tickets/316/attachment/osafamfd) 
(228.2 kB; application/octet-stream)
- 
[osafamfnd](https://sourceforge.net/p/opensaf/tickets/316/attachment/osafamfnd) 
(122.8 kB; application/octet-stream)
- 
[pl_logs.tar](https://sourceforge.net/p/opensaf/tickets/316/attachment/pl_logs.tar)
 (1.3 MB; application/x-gzip-compressed)


Migrated from http://devel.opensaf.org/ticket/2987

changeset : 3855
Model : NWay
configuration : 1App,1SG,5SU with 3comps each, 5SIs with 3csi each.
si-si deps configured as SI1<-SI2<-SI3<-SI4
SIrankedSus not configured. 
Node mapping : SU1 on SC-1, SU2 on SC-2, SU3 on PL-3, SU4,SU5 on PL-4.


While running the campaign, smf performs lock,lock-in of the activation units 
i.e SUs. The SIs for SU3 are not removed though SU3 is in locked-state. 
Subsequent unlock-in,unlock of SU3 fails. 


/var/log/messages of active ctrl- SC-1 shows

Feb 3 22:45:14 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:16 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:18 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:20 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:23 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Fail to invoke admin operation, 
too many SA_AIS_ERR_TRY_AGAIN, giving up. 
dn=[safSu=SU3,safSg=SGONE,safApp=NWAYAPP], opId=[3]
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Failed to call admin operation 3 
on safSu=SU3,safSg=SGONE,safApp=NWAYAPP
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Failed to Terminate activation 
units in step=safSmfStep=0003
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Step undoing failed
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Step safSmfStep=0003 in procedure 
safSmfProc=amfClusterProc-1 failed, step result 5
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: NO CAMP: Procedure 
safSmfProc=amfClusterProc-1 returned FAILED


SU Assignments brief:
===
safSISU=safSu=SU1\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI3,safApp=NWAYAPP


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SU1\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI2,safApp=NWAYAPP


saAmfSISUHAState=STANDBY(2)


safSISU=safSu=SU3\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI5,safApp=NWAYAPP


saAmfSISUHAState=QUIESCED(3)


safSISU=safSu=SU4\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI5,safApp=NWAYAPP


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SU2\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI1,safApp=NWAYAPP


saAmfSISUHAState=ACTIVE(1)


SU States:
==
safSu=SU3,safSg=SGONE,safApp=NWAYAPP


saAmfSUAdminState=LOCKED(2)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=OUT-OF-SERVICE(1)


changed 4 months ago by bertil ¶
  ■owner changed from ingber to ravisekhar 
■component changed from saf/smfsv to saf/avsv 
I beleave this is an AMF problem. SMF only uses the AMF admin ops (lock, unlock 
etc).






---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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

[tickets] [opensaf:tickets] #1484 amf: Nway, two SUs active for same SI after sufailover recovery during si lock.

2016-08-09 Thread Praveen 
- **status**: unassigned --> accepted
- **assigned_to**: Praveen



---

** [tickets:#1484] amf: Nway, two SUs  active for same SI  after sufailover 
recovery during si lock.**

**Status:** accepted
**Milestone:** 4.7.2
**Created:** Wed Sep 16, 2015 09:08 AM UTC by Praveen
**Last Updated:** Wed May 04, 2016 07:27 PM UTC
**Owner:** Praveen
**Attachments:**

- 
[AppConfig-N-Way_2actives.xml](https://sourceforge.net/p/opensaf/tickets/1484/attachment/AppConfig-N-Way_2actives.xml)
 (16.1 kB; text/xml)
- 
[osafamfd](https://sourceforge.net/p/opensaf/tickets/1484/attachment/osafamfd) 
(1.3 MB; application/octet-stream)


Attached is the configuration and AMF traces to reproduce the problem.

steps to reproduce:
1)Lock the SI which has assignment on all the SUs.
2)When active component is processing quiesced callback, kill the standby comp 
for this Si on other SU with 
sufailover recovery.
3)AMF will revert back SI to unlocked state.
4)user will see two actives for same SIs.

Assignments before si lock:
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)

Assignment after si lock was tried and sufailover recovery:
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)

For safSi=AmfDemo1,safApp=AmfDemo1, there are two active assignments.




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1944 amf: two actives for same SI after sufailover recovery during su lock/shutdown, NWAY.

2016-08-09 Thread Praveen 
- **status**: unassigned --> accepted
- **assigned_to**: Praveen
- **Component**: unknown --> amf
- **Part**: - --> d
- **Comment**:

May be a duplicate of #1484  "amf: Nway, two SUs active for same SI after 
sufailover recovery during si lock."



---

** [tickets:#1944] amf: two actives for same SI after sufailover recovery 
during su lock/shutdown, NWAY.**

**Status:** accepted
**Milestone:** 4.7.2
**Created:** Tue Aug 09, 2016 09:23 AM UTC by Praveen
**Last Updated:** Tue Aug 09, 2016 09:23 AM UTC
**Owner:** Praveen
**Attachments:**

- 
[two_actives.tgz](https://sourceforge.net/p/opensaf/tickets/1944/attachment/two_actives.tgz)
 (69.1 kB; application/x-compressed)


Attached are traces and conf.

steps to reproduce:
1)Bring the configuration up.
2)Lock active SU.
3)While processing remove callback, one comp must fault sufailover recovery.
4)Amf will make Su3 also active for both the SIs when Su2 is already make 
active after quiesced assignments.

Assignments before su lock
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)

Assignments after SU lock:
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)

Issue will be applicable to Nore lock/shutdown also.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1944 amf: two actives for same SI after sufailover recovery during su lock/shutdown, NWAY.

2016-08-09 Thread Praveen 



---

** [tickets:#1944] amf: two actives for same SI after sufailover recovery 
during su lock/shutdown, NWAY.**

**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue Aug 09, 2016 09:23 AM UTC by Praveen
**Last Updated:** Tue Aug 09, 2016 09:23 AM UTC
**Owner:** nobody
**Attachments:**

- 
[two_actives.tgz](https://sourceforge.net/p/opensaf/tickets/1944/attachment/two_actives.tgz)
 (69.1 kB; application/x-compressed)


Attached are traces and conf.

steps to reproduce:
1)Bring the configuration up.
2)Lock active SU.
3)While processing remove callback, one comp must fault sufailover recovery.
4)Amf will make Su3 also active for both the SIs when Su2 is already make 
active after quiesced assignments.

Assignments before su lock
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)

Assignments after SU lock:
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)

Issue will be applicable to Nore lock/shutdown also.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1943 imm: Applier crashes when receiving ccb upcalls

2016-08-09 Thread Hung Nguyen 
Adding coredump backtrace.


Attachments:

- 
[osafntfimcnd.6922.SC-1.core.txt](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/fa1acd3b/4db3/attachment/osafntfimcnd.6922.SC-1.core.txt)
 (12.4 kB; text/plain)


---

** [tickets:#1943] imm: Applier crashes when receiving ccb upcalls**

**Status:** accepted
**Milestone:** 4.7.2
**Created:** Tue Aug 09, 2016 09:08 AM UTC by Hung Nguyen
**Last Updated:** Tue Aug 09, 2016 09:08 AM UTC
**Owner:** Hung Nguyen
**Attachments:**

- 
[systemlogs.7z](https://sourceforge.net/p/opensaf/tickets/1943/attachment/systemlogs.7z)
 (1.8 MB; application/octet-stream)


~~~
Aug  5 10:40:28 SC-1 osafntfimcnd[6922]: ER imma_oi_ccb_record_add inv==0 yet 
cl_node->isPbe is false!
Aug  5 10:40:28 SC-1 osafntfimcnd[6922]: imma_db.c:238: imma_oi_ccb_record_add: 
Assertion 'cl_node->isPbe' failed.
~~~

ntfimcn sets IMMA_SYNCR_TIMEOUT to 100 (1 second).
If timeout occurs when invoking saImmOiImplementerSet(), isApplier is reverted 
to false.
Applier will crash if it receiving a ccb upcall at that time.



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1943 imm: Applier crashes when receiving ccb upcalls

2016-08-09 Thread Hung Nguyen 



---

** [tickets:#1943] imm: Applier crashes when receiving ccb upcalls**

**Status:** accepted
**Milestone:** 4.7.2
**Created:** Tue Aug 09, 2016 09:08 AM UTC by Hung Nguyen
**Last Updated:** Tue Aug 09, 2016 09:08 AM UTC
**Owner:** Hung Nguyen
**Attachments:**

- 
[systemlogs.7z](https://sourceforge.net/p/opensaf/tickets/1943/attachment/systemlogs.7z)
 (1.8 MB; application/octet-stream)


~~~
Aug  5 10:40:28 SC-1 osafntfimcnd[6922]: ER imma_oi_ccb_record_add inv==0 yet 
cl_node->isPbe is false!
Aug  5 10:40:28 SC-1 osafntfimcnd[6922]: imma_db.c:238: imma_oi_ccb_record_add: 
Assertion 'cl_node->isPbe' failed.
~~~

ntfimcn sets IMMA_SYNCR_TIMEOUT to 100 (1 second).
If timeout occurs when invoking saImmOiImplementerSet(), isApplier is reverted 
to false.
Applier will crash if it receiving a ccb upcall at that time.



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1937 immtools: Allow immadm to explicitly set ReleaseOnFinalize

2016-08-09 Thread Hung Nguyen 
- **status**: accepted --> review



---

** [tickets:#1937] immtools: Allow immadm to explicitly set ReleaseOnFinalize**

**Status:** review
**Milestone:** 5.1.FC
**Created:** Mon Aug 08, 2016 05:54 AM UTC by Hung Nguyen
**Last Updated:** Mon Aug 08, 2016 06:01 AM UTC
**Owner:** Hung Nguyen


When using immadm with '-a' option to use a custom admo name, ROF is always set 
to false.
In some cases, users might want to auto release the Admo from the object 
instead of using 'immcfg --admin-owner-clear' after every immadm command.

Introduce '-r' option to explicitly set the ROF when initializing admin owner 
handle.
The default value for ROF (when -r option is not specified) is SA_FALSE.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1933 log: client crashed due to not initialize the client_list pointer

2016-08-09 Thread Vu Minh Nguyen 
- **status**: review --> fixed
- **assigned_to**: Vu Minh Nguyen -->  nobody 
- **Comment**:

changeset:   7845:1f90fdce1b07
tag: tip
parent:  7843:a474d9b4ad86
user:Vu Minh Nguyen 
date:Tue Aug 09 13:57:23 2016 +0700
summary: log: client crashed due to not initialize the client_list pointer 
[#1933]

changeset:   7844:c603424ffe8d
branch:  opensaf-5.0.x
parent:  7839:cd74d23ecbcd
user:Vu Minh Nguyen 
date:Fri Aug 05 14:42:38 2016 +0700
summary: log: client crashed due to not initialize the client_list pointer 
[#1933]




---

** [tickets:#1933] log: client crashed due to not initialize the client_list 
pointer**

**Status:** fixed
**Milestone:** 5.0.1
**Created:** Thu Aug 04, 2016 11:33 AM UTC by Vu Minh Nguyen
**Last Updated:** Fri Aug 05, 2016 07:47 AM UTC
**Owner:** nobody


The global `client_list` pointer is not initialized to NULL.
 
When the SCs is restarted from headless, the recovery thread will do recover 
based on the info in `client_list`. As the pointer is not initialized, the 
default value is unspecific. 
It might refer to an invalid/unallocated memory. If it is the case, the 
application will be crashed.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1942 amf: issue with comp-failover recovery during su lock in N-Way model.

2016-08-09 Thread Praveen 



---

** [tickets:#1942] amf: issue with comp-failover recovery during su lock in 
N-Way model.**

**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue Aug 09, 2016 06:56 AM UTC by Praveen
**Last Updated:** Tue Aug 09, 2016 06:56 AM UTC
**Owner:** nobody
**Attachments:**

- 
[compfail.tgz](https://sourceforge.net/p/opensaf/tickets/1942/attachment/compfail.tgz)
 (52.1 kB; application/x-compressed)


Conf: Nway model, comp-failover recovery.
steps to reprodue:
1)Bring attached configuration up.
2)Issue lock operation on SU and make sure one comp faults with comp-failover 
recovery.
3)One of the SIs will remain with standby assignments without active. AMFD does 
not perform failover/switchover of SI.

AMFD sends deletion of assignments during recivery request:
Aug  9 11:51:31.142846 osafamfd [4373:sgproc.cc:2340] >> avd_sg_su_si_del_snd: 
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Aug  9 11:51:31.142854 osafamfd [4373:mbcsv_api.c:0773] >> 
mbcsv_process_snd_ckpt_request: Sending checkpoint data to all STANDBY peers, 
as per the send-type specified
Aug  9 11:51:31.142860 osafamfd [4373:mbcsv_api.c:0803] TR svc_id:10, 
pwe_hdl:65537
Aug  9 11:51:31.142865 osafamfd [4373:mbcsv_util.c:0343] >> mbcsv_send_ckpt_dat

When AMFD gets response from AMFND in realign state, it does not faiolver the 
assignments and deletes SUSIs in SU:
Aug  9 11:51:31.160480 osafamfd [4373:sgproc.cc:1051] >> avd_su_si_assign_evh: 
id:106, node:2010f, act:4, 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1', '', ha:3, 
err:1, single:0
Aug  9 11:51:31.160703 osafamfd [4373:sg_nway_fsm.cc:2182] >> 
avd_sg_nway_susi_succ_sg_realign:  action:4 state:3
Aug  9 11:51:31.160709 osafamfd [4373:su.cc:2047] >> delete_all_susis: 
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Aug  9 11:51:31.160714 osafamfd [4373:csi.cc:1198] >> avd_compcsi_delete
Aug  9 11:51:31.160720 osafamfd [4373:pg.cc:0165] >> avd_pg_compcsi_chg_prc
Aug  9 11:51:31.160725 osafamfd [4373:pg.cc:0175] << avd_pg_compcsi_chg_prc: 1

Because of this one SI remain in standby state without any active. 


Assignments before lock operation:
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo2,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo2,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)

Assginemnts after lock operation:
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo2,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
After lock operation and fault safSi=AmfDemo,safApp=AmfDemo1 remain with 
standby assignments only. AMFD can make SU3 active for this SI as it is allowed 
by the configuration.

AMFD is not performing any switchover/failover in realign state for SU level 
delete  in avd_sg_nway_susi_succ_sg_realign() function. Case of single SUSI 
delete is handled. 
Also when operation is in progress, SG was marked stable even though comp in 
locked SU is still having quiesced assignments. In Nway model, AMFD some times 
handle events in like stable state, but it should not mark it stable as it will 
open window for other admin op to progress.

Issue will be applicable to lock operation on Node also as it uses same code 
path.

Attachment includes conf and traces.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net

[tickets] [opensaf:tickets] #1638 Integrate LOG service with CLM

2016-08-09 Thread A V Mahesh (AVM) 
- **status**: assigned --> review



---

** [tickets:#1638] Integrate LOG service with CLM **

**Status:** review
**Milestone:** 5.1.FC
**Created:** Tue Dec 15, 2015 08:26 AM UTC by Mathi Naickan
**Last Updated:** Wed Jul 20, 2016 04:53 AM UTC
**Owner:** A V Mahesh (AVM)


Refer section 3.2 Unavailability of the Log Service API on a Non-Member Node.
More details to come.



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1658 mds : Opensf transport should adopt the size of the timeout parameter from 32 bits to 64 bits

2016-08-09 Thread A V Mahesh (AVM) 
- **status**: assigned --> review



---

** [tickets:#1658] mds : Opensf transport should adopt the size of the timeout 
parameter from 32 bits to 64 bits**

**Status:** review
**Milestone:** 5.1.FC
**Created:** Thu Jan 07, 2016 09:13 AM UTC by A V Mahesh (AVM)
**Last Updated:** Wed May 04, 2016 05:00 PM UTC
**Owner:** A V Mahesh (AVM)


In current implementation their is a mismatch of variable sizes between SAF 
SaTimeT variable ( 64 bit) and MDS transport implementation (32 bit) timeout 
variable , the  MDS transpot should  adopt the size of the timeout parameter 
from 32 bits to 64 bits.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1941 log: logtest suite 9 and 10 failed

2016-08-09 Thread Vu Minh Nguyen 



---

** [tickets:#1941] log: logtest suite 9 and 10 failed**

**Status:** accepted
**Milestone:** 5.1.FC
**Created:** Tue Aug 09, 2016 06:12 AM UTC by Vu Minh Nguyen
**Last Updated:** Tue Aug 09, 2016 06:12 AM UTC
**Owner:** Vu Minh Nguyen


`create_new_app_stream()` was changed and introduced new error codes in long DN 
ticket. One of them is `SA_AIS_ERR_EXIST`. 

When SCs restart from headless,  `create_new_app_stream()` returns 
`SA_AIS_ERR_EXIST` but this error code was not handled correctly and made 
recovery functionality fail.

`lgs_restore_one_app_stream` needs to be updated.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets