cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
926
Views
0
Helpful
2
Replies

service creation is not sent to devices

erdemk
Level 1
Level 1

Hello,

 

I am connected to physical devices.

I have created a template based service.

When i try to create a service instance , it says it is created as shown below. but there is no config change on the router side.

May you point me to a direction for troubleshoot this case or tell me a method to debug ?

 

Many thanks in advance.

 

below : yang model, template and screen output while creating the service

note: i have not yet implemented spoke part of the yang file into the template

 

screen output

admin@ncs(vpn-dmvpn-hub)# commit dry-run
cli {
local-node {
data vpn {
+ dmvpn saab {
+ tunnel-id 12;
+ hub {
+ device asr920-3;
+ tunnel-source {
+ interface-name GigabitEthernet;
+ port-number 0/0/5;
+ }
+ tunnel-ip-address {
+ tunnel-ip-address 192.168.2.167;
+ tunnel-ip-address-mask 255.255.255.0;
+ }
+ tunnel-key 7;
+ bandwidth 800;
+ }
+ }
}
}
}
admin@ncs(vpn-dmvpn-hub)# commit
Commit complete.
admin@ncs(vpn-dmvpn-hub)#
admin@ncs#

 

ang model : 

module dmvpn {

namespace "http://com/example/dmvpn";
prefix dmvpn;

import ietf-inet-types {
prefix inet;
}

import tailf-common {
prefix tailf;
}

import tailf-ncs {
prefix ncs;
}

grouping source-grouping {
leaf interface-name {
tailf:info "Interface name. GigabitEthernet or TenGigabitEthernet";
type string;
}
leaf port-number {
tailf:info "Port number. For example 0/0/3";
type string;
}
}

grouping tunnel-ip-address-grouping {
leaf tunnel-ip-address {
tailf:info "A.B.C.D";
type inet:ipv4-address;
}
leaf tunnel-ip-address-mask {
tailf:info "A.B.C.D";
type inet:ipv4-address;
}
}

container vpn {

list dmvpn {
description "Dynamic Multipoint VPN";

key name;
leaf name {
tailf:info "Unique service name";
tailf:cli-allow-range;
type string;
}

uses ncs:service-data;
ncs:servicepoint "dmvpn-template";

leaf tunnel-id {
description "descTunnel interface number";
tailf:info "infoTunnel interface number";
type uint32;
}

leaf ip-nhrp-authentication {
description "descWORD ip nhrp authentication string";
tailf:info "infoauthentication string";
type string;
}

leaf tunnel-mode-gre {
description "desc-multipoint or ip or ipv6";
tailf:info "info-multipoint or ip or ipv6";
type string;
}

leaf ip-tcp-adjust-mss {
description "descMax segment size in bytes";
tailf:info "infoMax segment size in bytes";
type uint32;
}

leaf ip-nhrp-hold-time {
description "descNumber of seconds";
tailf:info "infoNumber of seconds";
type uint32;
}

leaf delay {
description "descThroughput delay ( tens of miliseconds )";
tailf:info "infoThroughput delay ( tens of miliseconds )";
type uint32;
}

container hub {
tailf:cli-add-mode;
tailf:cli-mode-name "vpn-dmvpn-hub";

leaf device {
mandatory true;
type leafref {
path "/ncs:devices/ncs:device/ncs:name";
}
}

container tunnel-source {
tailf:cli-compact-syntax;
uses source-grouping;
}

container tunnel-ip-address {
tailf:cli-compact-syntax;
uses tunnel-ip-address-grouping;
}

leaf tunnel-key {
description "key";
tailf:info "infoSelector key";
type uint32;
}

leaf bandwidth {
description "descBandwidth in kilobits";
tailf:info "infoBandwidth in kilobits";
type uint32;
}
}

container spoke {
tailf:cli-add-mode;
tailf:cli-mode-name "vpn-dmvpn-spoke";

leaf tunnel-key {
description "key";
tailf:info "infoSelector key";
type uint32;
}

leaf bandwidth {
description "descBandwidth in kilobits";
tailf:info "infoBandwidth in kilobits";
type uint32;
}
}
}
}
}

 

template : 

<config-template xmlns="http://tail-f.com/ns/config/1.0"
servicepoint="dmvpn-template">
<devices xmlns="http://tail-f.com/ns/ncs">
<device tags="nocreate">
<name>{hub/device}</name>
<config tags="merge">
<interface xmlns="urn:ios">
<Tunnel>
<name>{tunnel-id}</name>
<bandwidth>
<kilobits>{hub/bandwidth}</kilobits>
</bandwidth>
<ip>
<address>
<primary>
<address>{hub/tunnel-ip-address/tunnel-ip-address}</address>
<mask>hub/tunnel-ip-address/tunnel-ip-address-mask}</mask>
</primary>
</address>
<redirects>false</redirects>
<nhrp>
<authentication>{ip-nhrp-authentication}</authentication>
<map>
<multicast>
<dynamic/>
</multicast>
</map>
<holdtime>{ip-nhrp-hold-time}</holdtime>
</nhrp>
<tcp>
<adjust-mss>{ip-tcp-adjust-mss}</adjust-mss>
</tcp>
</ip>
<delay>{delay}</delay>
<tunnel>
<source>{hub/tunnel-source/interface-name}{hub/tunnel-source/port-number}</source>
<mode>
<gre>
<multipoint>
</multipoint>
</gre>
</mode>
<key>{tunnel-key}</key>
</tunnel>
</Tunnel>
</interface>
</config>
</device>
</devices>
</config-template>

 

1 Accepted Solution

Accepted Solutions

vleijon
Cisco Employee
Cisco Employee

I would suggest using commit dry-run | debug service or | debug template to see what is happening.

View solution in original post

2 Replies 2

vleijon
Cisco Employee
Cisco Employee

I would suggest using commit dry-run | debug service or | debug template to see what is happening.

Thanks for reply.

There was a problem with context node..

I resolved the issue now.

 

Polls
AI-powered tools for network troubleshooting are likely to be part of everyone’s workflow sooner or later. What is the single biggest challenge or concern you see with adopting these tools in your organization?