IBM-LES-BUS-MIB: View SNMP OID List / Download MIB

VENDOR: IBM


 Home MIB: IBM-LES-BUS-MIB
Download as:   

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 ibmLesBusMIB 1.3.6.1.4.1.2.6.118.1.2.1.1
     ibmLesBusConfGroup 1.3.6.1.4.1.2.6.118.1.2.1.1.1
         ibmLesBusConfTable 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1 no-access
This table contains configuration information for the LESs within the scope of the agent.
             ibmLesBusConfEntry 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1 no-access
Each entry in this table represents a LES. The parameters in each entry apply to one emulated LAN served by one LES. Objects lesLanType and lesMaxFrameSize are also required besides lesRowStatus during row creation.
                 atmDevNum 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.1 integer read-write
Identifies ATM device to be used by LES/BUS.
                 useBurnedInEsi 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.2 truthvalue read-write
Specifies whether a MAC Address burned into the ATM device should be used as the End System Identifier component of the LES/BUS ATM Address.
                 configuredEsi 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.3 atmprivateaddresi read-only
Locally Administered End System Identifier that is to be used as the ESI component of the LES/BUS ATM Address. If this object is used do not use the ATM Forum elanLecAtmMask. If both are used the last object set will take affect.
                 configuredSelector 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.4 atmselector read-only
Specifies value to be used as Selector field component of LES/BUS ATM Address. If this object is used do not use the ATM Forum elanLecAtmMask. If both are used the last object set will take affect.
                 leArpResponseDest 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.5 integer read-write
When the value is ALL_CLIENTS, LE_ARP_RESPONSE frames initiated or forwarded by the LES are sent to all clients on the Point-to-Multipoint Control Distribute VCC(s). When the value is ONE_CLIENT, LE_ARP_RESPONSE frames are sent solely to the client that originated the associated LE_ARP_REQUEST over the Control Direct VCC to that client. The primary advantage of sending LE_ARP_RESPONSE frames to all clients is that the clients are provided an opportunity to learn new {LAN Destination, ATM Address} mappings by 'eavesdropping' (secondary effects include lower LES processing requirements and less latency introduced by the LES). The potential disadvantage is that the benefits of eavesdropping, if it is even performed, may not compensate for the additional client overhead. Enumeration: 'oneClient': 0, 'allClients': 1.
                 use2ControlDistributeVccs 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.6 truthvalue read-write
When TRUE, proxy clients are placed on one Point-to-Multipoint Control Distribute VCC and all other clients are placed on another Point-to-Multipoint Control Distribute VCC. When FALSE, all clients are placed on a single Point-to-Multipoint Control Distribute VCC. The advantage of using two Control Distribute VCCs is that non-proxy clients are not perturbed by LE_ARP_REQUESTs for unregistered LAN Destinations (the LES answers LE_ARP_REQUESTs for registered LAN Destinations). The disadvantage is that Control Frames destined for all clients (LE_TOPOLOGY_REQUEST, LE_NARP_REQUEST, and possibly LE_ARP_RESPONSE depending upon LES-BUS-12) must be transmitted on 2 VCCs (as a related aside, note that LE_FLUSH_RESPONSEs are sent solely to the originator of the corresponding LE_FLUSH_REQUEST over the Control Direct VCC to that client).
                 use2MulticastForwardVccs 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.7 truthvalue read-write
When TRUE: - proxy clients are placed on one Point-to-Multipoint Multicast Forward VCC and all other clients are placed on another Point-to-Multipoint Multicast Forward VCC, - all 'unknown' unicast frames and all unicast frames for LAN Destinations registered by proxy clients are forwarded on the Proxy Multicast Forward VCC ('unknown' unicast frames are not forwarded to non-proxy clients), - all unicast frames for LAN Destinations registered by non-proxy clients are forwarded on the Multicast Send VCC to that client, and - multicast and broadcast frames are transmitted on both Multicast Forward VCCs. When FALSE: - all clients are placed on a single Point-to-Multipoint Multicast Forward VCC, and - the BUS functions as a simple forwarding device (efficient, but 'dumb') with respect to unicast frames. One advantage of enabling this option is a reduction in client pertubation due to 'nuisance' unicast frames (i.e., unicast frames not destined for the client); proxy clients do not receive unicast frames destined for non-proxy clients, and non-proxy clients never receive nuisance unicast frames. Another advantage is the reduction in network bandwidth devoted to nuisance frames. The potential disadvantage is that the increased processing requirements result in a degradation of overall system performance.
                 validateBestEffortPcr 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.8 truthvalue read-write
