DECHUB90-MIB: View SNMP OID List / Download MIB

There have been three consecutive failures to enter a correct password when attempting to log into the DECagent 90 console port.

An error in the non-volatile storage on the DECagent 90 has occurred. Some configuration information may have been lost.

An 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.

A 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.

A 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.

The 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.

The 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.

The 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.

Identifies 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. Enumeration: 'decstack90': 6, 'unknown': 1, 'invalid': 2, 'dechub90': 4, 'standAloneCommunity': 3, 'dechub900': 5.

Media on the backplane of hub. Enumeration: 'unknown': 1, 'ethernet': 2.

The value of the sysUpTime at the time a module was added or removed from this community.

Number 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.

A 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.

Contains objects defining characteristics of modules in the community.

The 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.

- 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. Enumeration: 'decmau900TC': 25, 'decagent90': 7, 'decwanrouter90': 15, 'decrepeater900FL': 26, 'decbridge90FL': 14, 'unknown': 1, 'decserver90TL': 9, 'decrepeater900SL': 23, 'decserver90Lplus': 8, 'decbrouter90T1': 10, 'decbrouter90T2': 11, 'decagent900RA': 24, 'empty': 2, 'decrepeater90C': 5, 'decserver90Lplus2': 18, 'decbridge90': 4, 'decmau900TL': 21, 'decbrouter90T2A': 20, 'decrepeater90T': 6, 'decserver90L': 3, 'decserver90M': 19, 'decpacketprobe90plus': 17, 'decrepeater90FL': 12, 'decpacketprobe90': 16, 'decrepeater90FA': 13, 'decrepeater900TL': 22.

A 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.

A textual description of the version level of the hardware and firmware of the module.

Time since the counters of this module were zeroed. Devices which do not support MOP counters will return a 'noSuchName' response.

An 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.

The 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.

A 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.

The 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.

Password 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.

Setting 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.

The 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. Enumeration: 'on': 2, 'off': 1.

For 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.

For 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.

The IP address of the device in the given slot. This value is returned only for devices which implement their own on-board SNMP agent.

The 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.

The 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.

The 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. Enumeration: 'unreachable': 2, 'reachable': 1, 'not-present': 4, 'present': 3.

Indicates 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. Enumeration: 'none': 1, 'conflict': 2.

If 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.

A 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. Enumeration: 'ready': 1, 'reset': 2, 'resetToFactory': 3.

A table of IP addresses to which this device will send SNMP traps.

Each entry contains an IP address to which all SNMP traps will be sent by this community.

An 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.

Indicates 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.

The 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.

The 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.

The 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.

The 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.

The 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.

The 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.

The number of times the flash memory on this DECagent 90 has been erased. This number is the total of erasures for all flash segments.

A 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. Enumeration: 'ready': 1, 'reset': 3, 'resetToFactory': 4, 'setsDisabled': 2.

Number of entries in the da90CommunityTable.

A table of community strings for client communities.

Contains community type and strings, including the read-only profile, the read-write profile and a trap string.

Index into hub-community string pair table, identifies the community being accessed.

Identifies 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. Enumeration: 'active': 3, 'unknown': 1, 'invalid': 2.

Community 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.

Community 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.

Community 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.

The slot number in which the managing DECagent 90 resides.

The 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.

An 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.

The index into the errorlog table.

The 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.

The uptime, in hundredths of a second, of the DECagent when this entry was logged.

The number of times this row in the errorlog table has been written.

A textual description of the error for this errorlog entry.

The 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.

The 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). Enumeration: 'master': 2, 'slave': 1.

Indicates whether the DECagent 90 is managing the hub (i.e. capable of directly managing repeaters, terminal servers and bridges and discovering other modules). Enumeration: 'master': 2, 'slave': 1.

A 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.

This 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. Enumeration: 'cancel': 4, 'start-write': 3, 'other': 1, 'start-read': 2.

The 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). Enumeration: 'failure': 3, 'none': 1, 'success': 2.

The 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.

The 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.

A 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). Enumeration: 'readFailed': 2, 'none': 1, 'timedOut': 3, 'unknownFailure': 5, 'crcFailure': 4.

This 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. Enumeration: 'reset': 3, 'console': 1, 'slip': 2.

Number of DECserver 90 modules represented in the ds90LModuleTable.

A table of DECserver 90 modules installed in the group. The number of entries is given by ds90LNumberModules.

