eventInstanceType
ZYXEL-ves1616pe54-MIB ·
.1.3.6.1.4.1.890.1.5.12.37.26.1.1.1.4
Object
column InstanceType
This variable represents the type of InstanceId of a
particular event in the event table. In brief
the instanceType refers to the type of sub-component
generating this event in the system, for example
switch (5). For more details see the textual
conventions section.
AFFECTS: eventInstanceId,
eventInstanceName
Context
- MIB
- ZYXEL-ves1616pe54-MIB
- OID
.1.3.6.1.4.1.890.1.5.12.37.26.1.1.1.4- Type
- column
- Access
- readonly
- Status
- current
- Parent
- eventEntry
Net-SNMP examples
How SNMP and these commands workWalk the column to discover its indexed instances, or supply every index to read one instance.
Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ZYXEL-ves1616pe54-MIB' -M '/opt/observium/mibs/zyxel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ZYXEL-ves1616pe54-MIB::eventInstanceType'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'ZYXEL-ves1616pe54-MIB' -M '/opt/observium/mibs/zyxel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ZYXEL-ves1616pe54-MIB::eventInstanceType.<eventSeqNum>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'ZYXEL-ves1616pe54-MIB' -M '/opt/observium/mibs/zyxel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ZYXEL-ves1616pe54-MIB::eventInstanceType'
Syntax
- Source
- InstanceType
- Base type
Enumeration
Type Description
This textual convention describes the type of an instanceId
associated with each event and by that means specifies how
the instanceId variable should be intepreted.
Various instanceId types are specified below to enable fault
monitoring for different kind of devices from fixed
configuration pizza boxes to multi chassis nodes. All
instanceId types may not need to be used in every device
type.
Note also that instanceId semantics are element type dependent
(e.g. different kind of interface naming conventions may be used)
and thus instanceId usage may vary from element to element.
=========================================================================
Type Description Example form
of InstanceId
=========================================================================
unknown (1) unknown type - Irrelevant-
-------------------------------------------------------------------------
node (2) Associated with events originating from 1
the node. Used for general events that (Node number)
can not be associated with any specific
block. InstanceId value 1 is used for
single node equipment.
-------------------------------------------------------------------------
shelf (3) Associated with events originating from 1
the shelf. In the case of fixed (shelf number)
configuration devices this type is used
for events that are associated with the
physical enclosure, e.g. faults related
to fan etc. InstanceId value 1 is used
for single self equipment.
-------------------------------------------------------------------------
line (4) Associated with events originating from
physical interfaces or associated
components such as line cards.
InstanceId usage examples for faults
originating from:
- Physical port: Simply port number, e.g. .......1
-------------------------------------------------------------------------
switch (5) Associated with events originating from 1
from a switch chip or a switch card. (switch number)
For single switch equipment InstanceId
value 1 is used, for multi swich nodes
InstanceId semantics if for further
study.
-------------------------------------------------------------------------
lsp (6) Associated with events originating from 1
a particular lsp. (lsp index)
NOTE: In this case the InstanceName
contains the lsp name and InstanceId
contains lsp index.
-------------------------------------------------------------------------
l2Interface(7) Associated with events originating from - TBD -
a particular layer 2 interface. Used for
layer 2 related events such as L2 control
protocol faults. InstanceId semantics is
for further study.
-------------------------------------------------------------------------
l3Interface(8) Associated with events originating from - TBD -
a particular layer 3 interface. Used for
layer 3 related events such as L3 control
protocol faults. InstanceId semantics is
for further study.
-------------------------------------------------------------------------
rowIndex (9) Associated with events reporting about a
'logical' or conceptual table that consists
of rows. The Instance Id is the index/key
for a row in the table. The format of the
Instance Id will simply be a series of decimal
numbers seperated by a '.':
=========================================================================
Values & Constraints
Type Values
1 | unknown |
2 | node |
3 | shelf |
4 | line |
5 | switch |
6 | lsp |
7 | l2Interface |
8 | l3Interface |
9 | rowIndex |