ODSLANBlazer7000-MIB: View SNMP OID List / Download MIB

The version of the LANBlazer 700 Enterprise Specific MIB that this agent supports.

The value of this object represents the index into the community table that is used to authenticate SNMP requests for this manager.

An index that uniquely identifies this entry.

The community string included in the SNMP PDU used for authentication purposes.

The type of address associated with this community. If set to any(1), only the community string is authenticated. Enumeration: 'any': 1, 'ipv4': 2.

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

The 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. Enumeration: 'readWrite': 3, 'none': 1, 'moreSpecific': 4, 'readOnly': 2.

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

Secure 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. Enumeration: 'administrator': 2, 'normal': 1.

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

The subdirectory that contains the help files on the document server. Typically, this directory is 'help'.

The model of the chassis that this agent is managing. Enumeration: 'p220': 2, 'p550': 1.

The number of slots available in this chassis. If this chassis is a stackable chassis, the total capacity of stacking units.

A table of inventory information.

Inventory information related to this device.

The resource class of this inventory item.

The resource identifier of this inventory item.

The model number of this device.

The serial number of this device.

The revision number of this device.

Information related to the manufacturing of this device.

A scratch pad area available for keeping user-supplied inventory information.

A table of information related to each power supply in the system.

An entry providing information about a particular power supply in the system.

An index that uniquely identifies this power supply. This index corresponds to the lanBlazer7000ResourceIndex of the power supply type resource.

An enumerated integer describing the type of power supply. Enumeration: 'psB': 3, 'unknown': 1, 'psA': 2.

The 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. Enumeration: 'unknown': 3, 'faulty': 2, 'okay': 1.

The status of the input power feed (e.g. the AC power cord) to this power supply. Enumeration: 'unknown': 3, 'faulty': 2, 'okay': 1.

The status of the output power from this power supply. Enumeration: 'unknown': 3, 'faulty': 2, 'okay': 1.

The total capacity of power supplied by this supply in Watts.

The total capacity (in Watts) of power available (currently) in the system.

The total power (in Watts) currently being consumed in the system.

This table manages the power attributes associated with each module.

An entry in the power control table manages the power attributes of the specified module.

The total power (in Watts) used by this module.

The 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. Enumeration: 'high': 1, 'low': 3, 'normal': 2.

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

A table of information related to the temperature within the system.

An entry providing temperature information related to a specific temperature probe in the system.

A unique index that identifies this temperature probe. This index corresponds to the lanBlazer7000ResourceIndex for temperature probe type resources.

The current temperature reading of this temperature probe in degrees Celsius.

The upper temperature limit of this temperature probe in degrees Celsius.

The upper temperature warning of this temperature probe in degrees Celsius.

The lower temperature warning of this temperature probe in degrees Celsius.

The lower temperature limit of this temperature probe in degrees Celsius.

A table of information related to the modules in the system.

Attributes related to managing this module.

An index that uniquely identifies this module. This index corresponds to the lanBlazer7000ResourceIndex associated with module type resources.

A user-assignable name for this module.

An enumerated integer that is unique for each module model. Enumeration: 'm5504-1000': 7, 'm5500R-SUP': 13, 'm2204-100TX': 16, 'm2206-1000': 3, 'm2202-100FX': 10, 'unknown': 1, 'm5512R-100TX': 12, 'm5502-1000': 2, 'm2201-1000': 8, 'm2200-SUP': 15, 'm5520-100TX-I': 9, 'm5510R-100FX': 11, 'm5510-100FX': 5, 'm5500-SUP': 6, 'm2224-100TX': 17, 'm5502R-1000': 14, 'm5520-100TX-QS': 4.

The 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. Enumeration: 'supervisor': 3, 'gigabit': 1, 'fastEthernet': 2.

The number of slots that this module occupies.

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

The total number of ports associated with this module.

A table of information related to every data port in this data networking system.

A data port associated with this data networking system.

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

The user-assigned name for this port. Note that setting this object for an internal(1) port results in an error.

An 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. Enumeration: 'ether-oneHundred': 3, 'internal': 1, 'ether-ten-oneHundred': 2, 'ether-gigabit': 4.

