T.R | Title | User | Personal Name | Date | Lines |
---|
1700.1 | Use the Show command !! 8) | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Wed Oct 23 1991 17:36 | 18 |
| #1 You cannot have multiple rules with the same name .. You didn't
try that - did you ?
#2 If the Create commands is:
Create mcc 0 alarms rule foo expr=(node4 rome maximum address > 50)
Then the show command is:
Show mcc 0 alarms rule foo all characteristics
#3 You cannot specify multiple entities (ie, multiple rule names) in
a directive - but Alarms does support FULL wildcards:
Show mcc 0 alarms rule * all characteristics
/keith
|
1700.2 | ???? | MCIS5::ENSLEY | | Thu Oct 24 1991 10:38 | 5 |
| RE:
#1 How then can I test the circuit_substate on multiple nodes?
#2 I thought an "entity" were devices like Nodes or Bridges?
|
1700.3 | Maybe I'm not helping 8( | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Thu Oct 24 1991 11:03 | 30 |
| >> How then can I test the circuit_substate on multiple nodes?
You have to create multiple rules !!
Create mcc 0 alarms rule circuit_substate_ROME -
expr=(node4 rome ...)
Create mcc 0 alarms rule circuit_substate_PARIS -
expr=(node4 paris ...)
Enable mcc 0 alarms rule circuit_substate_ROME
Enable mcc 0 alarms rule circuit_sutstate_PARIS
If Global wildcards was available [ but for v1.2 it won't be 8( ]
you could put your nodes of interest in a domain, and enable
a rule with a global wildcard and the domain. All the nodes in the
domain would be tested -- with a single rule --
>> I thought an "entity" were devices like Nodes or Bridges?
Yes those are entities -- but so isn't an Alarm Rule too. The entity
model for Alarms is:
MCC <instance name>
Alarms <null-instance>
Rule <instance name>
Does this make it any clearer?
/keith
|
1700.4 | Thanks. | MCIS5::ENSLEY | | Thu Oct 24 1991 11:37 | 3 |
| Yes, thanks.
Taking me a while to get used to all the nomenclature DECmcc uses!!
|
1700.5 | DECmcc has a lot of new terms | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Thu Oct 24 1991 12:41 | 6 |
| >> Taking me a while to get used to all the nomenclature DECmcc uses!!
YES! DECmcc does define a lot of new terms, and it takes a bit to understand
them ...
/keith
|
1700.6 | create domain rule (name) domain dependent name | TOOK::CALLANDER | MCC = My Constant Companion | Thu Nov 21 1991 13:10 | 15 |
| I know this is a bit late,
note that you can create rules of the same name, as long as
they are defined for different domains.
Either :
create mcc 0 alarm rule foo ....., in domain bar
create mcc 0 alarm rule foo .... , in domain bar2
or
create domain bar rule foo ...
create domain bar2 rule foo ...
|