DECHUB90-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for DECHUB90-MIB.
217
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
217 total| Object Name |
|---|
dec OBJECT IDENTIFIER .1.3.6.1.4.1.36 |
RFC1155-SMI Unknown .1.3.6.1.4.1.36 |
ema OBJECT IDENTIFIER .1.3.6.1.4.1.36.2 |
emaSystem OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.15 |
proxyAgent OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.15.10 |
decagent90 OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.15.10.1 |
decagent90v1 OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.15.10.1.1 |
consolePasswordFailureThere have been three consecutive failures to enter a correct password
when attempting to log into the DECagent 90 console port. TRAP-TYPE .1.3.6.1.4.1.36.2.15.10.1.1.0.1 |
nonVolatileRamErrorAn error in the non-volatile storage on the DECagent 90 has occurred.
Some configuration information may have been lost. TRAP-TYPE .1.3.6.1.4.1.36.2.15.10.1.1.0.2 |
configurationExceededAn attempt was made to exceed the maximum configuration supported by
the DECagent 90. The request to create the additional community or to
add the additional module has been rejected. TRAP-TYPE .1.3.6.1.4.1.36.2.15.10.1.1.0.3 |
populationChangeA module has been added or discovered, or has been deleted or
undiscovered. The objects dh90PopulationChange and
dh90PopulationLastChange have been updated to reflect this change.
The community index, slot index, and module object id are included in
the trap PDU. TRAP-TYPE .1.3.6.1.4.1.36.2.15.10.1.1.0.4 |
moduleStatusChangeA module has become reachable or unreachable. The objects
dh90StatusChange and dh90StatusLastChange have been updated to reflect
this change. The community index, slot index, module object id and
proxy status are included in the trap PDU. TRAP-TYPE .1.3.6.1.4.1.36.2.15.10.1.1.0.5 |
rptrPortStatusChangeThe port status has changed on a repeater module. The objects
dh90StatusChange and dh90StatusLastChange have been updated to reflect
this change. The community index, slot index, module object id, port
index and port state are included in the trap PDU. TRAP-TYPE .1.3.6.1.4.1.36.2.15.10.1.1.0.6 |
srvrPortStatusChangeThe port status has changed on a terminal server module. The objects
dh90StatusChange and dh90StatusLastChange have been updated to reflect
this change. The community index, slot index, module object id, port
index and port operational status are included in the trap PDU. TRAP-TYPE .1.3.6.1.4.1.36.2.15.10.1.1.0.7 |
brdgPortStatusChangeThe port status has changed on a bridge module. The objects
dh90StatusChange and dh90StatusLastChange have been updated to reflect
this change. The community index, slot index, module object id, port
index and port operational status are included in the trap PDU. TRAP-TYPE .1.3.6.1.4.1.36.2.15.10.1.1.0.8 |
decMIBextension OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18 |
dechub90 OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10 |
dh90 OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.1 |
dh90TypeIdentifies the type of community (hub, string or standalone device)
managed by DECagent 90 modules. Setting this variable to invalid(2)
deletes the community associated with the community string and releases
resources used by the community. Setting the value of an existing
community of type dechub90(4) or dechub900(5) or STACKhub90(6) to
standAloneCommunity(3) requires that there be no modules or a single
module in the hub. Any other configuration will result in a 'genErr'
response. The value unknown(1) is read-only as an indicator that a
particular community's resource area may be corrupt. Attempting to
set the value to unknown(1) will result in a 'badValue' response.rw Enumeration .1.3.6.1.4.1.36.2.18.10.1.1 |
dh90BackplaneMedia on the backplane of hub.ro Enumeration .1.3.6.1.4.1.36.2.18.10.1.2 |
dh90LastChangeThe value of the sysUpTime at the time a module was added or removed
from this community.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.36.2.18.10.1.3 |
dh90NumberSlotsNumber of slots in the hub backplane. Setting this variable to the
value 1, 8 or 16 defines the size of a hub in a particular community.
Note that attempting to set this variable to a value smaller than the
existing value when there are modules present in the slots that would
be eliminated by the reduction in hub size will result in a 'genErr'
response.rw INTEGER .1.3.6.1.4.1.36.2.18.10.1.4 |
dh90SlotTableA list of modules installed in the DEChub 90. To create a new row
(module) in the slot table, set an instance (slot) of
dh90SlotModuleType which is currently empty(2) to the appropriate
value. If adding a bridge or server, next set the
dh90SlotPhysicalAddress for the row. Sets of the other variables in
the row must be done in separate PDUs after the MAC address of the
device has been set correctly.
When sweeping the slot table with getNext, rows of the table which are
empty will be skipped. The only values returned are for slots which
are occupied.
To delete a module, set the dh90SlotModuleType (instanced by slot
number) to empty(2). The row corresponding to the slot number will be
deleted from the table. SEQUENCE OF Dh90SlotEntry .1.3.6.1.4.1.36.2.18.10.1.5 |
dh90SlotEntryContains objects defining characteristics of modules in the
community. Dh90SlotEntry .1.3.6.1.4.1.36.2.18.10.1.5.1 |
dh90SlotIndexThe slot number containing the module. Setting this variable to the
slot number of an empty slot in the community will result in the module
being moved to that slot. Setting this variable to the value of a slot
which is occupied results in a 'genErr' response. Setting it to a
value which is outside the range (1..dh90NumberSlots) results in a
'badValue' response.
DEChub 90 restrictions: some modules can reside only in certain slots
of a DEChub 90. The DECbridge 90 and DECbridge 90FL are restricted to
slot 7 or 8. The DECagent 90 and DECrepeater 90FA are restricted to
slot 7, 8, 15, or 16. These restrictions do not apply when these
modules are in a DEChub 900.
You are not allowed to move the managing DECagent 90. Attempting to do
so will result in a 'genErr' response.rw INTEGER .1.3.6.1.4.1.36.2.18.10.1.5.1.1 |
dh90SlotModuleType- do not use, provided for backwards compatibility only -
Use dh90SlotObjectID instead.
The type of the module in a slot. If the slot is known to be empty,
a value of empty(2) is used. If the slot is occupied by a module of
unknown type, a value of unknown(1) is used. Note that the
restrictions on module placement in the DEChub 90 as described in the
description of dh90SlotIndex apply here as well. The value unknown(1)
is read-only as an indicator that a particular module's resource area
may be corrupt. Attempting to set the value to unknown(1) will result
in a 'badValue' response.rw Enumeration .1.3.6.1.4.1.36.2.18.10.1.5.1.2 |
dh90SlotModuleNameA textual description of the module. Setting a value with embedded
spaces or tabs will result in a 'badValue' response.
Note that for a DECserver 90, you cannot set this value to a null
string. Attempting to do so will result in a 'badValue' response.rw DisplayString .1.3.6.1.4.1.36.2.18.10.1.5.1.3 |
dh90SlotModuleVersionA textual description of the version level of the hardware and
firmware of the module.ro DisplayString .1.3.6.1.4.1.36.2.18.10.1.5.1.4 |
dh90SlotCounterTimeTime since the counters of this module were zeroed. Devices which do
not support MOP counters will return a 'noSuchName' response.ro Gauge .1.3.6.1.4.1.36.2.18.10.1.5.1.5 |
dh90SlotIfBaseAn index into the ifTable for the first network interface on this
module. Add one to this value to reference the ifTable entry which
corresponds to the second interface, etc. If no interfaces are
supported on the module, a response of 'noSuchName' is returned.ro INTEGER .1.3.6.1.4.1.36.2.18.10.1.5.1.6 |
dh90SlotIfNumberThe number of network interfaces on this module. For example, a
DECbridge 90 has 2 network interfaces, the backbone and the workgroup
ports. A DECserver 90L has a single network interface. For devices
with no interfaces, a response of 'noSuchName' is returned.ro INTEGER .1.3.6.1.4.1.36.2.18.10.1.5.1.7 |
dh90SlotPhysicalAddressA read-write variable for the physical address to allow devices to be
added to the hub remotely. Writing this variable as part of a remote
add device routine will cause the new physical address to be accessible
in the corresponding ifPhysAddress variable in the ifTable. Attempts
to set this variable for the managing DECagent 90 with a value which is
different from the actual station address will result in a 'genErr'
response.rw OCTET STRING .1.3.6.1.4.1.36.2.18.10.1.5.1.8 |
dh90SlotNumberOfPortsThe number of ports on this module. Returns the following values for
the indicated devices:
Device Value
================ =====
DECagent 90 1
DECbridge 90 2
DECbridge 90FL 2
DECrepeater 90FA 2
DECrepeater 90FL 4
DECrepeater 90C 6
DECrepeater 90T 8
DECserver 90L 8
DECserver 90L+ 8
DECserver 90M 8
DECserver 90TL 8
Other devices may return a non-zero value also.ro INTEGER .1.3.6.1.4.1.36.2.18.10.1.5.1.9 |
dh90SlotPasswordPassword used to enable privileged operations on devices which support
the MOP and RBMS protocols for remote management. Setting a value
containing embedded spaces or tabs will result in a 'badValue'
response.
Supported devices include: DECserver 90L, DECserver 90L+, DECbridge 90
and DECbridge 90FL.
For DECserver 90's, the maximum password length is eight (8).
For DECbridge 90's, the maximum password length is sixteen (16).
Passwords which exceed these values will result in a 'badValue'
response.
Reads to this variable for supported devices will always return a null
string. For other devices, access to this variable will result in a
'noSuchName' response.
NOTE: It is imperative that the DECagent 90 be password-synchronized
with the remote devices it is managing. If a device has a password,
the DECagent 90 will not be able to perform sets to it without the
correct password. Sets to this variable cause the value to be stored
in the DECagent 90's non-volatile storage for use when accessing the
device in the specified slot.rw DisplayString .1.3.6.1.4.1.36.2.18.10.1.5.1.10 |
dh90SlotNewPasswordSetting this variable causes the agent to set a new password on the
device using the value provided as the new password and the current
value of dh90SlotPassword as the old password. Setting a value
containing embedded spaces or tabs will result in a 'badValue'
response.
See the description of dh90SlotPassword above for supported devices and
password length restrictions.
Notes related only to DECservers: authorized mode must be enabled in
order to set a new password. See the description of ds90LAuthorizeMode
for details. If authorized mode is disabled, a 'genErr' response will
be returned. Also, the new password cannot be set to null. Attempting
to do so will result in a 'badValue' response. To disable password
security you must set ds90LAuthorizeMode to disable(2).
Reads to this variable for supported devices will always return a null
string. For other devices, access to this variable will result in a
'noSuchName' response.rw DisplayString .1.3.6.1.4.1.36.2.18.10.1.5.1.11 |
dh90SlotPollingThe current polling status of the module. If the DECagent 90 is
polling this device, a get of this variable will return on(2),
otherwise off(1) is returned. Setting this variable to off(1) causes
the agent to stop polling the device in this slot. Setting this
variable to on(2) causes the agent to start polling the device in the
specified slot. If a device does not repond to a poll, a
SlotStatusChange(1) enterprise-specific trap is generated. Attempting
to set to off(1) the slot polling of the agent will result in a
'badValue' response.rw Enumeration .1.3.6.1.4.1.36.2.18.10.1.5.1.12 |
dh90SlotPrimarySpecificFor proxied modules, a reference to its primary MIB definition.
For bridges, a reference to the MIB-II dot1dBridge MIB. For terminal
servers, a reference to the MIB-II character-like MIB. For DECagents,
a reference to the { da90 } portion of this MIB. For repeaters, a
reference to the { drpt90 } portion of this MIB. If the module
realizes some other function, the object identifier
nullSpecific OBJECT IDENTIFIER ::= { 0 0 }
is returned.ro OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.1.5.1.13 |
dh90SlotSecondarySpecificFor bridges, a reference to the { db90ext } portion of this MIB. For
terminal servers, a reference to the MIB-II rs232-like MIB definition.
Otherwise, the object identifier
nullSpecific OBJECT IDENTIFIER ::= { 0 0 }
is returned.ro OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.1.5.1.14 |
dh90SlotIpAddressThe IP address of the device in the given slot. This value is returned
only for devices which implement their own on-board SNMP agent.rw IpAddress .1.3.6.1.4.1.36.2.18.10.1.5.1.15 |
dh90SlotCommunityStringThe community string of the device in the given slot. This value is
returned only for devices which implement their own on-board SNMP agent.
For the managing agent, the read-only community string is returned if it
is not null, otherwise the read-write community string is returned.rw OCTET STRING .1.3.6.1.4.1.36.2.18.10.1.5.1.16 |
dh90SlotObjectIDThe sysObjectID of the module in the given slot. This value is
provided by the DECagent 90 for modules in community 1. It can
be stored manually for modules in other communities.rw OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.1.5.1.17 |
dh90SlotProxyStatusThe state of the module as known by the proxy agent. The possible
states and their meanings are:
reachable - indicates an operational module for which this agent
will perform proxy operations.
unreachable - indicates a proxy operation has been unsuccessful to
this module. The agent cannot determine if the module
has been removed, has failed, or is unreachable due to
network load.
present - indicates a module for which this agent does not
perform proxy operations.
not-present - indicates that the agent has determined that the module
has been removed, or has failed, but the module data
has been retained since the user has performed sets to
this module. The module data will be retained until
the module is returned to this location, or moved or
deleted by the NMS.ro Enumeration .1.3.6.1.4.1.36.2.18.10.1.5.1.18 |
dh90SlotConflictStatusIndicates whether a module conflict has been detected. A conflict
indicates that the agent has discovered a module in this slot which is
a different type from the module which already exists in the agent's
database. Examples of conflicts are:
- A module has been discovered in this slot and there is an active
module already in this slot. In this case, dh90SlotProxyStatus
would have a value of present(4). This indicates that the active
module was manually added to an incorrect slot and should be moved
to its correct location.
- A module has been discovered in this slot and the last known module
in this slot was of a different type and that last known module had
other than default parameters set. The last known module was
physically removed and possibly moved to a new location. In this
case, the dh90SlotProxyStatus may have the a of unreachable(2) or
not-present(3). Either delete the module from this slot to allow
the discovered module to replace it, or move the module in this
slot to a new location.ro Enumeration .1.3.6.1.4.1.36.2.18.10.1.5.1.19 |
dh90SlotConflictDiscoveredIDIf dh90SlotConflictStatus has a value of conflict(2) then this object
indicates the sysObjectID of the module that has been discovered thus
creating the conflict. If dh90SlotConflictStatus has a value of none(1)
then this object will contain the sysObjectID of the module.ro OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.1.5.1.20 |
dh90SlotResetA control variable to perform reset functions on DEChub 90 modules
which are in the same hub as the managing agent. The agent must be the
hub master (see da90BackplaneState) for reset functions to be performed.
In response to a Get or getNext request, the agent returns the value
ready(1). Setting this value to reset(2) causes the entire module to be
reset. Setting this value to resetToFactory(3) causes the entire device
to be reset to the original factory settings. For repeaters, all port
names are cleared and all drpt90PortAdminStatus values are set to
enabled(1). For both reset functions, the port address database is
cleared.
Note that this object performs the same reset functions as
ds90LMaintenance for terminal servers, dbSysInitSwitch for bridges and
da90Maintenance for the managing agent.rw Enumeration .1.3.6.1.4.1.36.2.18.10.1.5.1.21 |
dh90TrapAddressTableA table of IP addresses to which this device will send SNMP traps. SEQUENCE OF Dh90TrapEntry .1.3.6.1.4.1.36.2.18.10.1.6 |
dh90TrapEntryEach entry contains an IP address to which all SNMP traps will be sent
by this community. Dh90TrapEntry .1.3.6.1.4.1.36.2.18.10.1.6.1 |
dh90TrapAddressAn IP address to which all SNMP traps generated for this community will
be sent. Setting an instance to a value of zero will delete the row in
the table. Setting an instance to the current value of the DECagent's
IP address will result in a 'genErr' response.rw IpAddress .1.3.6.1.4.1.36.2.18.10.1.6.1.1 |
dh90LastErrorMsgIndicates the last error message for this community. Examples of
errors which may cause this string to be updated are:
- An error in a proxy operation (get or set) to a terminal server or
bridge (e.g. invalid command response, invalid password).
- Terminal server MOP console is busy.
Whenever this object changes value, the dh90LastErrorSlot object and the
dh90LastErrorChange object will be updated.ro DisplayString .1.3.6.1.4.1.36.2.18.10.1.7 |
dh90LastErrorChangeThe value of MIB-II's sysUpTime (in the agent supporting this MIB) when
a module event occurred which caused the dh90LastErrorMsg object to be
updated.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.36.2.18.10.1.8 |
dh90LastErrorSlotThe slot of the module which caused the dh90LastErrorMsg object to be
updated. A value of zero (0) indicates that an error has not yet
occurred.ro INTEGER .1.3.6.1.4.1.36.2.18.10.1.9 |
dh90PopulationChangeThe total number of changes in population of the modules within the
community. This counter is incremented:
- when a module is added or discovered, or
- when a module is deleted or undiscovered, or
- when a module conflict occurs
The purpose of this object is to provide a single object in the
community which can be polled by an NMS to determine if there have been
changes in the hub population.ro Counter .1.3.6.1.4.1.36.2.18.10.1.10 |
dh90PopulationLastChangeThe value of MIB-II's sysUpTime (in the agent supporting this MIB) when
a module event occurred which caused the increment of the
dh90PopulationChange counter.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.36.2.18.10.1.11 |
dh90StatusChangeThe total number of changes to status of the modules within the
community. This counter is incremented:
- when a proxied module becomes reachable, or
- when a proxied module becomes unreachable, or
- when a proxied module has a change in port status.
The purpose of this object is to provide a single object in the
community which can be polled by an NMS to determine if there have been
changes in status of modules or ports within the hub. Note that this
object does not warn of impending counter rollovers, which the NMS will
still have to poll for occasionally.ro Counter .1.3.6.1.4.1.36.2.18.10.1.12 |
dh90StatusLastChangeThe value of MIB-II's sysUpTime (in the agent supporting this MIB) when
a module event occurred which caused the increment of the
dh90StatusChange counter.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.36.2.18.10.1.13 |
da90 OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.2 |
da90FlashErasuresThe number of times the flash memory on this DECagent 90 has been
erased. This number is the total of erasures for all flash segments.ro Counter .1.3.6.1.4.1.36.2.18.10.2.1 |
da90MaintenanceA control variable to perform reset functions on a DECagent 90. In
response to a Get or a getNext request, the agent returns ready(1) if
SNMP sets are enabled, or setsDisabled(2) if they are disabled.
Setting this value to setsDisabled(2) causes SNMP sets to be disabled.
Note, however, that you cannot re-enable SNMP sets via this mechanism.
SNMP sets can only be re-enabled via the console interface, or by
restoring factory settings. Setting this value to reset(3) causes the
entire module to be reset. Setting this value to resetToFactory(4)
causes the entire device to be reset to the original factory settings.
Setting either reset(3) and resetToFactory(4) results in an immediate
reset with no response PDU being issued.rw Enumeration .1.3.6.1.4.1.36.2.18.10.2.2 |
da90CommunityNumberNumber of entries in the da90CommunityTable.ro INTEGER .1.3.6.1.4.1.36.2.18.10.2.3 |
da90CommunityTableA table of community strings for client communities. SEQUENCE OF Da90CommunityEntry .1.3.6.1.4.1.36.2.18.10.2.4 |
da90CommunityEntryContains community type and strings, including the read-only profile,
the read-write profile and a trap string. Da90CommunityEntry .1.3.6.1.4.1.36.2.18.10.2.4.1 |
da90CommunityIndexIndex into hub-community string pair table, identifies the community
being accessed.ro INTEGER .1.3.6.1.4.1.36.2.18.10.2.4.1.1 |
da90CommunityTypeIdentifies whether the current community information is active for
this row in the community table. The value unknown(1) is read-only and
indicates that this row in the community table contains questionable
data. Setting to invalid(2) deletes this row in the community table,
thereby freeing the NVRAM used to store the community information (i.e.
destroys the slot and port tables for this community). Attempting to
set invalid(2) the community in which the managing DECagent resides
will result in a 'genErr' response.rw Enumeration .1.3.6.1.4.1.36.2.18.10.2.4.1.2 |
da90CommunityROStringCommunity string, with a read-only profile, used to access a client
hub. All community strings in the read-only set must be unique.
Setting such a community string to a pre-existing value returns a
status of 'badValue'. Reading this variable with a community string
other than one of the agent's community strings will result in a
'noSuchName' response.rw OCTET STRING .1.3.6.1.4.1.36.2.18.10.2.4.1.3 |
da90CommunityRWStringCommunity string, with a read-write profile, used to access a client
hub. All community strings in the read-write set must be unique.
Setting such a community string to a pre-existing value returns a
status of 'badValue'. Reading this variable with a community string
other than the agent's read-write community string will result in a
'noSuchName' response.rw OCTET STRING .1.3.6.1.4.1.36.2.18.10.2.4.1.4 |
da90CommunityTrapStringCommunity string sent with traps generated due to events caused by
this community. The trap community strings do not have to be unique.
This variable is read using one of the agent's community string.rw OCTET STRING .1.3.6.1.4.1.36.2.18.10.2.4.1.5 |
da90AgentSlotThe slot number in which the managing DECagent 90 resides.ro INTEGER .1.3.6.1.4.1.36.2.18.10.2.5 |
da90ErrorlogTableThe da90ErrorlogTable is a ring of eight (8) errorlog entries for this
DECagent 90. Thus, the ninth entry will overwrite the first entry, the
tenth entry will overwrite the second entry, and so on. The last entry
with the highest value of da90ErrorlogWriteCount is the most recent
entry. The errorlog contains information about extraordinary events
which have occurred in the DECagent, including user-initiated
reset-to-factory settings, fatal traps and unexpected traps. The
errorlog does not contain normal SNMP trap information. SEQUENCE OF Da90ErrorlogEntry .1.3.6.1.4.1.36.2.18.10.2.6 |
da90ErrorlogEntryAn entry in the errorlog containing the DECagent reset count at the
time the entry was logged, the timestamp in hundredths of a second
since the last reset occurred, the number of times this table entry has
been written to and the error information in textual form. Da90ErrorlogEntry .1.3.6.1.4.1.36.2.18.10.2.6.1 |
da90ErrorlogIndexThe index into the errorlog table.ro INTEGER .1.3.6.1.4.1.36.2.18.10.2.6.1.1 |
da90ErrorlogResetCountThe number of times the DECagent has been reset (soft or hard reset)
since the creation of the errorlog or the last reset-to-factory
settings. A value of zero indicates that this error occurred before
initialization was complete. See da90ResetCount for additional
details.ro INTEGER .1.3.6.1.4.1.36.2.18.10.2.6.1.2 |
da90ErrorlogTimeStampThe uptime, in hundredths of a second, of the DECagent when this entry
was logged.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.36.2.18.10.2.6.1.3 |
da90ErrorlogWriteCountThe number of times this row in the errorlog table has been written.ro INTEGER .1.3.6.1.4.1.36.2.18.10.2.6.1.4 |
da90ErrorlogDataA textual description of the error for this errorlog entry.ro DisplayString .1.3.6.1.4.1.36.2.18.10.2.6.1.5 |
da90ResetCountThe total number of resets to the agent that has occurred, including
power-ups. This counter is maintained in non-volatile storage and is
reset to zero only when a reset-to-factory settings occurs.ro Counter .1.3.6.1.4.1.36.2.18.10.2.7 |
da90BackplaneModeThe desired state of the DECagent 90's hub mastership (i.e. it's
ability to directly manage repeaters, terminal servers and bridges and
discover other modules which reside in the same hub as the agent).
This value is retained in non-volatile storage. It's default value is
master(2).rw Enumeration .1.3.6.1.4.1.36.2.18.10.2.8 |
da90BackplaneStateIndicates whether the DECagent 90 is managing the hub (i.e. capable of
directly managing repeaters, terminal servers and bridges and
discovering other modules).ro Enumeration .1.3.6.1.4.1.36.2.18.10.2.9 |
da90BackplaneAddrDbAgingTimeA non-volatile value indicating the number of minutes an address
discovered by the agent will remain in the forwarding database address
table. This variable is meaningful only when the agent is the bus
master of the hub backplane (see da90BackplaneState). It's default
value is 600 minutes.rw INTEGER .1.3.6.1.4.1.36.2.18.10.2.10 |
da90LoadAdminStatusThis object is used to control the program TFTP load process of a
device. When read, the value other(1) is returned.
When set to start-read(2) the device initiates a TFTP read operation to
read a new program image. This implementation does not support
start-write(3) to initiate a new program load via a TFTP write
operation.
The status of the last load attempt is reflected in da90LoadOperStatus.
A device shall always reset upon completion of a successful load
attempt. It may reset upon unsuccessful completion of the load
attempt.
This implementation does not support the cancel(4) option.rw Enumeration .1.3.6.1.4.1.36.2.18.10.2.11 |
da90LoadOperStatusThe final state of the last load attempt. The value none(1) indicates
that no load has been attempted, ever.
This object is non-volatile. It's default value is none(1).ro Enumeration .1.3.6.1.4.1.36.2.18.10.2.12 |
da90LoadFilenameThe name of the file in which to load. When the device is reading,
this is the name of the file to be read. When the device is being
written, this is the only name of the file in which writes will be
accepted - provided the device can check the file name. If the device
can not check the file name then this object is ignored. It is the
duty of the NMS triggering the device to load this object.
This object is non-volatile. The initial and default value of this
object in a zero-length string. Setting a value containing embedded
spaces or tabs will result in a 'badValue' response.
In the case of multi-file loads (aka segmented loads) this object
contains the name of the first file in which to load. It is an
application specific issue as to how to get subsequent load files.rw DisplayString .1.3.6.1.4.1.36.2.18.10.2.13 |
da90LoadIpHostAddrThe IP address of the host from which to load. When the device is
reading, this is the IP address of the host in which the read will be
directed. When the device is being written, this is the IP address of
the only host in which writes will be accepted.
This object is non-volatile. The initial and default value of this
object is 0.0.0.0.rw IpAddress .1.3.6.1.4.1.36.2.18.10.2.14 |
da90LoadDevSpecificA device specific parameter which is used to indicate detailed error
information about the last attempted load.
A value of none(0) indicates that no load has been attempted, or that
there is nothing interesting to report of the last load. readFailed(1)
and timedOut(2) indicate that the TFTP file transfer was not
successful. A crcFailure(3) is returned when the image transferred
failed to pass the CRC check.
This object is non-volatile. It's default value is none(1).ro Enumeration .1.3.6.1.4.1.36.2.18.10.2.15 |
da90SetupPortStatusThis object indicates the current status of the setup port on
the front panel of the DECagent. When read, it will return
either console(1) or slip(2). Writing reset(3) to this object
will cause the setup port to return to the console state. The
setup port cannot be set to slip state from this object; it must
be done through the appropriate console menu option. Writing a
value other than reset(3) will result in a 'badValue' response.rw Enumeration .1.3.6.1.4.1.36.2.18.10.2.16 |
ds90L OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.3 |
ds90LNumberModulesNumber of DECserver 90 modules represented in the ds90LModuleTable.ro INTEGER .1.3.6.1.4.1.36.2.18.10.3.1 |
ds90LModuleTableA table of DECserver 90 modules installed in the group. The number of
entries is given by ds90LNumberModules. SEQUENCE OF Ds90LModuleEntry .1.3.6.1.4.1.36.2.18.10.3.2 |
ds90LModuleEntryContains objects defining characteristics of DECserver 90 modules in
the group. Ds90LModuleEntry .1.3.6.1.4.1.36.2.18.10.3.2.1 |
ds90LSlotIndexThe slot index value which addresses the dh90SlotTable for this
module.ro INTEGER .1.3.6.1.4.1.36.2.18.10.3.2.1.1 |
ds90LDot3StatsDeferredTransmissionsA count of frames for which the first transmission attempt on a
particular interface is delayed because the medium is busy.
The count represented by an instance of this object does not include
frames involved in collisions.ro Counter .1.3.6.1.4.1.36.2.18.10.3.2.1.2 |
ds90LDot3StatsSingleCollisionFramesA count of successfully transmitted frames on a particular interface
for which transmission is inhibited by exactly one collision.
(If the DECserver 90 implements the MIB-II if group, the following also
applies:
A frame that is counted by an instance of this object is also counted
by the corresponding instance of either the ifOutUcastPkts or
ifOutNUcastPkts object and is not counted by the corresponding instance
of the ds90LDot3StatsMultipleCollisionFrames object.)ro Counter .1.3.6.1.4.1.36.2.18.10.3.2.1.3 |
ds90LDot3StatsMultipleCollisionFramesA count of successfully transmitted frames on a particular interface
for which transmission is inhibited by more than one collision.
(If the DECserver 90 implements the MIB-II if group, the following also
applies:
A frame that is counted by an instance of this object is also counted
by the corresponding instance of either the ifOutUcastPkts or
ifOutNUcastPkts object and is not counted by the corresponding instance
of the ds90LDot3StatsSingleCollisionFrames object.)ro Counter .1.3.6.1.4.1.36.2.18.10.3.2.1.4 |
ds90LEnetDataOverrunsA count of the number of frames arriving at the DECserver 90 that were
lost due to data overrun since it last reinitialized or zeroed
counters.ro Counter .1.3.6.1.4.1.36.2.18.10.3.2.1.5 |
ds90LLatCircMsgsInsA count of the number of LAT circuit messages received by this
DECserver 90 since it last reinitialized or zeroed counters.ro Counter .1.3.6.1.4.1.36.2.18.10.3.2.1.6 |
ds90LLatCircMsgsOutsA count of the number of LAT circuit messages transmitted by this
DECserver 90 since it last reinitialized or zeroed counters.ro Counter .1.3.6.1.4.1.36.2.18.10.3.2.1.7 |
ds90LLatSessSolicitAcceptsA count of the number of LAT solicits accepted by this DECserver 90
since it last reinitialized or zeroed counters.ro Counter .1.3.6.1.4.1.36.2.18.10.3.2.1.8 |
ds90LLatSessSolicitRejectsA count of the number of LAT solicits rejected by this DECserver 90
since it last reinitialized or zeroed counters.ro Counter .1.3.6.1.4.1.36.2.18.10.3.2.1.9 |
ds90LLatCircDuplsMsgsA count of the number of duplicate LAT messages the DECserver 90 LAT
implementation has discarded since it last reinitialized or zeroed
counters.ro Counter .1.3.6.1.4.1.36.2.18.10.3.2.1.10 |
ds90LLatCircMsgRetransmitsA count of the total number of LAT circuit messages this DECserver 90
has retransmitted since it last reinitialized or zeroed counters.ro Counter .1.3.6.1.4.1.36.2.18.10.3.2.1.11 |
ds90LLatSessIllegalSlotsA count of the number of illegal LAT slots this DECserver 90 has
received on all LAT sessions since it last reinitialized or zeroed
counters.ro Counter .1.3.6.1.4.1.36.2.18.10.3.2.1.12 |
ds90LIllegalMulticastRcvsA count of the number of illegal multicast LAT messages received on
this DECserver 90 since it last reinitialized or zeroed counters.ro Counter .1.3.6.1.4.1.36.2.18.10.3.2.1.13 |
ds90LLatCircKeepAliveThis defines the number of seconds the LAT circuits provider waits
between transmitting LAT circuit layer keep-alive messages. Writing to
this object is equivalent to issuing the CHANGE SERVER KEEPALIVE TIMER
command via the user interface.ro INTEGER .1.3.6.1.4.1.36.2.18.10.3.2.1.14 |
ds90LLatCircRetransmitLimitThis object defines the maximum number of LAT circuit message
retransmissions the server will attempt before declaring the circuit
failed. Writing to this object is equivalent to issuing the CHANGE
SERVER RETRANSMIT LIMIT command via the user interface.ro INTEGER .1.3.6.1.4.1.36.2.18.10.3.2.1.15 |
ds90LLatCircInvalidMsgsThis counts the number of invalid LAT messages received on its entry's
LAT circuit since the DECserver last reinitialized or zeroed counters.ro Counter .1.3.6.1.4.1.36.2.18.10.3.2.1.16 |
ds90LAuthorizeModeSetting a value of enable(1) causes the DECserver to enter an
enable-authorized-mode-pending state. The device will enter authorized
mode if the power is cycled on the device within one minute. The
password used to enable authorized mode will be the current value of
dh90SlotPassword, which must be set to the desired value prior to
setting ds90LAuthorizeMode to enable(1).
Setting a value of disable(2) causes the DECserver to enter a
disable-authorized-mode-pending state. The device will exit authorized
mode if the power is cycled on the device within one minute.rw Enumeration .1.3.6.1.4.1.36.2.18.10.3.2.1.17 |
ds90LMaintenanceA control variable to reset the counters on a DECserver 90. In
response to a Get or a getNext request, the agent always returns
ready(1). Setting the value to zeroCounters(2) causes the interface,
LAT and dh90SlotCounterTime counters to be cleared. Setting the value
to reset(3) causes the entire module to be reset, any users and
circuits will be disconnected. Setting the value to resetToFactory(4)
causes the entire device to be reset to the original factory settings.
Passwords and port names will be cleared and port speeds set to
autobaud.rw Enumeration .1.3.6.1.4.1.36.2.18.10.3.2.1.18 |
ds90LPromptContains the prompt displayed when a session is local to the
DECserver 90L+ terminal server. The default value is '->'. This
variable returns 'noSuchName' for a DECserver 90L. Setting a value
containing embedded spaces or tabs will result in a 'badValue'
response.rw DisplayString .1.3.6.1.4.1.36.2.18.10.3.2.1.19 |
ds90LPortTableA table of port specific variables on this DECserver 90. The index
for a terminal server port is given by
(slot number * 100) + port number
The number of ports is given by dh90SlotNumberOfPorts. SEQUENCE OF Ds90LPortEntry .1.3.6.1.4.1.36.2.18.10.3.3 |
ds90LPortEntryA single LAT session instance this DECserver 90 currently provides. Ds90LPortEntry .1.3.6.1.4.1.36.2.18.10.3.3.1 |
ds90LPortIndexThe value of charPortIndex for this port.ro INTEGER .1.3.6.1.4.1.36.2.18.10.3.3.1.1 |
ds90LPortRemoteModificationEnables and disables remote modification of the port by the host
system.rw Enumeration .1.3.6.1.4.1.36.2.18.10.3.3.1.2 |
ds90LPortTypeSelects the type of device connected to the port.rw Enumeration .1.3.6.1.4.1.36.2.18.10.3.3.1.3 |
ds90LPortBreakDetermines if the port responds to local or remote break.rw Enumeration .1.3.6.1.4.1.36.2.18.10.3.3.1.4 |
ds90LPortTestSetting this variable to enable(2) places the port into loopback mode.
Loopback mode can be used to verify that a port is receiving and
sending characters.rw Enumeration .1.3.6.1.4.1.36.2.18.10.3.3.1.5 |
ds90LPortAutoConfigureEnables or disables the autoconfiguration of a port on a DECserver
90L+. Enabling autoconfiguration allows default settings to be
restored to a port after each reset of the terminal server. Disabling
autoconfiguration causes the speed and certain characteristics of the
port to be stored in non-volatile memory on the terminal server. These
port settings will be restored after the next reset of the device.
NOTE: Set this variable to disable(2) BEFORE setting a new port speed
with rs232PortInSpeed and rs232PortOutSpeed.
For the DECserver 90L, reads of this variable always return enable(1).
Setting this variable to a value other than enable(1) for a DECserver
90L will result in a 'badValue' response.rw Enumeration .1.3.6.1.4.1.36.2.18.10.3.3.1.6 |
ds90LPortOnDemandLoadingEnables or disables on-demand loading of fonts to a port in a
DECserver 90L+. For the DECserver 90L, reads of this variable always
return disable(1). Setting this variable to a value other than
disable(1) for a DECserver 90L will result in a 'badValue' response.rw Enumeration .1.3.6.1.4.1.36.2.18.10.3.3.1.7 |
ds90LPortDedicatedServiceStatusA status variable indicating whether or not dedicated service is
enabled on a terminal server port.
Dedicated service on a port means that the port will attempt to make
a connection only to the specified service/node/port. Attempts to make
a connection to another service/node/port is not possible on a port
with dedicated service enabled.
If the value of this variable is disabled(2), the corresponding name,
node and port variables will return 'noSuchName' on an SNMP Get and
'notFound' on an SNMP getNext.ro Enumeration .1.3.6.1.4.1.36.2.18.10.3.3.1.8 |
ds90LPortDedicatedServiceNameThe name of the dedicated service to which a connection will be
attempted when a connection to the terminal server port is made.
Setting a valid name, from 1 to 16 characters in length, will enable
dedicated service on the port. To disable dedicated service on the
port, set this variable to the null string. Setting a value containing
embedded spaces or tabs will result in a 'badValue' response.rw DisplayString .1.3.6.1.4.1.36.2.18.10.3.3.1.9 |
ds90LPortDedicatedServiceNodeThe node name of the remote system to which a connection will be
attempted when a connection to the terminal server port is made.
This variable can only be set for ports which already have dedicated
service enabled (i.e. ds90LPortDedicatedServiceName is not null).
Specifying a value for this variable for a port which does not have
dedicated service enabled will result in a 'genErr' response.
Note that setting this variable to null will also delete the port name
specified by ds90LPortDedicatedServicePort for this port. Setting a
value containing embedded spaces or tabs will result in a 'badValue'
response.rw DisplayString .1.3.6.1.4.1.36.2.18.10.3.3.1.10 |
ds90LPortDedicatedServicePortThe port on the remote system to which a connection will be attempted
when a connection to the terminal server port is made.
This variable can only be set for ports which already have dedicated
service enabled (i.e. ds90LPortDedicatedServiceName is not null) and a
valid node name (i.e. ds90LPortDedicatedServiceNode is not null). If
the above conditions are not met, a response of 'genErr' is returned.
Setting a value containing embedded spaces or tabs will result in a
'badValue' response.rw DisplayString .1.3.6.1.4.1.36.2.18.10.3.3.1.11 |
ds90LPortPreferredServiceStatusA status variable indicating whether or not preferred service is
enabled on a terminal server port.
Preferred service on a port means that the port will attempt to make
a connection to the specific service/node/port when the user does not
specify a service name with the 'CONNECT' command at the terminal
server prompt.
If the value of this variable is disabled(2), the corresponding name,
node and port variables will return 'noSuchName' on an SNMP Get and
'notFound' on an SNMP getNext.ro Enumeration .1.3.6.1.4.1.36.2.18.10.3.3.1.12 |
ds90LPortPreferredServiceNameThe name of the preferred service to which a connection will be
attempted when a connection to the terminal server port is made.
Setting a valid name, from 1 to 16 characters in length, will enable
preferred service on the port. To disable preferred service on the
port, set this variable to the null string. Setting a value containing
embedded spaces or tabs will result in a 'badValue' response.rw DisplayString .1.3.6.1.4.1.36.2.18.10.3.3.1.13 |
ds90LPortPreferredServiceNodeThe node name of the remote system to which a connection will be
attempted when a connection to the terminal server port is made.
This variable can only be set for ports which already have preferred
service enabled (i.e. ds90LPortPreferredServiceName is not null).
Specifying a value for this variable for a port which does not have
preferred service enabled will result in a 'genErr' response.
Note that setting this variable to null will also delete the port name
specified by ds90LPortPreferredServicePort for this port. Setting a
value containing embedded spaces or tabs will result in a 'badValue'
response.rw DisplayString .1.3.6.1.4.1.36.2.18.10.3.3.1.14 |
ds90LPortPreferredServicePortThe port on the remote system to which a connection will be attempted
when a connection to the terminal server port is made.
This variable can only be set for ports which already have preferred
service enabled (i.e. ds90LPortPreferredServiceName is not null) and a
valid node name (i.e. ds90LPortPreferredServiceNode is not null). If
the above conditions are not met, a response of 'genErr' is returned.
Setting a value containing embedded spaces or tabs will result in a
'badValue' response.rw DisplayString .1.3.6.1.4.1.36.2.18.10.3.3.1.15 |
ds90LSessionTableThe list of all LAT sessions active on this DECserver 90. SEQUENCE OF Ds90LSessionEntry .1.3.6.1.4.1.36.2.18.10.3.4 |
ds90LSessionEntryA single LAT session instance this DECserver 90 currently provides. Ds90LSessionEntry .1.3.6.1.4.1.36.2.18.10.3.4.1 |
ds90LSessionPortThe value of charPortIndex for the port to which this session
belongs.ro INTEGER .1.3.6.1.4.1.36.2.18.10.3.4.1.1 |
ds90LSessionIndexThe session index in the context of the port, a non-zero positive
integer. Will be 1 for the DECserver 90L, 4 for DECserver 90L+.ro INTEGER .1.3.6.1.4.1.36.2.18.10.3.4.1.2 |
ds90LSessionRemoteNodeThe name of the remote node providing the service for this session.ro DisplayString .1.3.6.1.4.1.36.2.18.10.3.4.1.3 |
ds90LSessionServiceThe service to which this session is connected.ro DisplayString .1.3.6.1.4.1.36.2.18.10.3.4.1.4 |
ds90LSessionRemotePortIdThe name of the port at the remote node providing the connection, for
example, LAT121.ro DisplayString .1.3.6.1.4.1.36.2.18.10.3.4.1.5 |
drpt90 OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.4 |
drpt90PortTableA table of port specific variables on this DECrepeater 90. The index
for a repeater port is given by
(slot number * 100) + port number
The number of ports is given by dh90SlotNumberOfPorts. SEQUENCE OF Drpt90PortEntry .1.3.6.1.4.1.36.2.18.10.4.1 |
drpt90PortEntryA collection of objects containing information for a given interface. Drpt90PortEntry .1.3.6.1.4.1.36.2.18.10.4.1.1 |
drpt90PortIndexIdentifies the module and port. The value of this object is given by:
(slot number * 100) + port numberro INTEGER .1.3.6.1.4.1.36.2.18.10.4.1.1.1 |
drpt90PortNameThe text description of the port given by the network manager.
Setting a value containing embedded spaces or tabs will result in a
'badValue' response.rw DisplayString .1.3.6.1.4.1.36.2.18.10.4.1.1.2 |
drpt90PortAdminStatusThe desired state of the port.rw Enumeration .1.3.6.1.4.1.36.2.18.10.4.1.1.3 |
drpt90PortStateThe state of the port. The value unknown(1) is returned when the port
state cannot be determined. The value autoPartitioned(2) indicates
that the repeater has disabled the port automatically, the value
managementPartitioned(3) indicates that the port has been disabled
remotely, and the value active(4) indicates that the port is
operational. A value of inactive(5) is returned by repeaters that
can detect that no media is attached to the port.ro Enumeration .1.3.6.1.4.1.36.2.18.10.4.1.1.4 |
drpt90PortTypeThe physical medium type of the port.ro Enumeration .1.3.6.1.4.1.36.2.18.10.4.1.1.5 |
drpt90PortPartitionsThe number of times this port has partitioned. This value is
significant only if drpt90PortStatus is not unknown(1).ro Counter .1.3.6.1.4.1.36.2.18.10.4.1.1.6 |
drpt90PortAutoPartitionReasonErrors currently detected on the port.ro Enumeration .1.3.6.1.4.1.36.2.18.10.4.1.1.7 |
drpt90PortJamBitsThe number of jam bits being used on the port segment.ro Enumeration .1.3.6.1.4.1.36.2.18.10.4.1.1.8 |
drpt90PortAddrTableA list of MAC addresses paired with the repeater port on which they
have been seen. SEQUENCE OF Drpt90PortAddrEntry .1.3.6.1.4.1.36.2.18.10.4.2 |
drpt90PortAddrEntryA MAC address and the repeater port on which it resides. Drpt90PortAddrEntry .1.3.6.1.4.1.36.2.18.10.4.2.1 |
drpt90PortPhyAddrA MAC address seen on this port.ro OCTET STRING .1.3.6.1.4.1.36.2.18.10.4.2.1.1 |
drpt90PortAddrIndexIdentifies the module and port. The value of this object is the same
as drpt90PortIndex and is given by:
(slot number * 100) + port numberro INTEGER .1.3.6.1.4.1.36.2.18.10.4.2.1.2 |
db90ext OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.5 |
db90system OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.5.1 |
dbSysChar OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.5.1.1 |
dbSysRomVersionThe version number of the software stored in ROM. The return value is
encoded as (major_version*10 + minor version). For example, version 1.0
is returned as 10 (1*10 + 0).ro INTEGER .1.3.6.1.4.1.36.2.18.10.5.1.1.1 |
dbSysInitSwitchThis object allows the management action of initializing a device and
forcing it to run selftest. It can also be used to reset all
information added to the device's NVRAM. When read, it returns a value
of other(1). When set to a value of reset(2) the bridge will empty the
forwarding database and start relearning. When set to resetToFactory(3)
the bridge will empty the forwarding database, reset spanning tree and
clear all protocol filters and password.rw Enumeration .1.3.6.1.4.1.36.2.18.10.5.1.1.2 |
dbSysStatus OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.5.1.2 |
dbSysDeviceStateThe operational state of the device.ro Enumeration .1.3.6.1.4.1.36.2.18.10.5.1.2.1 |
dbSysNvramFailedA flag that, when set to true(1), indicates that the NVRAM failed
selftest following the last initialization of the device. Values set to
variables maintained on the bridge will not be preserved over a power
cycle of the bridge.ro Enumeration .1.3.6.1.4.1.36.2.18.10.5.1.2.2 |
db90interfaces OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.5.2 |
dbIfTableA list of interface entries. The number of entries is given by
ifNumber. SEQUENCE OF DbIfEntry .1.3.6.1.4.1.36.2.18.10.5.2.1 |
dbIfEntryA collection of objects containing information for a given interface. DbIfEntry .1.3.6.1.4.1.36.2.18.10.5.2.1.1 |
dbIfIndexIdentifies the interface. The value of this object is the same as the
ifIndex for this interface.ro INTEGER .1.3.6.1.4.1.36.2.18.10.5.2.1.1.1 |
dbIfReceiveBadFramesNumber of frames received with a bad frame check sequence or the device
received a frame loss indication from the hardware on the interface.ro Counter .1.3.6.1.4.1.36.2.18.10.5.2.1.1.2 |
dbIfTransmitErrorFramesNumber of frames that were transmitted with an error on the line.ro Counter .1.3.6.1.4.1.36.2.18.10.5.2.1.1.3 |
db90bridge OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.5.3 |
db90Char OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.5.3.1 |
db90LB100SpanningTreeVerThe version number of the Spanning Tree algorithm used by the bridge
when in the LAN Bridge 100 Spanning Tree mode.ro INTEGER .1.3.6.1.4.1.36.2.18.10.5.3.1.1 |
db90802SpanningTreeVerThe version number of the Spanning Tree algorithm used by the bridge
when in the 802.1d Spanning Tree mode.ro INTEGER .1.3.6.1.4.1.36.2.18.10.5.3.1.2 |
db90MaxForwardingDBEntriesThe maximum number of address entries that the bridge can store in its
volatile memory.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.1.3 |
db90MaxNVForwardingDBEntriesThe maximum number of permanent address entries that the bridge can
store in its NVRAM.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.1.4 |
db90MaxProtocolDBEntriesThe maximum number of protocol entries that the bridge can store in its
protocol database. These entries control the handling of frames based
on their Ethernet protocol type, IEEE 802.2 DSAP or IEEE 802 SNAP
Protocol ID.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.1.5 |
db90MaxNVProtocolDBEntriesThe maximum number of protocol entries that the bridge can store in its
NVRAM. These are retained after a power-down.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.1.6 |
db90Stat OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.5.3.2 |
db90CurrProtocolDBEntriesThe number of protocol entries that are stored in the bridge's protocol
database. These control the handling of frames based on their Ethernet
protocol type, IEEE 802.2 DSAP, or 802 SNAP Protocol ID.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.2.1 |
db90CurrNVProtocolDBEntriesThe number of protocol entries in the bridge's NVRAM. These are
retained after a power loss.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.2.2 |
db90MgmtHeardPortThe port on which this command was received.ro Enumeration .1.3.6.1.4.1.36.2.18.10.5.3.2.3 |
db90LB100BeingPolledThe address of the LAN Bridge 100 mode bridge that sent this bridge
into the LAN Bridge 100 Spanning Tree mode. If this bridge is the Root,
this object indicates the bridge that will be polled periodically to
determine if it is still necessary to stay in this Spanning Tree mode.ro OCTET STRING .1.3.6.1.4.1.36.2.18.10.5.3.2.4 |
db90TimeSinceLastHelloThe number of seconds since the bridge last sent a hello message.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.2.5 |
db90HubManagementIndicates whether the bridge is managing the hub (i.e., is capable of
managing repeaters inserted in the hub).rw Enumeration .1.3.6.1.4.1.36.2.18.10.5.3.2.6 |
db90CurrFdbEntriesThe number of entries currently active in the DECbridge 90 forwarding
database, or one more than the value of db90MaxForwardingDBEntries if
the bridge has exceeded the size of the forwarding database hardware.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.2.7 |
db90Coun OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.5.3.3 |
db90SpanningTreeModeChangesThe number of times that the bridge switched from the 802.1d Spanning
Tree mode to the LB100 Spanning Tree mode.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.3.1 |
db90Span OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.5.3.4 |
db90BestRootAgeThe age, in hundredths of seconds, of the hello message that
established the best root.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.36.2.18.10.5.3.4.1 |
db90TopologyChangeFlagA flag that indicates whether a topology change is currently in effect
on the extended LAN.ro Enumeration .1.3.6.1.4.1.36.2.18.10.5.3.4.2 |
db90TellParentFlagA flag that indicates if the bridge is attempting to propagate a
topology change towards the root.ro Enumeration .1.3.6.1.4.1.36.2.18.10.5.3.4.3 |
db90ForwardingDBShortAgingTimeThe number of seconds that the bridge keeps learned entries active
while a topology change is in effect.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.4.4 |
db90BadHelloLimitThe number of hello intervals during which the bridge receives one or
more bad hellos on a line, before the bridge performs a test on the
link. A bad hello message is one that contains inferior information
that is received on a port on which this bridge is designated.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.4.5 |
db90BadHelloResetTimerThe number of hello intervals without bad hellos that the bridge will
wait before it resets its bad hello count to zero.rw Counter .1.3.6.1.4.1.36.2.18.10.5.3.4.6 |
db90NoFrameIntervalThe number of seconds of inactivity on a line that will cause the
bridge to run a test on that line. The bridge considers a line to be
inactive if it does not receive any frames on that line.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.4.7 |
db90LB100PollTimeThe number of seconds that a root bridge in LAN Bridge 100 mode waits
between polling the LAN Bridge 100 that is keeping it in this mode.
This polling is done to determine whether the LB100 is still present on
the extended LAN.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.4.8 |
db90LB100ResponseTimeoutThe number of seconds that a Root in LAN Bridge 100 Spanning Tree mode
will wait for a response from the LAN Bridge 100 which is keeping it in
this mode, before which it will assume that the LB100 is no longer on
the extended LAN.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.4.9 |
db90LB100SpanningTreeCompatA switch that controls the Spanning Tree mode used by the bridge. If
in Auto-Select mode, the bridge will go into 802 Spanning Tree mode by
default, but will switch to LB100 mode as soon as a LB100 is detected.
In 802 Spanning Tree mode, the bridge will stay in 802 mode.ro Enumeration .1.3.6.1.4.1.36.2.18.10.5.3.4.10 |
db90PortInterfaces OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.5.3.5 |
db90IfTableA list of interface entries. The number of entries is given by
ifNumber. SEQUENCE OF Db90IfEntry .1.3.6.1.4.1.36.2.18.10.5.3.5.1 |
db90IfEntryA collection of objects containing information for a given interface. Db90IfEntry .1.3.6.1.4.1.36.2.18.10.5.3.5.1.1 |
db90IfIndexIdentifies the interface. The value of this object is the same as the
ifIndex for this interface.ro INTEGER .1.3.6.1.4.1.36.2.18.10.5.3.5.1.1.1 |
db90IfReceiveDeviceFramesThe number of frames addressed to the bridge itself that were received
on this line.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.5.1.1.2 |
db90IfExceededBadHelloLimitsThe number of times that the bad hellos on the line exceeded the bad
hello limit.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.5.1.1.3 |
db90IfEtherTableA list of interface entries for an Ethernet port. SEQUENCE OF Db90IfEtherEntry .1.3.6.1.4.1.36.2.18.10.5.3.5.2 |
db90IfEtherEntryA collection of objects containing information for a given interface. Db90IfEtherEntry .1.3.6.1.4.1.36.2.18.10.5.3.5.2.1 |
db90IfEthIndexIdentifies the interface. The value of this object is the same as the
ifIndex for this interface.ro INTEGER .1.3.6.1.4.1.36.2.18.10.5.3.5.2.1.1 |
db90IfEthFramingErrorsThe number of times that a frame received on the line contained both a
non-integer multiple of eight bits and a CRC error.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.5.2.1.2 |
db90IfEthCarrierLossesThe number of times that the bridge detected a loss of the carrier
signal while transmitting a frame on the line.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.5.2.1.3 |
db90IfEthExceededCollisionLimitsThe number of times that the bridge failed to transmit a frame on this
line after 16 attempts, the collision limit.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.5.2.1.4 |
db90IfSpanTableA list of interface entries for a port. SEQUENCE OF Db90IfSpanEntry .1.3.6.1.4.1.36.2.18.10.5.3.5.3 |
db90IfSpanEntryA collection of objects containing information for a given interface. Db90IfSpanEntry .1.3.6.1.4.1.36.2.18.10.5.3.5.3.1 |
db90IfSpIndexIdentifies the interface. The value of this object is the same as the
ifIndex for this interface.ro INTEGER .1.3.6.1.4.1.36.2.18.10.5.3.5.3.1.1 |
db90IfSpDesigRootAgeThe age, in hundredths of a second, of the last hello message received
from the designated bridge on the line.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.36.2.18.10.5.3.5.3.1.2 |
db90IfSpForwardDelayTimerThe time remaining, in hundredths of a second, before the bridge will
leave the learning state of Preforwarding, and enter the Forwarding
state.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.5.3.1.3 |
db90IfSpBadHelloCountsThe number of hello intervals during which at least one bad hello was
received.ro Counter .1.3.6.1.4.1.36.2.18.10.5.3.5.3.1.4 |
db90IfSpTopologyChangeAckFlagA flag that indicates whether a topology change notification received
on a link that we are designated on needs to be acknowledged.ro Enumeration .1.3.6.1.4.1.36.2.18.10.5.3.5.3.1.5 |
db90ProtoFilt OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.10.5.3.6 |
db90ProtoFilterOtherAction taken by the bridge on Ethernet protocol types or the 5-byte
SNAP SAPs other than those specified in the db90ProtoTable. forward(1)
indicates that a 'filter all' entry exists in the db90ProtoTable. This
value also implies that no 'forward all' entry may be added to the
db90ProtoTable. filter(2) indicates that a 'forward all' entry exists
in the db90ProtoTable. This value also implies that no 'filter all'
entry may be added to the db90ProtoTable. default(3) indicates that an
entry of either 'forward all' or 'filter all' (i.e. not just Multicast
frames) may be added to the db90ProtoTable. This value also implies
that all other protocol entries not listed in the db90ProtoTable will be
forwarded.ro Enumeration .1.3.6.1.4.1.36.2.18.10.5.3.6.1 |
db90ProtoFilterTableA table that contains filtering information about Ethernet protocol
types and 5 byte SNAP SAPs for the DECbridge 90. SEQUENCE OF Db90ProtoFilterEntry .1.3.6.1.4.1.36.2.18.10.5.3.6.2 |
db90ProtoFilterEntryA table that contains filtering characteristics for Ethernet protocol
types and 5 byte SNAP SAPs for the DECbridge 90. Db90ProtoFilterEntry .1.3.6.1.4.1.36.2.18.10.5.3.6.2.1 |
db90ProtoFilterProtocolThe protocol type or SNAP SAP in a frame to which this entry's
filtering information applies. The length is 2 for Ethernet protocol
types and 5 for SNAP SAP.rw OCTET STRING .1.3.6.1.4.1.36.2.18.10.5.3.6.2.1.1 |
db90ProtoFilterTypeThe type of this entry. unknown(1) specifies that this protocol
filter is unused. invalid(2) deletes the filter. ethernet(3) or
snap-sap(4) defines the size of db90ProtoFilterProtocol. Setting this
variable to a value of deleteAllProtocols(5) will cause all protocols,
both volatile and non-volatile, to be deleted.rw Enumeration .1.3.6.1.4.1.36.2.18.10.5.3.6.2.1.2 |
db90ProtoFilterStatusAction taken by the bridge when it sees this Ethernet protocol type or
SNAP SAP in a received frame. Note that this value must be identical
to db90ProtoFilterOther unless db90ProtoFilterMulticastFlag is
multicastOnly(2) or there are no other entries with
db90ProtoFilterMulticastFlag equal to allFrames(1).rw Enumeration .1.3.6.1.4.1.36.2.18.10.5.3.6.2.1.3 |
db90ProtoFilterMulticastFlagIdentifies whether or not filtering is based on the multicast bit in
the MAC destination address. If allFrames(1), then filtering is
performed as per db90ProtoFilterStatus. For multicastOnly(2),
multicast frames for this protocol are always filtered and unicast
frames are always forwarded; this is true regardless of the value of
db90ProtoFilterOther.rw Enumeration .1.3.6.1.4.1.36.2.18.10.5.3.6.2.1.4 |
db90ProtoFilterPortMaskMust be allPorts(3) unless db90ProtoFilterMulticastFlag is
multicastOnly, in which case any specification is valid.rw Enumeration .1.3.6.1.4.1.36.2.18.10.5.3.6.2.1.5 |