How to deal with automatic generated parameters

[Gastonper]

Hi,

Some network devices have this particulary behavior when you configure them, that if you skip some numeric parameter, the device automatically creates one for you. For example, in Nokia 7750 devices, you can set the lacp administrative-key, or you can just skip it, and the device create one for you.

This generate a problem whit NSO services, making them out-of-sync inmediately after the create.

For exmple, if I have a service to configure lag interfaces, and I dont want to specifically set the administrative-key, in the create proceses NSO send the following to the device:

    lag XXX
        no shutdown
        description "bla,bla,bla"
        mode access
        encap-type qinq
        lacp active
    exit

But after I do a device sync-from, this is what I get:

    lag XXX
        no shutdown
        description "bla,bla,bla"
        mode access
        encap-type qinq
        lacp active dministrative-key 32780
    exit

At this point, doing a check-sync of the service will result in a false state.

This happend not only with this type of device/service, but with other as well. So, the question is:

Is there a way to handle this kind of problem at a service level, or is the NED the one who has to know how to deal with this kind of parameters.

[rogaglia · Accepted solution]

Hi,

The normal behavior would be for you or the NED to do everything possible to not let the device be out-of-sync after a commit.

So, one basic questions is: "do you absolutely need the device to auto-assign the parameter?" If the answer is no, just assign it in your template. One example are macros to configure for example vlans: vlan1-12 , just don't use them!.

If the answer is "yes" (you must support this behavior), the NED should resolve the problem for you. This is typically done via a ned-setting. Please review the NED README file as there may be the case that someone already asked for this behavior.

If you do not find anything in the README file (I checked and I believe there is not a solution to your problem), please raise a TAC ticket to discuss with support.