Thanks a lot for the reply.
This was not a design choice, I was trying out few callback interfaces.
The create callback was also implemented.
The reason I said the callback is not reaching is, I had put logs in these callback methods and I could not see them in "ncs-java-vm.log".
The Yang that is being used is,
module mplstunnel {
namespace "urn:temp:mpls:mplstunnel";
prefix mplstunnel;
import ietf-inet-types {
prefix inet;
}
import tailf-ncs {
prefix ncs;
}
typedef tunnel-type {
type enumeration{
enum "mpls-tp" {
value 0;
description "mpls-tp";
}
}
description "tunnel type";
}
typedef direction {
type enumeration {
enum "forward"{
value 0;
description "forward";
}
enum "reverse"{
value 1;
description "reverse";
}
}
}
typedef tunnel-direction-type {
type enumeration {
enum "unidirectional" {
value 0;
description "unidirectional";
}
enum "corouted-bidirectional" {
value 1;
description "co-routed-bidirectional";
}
enum "associate-bidirectional" {
value 2;
description "associate-bidirectional";
}
}
description "tunnel direction type";
}
grouping tunnel-path{
leaf in-label{
type uint32 {
range "200001..300000";
}
mandatory "true";
description "Static in label for tunnel";
}
leaf in-interface{
type uint16 {
range "1..4096";
}
mandatory "true";
description "VLan ID";
}
leaf tunnel-in-direction{
type direction;
mandatory "true";
description "Direction of the packet flow";
}
leaf out-label{
type uint32 {
range "200001..300000";
}
mandatory "true";
description "Static in label for tunnel";
}
leaf out-interface{
type uint16 {
range "1..4096";
}
mandatory "true";
description "VLan ID";
}
}
augment /ncs:services {
list mplstunnel {
key tunnel-id;
uses ncs:service-data;
ncs:servicepoint mplstunnel-servicepoint;
leaf tunnel-id {
type uint16{
range "0..4096";
}
mandatory "true";
description "MPLS Tunnel Identifier";
}
leaf-list device {
type leafref {
path "/ncs:devices/ncs:device/ncs:name";
}
}
leaf source {
type string {
length "0..50";
}
mandatory "true";
description "Source node ID of the tunnel";
}
leaf destination{
type string {
length "0..50";
}
mandatory "true";
description "Destination node ID of the tunnel";
}
leaf tunnel-type{
type tunnel-type;
default "mpls-tp";
description "tunnel type";
}
leaf tunnel-mode {
type tunnel-direction-type;
mandatory "true";
description "The object indicates the direction of tunnel";
}
container forward-path{
uses tunnel-path;
}
container reverse-path{
uses tunnel-path;
}
leaf lsp-id{
type uint16 {
range "0..4096";
}
mandatory "true";
description "LSP ID";
}
}
}
}
Regards
Sarath
