DECHUB900-CHASSIS-MIB-V3-0 :: chasEntityAccessCharacteristics

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › DECHUB900-CHASSIS-MIB-V3-0 › chasEntityAccessCharacteristics

chasEntityAccessCharacteristics

Module: DECHUB900-CHASSIS-MIB-V3-0

OID (symbolic): DECHUB900-CHASSIS-MIB-V3-0::chasEntityAccessCharacteristics

OID (numeric): 1.3.6.1.4.1.36.2.18.11.1.1.1.2.2.1.17

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This object is used to provide access characteristics
pertaining to other objects in the given entity row.
The characteristics are divided into categories.
Each category uses a set of predefined bits to 
encode data.

The following categories are currently supported:

   Category                    Bits
   --------                    ----
   Community Access Rights     1..4
   Network Interface           5..6
   UNUSED                      7..15

The categories are orthogonal to each other, so it
is not necessary to perform 'inter-category' bounds
checking.

The object value is a concatentation of encodings
from each category, and can be considered a sum.
The actual encoding mechanism is defined on a per
category basis.

Categories
==========

Community Access Rights
-----------------------
Community access rights are associated with the community
name, internet address pair.  More than one access right
can be defined for a given community name, internet
address pair.

The encoding works as follows:  Starting from zero, for 
each access right supported, 2 raised to a power is
added to the sum.  The powers are according to the
following table:

           Type         Power
           ----         -----
           readOnly       0
           readWrite      1
           trap           2
           other          3

For example, a community name, internet address pair
with readOnly and readWrite access rights, would have
a value of 3 (2^0 + 2^1).

An access right of other(3) defines the entity row as
non-SNMP manageable.  Management information is provided 
in the chasEntityAccessMethod and the Network Interface
(defined below).

Note:  Just because a user directs a message to the community
       name, internet address pair does not imply that the
       user is authorized on that pair.  Additional security
       mechanisms may be employed such that only messages from
       particular internet addresses are authorized.

Network Interface
-----------------
The network interface is associated with the internet
address and defines the route for management traffic.
A network interface can be one of the following:

       none(0),
       obm(1),
       ibm(2), and
       port(3).

The value is placed in the 2-bits reserved for network
interfaces.

Note:  ibm(2) and port(3) are both in-band management.  The
       difference is ibm(2) is a module wide ip address, and
       port(3) is associated with a particular port/interface.

What is chasEntityAccessCharacteristics?

A bitmask encoding this entity's community access rights (readOnly/readWrite/trap/other, bits 1-4) and network interface type (none/obm/ibm/port, bits 5-6) as a summed value. An admin decoding a value of 40, for instance, would learn the row grants 'other' (non-SNMP) access over an 'ibm' in-band management interface.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.36.2.18.11.1.1.1.2.2.1.17
snmpwalk -v2c -c public <target> DECHUB900-CHASSIS-MIB-V3-0::chasEntityAccessCharacteristics

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.36.2.18.11.1.1.1.2.2.1.17.1
snmpget -v2c -c public <target> DECHUB900-CHASSIS-MIB-V3-0::chasEntityAccessCharacteristics.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> chasEntityAccessCharacteristics.1

Start monitoring DEC DEChub 900 modular hub chassis with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DECHUB900-CHASSIS-MIB-V3-0::chasEntityAccessCharacteristics OID value, configure state conditions and alerts, and monitor any DEC DEChub 900 modular hub chassis from a single console.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.36decCMU-MIB
1.3.6.1.4.1.36.2emaDEC-ATM-CHASSIS-MIB
1.3.6.1.4.1.36.2.18decMIBextensionDEC-ATM-CHASSIS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.36.2.18.11decHub900DECHUB900-CHASSIS-MIB-V3-0
1.3.6.1.4.1.36.2.18.11.1mgmtAgentDECHUB900-CHASSIS-MIB-V3-0
1.3.6.1.4.1.36.2.18.11.1.1mgmtAgentVersion1DECHUB900-CHASSIS-MIB-V3-0
1.3.6.1.4.1.36.2.18.11.1.1.1chassisDECHUB900-CHASSIS-MIB-V3-0
1.3.6.1.4.1.36.2.18.11.1.1.1.2chasEntityDECHUB900-CHASSIS-MIB-V3-0
1.3.6.1.4.1.36.2.18.11.1.1.1.2.2chasEntityTableDECHUB900-CHASSIS-MIB-V3-0
1.3.6.1.4.1.36.2.18.11.1.1.1.2.2.1chasEntityEntryDECHUB900-CHASSIS-MIB-V3-0
1.3.6.1.4.1.36.2.18.11.1.1.1.2.2.1.17chasEntityAccessCharacteristicsDECHUB900-CHASSIS-MIB-V3-0