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

L2VPN between ASR900 and ASR9000

   Hi, I’m having problems configuring an EoMPLS connection between a Cisco ASR900 and a Cisco ASR9000.
I would like to transport the vlan 14 (rewriting it to vlan 200 at the far end).
I never had any problems between IOS devices or IOS-XE devices but between an ASR9000 (5.1.3) and an ASR900 (15.4(2)S1) it seems not to be working.

At the ASR9000 side I have the error "ReasonInvalid context 0x51478694 or container type 0"
At the ASR900 side I have the error "Last error: Remote peer access circuit is down"

Have you any suggestions?

Thankyou

Here is the ASR 9000 configuration:

!
l2vpn
 pw-class gia1
    encapsulation mpls
       protocol ldp
       transport-mode vlan
       tag-rewrite ingress vlan 200
!
  xconnect group pwhe
   p2p numero1
     interface TenGigE0/0/2/1.1
     neighbor ipv4 117.27.118.186 pw-id 50
         pw-class gia1
!
mpls ldp
   router-id 117.27.118.211
   interface GigabitEthernet0/0/0/5.1     <--- this is the WAN side
!
interface TenGigE0/0/2/1
!
interface TenGigE0/0/2/1.1 l2transport
   encapsulation dot1q 200
!
interface GigabitEthernet0/0/0/5.1
 ipv4 address 117.27.118.185 255.255.255.252
 encapsulation dot1q 222
!

Here is the ASR 901 configuration:

!
pseudowire-class num1
   encapsulation mpls
   no control-word
!
interface GigabitEthernet0/1
 mtu 1504
 no ip address
 negotiation auto
 service instance 1 ethernet
    encapsulation dot1q 14
    rewrite ingress tag pop 1 symmetric
     xconnect 117.27.118.185 50 encapsulation mpls pw-class num1
 !
!
interface Vlan222
   ip address 117.27.118.186 255.255.255.252
   mpls ip

At the ASR 9000 side this happen:

RP/0/RSP0/CPU0:ASR9001-A#show l2vpn xconnect detail
Fri Nov  7 07:31:07.217 UTC

Group pwhe, XC numero1, state is down; Interworking none
  AC: TenGigE0/0/2/1.1, state is up
    Type VLAN; Num Ranges: 1
    VLAN ranges: [200, 200]
    MTU 1504; XC ID 0x1080001; interworking none
    Statistics:
      packets: received 0, sent 0
      bytes: received 0, sent 0
      drops: illegal VLAN 0, illegal length 0
  PW: neighbor 117.27.118.186, PW ID 50, state is down ( all ready )
    PW class gia1, XC ID 0xc0000004
    Encapsulation MPLS, protocol LDP
    Source address 117.27.118.211
    PW type Ethernet VLAN, control word disabled, interworking none
    Static tag rewrite: 200
    PW backup disable delay 0 sec
    Sequencing not set

    PW Status TLV in use
      MPLS         Local                          Remote
      ------------ ------------------------------ -----------------------------
      Label        16002                          19
      Group ID     0x4000180                      unknown
      Interface    TenGigE0/0/2/1.1               unknown
      MTU          1504                           1504
      Control word disabled                       disabled
      PW type      Ethernet VLAN                  Ethernet VLAN
      VCCV CV type 0x2                            0x2
                   (LSP ping verification)        (LSP ping verification)
      VCCV CC type 0x6                            0x2
                   (router alert label)           (router alert label)
                   (TTL expiry)
      ------------ ------------------------------ -----------------------------
    Incoming Status (PW Status TLV):
      Status code: 0x0 (Up) in Notification message
    Outgoing Status (PW Status TLV):
      Status code: 0x10 (PW Down) in Notification message
    MIB cpwVcIndex: 3221225476
    Create time: 06/11/2014 15:35:54 (15:55:12 ago)
    Last time status changed: 07/11/2014 01:27:13 (06:03:53 ago)
    Statistics:
      packets: received 0, sent 0
      bytes: received 0, sent 0

 

RP/0/RSP0/CPU0:ASR9001-A#show l2vpn xconnect

Fri Nov  7 01:34:18.752 UTC

RP/0/RSP0/CPU0:Nov  7 01:34:18.927 : l2vpn_mgr[1154]: DBG-ALL: set_filter_xconnect:5007, Filter flags are 0x0
RP/0/RSP0/CPU0:Nov  7 01:34:18.927 : l2vpn_mgr[1154]: DBG-ALL: fill_xc_bag:4105, Adding to bag group pwhe xconnect name = numero1
RP/0/RSP0/CPU0:Nov  7 01:34:18.927 : l2vpn_mgr[1154]: DBG-ALL: fill_ac_bag:2035, acmgr_lookup_context_by_ifname(TenGigE0_0_2_1.1) OK
RP/0/RSP0/CPU0:Nov  7 01:34:18.927 : l2vpn_mgr[1154]: DBG-ALL: get_segment_state:1239, get_segment_state from 5
RP/0/RSP0/CPU0:Nov  7 01:34:18.927 : l2vpn_mgr[1154]: DBG-ALL: fill_ac_bag:2045, AC signal_info.state=5, bag State=4
RP/0/RSP0/CPU0:Nov  7 01:34:18.927 : l2vpn_mgr[1154]: DBG-ALL|ERR: get_vfi_from_fwd:1922, XC DB operation failed. Reason: Invalid context 0x51478694 or container type 0
RP/0/RSP0/CPU0:Nov  7 01:34:18.927 : l2vpn_mgr[1154]: DBG-ALL|ERR: bd_port_dbase_get_bp_from_fwd:1021, XC DB operation failed. Reason: Invalid context 0x51478694 or container type 0

