Custom Query (1408 matches)

This ticket is tracking an issue discovered on 2014-09-23, tracking to resolution.

On 9/23/14, 2:31 PM, Luisa Nevers wrote:

I have been running OESS stitching tests and have 2 topologies that can
be created without problem, but consistently have the same links not
work. The links that do not work are consistently ones that combine AL2S
and ION paths and for those links the VLAN allocated are not found in
the AL2S router proxy.

Here is an outline of the two topologies that fail:

Topology 1: (5 node star - Missouri-IG center node)

           GPO-IG<-ION><AL2S->
                             |
        Stanford-IG<-AL2S->Missouri-IG<-AL2S->Chicago-ig
                             |
                             <-AL2S><ION->Wisconsin

      - The link between Missouri and Wisconsin does not forward traffic
      - The link between Missouri and GPO does not forward traffic
      - Repeatable across multiple slivers.

Checked Router proxy for link between GPO and Missouri and found that
hop4(*) VLAN does not exist for the path:

hop1=publicid:IDN+instageni.gpolab.bbn.com+interface+procurve2:5.24.ion.newy.ae0
(3713)
hop2=urn:publicid:IDN+ion.internet2.edu+interface+rtr.newy:ae0:bbn (3713)
hop3=urn:publicid:IDN+ion.internet2.edu+interface+rtr.kans:xe-0/0/3:al2s
(3980)
hop4=urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth15/1:*
(3980)<<<*>>>>
hop5=urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:*
(1161)
hop6=urn:publicid:IDN+instageni.rnet.missouri.edu+interface+procurve2:1.19.al2s.kans.eth5_1
(1161)


Checked Router proxy routers for link between Wisconsin and Missouri and
found that hop3(*) VLAN does not exist for path:

hop1=urn:publicid:IDN+instageni.rnet.missouri.edu+interface+procurve2:1.19.al2s.kans.eth5_1
(1162)
hop2=urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:*
(1162)
hop3=urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth15/1:*
(3914)<<*>>>
hop4=urn:publicid:IDN+ion.internet2.edu+interface+rtr.kans:xe-0/0/3:al2s  (3914)
hop5=urn:publicid:IDN+ion.internet2.edu+interface+rtr.chic:et-8/0/0:wisconsin-ig
(935)
hop6=urn:publicid:IDN+instageni.wisc.edu+interface+procurve2:1.19 (935)

The above topology is still active.


I have seen similar behavior for a 4 nodes linear topology:

   GPO-IG<-ION><AL2S->Stanford-IG<-AL2S->Missouri-IG<-AL2S><ION->NYSERNet-IG
  
      - The link between Missouri and NYSERNet does not forward traffic
      - Replacing NYSERNet-IG with Rutgers IG does not help
      - Repeatable across multiple slivers.
      - When I remove "<-AL2S->Missouri-IG" from the above, then the
entire path works.

On 9/24/14, 10:08 AM, Luisa Nevers wrote:

I also mentioned that I had a 4 nodes linear topology that consistently
has no connectivity for the Missouri to 4th node Rutgers:

     
GPO-IG<-ION><AL2S->Stanford-IG<-AL2S->Missouri-IG<-AL2S><ION->Rutgers-IG

Again in this scenario one of the expected VLAN does not exist on the
Kansas router.  I am attaching the stitching request RSpec for this
scenarios as well, just in case it can provide more clues.

Can attach RSpecs that were sent directly to Luke, if needed.

This demo is to integrate the drone technology with GENI infrastructure, especially for the WiMAX systems. The drone will serve as the mobile WiMAX client to connect the WiMAX base station, which is connected to the GENI networks. The mobile WiMAX client will then provide WiFi signals to the user on the ground. The demo will show people how to extend GENI infrastructure from ground to the air. It will also give experimenters opportunity to study the network performance with high mobility nodes. In GEC 21, we will show GENI society our drone platform, which already integrated the WiFi networks. By working with GENI teams, especially WiMAX team, we plan to provide a live demo in GEC22 with full WiMAX capacity.

List of equipment that will need AC connections (e.g. laptop, switch, monitor): 3 laptops and 2 monitors

Just put in the number of connections needed if your demo description already lists equipment.

Total number of wired network connections (sum standard IP and VLAN connections): 0 Number of wired layer 2 VLANs (if any): 0

Specify VLAN number, if known, approximate bandwidth, and whether tagged or untagged.

Number of wireless network connections (include required bandwidth if significant): 3

Number of static addresses needed (if any): 0

Monitor (y/n, specify VGA or DVI): Yes, VGA

Specify resolution only if your software has resolution restrictions.

Number of posters (max size poster boards are 30" x 40"): 1

Special requests: N/A

Include any specific network connectivity needs (e.g. VLANs to a particular GENI location, projects you'd like to be near, etc.)

Demo description paragraph (three sentence minimum):

The SDX for GENI work lead by the Georgia Tech team will be demonstrated. Updates will be provided on the implementation and deployment. Draft service requirements will be presented.

List of equipment that will need AC connections (e.g. laptop, switch, monitor):

Two laptops and one external monitor.

Just put in the number of connections needed if your demo description already lists equipment.

Total number of wired network connections (sum standard IP and VLAN connections):

Two standard DHCP ports.

Number of wired layer 2 VLANs (if any): Specify VLAN number, if known, approximate bandwidth, and whether tagged or untagged.

None

Number of wireless network connections (include required bandwidth if significant):

Wireless will be preferred for the laptops if it is available.

Number of static addresses needed (if any):

none

Monitor (y/n, specify VGA or DVI):

1 monitor - HDMI preferred, VGA okay

Specify resolution only if your software has resolution restrictions.

Number of posters (max size poster boards are 30" x 40"):

1 poster

Special requests: Include any specific network connectivity needs (e.g. VLANs to a particular GENI location, projects you'd like to be near, etc.)