Ticket #300 (closed enhancement: fixed)

Opened 5 years ago

Last modified 5 years ago

Deal with FIU/UFL stitching

Reported by: ibaldin Owned by: ckh
Priority: major Milestone:
Component: Infrastructure: Internet2 AL2S Version: baseline
Keywords: Cc: yxin, ckh, vjo

Description

AL2S is unable to stitch two sites on the same port (as in the case of FIU and UFL). Investigate if it is possible to connect UFL and FIU directly with each other via a pool of VLANs over FLR and configure two virtual interfaces on either one of them. Pathfinding should 'just work'.

Change History

Changed 5 years ago by ckh

Waiting for FIU to agree to use Vlans 1440-1449 for inter-rack connectivity between UFL and FIU

Changed 5 years ago by ckh

Done - Vlans 1440-1449 are configured within FLR between both racks. Will coordinate with Victor.

Changed 5 years ago by yxin

I need to update the RDFs for the two sites. Is the plan to redeploy them now or wait for next maintenance?

Changed 5 years ago by yxin

And do they have a static GPO mesoscale vlan(s)?

Changed 5 years ago by yxin

sorry, they do, defined in vmsite RDF. I am about to check in the updated RDFs.

Changed 5 years ago by yxin

Checked in the new RDF and tested in emulator. Need to change vlan policy in config.xml in both site to :

<controls>

<control type="fiuNet.vlan" class="orca.plugins.ben.control.NdlInterfaceVLANControl" />

</controls>

Changed 5 years ago by yxin

  • cc vjo added

cc vjo.

Changed 5 years ago by vjo

Requested changes have been made to config.xml and to RDF at FIU and UFL.
A dumbbell topology between the two looks outwardly OK (all reservations active, VLAN chosen at both ends the same), but no packets are passed.

Presuming this needs to be debugged at the FLR level.

Changed 5 years ago by ibaldin

Email out to Chris Griffin to verify continuity

Changed 5 years ago by ibaldin

Physically works. Chris suspects NDL needs to be fixed. Port 64 is not in FIU flowvisor flowspace, however has all 20 10G ports.

Changed 5 years ago by ibaldin

UFL, not FIU.

Changed 5 years ago by yxin

that's right, port 64 was missed. I already checked in the fixed RDF.

Changed 5 years ago by ibaldin

Reported as working. Chris will test slices.

Changed 5 years ago by ckh

Can't ping from FIU to UFL. UFL is missing port 64 from it's flowspace.

[root@ufl-hn ~]# /opt/flowvisor/bin/fvctl --passwd-file=/etc/flowvisor.passwd listFlowSpace | grep 1440
rule 6: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=49,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863616],priority=[0],]
rule 7: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=48,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863614],priority=[0],]
rule 8: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=45,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863612],priority=[0],]
rule 9: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=44,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863610],priority=[0],]
rule 10: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=47,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863608],priority=[0],]
rule 11: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=19,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863606],priority=[0],]
rule 12: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=46,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863604],priority=[0],]
rule 13: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=17,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863602],priority=[0],]
rule 14: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=22,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863600],priority=[0],]
rule 15: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=18,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863598],priority=[0],]
rule 16: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=23,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863596],priority=[0],]
rule 17: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=24,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863594],priority=[0],]
rule 18: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=25,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863592],priority=[0],]
rule 19: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=26,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863590],priority=[0],]
rule 20: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=21,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863588],priority=[0],]
rule 21: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=20,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863586],priority=[0],]
rule 22: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=43,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863584],priority=[0],]
rule 23: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=42,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863582],priority=[0],]
rule 24: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=41,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863580],priority=[0],]
rule 25: FlowEntry?[dpid=[all_dpids],ruleMatch=[OFMatch[in_port=50,dl_vlan=0x5a0]],actionsList=[Slice:orca-1440=4],id=[-1217863578],priority=[0],]
[root@ufl-hn ~]#

Changed 5 years ago by vjo

Oy. Right. We need to take a maintenance for UFL, to update the NDL.

Shall I schedule it in the next couple of days?

Changed 5 years ago by ibaldin

Yes.

Changed 5 years ago by vjo

Maintenance announcement sent; will do this at 1 PM tomorrow.

Changed 5 years ago by vjo

Chris,

Maintenance will happen in a little over 45 minutes, to take care of UFL.
I have already updated the NDL; all that I have to do is clear out the site, un-claim it, restart it, and claim it.

What do I need to do to verify correctness?
I *presume* it's as simple as "set up a VM<->VM dumbbell between FIU and UFL, see if you can ping between." If it's anything more than that, please let me know.

After I re-claim, I will perform whatever steps are needed to verify, before I re-open UFL.

Presuming a successful verification, I will re-open UFL, and close this ticket.

Changed 5 years ago by vjo

Awaiting response; rack cleaned up.
Am proceeding w/ proposed VM<->VM dumbbell test.

Changed 5 years ago by vjo

I am able to ping across a UFL<->FIU VM dumbbell.
Is there anything further I need to do to test, before I open up UFL and declare this maintenance to be complete?

I will wait until 1:30; if I don't hear anything, I will proceed with opening things up.

Changed 5 years ago by vjo

While waiting, I tested a UFL<->FIU bare metal dumbbell.
This too passes packets.

I am opening up the testbed, in the absence of further guidance.

Changed 5 years ago by vjo

  • status changed from new to closed
  • resolution set to fixed

UFL back online, maintenance completion notification sent.
I am closing this ticket. If this issue is found to have not been resolved, please re-open.

Changed 5 years ago by ckh

Victor, I was PTO at the end of last week. Sorry for not replying. It looks good to me, too. I'm able to create three UFL-FIU dumbbell slices; all of which are ping-able. They include two VMs and one bare metal.

Note: See TracTickets for help on using tickets.