Legend: ST = State, UP = Up, DN = Down, AD = Admin Down, UR = Unresolved,
        SB = Standby, SR = Standby Ready, (PP) = Partially Programmed

XConnect                   Segment 1                       Segment 2
Group      Name       ST   Description            ST       Description            ST

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

pwhe       numero1    DN   Te0/0/2/1.1            UP       117.27.118.186  50     DN

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

RP/0/RSP0/CPU0:Nov  7 01:34:18.927 : l2vpn_mgr[1154]: DBG-ALL: fill_ac_bag:2130, AC nodeId,xconId=0x821,0x1080001

RP/0/RSP0/CPU0:Nov  7 01:34:18.927 : l2vpn_mgr[1154]: DBG-ALL|ERR: get_vfi_from_fwd:1922, XC DB operation failed. Reason: Invalid context 0x51478694 or container type 0

RP/0/RSP0/CPU0:Nov  7 01:34:18.928 : l2vpn_mgr[1154]: DBG-ALL: get_atom_segment_state:444, No redundancy role, state 2
RP/0/RSP0/CPU0:Nov  7 01:34:18.928 : l2vpn_mgr[1154]: DBG-ALL: get_atom_segment_state:444, No redundancy role, state 2
RP/0/RSP0/CPU0:Nov  7 01:34:18.928 : l2vpn_mgr[1154]: DBG-ALL: get_atom_pw_state:522, vc->state = 4
RP/0/RSP0/CPU0:Nov  7 01:34:18.928 : l2vpn_mgr[1154]: DBG-ALL: fill_atom_bag_from_vc:797, PW local binding is set
RP/0/RSP0/CPU0:Nov  7 01:34:18.928 : l2vpn_mgr[1154]: DBG-ALL: fill_atom_bag_from_vc:819, PW remote binding is set
RP/0/RSP0/CPU0:Nov  7 01:34:18.928 : l2vpn_mgr[1154]: DBG-ALL: fill_atom_bag_from_vc:1094, Time PW created 06/11/2014 15:35:54
RP/0/RSP0/CPU0:Nov  7 01:34:18.928 : l2vpn_mgr[1154]: DBG-ALL: fill_atom_bag_from_vc:1151, Time PW last status change 07/11/2014 01:27:13
RP/0/RSP0/CPU0:Nov  7 01:34:18.928 : l2vpn_mgr[1154]: DBG-ALL: fill_pw_bag:3433, Fill the mpls preferred-path info
RP/0/RSP0/CPU0:Nov  7 01:34:18.928 : l2vpn_mgr[1154]: DBG-ALL: fill_l2vpn_xc_segment_info:4007, Number of backup 0, backup_fwd Null
RP/0/RSP0/CPU0:Nov  7 01:34:18.928 : l2vpn_mgr[1154]: DBG-ALL: fill_l2vpn_xc_segment_info:4090, (pwhe:numero1): XC state 1, AC state 4, Primary state 2, backup state 0, seg1_state 4, seg2_state 2, fwd1_type 1, fwd2_type 2
RP/0/RSP0/CPU0:Nov  7 01:34:18.928 : l2vpn_mgr[1154]: DBG-ALL: fill_atom_bag_from_vc:794, Dynamic PW over MPLS (AToM)
RP/0/RSP0/CPU0:Nov  7 01:34:18.928 : l2vpn_mgr[1154]: DBG-ALL: l2vpn_edm_datalist_xc:6064, 1 xcs left
RP/0/RSP0/CPU0:Nov  7 01:34:18.928 : l2vpn_mgr[1154]: DBG-ALL: l2vpn_edm_datalist_xc:6033, Filter flags are 0x0
RP/0/RSP0/CPU0:Nov  7 01:34:18.928 : l2vpn_mgr[1154]: DBG-ALL: l2vpn_get_xc_stats_array:1049, AC i/f is 'TenGigE0/0/2/1.1', ispwhe 0, Xcon: 1080001, node: 821
RP/0/RSP0/CPU0:Nov  7 01:34:18.936 : l2vpn_mgr[1154]: DBG-ALL: l2vpn_get_xc_stats_array:1182, get 1 fwd stats = [No error]
RP/0/RSP0/CPU0:Nov  7 01:34:18.942 : l2vpn_mgr[1154]: DBG-ALL: l2vpn_get_xc_stats_array:1265, get 1 fwd stats = [No error]
RP/0/RSP0/CPU0:Nov  7 01:34:18.942 : l2vpn_mgr[1154]: DBG-ALL: l2vpn_get_xc_stats_array:1291, Error backup type
RP/0/RSP0/CPU0:Nov  7 01:34:18.942 : l2vpn_mgr[1154]: DBG-ALL: l2vpn_get_xc_stats_array:1299, get 1 fwd stats = [No error]
RP/0/RSP0/CPU0:Nov  7 01:34:18.942 : l2vpn_mgr[1154]: DBG-ALL: l2vpn_get_xc_stats_array:1321, XC 0: AC-PW XC, copying AC to PW stats
RP/0/RSP0/CPU0:Nov  7 01:34:18.943 : l2vpn_mgr[1154]: DBG-ALL: add_xc_datalist_stats:5915, got 1 stats OK
RP/0/RSP0/CPU0:ASR9001-A#
RP/0/RSP0/CPU0:ASR9001-A#