When false, Best Effort Control Direct or Multicast Send VCCs will be accepted without regard to the signalled forward Peak Cell Rate (PCR). When true, Best Effort VCCs will be rejected if the signalled forward PCR exceeds the line rate of the LES/BUS ATM device. Calls will not be rejected due to the backward PCR. The signalled backward PCR will be honored if it does not exceed the line rate; otherwise, transmissions to the caller will be at line rate.
                 controlDirectMaxReservedBw 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.9 bandwidth read-write
Defines the maximum acceptable Sustained Cell Rate (SCR) for a Control Direct VCC; if SCR is not specified on the incoming call, then this parameter defines the maximum acceptable Peak Cell Rate (PCR) for a Control Direct VCC with reserved bandwidth. This parameter is applied to both forward and backward directions. Calls received with Traffic Parameters specifying higher rates will be released. If SCR is specified on the incoming call, the call will not be rejected due to the PCR or Maximum Burst Size. The constraint imposed by this parameter is not applicable to BEST EFFORT connections.
                 multicastSendMaxReservedBw 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.10 bandwidth read-write
Defines the maximum acceptable Sustained Cell Rate (SCR) for a Multicast Send VCC; if SCR is not specified on the incoming call, then this parameter defines the maximum acceptable Peak Cell Rate (PCR) for a Multicast Send VCC with reserved bandwidth. This parameter is applied to both forward and backward directions. Calls received with Traffic Parameters specifying higher rates will be released. If SCR is specified on the incoming call, the call will not be rejected due to the PCR or Maximum Burst Size. The constraint imposed by this parameter is not applicable to BEST EFFORT connections.
                 controlDistributeVccType 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.11 atmvcctraffictype read-write
Specifies type of traffic characteristics to be associated with Control Distribute VCC(s). Bandwidth is not reserved for best effort traffic.
                 controlDistributePcr 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.12 bandwidth read-write
Specifies the Peak Cell Rate (PCR) Traffic Parameter for the Control Distribute VCC(s). Since the Control Distribute is a point-to-multipoint VCC, the specified rate applies to the forward direction only.
                 controlDistributeScr 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.13 bandwidth read-write
Specifies the Sustained Cell Rate (SCR) Traffic Parameter for the Control Distribute VCC(s). Since the Control Distribute is a point-to-multipoint VCC, the specified rate applies to the forward direction only. If the SCR equals the PCR specified in LES-BUS-19, the call is signalled with PCR only. If SCR is signalled, the Maximum Burst Size traffic parameter is set to accomodate the maximum control frame size of 1516 bytes.
                 multicastForwardVccType 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.14 atmvcctraffictype read-write
Specifies type of traffic characteristics to be associated with Multicast Forward VCC(s). Bandwidth is not reserved for best effort traffic.
                 multicastForwardPcr 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.15 bandwidth read-write
Specifies the Peak Cell Rate (PCR) Traffic Parameter for the Multicast Forward VCC(s). Since the Multicast Multicast Forward is a point-to-multipoint VCC, the specified rate applies to the forward direction only.
                 multicastForwardScr 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.16 bandwidth read-write
Specifies the Sustained Cell Rate (SCR) Traffic Parameter for the Multicast Forward VCC(s). Since the Multicast Forward is a point-to-multipoint VCC, the specified rate applies to the forward direction only. If the SCR equals the PCR specified in LES-BUS-22, the call is signalled with PCR only. If SCR is signalled, the Maximum Burst Size traffic parameter is set to accomodate the maximum data frame size specified in maxDataFrameSize.
                 validateJoinsWithLecs 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.17 truthvalue read-write
Specifies whether clients that attempt to join the ELAN must be validated by the LECS. The default value is taken from the corresponding object in the ELAN MIB, and it overrides the ELAN value.
                 redundancyEnabled 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.18 truthvalue read-write
Redundancy support allows clients to be assigned to a backup LES/BUS in the event that the primary LES/BUS for the ELAN fails.
                 redundancyRole 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.19 integer read-write
