[c-nsp] Issue with MPLS implementation using cisco ME-3750-24TE-M within our backbone

[Thomas Braun]

Hi,


for MPLS to work, you need to use the following ports:

interface GigabitEthernet1/1/1

interface GigabitEthernet1/1/2




>From the Cisco Documentation:
MPLS functionality is supported only on the enhanced-services (ES)
ports; EoMPLS is supported on standard ports and on switch virtual
interfaces (SVIs).


http://www.cisco.com/c/en/us/td/docs/switches/metro/catalyst3750m/software/release/12-2_58_se/configuration/guide/3750metro_scg/swmpls.html


Regards
Thomas


> 
> See in attach configurations files and show mpls forwarding-table output.
> 
> Regards
> 
>  
> 
> 
> 
> Thucydide TAJOUO
> 
> 
> Le Vendredi 12 septembre 2014 14h49, Mikael Abrahamsson <swmike at swm.pp.se> a écrit :
>  
> 
> 
> On Fri, 12 Sep 2014, thucydide tajouo wrote:
> 
>> I said : "Note that between PE and LSR, we use VLANs interface (because MPLS cannot be enable on physical interfaces)." because of what you can see on the image in attach according to this 
>>
>> http://www.cisco.com/c/en/us/td/docs/switches/metro/catalyst3750m/software/release/12-2_55_se/configuration/guide/3750metro_scg/swmpls.html#wp1182634
>>
>> until now, i realize that when  MPLS is disabled on MPLS cloud interfaces, i can ping from one customer from another but when i enable it again, ping cannot pass.
> 
> I don't understand your terminology. "cloud interface"? "VLANs interface"?
> 
> Please post config.
> 
> 
> 
> 
> _______________________________________________
> 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/
>