| Is there any plans to allow Wildcards for a Global entity ?
If not how many rule's can I safely setup? I mean I could have 1500 rules
to check one attribute and another 1500 rules to check another. This adds up
in a hurry.
Also when checking a attribute for a software status on a terminal server I
get the following results:
Examination of Attributes shows:
Disable Time: : 28-MAR-1991 17:28:43.64
Error Condition :%MCC-E-ILVTOOBIG, no more room in buffer for
additional values
Result of Last Evalutation: True
State : Disabled
Substate : Disabled by error condition
Apparently the return buffer is to small to handle the the Status error when
one occurs. It has no problem when it returns a "Normal" condition.
Has anyone discovered this problem ? If so are there any patches to handle
this ? I am running the V1.1 SSB DECmcc.
Thanks,
Jim
|
|
>> P.S. Can you reproduce this with the directive: SHOW TERMINAL_SERVER
>> xxx ALL STATUS?
No problem it returns everything just fine:
MCC> show terminal_server LAT801 all status
Terminal_Server DPDMCC_NS:.LAT801
AT 29-MAR-1991 15:41:34 Status
Examination of attributes shows:
Current Active Ports = 0
High Active Ports = 2
Max Active Ports = 8
Current Active Users = 0
High Active Users = 2
Max Active Users = 8
Current CPU Usage = 25 Percent
High CPU Usage = 38 Percent
Max CPU Usage = 100 Percent
Current Memory Usage = 51 Percent
High Memory Usage = 53 Percent
Max Memory Usage = 100 Percent
Minutes to Shutdown = -- Attribute Not Available
Resource Errors = 0
Total Port Framing Errors = 0
Total Port Parity Errors = 0
Total Port Overrun Errors = 1
Primary Host = NOTOUR
Load Address = AA-00-04-00-EC-41
Dump Address = -- Attribute Not Available
Console User = AA-00-04-00-56-40
Software Status = "PC=0067D8, SP=05DA82, SR=002304,
MEM=F84DB9, CODE=003"
Selftest Status = "DA82, "
MCC>
Here is a copy of the rule I was using:
Create MCC 0 ALARMS RULE LAT801_check -
Expression = (Terminal_Server DPDMCC_NS:.LAT801
software status <> "Normal"), -
Procedure = UD3:[MCC]MCC_ALARMS_LOG_ALARM.COM;1, -
Exception Handler = UD3:[MCC]MCC_ALARMS_LOG_EXCEPTION.COM;1, -
Perceived Severity = indeterminate, -
in domain = DPDMCC_NS:.SCA_SER_12_1
ALSO is there any plans to allow wildcarding of global entities ?
Any help.
Thanks,
Jim
BTW: I still haven't found the documentation on how many rules can safely be
run. I have checked the Alarms Manual.
|
| Hi Jim,
I am sorry I have been away from my desk for a while! We did encounter
the problem of insufficient bufffer in the EFT time frame. As far
as we can tell we tested it using TSM at several sites. (I don't have the
set up at my end. I am working on it!). Looks like some thing
fell through the crack. Can we take this off line and report
the problem when we find it? Thanks.
About how process quota: The information is in the release notes
I have enclosed the relevent sections below.
+--------------------------------------------------------------------------+
| 2.8.4.2 Enabling Rules: - |
| |
| The following page file quota (Pgflquo) is recommended for the |
| Alarms FM: |
| |
| Pgflquo = 50000 |
| |
|SOFTWARE NOTES FOR MANAGEMENT MODULES Page 2-24 |
| |
| |
| With a page file quota of 100,000, you can enable up to 100 |
| rules with a polling rate greater than 1 hour. A page file |
| quota of 120,000 lets you enable up to 300 rules with a |
| polling rate greater than 1 hour. |
| |
| |
| NOTE |
| |
| Using a page file quota greater than the |
| actual page file on the system could result in |
| page file fragmentation and possibly cause the |
| VMS system to crash or hang. Related factors |
| include the amount of physical memory |
| available and the memory load on the system by |
| other processes. |
+--------------------------------------------------------------------------+
About Global wild card capbility in Alarms: Sorry but this is some thing
we had to push it out to V2.0. Even if we had implemented this, I am
doubtful if a global entity wild carding on 1500 TS would be possible.
Is it possible for you to partition the problem into number of Domains?
if so, in V1.2 you can enable all rules in a Domain with a wild card.
I.e Enable MCC 0 ALARMS RULE *, IN DOMAIN xyz
The above functionality will be available in V1.2.
$ !-=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=-
$ MANA/ENTER
!
!Can you try following commands and report the result? Thanks.
!
Create MCC 0 ALARMS RULE TEST_1 -
Expression = (Terminal_Server LAT801 Selftest Status = "DA82, " ), -
Procedure = UD3:[MCC]MCC_ALARMS_LOG_ALARM.COM , -
Exception Handler = UD3:[MCC]MCC_ALARMS_LOG_EXCEPTION.COM , -
Perceived Severity = indeterminate , -
in domain = DPDMCC_NS:.SCA_SER_12_1
!-=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=-
!
Create MCC 0 ALARMS RULE TEST_2 -
Expression = (Terminal_Server LAT801 Current Active Ports <> 0), -
Procedure = UD3:[MCC]MCC_ALARMS_LOG_ALARM.COM;1 , -
Exception Handler = UD3:[MCC]MCC_ALARMS_LOG_EXCEPTION.COM;1 , -
Perceived Severity = indeterminate , -
in domain = DPDMCC_NS:.SCA_SER_12_1
!-=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=-
!
Create MCC 0 ALARMS RULE TEST_3 -
Expression = (Terminal_Server LAT801 Primary Host = NOTOUR ) , -
Procedure = UD3:[MCC]MCC_ALARMS_LOG_ALARM.COM , -
Exception Handler = UD3:[MCC]MCC_ALARMS_LOG_EXCEPTION.COM , -
Perceived Severity = indeterminate , -
in domain = DPDMCC_NS:.SCA_SER_12_1
!
!-=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=-
ENABLE MCC 0 ALARMS RULE TEST_1, IN DOMAIN DPDMCC_NS:.SCA_SER_12_1
ENABLE MCC 0 ALARMS RULE TEST_2, IN DOMAIN DPDMCC_NS:.SCA_SER_12_1
ENABLE MCC 0 ALARMS RULE TEST_3, IN DOMAIN DPDMCC_NS:.SCA_SER_12_1
!-=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=-
SHOW MCC 0 ALARMS RULE TEST_1 all att, AT START +00:01:00, IN DOMAIN DPDMCC_NS:.SCA_SER_12_1
SHOW MCC 0 ALARMS RULE TEST_2 all att, IN DOMAIN DPDMCC_NS:.SCA_SER_12_1
SHOW MCC 0 ALARMS RULE TEST_3 all att, IN DOMAIN DPDMCC_NS:.SCA_SER_12_1
!-=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=-
!
EXIT
|
|
>ALSO is there any plans to allow wildcarding of global entities ?
This could depend on exactly what you mean by the phrase: "wildcarding of
global entities". I won't say No for all cases--listing all global entities
in a Domain would be possible for a PM or FM. But in the unlimited general
case, the answer is No. The answer is always "NO!" if you mean a global entity
CLASS wildcard (all global entities, plus all instances of each one), instead
of a global entity INSTANCE wildcard (all instances of this specific global
entity).
Ruth
|
| I am sorry to say - you can not write an Alarm Rule with a global
wildcarded instance. We had hoped to get this into v1.2 but it looks
like it won't make it.
--------------------------
If you're wondering how rules with global wildcards *WOULD HAVE* work:
1) Create a rule with and specify a global wildcard:
create mcc 0 alarms rule myrule -
expr=(node4 * maximum address > 50, at every 01:00:00)
2) Enable the rule for a specified domain
enable mcc 0 alarms rule myrule, in domain mydomain
Alarms would read all the node4's from domain 'mydomain' - then
monitor each one, every 1 hour.
/keith
|