For Following reasons,I do not agree with the argument.
1.Imm configuration is the only configuration through which one can pick the
clm related configuration attributes."saClmNodeAddress" is a configuration
attribute and it needs to be specified.If it is not specifiedin the imm
configuration,you can still add values to both IMM and CLM database but not
only to CLM database.If the reason for not adding to IMM is that is not
mentioned in IMM,then it shouldn't be added to CLM as well.
2.From the user perspective,it would be not easy task to update the node
address information to every node ,especially in scalable set ups and for every
new node he adds dynamically,he needs to add the node information twice.When
he is already adding the node address in dtmd.conf and it is already being
picked for CLM.
---
** [tickets:#760] NodeAddress is not updated in the IMM database.**
**Status:** invalid
**Created:** Fri Jan 31, 2014 10:11 AM UTC by Sirisha Alla
**Last Updated:** Fri Jan 31, 2014 10:26 AM UTC
**Owner:** nobody
As part of ticket #228,node Address is implemented for CLM node object.
The address is added to CLM database but not added to IMM database (or not
retrivable through IMM interface).
Following is the snippet of console output.
3:/opt/goahead/tetware/opensaffire # immlist
safNode=SC-1,safCluster=myClmCluster
Name Type Value(s)
========================================================================
safNode SA_STRING_T safNode=SC-1
saClmNodeLockCallbackTimeout SA_TIME_T 50000000000
(0xba43b7400, Thu Jan 1 05:30:50 1970)
saClmNodeIsMember SA_UINT32_T 1 (0x1)
saClmNodeInitialViewNumber SA_UINT64_T 1 (0x1)
saClmNodeID SA_UINT32_T 131343 (0x2010f)
saClmNodeEE SA_NAME_T <Empty>
saClmNodeDisableReboot SA_UINT32_T 0 (0x0)
saClmNodeCurrAddressFamily SA_UINT32_T <Empty>
saClmNodeCurrAddress SA_STRING_T <Empty>
saClmNodeBootTimeStamp SA_TIME_T
1391160375000000000 (0x134e64fd89796600, Fri Jan 31 14:56:15 2014)
saClmNodeAdminState SA_UINT32_T 1 (0x1)
saClmNodeAddressFamily SA_UINT32_T <Empty>
saClmNodeAddress SA_STRING_T <Empty>
SaImmAttrImplementerName SA_STRING_T safClmService
SaImmAttrClassName SA_STRING_T SaClmNode
SaImmAttrAdminOwnerName SA_STRING_T IMMLOADER
SLOT3:/opt/goahead/tetware/opensaffire # immlist
safNode=SC-1,safCluster=myClmCluster -a saClmNodeAddress
saClmNodeAddress=<Empty>
SLOT3:/opt/goahead/tetware/opensaffire #
Note:
Able to retrieve the address through API interface or in the callback.
STEPS TO REPRODUCE:
1.Bring up opensaf with TCP as transport.
Before starting opensaf,Make the following configuration changes
a.In the file "/etc/opensaf/nid.conf"
export MDS_TRANSPORT=TCP
b.In the file "/etc/opensaf/dtmd.conf"
DTM_NODE_IP=<THE IP ADDRESS on which opensaf has to communicate>
2.Check the attributes of the node.
immlist safNode=SC-1,safCluster=myClmCluster
---
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.
------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends. Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
