[AG-TECH] running AG on DREN?

Richard Lopez richard.lopez at nara.gov
Wed Jul 8 06:12:25 CDT 2009


Hi,
 
Does anyone in the AG community have any experience with running an
Access Grid node on the Defense Research Engineering Network (DREN) in
unicast mode? DREN seems to block a lot of ports even though it peers
with other networks. 
 
 I have 3 AG nodes, 2 connected to Internet 2 and 1 connected to DREN
and the DREN node only works some of the time. I am  running in unicast
mode and I believe DREN blocks port 20000 which is the default port for
the bridge servers. If this is the case it prevents me from using most
of the available bridges since they tend to use 20000?.  I was wondering
if that is why the Argonne bridge uses port 8030?  I was also wondering
when the bridge list is built how does it determine the closest bridge?
I consistently show the AGSC bridge, using port 1992  as being the
closest to my AG DREN node in West Virginia which is odd since AGSC is
in England I believe. However when I can get the node to work it is
usually through the AGSC bridge, sometimes using Argonne but not
consistently. 
 
I have also tried running in debug mode but for some reason no log
files are being generated even though they are set to debug mode and
point to a directory (Windows XP is my platform). However I could
capture the following from the debug window on a session that didn't
work:
 
06/29/09 14:33:52 3332 JabberClient     jabberclient.py:151 DEBUG
national-archi
ves-and-records-administration-(nara)(vv3.mcs.anl. at conference.mcs.anl.go:
This r
oom supports the MUC protocol.
06/29/09 14:33:52 3332 JabberClient     jabberclient.py:151 DEBUG
national-archi
ves-and-records-administration-(nara)(vv3.mcs.anl. at conference.mcs.anl.go:
NARA -
  West Virginia has joined this session
06/29/09 14:34:25 3640 VenueClient     venueclient.py:593 DEBUG Calling
Heartbea
t, time now: 1246300465
06/29/09 14:34:25 3640 VenueClient     venueclient.py:617 DEBUG Next
Heartbeat n
eeded within 36s
06/29/09 14:34:25 3640 VenueClient     venueclient.py:627 DEBUG
heartBeatCounter
 = 2
06/29/09 14:35:01 3456 VenueClient     venueclient.py:593 DEBUG Calling
Heartbeat, time now: 1246300501
06/29/09 14:35:04 3456 VenueClient     venueclient.py:617 DEBUG Next
Heartbeat needed within 36s
06/29/09 14:35:04 3456 VenueClient     venueclient.py:627 DEBUG
heartBeatCounter = 3
06/29/09 14:35:38 3332 bajjer.io     io.py:167 DEBUG RECV:
 
06/29/09 14:35:40 3956 VenueClient     venueclient.py:593 DEBUG Calling
Heartbeat, time now: 1246300540
06/29/09 14:35:40 3956 VenueClient     venueclient.py:617 DEBUG Next
Heartbeat needed within 36s
06/29/09 14:35:40 3956 VenueClient     venueclient.py:627 DEBUG
heartBeatCounter = 4
06/29/09 14:36:16 3908 VenueClient     venueclient.py:593 DEBUG Calling
Heartbeat, time now: 1246300576
06/29/09 14:36:17 3908 VenueClient     venueclient.py:617 DEBUG Next
Heartbeat needed within 36s
06/29/09 14:36:17 3908 VenueClient     venueclient.py:627 DEBUG
heartBeatCounter = 5
06/29/09 14:36:39 3332 bajjer.io     io.py:167 DEBUG RECV:
 
06/29/09 14:36:53 3292 VenueClient     venueclient.py:593 DEBUG Calling
Heartbeat, time now: 1246300613
06/29/09 14:36:53 3292 VenueClient     venueclient.py:617 DEBUG Next
Heartbeat needed within 36s
06/29/09 14:36:53 3292 VenueClient     venueclient.py:627 DEBUG
heartBeatCounter = 6
06/29/09 14:37:29 3372 VenueClient     venueclient.py:593 DEBUG Calling
Heartbeat, time now: 1246300649
06/29/09 14:37:29 3372 VenueClient     venueclient.py:617 DEBUG Next
Heartbeat needed within 36s
06/29/09 14:37:29 3372 VenueClient     venueclient.py:627 DEBUG
heartBeatCounter = 7
06/29/09 14:37:41 3332 bajjer.io     io.py:167 DEBUG RECV:
 
06/29/09 14:38:05 3816 VenueClient     venueclient.py:593 DEBUG Calling
Heartbeat, time now: 1246300685
06/29/09 14:38:05 3816 VenueClient     venueclient.py:617 DEBUG Next
Heartbeat needed within 36s
06/29/09 14:38:05 3816 VenueClient     venueclient.py:627 DEBUG
heartBeatCounter = 8
06/29/09 14:38:41 2636 VenueClient     venueclient.py:593 DEBUG Calling
Heartbeat, time now: 1246300721
06/29/09 14:38:41 2636 VenueClient     venueclient.py:617 DEBUG Next
Heartbeat needed within 36s
06/29/09 14:38:41 2636 VenueClient     venueclient.py:627 DEBUG
heartBeatCounter = 9
06/29/09 14:38:42 3332 bajjer.io     io.py:167 DEBUG RECV:

 
 
Is there any documentation that explains how the process works of
connecting to a bridge server? I can see the various handshakes and then
eventually joining an IGMP group and then you see the UDP video traffic
(from a good session using windump).
 
I should also note that this is not a new problem. Running the AG node
in WV on DREN has never worked consistently since the install but we are
to the point where we would really like to use it to connect to other
nodes and I would like to see if I can get this solved. I am unable to
have multicast enabled on this router for various reasons unfortunately
so I'm stuck with getting it to work via unicast
 
 
Thanks for insight anyone might have.
 
Rick Lopez
National Archives (NARA)
College Park,MD

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20090708/9fc7ac4d/attachment.htm>


More information about the ag-tech mailing list