The 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. Enumeration: 'ether-oneHundred': 3, 'internal': 1, 'ether-ten-oneHundred': 2, 'ether-gigabit': 4.

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

The 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. Enumeration: 'disabled': 1, 'warning': 3, 'okay': 2, 'linkFailure': 5, 'disabledButOkay': 4.

The connector type associated with this port. Enumeration: 'fiber-SC': 4, 'aui': 6, 'rj45': 2, 'internal': 1, 'fiber-ST': 3, 'rs-232': 5.

The 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. Enumeration: 'one-hundred-megabits-per-second': 2, 'one-gigabit-per-second': 3, 'ten-megabits-per-second': 1, 'under-negotiation': 4.

The 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. Enumeration: 'half-duplex': 1, 'under-negotiation': 3, 'full-duplex': 2.

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

A table of ports that support flow control.

Configuration objects related to port based flow control.

Flow 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. Enumeration: 'enable-with-aggressive-backoff': 3, 'enable': 1, 'disable': 2.

A table of ports that support full- and half-duplex data communications.

A port device configuration that controls the duplex mode of this port.

A 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. Enumeration: 'half-duplex': 1, 'full-duplex': 2.

A table of port devices that support multiple speeds.

A port that supports multiple speeds.

Some 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. Enumeration: 'one-hundred-megabits-per-second': 2, 'ten-megabits-per-second': 1.

A table of ports that support auto-negotiation.

Attributes associated with a port that supports auto-negotiation.

Setting this object to autoNegotiate(1) causes this port to negotiate the duplex mode and the port speed, subject to the port's capabilities. Enumeration: 'autoNegotiate': 1, 'manualConfiguration': 2.

The speed to advertise while auto-negotiating. Enumeration: 'ten-megabits-per-second': 3, 'one-hundred-megabits-per-second': 2, 'ten-and-one-hundred-megabits-per-second': 1.

The duplexity to advertise while auto-negotiating. Enumeration: 'half-duplex': 2, 'full-and-half-duplex': 1.

A table of ports that support the ability to limit the rate of floods.

The rate limit configuration associated with this port.

This 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). Enumeration: 'enable': 1, 'enableIncludeKnownMulticast': 3, 'disable': 2.

The 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. Enumeration: 'two-percent': 2, 'five-percent': 3, 'eighty-percent': 7, 'ten-percent': 4, 'forty-percent': 6, 'one-percent': 1, 'twenty-percent': 5.

The 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. Enumeration: 'rateLimit128': 8, 'rateLimit8': 4, 'rateLimit2048': 11, 'rateLimit2': 2, 'rateLimit1': 1, 'rateLimit256': 9, 'rateLimit4': 3, 'rateLimit64': 7, 'rateLimit1024': 10, 'rateLimit16': 5, 'rateLimit32': 6.

A table of ports that support the ability to classify frame priority based on 3Com Pace(r) Prioritization.

A port that supports 3Com Pace(r) priority.

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

A table of ports that support the port category feature. Currently, all ports support this capability.

A port that supports port categorization.

By 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. Enumeration: 'userPort': 1, 'servicePort': 2.

A table of frame buffers in the system.

Objects related to the management of this frame buffer.

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

The switch fabric port associated with this buffer.

The value of this object indicates whether the buffer is used for buffering frames going into the switching fabric or coming out of the fabric. Enumeration: 'out': 2, 'in': 1.

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

The amount of memory available for frame buffering in Kilobytes (KB).

Configures 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). Enumeration: 'disable': 1, 'one-second': 3, 'quarter-second': 2.

The 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). Enumeration: 'everyFour': 5, 'everyThousand': 3, 'everyHundred': 4, 'everyTenThousand': 2, 'strictPriority': 1.

This 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. Enumeration: 'fiftyPercent': 6, 'none': 1, 'tenPercent': 2, 'thirtyPercent': 4, 'twentyPercent': 3, 'fortyPercent': 5.

This 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. Enumeration: 'none': 1, 'six': 7, 'three': 4, 'seven': 8, 'two': 3, 'four': 5, 'five': 6, 'one': 2.

This object indicates whether this buffer is in a congested state.. Enumeration: 'informationNotAvailable': 1, 'congested': 3, 'notCongested': 2.