—————————————————————————————————————————————————————————————————

At the ASR901 side this happen:

ASR901-TEST#show xconnect all
Legend:    XC ST=Xconnect State  S1=Segment1 State  S2=Segment2 State
  UP=Up       DN=Down            AD=Admin Down      IA=Inactive
  SB=Standby  HS=Hot Standby     RV=Recovering      NH=No Hardware

XC ST  Segment 1                         S1 Segment 2                         S2
------+---------------------------------+--+---------------------------------+--
DN pri   ac Gi0/1:14(Eth VLAN)           UP mpls 117.27.118.185:50            DN
ASR901-TEST#

 

ASR901-TEST#sh mpls l2transport vc 50 detail
Local interface: Gi0/1 up, line protocol up, Eth VLAN 14 up
  Destination address: 117.27.118.185, VC ID: 50, VC status: down
    Last error: Remote peer access circuit is down
    Output interface: Vl222, imposed label stack {16002}
    Preferred path: not configured
    Default path: active
    Next hop: 117.27.118.185
  Create time: 06:01:50, last status change time: 22:28:48
    Last label FSM state change time: 06:01:50
  Signaling protocol: LDP, peer 117.27.118.211:0 up
    Targeted Hello: 117.27.118.186(LDP Id) -> 117.27.118.185, LDP is UP
    Graceful restart: not configured and not enabled
    Non stop routing: not configured and not enabled
    Status TLV support (local/remote)   : enabled/supported
      LDP route watch                   : enabled
      Label/status state machine        : established, LruRrd
      Last local dataplane   status rcvd: No fault
      Last BFD dataplane     status rcvd: Not sent
      Last BFD peer monitor  status rcvd: No fault
      Last local AC  circuit status rcvd: No fault
      Last local AC  circuit status sent: DOWN(pw-tx-fault)
      Last local PW i/f circ status rcvd: No fault
      Last local LDP TLV     status sent: No fault
      Last remote LDP TLV    status rcvd: DOWN(pw-tx-fault)
      Last remote LDP ADJ    status rcvd: No fault
    MPLS VC labels: local 19, remote 16002
    Group ID: local 0, remote 67109248
    MTU: local 1504, remote 1504
    Remote interface description: TenGigE0_0_2_1.1
  Sequencing: receive disabled, send disabled
  Control Word: Off
  Dataplane:
    SSM segment/switch IDs: 8222/4125 (used), PWID: 1
  VC statistics:
    transit packet totals: receive 0, send 0
    transit byte totals:   receive 0, send 0
    transit packet drops:  receive 0, seq error 0, send 0


ASR901-TEST#

 

ASR901-TEST#

