[AG-TECH] One-page summary of AG port usage -- please help us complete it

Mon Feb 13 13:51:43 CST 2006

Clever, thanks for sharing -- it would be a great service if you could find
the time to write up detailed instructions for this process.

Cheers, Rick Rodgers

> From: "Adam Taylor" <accessgrid at ulm.edu>
> To: <ag-tech at mcs.anl.gov>
> Subject: RE: [AG-TECH] One-page summary of AG port usage -- please help us  
complete it
> Date: Mon, 13 Feb 2006 12:58:34 -0600
> 
> Just my two cents...
> 
> Just to let you know what we have done here on our campus.  We have two
> ports on our border router.  One goes into our firewall boxes and then our
> main campus network.  The other bypasses our firewall and trunks (802.1Q)
> across our campus's vlan structure.  So it is isolated from the main campus
> network as far as interacting, but allows up to drop a non-firewalled port
> (one single port or more) to whatever building we need to use the grid
> software.  And the best thing is that it takes all of 5 min to drop an AG
> friendly (fully multicast) port anywhere on our campus.  This is something
> that should be easily set up in any modern network.
> 
> This some 30,000 port problem is what made us figure out this way of doing
> it.  Our firewall guy looked at us funny when we told him the port range we
> needed.  He is a stickler and even he liked this solution we came up with.
> 
> Sorry if this doesn't exactly fit in this thread but I understand the
> problem and thought my experience might help.
> 
> Adam Taylor
> Computing Center
> University of Louisiana at Monroe
> 
> 
> 
> -----Original Message-----
> From: owner-ag-tech at mcs.anl.gov [mailto:owner-ag-tech at mcs.anl.gov] On Behalf
> Of R. P. Channing ["Rick"] Rodgers
> Sent: Friday, February 10, 2006 3:56 PM
> To: ag-tech at mcs.anl.gov
> Cc: rodgers at nlm.nih.gov; Zsolt-Nagykaldi at ouhsc.edu
> Subject: RE: [AG-TECH] One-page summary of AG port usage -- please help us
> complete it
> 
> Exactly!  :)
> 
> Actually, the problem you raise in a humorous way is why I put out the list,
> and the call for help in completing it.  I am in *exactly* the same
> situation
> you are in, trying to set up an AG cluster in a medical facility (UCSF)
> where
> I have collaborators.  It has been stalled for MONTHS now, because the
> local administrators run a very restrictive setup, and we have not been
> able to give them a clear, concise list of what ports have to be opened.
> It's been very frustrating, and has brought our collaboration to a halt.
> If I didn't have so many other pulls on my time, I'd sit down and read the
> source code for vic, rat, and the AG framework to try to figure out what
> ports are being used, but that seems ridiculous when I know that some active
> developer could probably do that in minutes (as opposed to my hours).
> I pray that someone will do just that, it would be a terrific service to the
> entire AG community!
> 
> Best Regards, Rick Rodgers
> 
> > Subject: RE: [AG-TECH] One-page summary of AG port usage -- please help us
> 
> complete it
> > Date: Fri, 10 Feb 2006 15:02:54 -0600
> > From: "Nagykaldi, Zsolt F. (HSC)" <Zsolt-Nagykaldi at ouhsc.edu>
> > To: <ag-tech at mcs.anl.gov>
> > 
> >  
> > Thanks for the list again. So you mean, if we open 30,000 ports in a
> medical 
> school's network we should not have any problem? :))
> >  
> >  
> > Zsolt
> >  
> >  
> > _ _ _
> >  
> > Zsolt Nagykaldi, PhD
> > Research Associate, Clinical IT Specialist
> > University Of Oklahoma Health Sciences Center
> > Department Of Family And Preventive Medicine
> > Oklahoma Center For Family Medicine Research
> >  
> > 900 NE 10th Street
> > Oklahoma City, OK 73104
> > Phone: (405) 271-8000 Ext.:1-32212
> > Fax:     (405) 271-1682
> > 
> > ________________________________
> > 
> > From: owner-ag-tech at mcs.anl.gov on behalf of R. P. Channing ["Rick"]
> Rodgers
> > Sent: Fri 2/10/2006 2:21 PM
> > To: ag-tech at mcs.anl.gov
> > Cc: rodgers at nlm.nih.gov; bernholdtde at ornl.gov; jsummers at bachman.cs.ou.edu;
> 
> terrazas at labmed2.ucsf.edu
> > Subject: [AG-TECH] One-page summary of AG port usage -- please help us 
> complete it
> > 
> > 
> > 
> > Dear AG Colleagues,
> > 
> > I now realize that the work I started last December, trying to create a
> > one-page summary of AG port usage (based on the commendable document
> created 
> by
> > Javier Gomez Alonso of the Access Grid Support Centre at the University
> > of Manchester) is not easily locatable in the list archives.  I resend it,
> > attached, along with the Excel version that David E. Bernholdt of ORNL
> kindly
> > created.  As I said earlier, all of these documents are missing some
> > key information, such as the port ranges used by vic and rat.  I send this
> out
> > again in the hope that another AG colleague will pick it up and complete
> it.
> > We all really need to have something like this, and i would hope that 
> eventually
> > it would end up on the AG web site(s), and be maintained to reflect any
> > coding changes/additions made to AG software.
> > 
> > Best Regards, Rick Rodgers
> > 
> > 
> ----------------------------------------------------------------------------
> ----
> > R. P. C. Rodgers, M.D. * rodgers at nlm.nih.gov * (301)435-3267 (voice, fax)
> > OHPCC, LHNCBC, U.S. National Library of Medicine, NIH
> > Bldg 38, Rm. B1N-30F2, 8600 Rockville Pike, Bethesda MD 20894 USA
> > http://lhc.nlm.nih.gov/staff/rodgers/rodgers.html
> > 
> > 
> 
> ----------------------------------------------------------------------------
> ----
> R. P. C. Rodgers, M.D. * rodgers at nlm.nih.gov * (301)435-3267 (voice, fax)
> OHPCC, LHNCBC, U.S. National Library of Medicine, NIH
> Bldg 38, Rm. B1N-30F2, 8600 Rockville Pike, Bethesda MD 20894 USA
> http://lhc.nlm.nih.gov/staff/rodgers/rodgers.html
> 

--------------------------------------------------------------------------------
R. P. C. Rodgers, M.D. * rodgers at nlm.nih.gov * (301)435-3267 (voice, fax)
OHPCC, LHNCBC, U.S. National Library of Medicine, NIH
Bldg 38, Rm. B1N-30F2, 8600 Rockville Pike, Bethesda MD 20894 USA
http://lhc.nlm.nih.gov/staff/rodgers/rodgers.html