Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

XConnect on vlan SVI

I have a 6500 facing my core network and tried to enable L2TPv3 (xconnect) on a vlan SVI but the vc will not come up. the module i am using is WS-X6748GE-TX card. Do i need a SIP module for this to work?

6 REPLIES
Cisco Employee

Re: XConnect on vlan SVI

Francisco,

You indeed need a SIP card (or ES20 card) if you want the SVI to be the termination point for your pseudowire.

Without such a card you can always put the xconect statement on a physical interface or subinterface.

Regards

Harold Ritter
Sr. Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México
Community Member

Re: XConnect on vlan SVI

I am testing ES card, and tried to create a PW from VLAN interface, it does not come up:

PE4#sh mpl l2transport vc

Local intf Local circuit Dest address VC ID Status

------------- -------------------------- --------------- ---------- ----------

Vl290 Eth VLAN 290 10.10.136.129 37123712 DOWN

PE4#sh mpl l2transport vc 37123712 det

PE4#sh mpl l2transport vc 37123712 detail

Local interface: Vl290 up, line protocol up, Eth VLAN 290 up

Interworking type is Ethernet

Destination address: 10.10.136.129, VC ID: 37123712, VC status: down

Output interface: none, imposed label stack {}

Preferred path: not configured

Default path: no route

No adjacency

Create time: 00:00:49, last status change time: 00:00:03

Signaling protocol: LDP, peer 10.10.136.129:0 up

Targeted Hello: 10.10.136.131(LDP Id) -> 10.10.136.129

Status TLV support (local/remote) : enabled/not supported

Label/status state machine : remote ready, LndRru

Last local dataplane status rcvd: no fault

Last local SSS circuit status rcvd: AC DOWN(rx,tx faults)

Last local SSS circuit status sent: no fault

Last local LDP TLV status sent: no fault (withdrawn)

Last remote LDP TLV status rcvd: not sent

MPLS VC labels: local unassigned, remote 340

Group ID: local unknown, remote 0

MTU: local unknown, remote 1500

Remote interface description: ** Test PW with PE4 ES SVI int **

Sequencing: receive disabled, send disabled

VC statistics:

packet totals: receive 0, send 0

byte totals: receive 0, send 0

packet drops: receive 0, seq error 0, send 0

PE4#sh module

Mod Ports Card Type Model Serial No.

--- ----- -------------------------------------- ------------------ -----------

2 40 7600 ES+ 7600-ES+40G3CXL JAE1309493P

3 40 7600 ES+ 7600-ES+40G3CXL JAE1309493M

5 2 Route Switch Processor 720 (Active) RSP720-3C-GE JAE12024CGH

6 2 Route Switch Processor 720 (Hot) RSP720-3C-GE JAE1130RD6Z

PE4#sh run int g3/10

Building configuration...

Current configuration : 207 bytes

!

interface GigabitEthernet3/10

description ** Connected to ISG-2000-2 E1/1 **

switchport

switchport trunk allowed vlan 290,299

switchport mode trunk

speed 1000

service-policy output trunk-policy

end

interface Vlan290

no ip address

xconnect 10.10.136.129 37123712 encapsulation mpls

end

Community Member

Re: XConnect on vlan SVI

***************

I moved it to physical interface it comes up:

interface GigabitEthernet2/1

no ip address

ip verify unicast source reachable-via any

load-interval 30

speed 1000

isis network point-to-point

isis authentication mode md5

isis authentication key-chain N-ISIS

xconnect 10.10.136.129 37123712 encapsulation mpls

end

PE4#sh mpls l2transport vc

Local intf Local circuit Dest address VC ID Status

------------- -------------------------- --------------- ---------- ----------

Gi2/1 Ethernet 10.10.136.129 37123712 UP

PE4#sh mpls l2transport vc 37123712 detail

Local interface: Gi2/1 up, line protocol up, Ethernet up

Destination address: 10.10.136.129, VC ID: 37123712, VC status: up

Output interface: Gi5/1, imposed label stack {16009 340}

Preferred path: not configured

Default path: active

Next hop: 10.10.129.53

Create time: 00:00:24, last status change time: 00:00:24

Signaling protocol: LDP, peer 10.10.136.129:0 up

Targeted Hello: 10.10.136.131(LDP Id) -> 10.10.136.129

Status TLV support (local/remote) : enabled/not supported

Label/status state machine : established, LruRru

Last local dataplane status rcvd: no fault

Last local SSS circuit status rcvd: no fault

Last local SSS circuit status sent: no fault

Last local LDP TLV status sent: no fault

Last remote LDP TLV status rcvd: not sent

MPLS VC labels: local 50279, remote 340

Group ID: local 0, remote 0

MTU: local 1500, remote 1500

Remote interface description: ** Test PW with PE4 ES SVI int **

Sequencing: receive disabled, send disabled

SSO Descriptor: 10.10.136.129/37123712, local label: 50279

SSM segment/switch IDs: 8426/4098 (used), PWID: 4098

VC statistics:

packet totals: receive 0, send 0

byte totals: receive 0, send 0

packet drops: receive 0, seq error 0, send 0

Community Member

Re: XConnect on vlan SVI

Hi Fran

This should be working, i have seen working in 7600. You can apply xconnect on the VLAN. Can i know the IOS version using on the 6500??

Community Member

Re: XConnect on vlan SVI

Hi

this might help (or confuse)

xconnect on interface VLAN could be working, but as I recall you need OSM/ES cards for uplink.

But using MUXUNI functionality and configuring xconnect on do1Q subinterface should be OK.

http://www.cisco.com/en/US/docs/routers/7600/install_config/12.2SR_OSM_config/mpls_ps368_TSD_Products_Module_Configuration_Guide_Chapter.html#wp1128955

Configuring EoMPLS VLAN Mode for Supervisor Engine 720-Based System

To configure MPLS to transport Layer 2 VLAN packets between two endpoints in a supervisor engine 720-based system, perform the following steps on the provider edge (PE) routers.

Note You must configure Ethernet over MPLS (VLAN mode) on the subinterfaces.

Community Member

Re: XConnect on vlan SVI

Hi!

We are setting up xconnects from a physical interface and the EoMPLS TE tunnels are connected over vlan interfaces with trunks in both ends.

Do i also have to configure the VLAN mode in someway to get this running?

A lot of our tunnels works perfecly but now when we are setting up new tunnels the incoming unicast traffic does not enter from the physical interface to the VC in both ends.

When doing packet capture from the incoming interface i can see unicast packets coming in but the the VC packet counters doesn't increase.

Multicast traffic are running perfect between the CE's and the cdp neigbour is shown in both ends.

Is there any known issue when connecting EoMPLS with xconnect from a physical interface over a trunk with SVI's?

7192
Views
0
Helpful
6
Replies
CreatePlease to create content