Nov  7 15:24:59.319: XC[12000005:GigabitEthernet0/1:]: i/f 200000007D000005 remove pending unprov
Nov  7 15:24:59.319: XC[12000005:GigabitEthernet0/1:]: Provision pending for i/f 200000007D000005
Nov  7 15:24:59.319: XC[12000005:GigabitEthernet0/1:]: Provisioning forwarder
Nov  7 15:24:59.319: XC VPWS[12000005:Gi0/1:14]: Member allocated, priority 0
Nov  7 15:24:59.319: XC VPWS[12000005:Gi0/1:14]: Added primary member into left memberlist
Nov  7 15:24:59.319: XC VPWS[12000005:Gi0/1:14]: Alloc switch 4125
Nov  7 15:24:59.319: XC VPWS[12000005:Gi0/1:14]: Provision client, service 12000005, i/f 200000007D000005
Nov  7 15:24:59.319: XC VPWS[12000005:Gi0/1:14]: Circuit attributes to client:
Nov  7 15:24:59.319: XC VPWS[12000005:Gi0/1:14]:  Status: DOWN(hard-down, not-ready) (0xC0)
Nov  7 15:24:59.319: XC VPWS[12000005:Gi0/1:14]:  Circuit directive: Go Active
Nov  7 15:24:59.319: XC VPWS[12000005:Gi0/1:14]:  Switch handle: 4125
Nov  7 15:24:59.319: XC[12000005:117.27.118.185:50]: Provision pending for i/f 9CA7
Nov  7 15:24:59.319: XC[12000005:117.27.118.185:50]: Provisioning forwarder
Nov  7 15:24:59.319: XC VPWS[12000005]: Setting member as part of slave group
Nov  7 15:24:59.319: XC VPWS[12000005:117.27.118.185:50]: Member allocated, priority 0
Nov  7 15:24:59.319: XC VPWS[12000005:117.27.118.185:50]: Added primary member into right memberlist
Nov  7 15:24:59.319: XC VPWS[12000005:117.27.118.185:50]: Use peer's switch 4125
Nov  7 15:24:59.319: XC VPWS[12000005:117.27.118.185:50]: Retrieving cached circuit attributes from peer
Nov  7 15:24:59.319: XC VPWS[12000005:117.27.118.185:50]: Provision client, service 12000005, i/f 9CA7
Nov  7 15:24:59.319: XC VPWS[12000005:117.27.118.185:50]: Circuit attributes to client:
Nov  7 15:24:59.323: XC VPWS[12000005:117.27.118.185:50]:  Status: DOWN(hard-down, not-ready) (0xC0)
Nov  7 15:24:59.323: XC VPWS[12000005:117.27.118.185:50]:  Circuit directive: Go Active
Nov  7 15:24:59.323: XC VPWS[12000005:117.27.118.185:50]:  Switch handle: 4125
Nov  7 15:24:59.327: XC: MPLS peer 117.27.118.185 vcid 50, VC state DOWN, PW Err
Nov  7 15:24:59.327: XC: MPLS peer 117.27.118.185 vcid 50, VC state ADMIN DOWN
Nov  7 15:24:59.327: XC VPWS[12000005:Gi0/1:14]: Update, i/f 200000007D000005
Nov  7 15:24:59.327: XC VPWS[12000005:Gi0/1:14]: Circuit attributes from client:
Nov  7 15:24:59.327: XC VPWS[12000005:Gi0/1:14]:  Interface handle: 0x200000007D000005
Nov  7 15:24:59.327: XC VPWS[12000005:Gi0/1:14]:  Status: UP (0x1)
Nov  7 15:24:59.327: XC VPWS[12000005:Gi0/1:14]:  Alarm: 0x0
Nov  7 15:24:59.327: XC VPWS[12000005:Gi0/1:14]:  Payload encap: Eth VLAN
Nov  7 15:24:59.327: XC VPWS[12000005:Gi0/1:14]:  Circuit Encap: Eth VLAN
Nov  7 15:24:59.327: XC VPWS[12000005:Gi0/1:14]:  Interworking type: none
Nov  7 15:24:59.331: XC VPWS[12000005:Gi0/1:14]:  Segment type: Vlan
Nov  7 15:24:59.331: XC VPWS[12000005:Gi0/1:14]:  XC packet match: 0x0
Nov  7 15:24:59.331: XC VPWS[12000005:Gi0/1:14]:  MTU: 1504
Nov  7 15:24:59.331: XC VPWS[12000005:Gi0/1:14]:  VLAN ID: 14
Nov  7 15:24:59.331: XC VPWS[12000005:Gi0/1:14]:  I/F Str: Gi0/1
Nov  7 15:24:59.331: XC VPWS[12000005:Gi0/1:14]:  Circuit string: 14
Nov  7 15:24:59.331: XC VPWS[12000005:Gi0/1:14]: Received status change, status is UP
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]: Client needs switch handle
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]: Circuit attributes to client:
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]:  Interface handle: 0x200000007D000005
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]:  Status: UP (0x1)
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]:  Alarm: 0x0
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]:  Payload encap: Eth VLAN
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]:  Circuit Encap: Eth VLAN
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]:  Interworking type: none
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]:  Segment type: Vlan
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]:  Switch handle: 4125
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]:  XC packet match: 0x0
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]:  MTU: 1504
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]:  VLAN ID: 14
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]:  I/F Str: Gi0/1
Nov  7 15:24:59.331: XC VPWS[12000005:117.27.118.185:50]:  Circuit string: 14
Nov  7 15:24:59.335: XC: MPLS peer 117.27.118.185 vcid 50, VC state DOWN
Nov  7 15:24:59.339: XC: MPLS peer 117.27.118.185 vcid 50, VC state DOWN, PW Err
Nov  7 15:24:59.343: XC VPWS[12000005:117.27.118.185:50]: Update, i/f 9CA7
Nov  7 15:24:59.343: XC VPWS[12000005:117.27.118.185:50]: Circuit attributes from client:
Nov  7 15:24:59.343: XC VPWS[12000005:117.27.118.185:50]:  Interface handle: 0x9CA7
Nov  7 15:24:59.343: XC VPWS[12000005:117.27.118.185:50]:  Status: DOWN(pw-tx-fault) (0x20)
Nov  7 15:24:59.343: XC VPWS[12000005:117.27.118.185:50]:  Payload encap: Eth VLAN
Nov  7 15:24:59.343: XC VPWS[12000005:117.27.118.185:50]:  Circuit Encap: Eth VLAN
Nov  7 15:24:59.347: XC VPWS[12000005:117.27.118.185:50]:  VCCV CC: 0x6
Nov  7 15:24:59.347: XC VPWS[12000005:117.27.118.185:50]:  Segment type: AToM
Nov  7 15:24:59.347: XC VPWS[12000005:117.27.118.185:50]:  Control Word: no
Nov  7 15:24:59.347: XC VPWS[12000005:117.27.118.185:50]:  Fast Switchover: yes
Nov  7 15:24:59.347: XC VPWS[12000005:117.27.118.185:50]:  MTU: 1504
Nov  7 15:24:59.347: XC VPWS[12000005:117.27.118.185:50]:  VLAN ID: 0
Nov  7 15:24:59.347: XC VPWS[12000005:117.27.118.185:50]:  I/F Str: pw100003
Nov  7 15:24:59.347: XC VPWS[12000005:117.27.118.185:50]:  Circuit string: 117.27.118.185:50
Nov  7 15:24:59.347: XC VPWS[12000005:117.27.118.185:50]: Received status change, status is DOWN(pw-tx-fault)
Nov  7 15:24:59.347: XC VPWS[12000005:Gi0/1:14]: Client needs switch handle
Nov  7 15:24:59.347: XC VPWS[12000005:Gi0/1:14]: Circuit attributes to client:
Nov  7 15:24:59.347: XC VPWS[12000005:Gi0/1:14]:  Interface handle: 0x9CA7
Nov  7 15:24:59.347: XC VPWS[12000005:Gi0/1:14]:  Status: DOWN(pw-tx-fault) (0x20)
Nov  7 15:24:59.347: XC VPWS[12000005:Gi0/1:14]:  Payload encap: Eth VLAN
Nov  7 15:24:59.347: XC VPWS[12000005:Gi0/1:14]:  Circuit Encap: Eth VLAN
Nov  7 15:24:59.347: XC VPWS[12000005:Gi0/1:14]:  VCCV CC: 0x6
Nov  7 15:24:59.347: XC VPWS[12000005:Gi0/1:14]:  Segment type: AToM
Nov  7 15:24:59.347: XC VPWS[12000005:Gi0/1:14]:  Switch handle: 4125
Nov  7 15:24:59.347: XC VPWS[12000005:Gi0/1:14]:  Control Word: no
Nov  7 15:24:59.347: XC VPWS[12000005:Gi0/1:14]:  Fast Switchover: yes
Nov  7 15:24:59.347: XC VPWS[12000005:Gi0/1:14]:  MTU: 1504
Nov  7 15:24:59.347: XC VPWS[12000005:Gi0/1:14]:  VLAN ID: 0
Nov  7 15:24:59.347: XC VPWS[12000005:Gi0/1:14]:  I/F Str: pw100003
Nov  7 15:24:59.351: XC VPWS[12000005:Gi0/1:14]:  Circuit string: 117.27.118.185:50
Nov  7 15:24:59.351: XC VPWS[12000005:117.27.118.185:50]: Update, i/f 9CA7
Nov  7 15:24:59.351: XC VPWS[12000005:117.27.118.185:50]: Circuit attributes from client:
Nov  7 15:24:59.351: XC VPWS[12000005:117.27.118.185:50]:  Payload encap: Eth VLAN
Nov  7 15:24:59.351: XC VPWS[12000005:Gi0/1:14]: Send active circuit attributes
Nov  7 15:24:59.351: XC VPWS[12000005:Gi0/1:14]: Circuit attributes to client:
Nov  7 15:24:59.351: XC VPWS[12000005:Gi0/1:14]:  Payload encap: Eth VLAN
Nov  7 15:24:59.351: XC VPWS[12000005:117.27.118.185:50]: Update, i/f 9CA7
Nov  7 15:24:59.351: XC VPWS[12000005:117.27.118.185:50]: Circuit attributes from client:
Nov  7 15:24:59.351: XC VPWS[12000005:117.27.118.185:50]:  Payload encap: Eth VLAN
Nov  7 15:24:59.351: XC VPWS[12000005:117.27.118.185:50]:  VLAN ID: 0
Nov  7 15:24:59.351: XC VPWS[12000005:117.27.118.185:50]:  Loadbalance mode: None
Nov  7 15:24:59.351: XC VPWS[12000005:117.27.118.185:50]:  Loadbalance Flow class: none
Nov  7 15:24:59.351: XC VPWS[12000005:Gi0/1:14]: Send active circuit attributes
Nov  7 15:24:59.351: XC VPWS[12000005:Gi0/1:14]: Circuit attributes to client:
Nov  7 15:24:59.351: XC VPWS[12000005:Gi0/1:14]:  Payload encap: Eth VLAN
Nov  7 15:24:59.351: XC VPWS[12000005:Gi0/1:14]:  VLAN ID: 0
Nov  7 15:24:59.351: XC VPWS[12000005:Gi0/1:14]:  Loadbalance mode: None
Nov  7 15:24:59.351: XC VPWS[12000005:Gi0/1:14]:  Loadbalance Flow class: none
Nov  7 15:24:59.351: XC VPWS[12000005:117.27.118.185:50]: Update, i/f 9CA7
Nov  7 15:24:59.351: XC VPWS[12000005:117.27.118.185:50]: Circuit attributes from client:
Nov  7 15:24:59.351: XC VPWS[12000005:117.27.118.185:50]:  Payload encap: Eth VLAN
Nov  7 15:24:59.351: XC VPWS[12000005:Gi0/1:14]: Send active circuit attributes
Nov  7 15:24:59.355: XC VPWS[12000005:Gi0/1:14]: Circuit attributes to client:
Nov  7 15:24:59.355: XC VPWS[12000005:Gi0/1:14]:  Payload encap: Eth VLAN
Nov  7 15:24:59.355: XC VPWS[12000005:117.27.118.185:50]: Update, i/f 9CA7
Nov  7 15:24:59.355: XC VPWS[12000005:117.27.118.185:50]: Circuit attributes from client:
Nov  7 15:24:59.355: XC VPWS[12000005:117.27.118.185:50]:  Payload encap: Eth VLAN
Nov  7 15:24:59.355: XC VPWS[12000005:117.27.118.185:50]:  VLAN ID: 0
Nov  7 15:24:59.355: XC VPWS[12000005:117.27.118.185:50]:  Loadbalance mode: None
Nov  7 15:24:59.355: XC VPWS[12000005:117.27.118.185:50]:  Loadbalance Flow class: none
Nov  7 15:24:59.355: XC VPWS[12000005:Gi0/1:14]: Send active circuit attributes
Nov  7 15:24:59.355: XC VPWS[12000005:Gi0/1:14]: Circuit attributes to client:
Nov  7 15:24:59.355: XC VPWS[12000005:Gi0/1:14]:  Payload encap: Eth VLAN
Nov  7 15:24:59.355: XC VPWS[12000005:Gi0/1:14]:  VLAN ID: 0
Nov  7 15:24:59.355: XC VPWS[12000005:Gi0/1:14]:  Loadbalance mode: None
Nov  7 15:24:59.355: XC VPWS[12000005:Gi0/1:14]:  Loadbalance Flow class: none
Nov  7 15:24:59.359: XC VPWS[12000005:Gi0/1:14]: Update, i/f 200000007D000005
Nov  7 15:24:59.359: XC VPWS[12000005:Gi0/1:14]: Circuit attributes from client:
Nov  7 15:24:59.359: XC VPWS[12000005:Gi0/1:14]:  Payload encap: Eth VLAN
Nov  7 15:24:59.359: XC VPWS[12000005:Gi0/1:14]:  Circuit Encap: Eth VLAN
Nov  7 15:24:59.359: XC VPWS[12000005:Gi0/1:14]:  Interworking type: none
Nov  7 15:24:59.359: XC VPWS[12000005:Gi0/1:14]:  Segment type: Vlan
Nov  7 15:24:59.359: XC VPWS[12000005:Gi0/1:14]:  XC packet match: 0x0
Nov  7 15:24:59.359: XC VPWS[12000005:Gi0/1:14]:  MTU: 1504
Nov  7 15:24:59.359: XC VPWS[12000005:Gi0/1:14]:  VLAN ID: 14
Nov  7 15:24:59.359: XC VPWS[12000005:Gi0/1:14]:  Circuit string: 14
Nov  7 15:24:59.359: XC VPWS[12000005:117.27.118.185:50]: Send active circuit attributes
Nov  7 15:24:59.359: XC VPWS[12000005:117.27.118.185:50]: Circuit attributes to client:
Nov  7 15:24:59.363: XC VPWS[12000005:117.27.118.185:50]:  Payload encap: Eth VLAN
Nov  7 15:24:59.363: XC VPWS[12000005:117.27.118.185:50]:  Circuit Encap: Eth VLAN
Nov  7 15:24:59.363: XC VPWS[12000005:117.27.118.185:50]:  Interworking type: none
Nov  7 15:24:59.363: XC VPWS[12000005:117.27.118.185:50]:  Segment type: Vlan
Nov  7 15:24:59.363: XC VPWS[12000005:117.27.118.185:50]:  XC packet match: 0x0
Nov  7 15:24:59.363: XC VPWS[12000005:117.27.118.185:50]:  MTU: 1504
Nov  7 15:24:59.363: XC VPWS[12000005:117.27.118.185:50]:  VLAN ID: 14
Nov  7 15:24:59.363: XC VPWS[12000005:117.27.118.185:50]:  Circuit string: 14

