Mailing List Archive: Routed sub interfaces?

Routed sub interfaces?

Dec 29, 2014, 3:13 AM

Post #1 of 4 (2535 views)

Hi,

We are moving from a Cisco ASR1002 to a Brocade CER2000RT but I can't
see any way to do routed sub interfaces (router on a stick) from looking
through the configuration guide. For example, on the ASR we'd have
gi1/1 going to provider X and gi1/2 going to provider Y with managed
ethernet circuits delivered on the same VLAN tags. The config would look
something like the example below and this wouldn't be an issue as vlan
tag 10 on gi1/1 would be separate from vlan tag 10 on gi1/2.

int gi 1/1
desc Trunk to provider X

int gi 1/1.10
desc Link to Site A
encap dot1q 10
ip add 192.168.1.1 255.255.255.252

int gi 1/2
desc Trunk to provider Y

int gi 1/2.10
desc Link to Site B
encap dot1q 10
ip add 192.168.2.1 255.255.255.252

However from reading the configuration guide, to do this on a CER we
would make e1/1 and e1/2 tagged ports in vlan 10 but then the virtual
routing interface (ve10) for vlan 10 would be reachable via both Site A
and B. What are people doing in this situation to keep vlan 10 from e1/1
separate from vlan 10 on e1/2?

Thanks,
Matthew
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Re: Routed sub interfaces? [ In reply to ]

darrenoc at outlook

Dec 29, 2014, 11:37 AM

Post #2 of 4 (2495 views)

Permalink

I no longer work with Brocades, only in my last job. But I did run into the same issue.
There is no easy way around it.
When we ordered circuits that required vlan tags, we created a database specifically in order that no two links used the same vlan tag. This is only a problem if you're terminating a layer 3 subinterface like this. If the CER is an MPLS PE, then each physical interface can have the same vlan tagged into different VLL/VPLS instances.
There are some workarounds, none of them fun.
1 - When the link comes in, put the subinterface into a VPLS with any vlan tag, then create a VE interface tied to that VPLS. The VE and vlan tags don't need to match. You will of course need an MPLS license for this. We used XMR so had no issue here.2 - Create a VLL to another box doing the actual routing. Same issue as above though.3 - Put another box in front that can do vlan manipulation like a Cisco me3600x and swap the vlan before it gets to the CER.
None of them pretty.
Darrenwww.mellowd.co.uk/ccie

> Date: Mon, 29 Dec 2014 21:43:32 +1030
> From: matthew@tav.id.au
> To: foundry-nsp@puck.nether.net
> Subject: [f-nsp] Routed sub interfaces?
>
> Hi,
>
> We are moving from a Cisco ASR1002 to a Brocade CER2000RT but I can't
> see any way to do routed sub interfaces (router on a stick) from looking
> through the configuration guide. For example, on the ASR we'd have
> gi1/1 going to provider X and gi1/2 going to provider Y with managed
> ethernet circuits delivered on the same VLAN tags. The config would look
> something like the example below and this wouldn't be an issue as vlan
> tag 10 on gi1/1 would be separate from vlan tag 10 on gi1/2.
>
> int gi 1/1
> desc Trunk to provider X
>
> int gi 1/1.10
> desc Link to Site A
> encap dot1q 10
> ip add 192.168.1.1 255.255.255.252
>
> int gi 1/2
> desc Trunk to provider Y
>
> int gi 1/2.10
> desc Link to Site B
> encap dot1q 10
> ip add 192.168.2.1 255.255.255.252
>
> However from reading the configuration guide, to do this on a CER we
> would make e1/1 and e1/2 tagged ports in vlan 10 but then the virtual
> routing interface (ve10) for vlan 10 would be reachable via both Site A
> and B. What are people doing in this situation to keep vlan 10 from e1/1
> separate from vlan 10 on e1/2?
>
> Thanks,
> Matthew
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp

Re: Routed sub interfaces? [ In reply to ]

erich at hoh

Dec 29, 2014, 3:52 PM

Post #3 of 4 (2493 views)

Permalink

Matthew,

You won't like it but there is no such concept as Subinterface on the Netiron Serie.

You have multiple Workarounds.

a) Use different VLAN from your upstream

Real Workarounds

b) Use the 802.3ah metro Features and S-VLAN type change

c) Use a loopback cable, local-vll, rewrite vlan features.

Maybe there are new possibilities since 5.6.

Regards Erich