Redundancy Protocol Role. Specifies whether this LES/BUS instance is to serve as the primary or backup LES/BUS for the ELAN. This object is only valid when redundancyEnabled is true. If this object is never set and redundancyEnabled has never been set to true redundancyRole will have a value of 0. Enumeration: 'backupLesBus': 2, 'primaryLesBus': 1, 'neverSet': 0.
                 redundancyAtmAddr 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.20 atmlaneaddress read-write
ATM Address of Backup LES/BUS. Specifies the ATM address of the backup LES/BUS for the ELAN. Currently, only the private address formats defined by the ATM Forum are supported, there are three private ATM address formats (Data Country Code (DCC) Format, International Code Designator (ICD) Format, and E.164 Format) and all are modeled after the format of an OSI Network Service Access Point (NSAP), all three private address formats are 20 octets (ATM_PRIVATE_ADDR_OCTETS) in length, and the most significant octet contains an Authority and Format Identifier (AFI) field that identifies the address format (see constants ATM_ADDR_DCC_AFI, ATM_ADDR_ICD_AFI, and ATM_ADDR_E164_AFI), the remaining octets of the address are divided into an Initial Domain Identifier (IDI) and a Domain Specific Part (DSP), the IDI has specific encoding rules that may be enforced by the configurator (see Section 5.1.3 of the ATM Forum UNI Specification).
                 bmonEnabled 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.21 truthvalue read-write
Enable BUS Monitor for ELAN. When TRUE, host usage of the Broadcast and Unknown Server is monitored. Periodic sampling is performed to provide information on the top N heaviest users of the BUS. Here, a user is defined as any MAC address originating data frames to the BUS. Information is available on the last sample interval. When FALSE, BUS Monitoring is not performed.
                 numTopMacs 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.22 integer read-write
Number of Top MAC Addresses to Record. Specifies the number of MACs to be recorded with the highest quantity of sampled frames sent to the BUS in a sample interval.
                 sampleDuration 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.23 integer read-write
Number of seconds in each Sample Interval. Specifies the number of seconds in each BUS Monitor sample interval.
                 interSampleTime 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.24 integer read-write
Minutes between start of one sample and the next sample. Specifies the number of minutes between the start of one BUS Monitor sample interval and the start of the next sample interval.
                 sampleRate 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.25 integer read-write
Specifies the rate at which the BUS Monitor samples frames sent to the BUS during a sample interval. A value of 1 indicates that every frame sent to the BUS is sampled. A value of 100 indicates that 1 out of every 100 frames sent to the BUS is sampled.
                 busMode 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.26 integer read-write
With the Fast Bus Feature the BUS can run now run in one of three modes: systemBusMode(1) - Frames from BUS are buffered into system memory. All intelligent BUS mode are available in this mode. adapterBusMode(2) - Frames received for the BUS are kept in adapter memory. BCM is not available in this mode. On Token-Ring all data frames are counted as multicast frames. vccSpliceBusMode(3) - The BUS ties all Multicast Send VCCs into the Multicast Forward VCC. Frames received for the BUS are immediately forwarded onto the Multicast Foward VCC without notifying the BUS. Statistics related to frame rec/transmit are not maintained when the Bus mode is VCC Splice. Enumeration: 'systemBusMode': 1, 'adapterBusMode': 2, 'vccSpliceBusMode': 3.
     ibmLesBusStatGroup 1.3.6.1.4.1.2.6.118.1.2.1.1.2
         ibmLesBusStatTable 1.3.6.1.4.1.2.6.118.1.2.1.1.2.1 no-access
This table contains all counters ???.
             ibmLesBusStatEntry 1.3.6.1.4.1.2.6.118.1.2.1.1.2.1.1 no-access
Each entry in this table contains a LES and its counters.
                 redundancyVccRefused 1.3.6.1.4.1.2.6.118.1.2.1.1.2.1.1.1 counter32 read-only
Number of Redundancy VCC call setup requests rejected by the LES for any reason.
                 redundancyVccReleased 1.3.6.1.4.1.2.6.118.1.2.1.1.2.1.1.2 counter32 read-only
Number of times a Redundancy VCC has been released by LEC/network for any reason.
                 redundancyVccFailure 1.3.6.1.4.1.2.6.118.1.2.1.1.2.1.1.3 counter32 read-only