ASR901-TEST#

ASR901-TEST#

 

 

 

 

5 REPLIES
New Member

Hello,

Hello,

You can establish the PW between the two attachment circuits with mismatched VLAN tags using the command  under the ASR900 EVC

remote circuit id 101

As below:

 

ASR9000:

l2vpn

pw-class gia1
    encapsulation mpls
       protocol ldp
       transport-mode vlan

xconnect group pwhe
   p2p numero1
     interface TenGigE0/0/2/1.1
     neighbor ipv4 117.27.118.186 pw-id 50
         pw-class gia1

 

interface TenGigE0/0/2/1.1 l2transport
   encapsulation dot1q 200

 

ASR901:

pseudowire-class num1
   encapsulation mpls
   no control-word
!
interface GigabitEthernet0/1
 mtu 1504
 no ip address
 negotiation auto
 service instance 1 ethernet
    encapsulation dot1q 14
     xconnect 117.27.118.185 50 encapsulation mpls pw-class num1

     remote circuit id 200

 

Solution 2:

Also if you need to do the rewrite yourself, you can use the rewrite ingress tag translate 1-1 from the ASR9000 side

 

please update us by the status

 

thanks

 

 

 

 

New Member

Hi,

Hi,

 

unfortuantely i discovred that the command "     remote circuit id 200" isn't available under the EVC Xconnect configuration on ASR900 routers.

 

