Juergen Schoenwaelder <[email protected]> wrote:
> On Tue, Sep 06, 2016 at 06:50:02AM +0000, Bogaert, Bart (Nokia - BE) wrote:
> >
> > [Bart Bogaert] Assume we have the following in the device already:
> > <entity>
> > <physical-entity>
> > <model-name>system-1</model-name>
> > <class>ianaent:chassis</class>
> > </physical-entity>
> > </entity>
> >
> > And assume the following is sent as pre-configuration:
> > <entity>
> > <physical-entity>
> > <model-name>dsl-brd-type1</model-name>
> > <class>ianaent:module</class>
> > <parent-rel-pos>2</parent-rel-pos>
> > <contained-in>system-1</contained-in>
> > </physical-entity>
> > </entity>
> >
> > When at a later stage, a board is plugged in the position corresponding to
> > parent-rel-pos 2, the system is able to detect whether the model-name
> > corresponds to dsl-brd-type-1 and accepts the pre-configured values. In
> > case a different model name is detected (e.g. eth-brd-type-1) a mismatch
> > alarm is to be raised indicating that an eth-brd-type-1 has been detected
> > while a dsl-brd-type-1 was expected as the pre-configuration does not match
> > with the actual configuration.
>
> What I see here is an attempt to provide a constraint on operational
> state which may trigger an alarm from the device if the operational
> state is present but different from what was provided as a
> constraint. I do not see pre-configuration here.
I assumed (maybe incorrectly; Bart?) that the example should have been
something like:
<entity>
<physical-entity>
<name>system-1</name>
<model-name>some-model</model-name>
<class>ianaent:chassis</class>
</physical-entity>
</entity>
<entity>
<physical-entity>
<name>dsl-board-1</name>
<model-name>dsl-brd-type1</model-name>
<class>ianaent:module</class>
<parent-rel-pos>2</parent-rel-pos>
<contained-in>system-1</contained-in>
// pre-configuration leafs here
</physical-entity>
</entity>
/martin
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