The count of the number of high priority frames dropped due to the high priority queue overflowing.

The count of the number of low priority frames dropped due to the low priority queue overflowing.

The count of the number of high priority frames dropped due to being in the high priority queue too long (the frame aged out).

The count of the number of low priority frames dropped due to being in the low priority queue too long (the frame aged out).

The count of the number of frames dropped due to the destination (output) buffer being congested.

When 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. Enumeration: 'ieee8021dStp': 1, 'stpPerVlan': 2, 'twoLayerStp': 3, 'disable': 4.

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

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

A table of Spanning Tree information for every bridge in the system.

An index that uniquely identifies this bridge.

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

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

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

The priority value of the Bridge Identifier. See dot1dStpPriority.

The time since the last topology change was detected. See dot1dStpTimeSinceTopologyChange.

The total number of topology changes. See dot1dStpTopChanges

The bridge considered to be root by this node. See dot1dStpDesignatedRoot.

The cost of the path to the root from this node. See dot1dStpRootCost.

The port number with the lowest cost path to the root bridge. See dot1dStpRootPort.

The maximum age used by this bridge to hold onto STP information before discarding. See dot1dStpMaxAge.

The amount of time between configuration BPDUs. See dot1dStpHelloTime.

The time value that indicates the interval during which no more than two configuration BPDUs will be sent by this node. See dot1dStpHoldTime.

The amount of time that this node stays in each of the Listening and Learning states. See dot1dStpForwardDelay.

The value of MaxAge when this bridge is the root. See dot1dStpBridgeMaxAge.

The value of HelloTime to use when this bridge is the root. See dot1dStpBridgeHelloTime.

The value of FowardDelay to use when this bridge is the root. See dot1dStpBridgeForwardDelay.

A table of Spanning Tree information for every port that supports Spanning Tree in every bridge in the system

An index that uniquely identifies this bridge port. This index corresponds to the lanBlazer7000ResourceIndex for bridge port type resources.

The value of the priority field in the port ID. See dot1dStpPortPriority. The default value is 128.

The 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. Enumeration: 'listening': 3, 'disabled': 1, 'broken': 6, 'learning': 4, 'forwarding': 5, 'blocking': 2.

The enabled/disabled status of this port. See dot1dStpPortEnable. The default is enabled(2). Enumeration: 'disabled': 2, 'enabled': 1.

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

The bridge recorded as root for this port's segment. See dot1dStpPortDesignatedRoot.

The path cost of the designated root of the segment connected to this port. See dot1dStpPortDesignatedCost.

The bridge identifier of the bridge that is considered the designated bridge for this port's segment. See dot1dStpPortDesignatedBridge.

The port identifier of the port on the Designated Bridge for this port's segment. See dot1dStpPortDesignatedPort.

The number of times this port has transitioned from the learning state to the forwarding state. See dot1dStpPortForwardTransitions.

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

When set to setDefault(2), the lanBlazer7000BridgePortPriority, lanBlazer7000BridgePortEnable, and lanBlazer7000BridgePortPathCost will be set to the factory default values. Enumeration: 'setDefault': 2, 'useCurrentValues': 1.

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

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

A particular address table entry.

An index that uniquely identifies this address entry.

The address table that this entry is associated with.

The IEEE 802 MAC Address associated with this database entry.

The switch port that this address is associated with.

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

The VLAN ID of the VLAN that this address entry corresponds to.

If set to high(2), frames destined to this address are classified with priority value 4. Enumeration: 'priorityFour': 2, 'priorityZero': 1.

When 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. Enumeration: 'normalForward': 1, 'specialDelivery': 2.

It is sometimes useful for the switch processor to eavesdrop on traffic to certain destinations. This is especially useful in supporting the intelligent multicasting function. Enumeration: 'copyCPU': 2, 'normalForward': 1.

This 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. Enumeration: 'permanent': 3, 'other': 1, 'deleteOnTimeout': 5, 'deleteOnReset': 4, 'invalid': 2.

This 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 permanent Enumeration: 'learned': 2, 'other': 1, 'self': 3, 'mgmt': 4.

This 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?]