could you please try the second solution and inform u, by only use the below command under the ASR9000 AC

rewrite ingress tag translate 1-1 dot1q 14 symmetric

 

then remove the rewite-tag command from the PW-class, also the rewrite command from the ASR900 EVC to be as below :

 

ASR9000:

 

l2vpn

pw-class gia1
    encapsulation mpls
       protocol ldp

xconnect group pwhe
   p2p numero1
     interface TenGigE0/0/2/1.1
     neighbor ipv4 117.27.118.186 pw-id 50
         pw-class gia1

 

interface TenGigE0/0/2/1.1 l2transport
   encapsulation dot1q 200

       rewrite ingress tag translate 1-1 dot1q 14 symmetric

 

 

ASR900

pseudowire-class num1
   encapsulation mpls
   no control-word
!
interface GigabitEthernet0/1
 mtu 1504
 no ip address
 negotiation auto
 service instance 1 ethernet
    encapsulation dot1q 14
     xconnect 117.27.118.185 50 encapsulation mpls pw-class num1

 

Please update us by the status

New Member

Hi,  thankyou for you answer.

Hi,

  thankyou for you answer. Your suggestions are very helpful for me. However, the problem remain.

See above for my solution.

 

Thankyou

 

New Member

Summary:  I'm trying to setup

