cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
40
Views
2
Helpful
5
Replies
Highlighted
Cisco Employee

iosxr xconnect ned issue

Hi team,

I have the following config device config:

xconnect group EACCESS

  p2p EACCESS_2764760001

   interface Bundle-Ether100.34

   neighbor ipv4 97.76.237.3 pw-id 27647601

    pw-class RAW-MODE-RPW

   !

  !

!

After my service creation, im adding additional p2p under same xconnect group successfully:

xconnect group EACCESS

  p2p EACCESS_34567830

   interface Bundle-Ether100.3000

   neighbor ipv4 10.0.0.1 pw-id 130345678

    pw-class RAW-MODE-RPW

   !

  !

  p2p EACCESS_2764760001

   interface Bundle-Ether100.34

   neighbor ipv4 97.76.237.3 pw-id 27647601

    pw-class RAW-MODE-RPW

   !

  !

!

Now when I want to delete the service I get the following dry-run to perform:

commit dry-run outformat native

device tlab79-dar2 {

  l2vpn

   no xconnect group EACCESS

  exit

}

This will destroy my other p2p I had previously configured under the xconnect group

Any leads how to handle this would be much appreciated

Noam

Everyone's tags (4)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: iosxr xconnect ned issue

Closing this thread with the solution:

With the assistance from Mike Leske, we found the issue and fixed it

The good device was running XR 5.1.3 and the bad one was running XR 5.3.1

So in 5.3.1 there is an option for redundancy configuration which adds an additional configuration level closing:

l2vpn

logging

  pseudowire

!

pw-class RAW-MODE-PW

  encapsulation mpls

   transport-mode ethernet

  !

!

pw-class ATOM-VLAN-CW

  encapsulation mpls

   control-word

   transport-mode vlan

  !

!

pw-class RAW-MODE-RPW

  encapsulation mpls

   transport-mode ethernet

   redundancy

    one-way

   !

  !

!

xconnect group ELINE

  p2p CM_ACB3-13AC-8EB2

   interface Bundle-Ether100.178

   neighbor ipv4 97.76.237.3 pw-id 178

    pw-class RAW-MODE-RPW

   !

  !

!

This was fixed by modifying the XR NED and adding the following:

container redundancy {

  tailf:cli-add-mode;

  tailf:cli-mode-name "config-l2vpn-pwc-mpls-pw";

  leaf one-way {

    tailf:cli-full-command;

    type empty;

  }

}

Noam

5 REPLIES 5
Cisco Employee

Re: iosxr xconnect ned issue

This is the relevant section from the NED:

    container xconnect {

      tailf:info "Configure cross connect commands";

      // l2vpn / xconnect group *

      list group {

        tailf:info "Specify the group the cross connects belong to";

        tailf:cli-mode-name "config-l2vpn-xc";

        key name;

        leaf name {

          type string {

            tailf:info "WORD;;Name of the cross connects group";

          }

        }

list p2p {

          tailf:info "Configure point to point cross connect commands";

          tailf:cli-mode-name "config-l2vpn-xc-p2p";

          key name;

          leaf name {

            type string {

              tailf:info "WORD;;Name of the point to point cross connect";

            }

          }

          // l2vpn / xconnect group * / p2p * / interface

          list interface {

            tailf:info "Specify the attachment circuit";

            tailf:cli-suppress-mode;

            tailf:cli-delete-when-empty;

            key name;

            leaf name {

              type string {

                tailf:info "WORD;;Interface Name";

              }

            }

          }

tailf-ned-cisco-ios-xr

  revision 2015-05-15 {

    description

      “3.9.0.9

Cisco Employee

Re: iosxr xconnect ned issue

This looks strange - did you execute a sync-from before creating the service - i.e was NCS aware of the previous existence of the /xconnect/group[name='EACCESS'] list entry when the service was created.

Cisco Employee

Re: iosxr xconnect ned issue

Klacke, thanks for the pointer, this is true, the xconnect group will be removed once only one p2p connection exist under the group otherwise it will remove the specific p2p entry for the service

My problem is that one of the XR in the setup doesn’t populate the l2vpn xconnect subtree (that’s why the xconnect group was removed as it was the only one ncs know of) under the device model while it is on other device I will dig further tomorrow try figure why is that

Cisco Employee

Re: iosxr xconnect ned issue

Ok - yes that's how it works.

Remember I wanted you to do show | display service-meta-properties

It didn't show anything, I remember now, that probably only works with the Juniper cli

> switch cli

> show ....

This shows refcounters, and backpointers, try it.

If something exists on the dev, service tries to create it, refcount becomes 2, and then when we del service, the container/list-entry remains

OTOH, the stuff I saw on your setup today still looked real strange.

/klacke

Cisco Employee

Re: iosxr xconnect ned issue

Closing this thread with the solution:

With the assistance from Mike Leske, we found the issue and fixed it

The good device was running XR 5.1.3 and the bad one was running XR 5.3.1

So in 5.3.1 there is an option for redundancy configuration which adds an additional configuration level closing:

l2vpn

logging

  pseudowire

!

pw-class RAW-MODE-PW

  encapsulation mpls

   transport-mode ethernet

  !

!

pw-class ATOM-VLAN-CW

  encapsulation mpls

   control-word

   transport-mode vlan

  !

!

pw-class RAW-MODE-RPW

  encapsulation mpls

   transport-mode ethernet

   redundancy

    one-way

   !

  !

!

xconnect group ELINE

  p2p CM_ACB3-13AC-8EB2

   interface Bundle-Ether100.178

   neighbor ipv4 97.76.237.3 pw-id 178

    pw-class RAW-MODE-RPW

   !

  !

!

This was fixed by modifying the XR NED and adding the following:

container redundancy {

  tailf:cli-add-mode;

  tailf:cli-mode-name "config-l2vpn-pwc-mpls-pw";

  leaf one-way {

    tailf:cli-full-command;

    type empty;

  }

}

Noam

Content for Community-Ad
July's Community Spotlight Awards
This widget could not be displayed.