[c-nsp] Sup720 + EoMPLS type interworking

[Tim Winders]

I haven't paid attention to MPLS technology as I didn't believe it would 
affect me, however, looking at this scenario, I may be wrong.

Can one run a private MPLS network?  Specifically, I have this situation:

Sup720 -> GigE over Telco network -> Sup720

The carrier's equipment does not allow me to natively trunk between the 
networks, so I am routing.  Could I run MPLS between the two sites and 
pass my dot1Q vlans across the network?

--

Tim Winders
Associate Dean of Information Technology
South Plains College
Levelland, TX 79336

On Fri, 3 Mar 2006, Ian Cox wrote:

>
> To do vlan mode, with Sup7203b/3XL you do the xconnect on sub-interfaces.
>
> int gig 9/7.100
>  encap dot1q 100
>  xconnect ....
>
> If you want to carry the entire 1q range of tags between two ports
> you put the xconnect on the phsyical interface.
> int gig 9/7
>  xconnect ...
>
>
> Ian
>
>
> At 09:07 AM 3/3/2006 +0000, David Freedman wrote:
>> Question.
>> --------
>>
>>
>> We have the following setup in place.
>>
>>
>> =====802.1q bundle====[PE Router A]
>>                               |
>>                               | MPLS Cloud
>>                               |
>>                        [PE Router B]
>>                            |
>>                            |
>>                           Ethernet port
>>
>>
>> Currently, PE router A is a 7200 NPE-G1 running
>> 12.3(10)
>>
>> PE router B is a Catalyst 6500 with a Supervisor2 / MSFC2
>> and a 4GE-WAN-OSM card.
>> This router has its PE->P connection on the OSM which is fine.
>>
>>
>> We receive 802.1q tagged VLAN traffic ingress on PE A
>> from a customer and send it to PE B via EoMPLS to a dedicated router
>> port by carrying the VLAN all the way through (EoMPLS VLAN mode)
>>
>>
>>
>> The way we currently do this is:
>>
>> PE router A:
>>
>> !
>> interface GigabitEthernet0/1.100
>>   encapsulation dot1q 100
>>   description Customer A (vlan 100)
>>   xconnect <PE B> 100 encapsulation mpls
>> !
>>
>> PE router B:
>>
>> !
>> interface vlan 100
>>   description Customer A from PE A (vlan 100)
>>   mpls l2transport route <PE A> 100 vc-type vlan
>> !
>> interface FastEthernet 1/1
>>   description drop for vlan 100
>>   switchport
>>   switchport mode access
>>   switchport access vlan 100
>> !
>>
>>
>>
>> Now, this works fine, if the customer wants to further carry dot1q
>> inside the vlan, we just do this on the access switchport
>>
>> !
>> interface FastEthernet 1/1
>>   description drop for vlan 100
>>   switchport
>>   switchport mode access
>>   switchport access vlan 100
>>   switchport mode dot1q-tunnel
>> !
>>
>>
>>
>> The question comes when we upgrade PE B to Supervisor720 PFC3BXL.
>>
>>  From the earlier discussion that was going on here, you can't do EoMPLS
>> on an SVI without an OSM which we are not planning on using after the
>> upgrade (we want to ditch the 4GE-WAN-OSM as its end of life)
>>
>>
>> <the crunch>
>>
>> So, the question really is, how do we transport EoMPLS vlan mode on a
>> Supervisor 720 PFC3BXL without an OSM, considering EoMPLS SVI isn't
>> possible.
>>
>> If we cant do this, how do we use interworking to turn the VC into a
>> "port-mode"  VC?
>>
>>
>> </the crunch>
>>
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>