How can I reload the rebuilded NED with licence status "Development mode: disabled"

[jianx2]

I'm trying to add some codes to the yang file "tailf-ned-cisco-nx.yang" as follows with red color. My cisco-nx version is v5.7.1.

This part of codes was removed after v4.1.13 probably. I just want to enable it.

container allowed {
        tailf:info "Set allowed VLAN characteristics when interface "+
          "is in trunking mode";
        // interface * / switchport trunk allowed vlan
        container vlan {
          tailf:info "Set allowed VLANs when interface is in trunking mode (NOTE: this is not a presence, only used internally)";
          tailf:cli-delete-when-empty;
          tailf:cli-display-separated;
          tailf:cli-diff-dependency "../../../mode";
          presence true; // NOTE: this is not a presence, only used internally
          choice vlan-choice {
            leaf fixed {
              // Note: Must not be leaf with type empty, breaks java code!
              tailf:cli-drop-node-name;
              type enumeration {
                // interface * / switchport trunk allowed vlan all
                enum "all" {
                  tailf:info "All VLANs";
                }
                // interface * / switchport trunk allowed vlan none
                enum "none" {
                  tailf:info "No VLANs";
                }
              }
            }
            leaf-list ids {
              tailf:cli-drop-node-name;
              tailf:cli-range-list-syntax;
              type vlan-list-type;
            }
          }
        }

  It looks like I can build it successfully, running "request package reload" successfully, but I can't find the "all" option in NSO webui.

But in my test env, not prod env, with license status "Development mode: enable", it's working fine.

Any ideas about it, thanks.

Scott

[yfherzog]

If you were able to build it (running 'make' under the NED src directory), and then were able to reload packages, and you still cannot see the changes, then first couple of things I would be checking is:

1. Whether the code you've changed is actually the one controlling the node you're looking to change - it might be that it's a similar block but in some other part of the model.

2. Whether the package you've been modifying is the one which actually sits in your packages directory. If you reload packages from the cli, and changes were made to the data model, you'd see something like this in the output:

>>> System upgrade is starting.
>>> Sessions in configure mode must exit to operational mode.
>>> No configuration changes can be performed until upgrade has completed.
>>> System upgrade has completed successfully.

If you don't see it, then no changes to the data model were made in the current packages you're loading comparing to the current one.