On Tue, Sep 06, 2016 at 07:50:47AM +0000, Bogaert, Bart (Nokia - BE) wrote: > > [Bart Bogaert] When sending a configuration request to a device while > there is no HW physically present yet is what we call pre-provisioning > meaning that the configuration is made up-front in attendance of the > HW being plugged at a later stage. When the plugged HW does not meet > the pre-configured data I think it is normal that an alarm is raised > but that does not take away the fact that the device was configured in advance. >
In your example, there is nothing configured as far as I can tell. The way the interfaces data model supports pre-configuration is by having a _name binding_; a pre-configured interface is applied once the name of the pre-configured interfaces matches the name of a (physical) interface. I think Martin is asking the question whether the same model of using name bindings can be applied in your case and if not why not. [Bart Bogaert] I'm afraid I am lost in the names being used here. Whether it's called name binding or pre-configuration or still something else, the key point is that we configure objects in the device prior to them being physically present, nothing more, nothing less. The consequence of this being that these objects should be present in the data tree of the device and once the HW gets plugged all operational data linked to that comes into existence too. I do not know of another way to explain what is intended with what we call 'pre-configuration'. /Bart /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
