E1 is not working in ASR 920 Router by using VLL line from ISP.

MustafaBinAmar0901 · ‎06-20-2021

Hi,

we are using ASR 920 Router to connect two branch and ISP give us VLL (virtual leased line). We connected this two (Branch) router with VLL we can telnet and ping this router (Connectivity is OK) but E1 is not working on both the router.

I will share below configuration for Branch 1 and Branch 2. Please if any one can assist in this.

Branch1 Configuration:

Branch1#sh run
Building configuration...

Current configuration : 3735 bytes
!
! Last configuration change at 03:32:51 UTC Sun Jun 13 2021
!
version 16.8
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no platform punt-keepalive disable-kernel-core
platform bfd-debug-trace 1
platform xconnect load-balance-hash-algo mac-ip-instanceid
platform tcam-parity-error enable
platform tcam-threshold alarm-frequency 1
!
hostname Riyadh_VLL
!
boot-start-marker
boot-end-marker
!
!
vrf definition Mgmt-intf
!
address-family ipv4
exit-address-family
!
address-family ipv6
exit-address-family
!
card type e1 0 1
no logging console
enable secret 5 $1$.C7M$yS/ua/qS8E2r5STOCpVbo1
!
no aaa new-model
!
!
!
!
!
!
!
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
mpls label protocol ldp
!
!
multilink bundle-name authenticated
license udi pid ASR-920-12SZ-IM
license boot level advancedmetroipaccess
no license smart enable
!
!
spanning-tree mode pvst
spanning-tree extend system-id
sdm prefer default
diagnostic bootup level minimal
!
!
!
redundancy
!
!
!
!
!
controller E1 0/1/0
framing unframed
cem-group 0 unframed
!
controller E1 0/1/1
framing unframed
cem-group 1 unframed
!
controller E1 0/1/2
framing unframed
cem-group 2 unframed
!
controller E1 0/1/3
shutdown
!
controller E1 0/1/4
shutdown
!
controller E1 0/1/5
shutdown
!
controller E1 0/1/6
shutdown
!
controller E1 0/1/7
shutdown
!
!
transceiver type all
monitoring
cdp run
!
!
class cem mycemclass
payload-size 512
dejitter-buffer 10
idle-pattern 0x55
!
!
!
!
!
!
!
!
!
!
!
interface Loopback0
ip address 1.1.1.19 255.255.255.255
!
interface GigabitEthernet0/0/0
no ip address
media-type rj45
negotiation auto
mpls ip
service instance 1 ethernet
encapsulation dot1q 2251
rewrite egress tag push dot1q 2251
bridge-domain 2251
!
!
interface GigabitEthernet0/0/1
no ip address
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0/2
no ip address
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0/3
no ip address
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0/4
no ip address
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0/5
no ip address
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0/6
no ip address
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0/7
no ip address
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0/8
no ip address
negotiation auto
!
interface GigabitEthernet0/0/9
no ip address
negotiation auto
!
interface GigabitEthernet0/0/10
no ip address
negotiation auto
!
interface GigabitEthernet0/0/11
no ip address
negotiation auto
!
interface TenGigabitEthernet0/0/12
no ip address
!
interface TenGigabitEthernet0/0/13
no ip address
!
interface TenGigabitEthernet0/0/14
no ip address
!
interface TenGigabitEthernet0/0/15
no ip address
!
interface GigabitEthernet0
vrf forwarding Mgmt-intf
ip address 10.10.10.119 255.255.255.0
negotiation auto
!
interface CEM0/1/0
no ip address
cem 0
xconnect 1.1.1.18 118 encapsulation mpls
cem class mycemclass
!
!
interface CEM0/1/1
no ip address
cem 1
xconnect 1.1.1.18 119 encapsulation mpls
cem class mycemclass
!
!
interface CEM0/1/2
no ip address
cem 2
xconnect 1.1.1.18 120 encapsulation mpls
cem class mycemclass
!
!
interface BDI2251
ip address 192.168.99.1 255.255.255.0
encapsulation dot1Q 2251
mpls ip
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
ip tftp source-interface GigabitEthernet0
ip route 1.1.1.18 255.255.255.255 192.168.99.2
!
!
mpls ldp router-id Loopback0 force
!
!
control-plane
!
!