A summary object that packs as many address entries possible into a summary object.

The 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]; };

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

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

The index of the address entry that was created for this address.

The IEEE 802 MAC Address associated with this database entry.

The port to bind this address to.

The VLAN ID of the VLAN to bind this address to.

If set to high(2), frames destined to this address are classified with priority value 4. Enumeration: 'priorityFour': 2, 'priorityZero': 1.

The 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. Enumeration: 'permanent': 1, 'deleteOnTimeout': 3, 'deleteOnReset': 2.

The 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). Enumeration: 'invalidVlanID': 8, 'entryExistsError': 5, 'success': 3, 'underCreation': 2, 'createRequest': 1, 'invalidMacAddress': 6, 'otherError': 4, 'invalidPortBinding': 7.

The index of the last entry written to the address change table

The count of the number of times the address change table has wrapped.

The maximum number of entries in the address change table.

.

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

The number of times that the lanBlazer7000AddressChangeLastIndex had wrapped when this entry was added.

The index that uniquely identifies this address change entry.

The address entry that changed. The value of this object corresponds to the lanBlazer7000L2AddressIndex object.

The structure is interpreted in the following manner:

A unique index that identifies this switch port. The value of this index corresponds to the value of the lanBlazer7000ResourceIndex for switch ports.

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

When 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. Enumeration: 'learnAsDynamic': 1, 'convertToStatic': 2.

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

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

The physical port resource bound to this switch port.

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

The 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. Enumeration: 'port-based': 1.

The 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. Enumeration: 'trunk3Com': 4, 'clear': 1, 'ieee8021q': 2, 'multiLevel': 3.

The 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. Enumeration: 'dynamic': 3, 'static': 1, 'persistent': 2.

Each 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. Enumeration: 'useTag': 1, 'ignoreTag': 2.

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

The 3Com VLAN mapping table associated with this switch port. The default is 1, which indicates the default mapping table.

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

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

Each switch port is associated with an interface. This object provides a mechanism to map switch ports to bridge ports.

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

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

An index that uniquely identifies this hunt group. This index corresponds to the value of lanBlazer7000ResourceIndex for resources of the hunt group type.

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

The current number of ports that belong to this hunt group.

Enumeration: 'enable': 1, 'disable': 2.

Enumeration: 'underCreation': 2, 'deleteRequest': 3, 'createRequest': 1, 'active': 4.

A table of port mirroring entries used to mirror traffic from a source port to a mirror port.

Objects related to the PortMirroring functionality.

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

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

The 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). Enumeration: 'enable': 2, 'disable': 1, 'periodic': 3.

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

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

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

A user-assignable name for this Vlan.

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

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

The bridge resource which is bound to this Vlan.

The 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. Enumeration: 'invalidVlanID': 8, 'invalidVlanAFTIndex': 10, 'entryExistsError': 7, 'invalidVlanInitialHashTableSize': 12, 'invalidVlanBridgeIndex': 11, 'underCreation': 2, 'createRequest': 1, 'destroyRequest': 3, 'invalidVlanName': 9, 'otherError': 6, 'invalidVlanAutoIncrementHTSize': 13, 'active': 5, 'underDestruction': 4.

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

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

This attribute indicates if the VLAN was learned. If learned it indicates if the VLAN was learned either by VLAN Exchange or Auto VLAN creation. Enumeration: 'auto': 3, 'notLearned': 1, 'vlanExchange': 2.

A user-readable name associated with this table.

The 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. Enumeration: 'active': 3, 'createRequest': 1, 'destroyRequest': 2, 'otherError': 5, 'entryExistsError': 4.

The external tag of this 3Com VLAN.

The VLAN ID of the VLAN that this 3Com tag is associated with.

The 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. Enumeration: 'active': 3, 'createRequest': 1, 'destroyRequest': 2, 'otherError': 4.

An instance of a virtual switch port indicates that this switch port is a member of this VLAN.

The Resource ID of the virtual switch port bound to the VLAN.

Typically, 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). Enumeration: 'clear': 1, 'trunkingFormat': 2.

The bridge port resource bound to this virtual port.

The 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. Enumeration: 'dynamic': 3, 'static': 1, 'persistent': 2.

