Marcel and list- The daemon didn't account for new devices or interfaces at first. :-) What we have now is a version with three watches - changes to attribute on existing models, new devices added, and new interfaces/modules added. When a new device is added, we add a watch for its attributes, and when a new interface or module is added, we find its parent and copy the attributes from it.
As much fun as it was to build this, I'd happily replace it with Policy Manager if you find a way to do so. Good luck, Jim On 1/26/11 11:27 AM, "Marcel Schulte" <[email protected]> wrote: > Hi Jim, list, > > thanks for your reply! > > I already had an idea to configure a watch keeping track of the > attribute and starting a script if value changes. Sounds like exactly > what your daemon does, doesn't it? > > But this watch would only fire if attribute changes - what if Spectrum > discovers a new module in a switch and models new ports...? When will > they get the attribute value? Does your daemon cover this? > > For now my intention is this: > > 1. Watch starting a script which inherits the attribute value to the > childs if attribute value changes on device level > 2. Maybe a policy in PolicyMgr inheriting attribute value to childs > for every device having set this attribute > > ...but if anybody knows a better way I'd appreciate your hints. > > Regards, > Marcel > > > On Wed, Jan 26, 2011 at 5:22 PM, Pfleger, Jim <[email protected]> wrote: >> We had this exact problem, and ended up building a daemon with the CORBA >> toolkit that listens for changes to the parent and pushes them to the >> children. I know you said that you don't have the toolkit, but it was the >> only solution we came up with. We looked into Policy Manager, but you cannot >> use it to modify attributes on one model based on changes to another model. >> You could probably build something similar with SANM by listening for >> attribute changes, but you would have to make those events into alarms. Your >> SANM script would then recurse through the model's children, setting the >> attribute, and finally clear the attribute change alarm. >> >> HTH, >> Jim >> >> >> -- >> JIM PFLEGER | Application Architect | Insight | insight.com >> >> t. 480.889.9680 f. 480.889.9599 [email protected] >> >> >> >> >> On 1/26/11 4:36 AM, "Marcel Schulte" <[email protected]> wrote: >> >>> Hi users, >>> >>> I'd like to do this: >>> >>> 1. implement an attribute which is available in all device- and >>> subcomponent-modeltypes >>> 2. if the attribute is changed at device level all the device's >>> subcomponents are changed automatically >>> >>> I searched in documentation and ModelTypeEditor but did not found any >>> hint in inheriting attribute values between models. >>> >>> Did anyone of you do something similar and would share experiences? >>> >>> Many thanks in advance! >>> >>> Kind regards, >>> Marcel >>> >>> P.S.: we currently use Spectrum 9.2H03, no Corba Toolkit >>> >>> --- >>> To unsubscribe from spectrum, send email to [email protected] with the body: >>> unsubscribe spectrum [email protected] >> >> > > --- > To unsubscribe from spectrum, send email to [email protected] with the body: > unsubscribe spectrum [email protected] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