Update:  I'm trying to setup an L2VPN  with xconnect between an ASR9000 (5.1.3) and an ASR900 (15.4(2)S1).
I have these errors:

1. At the ASR9000 side I have the error "ReasonInvalid context 0x51478694 or container type 0"
2. At the ASR900 side I have the error "Last error: Remote peer access circuit is down"

I made new tests in lab. The network is very simple. The ASR's are connected back to back. So I'm using explicit-null.

I understand that the message n.1 is not an error. I find that also in a working EoMPLS connection between an ASR9000 and an ASR1000...

The error number 2 told me that the remote peer access circuit is down. In my case the remote circuit is perfectly UP!

The verification test is made using a LSP Ping for VCCV, that is basically the same of "ping mpls ipv4 ...".

You can see that using the  command"show l2vpn xconnect detail":
...
 VCCV CV type 0x2                            0x2
                   (LSP ping verification)        (LSP ping verification)
...

This verification test fail in my lab.

So all my problems seems to be related to MPLS label binding.
Router is unable to reach the EoMPLS end point.

In my new lab I have this configuration:

l2vpn
 pw-class gia1
  encapsulation mpls
   protocol ldp
   transport-mode vlan
  !
 !
 xconnect group pwhe
  p2p numero1
   interface GigabitEthernet0/0/0/6.1
   neighbor ipv4 192.168.201.1 pw-id 50
    pw-class gia1
   !
  !
 !
!
mpls oam
!
mpls ldp
 router-id 192.168.200.1
 address-family ipv4
  label
   local
    advertise
     interface GigabitEthernet0/0/0/5
     interface GigabitEthernet0/0/0/5.1
     explicit-null
    !
   !
  !
 !

192.168.201.1 is the tunnel endpoint. The problem here is that I have an "Unlabelled" instead of "Exp-Null-v4"!

RP/0/RSP0/CPU0:9001#show mpls forwarding
Sat Nov 15 06:22:16.995 UTC
Local  Outgoing    Prefix             Outgoing     Next Hop        Bytes
Label  Label       or ID              Interface                    Switched
------ ----------- ------------------ ------------ --------------- ------------
20000  Pop         PW(192.168.201.1:50)   \
                                      Gi0/0/0/6.1  point2point     0
20001  Unlabelled  192.168.201.0/24   Gi0/0/0/5    192.168.210.2   0
20002  Unlabelled  192.168.201.1/32   Gi0/0/0/5    192.168.210.2   74

RP/0/RSP0/CPU0:LENTINI#show mpls ldp bindings
...
        192.168.201.1/32, rev 157
        Local binding: label: 20002
        Remote bindings: (1 peers)
            Peer                Label
            -----------------   ---------
            192.168.201.1:0     ExpNullv4
...

 

RP/0/RSP0/CPU0:9001#ping 192.168.201.1
Sat Nov 15 06:25:54.351 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.201.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/2 ms

But the endpoint is not be reached by MPLS:

RP/0/RSP0/CPU0:9001#ping mpls ipv4 192.168.201.1/32
Sat Nov 15 06:27:53.699 UTC