> Am 29.12.2014 um 12:13 schrieb Matthew <matthew@tav.id.au>:
>
> Hi,
>
> We are moving from a Cisco ASR1002 to a Brocade CER2000RT but I can't see any way to do routed sub interfaces (router on a stick) from looking through the configuration guide. For example, on the ASR we'd have gi1/1 going to provider X and gi1/2 going to provider Y with managed ethernet circuits delivered on the same VLAN tags. The config would look something like the example below and this wouldn't be an issue as vlan tag 10 on gi1/1 would be separate from vlan tag 10 on gi1/2.
>
> int gi 1/1
> desc Trunk to provider X
>
> int gi 1/1.10
> desc Link to Site A
> encap dot1q 10
> ip add 192.168.1.1 255.255.255.252
>
> int gi 1/2
> desc Trunk to provider Y
>
> int gi 1/2.10
> desc Link to Site B
> encap dot1q 10
> ip add 192.168.2.1 255.255.255.252
>
> However from reading the configuration guide, to do this on a CER we would make e1/1 and e1/2 tagged ports in vlan 10 but then the virtual routing interface (ve10) for vlan 10 would be reachable via both Site A and B. What are people doing in this situation to keep vlan 10 from e1/1 separate from vlan 10 on e1/2?
>
> Thanks,
> Matthew
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Re: Routed sub interfaces? [ In reply to ]

josh at zevlag

Dec 31, 2014, 8:00 AM

Post #4 of 4 (2473 views)

Permalink

I find myself using Option #1 frequently.
1 - When the link comes in, put the subinterface into a VPLS with any vlan
tag, then create a VE interface tied to that VPLS. The VE and vlan tags
don't need to match. You will of course need an MPLS license for this. We
used XMR so had no issue here.

And I use this really ugly one too!
c) Use a loopback cable, local-vll, rewrite vlan features.

On Mon, Dec 29, 2014 at 12:37 PM, Darren O'Connor <darrenoc@outlook.com>
wrote:

> I no longer work with Brocades, only in my last job. But I did run into
> the same issue.
>
> There is no easy way around it.
>
> When we ordered circuits that required vlan tags, we created a database
> specifically in order that no two links used the same vlan tag. This is
> only a problem if you're terminating a layer 3 subinterface like this. If
> the CER is an MPLS PE, then each physical interface can have the same vlan
> tagged into different VLL/VPLS instances.
>
> There are some workarounds, none of them fun.
>
> 1 - When the link comes in, put the subinterface into a VPLS with any vlan
> tag, then create a VE interface tied to that VPLS. The VE and vlan tags
> don't need to match. You will of course need an MPLS license for this. We
> used XMR so had no issue here.
> 2 - Create a VLL to another box doing the actual routing. Same issue as
> above though.
> 3 - Put another box in front that can do vlan manipulation like a Cisco
> me3600x and swap the vlan before it gets to the CER.
>
> None of them pretty.
>
> Darren
> www.mellowd.co.uk/ccie
>
>
> > Date: Mon, 29 Dec 2014 21:43:32 +1030
> > From: matthew@tav.id.au
> > To: foundry-nsp@puck.nether.net
> > Subject: [f-nsp] Routed sub interfaces?
>
> >
> > Hi,
> >
> > We are moving from a Cisco ASR1002 to a Brocade CER2000RT but I can't
> > see any way to do routed sub interfaces (router on a stick) from looking
> > through the configuration guide. For example, on the ASR we'd have
> > gi1/1 going to provider X and gi1/2 going to provider Y with managed
> > ethernet circuits delivered on the same VLAN tags. The config would look
> > something like the example below and this wouldn't be an issue as vlan
> > tag 10 on gi1/1 would be separate from vlan tag 10 on gi1/2.
> >
> > int gi 1/1
> > desc Trunk to provider X
> >
> > int gi 1/1.10
> > desc Link to Site A
> > encap dot1q 10
> > ip add 192.168.1.1 255.255.255.252
> >
> > int gi 1/2
> > desc Trunk to provider Y
> >
> > int gi 1/2.10
> > desc Link to Site B
> > encap dot1q 10
> > ip add 192.168.2.1 255.255.255.252
> >
> > However from reading the configuration guide, to do this on a CER we
> > would make e1/1 and e1/2 tagged ports in vlan 10 but then the virtual
> > routing interface (ve10) for vlan 10 would be reachable via both Site A
> > and B. What are people doing in this situation to keep vlan 10 from e1/1
> > separate from vlan 10 on e1/2?
> >
> > Thanks,
> > Matthew
> > _______________________________________________
> > foundry-nsp mailing list
> > foundry-nsp@puck.nether.net
> > http://puck.nether.net/mailman/listinfo/foundry-nsp
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>