The 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. Enumeration: 'entryExistsError': 5, 'entryNoExistError': 6, 'createRequest': 1, 'destroyRequest': 2, 'otherError': 4, 'active': 3.

Table of events currently supported.

Attributes associated with the event.

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

When enabled, this action will cause an event log entry to be created. Enumeration: 'enable': 1, 'disable': 2.

When enabled, this event will cause an SNMP trap to be generated. Enumeration: 'enable': 1, 'disable': 2.

When enabled, this event will cause a message to printed to the console serial port. Enumeration: 'enable': 1, 'disable': 2.

The maximum number of entries in the log table. Changing this value causes the existing log to be truncated and rebuilt.

The log index of the last entry entered in the log.

The number of times that the last entry has wrapped from 65K back to 1.

The log table for the events in the event table that are enabled for the Log Action.

An entry in the log indicates information associated with a particular event.

The index that uniquely identifies the event that caused this log entry.

An index that uniquely identifies this log entry.

The value of sysUpTime when this event was triggered.

The event log description.

The type of event that caused this log entry.

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

The date and time when this log entry was made. The format is yy-Mon- dd hh:mm:ss, time is in 24 hour time.

The type of object (if provided) that triggered this event. If not provided, the value is equal to 'Invalid Resource'.

The instance of this resource (if provided - see lanBlazer7000EventLogResType) that triggered this event.

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

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

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

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

A unique index that identifies the occurence of this event. This ID can be correlated between traps, logs and the like.

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

The ID of the last entry made to the shutdown log.

This 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. Enumeration: 'acknowledged': 2, 'not-acknowledged': 1.

A table of the last events logged before the system restarted.

A log entry stored in non-volatile memory.

The index that uniquely identifies the event that caused this ShutdownLog entry.

An index that uniquely identifies this ShutdownLog entry.

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

The event ShutdownLog description.

The type of event that caused this ShutdownLog entry.

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

The date and time when this ShutdownLog entry was made. The format is yy-Mon-dd hh:mm:ss, time is in 24 hour time.

The type of object (if provided) that triggered this event. If not provided, the value is invalid.

The instance of this resource (if provided) that triggered this event.

To be provided.

The data type associated with the ShutdownLog event value. This object indicates how to interpret the data stored in the event ShutdownLog value.

The value associated with the event encoded in an octet string.

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

A unique index that identifies the occurence of this event. This ID can be correlated between traps, logs and the like.

The index that uniquely identifies the event that caused this trap.

The value of sysUpTime when this event was triggered.

The event log description.

The type of event that caused this trap.

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

The date and time when this trap was sent. The format is yy-Mon- dd hh:mm:ss, time is in 24 hour time.

The type of object (if provided) that triggered this event. If not provided, the value is equal to 'Invalid Resource'.

The instance of this resource (if provided - see lanBlazer7000EventTrapResType) that triggered this event.

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

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

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

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

A unique index that identifies the occurence of this event. This ID can be correlated between traps, logs and the like.

The total number of alarm entries in the triggered state currently in the alarm table.

The value of sysUpTime when any alarm state last changed (either triggering a new alarm or re-arming an old one).

A table of all alarms in the triggered state.

An alarm in the triggered state.

The unique index that identifies this alarm.

The name of this alarm.

The high order 32 bits of the value that triggered this alarm.

The low order 32 bits of the value that triggered this alarm.

The OID of the alarm variable if this is a user-created alarm (null otherwise).

The resource type of this alarm if this is an internally created alarm.

The resource identifier associated with this alarm if this is an internally created alarm.

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

This is the owner of the alarm.

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

The VLAN Exchange Domain Name of the switch. A switch may only belong to one domain.

The IP address of the switch from which the VLAN Exchange configuration was learned.

The time at which the VLAN Exchange configuration changed on the initiating switch.

Configuration Revision Number of VLAN Exchange Configuration on the switch that initiated the VLAN Exchange.

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

A lanBlazer7000ConfigurationTrap is sent by the agent when the configuration event is triggered. These events are triggered when a configuration change is made.

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

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

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

A lanBlazer7000PowerTrap is sent by the agent when the power event is triggered. These events are triggered when a power supply changes status.