Sending 5, 100-byte MPLS Echos to 192.168.201.1/32,
      timeout is 2 seconds, send interval is 0 msec:

Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
  'L' - labeled output interface, 'B' - unlabeled output interface,
  'D' - DS Map mismatch, 'F' - no FEC mapping, 'f' - FEC mismatch,
  'M' - malformed request, 'm' - unsupported tlvs, 'N' - no rx label,
  'P' - no rx intf label prot, 'p' - premature termination of LSP,
  'R' - transit router, 'I' - unknown upstream index,
  'X' - unknown return code, 'x' - return code 0

Type escape sequence to abort.

QQRP/0/RSP0/CPU0:Nov 15 06:27:53.841 : lspv_server[1096]: [1] ERR-Pkt: : Failed to lookup forwarding info for IPv4 prefix 192.168.201.1/32
QQQ
Success rate is 0 percent (0/5)
RP/0/RSP0/CPU0:Nov 15 06:27:53.841 : lspv_server[1096]: [1] ERR-Pkt: : Failed to get label stack, phy out intf and nexthop for IPv4 FEC
RP/0/RSP0/CPU0:Nov 15 06:27:53.841 : lspv_server[1096]: [1] DBG-Event: : Null pointer is passed for free if chain
RP/0/RSP0/CPU0:Nov 15 06:27:53.843 : lspv_server[1096]: [1] ERR-Pkt: : Failed to lookup forwarding info for IPv4 prefix 192.168.201.1/32
RP/0/RSP0/CPU0:LENTINI_9001#RP/0/RSP0/CPU0:Nov 15 06:27:53.843 : lspv_server[1096]: [1] DBG-Event: : Null pointer is passed for free if chain
RP/0/RSP0/CPU0:Nov 15 06:27:53.843 : lspv_server[1096]: [1] ERR-Pkt: : Failed to get label stack, phy out intf and nexthop for IPv4 FEC
RP/0/RSP0/CPU0:Nov 15 06:27:53.844 : lspv_server[1096]: [1] ERR-Pkt: : Failed to lookup forwarding info for IPv4 prefix 192.168.201.1/32
RP/0/RSP0/CPU0:Nov 15 06:27:53.844 : lspv_server[1096]: [1] ERR-Pkt: : Failed to get label stack, phy out intf and nexthop for IPv4 FEC
RP/0/RSP0/CPU0:Nov 15 06:27:53.844 : lspv_server[1096]: [1] DBG-Event: : Null pointer is passed for free if chain
RP/0/RSP0/CPU0:Nov 15 06:27:53.845 : lspv_server[1096]: [1] ERR-Pkt: : Failed to lookup forwarding info for IPv4 prefix 192.168.201.1/32
RP/0/RSP0/CPU0:Nov 15 06:27:53.845 : lspv_server[1096]: [1] DBG-Event: : Null pointer is passed for free if chain
RP/0/RSP0/CPU0:Nov 15 06:27:53.845 : lspv_server[1096]: [1] ERR-Pkt: : Failed to get label stack, phy out intf and nexthop for IPv4 FEC
RP/0/RSP0/CPU0:Nov 15 06:27:53.847 : lspv_server[1096]: [1] ERR-Pkt: : Failed to lookup forwarding info for IPv4 prefix 192.168.201.1/32
RP/0/RSP0/CPU0:Nov 15 06:27:53.847 : lspv_server[1096]: [1] ERR-Pkt: : Failed to get label stack, phy out intf and nexthop for IPv4 FEC
RP/0/RSP0/CPU0:Nov 15 06:27:53.847 : lspv_server[1096]: [1] DBG-Event: : Null pointer is passed for free if chain

 

So I have the error:

Failed to lookup forwarding info for IPv4 prefix 192.168.201.1/32

But the 192.168.201.1 is reachable as you can see above.

Any suggestions?

Thankyou

New Member

 

 

Ok, I found a workaround.
Since ASR9000 refuse to use explicit-null notification from ASR 900 I use a static label.
All is working now but I think there is an IOS bug here.

mpls static
  interface GigabitEthernet0/0/0/5
   address-family ipv4 unicast
    local-label 30000 allocate per-prefix 192.168.201.1/32
    forward
    path 1 nexthop GigabitEthernet0/0/0/5 192.168.210.2 out-label exp-null
   !

Now the forwarding table is right, MPLS PING works and the L2VPN tunnel goes UP.

RP/0/RSP0/CPU0: 9001#show mpls forwarding
Sat Nov 15 16:09:32.895 UTC
Local  Outgoing    Prefix             Outgoing     Next Hop        Bytes
Label  Label       or ID              Interface                    Switched
------ ----------- ------------------ ------------ --------------- ------------
16000  Unlabelled  192.168.201.0/24   Gi0/0/0/5    192.168.210.2   0
16001  Pop         PW(192.168.201.1:50)   \
                                      Gi0/0/0/6.1  point2point     0
30000  Exp-Null-v4 192.168.201.1/32   Gi0/0/0/5    192.168.210.2   4294

 

1057
Views
4
Helpful
5
Replies
CreatePlease to create content