Branch 2 Configuration:

Branch 2 #sh run
Building configuration...

Current configuration : 3660 bytes
!
! Last configuration change at 23:04:28 UTC Sun Jun 13 2021
!
version 16.8
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no platform punt-keepalive disable-kernel-core
platform bfd-debug-trace 1
platform xconnect load-balance-hash-algo mac-ip-instanceid
platform tcam-parity-error enable
platform tcam-threshold alarm-frequency 1
!
hostname Test
!
boot-start-marker
boot-end-marker
!
!
vrf definition Mgmt-intf
!
address-family ipv4
exit-address-family
!
address-family ipv6
exit-address-family
!
card type e1 0 1
enable secret 5 $1$fpPD$GhGSZceTcybW3vYcO8P22.
!
no aaa new-model
!
!
!
!
!
!
!
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
mpls label protocol ldp
!
!
multilink bundle-name authenticated
license udi pid
license boot level advancedmetroipaccess
no license smart enable
!
!
spanning-tree mode pvst
spanning-tree extend system-id
sdm prefer default
diagnostic bootup level minimal
!
!
!
redundancy
!
!
!
!
!
controller E1 0/1/0
framing unframed
cem-group 0 unframed
!
controller E1 0/1/1
framing unframed
cem-group 1 unframed
!
controller E1 0/1/2
framing unframed
cem-group 2 unframed
!
controller E1 0/1/3
!
controller E1 0/1/4
!
controller E1 0/1/5
!
controller E1 0/1/6
!
controller E1 0/1/7
!
!
transceiver type all
monitoring
cdp run
!
!
class cem mycemclass
payload-size 512
dejitter-buffer 10
idle-pattern 0x55
!
!
!
!
!
!
!
!
!
!
!
interface Loopback0
ip address 1.1.1.18 255.255.255.255
!
interface GigabitEthernet0/0/0
no ip address
media-type rj45
negotiation auto
mpls ip
service instance 1 ethernet
encapsulation dot1q 2476
rewrite egress tag push dot1q 2476
bridge-domain 2476
!
!
interface GigabitEthernet0/0/1
no ip address
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0/2
no ip address
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0/3
no ip address
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0/4
no ip address
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0/5
no ip address
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0/6
no ip address
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0/7
no ip address
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0/8
no ip address
negotiation auto
!
interface GigabitEthernet0/0/9
no ip address
negotiation auto
!
interface GigabitEthernet0/0/10
no ip address
negotiation auto
!
interface GigabitEthernet0/0/11
no ip address
negotiation auto
!
interface TenGigabitEthernet0/0/12
no ip address
!
interface TenGigabitEthernet0/0/13
no ip address
!
interface TenGigabitEthernet0/0/14
no ip address
!
interface TenGigabitEthernet0/0/15
no ip address
!
interface GigabitEthernet0
vrf forwarding Mgmt-intf
ip address 10.10.10.118 255.255.255.0
negotiation auto
!
interface CEM0/1/0
no ip address
cem 0
xconnect 1.1.1.19 118 encapsulation mpls
cem class mycemclass
!
!
interface CEM0/1/1
no ip address
cem 1
xconnect 1.1.1.19 119 encapsulation mpls
cem class mycemclass
!
!
interface CEM0/1/2
no ip address
cem 2
xconnect 1.1.1.19 120 encapsulation mpls
cem class mycemclass
!
!
interface BDI2476
ip address 192.168.99.2 255.255.255.0
encapsulation dot1Q 2476
mpls ip
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
ip tftp source-interface GigabitEthernet0
ip route 1.1.1.19 255.255.255.255 192.168.99.1
!
!
mpls ldp router-id Loopback0 force
!
!
control-plane
!
!

so If any one can assist me.

Thanks.

Richard Burts · ‎06-20-2021

I do not have experience with this technology, and if someone who does have experience would jump into the discussion it would be good. But it looks to me like this is a "virtual" leased line and I suspect that you do not need the physical interfaces to make it work. The connectivity is supplied by the G0/0/0 interfaces and BDI. If you can ping and telnet between sites it looks to me like you should be good to go. Is there anything that is not working, other than the E1 interfaces?

HTH

Rick

MustafaBinAmar0901 · ‎06-21-2021

