Opened 9 years ago

Closed 9 years ago

#96 closed (fixed)

Northwestern is missing a campus connection (port 23 on vlan 10)

Reported by: lnevers@bbn.com Owned by: somebody
Priority: major Milestone:
Component: Experiment Version: SPIRAL5
Keywords: confirmation tests Cc: jim-chen@northwestern.edu
Dependencies:

Description

As part of the InstaGENI Confirmation testing there is a check to verify that a campus resources connection is configured for the rack being verified. The Northwestern rack does not have a port configured for a campus network.

Current procurve1 config:

vlan 10 
   name "control-hardware" 
   ip address 10.1.1.253 255.255.255.0 

Expected procurve1 config:

vlan 10 
   name "control-hardware" 
   untagged 23 
   ip address 10.1.1.253 255.255.255.0 

Change History (5)

comment:1 Changed 9 years ago by lnevers@bbn.com

On 2/19/13 12:43 PM, Leigh Stoller wrote:

 First, when I log into procurve1 and do a show config, I get:

 vlan 11 
    name "control-alternate" 
    untagged 24 
    ip address 10.2.1.253 255.255.255.0 
    exit 
 vlan 10 
    name "control-hardware" 
    untagged 23 
    ip address 10.1.1.253 255.255.255.0 
    exit 

 Second, the above vlans are not the campus connection; the above vlans are
 how boss talks to the switches themselves, to control them with snmp.

 For procurve1, the campus connection is really just the link to the public
 internet and that comes in on port 26 I think, and is in vlan 1 (DEFAULT).
 There is no special config for this.

 For procurve2, the campus connection is variable, and in the case of
 northwestern, it has not been defined yet. The site survey says:
 "Links to StarLight/ION/NLR on port 23 will be added on phase 3
 vlans TBD". So nothing can be done until these details are filled in.

I had expected the same VLAN configuration for the 10.1.X addresses, but since both are configured, not a problem, will expect this for next comparison.

About the second point:

I do not have a definition of the networks addresses and how they are used in the rack, is there such a page?

For procurve1, I do not see a port 26 for the public internet connection, is it port 24?

For procurve2, I will assume port 23 and report if otherwise.

comment:2 Changed 9 years ago by lnevers@bbn.com

Capturing email:

On 2/19/13 12:58 PM, Heidi Picher Dempsey wrote:

 I haven't see the survey, and I don't know what Phase 3 is, but we are expecting a 
campus connection to something at Starlight as part of the initial deployment.  This
should be true for every InstaGENI rack.  (I pointed this out in my earlier email 
about the Northwestern Aggregate Info page too, but got no response.)  Is there an 
issue with getting a local Starlight dataplane connection to the rack?

comment:3 Changed 9 years ago by lnevers@bbn.com

Capturing email:

On 2/19/13 1:22 PM, Jim Hao Chen wrote:

This should be true for every InstaGENI rack.

maybe this should be on the site survey if this is the case.

(I pointed this out in my earlier email about the Northwestern >Aggregate Info page too, but got no response.)

I have been working with Tim & Luisa & send update info on the Aggregate pages, sorry did not response to you directly.

we do have a link on procurve2 port 23 to a uplink switch, for your testing purpose.

I see that the Northwestern OpenFlow Aggregate page was updated to show port 23 to iCAIR-Arista 3792. Are there some resources on the Campus connection that I can connect to?

comment:4 Changed 9 years ago by lnevers@bbn.com

Please ignore request to connect to campus resources, this is beyond the scope of confirmation testing. Tests simply verify the existence of the connection, but do not use it.

comment:5 Changed 9 years ago by lnevers@bbn.com

Resolution: fixed
Status: newclosed

This ticket should have been closed in February and is beyond the scope of the confirmation tests.

Note: See TracTickets for help on using tickets.