This table contains information about each sub-type for
each resource owner in the cermResOwnerTable.
For example, lets consider that the 'memory' resource owner
has two sub-types called 'processor' and 'io' in the system.
Then, two entries (one is for 'processor' memory and another
one is for 'io' memory) will be present in this table for
the 'memory' resource owner.
If a resource owner does not have any sub-types, then
this table will have an entry with the zero value for
the cermResOwnerSubTypeId and zero-length string value
for the cermResOwnerSubTypeName, for the corresponding
resource owner.
Parsed from file CISCO-ERM-MIB.mib
Module: CISCO-ERM-MIB
This table contains information about each sub-type for
each resource owner in the cermResOwnerTable.
For example, lets consider that the 'memory' resource owner
has two sub-types called 'processor' and 'io' in the system.
Then, two entries (one is for 'processor' memory and another
one is for 'io' memory) will be present in this table for
the 'memory' resource owner.
If a resource owner does not have any sub-types, then
this table will have an entry with the zero value for
the cermResOwnerSubTypeId and zero-length string value
for the cermResOwnerSubTypeName, for the corresponding
resource owner.
This table contains information about each sub-type for
each resource owner in the cermResOwnerTable.
For example, lets consider that the 'memory' resource owner
has two sub-types called 'processor' and 'io' in the system.
Then, two entries (one is for 'processor' memory and another
one is for 'io' memory) will be present in this table for
the 'memory' resource owner.
If a resource owner does not have any sub-types, then
this table will have an entry with the zero value for
the cermResOwnerSubTypeId and zero-length string value
for the cermResOwnerSubTypeName, for the corresponding
resource owner.
Parsed from file CISCO-ERM-MIB.my.txt
Company: None
Module: CISCO-ERM-MIB
This table contains information about each sub-type for
each resource owner in the cermResOwnerTable.
For example, lets consider that the 'memory' resource owner
has two sub-types called 'processor' and 'io' in the system.
Then, two entries (one is for 'processor' memory and another
one is for 'io' memory) will be present in this table for
the 'memory' resource owner.
If a resource owner does not have any sub-types, then
this table will have an entry with the zero value for
the cermResOwnerSubTypeId and zero-length string value
for the cermResOwnerSubTypeName, for the corresponding
resource owner.
cermResOwnerSubTypeTable OBJECT-TYPE SYNTAX SEQUENCE OF CermResOwnerSubTypeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains information about each sub-type for each resource owner in the cermResOwnerTable. For example, lets consider that the 'memory' resource owner has two sub-types called 'processor' and 'io' in the system. Then, two entries (one is for 'processor' memory and another one is for 'io' memory) will be present in this table for the 'memory' resource owner. If a resource owner does not have any sub-types, then this table will have an entry with the zero value for the cermResOwnerSubTypeId and zero-length string value for the cermResOwnerSubTypeName, for the corresponding resource owner." ::= { cermStats 2 }
cermResOwnerSubTypeTable OBJECT-TYPE SYNTAX SEQUENCE OF CermResOwnerSubTypeEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table contains information about each sub-type for each resource owner in the cermResOwnerTable. For example, lets consider that the 'memory' resource owner has two sub-types called 'processor' and 'io' in the system. Then, two entries (one is for 'processor' memory and another one is for 'io' memory) will be present in this table for the 'memory' resource owner. If a resource owner does not have any sub-types, then this table will have an entry with the zero value for the cermResOwnerSubTypeId and zero-length string value for the cermResOwnerSubTypeName, for the corresponding resource owner." ::= { cermStats 2 }
Vendor: Cisco
Module: CISCO-ERM-MIB
[Automatically extracted from oidview.com]
cermResOwnerSubTypeTable OBJECT-TYPE SYNTAX SEQUENCE OF CermResOwnerSubTypeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains information about each sub-type for each resource owner in the cermResOwnerTable. For example, lets consider that the 'memory' resource owner has two sub-types called 'processor' and 'io' in the system. Then, two entries (one is for 'processor' memory and another one is for 'io' memory) will be present in this table for the 'memory' resource owner. If a resource owner does not have any sub-types, then this table will have an entry with the zero value for the cermResOwnerSubTypeId and zero-length string value for the cermResOwnerSubTypeName, for the corresponding resource owner." ::= { cermStats 2 }
cermResOwnerSubTypeTable OBJECT-TYPE SYNTAX SEQUENCE OF CermResOwnerSubTypeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains information about each sub-type for each resource owner in the cermResOwnerTable. For example, lets consider that the 'memory' resource owner has two sub-types called 'processor' and 'io' in the system. Then, two entries (one is for 'processor' memory and another one is for 'io' memory) will be present in this table for the 'memory' resource owner. If a resource owner does not have any sub-types, then this table will have an entry with the zero value for the cermResOwnerSubTypeId and zero-length string value for the cermResOwnerSubTypeName, for the corresponding resource owner." ::= { cermStats 2 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.9.9.510.1.2.2.1 | cermResOwnerSubTypeEntry | 6 | 6 | An entry containing information about a resource owner sub-type. This entry includes resource owner sub-type name, utilization in… |
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.9.9.510.1.2.1 | cermResOwnerTable | 1 | 8 | This table contains information about each resource owner in the system. Each resource owner maintains a list of resource users a… |
1.3.6.1.4.1.9.9.510.1.2.3 | cermResOwnerSubTypeThresholdTable | 1 | 6 | This table contains information about each applied global threshold configuration for each resource owner sub-type in the system. |
1.3.6.1.4.1.9.9.510.1.2.4 | cermResUserTypeTable | 1 | 7 | This table contains information about each resource user type in the system. This table will have one entry for each resource use… |
1.3.6.1.4.1.9.9.510.1.2.5 | cermResUserTable | 1 | 5 | A table which contains information about each resource user in the system. This table will have one entry for each resource user … |
1.3.6.1.4.1.9.9.510.1.2.6 | cermResGroupTable | 1 | 4 | This table contains information about each resource group in the system. This table will have one entry for each resource group i… |
1.3.6.1.4.1.9.9.510.1.2.7 | cermResGroupResUserTable | 1 | 2 | This table has list of resource users present in each resource group. |
1.3.6.1.4.1.9.9.510.1.2.8 | cermResOwnerResUserOrGroupTable | 1 | 9 | This table contains information about each resource owner sub-type and resource user/group relationship. |
1.3.6.1.4.1.9.9.510.1.2.9 | cermResOwnerResUserOrGroupThresholdTable | 1 | 8 | This table contains information about each applied threshold configuration for each resource owner sub-type <-> resource user/group …-> |
1.3.6.1.4.1.9.9.510.1.2.10 | cermResUserTypeResOwnerTable | 1 | 2 | This table contains an entry for each resource user type and resource owner relationship in the system. This table would be usefu… |
1.3.6.1.4.1.9.9.510.1.2.11 | cermResMonitorTable | 1 | 4 | This table contains information about each resource monitor in the system. |
1.3.6.1.4.1.9.9.510.1.2.12 | cermResMonitorResOwnerResUserTable | 1 | 5 | This table contains the following information: 1) resource owners being watched by each resource monitor. 2) resource users being… |
1.3.6.1.4.1.9.9.510.1.2.13 | cermResMonitorPolicyTable | 1 | 2 | This table contains an entry for each resource policy being watched by each resource monitor in the system. This table will be us… |