Multicasting questions

[skhs]

Hi I would like to request some help in clarifying couple of questions in regards to SWD. 

1. If a multicast sessions is in process for a while, would the new computer coming online needing and requesting package will join that session or start a new session. 

2. if  computer A,  in a site already downloaded a pacakge and new machines need would that Comptuer A , provide that package or new computer will start a new session with Package server. 

 

I would really apreciate help as docmentation was not very clear on it. 

 

Thanks

 

[Migration User]

Hi,

1. If session has been started then new computer will waiting untill a new session will be initiated. In new session it will be joined along with computers that was not added into previouse session.
2. If some computer has already downloaded the package, he can multicast it and can be  the master of the session.

Regards,
Dmitri
 

[skhs]

Thank you Dmitri, so if the some computers in a site have the package why would they join the multicast session or how can I make them to join the session so the package does not download from the SMP again. 

This seems like in multicast if any computer in the site have a package will act like a PS to provide the pacakge to other computers?

 

Appreciate if you can clarify please. 

[Migration User]

Hi skhs,

1. Computer Connection to multicast session depends on next parameters:

a. "Allow Symantec Management Agents to use multicast for downloading package" setting should be enabled in "Targeted Agent Settings"

b. "Wait time to begin session"  is set tot "Minutes" or "% of Configuration Request"

c. "Wait time to begin session" value.

d. "Minimum receiving computers per session" value.

Multicasting works by next algorithm:

1. All computers with enabled multicasting received request on needed package

2. From computers who respond on this request will be selected most faster (less ping from all other peers), package downloading will be initiated from this computer

3. If package is not exist on any client computer, few computers will download it from NS server, and after that another clients will download this package from computer who download them from NS

 

Answering on your last question: yes, Multicasting will reduce loading on NS.

Regards,
Dmitri

[Migration User]

Any comments on the best settings for this scenario?
Single package server in main office - all remote offices connect to main office via LAN-to-LAN
Bandwidth at main office is currently 5M but will be 15 in a week or so.
We have 34 remote offices - they range in size from 2 computers to about 18 computers.
We have 350 managed computers in the field.
Currently I find even a single update can saturate the pipe here.

I am unsure what the best multicast settings could be, or what a couple of the settings even mean or do.

I know "allow" should be set, what about the "by default, the SMA should use multicase........." ? It would seem to make sense to do so.

Max master sessions per computer - I assume this means the most sessions any given computer which already had a package can be the master of at a given time - to control the load on that computer and its network connection in that office?

Minimum receiving computers - gee, I see no problem with 1 - but then, there may be reasons to have that set higher, but if an office has 2 computers, why should each fill the line back to the main office when 1 can download it and the second computer in that office can get it from that one, so 1 would be needed there.

Wait time to begin session - what are the implications of a higher or lower wait time? 20 minutes? Less? More? What is the impact of 10 instead of 20, or 30 instead of 20?

Number of receiving computers required to begin session before wait time has expired - does this imply that if it is set at 3 and 3 computers are wanting to receive, the session could start? Does that mean if it's set at 3 and only 2 computers are wanting that package, then they can receive it once that wait time expires?
So if the wait time was 20 minutes and the number of receiving computers required to begin session before wait time has expired is set to 3, then if 2 join and the wait time has expired, a session will start but if 3 or more join, then the wait time won't matter, a session will start?

Is it implying that EITHER 3 computers are needed to join OR 20 minutes has to pass, and if either is true, then it happens?
 

If this were VBScript, it might look similar to this - in this case with these settings,
wait time to begin session = 20
number of receiving computers required to begin session before wait time has expired = 3

Set wait time = 21
Set receiving computers = 2
If wait time is equal to or greater than 20 OR if receiving computers is equal to or greater than 3, then start session

It would start
OR
Set wait time = 19
Set receiving computers = 3
If wait time is equal to or greater than 20 OR if receiving computers is equal to or greater than 3, then start session

It would start in this case, too.
Is that correct?

[Migration User]

Hi ShadowsPapa,

If you want to reduce traffic between offices, you should raise all parameters.
1.    Wait time to begin session -  bigger value – bigger number of computers will connect to the session.
2.    Number of receiving computers required to begin session before – if set 1-2 will be started small sessions (will not wait till time period will be ended)
3.    Minimum receiving computers per session 1 – better to leave as is, because if package needed only to one client, it cannot receive it if value will be greater than one.
4.    For big offices you can add some additional Package Servers.
5.    Also you can set throttling period.

 

Your scrips are correct.

Regards,
Dmitri