Hi, 1. Please mention the detail steps that is followed while testing the use case. Are you using opensaf-4.3.0.tar.gz?
2. since it is reproducible(Before reproducing, cleanup all the nodes), please run the use case and share the syslog of all the nodes and ps output of opensaf process. There is no problem, as you are removing the payload blade, and in general this should not affect the cluster (particularly controllers). /Neel. On Wednesday 26 February 2014 02:22 AM, Tony Hart wrote: > We are seeing osaf stall on startup on a payload card. The 'ps' trace below > shows the processes on the payload. It never gets any further than this > until we kill the osafimmnd process running on the controller. As soon as we > do that the payload comes up. > > oot 1319 0.0 0.0 0 0 ? ZNs 20:34 0:00 [osaf-immnd] > <defunct> > opensaf 1326 0.3 0.3 173916 11876 ? SNsl 20:34 0:01 > /usr/lib64/opensaf/osafimmnd osafimmnd > root 1340 0.0 0.0 0 0 ? Zs 20:34 0:00 [osaf-noded] > <defunct> > root 1349 0.0 0.0 0 0 ? Zs 20:34 0:00 [osaf-amfnd] > <defunct> > root 1353 0.0 0.0 159956 1720 ? Ssl 20:34 0:00 > /usr/lib64/opensaf/osafamfnd osafamfnd > > When we look that the state of the OpenSAF SU we see the following.. > > scm1:~$ immlist $(amf-find su | grep OpenSAF | grep SCM1 | grep 2N) > > Name Type Value(s) > ======================================================================== > safSu SA_STRING_T safSu=SCM1 > saAmfSUType SA_NAME_T > safVersion=4.0.0,safSuType=OpenSafSuTypeServer (46) > saAmfSURestartCount SA_UINT32_T <Empty> > saAmfSUReadinessState SA_UINT32_T <Empty> > saAmfSURank SA_UINT32_T 0 (0x0) > saAmfSUPresenceState SA_UINT32_T <Empty> > saAmfSUPreInstantiable SA_UINT32_T <Empty> > saAmfSUOperState SA_UINT32_T <Empty> > saAmfSUNumCurrStandbySIs SA_UINT32_T <Empty> > saAmfSUNumCurrActiveSIs SA_UINT32_T <Empty> > saAmfSUMaintenanceCampaign SA_NAME_T <Empty> > saAmfSUHostedByNode SA_NAME_T <Empty> > saAmfSUHostNodeOrNodeGroup SA_NAME_T > safAmfNode=SCM1,safAmfCluster=myAmfCluster (42) > saAmfSUFailover SA_UINT32_T 1 (0x1) > saAmfSUAssignedSIs SA_NAME_T <Empty> > saAmfSUAdminState SA_UINT32_T 1 (0x1) > SaImmAttrImplementerName SA_STRING_T safAmfService > SaImmAttrClassName SA_STRING_T SaAmfSU > SaImmAttrAdminOwnerName SA_STRING_T IMMLOADER > > > This is reproducible all we need to do is remove two payload cards and > re-insert them both. > > Does this problem ring any bells? > > thanks > --- > tony > > P.S. full logs are attached. > > > ------------------------------------------------------------------------------ > Flow-based real-time traffic analytics software. Cisco certified tool. > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer > Customize your own dashboards, set traffic alerts and generate reports. > Network behavioral analysis & security monitoring. All-in-one tool. > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk > > > _______________________________________________ > Opensaf-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensaf-users ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
