[Robbie Parker]

My project’s interface resource for vendor =Allscripts took this on for me and worked it out with their native engine, so I don’t have the immediate need, but if anyone has a template for this scenario any advice would be helpful for future considerations.  Thanks, -robbie

[Robbie Parker]

Hey-  looking forward to following this thread as I too am getting ready to have to pass 270/271s through our engine.   -robbie

[Robbie Parker]

Daniel-

Nice work here and I for one would greatly enjoy seeing any documentation you would be able to present.

[Robbie Parker]

Thanks Eric. I haven’t examined this yet, but sounds like exactly what I needed…’something’ to be able to trigger on to perform a process restart to be in front of a winsock error.

-Robb ie

[Robbie Parker]

Cycling the owning process pre 8am to force CL to close the socket has done the trick here.  I have had successful, timely transfers for 7 business days at this time.

Thanks again for the assistance.

[Robbie Parker]

Thanks Guys!

[Robbie Parker]

Yesterday, I changed the thread from server to multiserver and set to “2” and immediately caused thread errors, so I removed that.

Thinking along the same lines that Athena, or Firewall, or VShell has broken connection, but CL thread still thinks connected that Rob mentioned, I scripted cycling the process owning the thread in question today at 7am and 7:30am.

I was hoping then this would make sure all parties then aware ‘pipe broken, rebuild’- it seemed to work today.  Pre 8am msgs were delivered in an appropriate timeframe.

I hope this continues to be the case over the next few days.

Even though the exact reason is unknown to me, this simple, acceptable work around will do what I need if indeed it keeps giving good results.

I thank Rob and Robert for their feedback.  Cheers!

[Robbie Parker]

Rob,

I really appreciate your assistance here.  I think you may be correct regarding the firewall.

I captured packets from SSH box and Cloverleaf box this morning, though have yet to compare side by side..

I did run netstat at 7:54am and 7:59am and the connection is ESTABLISHED on the port / thread in question (thread status=Up at this time as well).  The interesting part is at 8:02, I saw the ib Athena thread go from Up to Opening, then Up.  At that time that the connection is made for delivery from SSH box, and data is passed…  

Is the multiserver option a quick fix from the cloverleaf side and somewhat normal protocol for troublesome threads or if it were you would you prod the Firewall chief?  🙂

Thanks again.

[Robbie Parker]

We are running 5.6Rev2 on Windows 2003.

..having now acquired Wireshark user status  🙂

I had Wireshark capture from 7am to 8:30am today.  I have matched the timestamp from the VShell log of:

07:48:16,fwd ,00007: Port forwarding connection to :9960 failed.  Winsock error: The remote system refused the connection.  This probably means that the remote system does not provide the service you are attempting to access, or that the service is being provided on a different port.

with the SSH to Clovereleaf comm packets in the capture, and I see the SYN and RST,ACK:

from VShell to Cloverleaf>

No.     Time        Source                Destination           Protocol Info

   434 3093.046911                     TCP      altav-remmgt > 9960 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 SACK_PERM=1

from Cloverleaf to VShell>

No.     Time        Source                Destination           Protocol Info

   435 3093.047678                     TCP      9960 > altav-remmgt [RST, ACK] Seq=4029370377 Ack=1 Win=0 Len=0

---

this is what Rob mentioned to look for and that the RST means Cloverleaf is not listening…but it is (???)

---

At 8:02:15 (time when the first connection is made and data delivered the entries are:

from VShell to Cloverleaf>

No.     Time        Source                Destination           Protocol Info

   849 3931.962964                     TCP      direcpc-si > 9960 [PSH, ACK] Seq=4506 Ack=769 Win=64767 Len=573

from Cloverleaf to VShell>

No.     Time        Source                Destination           Protocol Info

   850 3931.971360                     TCP      9960 > direcpc-si [PSH, ACK] Seq=769 Ack=5079 Win=32768 Len=96

---

After this point, connection is good throughout the day.  I guess my question now is, is there something on Cloverleaf I can change, or do I have enough info to ‘engage the vendor with a slight lean toward “what the heck are you doing at 8:02am that you are not doing before then?” ‘

Think the direcpc-si and the altav-remmgt are Athenahealth hostnames and that may have something to do with it?

I enjoy the logic/coding portion of this job- not the networking 🙂

[Robbie Parker]

Thanks Rob.  Netadmin claims he is doing nothing but I will get him to confirm again.

Say there is no firewall limitations occurring, would there be a next step of troubleshooting.

Netadmins are ornery people here 🙂

[Robbie Parker]

Jim,

My experience with Picis is that they are a stubborn grouchy vendor…

While implementation Lawson suite, they even tried to tell our Materials dept how they should classify items in our organization to make it easier on the OR Staff and Picis…nevermind the materials staff and the other systems dependant on item master information.  And this came unsolicited simply from me contractually having to tell them the data is now coming from Lawson-  nothing changing, you will see no difference, just let it be known data is now coming from Lawson, and they got on this high horse about how items should be classified outside of their app.

[Robbie Parker]

Jim,

Are you referring to Lawson->MFN->Picis or Picis->MFN->Lawson ?

[Robbie Parker]

…of course mine goes the other way.  Just noticed that 🙂

[Robbie Parker]

We have an interface from Lawson to PicisOR Mgr to add/update item master in Picis.  

This consists of sql .csv output from Lawson, normalized to HL7 via tcl, then translated via xlate to FRL for Picis.  

I normalized to HL7 b/c we had an HL7-to-xlate-to-FRL to Picis established from another vendor…so that was the quickest solution while trying to do other interfaces while implementing Lawson.

[Robbie Parker]

Yes, I learned that the hard way when serverAdmins moved one of the HA cluster blades to a new blade chassis.   Failover failed, b/c license invalid on that new host with new blade chassis-NIC block, or whatever it is called.

🙂

[Author]

Replies