Re: NISN help requested for RSA comm line

Jackie,

Wow!  Incompatible MTU sizes is a new on on me.  Congratulations on
tracking-down this weird bug in your network.

If you have any problems with the LDM, please let me know.

Regards,
Steve Emmerson
LDM Developer

------- Original Message

Date:    Wed, 15 Feb 2006 10:58:50 -0500
From:    "Petit, Jackie" <address@hidden>
To:      "Biggerstaff, Brice A9" <address@hidden>,
         "Sims, Vashon J" <address@hidden>,
         "Hoeth, Brian R. (JSC-WS8)[LM]" <address@hidden>
cc:      "Batson, Bryan" <address@hidden>,
         "Schaffert, Lowell" <address@hidden>,
         "Sautter, David" <address@hidden>,
         "Zickert, Glenn A" <address@hidden>,
         "Oram, Timothy D. (JSC-ZS8)" <address@hidden>,
         "Levitt, John S" <address@hidden>,
         "Steve Emmerson (E-mail)" <address@hidden>,
         "MEYERS, HOWARD A9" <address@hidden>
Subject: RE: NISN help requested for RSA comm line

Not sure if everyone knows yet, but the interface appears to be working
now.  Vashon's recommendation to change our MTU size on the ftp server
worked like a champ.  Apparently, on JSC side they can use ICMP messages
which tell the server that the packet size is too big and then it drops
it to the acceptable size (1500 down to 1476).  On our side, we must not
allow ICMP messages (not sure if through firewall or routers where it
doesn't allow it).  So the link would break.  With hardcoding the MTU
size, it lets it through.  In case anyone wants the Linux command, it
was "ip link set eth0 mtu 1476".

Thanks everyone for your help!!

Jackie

-----Original Message-----
From: Biggerstaff, Brice A9 
Sent: Monday, February 13, 2006 11:24 AM
To: Sims, Vashon J; Hoeth, Brian R. (JSC-WS8)[LM]
Zickert, Glenn A; Oram, Timothy D. (JSC-ZS8); Levitt, John S
Subject: RE: NISN help requested for RSA comm line


Jackie, et al,

  I will be over on-site here in a little bit and for most of the
afternoon.  If anyone needs to get in touch with me, try 281-483-2270
(which is alongside our LDM server) or ask the MIDDS operators at
281-483-1045 to check for me.

Brice   

-----Original Message-----
From: Sims, Vashon J [mailto:address@hidden] 
Sent: Monday, February 13, 2006 10:20 AM
To: Hoeth, Brian R. (JSC-WS8)[LM]
Lowell; Sautter, David; Zickert, Glenn A; Oram, Timothy D. (JSC-ZS8);
Levitt, John S
Subject: RE: NISN help requested for RSA comm line

All,
    I have opened a trouble ticket with our ENMC.  The trouble ticket
number is 547426.  They will be able to assist with troubleshooting.  I
listed Jackie as the POC.  The number to the ENMC is 256-961-4000,
remember to reference trouble ticket number 547426.  I will also provide
assistance if necessary. 

Thank you,

Vashon

-----Original Message-----
From: Hoeth, Brian R. (JSC-WS8)[LM] [mailto:address@hidden]
Sent: Friday, February 10, 2006 4:38 PM
To: Sims, Vashon J
Lowell; Sautter, David; Zickert, Glenn A; Oram, Timothy D. (JSC-ZS8);
Levitt, John S
Subject: RE: NISN help requested for RSA comm line

Vashon,

You can open the trouble ticket, but please keep us updated as to the
progress/status of the trouble ticket.

Thanks,
Brian 

-----Original Message-----
From: Sims, Vashon J [mailto:address@hidden]
Sent: Friday, February 10, 2006 1:10 PM
To: Hoeth, Brian R. (JSC-WS8)[LM]; Petit, Jackie
David; Zickert, Glenn A; Oram, Timothy D. (JSC-WS8); Levitt, John S.
(MSFC)
Subject: RE: NISN help requested for RSA comm line

All,
    I apologize, I didn't see this message previously.  Yes, you can
open a NISN trouble ticket by contacting our ENMC at (256)961-4000
referencing NISN Circuit ID KS29065 or I can open it for you.

Thank you,

Vashon Sims
Network Engineer
SAIC - NISN\UNITeS
Office (321) 867-3465
Fax    (321) 867-8220


-----Original Message-----
From: Hoeth, Brian R. (JSC-WS8)[LM] [mailto:address@hidden]
Sent: Friday, February 10, 2006 12:36 PM
To: Sims, Vashon J; Petit, Jackie
David; Zickert, Glenn A; Oram, Timothy D. (JSC-WS8)
Subject: NISN help requested for RSA comm line

Vashon,

Still haven't heard back from you?  Do we need to open a NISN trouble
ticket?

Brian Hoeth
Spaceflight Meteorology Group
Johnson Space Center
Houston, TX
281-483-3246
 

-----Original Message-----
From: ORAM, TIMOTHY D. (TIM) (JSC-ZS8) (NASA)
[mailto:address@hidden]
Sent: Monday, February 06, 2006 2:57 PM
To: Sims, Vashon J (MSFC Secondary); Petit, Jackie
Schaffert, Lowell; Sautter, David; Zickert, Glenn A
Subject: RE: 20060203: RSA Comm Test (Weather - JSC) LDM Troubleshooting
(cont.)

We connected our Linux PC with the LDM software to transfer data.
However, the failures are the same as on the HP.  
The "advantage" of the Linux PC was that the PC has only one network
card, while the HP has two.  This test should eliminate any concerns
that the dual network card was "confusing" the LDM software in some way.

At this point, I think we can rule out the workstation at JSC as the
source of the problem.  I think it is also unlikely that the LDM
configuration at CCAFS is the source of the problem either.  We can ping
the CCAFS LDM, we can see the products in the CCAFS queue using
notifyme, and the log files indicate some type of connection is
established.

I think we need someone who can look at the network traffic in detail to
help figure out what the problem is.  

Vashon is that you?  If not, can you find someone who can help Brice and
Jackie sort through this?

Thanks,
Tim

Tim Oram
Meteorologist

Your National Weather Service
.....Serving NASA's Spaceflight Program since 1960 .....and the Nation
since 1870




------- End of Original Message