Vishal Soni-G20083 wrote:
> Hello Matt,
>  
> node_id file is populated by file nid_tipc.sh (not TIPC), using content 
> of two files chassis_id and slot_id.

In a real system (PC cluster), these two files probably has to be auto 
generated. E.g. using the last byte of the IP address for a certain network 
interface.

Thanks,
Hans

>  
> This is the exact line where it is done
> printf "00%02x%02x0f\n" $CHASSIS_ID $SLOT_ID > /var/opt/opensaf/node_id
>  
> And in INSTALL file of OpenSAF code has descripton of SLOT_ID, we could 
> have elaborated a bit more for better understanding.
>  
> Your understanding of populating of  node_id file is fine.
>  
> PS: Node id we configure for TIPC is extracted from node_id file. For 
> more information on how we configure TIPC node id (using tipc-config) 
> refer to nid_tipc.sh.
>  
> Regards,
> Vishal Soni.
>  
> 
>     ------------------------------------------------------------------------
>     *From:* [EMAIL PROTECTED]
>     [mailto:[EMAIL PROTECTED] *On Behalf Of *Schoen
>     Matthew-MSCHOEN1
>     *Sent:* Thursday, February 28, 2008 9:15 AM
>     *To:* [email protected]
>     *Subject:* [Users] node_id question
> 
>     All,
>     I have a quick question regarding the node_id file in
>     /etc/opt/opensaf. I see the distribution comes with node_id file
>     with a value of 1. I couldn't find any reference to node_id in the
>     openSAF documentation....maybe I missed it. Anyways, I did a web
>     search to see if I could find anything on this file and found a page
>     that indicated that TIPC will actually populate the file based on
>     the data in the slot_id file. Is this the case? If it is, does TIPC
>     automatically populate the node_id file using the HPI Entity path
>     format? Ex. If we are talking about slot_id of 3 then the data in
>     the node_id file will contain 0x0002030f? Is this correct? Any
>     information is greatly appreciated.
>     -Matt
> 
> 
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Users mailing list
> [email protected]
> http://list.opensaf.org/maillist/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://list.opensaf.org/maillist/listinfo/users

Reply via email to