[AusNOG] L3 vlan tunneling

Mon May 27 18:41:22 EST 2013

Cheers everybody for your responses,

Andrew I will definitely look at VXLAN, I had not heard of it (not generally a VMware guy specifically) and my mind is a little blown with what I'm reading :)

James, the thought of using a few ASRs to do OTV had occurred to me, the only issue is I would effectively require 4 for redundancy (2 at each end, peering with the other 2 at the other) that would (at least initially) be doing very little else so that may end out being expensive, I'll check it out but it may need to be a slightly bigger model, this is all 10gig connected and from what I have seen the ASR1001 has a max of 5gbps.

Tom, the links are vlans / SVI's with routing running on them, they are all our equipment so turning on LDP is not a drama assuming its all supported on the 6500's / interconnecting gear. There is a few devices between them on a few of the redundant links, the two DC core routers are Direct connect on the primary path but the redundant links cross multiple hops to get there.

I believe (and I would need to check) that the most major of those redundant links would be fine with LDP (4500-X) but I'll confirm.

Either way, I have three decent plans to go with :)

Thanks again, its much appreciated!

Cheers,
Ayden

________________________________
From: Andrew Thrift [andrew at networklabs.co.nz]
Sent: Monday, 27 May 2013 6:01 PM
To: Beeson, Ayden
Subject: Re: [AusNOG] L3 vlan tunneling

Hi Ayden,

Have you considered using VXLAN on VMWare to connect your two locations ?   This will basically give you a single dvSwitch accross both sites (or multiples if you so desire) and is done at the host level removing the requirement for any complex configuration on your Cisco switches.

Regards,

Andrew

On 5/27/2013 7:31 PM, Beeson, Ayden wrote:
Hey Noggers,

I have a problem and I’m hoping one of you can offer some advice to help me out here.

We currently have 2 main datacentres, one in Wagga and one in Bathurst. They are currently connected using (mostly) 6500’s running L3 code with the L3 links generally consisting of L3 vlans.

Most of them are P2P L3 vlans but as we have VMware / UCS gear in both Bathurst and Wagga Wagga we now have “stretched vlans” which go between Wagga Wagga and Bathurst at L2 for vMotion etc.

We are currently in the processes of a network redesign ahead of a new equipment purchase and we want to remove the L2 vlans from the routed interfaces and get back to a clean routed core model.

So, onto the meat of the question, what technology is available on the 6500’s (older Sup720 cards with the PFC3A so no 15.x IOS available) that would allow us to tunnel the L2 Ethernet vlan’s across the L3 network and what would be something we should be looking at for our equipment / network redesign later.

So far I have found out that the following is not going to work:
L2tpv3 (not supported on 6500)
EoMPLSoGRE (the oGRE part isn’t supported unless you have the 7600 SIP-400 card in the chassis)

The only one that looks like a possibility is EoMPLS, I have confirmed I can do pseudo wires with MPLS encapsulation, the two DC’s are basically direct connect give or take a few core devices so it would be workable, but not necessarily ideal as we have no internal MPLS at the moment and I’d like to avoid doing it if possible (for no other reason than to save complexity)

I’m still looking at VPLS etc as well.

As for into the future, we are currently looking at 4500-X’s in the core as a temporary upgrade until we can get the budget approved for 6500-E’s with Sup 2T’s (likely but not set in stone), given that what would you suggest could work for that layout? I’m still reading on what is / isn’t available on the 4500-X’s but theoretically the 6500’s could still be available for the DC interconnect tunnels / encap if required.

FYI – the connections between are all controlled by us, we have fibre circuits that are dedicated to us so there should be no carrier / provider issues to stop us.

PS – Our DC’s use nexus 5k’s unfortunately so no OTV to save us :(

PPS – if something isn’t clear please let me know and I’ll clarify, I think I have explained enough to cover it off but feel free to ask away.

Thanks,
Ayden Beeson

[cid:part1.06070807.09040302 at networklabs.co.nz]<http://www.csu.edu.au/>

|   ALBURY-WODONGA   |   BATHURST   |   CANBERRA   |   DUBBO   |   GOULBURN   |   MELBOURNE   |   ONTARIO   |   ORANGE   |   PORT MACQUARIE   |   SYDNEY   |   WAGGA WAGGA   |

________________________________
LEGAL NOTICE
This email (and any attachment) is confidential and is intended for the use of the addressee(s) only. If you are not the intended recipient of this email, you must not copy, distribute, take any action in reliance on it or disclose it to anyone. Any confidentiality is not waived or lost by reason of mistaken delivery. Email should be checked for viruses and defects before opening. Charles Sturt University (CSU) does not accept liability for viruses or any consequence which arise as a result of this email transmission. Email communications with CSU may be subject to automated email filtering, which could result in the delay or deletion of a legitimate email before it is read at CSU. The views expressed in this email are not necessarily those of CSU.

Charles Sturt University in Australia<http://www.csu.edu.au> The Grange Chancellery, Panorama Avenue, Bathurst NSW Australia 2795 (ABN: 83 878 708 551; CRICOS Provider Numbers: 00005F (NSW), 01947G (VIC), 02960B (ACT)). TEQSA Provider Number: PV12018
Charles Sturt University in Ontario<http://www.charlessturt.ca/> 860 Harrington Court, Burlington Ontario Canada L7N 3N4 Registration: www.peqab.ca<http://www.peqab.ca>

Consider the environment before printing this email.

Disclaimer added by CodeTwo Exchange Rules 2007
www.codetwo.com<http://www.codetwo.com>

_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net<mailto:AusNOG at lists.ausnog.net>
http://lists.ausnog.net/mailman/listinfo/ausnog

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ATT00001.bmp
Type: image/bmp
Size: 37976 bytes
Desc: ATT00001.bmp
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20130527/0ecda3f1/attachment.bin>