[nsp] AToM

adel mezibra adel.mezibra at peoch.net
Mon Dec 22 14:19:12 EST 2003


(sorry if you get this mail twice i messed up with list source mail )


mpls l2transport is replaced by xconnect
that's the same command just writen differently for config compatibility
issue.
(like mpls .. and tag-switcthing .. )


Antoine,

I only played port mode using 7206/75XX as PE and that worked pretty fine..

could you try "switchport mode dot1qtunnel"  ? check also your MTU along the
path and at both end.

you also seems to miss the vc-type info on the mpls l2transport line..
end it with vc-type 'ether' or 'vlan' (depending if you want port based or
vlan based forwarding)

adel

-----Message d'origine-----
De : cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net]De la part de Temkin, David
Envoye : lundi 22 decembre 2003 19:06
A : Antoine Versini; cisco-nsp at puck.nether.net
Objet : RE: [nsp] AToM


To me it looks like you're trying to do VLAN x-connect, which is
different from what you've specified below I *think*...

Does the following command work (under the interface)

 xconnect (ip addr) (vc) encapsulation mpls

Keep in mind the VLAN id's MUST be the same on both ends, unless you're
using a GSR which can do the re-write.

-Dave

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Antoine Versini
Sent: Monday, December 22, 2003 12:42 PM
To: cisco-nsp at puck.nether.net
Subject: [nsp] AToM


Hi NSP !

I'm trying to achieve layer 2 ethernet transport between two 7600 w/
SUP720 running 12.2(17a)SX1. I've been carefully studying
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft
/121limit/121ex/121ex8a/eompls9.htm
and then reproduced the configuration. The VC goes UP, but doesn't carry
any traffic :

c6k03-v#sh mpls l2transport vc 69 detail
Local interface: Vl42 up, line protocol up, Eth VLAN 42 up
  Destination address: 194.117.192.203, VC ID: 69, VC status: up
    Tunnel label: 17, next hop 62.34.0.26
    Output interface: Vl210, imposed label stack {17 16}
  Create time: 02:11:26, last status change time: 00:00:42
  Signaling protocol: LDP, peer 194.117.192.203:0 up
    MPLS VC labels: local 16, remote 16
    Group ID: local 39, remote 39
    MTU: local 1500, remote 1500
    Remote interface description: AToM c6k04-v
  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

Here is the basic config i've done on the two edge routers (the configs
are symetrical, except the destination IP addresses, of course) :

no spanning-tree vlan 42
!
vlan 42
 name AToM
!
interface GigabitEthernet5/2
 no ip address
 logging event link-status
 media-type rj45
 speed 100
 duplex full
 switchport
 switchport access vlan 42
 switchport mode access
!
interface Vlan42
 description AToM c6k03-v
 no ip address
 mpls l2transport route 194.117.192.203 69
!

An end-station is attached to the Gi5/2 interface and there is another
one connected the same way on the other end. They share the same IP
subnet, but can't ping each other. Please also note that there is a P
router between the two edge 7600's and IP labels are switched fine (thus
I assume this is not a problem on the MPLS core itself).

If you think there is a mistake in this configuration, feel free to
point it to me :)

Thanks,
AV.

--
Antoine Versini
IP Networks Project Manager / T-Online France - Club-Internet
_______________________________________________
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/

IMPORTANT: The information contained in this email and/or its attachments is
confidential. If you are not the intended recipient, please notify the
sender immediately by reply and immediately delete this message and all its
attachments.  Any review, use, reproduction, disclosure or dissemination of
this message or any attachment by an unintended recipient is strictly
prohibited.  Neither this message nor any attachment is intended as or
should be construed as an offer, solicitation or recommendation to buy or
sell any security or other financial instrument.  Neither the sender, his or
her employer nor any of their respective affiliates makes any warranties as
to the completeness or accuracy of any of the information contained herein
or that this message or any of its attachments is free of viruses.


_______________________________________________
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/



More information about the cisco-nsp mailing list