Bug 688049

Summary: Add support to configure ttl multicast parameter
Product: Red Hat Enterprise Linux 6 Reporter: Fabio Massimo Di Nitto <fdinitto>
Component: luciAssignee: Ryan McCabe <rmccabe>
Status: CLOSED DUPLICATE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.1CC: agk, asalkeld, ccaulfie, cluster-maint, djansa, djoo, edamato, fdinitto, jkortus, jparsons, lhh, neil, rmccabe, rpeterso, sdake, teigland
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 684020 Environment:
Last Closed: 2011-03-17 15:55:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 633415, 640311, 684020, 684305, 684928, 684930    
Bug Blocks:    

Comment 1 Fabio Massimo Di Nitto 2011-03-16 07:23:14 UTC 
Ryan, setting ttl option is "advanced configuration" only, and should be represented/made available next to the cman/multicast address.

output should be:

<cman..>
 <multicast ttl="value"/>
</cman>

where value is between 0 and 255 included.

Note that multicast also accepts addr="".

In previous cluster version, it was mandatory to specify addr with mulicast. This restriction has been lifted in order to allow either addr or ttl or both in the syntax.

cman will do the right thing when addr or ttl are not specified.
Comment 2 Lon Hohberger 2011-03-17 14:15:21 UTC 
Is this an 'expert mode' feature or should it be normal mode?
Comment 3 Fabio Massimo Di Nitto 2011-03-17 14:22:11 UTC 
(In reply to comment #2)
> Is this an 'expert mode' feature or should it be normal mode?

expert mode IMHO.