You can do port-based EoMPLS quite easily. ME3600:
http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/12.2_52_ey/configuration/guide/swmpls.html 7600: http://www.cisco.com/en/US/docs/routers/7600/ios/15S/configuration/guide/pfc3mpls.html On 2013-04-10, at 1:14 PM, Antonis Vosdoganis <[email protected]> wrote: > We have a BGP session with a carrier delivered on ME3600-A. Because ME3600 > is not able to carry bgp table we have create vlan 100 and we and made the > gigabit port access to vlan 100. > > 7609 <---------- ME3600-B <--------- ME3600-A <------- BGP SESSION > > ME3600-A > vlan 100 > name BGP_PEERING > > interface GigabitEthernet0/1 > description BGP_PEERING > switchport access vlan 100 > > ME3600-A and ME3600-B are interconnected with a trunk port. > > ME3600-B > vlan 100 > name BGP_PEERING > > ME3600-B and 7609 are also interconnected with a trunk port > > CISCO 7609-S > vlan 100 > name BGP_PEERING > > interface Vlan100 > description BGP_PEERING > ip address XXX.XXX.XXX.XXX 255.255.255.248 > > In all trunk ports we are using mpls enabled SVIs. > > So the vlan 100 travels all the way from ME3600-A to 7609 and the bgp > session is running on 7609. > > > I am trying to say is it possible to replace the vlan with EoMPLS and how? > > Best Regards > > Antonis. > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