Hi Richard,

Thanks for Support ,Yes only E1 is having issues.

Thanks.

Giuseppe Larosa · ‎06-20-2021

Hello @MustafaBinAmar0901 ,

it would be helpful if you :

a) if you would use the same VLAN -ID on both branches.

I see two different VLAN-Ids used here Branch 1 VLAN 2251, Branch 2 uses VLAN 2476

Who performs VLAN ID rewrite ? The PE Node ? But in this case the ISP must be aware of what you are doing.

b) you can run an OSPF process on the shared subnet 192.168.99.0/24 using it to publish the loopbacks.

At this point your circuit emulation configuration CEM may start to work as each of them can be compared to an EoMPLS pseudowires . These are point to point L2 services but LDP must run on the devices and an IGP as far as I know is needed.

Branch1 :

router ospf 10

network 192.168.99.0 0.0.0.255 area 0

network 1.1.1.1.19 0.0.0.0 area 0

Branch 2:

router ospf 10

network 192.168.99.0 0.0.0.255 area 0

network 1.1.1.1.18 0.0.0.0 area 0

When you define the pseudowire you need to point to the remote loopback IP address and to use a shared VC label for each of them.

Check with show mpls forwarding 1.1.1.18 on Branch1 the correct action is POP TaG = implicit null

on Branch 2 show mpls forwarding 1.1.1.19 should show the same POP TAG

The local E1 interfaces need to be connected to real E1 circuits to work.

Start by enabling OSPF and checking LDP .

Hope to help

Giuseppe

MustafaBinAmar0901 · ‎06-21-2021

Hi,

Thanks for support. Actually ISP provided that VLAN number, If we change that VLAN then Pinging Both Branch router Stop.

Regarding IGP before I configure OSPF as you told but we have same issues. See the above configuration is working fine if we use VPLS line from ISP. We check that, But for in VLL line, E1 is not working and in this two Branchs (Connectivity is ok but E1 is not working).

and see the output of command as you mention above.

Branch 1#sh mpls forwarding 1.1.1.18
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
19 No Label 1.1.1.18/32 0 BD2251 192.168.99.2

Branch2#sh mpls forwarding 1.1.1.19
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
19 No Label 1.1.1.19/32 0 BD2476 192.168.99.1

Please find the below attached output for Both Branch's.

Please advise

Thanks.

Giuseppe Larosa · ‎06-21-2021

Hello @MustafaBinAmar0901 ,

>> Actually ISP provided that VLAN number,

I had thought of it later after my first post.

>> See the above configuration is working fine if we use VPLS line from ISP.

Either there is MTU issue with VLL service or it drops MPLS frames.

Ask the ISP if you can send MPLS frames over the VLL service if the answer is no you have found the reason why the circuit emulation over MPLS is not working with VLL.

Hope to help

Giuseppe

MustafaBinAmar0901 · ‎06-21-2021

Hi Giuseppe,

We ask ISP he is saying that he provided Layer 2 circuit. He is saying what every configuration we want to do we can do no issues.

Can you give me some more steps to check is there MTU issues or any other thing etc.

Thanks.

MustafaBinAmar0901 · ‎06-22-2021

Hi,

I check with ISP he is saying he give PLL line (no VLL). They are saying PLL layer 2 circuit.

Please advise if you can help me in this.

Thanks.

Giuseppe Larosa · ‎06-22-2021

Hello @MustafaBinAmar0901 ,

check with the new service PLL.

As a way to check an easier to troubleshoot service you can add a L3 MPLS VPN between Branch1 and Branch2 using dedicated loopbacks in VRF .

If this service will work , then the MPLS forwarding plane will be OK and you can move on checking the CEM over MPLS.

This is my suggestion because it is enough to use a ping test in vrf to check if the MPLS L3 VPN works. You need to add also MP BGP between the loopbacks of Branch1 and Branch2 in address-family vpnv4 and ipv4 vrf <name>.

Hope to help

Giuseppe

MustafaBinAmar0901 · ‎06-22-2021

Hi Giuseppe,

I have little bit confused. I have access to only my two CISCO Router ASR 920 one is in Brach 1 and other is in Branch 2.

can you please share configuration as you will mention above.

Thanks.