Without the right hardware you can expect to see all kinds of problem's
like control plane being learnt correctly but VC still being down or VC
manages to come up but traffic does not pass.
Which is why it is important to use the correct/supported LC for the
feature.
[email protected] said the following on 8/20/2009 1:21 PM:
More over in some ios version it comes up but not passing traffic and no label imposed. While in later release it stays down.
Hth
Hash
Sent from my BlackBerry® wireless device from Aljawal
-----Original Message-----
From: Shimol Shah <[email protected]>
Date: Thu, 20 Aug 2009 13:05:17
To: Atif Sid<[email protected]>
Cc: <[email protected]>
Subject: Re: [c-nsp] xconnect on VLAN interface ES card
On the 7600 for doing SVI EoMPLS (Xconnect under SVI) you need a CWAN
card (ES20, SIP400 etc) facing the core.
For using Hardware EoMPLS (i.e. with Xconnect under main/single tag
subif ) on the 7600, you can use below
CE Facing LC: LAN Line Card, ES-20, SIP-600
Core Facing LC: Any
Atif Sid said the following on 8/20/2009 12:55 PM:
I have seen posts on this topic but still not clear.. currentl have WS line
cards, with SUP-32 on 7606; PW on VLAN interface do not work. testing ES
card customer facing, RSP-720 core facing, here is the issue.. any help will
be great !
Is it possible to configure xconnect from an SVI interface, when your core
facing cards are RSP-720?
I have configured it:
interface Vlan290
no ip address
xconnect 10.10.136.129 37123712 encapsulation mpls
end
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
Although when I use a physical interface it comes up?
RSP720 does not support it??
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
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
_______________________________________________
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/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