Contains objects defining characteristics of DECserver 90 modules in the group.

The slot index value which addresses the dh90SlotTable for this module.

A 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.

A 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.)

A 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.)

A 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.

A count of the number of LAT circuit messages received by this DECserver 90 since it last reinitialized or zeroed counters.

A count of the number of LAT circuit messages transmitted by this DECserver 90 since it last reinitialized or zeroed counters.

A count of the number of LAT solicits accepted by this DECserver 90 since it last reinitialized or zeroed counters.

A count of the number of LAT solicits rejected by this DECserver 90 since it last reinitialized or zeroed counters.

A count of the number of duplicate LAT messages the DECserver 90 LAT implementation has discarded since it last reinitialized or zeroed counters.

A count of the total number of LAT circuit messages this DECserver 90 has retransmitted since it last reinitialized or zeroed counters.

A count of the number of illegal LAT slots this DECserver 90 has received on all LAT sessions since it last reinitialized or zeroed counters.

A count of the number of illegal multicast LAT messages received on this DECserver 90 since it last reinitialized or zeroed counters.

This 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.

This 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.

This counts the number of invalid LAT messages received on its entry's LAT circuit since the DECserver last reinitialized or zeroed counters.

Setting 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. Enumeration: 'enable': 1, 'disable': 2.

A 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. Enumeration: 'ready': 1, 'reset': 3, 'resetToFactory': 4, 'zeroCounters': 2.

Contains 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.

A 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.

A single LAT session instance this DECserver 90 currently provides.

The value of charPortIndex for this port.

Enables and disables remote modification of the port by the host system. Enumeration: 'enable': 2, 'disable': 1.

Selects the type of device connected to the port. Enumeration: 'terminal': 1, 'printer': 2.

Determines if the port responds to local or remote break. Enumeration: 'remote': 2, 'local': 1.

Setting 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. Enumeration: 'enable': 2, 'disable': 1.

Enables 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. Enumeration: 'enable': 1, 'disable': 2.

Enables 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. Enumeration: 'enable': 2, 'disable': 1.

A 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. Enumeration: 'disabled': 2, 'enabled': 1.

The 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.

The 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.

The 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.

A 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. Enumeration: 'disabled': 2, 'enabled': 1.

The 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.

The 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.

The 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.

The list of all LAT sessions active on this DECserver 90.

A single LAT session instance this DECserver 90 currently provides.

The value of charPortIndex for the port to which this session belongs.

The session index in the context of the port, a non-zero positive integer. Will be 1 for the DECserver 90L, 4 for DECserver 90L+.

The name of the remote node providing the service for this session.

The service to which this session is connected.

The name of the port at the remote node providing the connection, for example, LAT121.

A 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.

A collection of objects containing information for a given interface.

Identifies the module and port. The value of this object is given by: (slot number * 100) + port number

The text description of the port given by the network manager. Setting a value containing embedded spaces or tabs will result in a 'badValue' response.

The desired state of the port. Enumeration: 'disabled': 2, 'enabled': 1.

The 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. Enumeration: 'active': 4, 'unknown': 1, 'managementPartitioned': 3, 'inactive': 5, 'autoPartitioned': 2.

The physical medium type of the port. Enumeration: 'aui': 5, 'unknown': 1, 'thinWire': 3, 'fiberOptic': 4, 'twistedPair': 2.

The number of times this port has partitioned. This value is significant only if drpt90PortStatus is not unknown(1).

Errors currently detected on the port. Enumeration: 'notPartitioned': 0, 'transmitCarrierDropoutAndMgmtPart': 11, 'excessiveLengthAndMgmtPart': 3, 'excessiveLength': 2, 'excessiveCollisionsAndMgmtPart': 5, 'jabberAndMgmtPart': 7, 'nocarrierLoopback': 8, 'transmitCarrierDropout': 10, 'excessiveCollisions': 4, 'nocarrierLoopbackAndMgmtPart': 9, 'jabber': 6, 'managementPartitioned': 1.

The number of jam bits being used on the port segment. Enumeration: 'unknown': 1, 'jb128': 3, 'jb96': 2.

A list of MAC addresses paired with the repeater port on which they have been seen.

A MAC address and the repeater port on which it resides.

A MAC address seen on this port.

