[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #BIG-900661]: Terminated obsolete upstream

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #BIG-900661]: Terminated obsolete upstream
  • Date: Thu, 12 Jun 2014 14:22:40 -0600
Brice,

Is each direct-connect client only making one REQUEST to each upstream LDM?

> "Able was I ere I saw Elba."  ... indeed.
> 
> The 'direct-connect' hosts are behind a firewall but as the log shows, they 
> connect with those different addresses, .152 and .153.  That's why I'm 
> confused.  I was able (since I'm not on Elba... at the moment, anyway) to 
> look at the configuration on one of the clients and it was using the default 
> pattern to each server.  But as I understand it those should have been 
> treated differently.  ?
> 
> I have asked Richard to change his patterns to the following -
> 
> On Sun –
> 
> Request  FT4  “^(MSFC-Sun|WT|LR|LW|PT|PS|MS|UF|JS|HR)”    134.xxx.xxx.AAA
> Request  FT4  “^(MSFC-Sun|WT|LR|LW|PT|PS|MS|UF|JS|HR)”    134.xxx.xxx.BBB
> 
> On Moon –
> 
> Request  FT4  “^(MSFC-Moon|WT|LR|LW|PT|PS|MS|UF|JS|HR)”    134.xxx.xxx.AAA
> Request  FT4  “^(MSFC-Moon|WT|LR|LW|PT|PS|MS|UF|JS|HR)”    134.xxx.xxx.BBB
> 
> 
> which I think should make the patterns sufficiently different and will give 
> me the hook for the other customers so I don't have to keep inventing new 
> patterns.
> 
> I'll let you know what comes up.
> 
> Brice

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: BIG-900661
Department: Support LDM
Priority: Normal
Status: Closed