EndNode class
Use this sample EndNode class AOC file to understand how Network Manager assigns discovered devices to the EndNode class.
Sample
The following sample AOC file fragment assigns devices to the EndNode class using the filter defined in the instantiate_rule clause.//*************************************************************
//
// File : EndNode.aoc
//
//*************************************************************
active object 'EndNode'
{
super_class = 'Core';
instantiate_rule = "EntityOID like '1 \.3\.6\.1\.4\.1\.2021\.' OR
EntityOID = '1.3.6.1.4.1.2021' OR
EntityOID = '1.3.6.1.4.1.1575' OR
EntityOID like '1 \.3\.6\.1\.4\.1\.11\.2\.3\.9\.' OR
EntityOID = '1.3.6.1.4.1.11.2.3.9' OR
(EntityType = 1 AND EntityOID IS NULL)
OR
...
OR
(
EntityOID = '1.3.6.1.4.1.1977'
)
OR
(
EntityOID like '1\.3\.6\.1\.4\.1\.2136\.'
)
OR
...
For the EndNode class the instantiate_rule is very
long. It consists of multiple lines comparing the EntityOID, (this
is the sysObjectID of the device), to various values, joined together
by an OR operator. There are different versions of the OR comparison:
- EntityOID = '1.3.6.1.4.1.2021'
- This filter is looking for an exact match of the EntityOID to the value 1.3.6.1.4.1.2021. If the match is not exact, then the comparison fails and the device is not assigned to the EndNode class.
- EntityOID like '1\.3\.6\.1\.4\.1\.11\.2\.3\.9\.'
- This filter is looking for a match like the value 1\.3\.6\.1\.4\.1\.11\.2\.3\.9\. The \. is required to make sure that the . (period) is matched. Also, notice that the value ends in \. This allows matching OIDs that start with the specified value but have additional values following the last . (period) specified.