ODSLANBlazer7000-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for ODSLANBlazer7000-MIB.
388
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
388 total| Object Name |
|---|
ods OBJECT IDENTIFIER .1.3.6.1.4.1.50 |
RFC1155-SMI Unknown .1.3.6.1.4.1.50 |
odsTPS OBJECT IDENTIFIER .1.3.6.1.4.1.50.8 |
odsLANBlazer OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1 |
odsLANBlazerMibs OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2 |
odsLANBlazer7000Mib OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1 |
lanBlazer7000Agent OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.1 |
lanBlazer7000AgentGen OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.1.1 |
lanBlazer7000AgentMIBVersionThe version of the LANBlazer 700 Enterprise Specific MIB that this
agent supports.ro DisplayString .1.3.6.1.4.1.50.8.1.2.1.1.1.1 |
lanBlazer7000AgentMgrIndexThe value of this object represents the index into the community table that
is used to authenticate SNMP requests for this manager.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.1.1.2 |
lanBlazer7000AgentCommunity OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.1.2 |
lanBlazer7000CommunityTable SEQUENCE OF LanBlazer7000CommunityEntry .1.3.6.1.4.1.50.8.1.2.1.1.2.1 |
lanBlazer7000CommunityEntry LanBlazer7000CommunityEntry .1.3.6.1.4.1.50.8.1.2.1.1.2.1.1 |
lanBlazer7000CommunityIndexAn index that uniquely identifies this entry.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.1.2.1.1.1 |
lanBlazer7000CommunityStringThe community string included in the SNMP PDU used for authentication
purposes.rw DisplayString .1.3.6.1.4.1.50.8.1.2.1.1.2.1.1.2 |
lanBlazer7000CommunityAddressTypeThe type of address associated with this community. If set to any(1), only
the community string is authenticated.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.1.2.1.1.3 |
lanBlazer7000CommunityAddressIf the address type is any, then the value of this object is a null string. If
the type is ipv4(2), then this value represents a 4 byte IP address.rw NetworkAddress .1.3.6.1.4.1.50.8.1.2.1.1.2.1.1.4 |
lanBlazer7000CommunityAccessThe MIB access supported for this community entry.
A Get or GetNext SNMP PDU is authenticated if the value of this object
is read-only(2) or read-write(3). A Set request will be honored if the value
of this object is read-write(3).
If more granular access control is desired, then the value of this object is set
to more-specific(4), and the view table should be consulted. This enables
the capability to set different access rights to different branches of the MIB
for a particular community.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.1.2.1.1.5 |
lanBlazer7000CommunityTrapReceiverIf set to enable(1), this community entry is considered a trap receiver.
When the agent generates an SNMP trap, a copy will be sent to this host
using this community string.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.1.2.1.1.6 |
lanBlazer7000CommunitySecurityLevelSecure tables are only accessible from users with security clearance. For
example, this table (the community table) is only accessible by parties that
have the security clearance.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.1.2.1.1.7 |
lanBlazer7000CommunityStatusrw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.50.8.1.2.1.1.2.1.1.8 |
lanBlazer7000AgentWeb OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.1.3 |
lanBlazer7000AgentWebServerURLThe URL of where the document server software is
installed. The switch uses this location to find online
help and bimapped graphics. Enter the host name or IP
address of the HTTP server at the HTTP Server Location
prompt, followed by ':2010'. For example, for a host
named 'phantom,', enter 'http://phantom:2010'. If no
server is desired or installed, set this object to the
empty string.rw DisplayString .1.3.6.1.4.1.50.8.1.2.1.1.3.1 |
lanBlazer7000AgentWebServerHelpDirectoryThe subdirectory that contains the help files on the
document server. Typically, this directory is 'help'.rw DisplayString .1.3.6.1.4.1.50.8.1.2.1.1.3.2 |
lanBlazer7000Chassis OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3 |
lanBlazer7000ChassisGen OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.1 |
lanBlazer7000ChassisTypeThe model of the chassis that this agent is managing.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.1.1 |
lanBlazer7000ChassisSlotsThe number of slots available in this chassis. If this chassis is a stackable
chassis, the total capacity of stacking units.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.3.1.2 |
lanBlazer7000Inventory OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.2 |
lanBlazer7000InventoryTableA table of inventory information. SEQUENCE OF LanBlazer7000InventoryEntry .1.3.6.1.4.1.50.8.1.2.1.3.2.1 |
lanBlazer7000InventoryEntryInventory information related to this device. LanBlazer7000InventoryEntry .1.3.6.1.4.1.50.8.1.2.1.3.2.1.1 |
lanBlazer7000InventoryResourceTypeThe resource class of this inventory item.ro ResourceType .1.3.6.1.4.1.50.8.1.2.1.3.2.1.1.1 |
lanBlazer7000InventoryResourceIndexThe resource identifier of this inventory item.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.3.2.1.1.2 |
lanBlazer7000InventoryModelNumberThe model number of this device.ro DisplayString .1.3.6.1.4.1.50.8.1.2.1.3.2.1.1.3 |
lanBlazer7000InventorySerialNumberThe serial number of this device.ro DisplayString .1.3.6.1.4.1.50.8.1.2.1.3.2.1.1.4 |
lanBlazer7000InventoryVersionThe revision number of this device.ro DisplayString .1.3.6.1.4.1.50.8.1.2.1.3.2.1.1.5 |
lanBlazer7000InventoryManufactureInfoInformation related to the manufacturing of this device.ro DisplayString .1.3.6.1.4.1.50.8.1.2.1.3.2.1.1.6 |
lanBlazer7000InventoryScratchPadA scratch pad area available for keeping user-supplied inventory
information.rw DisplayString .1.3.6.1.4.1.50.8.1.2.1.3.2.1.1.7 |
lanBlazer7000PowerSystems OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.3 |
lanBlazer7000PowerSupplies OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.3.1 |
lanBlazer7000PowerSupplyTableA table of information related to each power supply in the system. SEQUENCE OF LanBlazer7000PowerSupplyEntry .1.3.6.1.4.1.50.8.1.2.1.3.3.1.1 |
lanBlazer7000PowerSupplyEntryAn entry providing information about a particular power supply in the
system. LanBlazer7000PowerSupplyEntry .1.3.6.1.4.1.50.8.1.2.1.3.3.1.1.1 |
lanBlazer7000PowerSupplyIndexAn index that uniquely identifies this power supply. This index
corresponds to the lanBlazer7000ResourceIndex of the power supply type
resource.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.3.3.1.1.1.1 |
lanBlazer7000PowerSupplyTypeAn enumerated integer describing the type of power supply.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.3.1.1.1.2 |
lanBlazer7000PowerSupplyStatusThe status of this power supply. Okay(1) indicates the power supply is
operating properly. Faulty(2) indicates that the power supply is not
functioning properly. In this case, more information can be determined
from the other power supply attributes.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.3.1.1.1.3 |
lanBlazer7000PowerSupplyInputStatusThe status of the input power feed (e.g. the AC power cord) to this
power supply.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.3.1.1.1.4 |
lanBlazer7000PowerSupplyOutputStatusThe status of the output power from this power supply.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.3.1.1.1.5 |
lanBlazer7000PowerSupplyOutputCapacityThe total capacity of power supplied by this supply in Watts.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.3.3.1.1.1.6 |
lanBlazer7000PowerMgmtGen OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.3.2 |
lanBlazer7000PowerCapacityThe total capacity (in Watts) of power available (currently) in the system.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.3.3.2.1 |
lanBlazer7000PowerUsedThe total power (in Watts) currently being consumed in the system.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.3.3.2.2 |
lanBlazer7000PowerMgmtCtl OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.3.3 |
lanBlazer7000PowerControlTableThis table manages the power attributes associated with each module. SEQUENCE OF LanBlazer7000PowerControlEntry .1.3.6.1.4.1.50.8.1.2.1.3.3.3.1 |
lanBlazer7000PowerControlEntryAn entry in the power control table manages the power attributes of the
specified module. LanBlazer7000PowerControlEntry .1.3.6.1.4.1.50.8.1.2.1.3.3.3.1.1 |
lanBlazer7000PowerControlUsedThe total power (in Watts) used by this module.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.3.3.3.1.1.1 |
lanBlazer7000PowerControlPriorityThe priority of this module to be considered in the event of a power
supply failure where the amount of power used exceeds the system
capacity. Low priority modules will be powered down before higher
priority modules.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.3.3.1.1.2 |
lanBlazer7000PowerControlModeNormally, a module power mode is enable(1).
In the event of a power supply failure resulting in a power shortage, or in
the event of this module being inserted without enough available power,
the mode will be poweredDown(3). Setting this object to the value of
poweredDown(3) will result in an error.
When enough power is available, the module will power back up when in
this mode. A module may be powered down through administrative
action by setting the value of this object to disable(2). In this mode, the
module will remain powered down until the mode is set back to enable.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.3.3.1.1.3 |
lanBlazer7000Temperature OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.4 |
lanBlazer7000TempTableA table of information related to the temperature within the system. SEQUENCE OF LanBlazer7000TempEntry .1.3.6.1.4.1.50.8.1.2.1.3.4.1 |
lanBlazer7000TempEntryAn entry providing temperature information related to a specific
temperature probe in the system. LanBlazer7000TempEntry .1.3.6.1.4.1.50.8.1.2.1.3.4.1.1 |
lanBlazer7000TempIndexA unique index that identifies this temperature probe. This index
corresponds to the lanBlazer7000ResourceIndex for temperature probe type
resources.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.3.4.1.1.1 |
lanBlazer7000TempValueThe current temperature reading of this temperature probe in degrees
Celsius.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.3.4.1.1.2 |
lanBlazer7000TempUpperLimitThe upper temperature limit of this temperature probe in degrees
Celsius.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.3.4.1.1.3 |
lanBlazer7000TempUpperWarningThe upper temperature warning of this temperature probe in degrees
Celsius.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.3.4.1.1.4 |
lanBlazer7000TempLowerWarningThe lower temperature warning of this temperature probe in degrees
Celsius.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.3.4.1.1.5 |
lanBlazer7000TempLowerLimitThe lower temperature limit of this temperature probe in degrees
Celsius.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.3.4.1.1.6 |
lanBlazer7000Modules OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.5 |
lanBlazer7000ModuleTableA table of information related to the modules in the system. SEQUENCE OF LanBlazer7000ModuleEntry .1.3.6.1.4.1.50.8.1.2.1.3.5.1 |
lanBlazer7000ModuleEntryAttributes related to managing this module. LanBlazer7000ModuleEntry .1.3.6.1.4.1.50.8.1.2.1.3.5.1.1 |
lanBlazer7000ModuleIndexAn index that uniquely identifies this module. This index corresponds to
the lanBlazer7000ResourceIndex associated with module type resources.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.3.5.1.1.1 |
lanBlazer7000ModuleNameA user-assignable name for this module.rw DisplayString .1.3.6.1.4.1.50.8.1.2.1.3.5.1.1.2 |
lanBlazer7000ModuleTypeAn enumerated integer that is unique for each module model.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.5.1.1.3 |
lanBlazer7000ModuleBaseTypeThe base type of this module. This object is used to describe the core
functions of the module. Often, base designs are derived into multiple
module types which are typically just packaging variations (e.g. changing the
connector types). The value of this object corresponds to the value of
lanBlazer7000ResourceBaseType.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.5.1.1.4 |
lanBlazer7000ModuleSlotWidthThe number of slots that this module occupies.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.3.5.1.1.5 |
lanBlazer7000ModuleSlotOffsetThe slot offset (one based) that identifies, along with the slot width and
slot location, the actual slots that this module occupies. The offset identifies
which slot within the width of the module that this module reports as its
slot number.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.3.5.1.1.6 |
lanBlazer7000ModulePortsThe total number of ports associated with this module.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.3.5.1.1.7 |
lanBlazer7000Ports OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.6 |
lanBlazer7000PortMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.6.1 |
lanBlazer7000PortTableA table of information related to every data port in this data networking
system. SEQUENCE OF LanBlazer7000PortEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.1.1 |
lanBlazer7000PortEntryA data port associated with this data networking system. LanBlazer7000PortEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.1.1.1 |
lanBlazer7000PortIndexAn index that uniquely identifies this port. Typically, ports are child
resources of the module that contains them. In these cases, ports are
identified by their module and their relative physical position on that
module.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.3.6.1.1.1.1 |
lanBlazer7000PortNameThe user-assigned name for this port.
Note that setting this object for an internal(1) port results in an error.rw DisplayString .1.3.6.1.4.1.50.8.1.2.1.3.6.1.1.1.2 |
lanBlazer7000PortTypeAn internal(1) port does not have an external connection.
An ether-ten-oneHundred(2) port is an Ethernet port which can be switched between
10 and 100 megabits per second.
An ether-oneHundred(3) port is a 100 megabits per second Fast Ethernet port.
An ether-gigabit(4) port is a 1000 megabits per second Gigabit Ethernet port.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.1.1.1.3 |
lanBlazer7000PortBaseTypeThe base type of this port. This object may be useful to help manage new
port types that are similar in nature to legacy port types.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.1.1.1.4 |
lanBlazer7000PortModeThe mode of this port. When set to enable(1), this port passes data.
When set to disable(2), the port does not receive or transmit data, nor does
it generate port-level signaling e.g. link integrity pulses.
Note that setting an internal(1) port to disable(2) results in an error.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.1.1.1.5 |
lanBlazer7000PortStatusThe status of this port. Disabled(1) means that this port has been disabled
through management action. Okay(2) indicates that this port is operating
properly. Warning(3) indicates that this port is encountering an abnormal
condition that, however, allows it to continue to pass data. LinkFailure(5)
means that this port is unable to pass data.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.1.1.1.6 |
lanBlazer7000PortConnectorThe connector type associated with this port.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.1.1.1.7 |
lanBlazer7000PortSpeedStateThe data rate of this port in bits per second. For example, a standard
Ethernet port (e.g. 10BASE-T) would indicate a value of ten-megabits-per-second((1)
indicating that the port supports a data rate of 10Mb/s. For ports that can
change their data rate (e.g. 10/100 ports), the value of this object indicates
the current state of the port's speed capability.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.1.1.1.8 |
lanBlazer7000PortDuplexStateThe value of this object indicates whether this port is operating in full- or
half-duplex mode.
The value under-negotiation(3) indicates that the port has not selected an
operational duplex setting yet.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.1.1.1.9 |
lanBlazer7000PortGroupBindingEach port is associated with a port group. Typically, a port will belong to
a port group of one and the value of this object will be the same as the
port index for this instance. That is, this port will point to itself.
The intent of this object is to help manage ports that have hierarchical
relationships. For example, an ATM port typically has a physical port and
multiple logical ports (e.g. each logical port corresponding to an instance of
an emulated LAN). In this case, each LANE instance would refer to the
instance of the physical port associated with the ATM front-end.
Another example is an FDDI DAS type port. In this case, there is a logical
port associated with the FDDI switch port which is connected to the two
FDDI physical port connectors. The physical FDDI ports both point to
the logical instance of an FDDI port.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.3.6.1.1.1.10 |
lanBlazer7000PortFlowControlMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.6.2 |
lanBlazer7000PortFlowControlTableA table of ports that support flow control. SEQUENCE OF LanBlazer7000PortFlowControlEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.2.1 |
lanBlazer7000PortFlowControlEntryConfiguration objects related to port based flow control. LanBlazer7000PortFlowControlEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.2.1.1 |
lanBlazer7000PortFlowControlModeFlow control is used to prevent or reduce the dropping of frames due to
the lack of buffer space. Overall, networks are more efficient when a
sending station is asked to pause in its sending process, rather than having
the transmitted frames dropped.
Flow control is not as efficient when used in conjunction with a shared
ports, i.e. when used with a repeater. Therefore, flow control is not
recommended for a port connected to shared topologies.
Flow control is most effective when the port is directly connected to an
end-station, especially when connected to a server. Flow control is
recommended for ports connected directly to end-stations.
When the port is in half-duplex mode, back pressure is used to control
the incoming flow. Back pressure essentially forces collisions for short
periods of time.
When the port is in full-duplex mode, IEEE 802.3 standard pause frames
are used to control the incoming flow.
Note that setting an ether-gigabit(4) port to enable-with-aggressive-backoff(3)
results in an error.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.2.1.1.21 |
lanBlazer7000PortDuplexMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.6.3 |
lanBlazer7000PortDuplexTableA table of ports that support full- and half-duplex data communications. SEQUENCE OF LanBlazer7000PortDuplexEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.3.1 |
lanBlazer7000PortDuplexEntryA port device configuration that controls the duplex mode of this port. LanBlazer7000PortDuplexEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.3.1.1 |
lanBlazer7000PortDuplexModeA point-to-point Ethernet port may be configured to support half or full
duplex communications.
A full-duplex(2) port transmits and receives data concurrently, effectively
doubling the data rate of the port.
Half-duplex(1) ports transmit or receive data, but not at the same time.
Half-duplex ports use CSMA/CD as the access method to the network.
Ports that are connected to shared segments (i.e. connected to a repeater),
should always be configured to be in half-duplex mode.
This object indicates the desired duplexity of this port. If
auto-negotiation is turned on for this port, then this value is ignored.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.3.1.1.31 |
lanBlazer7000PortSpeedMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.6.4 |
lanBlazer7000PortSpeedTableA table of port devices that support multiple speeds. SEQUENCE OF LanBlazer7000PortSpeedEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.4.1 |
lanBlazer7000PortSpeedEntryA port that supports multiple speeds. LanBlazer7000PortSpeedEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.4.1.1 |
lanBlazer7000PortSpeedModeSome of these values may not be applicable to certain types of ports.
This object indicates the desired data rate of this port. If
auto-negotiation is turned on for this port, then this value is ignored.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.4.1.1.41 |
lanBlazer7000PortAutoNegotiationMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.6.5 |
lanBlazer7000PortAutoNegotiationTableA table of ports that support auto-negotiation. SEQUENCE OF LanBlazer7000PortAutoNegotiationEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.5.1 |
lanBlazer7000PortAutoNegotiationEntryAttributes associated with a port that supports auto-negotiation. LanBlazer7000PortAutoNegotiationEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.5.1.1 |
lanBlazer7000PortAutoNegotiationModeSetting this object to autoNegotiate(1) causes this port to negotiate the
duplex mode and the port speed, subject to the port's capabilities.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.5.1.1.51 |
lanBlazer7000PortAutoNegotiationSpeedAdvertisementThe speed to advertise while auto-negotiating.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.5.1.1.52 |
lanBlazer7000PortAutoNegotiationDuplexAdvertisementThe duplexity to advertise while auto-negotiating.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.5.1.1.53 |
lanBlazer7000PortRateLimitMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.6.6 |
lanBlazer7000PortRateLimitTableA table of ports that support the ability to limit the rate of floods. SEQUENCE OF LanBlazer7000PortRateLimitEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.6.1 |
lanBlazer7000PortRateLimitEntryThe rate limit configuration associated with this port. LanBlazer7000PortRateLimitEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.6.1.1 |
lanBlazer7000PortRateLimitModeThis object configures whether rate limiting is enabled for this port (the
factory default is enable(1)). Enabling rate limiting for this port prevents
floods from overwhelming the output buffer associated with this port.
Normally, rate limiting will only consider frames that are flooded to this
port. This typically does not include known multicasts. However, known
multicasts can be included in the flood limiting by setting the value of this
object to enableIncludeKnownMulticast(3).rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.6.1.1.61 |
lanBlazer7000PortRateLimitRateThe percentage of the port's transmitted data allowed to be floods (or floods
and known multicasts). For example, the factory default setting of
twenty-percent(4) indicates that 20% of the data rate can be floods. For 10 Mb/s
ports, this is equivalent to a maximum rate of approximately 3000 flooded pps;
for 100 Mb/s ports, a maximum rate of approximately 30,000 flooded pps.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.6.1.1.62 |
lanBlazer7000PortRateLimitBurstSizeThe maximum number of consecutive transmitted flooded (or flooded and known
multicasted) packets. Typically, the burst size is set so as to not overflow the
port's buffer.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.6.1.1.63 |
lanBlazer7000PortPacePriorityMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.6.7 |
lanBlazer7000PortPacePriorityTableA table of ports that support the ability to classify frame priority based on
3Com Pace(r) Prioritization. SEQUENCE OF LanBlazer7000PortPacePriorityEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.7.1 |
lanBlazer7000PortPacePriorityEntryA port that supports 3Com Pace(r) priority. LanBlazer7000PortPacePriorityEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.7.1.1 |
lanBlazer7000PortPacePriorityModeWhen Pace priority is enabled, this port will detect frames that use 3Com
Corporation's Pace(r) Priority signaling. Frames signaled with priority in
this manner are mapped to traffic priority level 4 (on scale of 0-7).rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.7.1.1.71 |
lanBlazer7000PortCategoryMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.6.8 |
lanBlazer7000PortCategoryTableA table of ports that support the port category feature. Currently, all
ports support this capability. SEQUENCE OF LanBlazer7000PortCategoryEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.8.1 |
lanBlazer7000PortCategoryEntryA port that supports port categorization. LanBlazer7000PortCategoryEntry .1.3.6.1.4.1.50.8.1.2.1.3.6.8.1.1 |
lanBlazer7000PortCategoryModeBy default, all ports are considered service ports. A
service port is a port that provides a networks service
such as a connection to a server, other switches, or
the like. A service port will trigger the service port
event for status changes with the alarm severity and
will trigger an alarm in the alarm table on link
failure.
In contrast, user ports trigger the user link event
with warning severity. They do not trigger an alarm
upon link failures. User ports are useful to prevent
floods of traps or entries in the alarm table. This is
especially true for ports connected to user hosts that
power up in the morning and power down again at the end
of the work day.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.6.8.1.1.81 |
lanBlazer7000BufferMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.3.7 |
lanBlazer7000BufferTableA table of frame buffers in the system. SEQUENCE OF LanBlazer7000BufferEntry .1.3.6.1.4.1.50.8.1.2.1.3.7.1 |
lanBlazer7000BufferEntryObjects related to the management of this frame buffer. LanBlazer7000BufferEntry .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1 |
lanBlazer7000BufferIndexThe unique index that identifies this buffer within the system. Buffers are
indexed first by their module association and then a unique index within
that module.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.1 |
lanBlazer7000BufferFabricPortThe switch fabric port associated with this buffer.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.2 |
lanBlazer7000BufferFabricPortDirectionThe value of this object indicates whether the buffer is used for buffering
frames going into the switching fabric or coming out of the fabric.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.3 |
lanBlazer7000BufferSwitchPortThe switch port associated with this frame buffer. Some buffers are not
associated with any one switch port. In those cases, the value of the
resource ID returned will be the null resource ID.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.4 |
lanBlazer7000BufferMemoryThe amount of memory available for frame buffering in Kilobytes (KB).ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.5 |
lanBlazer7000BufferAgeTimerConfigures the timer used for aging frames in this buffer. If the timer
expires for a frame, the frame is dropped and the event is counted in the
stale drop counter. By default, the age timer is set to a 0.25 seconds
(quarter of a second).
The actual time that a frame may be aged out may vary. When set to a
quarter of a second (250ms), the actual time may vary between 160ms and
320ms. When set to a second (1000ms), the time may vary between 640ms
and 1.28 seconds (1028ms).rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.6 |
lanBlazer7000BufferPriorityServicingThe value of this object configures how often the normal priority queue is
serviced relative to the high priority queue. By default, the normal priority
queue is serviced every thousand frames(3). This means that the normal
priority queue is guaranteed to be serviced after servicing, at most, one
thousand high priority frames.
It is important to service the normal priority queue for two reasons. One is
to prevent starvation for frames on the normal priority queue. The other
reason is that frames cannot be aged if they are not serviced (see the age
timer).rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.7 |
lanBlazer7000BufferPriorityAllocationThis object controls how much of the total buffer space should be
allocated to high priority queue. Please be warned that setting this object to
a different value causes the associated buffer to reset, causing a short loss of
data.
Setting the value of this object to none(1) not only allocates the entire buffer
space to normal traffic, but also has the side effect of disabling the priority
threshold. In other words, all traffic will be considered as normal priority
traffic.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.8 |
lanBlazer7000BufferPriorityThresholdThis object configures the threshold for which frames are considered high
priority. Frames may have a priority classification ranging from 0-7, 7
being the highest. By default, every frame that has priority 4 (four(5)) or
above is considered a high priority frame and is buffered accordingly.
If this buffer does not have any buffer space allocated for high priority
frames, then the buffer threshold will be none(1). Setting this object to a
different value without allocating buffer space to high priority traffic will
result in an error.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.9 |
lanBlazer7000BufferCongestionThis object indicates whether this buffer is in a congested state..ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.10 |
lanBlazer7000BufferHighOverflowDropsThe count of the number of high priority frames dropped due to the high
priority queue overflowing.ro Counter .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.11 |
lanBlazer7000BufferLowOverflowDropsThe count of the number of low priority frames dropped due to the low
priority queue overflowing.ro Counter .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.12 |
lanBlazer7000BufferHighStaleDropsThe count of the number of high priority frames dropped due to being in
the high priority queue too long (the frame aged out).ro Counter .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.13 |
lanBlazer7000BufferLowStaleDropsThe count of the number of low priority frames dropped due to being in
the low priority queue too long (the frame aged out).ro Counter .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.14 |
lanBlazer7000BufferCongestionDropsThe count of the number of frames dropped due to the destination
(output) buffer being congested.ro Counter .1.3.6.1.4.1.50.8.1.2.1.3.7.1.1.16 |
lanBlazer7000Switching OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.5 |
lanBlazer7000SwitchingLayerII OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.5.1 |
lanBlazer7000SwitchGen OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.5.1.1 |
lanBlazer7000SwitchSTPConfigWhen set to ieee8021dStp(1), the switch executes spanning tree conformant
to the IEEE 802.1D bridging standard. The switch runs one instance of
spanning tree.
When set to stpPerVlan(2), the switch executes a separate instance of spanning
tree for each virtual LAN. This configuration conforms to the model that
instances of virtual LANs within the switch are separate virtual bridging
functions. This method may not work well with bridge/routers that are also
running spanning tree.
When set to twoLayerStp(3), the switch executes a two-layer spanning tree to prevent loops. Two layer
spanning tree creates a higher 'plane' of spanning tree between VLAN devices. This method of running
spanning tree is 'plug and play' with bridge/router type devices and also scales better than the other
two methods for large environments.
When set to disable(4), spanning tree is disabled in the switch.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.1.1 |
lanBlazer7000SwitchAgingTimeThe timeout period in seconds for aging dynamically learned forwarding
information. A default of 300 seconds is recommended. An aged entry is
marked invalid, but is not removed from the Address Forwarding Table,
because it is assumed that it will be relearned to the same location within
the table.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.1.2 |
lanBlazer7000SwitchSuperAgingTimeThe timeout period in days for removing stale invalid entries from the Address
Forwarding Table. A superaged entry is removed completely from the Address
Forwarding Table, because it is assumed that the entry will never be relearned.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.1.3 |
lanBlazer7000BridgeMgmt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.5.1.2 |
lanBlazer7000BridgeTableA table of Spanning Tree information for every bridge in the system. SEQUENCE OF LanBlazer7000BridgeEntry .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1 |
lanBlazer7000BridgeEntry LanBlazer7000BridgeEntry .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1 |
lanBlazer7000BridgeIndexAn index that uniquely identifies this bridge.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.1 |
lanBlazer7000BridgeTypeIndicates whether this is a legacy dot1d bridge consisting of all switch
ports or a virtual bridge consisting of all virtual subports for a particular
Vlan.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.2 |
lanBlazer7000BridgeModeUsed to enable or disable Spanning Tree for this bridge. When set to
disable(2), all BPDUs are forwarded like regular multicast packets. The
default value is enable(1).rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.3 |
lanBlazer7000BridgeStatusThe enable/disable status of this bridge. This object incorporates the
setting of the lanBlazer7000SwitchSTPConfig object. When
lanBlazer7000SwitchSTPConfig is set such that this bridge will not be active,
lanBlazer7000BridgeStatus returns disabled(2). If lanBlazer7000SwitchSTPConfig is set
such that this bridge will be active, and lanBlazer7000BridgeMode is enable(1), this
object returns enabled(2).ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.4 |
lanBlazer7000BridgeStpPriorityThe priority value of the Bridge Identifier. See dot1dStpPriority.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.5 |
lanBlazer7000BridgeStpTimeSinceTopologyChangeThe time since the last topology change was detected. See
dot1dStpTimeSinceTopologyChange.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.6 |
lanBlazer7000BridgeStpTopChangesThe total number of topology changes. See dot1dStpTopChangesro Counter .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.7 |
lanBlazer7000BridgeStpDesignatedRootThe bridge considered to be root by this node. See
dot1dStpDesignatedRoot.ro BridgeId .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.8 |
lanBlazer7000BridgeStpRootCostThe cost of the path to the root from this node. See dot1dStpRootCost.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.9 |
lanBlazer7000BridgeStpRootPortThe port number with the lowest cost path to the root bridge. See
dot1dStpRootPort.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.10 |
lanBlazer7000BridgeStpMaxAgeThe maximum age used by this bridge to hold onto STP information
before discarding. See dot1dStpMaxAge.ro Timeout .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.11 |
lanBlazer7000BridgeStpHelloTimeThe amount of time between configuration BPDUs. See
dot1dStpHelloTime.ro Timeout .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.12 |
lanBlazer7000BridgeStpHoldTimeThe time value that indicates the interval during which no more than two
configuration BPDUs will be sent by this node. See dot1dStpHoldTime.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.13 |
lanBlazer7000BridgeStpForwardDelayThe amount of time that this node stays in each of the Listening and
Learning states. See dot1dStpForwardDelay.ro Timeout .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.14 |
lanBlazer7000BridgeStpBridgeMaxAgeThe value of MaxAge when this bridge is the root. See
dot1dStpBridgeMaxAge.rw Timeout .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.15 |
lanBlazer7000BridgeStpBridgeHelloTimeThe value of HelloTime to use when this bridge is the root. See
dot1dStpBridgeHelloTime.rw Timeout .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.16 |
lanBlazer7000BridgeStpBridgeForwardDelayThe value of FowardDelay to use when this bridge is the root. See
dot1dStpBridgeForwardDelay.rw Timeout .1.3.6.1.4.1.50.8.1.2.1.5.1.2.1.1.17 |
lanBlazer7000BridgePortMgmt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.5.1.3 |
lanBlazer7000BridgePortTableA table of Spanning Tree information for every port that supports
Spanning Tree in every bridge in the system SEQUENCE OF LanBlazer7000BridgePortEntry .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1 |
lanBlazer7000BridgePortEntry LanBlazer7000BridgePortEntry .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1.1 |
lanBlazer7000BridgePortIndexAn index that uniquely identifies this bridge port. This index corresponds
to the lanBlazer7000ResourceIndex for bridge port type resources.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1.1.1 |
lanBlazer7000BridgePortPriorityThe value of the priority field in the port ID. See dot1dStpPortPriority.
The default value is 128.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1.1.2 |
lanBlazer7000BridgePortStateThe port's current state as defined by the Spanning Tree Protocol. See
dot1dStpPortState.
The virtual port is considered broken if its switch port is blocked.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1.1.3 |
lanBlazer7000BridgePortEnableThe enabled/disabled status of this port. See dot1dStpPortEnable. The
default is enabled(2).rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1.1.4 |
lanBlazer7000BridgePortPathCostThe contribution of this port to the path cost of the paths towards the
spanning tree root. See dot1dStpPortPathCost. The default value is
dependent on the port speed, trunking mode, and duplexity.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1.1.5 |
lanBlazer7000BridgePortDesignatedRootThe bridge recorded as root for this port's segment. See
dot1dStpPortDesignatedRoot.ro BridgeId .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1.1.6 |
lanBlazer7000BridgePortDesignatedCostThe path cost of the designated root of the segment connected to this
port. See dot1dStpPortDesignatedCost.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1.1.7 |
lanBlazer7000BridgePortDesignatedBridgeThe bridge identifier of the bridge that is considered the designated bridge
for this port's segment. See dot1dStpPortDesignatedBridge.ro BridgeId .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1.1.8 |
lanBlazer7000BridgePortDesignatedPortThe port identifier of the port on the Designated Bridge for this port's
segment. See dot1dStpPortDesignatedPort.ro OCTET STRING .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1.1.9 |
lanBlazer7000BridgePortForwardTransitionsThe number of times this port has transitioned from the learning state to
the forwarding state. See dot1dStpPortForwardTransitions.ro Counter .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1.1.10 |
lanBlazer7000BridgePortFastStartThis object is being replaced by the switch port object
lanBlazer7000SwitchPortFastStart. When this bridge port object is set to
enable(1), the bridge port and all other bridge ports on the same switch port,
transition right from blocking to forwarding, skipping the listening and
learning states. When this bridge port object is set to disable(2), the bridge
port and all other bridge ports on the same switch port have this option
disabled. The user should be warned that using the fast start feature greatly
increases the likelihood of unintended network loops that would otherwise be
prevented by participating in the normal spanning tree algorithm.
The factory default value for this object is disable(2).rwdeprecated Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1.1.11 |
lanBlazer7000BridgePortSetDefaultWhen set to setDefault(2), the lanBlazer7000BridgePortPriority,
lanBlazer7000BridgePortEnable, and lanBlazer7000BridgePortPathCost
will be set to the factory default values.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1.1.12 |
lanBlazer7000BridgePortEnableChangeDetectionWhen this object is set to enable(1), a Topology Change Notification
will be generated when this port goes to Blocking or Forwarding (if
the port is a designated port). When set to disable(2), no
Topology Change Notification will be generated for this port. The
default is enable(1).rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.3.1.1.13 |
lanBlazer7000L2AddrMgmt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.5.1.4 |
lanBlazer7000L2AddrDatabaseMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.5.1.4.1 |
lanBlazer7000L2AddressTableA table of address table entries. The address table is used by the bridging
function to perform forwarding and filtering decisions. An address may
appear multiple times in different entries corresponding to the different
logical address tables. SEQUENCE OF LanBlazer7000L2AddressEntry .1.3.6.1.4.1.50.8.1.2.1.5.1.4.1.1 |
lanBlazer7000L2AddressEntryA particular address table entry. LanBlazer7000L2AddressEntry .1.3.6.1.4.1.50.8.1.2.1.5.1.4.1.1.1 |
lanBlazer7000L2AddressIndexAn index that uniquely identifies this address entry.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.4.1.1.1.1 |
lanBlazer7000L2AddressTableIndexThe address table that this entry is associated with.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.4.1.1.1.2 |
lanBlazer7000L2AddressMacAddressThe IEEE 802 MAC Address associated with this database entry.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.50.8.1.2.1.5.1.4.1.1.1.3 |
lanBlazer7000L2AddressPortBindingThe switch port that this address is associated with.rw ResourceId .1.3.6.1.4.1.50.8.1.2.1.5.1.4.1.1.1.4 |
lanBlazer7000L2AddressBindingValidThe port binding of an address entry is aged out in conformance with the
specifications laid out in the IEEE 802.1D standard. When the address is
aged out, the port binding becomes invalid.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.4.1.1.1.5 |
lanBlazer7000L2AddressVlanIDThe VLAN ID of the VLAN that this address entry corresponds to.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.4.1.1.1.6 |
lanBlazer7000L2AddressPriorityIf set to high(2), frames destined to this address are classified with priority
value 4.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.4.1.1.1.7 |
lanBlazer7000L2AddressForwardWhen set to specialDelivery(2), frames sent to this address are treated to
special delivery where the spanning tree state of the inbound port is
ignored. Typically, special delivery is only used for Bridge PDUs such as
spanning tree frames.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.4.1.1.1.8 |
lanBlazer7000L2AddressCopyIt is sometimes useful for the switch processor to eavesdrop on traffic to
certain destinations. This is especially useful in supporting the intelligent
multicasting function.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.4.1.1.1.9 |
lanBlazer7000L2AddressPersistenceThis object indicates the persistence of this entry:
other(1) - This entry is currently in use but the conditions under which it
will remain so are different from each of the following values.
invalid(2) - Writing this value to the object removes the corresponding
entry.
permanent(3) - Address is not aged out. Additionally, if the address is seen
as a source on a different port for this VLAN, the frame is filtered and the
filter event is counted. Static address entries are stored in non-volatile
memory and are restored to the address table following each system reset.
deleteOnReset(4) - Indicates that the entry is not aged out, however the
entry is not stored in non-volatile memory. Therefore, when the device is
reset, the entry will not be restored.
deleteOnTimeout(5) - Typically, address entries are learned dynamically by
the switch. These entries are aged out of the table if they are not active on
the network. This value
correlates to this state.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.4.1.1.1.10 |
lanBlazer7000L2AddressStatusThis object indicates the status of the entry:
other(1) - None of the following.
learned(2) - This entry was learned dynamically.
self(3) - The value of the corresponding instance of
lanBlazer7000AddressMacAddress represents one of the bridge's addresses.
mgmt(4) - This entry was added or modified by management. Entries
that have been added by management and made permanentro Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.4.1.1.1.11 |
lanBlazer7000L2AddrSummaryMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.5.1.4.2 |
lanBlazer7000L2AddrSummaryTableThis summary table packs the address entries in the address database into
summary objects. The goal is to optimize the upload of the large amount
of data stored therein.
Typically, a management station would use getNext requests to retrieve the
next logical summary object. The returned object value contains the next n
entries of the address database packed into one PDU. The instance of the
object returned is the index of the last address entry packed in the
summary, thereby optimizing for the next getNext request.
[ Fix this? What about gets?] SEQUENCE OF LanBlazer7000L2AddrSummaryEntry .1.3.6.1.4.1.50.8.1.2.1.5.1.4.2.1 |
lanBlazer7000L2AddrSummaryEntryA summary object that packs as many address entries possible into a
summary object. LanBlazer7000L2AddrSummaryEntry .1.3.6.1.4.1.50.8.1.2.1.5.1.4.2.1.1 |
lanBlazer7000L2AddrSummaryThe value of this object is a packed opaque structure representing an array
of address entries. The format of this structure is:
struct L2AddressEntry {
UNS32 index;
UNS8 addr[6]; // mac address
UNS8 fabricPort; //fabricPort and subPort == lanBlazer7000L2AddressPortBinding
UNS8 subPort;
UNS16 vlanID, //the global vlan id
UNS8 portBindingValidFlag;
UNS8 addressForwardFlag;
UNS8 addressCopyFlag;
UNS8 addressPersistence;
UNS8 addressStatus;
};
struct L2AddressSummary{
UNS8 numberOfEntries; // Number of entries that follow
UNS8 version; // version == 1
UNS16 endianFlag;
L2AddressEntry entryArray[numberOfEntries];
};ro OCTET STRING .1.3.6.1.4.1.50.8.1.2.1.5.1.4.2.1.1.1 |
lanBlazer7000L2AddrControlMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.5.1.4.3 |
lanBlazer7000L2AddressControlTableThis table provides the network manager the ability to create new, static
address entries. Entries added through this table are added to the specified
address table as a static entry and are save in non-volatile memory for
reconfiguration upon system restart.
This table is indexed by the lanBlazer7000AgentMgrIndex value which provides a
separate instance for each manager. SEQUENCE OF LanBlazer7000L2AddressControlEntry .1.3.6.1.4.1.50.8.1.2.1.5.1.4.3.1 |
lanBlazer7000L2AddressControlEntryA control entry enables this manager to add a new entry to the specified
address table. When the entry is written to, the control index value is reset
to 0. When the actual entry is created, the index value will read as non-zero,
reporting the actual entry created. LanBlazer7000L2AddressControlEntry .1.3.6.1.4.1.50.8.1.2.1.5.1.4.3.1.1 |
lanBlazer7000L2AddressControlIndexThe index of the address entry that was created for this address.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.4.3.1.1.1 |
lanBlazer7000L2AddressControlMacAddressThe IEEE 802 MAC Address associated with this database entry.rw MacAddress (SNMPv2-TC) .1.3.6.1.4.1.50.8.1.2.1.5.1.4.3.1.1.2 |
lanBlazer7000L2AddressControlPortBindingThe port to bind this address to.rw ResourceId .1.3.6.1.4.1.50.8.1.2.1.5.1.4.3.1.1.3 |
lanBlazer7000L2AddressControlVlanIDThe VLAN ID of the VLAN to bind this address to.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.4.3.1.1.4 |
lanBlazer7000L2AddressControlPriorityIf set to high(2), frames destined to this address are classified with priority
value 4.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.4.3.1.1.5 |
lanBlazer7000L2AddressControlPersistenceThe persistence of the entry to be created:
permanent(1) - Address is not aged out. Additionally, if the address is seen
as a source on a different port for this VLAN, the frame is filtered and the
filter event is counted. Static address entries are stored in non-volatile
memory and are restored to the address table following each system reset.
deleteOnReset(2) - Indicates that the entry is not to be aged, however the
entry is not stored in non-volatile memory. Therefore, when the device is
reset, the entry will not be restored.
deleteOnTimeout(3) - Indicates that the entry is to be aged by the normal
aging process.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.4.3.1.1.6 |
lanBlazer7000L2AddressControlStatusThe status of an entry to be created. When adding an entry all fields will
be set, and then the control status is set to createRequest(1), indicating that
the entry is to be created. During creation, the status will be
underCreation(2). If the creation is successful, then the status will be set to
success(3), and the value of lanBlazer7000AddressControlIndex indicates the index
of the entry that was created in the address table. Otherwise if the creation
was not successful, then one of the following error codes will be set and
the entry will not be created:
otherError(4) - An error other then the others defined.
entryExistsError(5) - An entry already exists with this MAC address in this
address table.
invalidMacAddress(6) - Cannot create an entry with this MAC address.
invalidTableIndex(7) - The table does not exist.
invalidPortBinding(8) - The port binding is invalid.
invalidVlanID(9) - The VLAN ID is invalid.
Note that the only value that is valid to write to this object is
createRequest(1), and that this object will never return the value
createRequest(1).rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.1.4.3.1.1.7 |
lanBlazer7000L2AddrChangeMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.5.1.4.4 |
lanBlazer7000L2AddressChangeLastThe index of the last entry written to the address change tablero INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.4.4.1 |
lanBlazer7000L2AddressChangeWrapsThe count of the number of times the address change table has wrapped.ro Counter .1.3.6.1.4.1.50.8.1.2.1.5.1.4.4.2 |
lanBlazer7000L2AddressChangeMaxEntriesThe maximum number of entries in the address change table.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.4.4.3 |
lanBlazer7000L2AddressChangeTable. SEQUENCE OF LanBlazer7000L2AddressChangeEntry .1.3.6.1.4.1.50.8.1.2.1.5.1.4.4.4 |
lanBlazer7000L2AddressChangeEntryThe address change table provides a quick way of getting only the entries
that have recently changed. Since entries age out as part of the normal
switching process, entries that have aged (i.e. their destination bindings are
no longer valid) are not considered to be changed. Any other modification
to the entry, including deletion or creation, are considered to be changes.
The address change table is considered a circular table. When an entry
changes, it is added to the next position within the table. If the 'next'
position goes beyond the end of the table, the 'next' position is set to the
beginning of the table (1) and the wrap counter
(lanBlazer7000AddressChangeWraps) is incremented. The
lanBlazer7000AddressChangeLast value is updated with the index of the last
entered entry.
An entry may be in the table multiple times if it has changed multiple times.
Every time that an entry changes, it is added to the change table.
A network management application should follow the following algorithm
when polling this table:
1. Set lastChangeWrap = lanBlazer7000AddressChangeWraps.
2. Set lastChangeIndex = lanBlazer7000AddressChangeLast
3. Get the entire lanBlazer7000AddressEntryTable.
4. Submit a getNext for <lastChangeWrap>.<lastChangeIndex>,
updating lastChangeWrap and lastChangeIndex with the returned next
values. Update the address entry database with the changed values.
5. Repeat step 4 until no more entries are returned.
6. Wait polling timeout period.
7. Get wrap events counter and last index. If the wrap events counter is
equal to lastChangeWrap, then goto step 4. Else if the wrap events
counter is more then one greater then lastChangeWrap, goto step 1.
Else the wrap events counter is exactly one greater then
lastChangeWrap, and if the last index is greater then lastChangeIndex,
then goto step 1, else goto step 4.
The last step simply insures that we have not missed any of the change
entries. Essentially it says that if we have wrapped to beyond where we last
polled, then we must get the entire table to synch up again. Otherwise we
can just get the entries that have changed. LanBlazer7000L2AddressChangeEntry .1.3.6.1.4.1.50.8.1.2.1.5.1.4.4.4.1 |
lanBlazer7000L2AddressChangeWrapCountThe number of times that the lanBlazer7000AddressChangeLastIndex had
wrapped when this entry was added.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.4.4.4.1.1 |
lanBlazer7000L2AddressChangeIndexThe index that uniquely identifies this address change entry.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.4.4.4.1.2 |
lanBlazer7000L2AddressChangeIndexChangedThe address entry that changed. The value of this object corresponds to
the lanBlazer7000L2AddressIndex object.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.1.4.4.4.1.3 |
lanBlazer7000L2AddressChangeSummaryThe structure is interpreted in the following manner:ro OCTET STRING .1.3.6.1.4.1.50.8.1.2.1.5.1.4.4.4.1.4 |
lanBlazer7000SwitchPortMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.5.2 |
lanBlazer7000SwitchPortTable SEQUENCE OF LanBlazer7000SwitchPortEntry .1.3.6.1.4.1.50.8.1.2.1.5.2.1 |
lanBlazer7000SwitchPortEntry LanBlazer7000SwitchPortEntry .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1 |
lanBlazer7000SwitchPortIndexA unique index that identifies this switch port. The value of
this index corresponds to the value of the lanBlazer7000ResourceIndex for
switch ports.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.1 |
lanBlazer7000SwitchPortSTAPModeDisabling spanning tree on a switch port prevents the switch
port from participating in the spanning tree process. When
disabled(2), this port will neither generate BPDUs, nor process
received BPDUs. Also, the port will always start in the
forwarding state. A port configured in this mode will not be
able to detect network loops involving this port.
The factory default is to enable spanning tree on all ports.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.2 |
lanBlazer7000SwitchPortConvertToStaticWhen this object is set to convertToStatic(2), all addresses
learned on this port will be added to the non-volatile version
of the static address table.
Typically, this object will be used to perform a crude form of
address database update where the address activity associated
with this port is collected as static (i.e. permanent) addresses
while the value of this object is set to convertToStatic(2).
Following this usually short period of time (perhaps a week of
activity), the value of this object is restored back to its
default value of learnAsDynamic(1) and learning for this port is
disabled.
It is important that the user verify the address database to
verify that only the desired addresses were made permanent.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.3 |
lanBlazer7000SwitchPortLearningModeDisable learning on a bridge port to prevent new addresses from
being added to the address database. Used in combination with
static (permanent) address entries, disabling address learning
is an effective security feature to prevent new hosts from
appearing on the network, or to prevent hosts from moving to
different locations in the network. The default is enable.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.4 |
lanBlazer7000SwitchPortHuntGroupHunt groups provide the capability to logically bind multiple
switch ports into one switch port. This provides a way of
balancing the load of multiple links between like-configured
switches.
Care must be taken to configure the hunt groups properly to
prevent accidental network looping.
Use this object to bind this port to a specific hunt group.
When not configured to a specific hunt group, set the value of
this object to zero.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.5 |
lanBlazer7000SwitchPortPhysicalPortThe physical port resource bound to this switch port.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.6 |
lanBlazer7000SwitchPortKnownModeEnabling known mode for this switch port causes the port to
safely discard frames flooded because they are unknown unicast
frames. This mode greatly enhances the efficiency of the port's
output buffer since space is not wasted for frames not meant for
this port.
Enabling this feature disables learning for this port.
Addresses associated for this port should be entered statically.
The default is disable.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.7 |
lanBlazer7000SwitchPortMappingMethodThe frame mapping method of this switch port. When set to
port-based(1) (the factory default), all non-tagged frames are
classified to the VLAN associated with this switch port.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.8 |
lanBlazer7000SwitchPortTrunkingModeThe trunking mode of this port. All frames transmitted out
this switch port are translated to the appropriate trunking
format:
Clear: Ethernet or IEEE 802.3 frame format.
This is the default.
IEEE 802.1Q: The original frame with a new Ethernet Type
(Protocol = 0xXXXX) and the VLAN ID inserted
following the original Source Address.
Also, the CRC is recalculated.
Multi-level: The original frame is encapsulated in an
IEEE 802.3 legal frame proprietary to a
major networking equipment vendor.
3Com LinkSwitch: The original frame has the VLAN ID added to
the front of the frame (before the
Destination Address). Trunking format is
proprietary to 3Com Corporation.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.9 |
lanBlazer7000SwitchPortVlanBindingMethodThe VLAN binding method of a switch port specifies the way in
which the port can be a member of the egress lists of VLANs
other than the port default VLAN specified by
lanBlazer7000SwitchPortVlanID:
static: A Virtual Switch Port must be statically created for
each VLAN/port combination.
persistent: A Virtual Switch Port is automatically created for
each VLAN known to the switch (i.e., the port is
a member of the egress lists of all VLANs).
dynamic: A Virtual Switch Port is automatically created for
each VLAN when the associated VLAN ID is used as a
tag in an IEEE 802.1Q or Multi-level tagged frame
received on the port (i.e., the port is a member of
the egress lists of the VLANs from frames received
on the port).
The default is static.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.10 |
lanBlazer7000SwitchPortIgnoreTagEach switch port is capable of ignoring the VLAN Tag associated
with a frame in a trunking format. When ignored, the tag is
used as the default in the event that a VLAN classification
based on the switch's policy(s) cannot be made.
This feature is useful for connecting layer 2 VLANs and layer 3
VLANs. The default is useTag.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.11 |
lanBlazer7000SwitchPortVlanIDWhen this switch port is configured in port-based VLAN mode,
all non-tagged frames received on this port are bound to this
VLAN. Otherwise, non-tagged frames are classified to this VLAN
as the default if a VLAN binding cannot be otherwise determined.
The factory default is 1, which is the VLAN ID of the Default
VLAN.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.12 |
lanBlazer7000SwitchPort3ComMappingTableIndexThe 3Com VLAN mapping table associated with this switch port.
The default is 1, which indicates the default mapping table.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.13 |
lanBlazer7000SwitchPortAutoVlanCreationEnabling auto VLAN creation for this switch port causes the
port to dynamically create a VLAN whenever an IEEE 802.1Q or
Multi-level tagged frame is received on the port with a tag value
which does not correspond to a known VLAN. All switch ports with
a trunking mode of IEEE 802.1Q or Multi-level are bound to this
created VLAN. The default is disable.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.14 |
lanBlazer7000SwitchPortMirrorModeWhen set to enable(1), this object indicates that the port is
defined as a mirror port through the
lanBlazer7000PortMirroringTable. A mirror port duplicates frames
received at one or more source ports.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.15 |
lanBlazer7000SwitchPortIfIndexEach switch port is associated with an interface. This object
provides a mechanism to map switch ports to bridge ports.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.16 |
lanBlazer7000SwitchPortFastStartWhen this object is set to enable(1), bridge ports on this switch port
transitions right from blocking to forwarding, skipping the listening
and learning states. The user should be warned that using the fast start
feature greatly increases the likelihood of unintended network loops that
would otherwise be prevented by participating in the normal spanning tree
algorithm.
The factory default value for this object is disable(2).rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.17 |
lanBlazer7000SwitchPortVlanExchangeWhen this object is set to enable(1), this switch port attempts to
learn VLANs from a major networking equipment vendor if the switch port's
trunking mode is IEEE 802.1Q Format or Multi-level Format.
The factory default value for this object is enable(1).rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.2.1.1.18 |
lanBlazer7000HuntGroupMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.5.4 |
lanBlazer7000HuntGroupTable SEQUENCE OF LanBlazer7000HuntGroupEntry .1.3.6.1.4.1.50.8.1.2.1.5.4.1 |
lanBlazer7000HuntGroupEntry LanBlazer7000HuntGroupEntry .1.3.6.1.4.1.50.8.1.2.1.5.4.1.1 |
lanBlazer7000HuntGroupIndexAn index that uniquely identifies this hunt group. This index corresponds
to the value of lanBlazer7000ResourceIndex for resources of the hunt group type.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.4.1.1.1 |
lanBlazer7000HuntGroupNamerw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.50.8.1.2.1.5.4.1.1.2 |
lanBlazer7000HuntGroupBasePortThe switch port index that serves as the base port for this hunt group.
Each hunt group requires a base port. In lieu of a specific configuration,
the hunt group will inherit the first switch port bound to the hunt group as
its base port.
The base port serves as the management focus for the hunt group. That is,
a hunt group is managed as one switch port whose instance is provided by
the base switch port. All configuration (e.g. spanning tree information) and
statistics related to switch ports are meaningful only through the instance of
the base port.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.5.4.1.1.3 |
lanBlazer7000HuntGroupNumberOfPortsThe current number of ports that belong to this hunt group.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.4.1.1.4 |
lanBlazer7000HuntGroupLoadSharingrw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.4.1.1.5 |
lanBlazer7000HuntGroupStatusrw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.4.1.1.6 |
lanBlazer7000PortMirroringMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.5.5 |
lanBlazer7000PortMirroringTableA table of port mirroring entries used to mirror traffic from
a source port to a mirror port. SEQUENCE OF LanBlazer7000PortMirroringEntry .1.3.6.1.4.1.50.8.1.2.1.5.5.1 |
lanBlazer7000PortMirroringEntryObjects related to the PortMirroring functionality. LanBlazer7000PortMirroringEntry .1.3.6.1.4.1.50.8.1.2.1.5.5.1.1 |
lanBlazer7000PortMirroringIndexThe unique index that identifies this entry. This index consists
of a switch fabric port and the index of a Packet Lookup Engine
servicing this fabric port.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.5.5.1.1.1 |
lanBlazer7000PortMirroringSourceSubPortThe frame sampler source switch subport. The source port is the
port from which received traffic will be mirrored. This object
identifies the switch subport only, the switch fabric port is
identified in lanBlazer7000PortMirroringIndex. If set to 0, all subports
associated with the lanBlazer7000PortMirroringIndex will be source ports. The
default value is 0.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.5.1.1.2 |
lanBlazer7000PortMirroringSamplerTypeThe type for this frame sampler. When set to enable(1), every
frame received on the source port(s) will be mirrored at the mirror
port. When set to disable(2), no frames received on the source
port(s) will be mirrored at the mirror port. When set to
periodic(3), frames will be mirrored at the rate defined in
lanBlazer7000PortMirroringRate. The default value is disable(2).rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.5.5.1.1.3 |
lanBlazer7000PortMirroringRateUsed in conjunction with lanBlazer7000PortMirroringSamplerType to implement
periodic sampling functionality. If lanBlazer7000PortMirroringSamplerType is
set to periodic(3), this object defines the number of packets/second
that will be mirrored. If lanBlazer7000PortMirroringSamplerType is not
periodic(3), this object will set to 0.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.5.5.1.1.4 |
lanBlazer7000PortMirroringMirrorPortThe Switch Port on which frames received at source ports(s) will be
duplicated. If no mirror port has been defined this object will
return NULL.rw ResourceId .1.3.6.1.4.1.50.8.1.2.1.5.5.1.1.5 |
lanBlazer7000VlanMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.7 |
lanBlazer7000Vlans OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.7.1 |
lanBlazer7000VlanTable SEQUENCE OF LanBlazer7000VlanEntry .1.3.6.1.4.1.50.8.1.2.1.7.1.1 |
lanBlazer7000VlanEntry LanBlazer7000VlanEntry .1.3.6.1.4.1.50.8.1.2.1.7.1.1.1 |
lanBlazer7000VlanIDAn identifier that is unique within the administrative domain.
This ID is assigned by the management application and is
meaningful within that context.
This ID is used to identify VLANs when tagged using either the
IEEE 802.1 frame format or the Multi-level frame format.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.7.1.1.1.1 |
lanBlazer7000VlanNameA user-assignable name for this Vlan.rw DisplayString .1.3.6.1.4.1.50.8.1.2.1.7.1.1.1.2 |
lanBlazer7000VlanIfIndexEach virtual LAN has a virtual interface associated with it.
This enables RMON monitoring to occur per-VLAN. It also
provides a handy mechanism to map virtual LANs to bridge ports
by mapping them with the ifStack table from the Interface MIB.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.7.1.1.1.3 |
lanBlazer7000VlanAFTIndexThe address table used for this VLAN for explicitly tagged
frames (frames received in a trunking frame format or from a
port in port-based VLAN mode.) Normally, each VLAN maps to a
unique address table. This is useful for environments with
duplicate host addresses appear on different VLANs on different
ports.
For those environments where duplicate hosts on different VLANs
don't exist, or exist but are on the same port, and where the
address table size and/or aging is a concern, then multiple
VLANs may be mapped to the same address table.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.7.1.1.1.4 |
lanBlazer7000VlanBridgeIndexThe bridge resource which is bound to this Vlan.rw ResourceId .1.3.6.1.4.1.50.8.1.2.1.7.1.1.1.5 |
lanBlazer7000VlanStatusThe status of an entry to be created or deleted.
When adding an entry all fields will be set, and then the status
is set to createRequest(1) (indicating that the entry is to be
created). When deleting an entry the status is set to
destroyRequest(3) (indicating that the entry is to be destroyed).
During creation the status will be underCreation(2). If the
creation is successful, then the status will be set to
active(5). Otherwise if the creation was not successful then
one of the following error codes will be set and the entry will
not be created:
otherError(6) - An error other than the others defined.
entryExistsError(7) - An entry already exists.
invalidVlanID(8) - the VLAN ID is invalid.
invalidVlanName(9) - the VLAN name is invalid.
invalidVlanAFTIndex(10) - the VLAN AFT index is invalid.
invalidVlanBridgeIndex(11) - the VLAN bridge index is invalid.
invalidVlanInitialHashTableSize(12) - the VLAN initial hash
table size is invalid.
invalidVlanAutoIncrementHTSize(13) - the VLAN auto increment
hash table size is
invalid.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.7.1.1.1.6 |
lanBlazer7000VlanInitialHashTableSizeThe initial hash table size used for MAC addresses on this
VLAN. This attribute may only be set when lanBlazer7000VlanStatus is
set to createRequest(1). It must be a power of 2 between 16
and 8192, inclusive.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.7.1.1.1.7 |
lanBlazer7000VlanAutoIncrementHTSizeThis attribute specifies whether or not the hash table size
used for MAC addresses on this VLAN is automatically increased
as necessary to hold more MAC addresses. This attribute may only
be set when lanBlazer7000VlanStatus is set to createRequest(1).rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.7.1.1.1.8 |
lanBlazer7000VlanLearnStatusThis attribute indicates if the VLAN was learned. If learned
it indicates if the VLAN was learned either by VLAN Exchange or
Auto VLAN creation.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.7.1.1.1.9 |
lanBlazer7000VlanMappings OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.7.3 |
lanBlazer70003ComMapping OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.7.3.1 |
lanBlazer70003ComMappingTable SEQUENCE OF LanBlazer70003ComMappingEntry .1.3.6.1.4.1.50.8.1.2.1.7.3.1.1 |
lanBlazer70003ComMappingEntry LanBlazer70003ComMappingEntry .1.3.6.1.4.1.50.8.1.2.1.7.3.1.1.1 |
lanBlazer70003ComMappingTableIndexro INTEGER .1.3.6.1.4.1.50.8.1.2.1.7.3.1.1.1.1 |
lanBlazer70003ComMappingTableNameA user-readable name associated with this table.rw DisplayString .1.3.6.1.4.1.50.8.1.2.1.7.3.1.1.1.2 |
lanBlazer70003ComMappingTableStatusThe status of an entry to be created. When adding an entry all
fields will be set, and then the status is set to
createRequest(1), indicating that the entry is to be created.
If the creation is successful, then the status will be set to
active(3). Otherwise if the creation was not successful then
one of the following error codes will be set and the entry will
not be created:
entryExistsError(4) - An entry already exists.
otherError(5) - An error other than the others defined.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.7.3.1.1.1.3 |
lanBlazer7000Vlan3ComMapping OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.7.3.2 |
lanBlazer7000Vlan3ComMappingTable SEQUENCE OF LanBlazer7000Vlan3ComMappingEntry .1.3.6.1.4.1.50.8.1.2.1.7.3.2.1 |
lanBlazer7000Vlan3ComMappingEntry LanBlazer7000Vlan3ComMappingEntry .1.3.6.1.4.1.50.8.1.2.1.7.3.2.1.1 |
lanBlazer7000Vlan3ComMappingIndexThe external tag of this 3Com VLAN.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.7.3.2.1.1.1 |
lanBlazer7000Vlan3ComMappingVlanIDThe VLAN ID of the VLAN that this 3Com tag is associated with.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.7.3.2.1.1.2 |
lanBlazer7000Vlan3ComMappingStatusThe status of an entry to be created. When adding an entry all
fields will be set, and then the status is set to
createRequest(1), indicating that the entry is to be created.
If the creation is successful, then the status will be set to
active(3). Otherwise if the creation was not successful then
one of the following error codes will be set and the entry will
not be created:
otherError(4) - An error other than the others defined.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.7.3.2.1.1.3 |
lanBlazer7000VirtualPorts OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.7.4 |
lanBlazer7000VirtualSwitchPortTable SEQUENCE OF LanBlazer7000VirtualSwitchPortEntry .1.3.6.1.4.1.50.8.1.2.1.7.4.1 |
lanBlazer7000VirtualSwitchPortEntryAn instance of a virtual switch port indicates that this
switch port is a member of this VLAN. LanBlazer7000VirtualSwitchPortEntry .1.3.6.1.4.1.50.8.1.2.1.7.4.1.1 |
lanBlazer7000VirtualSwitchPortIndexThe Resource ID of the virtual switch port bound to the VLAN.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.7.4.1.1.1 |
lanBlazer7000VirtualSwitchPortFormatTypically, a VLAN capable switch port has one of three modes:
access, trunk, or hybrid. In access mode, the port sends
frames in clear format (untagged). In trunk mode, all outbound
frames are translated into the switch port's configured
trunking format.
In hybrid mode, it is possible for a port to send trunked
frames for some VLANs and clear frames for others. In this
case, the switch port is configured to trunk, and the virtual
switch port(s) for those VLANs that require clear formatted
frames are configured to be override the switch port setting.
This is done by setting this object to clear(1).
By default, the value of this object is trunkingFormat(2)
which means to use the trunking format configured for this
switch port. (which may be clear).rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.7.4.1.1.2 |
lanBlazer7000VirtualSwitchPortBridgePortThe bridge port resource bound to this virtual port.rw ResourceId .1.3.6.1.4.1.50.8.1.2.1.7.4.1.1.3 |
lanBlazer7000VirtualSwitchPortBindingTypeThe method by which this switch port was bound to the VLAN.
If the value is static(1), the binding was manually created
by the administrator. If the value is persistent(2), the
binding was created by the switch because the VLAN is the
port-based VLAN for the switch port, or the switch port
VLAN Binding Method is persistent. These bindings may not
be removed. If the value is dynamic(3), the binding was
created by the switch as a result of receiving a tagged
frame on the switch port with a VLAN ID corresponding to
the VLAN.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.7.4.1.1.4 |
lanBlazer7000VirtualSwitchPortStatusThe status of an entry to be created or deleted.
When adding an entry all fields will be set, and then the status
is set to createRequest(1) (indicating that the entry is to be
created). When deleting an entry the status is set to
destroyRequest(2) (indicating that the entry is to be destroyed).
If the creation is successful, then the status will be set to
active(3). Otherwise if the creation was not successful then
one of the following error codes will be set and the entry will
not be created:
otherError(4) - An error other than the others defined.
entryExistsError(5) - On creation, an entry already exists.
On deletion, the entry may not be
removed.
entryNoExistError(6) - The VLAN specified by ID
does not exist.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.7.4.1.1.5 |
lanBlazer7000Events OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.10 |
lanBlazer7000EventMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.10.1 |
lanBlazer7000EventTableTable of events currently supported. SEQUENCE OF LanBlazer7000EventEntry .1.3.6.1.4.1.50.8.1.2.1.10.1.1 |
lanBlazer7000EventEntryAttributes associated with the event. LanBlazer7000EventEntry .1.3.6.1.4.1.50.8.1.2.1.10.1.1.1 |
lanBlazer7000EventIndexro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.1.1.1.1 |
lanBlazer7000EventModeDisabling an event prevents this event from taking any actions when
triggered.
When set to enable to the console, the event will print the event information
to the console serial port. The user can select whether to view log
messages, trap messages or any event at the console.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.10.1.1.1.2 |
lanBlazer7000EventLogActionWhen enabled, this action will cause an event log entry to be created.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.10.1.1.1.3 |
lanBlazer7000EventTrapActionWhen enabled, this event will cause an SNMP trap to be generated.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.10.1.1.1.4 |
lanBlazer7000EventConsoleActionWhen enabled, this event will cause a message to printed to the console serial port.rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.10.1.1.1.5 |
lanBlazer7000EventLogMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.10.2 |
lanBlazer7000LogTableMaxSizeThe maximum number of entries in the log table.
Changing this value causes the existing log to be
truncated and rebuilt.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.2.1 |
lanBlazer7000LogLastEntryThe log index of the last entry entered in the log.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.2.2 |
lanBlazer7000LogWrapsThe number of times that the last entry has wrapped from 65K back to 1.ro Counter .1.3.6.1.4.1.50.8.1.2.1.10.2.3 |
lanBlazer7000EventLog OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.10.3 |
lanBlazer7000EventLogTableThe log table for the events in the event table that are enabled for the
Log Action. SEQUENCE OF LanBlazer7000EventLogEntry .1.3.6.1.4.1.50.8.1.2.1.10.3.1 |
lanBlazer7000EventLogEntryAn entry in the log indicates information associated with a particular
event. LanBlazer7000EventLogEntry .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1 |
lanBlazer7000EventLogEventIndexThe index that uniquely identifies the event that caused this log entry.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1.1 |
lanBlazer7000EventLogIndexAn index that uniquely identifies this log entry.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1.2 |
lanBlazer7000EventLogTimeThe value of sysUpTime when this event was triggered.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1.3 |
lanBlazer7000EventLogDescrThe event log description.ro DisplayString .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1.4 |
lanBlazer7000EventLogTypeThe type of event that caused this log entry.ro EventCategory .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1.5 |
lanBlazer7000EventLogSeverityThe severity associated with this event. It is recommended that the
severity be interpreted in the following manner:
0-19: Normal
20-39: Informational
40-59: Warning
60-79: Alarm
80-99: Severe Error
100: Failure.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1.6 |
lanBlazer7000EventLogDTMThe date and time when this log entry was made. The format is yy-Mon-
dd hh:mm:ss, time is in 24 hour time.ro DisplayString .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1.7 |
lanBlazer7000EventLogResTypeThe type of object (if provided) that triggered this event. If not provided,
the value is equal to 'Invalid Resource'.ro ResourceType .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1.8 |
lanBlazer7000EventLogResIDThe instance of this resource (if provided - see lanBlazer7000EventLogResType)
that triggered this event.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1.9 |
lanBlazer7000EventLogResLeafA number corresponding to the attribute associated with this resource and
this event entry. It corresponds exactly to the leaf MIB number of the MIB
that manages this resource. For example, if a port's mode changed, the
configuration event log entry would indicate the value of 5 which is the
leaf index of the lanBlazer7000PortMode within the lanBlazer7000PortTable MIB table.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1.10 |
lanBlazer7000EventLogValueTypeThe data type associated with the log event value. This object indicates
how to interpret the data stored in the event log value:
- none(1) indicates no value returned.
- integer32(2) - a 4 byte unsigned integer.
- integer64(3) - an 8 byte unsigned integer.
- displayString(4) - a null terminated (or up to 8 characters) string.
- ipv4NetworkAddress(5) - a 4 byte IP version 4 network address.
- ieee802MACAddress(6) - a 6 byte MAC Address.
- timeticks(7) - sysUpTime type value (4 bytes)ro EventValueType .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1.11 |
lanBlazer7000EventLogValueThe value associated with the event encoded in an octet string. Refer to
lanBlazer7000EventLogValueType for how to interpret this value.
The value encoded in this string is in Big Endian order.ro OCTET STRING .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1.12 |
lanBlazer7000EventLogEpochTimeThe number of time ticks since the epoch when this
event was logged. The interpretation of this value is
as follows:
struct DateTimeOvly {
UNS32 year:6;
UNS32 month:4;
UNS32 day:5;
UNS32 hour:5;
UNS32 minute:6;
UNS32 second:6;
};
The epoch is January 1, 1997, at 00:00:00. A value of
0 refers to this date and time.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1.13 |
lanBlazer7000EventLogIDA unique index that identifies the occurence of this
event. This ID can be correlated between traps, logs
and the like.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.3.1.1.14 |
lanBlazer7000ShutdownLogMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.10.4 |
lanBlazer7000ShutdownLogTableMaxSizeThe maximum number of entries in the non-volatile log table. Changing
the value of this object changes the maximum number of entries to be
stored in Shutdown.rw INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.4.1 |
lanBlazer7000ShutdownLogLastEntryThe ID of the last entry made to the shutdown log.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.4.2 |
lanBlazer7000ShutdownLogAcknowledgedThis object is to set to acknowledged(2) the first time the Shutdown Log
Table is accessed indicating that the Shutdown log has been read (at least
once) since the system restarted.ro Enumeration .1.3.6.1.4.1.50.8.1.2.1.10.4.3 |
lanBlazer7000EventShutdownLog OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.10.5 |
lanBlazer7000EventShutdownLogTableA table of the last events logged before the system restarted. SEQUENCE OF LanBlazer7000EventShutdownLogEntry .1.3.6.1.4.1.50.8.1.2.1.10.5.1 |
lanBlazer7000EventShutdownLogEntryA log entry stored in non-volatile memory. LanBlazer7000EventShutdownLogEntry .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1 |
lanBlazer7000EventShutdownLogEventIndexThe index that uniquely identifies the event that caused this ShutdownLog
entry.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1.1 |
lanBlazer7000EventShutdownLogIndexAn index that uniquely identifies this ShutdownLog entry.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1.2 |
lanBlazer7000EventShutdownLogTimeThe value of sysUpTime when this event was triggered. Note,
the value corresponds to the sysUpTime when the system was last
running (i.e. before it was shutdown.)ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1.3 |
lanBlazer7000EventShutdownLogDescrThe event ShutdownLog description.ro DisplayString .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1.4 |
lanBlazer7000EventShutdownLogTypeThe type of event that caused this ShutdownLog entry.ro EventCategory .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1.5 |
lanBlazer7000EventShutdownLogSeverityThe severity associated with this event. It is recommended that the
severity be interpreted in the following manner:
0-19: Normal
20-39: Informational
40-59: Warning
60-79: Alarm
80-99: Severe Error
100: Failure.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1.6 |
lanBlazer7000EventShutdownLogDTMThe date and time when this ShutdownLog entry was made. The format
is yy-Mon-dd hh:mm:ss, time is in 24 hour time.ro DisplayString .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1.7 |
lanBlazer7000EventShutdownLogResTypeThe type of object (if provided) that triggered this event. If not provided,
the value is invalid.ro ResourceType .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1.8 |
lanBlazer7000EventShutdownLogResIDThe instance of this resource (if provided) that triggered this event.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1.9 |
lanBlazer7000EventShutdownLogResLeafTo be provided.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1.10 |
lanBlazer7000EventShutdownLogValueTypeThe data type associated with the ShutdownLog event value. This object
indicates how to interpret the data stored in the event ShutdownLog
value.ro EventValueType .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1.11 |
lanBlazer7000EventShutdownLogValueThe value associated with the event encoded in an octet string.ro OCTET STRING .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1.12 |
lanBlazer7000EventShutdownLogEpochTimeThe number of time ticks since the epoch when this
event was logged. The interpretation of this value is
as follows:
struct DateTimeOvly {
UNS32 year:6;
UNS32 month:4;
UNS32 day:5;
UNS32 hour:5;
UNS32 minute:6;
UNS32 second:6;
};
The epoch is January 1, 1997, at 00:00:00. A value of
0 refers to this date and time.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1.13 |
lanBlazer7000EventShutdownLogIDA unique index that identifies the occurence of this
event. This ID can be correlated between traps, logs
and the like.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.5.1.1.14 |
lanBlazer7000EventTrapMgmt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.10.6 |
lanBlazer7000EventTrapEventIndexThe index that uniquely identifies the event that caused this trap.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.6.1 |
lanBlazer7000EventTrapTimeThe value of sysUpTime when this event was triggered.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.50.8.1.2.1.10.6.2 |
lanBlazer7000EventTrapDescrThe event log description.ro DisplayString .1.3.6.1.4.1.50.8.1.2.1.10.6.3 |
lanBlazer7000EventTrapTypeThe type of event that caused this trap.ro EventCategory .1.3.6.1.4.1.50.8.1.2.1.10.6.4 |
lanBlazer7000EventTrapSeverityThe severity associated with this event. It is recommended that the
severity be interpreted in the following manner:
0-19: Normal
20-39: Informational
40-59: Warning
60-79: Alarm
80-99: Severe Error
100: Failure.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.6.5 |
lanBlazer7000EventTrapDTMThe date and time when this trap was sent. The format is yy-Mon-
dd hh:mm:ss, time is in 24 hour time.ro DisplayString .1.3.6.1.4.1.50.8.1.2.1.10.6.6 |
lanBlazer7000EventTrapResTypeThe type of object (if provided) that triggered this event. If not provided,
the value is equal to 'Invalid Resource'.ro ResourceType .1.3.6.1.4.1.50.8.1.2.1.10.6.7 |
lanBlazer7000EventTrapResIDThe instance of this resource (if provided - see lanBlazer7000EventTrapResType)
that triggered this event.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.10.6.8 |
lanBlazer7000EventTrapResLeafA number corresponding to the attribute associated with this resource and
this event entry. It corresponds exactly to the leaf MIB number of the MIB
that manages this resource. For example, if a port's mode changed, the
configuration event log entry would indicate the value of 5 which is the
leaf index of the lanBlazer7000PortMode within the lanBlazer7000PortTable MIB table.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.6.9 |
lanBlazer7000EventTrapValueTypeThe data type associated with the trap event value. This object indicates
how to interpret the data stored in the event trap value:
- none(1) indicates no value returned.
- integer32(2) - a 4 byte unsigned integer.
- integer64(3) - an 8 byte unsigned integer.
- displayString(4) - a null terminated (or up to 8 characters) string.
- ipv4NetworkAddress(5) - a 4 byte IP version 4 network address.
- ieee802MACAddress(6) - a 6 byte MAC Address.
- timeticks(7) - sysUpTime type value (4 bytes)ro EventValueType .1.3.6.1.4.1.50.8.1.2.1.10.6.10 |
lanBlazer7000EventTrapValueThe value associated with the event encoded in an octet string. Refer to
lanBlazer7000EventTrapValueType for how to interpret this value.
The value encoded in this string is in Big Endian order.ro OCTET STRING .1.3.6.1.4.1.50.8.1.2.1.10.6.11 |
lanBlazer7000EventTrapEpochTimeThe number of time ticks since the epoch when this
event was logged. The interpretation of this value is
as follows:
struct DateTimeOvly {
UNS32 year:6;
UNS32 month:4;
UNS32 day:5;
UNS32 hour:5;
UNS32 minute:6;
UNS32 second:6;
};
The epoch is January 1, 1997, at 00:00:00. A value of
0 refers to this date and time.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.6.12 |
lanBlazer7000EventTrapIDA unique index that identifies the occurence of this
event. This ID can be correlated between traps, logs
and the like.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.10.6.13 |
lanBlazer7000AlarmMgt OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.11 |
lanBlazer7000AlarmGeneral OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.11.1 |
lanBlazer7000AlarmGeneralActiveEntriesThe total number of alarm entries in the triggered state currently in the
alarm table.ro Gauge .1.3.6.1.4.1.50.8.1.2.1.11.1.1 |
lanBlazer7000AlarmGeneralTimeStampThe value of sysUpTime when any alarm state last changed (either
triggering a new alarm or re-arming an old one).ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.50.8.1.2.1.11.1.2 |
lanBlazer7000Alarms OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.11.2 |
lanBlazer7000ActiveAlarmTableA table of all alarms in the triggered state. SEQUENCE OF LanBlazer7000ActiveAlarmEntry .1.3.6.1.4.1.50.8.1.2.1.11.2.2 |
lanBlazer7000ActiveAlarmEntryAn alarm in the triggered state. LanBlazer7000ActiveAlarmEntry .1.3.6.1.4.1.50.8.1.2.1.11.2.2.1 |
lanBlazer7000ActiveAlarmIndexThe unique index that identifies this alarm.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.11.2.2.1.1 |
lanBlazer7000ActiveAlarmNameThe name of this alarm.ro DisplayString .1.3.6.1.4.1.50.8.1.2.1.11.2.2.1.2 |
lanBlazer7000ActiveAlarmValueHighThe high order 32 bits of the value that triggered this alarm.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.11.2.2.1.3 |
lanBlazer7000ActiveAlarmValueLowThe low order 32 bits of the value that triggered this alarm.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.11.2.2.1.4 |
lanBlazer7000ActiveAlarmVariableThe OID of the alarm variable if this is a user-created alarm (null
otherwise).ro OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.11.2.2.1.5 |
lanBlazer7000ActiveAlarmResTypeThe resource type of this alarm if this is an internally created alarm.ro ResourceType .1.3.6.1.4.1.50.8.1.2.1.11.2.2.1.6 |
lanBlazer7000ActiveAlarmResIDThe resource identifier associated with this alarm if this is an internally created alarm.ro ResourceId .1.3.6.1.4.1.50.8.1.2.1.11.2.2.1.7 |
lanBlazer7000ActiveAlarmLeafThe leaf index of the MIB table used to manage this resource that is associated with this
alarm, if this is an internally created alarm. For example, if this alarm was created to
monitor a port's status, then the value of this object will be 6, corresponding to the leaf
index of the lanBlazer7000PortStatus object.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.11.2.2.1.8 |
lanBlazer7000ActiveAlarmOwnerThis is the owner of the alarm.ro DisplayString .1.3.6.1.4.1.50.8.1.2.1.11.2.2.1.9 |
lanBlazer7000SnmpTraps OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.13 |
lanBlazer7000SystemTrapA lanBlazer7000SystemTrap is sent by the agent when a system
event is triggered. These events are usually triggered
when the software encounters an unexpected situation,
e.g. a hardware failure or a software bug. TRAP-TYPE .1.3.6.1.4.1.50.8.1.2.1.13.0.2 |
lanBlazer7000ConfigurationTrapA lanBlazer7000ConfigurationTrap is sent by the agent when the
configuration event is triggered. These events are
triggered when a configuration change is made. TRAP-TYPE .1.3.6.1.4.1.50.8.1.2.1.13.0.3 |
lanBlazer7000TemperatureTrapA lanBlazer7000TemperatureTrap is sent by the agent when the
temperature event is triggered. This event is
triggered when a temperature probe detects the
temperature crossing a threshold. TRAP-TYPE .1.3.6.1.4.1.50.8.1.2.1.13.0.4 |
lanBlazer7000ResourceTrapA lanBlazer7000ResourceTrap is sent by the agent when the
resource event is triggered. The resource event is
triggered when a resource is added or removed from the
system. TRAP-TYPE .1.3.6.1.4.1.50.8.1.2.1.13.0.5 |
lanBlazer7000FanTrapA lanBlazer7000FanTrap is sent by the agent when the
fan status event is triggered. The fan status event
is triggered when a fan has a change in its status. TRAP-TYPE .1.3.6.1.4.1.50.8.1.2.1.13.0.6 |
lanBlazer7000PowerTrapA lanBlazer7000PowerTrap is sent by the agent when the power
event is triggered. These events are triggered when a
power supply changes status. TRAP-TYPE .1.3.6.1.4.1.50.8.1.2.1.13.0.9 |
lanBlazer7000VlanExchange OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.14 |
lanBlazer7000VlanExchangeSwitch OBJECT IDENTIFIER .1.3.6.1.4.1.50.8.1.2.1.14.1 |
lanBlazer7000VlanExchangeStateWhen this object is set to enable(1), the switch attempts to
learn VLANs from a major networking equipment vendor on switch
ports that have their VLAN Exchange parameter set to enable(1).
trunking mode is IEEE 802.1Q Format or Multi-level Format.
The factory default value for this object is disable(2).rw Enumeration .1.3.6.1.4.1.50.8.1.2.1.14.1.1 |
lanBlazer7000VlanExchangeDomainNameThe VLAN Exchange Domain Name of the switch. A switch may
only belong to one domain.rw DisplayString .1.3.6.1.4.1.50.8.1.2.1.14.1.2 |
lanBlazer7000VlanExchangeUpdaterIdThe IP address of the switch from which the VLAN Exchange
configuration was learned.ro NetworkAddress .1.3.6.1.4.1.50.8.1.2.1.14.1.3 |
lanBlazer7000VlanExchangeUpdateTimeStampThe time at which the VLAN Exchange configuration changed
on the initiating switch.ro DisplayString .1.3.6.1.4.1.50.8.1.2.1.14.1.4 |
lanBlazer7000VlanExchangeConfigRevNumConfiguration Revision Number of VLAN Exchange Configuration on
the switch that initiated the VLAN Exchange.ro INTEGER .1.3.6.1.4.1.50.8.1.2.1.14.1.5 |