| Hi Dave,
I can't answer whether you can retarget a partially registered entity but
you may have options. If retargeting these options does in fact turn out
to be not achievable then you can try the following:
1. Represent the non-communicative IP nodes as REFERENCE entities
2. When targeting you should be able to use the wildcards in the target
command to hit these objects. Register them with the same name and use
the same technique for wildcarding you used with DECnet objects except
the TARGET will now be REFERENCE #2 or whatever.
The other option is to use the data collector which has a built in TARGETing
mechanism. Again, register them as REFERENCE entities and you should have no
problem hitting them. Also note it probably won't matter to your custormer
that the objects aren't IP on the map because MCC can't talk to them
anyway.
Either option is worth a try.
best regards,
brad...
|
| Hi Brad,
Thanks for helping me out again!
Your first suggestion of setting up reference nodes and targeting them seems
the way to go. Having never targeted using SNMP, I'm a little confused. In
referring to pages 3-22 & 3-23 in the Alarms Funcion manual, the domain entry
seems pretty straight forward. However, I'm not too sure about Event Source
and Event name entries. Mainly, because I'm interested in a table value that
is being returned from the agent on B, as per the diagram in .0. I've expanded
the Event name field, and none of the choices seem what I want. Furthermore, I
have a rule set up that turns A or C red which ever is applicable. It reads:
SNMP Local_NS:.ip.A sys_test Table 7 state=off. I also have a rule for .ip.C.
There are several states that each machine can be in, so I guess I'll have to
create a rule for each of the states for each machine. This involves creating
a large amount of rules, unless there is another way. Anyway, it doesn't look
like any of the Event Name choices apply. Then when I look at Exhibit 3-18,
it looks like I can specify a rule name, but the event name is OSI Rule Fire,
and I don't see a SNMP Rule Fire choice. But if Local_NS:.ip.A sys_test Table
7 state=off is a configuration event then maybe I can setup something like in
Exhibit 3-19. So, I'm confused as to how to proceed to assign targets.
Assigning Targets in DECnet phase IV was so much easier. Please Help!!
Thanks,
/Dave
|
| FYI, for anybody who cares,
I spoke to Dave and what we tried was to bring the TABLE CHILD entity up to
the global level using the toolbox. Because each of the nodes being monitored
is described by a different TABLE <num> then bringing each of them up and out
onto the map allows for easy determination of which one has the outage. This
seems to have worked (targets not even needed).
best regards,
brad...
|