| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4573.1 | From the Alarms FM perspective ... | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Fri Feb 19 1993 07:52 | 13 |
| Fran�ois,
From the perspective of the Alarms FM ... Alarms uses the Entity spec
as you specified it in the Rule Expression. I imagine that you are
using a DNS full name(?) The entity spec is passed to the Management
Module which in this case is converting the DNS Full Name to a form
which it can use to directly communicate with the entity. But, because
the entity was never 'fully' registered, an error is returned during
the conversion; the Management Module then returns the error to Alarms.
What kind of entity were you registering?
/keith
|
| 4573.2 | Station entity | STRAS4::EBLE | Fran�ois EBLE. EIS Strasbourg France. | Mon Mar 08 1993 09:53 | 11 |
| Keith,
I tried it with a station entity. With this kind of entity what is the result of
the conversion from a DNS full name ? In the partial registration the Ethernet
address is given and the Alternate Ethernet address also, so why is it impossible
to put an alarm on this entity ?
Thanks for your answer.
Fran�ois.
|
| 4573.3 | Station 'Full Names' are converted to Ethernet Addresses | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Mon Mar 15 1993 16:08 | 49 |
|
Fran�ois,
>> With this kind of entity what is the result of the conversion from
>> a DNS full name ?
The DNS full name for the Station entity is converted to the Ethernet
Address.
---------
Below, I have attempted to register a ficticious 'Station' entity.
The register command failed with 'Cannot communicate with target'.
Subsequent 'Show' directives return the 'Insufficient information...'
error .. even though I gave the Stations ethernet address.
Alarms uses the same 'Show' directive and therefore returned the same
'Insufficient information...' error. This is why your rule is failing.
The solution?
Re-register your Station entity. The registration must be successful
before the Alarm Rule (the Show directive) will work correctly. Also,
if the Register directive fails, it will tell you why.
Ok ?
/keith
------------------------------------------------------------------------
MCC> register station fester address 08-00-2b-00-33-22
Station LOCAL_NS:.fester
AT 15-MAR-1993 15:59:08
Partial registration success. Please retry later to complete the registration.
Reason for Partial Registration = Cannot communicate with target
------------------------------------------------------------------------
MCC> show station fester all count
Station LOCAL_NS:.fester
AT 15-MAR-1993 16:00:06 Counters
Insufficient information, entity has only been partially registered
------------------------------------------------------------------------
|
| 4573.4 | use address instead of fullname | GOSTE::CALLANDER | | Mon Mar 15 1993 17:32 | 5 |
| modify your rule to specify the address and the rule will enable
and if the device is available it will run. Otherwise partial or
fully registered, it won't make a difference, only boxes that respond
and keep a rule active.
|