Number of Redundancy VCC requests made by LES that failed.
     ibmBusMonStatGroup 1.3.6.1.4.1.2.6.118.1.2.1.1.3
         bmonSampleInfoTable 1.3.6.1.4.1.2.6.118.1.2.1.1.3.1 no-access
This table contains the BUS Monitor (BMON) information for the last complete sample processed. The following information is maintained for each BUS instance using BMON: - Time that the last complete sample interval started. - Duration of the sample interval. - Number of top hosts actually recorded in the sample. - Number of frames received during the sample interval. - Number of frames sampled in the sample interval. - Frame sampling rate (i.e., 1 out of N frames sampled). Each BUS instance may have a BMON. This table is indexed by lesConfIndex.
             bmonSampleInfoEntry 1.3.6.1.4.1.2.6.118.1.2.1.1.3.1.1 no-access
Each entry in this table contains BMON information for the last complete sample processed for a specific BUS instance.
                 bmonSampleStartTime 1.3.6.1.4.1.2.6.118.1.2.1.1.3.1.1.1 timestamp read-only
Timestamp for the start of the last complete BUS Monitor sample interval.
                 bmonSampleDuration 1.3.6.1.4.1.2.6.118.1.2.1.1.3.1.1.2 counter32 read-only
Duration of the last complete sample interval.
                 bmonNumTopMacs 1.3.6.1.4.1.2.6.118.1.2.1.1.3.1.1.3 counter32 read-only
The number of top hosts actually recorded during the last complete sample interval.
                 bmonReceivedFrames 1.3.6.1.4.1.2.6.118.1.2.1.1.3.1.1.4 counter32 read-only
The total number of frames received during the last complete sample interval.
                 bmonSampledFrames 1.3.6.1.4.1.2.6.118.1.2.1.1.3.1.1.5 counter32 read-only
The number of frames actually sampled during the last complete sample interval.
                 bmonSamplingRate 1.3.6.1.4.1.2.6.118.1.2.1.1.3.1.1.6 counter32 read-only
The frame sampling rate given as N where the rate is 1 out of every N frames will be sampled.
         bmonStatTable 1.3.6.1.4.1.2.6.118.1.2.1.1.3.2 no-access
This table contains the BUS Monitor (BMON) counters for the top N heaviest users of a BUS (i.e., the N MAC addresses that originate the most data frames. Each BUS instance may have a BMON. This table augments the bmonConfTable.
             bmonStatEntry 1.3.6.1.4.1.2.6.118.1.2.1.1.3.2.1 no-access
Each entry in this table contains BMON statistics for the top users of the indicated BUS instance.
                 bmonTopNRank 1.3.6.1.4.1.2.6.118.1.2.1.1.3.2.1.1 counter32 read-only
Rank for the indicated host (i.e., MAC address) given as N where 1 is the host originating the most frames.
                 bmonTopNSrcMacAddr 1.3.6.1.4.1.2.6.118.1.2.1.1.3.2.1.2 macaddress read-only
Source MAC Address for this host.
                 bmonTopNLecAtmAddr 1.3.6.1.4.1.2.6.118.1.2.1.1.3.2.1.3 atmlaneaddress read-only
Associated LEC ATM Address for this host.
                 bmonTopNFramesSampled 1.3.6.1.4.1.2.6.118.1.2.1.1.3.2.1.4 counter32 read-only
Number of frames sampled from this host during last complete sample interval.
     ibmLesBusMIBConformance 1.3.6.1.4.1.2.6.118.1.2.1.1.4
         ibmLesBusMIBGroups 1.3.6.1.4.1.2.6.118.1.2.1.1.4.1
             ibmLesBusCConfGroup 1.3.6.1.4.1.2.6.118.1.2.1.1.4.1.1
             ibmLesBusCStatGroup 1.3.6.1.4.1.2.6.118.1.2.1.1.4.1.2
             ibmBusMonCStatGroup 1.3.6.1.4.1.2.6.118.1.2.1.1.4.1.3
         ibmLesBusMIBCompliances 1.3.6.1.4.1.2.6.118.1.2.1.1.4.2
             ibmLesBusMIBCompliance 1.3.6.1.4.1.2.6.118.1.2.1.1.4.2.1