Identifies the module and port. The value of this object is the same as drpt90PortIndex and is given by: (slot number * 100) + port number

The 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).

This 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. Enumeration: 'reset': 2, 'resetToFactory': 3, 'other': 1.

The operational state of the device. Enumeration: 'broken': 3, 'init': 1, 'operate': 2.

A 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. Enumeration: 'false': 2, 'true': 1.

A list of interface entries. The number of entries is given by ifNumber.

A collection of objects containing information for a given interface.

Identifies the interface. The value of this object is the same as the ifIndex for this interface.

Number of frames received with a bad frame check sequence or the device received a frame loss indication from the hardware on the interface.

Number of frames that were transmitted with an error on the line.

The version number of the Spanning Tree algorithm used by the bridge when in the LAN Bridge 100 Spanning Tree mode.

The version number of the Spanning Tree algorithm used by the bridge when in the 802.1d Spanning Tree mode.

The maximum number of address entries that the bridge can store in its volatile memory.

The maximum number of permanent address entries that the bridge can store in its NVRAM.

The 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.

The maximum number of protocol entries that the bridge can store in its NVRAM. These are retained after a power-down.

The 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.

The number of protocol entries in the bridge's NVRAM. These are retained after a power loss.

The port on which this command was received. Enumeration: 'backbone': 1, 'workgroup': 2.

The 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.

The number of seconds since the bridge last sent a hello message.

Indicates whether the bridge is managing the hub (i.e., is capable of managing repeaters inserted in the hub). Enumeration: 'enable': 1, 'disable': 2.

The 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.

The number of times that the bridge switched from the 802.1d Spanning Tree mode to the LB100 Spanning Tree mode.

The age, in hundredths of seconds, of the hello message that established the best root.

A flag that indicates whether a topology change is currently in effect on the extended LAN. Enumeration: 'false': 2, 'true': 1.

A flag that indicates if the bridge is attempting to propagate a topology change towards the root. Enumeration: 'false': 2, 'true': 1.

The number of seconds that the bridge keeps learned entries active while a topology change is in effect.

The 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.

The number of hello intervals without bad hellos that the bridge will wait before it resets its bad hello count to zero.

The 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.

The 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.

The 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.

A 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. Enumeration: 'ieee802': 2, 'autoSelect': 1.

A list of interface entries. The number of entries is given by ifNumber.

A collection of objects containing information for a given interface.

Identifies the interface. The value of this object is the same as the ifIndex for this interface.

The number of frames addressed to the bridge itself that were received on this line.

The number of times that the bad hellos on the line exceeded the bad hello limit.

A list of interface entries for an Ethernet port.

A collection of objects containing information for a given interface.

Identifies the interface. The value of this object is the same as the ifIndex for this interface.

The number of times that a frame received on the line contained both a non-integer multiple of eight bits and a CRC error.

The number of times that the bridge detected a loss of the carrier signal while transmitting a frame on the line.

The number of times that the bridge failed to transmit a frame on this line after 16 attempts, the collision limit.

A list of interface entries for a port.

A collection of objects containing information for a given interface.

Identifies the interface. The value of this object is the same as the ifIndex for this interface.

The age, in hundredths of a second, of the last hello message received from the designated bridge on the line.

The time remaining, in hundredths of a second, before the bridge will leave the learning state of Preforwarding, and enter the Forwarding state.

The number of hello intervals during which at least one bad hello was received.

A flag that indicates whether a topology change notification received on a link that we are designated on needs to be acknowledged. Enumeration: 'false': 2, 'true': 1.

Action 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. Enumeration: 'forward': 1, 'filter': 2, 'default': 3.

A table that contains filtering information about Ethernet protocol types and 5 byte SNAP SAPs for the DECbridge 90.

A table that contains filtering characteristics for Ethernet protocol types and 5 byte SNAP SAPs for the DECbridge 90.

The 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.

The 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. Enumeration: 'deleteAllProtocols': 5, 'unknown': 1, 'snap-sap': 4, 'invalid': 2, 'ethernet': 3.

Action 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). Enumeration: 'forward': 1, 'filter': 2.

Identifies 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. Enumeration: 'allFrames': 1, 'multicastOnly': 2.

Must be allPorts(3) unless db90ProtoFilterMulticastFlag is multicastOnly, in which case any specification is valid. Enumeration: 'backbone': 1, 'workGroup': 2, 'allPorts': 3.