[LDM #EEM-529083]: proper config of ldmd.conf

Roger,

I recommend that for each stream of data that you want, you have two REQUEST 
entries -- each to a different upstream LDM. The requests should be for 
*exactly* the same data so as not confuse the LDM. The first such entry will 
start in primary mode and the second will start in alternate mode. They might 
switch, however, and will switch if the alternate mode connection is better.

The cost of having two identical requests is negligible.

You should count the request to your dish's LDM as one of the requests -- so 
either request from the dish's LDM and another site or request from two other 
sites (if the dish is offline).

I hope this helps.

> Full Name: Rodger R. Getz
> Email Address: address@hidden
> Organization: AWIS Weather Services
> Package Version:
> Operating System:
> Hardware:
> Description of problem:
> 
> We use a PDI NOAAPort system to feed our LDM. Last weekend the coax
> from our dish was damaged by a contractor. Fortunately, we were able
> to repair it and plan to replace it with new coax. We've arranged with
> several sites to obtain temporary IDD feeds while the dish is offline for
> repairs. Since we haven't used IDD feeds in many years, I'm not familiar
> with how it now works with multiple request entries. Reading the docs
> it appears that the first request will be the primary one and any other
> requests will not be active unless the primary is unavailable. Is there
> any "costs" for having multiple requests? Do the alternate requests
> use any bandwidth or system resources? When our dish is online, would
> there be any similar costs to having the IDD requests active or should
> we comment out the IDD requests when feeding from the dish?
> 
> As always, thanks for all you do!


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: EEM-529083
Department: Support LDM
Priority: Normal
Status: Closed