cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2587
Views
0
Helpful
3
Replies

control-word usage in l2vpn question?

fly
Level 2
Level 2

Hi,Dear Sir/Madam,

    we config a l2 vpn between two 6509,  it worked, but we move line between two 6509 to SDH to extend the distance.

   but the sdh device can't allowed <64 bytes packet, we found when <64 bytes packet send from 6509 was dropped by sdh device.

   can we config control-word on two 6509 to auto pad packet to 64 bytes?

   but we found one 6509 don't have control-word ,the other 6509 has control-word configured, but two 6509 can't negotiate control-word?

 

   can i auto padding to 64 bytes by using control-word?

 

pseudowire-class eompls

 encapsulation mpls

 interworking ethernet

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

interface GigabitEthernet2/2/1

 description

 no switchport

 no ip address

 no keepalive

 xconnect x.x.x.x 1000 pw-class eompls

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

router 1#sh mpls l2transport vc 1000 detail

Local interface: Gi2/2/3 up, line protocol up, Ethernet up

  Destination address: x.x.x.x, VC ID: 1000, VC status: up

    Output interface: Gix.x.x.x, imposed label stack {100}

    Preferred path: not configured

    Default path: active

    Next hop: x.x.x.x

  Load Balance: none

  Flow Label: Disabled

  Create time: 2d05h, last status change time: 2d05h

  Signaling protocol: LDP, peer x.x.x.x:0 up

    Targeted Hello: x.x.x.x(LDP Id) -> x.x.x.x

    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 147, remote 100

    Group ID: local 0, remote 0

    MTU: local 1500, remote 1500

    Remote interface description:

  Sequencing: receive disabled, send disabled

  VC statistics:

    packet totals: receive 23300, send 23299

    byte totals:   receive 2893290, send 2602655

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

 

6509-2

pseudowire-class eompls

 encapsulation mpls

 interworking ethernet

control-word

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

interface FastEthernetx/x

 no ip address

 xconnect x.x.x.x 1000 pw-class eompls

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

6509-2#sh mpls l2transport vc detail

Local interface: Fax/x up, line protocol up, Ethernet up

  Destination address: x.x.x.x, VC ID: 1000, VC status: up

    Output interface: x/x, imposed label stack {147}

    Preferred path: not configured

    Default path: active

    Next hop: x.x.x.x

  Load Balance: none

  Flow Label: Disabled

  Create time: 2d05h, last status change time: 2d05h

  Signaling protocol: LDP, peer x.x.x.x8:0 up

    Targeted Hello: x..x.x.x(LDP Id) -> 10.1.1.x, LDP is UP

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

      LDP route watch                   : enabled

      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

      Last remote LDP ADJ    status rcvd: No fault

    MPLS VC labels: local 100, remote 147

    Group ID: local 0, remote 0

    MTU: local 1500, remote 1500

    Remote interface description: PE-PuDong-Test

  Sequencing: receive disabled, send disabled

  Control Word: Off (configured: enabled) <<<<<<---control-word configured but not work

  VC statistics:

    transit packet totals: receive 23279, send 23279

    transit byte totals:   receive 2600434, send 2564554

    transit packet drops:  receive 0, send 0

 

3 Replies 3

Nagendra Kumar Nainar
Cisco Employee
Cisco Employee

Hi Fly,

Enabling control-word will only add additional 4 bytes. It will not pad a packet uptil any minimum size. So I doubt enabling CW is going to help.

 

Regarding the CW staying as OFF, I think it depends on the line card support. SOme cards are not capable of supporting control-word for edge/core functionality.

What is your CE facing linecard?. Can you check "show mpls l2transport hw-capability interface fax/x" (This is the interface under which you enabled xconnect") and see if control-word processing is supported or not?.

 

-Nagendra

if enable control-word can't auto pad packet to 64 bytes, that doesn't help us.

we capture packet on sdh devices , found sdh drop packet < 64 bytes.

Is there any method to support pad small packet?

Hi,Nagendra,

   I think customer mislead me.

    for ethernet interface, if frame <64 bytes, ethernet interface driver will pad the frame and send out.

So this padding don't happen at l2vpn encapsulation , and happend at ethernet interface.

   If etherner interface on SDH device receive <64 bytes frame , it means there may be some  duplex,mtu, cable problem , not l2 vpn encapsulation problem

   I will check 651----sdh----652 ethernet config! \

   thank you!

Tom