Thanks Stoffi, Oli..
The VLAN was SVI-based on the ME6524. I've switched to VLAN-based, attached to
the outgoing interface.. The VC is not coming up, so I've included a snippet
below, in case I've missed anything. Also, there is a name Cisco refers to
adding a sub-interface for xconnect statements, while the main interface can be
trunked for passing standard VLAN's. For the life of me I cannot remember what
it is. Any ideas there?
ME6524#sh run int Gi1/10
Building configuration...
Current configuration : 464 bytes
!
interface GigabitEthernet1/10
description Trunk to Edge device
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 16,305,330
switchport mode trunk
switchport nonegotiate
mtu 9000
logging event link-status
logging event trunk-status
logging event spanning-tree status
logging event subif-link-status ignore-bulk
speed 1000
duplex full
spanning-tree portfast trunk
spanning-tree guard none
end
ME6524#sh run int gi1/10.655
Building configuration...
Current configuration : 112 bytes
!
interface GigabitEthernet1/10.655
encapsulation dot1Q 655
xconnect 10.200.1.8 655 encapsulation mpls
end
ME6524#sh mpls l2transport vc 655 detail
Local interface: Gi1/10.655 up, line protocol up, Eth VLAN 655 up
Destination address: 10.200.1.8, VC ID: 655, VC status: down
Output interface: if-?(0), imposed label stack {}
Preferred path: not configured
Default path: no route
No adjacency
Create time: 00:05:18, last status change time: 00:05:18
Signaling protocol: LDP, peer 10.200.1.8:0 up
MPLS VC labels: local 330, remote 69
Group ID: local 0, remote 0
MTU: local 9000, remote 1500
Remote interface description: MPLS Test VLAN
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 0, send 0
byte totals: receive 0, send 0
packet drops: receive 0, send 0
Thoughts?
-- Stephen
Christoph Loibl wrote:
Hi,
On Nov 15, 2008, at 9:40 AM, Oliver Boehmer (oboehmer) wrote:
you've configured vlan-based EoMPLS (i.e. xconnect on the SVI). In order
for this to work on Cat65xx/Sup720, you need OSM/SIP as core-facing
linecard, something which isn't possible on the fixed-configuration
ME6524..
So you need to move xconnect to the physical port.
Hm. What is the cisco-speak "correct" name now (which in fact is not
very intuitive): Vlan-based or SVI-based? Vlan-based is
interface gigabitethernet 1/interface.subinterface
encapsulation dot1q vlan_id
xconnect peer_router_id vcid encapsulation mpls
!
This is possible on sup720 even without any fancy linecards. But SVI-based
interface vlan 10
xconnect peer_router_id vcid encapsulation mpls
!
requires those OSM/SIP modules on cat65xx/Sup720 (as Oli wrote) but
works fine on ME3750. Thus SVI-based (on ME3750) together with
VLAN-based (on ME6524) should work.
When configuring SVI-based EoMPLS on the ME6524 usually some kind of
warning is logged ("Config not supported", or "MPLS configured on LAN
interfaces" as far as I remember).
Stoffi
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
