|
This type specifies the target Managed Object (MO) or MO Class (MOC) that a rule applies to.
Entire sub-trees can be addressed as well as attributes and actions defined for a specific MO or MOC. Patterns are used for this purpose according to simplified regular expression syntax. Any regular expression can also be defined but must be identified as such using a specific prefix.
MOCs are specified in their containment hierarchy separated by commas “,”. For example: “ManagedElement,ApplFuncX”.
MOs are specified using the 3GPP DN notation, with the exception that the same rule may mix MO and MOC, such as “ManagedElement, ApplFuncX=1”. Omitting the instance Id is the preferred notation for singleton MOCs, which makes the rule applicable for all ManagedElement instances. Thus rule design becomes independent of system implementation for singleton MOC types.
If the naming attribute is not the same as the MO Class name + “Id”, the naming attribute is in accordance with the 3GPP part of the DN as well. This means that if ApplFuncX naming attribute is xyz, then the DN is “ManagedElement,ApplFuncX.xyz=2”. However, it is not required nor forbidden to use this more elaborate form of DN. The naming attribute xyz can be omitted.
Attributes and actions are specified after the MO or MOC separated by a dot “.”. Since the ‘,’ character is allowed in the naming attribute of MO of 3GPP DNs, escaping must be used if the character occurs in an attribute value by the reverse solidus (‘\’) character. Several attributes or actions can be specified for the same MO or MOC separated by the the bar “|” character.
The rule applies to a single MO or MOC and all its attributes and actions unless the following notation is used:
...,MOC.* The rule applies to all attributes and actions that belong to the MO Class, but not to the MOC itself.
...,MOC,* The rule applies to the MOC and all its attributes and actions and all contained (child) MOCs and their attribute and actions.
(DEPRECATED: ...,MOC$ The rule applies only to the MOC itself and not to its attributes and actions.)
The above notations are also valid for MOs and must close an expression.
In addition, the ruleData attribute can specify any Perl Compatible Regular Expressions. These regular expressions must only be used by CLI command modules for tailored commands or by Netconf modules for Netconf operations. The permitted content is specified by the CLI and Netconf documentation. The only general restriction to these kinds of rule data is that they must start with “:cli:regexp:” or “:netconf:regexp:” plus a different expression from the wild card “.*”.
Examples:
1) Entire MO tree, that is the rule will match all Managed Objects:
ManagedElement,*
2) Only MOs and their attributes and actions of ManagedElement MOC:
ManagedElement
3) (Deprecated) Only MOs of ManagedElement MOC but not their attributes and actions:
ManagedElement$
4) A specific MO including singleton parents:
ManagedElement,Equipment,FRU=19
ManagedElement=10\.10\.10\.10
5) An entire sub-tree below that includes a specific MO:
ManagedElement,Equipment,FRU=17,*
6) An entire sub-tree below that includes a specific MO that belongs to an MO class where the naming attribute is not equal to the MOC Name + “Id”. Two examples are given, both are valid and accurately describe the same MO tree:
ManagedElement,Equipment,Abc.xyz=1,*
ManagedElement,Equipment,Abc=1,*
7) All port attributes that belong to MOs of the Boo MOC:
ManagedElement,ApplFuncX,Boo.port
8) All ipAddress and port attributes that belong to MOs of the Boo MO class:
ManagedElement,ApplFuncX,Boo.ipAddress|port
9) Only the port attribute that belongs to a specific instance of the Boo MOC:
ManagedElement,ApplFuncX=1,Boo=17.port
10) The restart action on the ManagedElement MOC:
ManagedElement.restart
11) All CLI commands in the command module group 'System':
:cli:regexp:System-[a-zA-Z0-9]+
or
regexp:System-[a-zA-Z0-9]+
12) Netconf operation <operationx>:
:netconf:regexp:operationx
|