IBM-OSA-MIB: View SNMP OID List / Download MIB

The IBM Enterprise Specific MIB definitions for enabling management of an IBM OSA-Express feature. Licensed Materials - Property of IBM Restricted Materials of IBM 5694-A01 (C) Copyright IBM Corp. 2002 US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Indexed by ifIndex. One entry in this table will exist per OSA Device Interface.

Definition of a single entry in the ibmOSAExpChannelTable. Indexed by the ifIndex of the corresponding Device interface.

The CHPID corresponding to this ifIndex.

The type of channel for this interface. OSA Direct Express has a value of 17. Enumeration: 'osaDirectExpress': 17.

Hardware model of the channel. The value oasExp150(2) indicates a hardware level of 1.50. The value oasExp175(3) indicates a hardware level of 1.75. Enumeration: 'unknown': 1, 'osaExp175': 3, 'osaExp150': 2.

Indicates the type of OSA feature present. Enumeration: 'tokenRing': 82, 'unknown': 1, 'gigabitEthernet': 65, 'atmEmulatedEthernet': 2304, 'fastEthernet': 81.

An OSA-Express feature can be shared across multiple LPs. This object indicates if this feature is currently being shared between LPs Enumeration: 'notShared': 0, 'shared': 1.

This is the Node Descriptor of the OSA feature. It represents the ND obtained from the Channel Subsystem. Bits Name Flag is first byte char(1) Validity Valid - always '20'x char(1) Reserved Reserved by architecture char(1) Class Class for subsystem node char(1) CHPID CHP ID for specified int char(6) TypeNum Type number of the SDC char(3) ModelNum Model number in the form of 3 EBCDIC OCTETS char(3) Manufacturer Manufacturer in the form of 3 EBCDIC OCTETS char(2) Mfr Plant Plant of manufacture-2 digit code char(12)SeqNum Sequence number (12 EBCDIC OCTETS) char(2) Tag Tag

This is the firmware (or micro code level) of the OSA feature. For example, OSA code level 05.6A would be represented as 0x056A.

The average, over a 1 minute interval, of the percentage of time that the PCI bus was utilized to transfer data. It does not include idle time or time used by routine maintenance tasks. The range for this value is from 0 to 100%.

The average, over a 1 minute interval, of the percentage of time that the CHPID Processor was utilized to transfer data. It does not include idle time or time used by routine maintenance tasks. The range for this value is from 0 to 100%.

The average, over a 5 minute interval, of the percentage of time that the PCI bus was utilized to transfer data. It does not include idle time or time used by routine maintenance tasks. The range for this value is from 0 to 100%.

The average, over a 5 minute interval, of the percentage of time that the CHPID Processor was utilized to transfer data. It does not include idle time or time used by routine maintenance tasks. The range for this value is from 0 to 100%.

The average, over an hour interval, of the percentage of time that the PCI bus was utilized to transfer data. It does not include idle time or time used by routine maintenance tasks.

The average, over an hour interval, of the percentage of time that the CHPID Processor was utilized to transfer data. It does not include idle time or time used by routine maintenance tasks. The range for this value is from 0 to 100%.

This table provides performance information for each Logical Partition (LP) the OSA can connect to.

Definition of a single entry for a single LP in the ibmOSAExpPerfTable. Indexed by the ifIndex of the corresponding Device interface.

The performance data on this OSA for partition 0. The 40 bytes of hex data that are returned are decoded as follows: Offset Bytes Field Meaning 0 4 LP Number 4 4 Processor Util 1 Minute 8 4 In Kbytes Rate 1 Minute 12 4 Out Kbytes Rate 1 Minute 16 4 Processor Util 5 Minutes 20 4 In Kbytes Rate 5 Minutes 24 4 Out Kbytes Rate 5 Minutes 28 4 Processor Util 60 Minutes 32 4 In Kbytes Rate 60 Minutes 36 4 Out Kbytes Rate 60 Minutes The Processor Util 1 Minute is defined as follows: The average, over a 1 minute interval, of the percentage of time that the CHPID Processor was utilized to transfer data for a specific LP. It does not include idle time or time used by routine maintenance tasks. The range for this value is from 0 to 100%. The In Kbytes Rate 1 Minute is defined as follows: The average, over a 1 minute interval, of the number of inbound kilobytes processed for a specific LP. The Out Kbytes Rate 1 Minute is defined as follows: The average, over a 1 minute interval, of the number of outbound kilobytes processed for a specific LP. The 5 and 60 minute fields are defined similar to the 1 minute fields, but pertain to intervals of 5 and 60 minutes.

The performance data on this OSA for partition 1. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

The performance data on this OSA for partition 2. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

The performance data on this OSA for partition 3. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

The performance data on this OSA for partition 4. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

The performance data on this OSA for partition 5. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

The performance data on this OSA for partition 6. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

The performance data on this OSA for partition 7. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

The performance data on this OSA for partition 8. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

The performance data on this OSA for partition 9. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

The performance data on this OSA for partition 10. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

The performance data on this OSA for partition 11. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

The performance data on this OSA for partition 12. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

The performance data on this OSA for partition 13. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

The performance data on this OSA for partition 14. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

The performance data on this OSA for partition 15. The 40 bytes of hex data that are returned are decoded the same as for partition 0.

This table provides PE information to help IBM diagnose any OSA problems.

Definition of a single entry in the ibmOSAExpPETable. Indexed by the ifIndex of the corresponding Device interface

The maximum size of the OSA ARP Cache

This is the number of Pending entries in the ARP cache.

This the number of active ARP entries.

The number of IP addresses known to the OSA For OSD chpids, this is the maximum # of IP addresses that are: - home ip addresses (Version 4 and Version 6) - remote ip addresses in the arp cache (Version 4 only) - multicast ip addresses that the OSA must accept inbound data packets for (Version 4 and Version 6)

This is the number of IP multicast addresses currently on the OSA

This contains information on the multicast entries that are currently on the OSA. These are in a format that is for IBM use only

This table represents the data associated with a port on an OSA-Express Gigabit or Fast Ethernet OSA.

Definition of a single entry in the ibmOSAExpEthPortTable. Indexed by the ifIndex of the corresponding Device interface.

The physical port number for this port.

The physical port type. Enumeration: 'gigabitEthernet': 65, 'fastEthernet': 81.

The LAN state value ranges from 0 to 8. A value of 5, disabled is further explained in object ibmOsaExpEthDisabledStatus. Enumeration: 'disabled': 5, 'undefined': 0, 'configuredOffline': 8, 'enabled': 4, 'enabling': 2, 'definitionError': 7, 'linkMonitor': 6, 'disabling': 3, 'unavailable': 1.

This object indicates if the processor is in service mode or not. Enumeration: 'notInServiceMode': 0, 'inServiceMode': 1.

When the value of ibmOsaExpEthLanTrafficState is NOT disabled, the value of this object will be zero. When the value of ibmOsaExpEthLanTrafficState is disabled(5), this object explains the reason for the disabled state. The value for this object may be a combination of the bits shown. Bits: 'reserved15': 15, 'serviceProcessorRequest': 9, 'internalPortFailure': 1, 'portTemporarilyDisabled': 6, 'osasfRequest': 11, 'linkFailureThresholdExceeded': 13, 'configurationChange': 12, 'reserved14': 14, 'reserved8': 8, 'networkRequest': 10, 'reserved5': 5, 'reserved4': 4, 'reserved7': 7, 'reserved0': 0, 'reserved3': 3, 'reserved2': 2.

This is the name of the configuration that is on the OSA. It is set using OSA/SF. It is not used by OSA

The configured port speed. This field shows the speed that was configured by the user for the OSA-Express Fast Ethernet feature. It is not used by OSA-Express Gigabit features and will return -1 (FFFF) Enumeration: 'oneHundredMbHalfDuplex': 3, 'tenMbHalfDuplex': 1, 'autoNegotiate': 0, 'tenMbFullDuplex': 2, 'oneThousandMbFullDuplex': 6, 'oneHundredMbFullDuplex': 4, 'notValidGigabit': -1.

The actual speed and mode the OSA is running in Enumeration: 'tenMbFullDuplex': 2, 'tenMbHalfDuplex': 1, 'unknown': 0, 'oneHundredMbFullDuplex': 4, 'oneHundredMbHalfDuplex': 3, 'oneThousandMbFullDuplex': 6.

A 6 byte OCTET STRING which contains the current MAC address in use on the adapter. The values are in canonical format.

A 6 byte OCTET STRING which contains the burned in MAC address on the OSA. The values are in canonical format.

Data set by the user. It is ignored by the OSA.

This is the number of packets that have been transmitted by the OSA since the last time the OSA port was reset

This is the number of packets that have been received by the OSA since the last time the OSA port was reset

This is the number of multicast frames that have been received by the OSA.

This is the number of broadcast frames that have been received by the OSA.

Name of the port as used by TCP/IP

This is the number of non-IP received frames

This field contains the active Group Addresses. An individual Group Address is 6 bytes long with an additional 2 bytes of padding. There are 32 group addresses.

This table represents the data associated with a port on an OSA-Express token ring feature.

Definition of a single entry in the ibmOSAExpTRPortTable. Indexed by the ifIndex of the corresponding Device interface.

The physical port number for this port.

The physical port type. Enumeration: 'tokenring': 82.

The LAN state value ranges from 0 to 8. A value of 5, disabled is further explained in object ibmOsaExpTRDisabledStatus Enumeration: 'disabled': 5, 'undefined': 0, 'configuredOffline': 8, 'enabled': 4, 'enabling': 2, 'definitionError': 7, 'linkMonitor': 6, 'disabling': 3, 'unavailable': 1.

This object indicates if the processor is in service mode or not. Enumeration: 'notInServiceMode': 0, 'inServiceMode': 1.

When the value of ibmOsaExpTRLanTrafficState is NOT disabled, the value of this object will be zero. When the value of ibmOsaExpTRLanTrafficState is disabled(5), this object explains the reason for the disabled state. The value for this object may be a combination of the bits shown. Bits: 'reserved15': 15, 'serviceProcessorRequest': 9, 'internalPortFailure': 1, 'portTemporarilyDisabled': 6, 'osasfRequest': 11, 'linkFailureThresholdExceeded': 13, 'configurationChange': 12, 'reserved14': 14, 'reserved8': 8, 'networkRequest': 10, 'reserved5': 5, 'reserved4': 4, 'reserved7': 7, 'reserved0': 0, 'reserved3': 3, 'reserved2': 2.

This is the name of the configuration that is on the OSA. It is set using OSA/SF. It is not used by OSA

A 6 byte OCTET STRING which contains the current MAC address in use on the OSA.

A 6 byte OCTET STRING which contains the burned in MAC address on the OSA

The configured port speed. This field shows the speed that was configured by the user for the OSA-Express Token Ring feature. Enumeration: 'fourMbFullDuplex': 2, 'autoNegotiate': 0, 'sixteenMbHalfDuplex': 3, 'fourMbHalfDuplex': 1, 'sixteenMbFullDuplex': 4, 'oneHundredMbFullDuplex': 6.

The actual speed and mode the OSA is running in Enumeration: 'fourMbFullDuplex': 2, 'unknown': 0, 'oneHundredMbFullDuplex': 6, 'sixteenMbHalfDuplex': 3, 'fourMbHalfDuplex': 1, 'sixteenMbFullDuplex': 4.

Data set by the user. It is ignored by the OSA.

Name of the port as used by TCP/IP

This field contains the active Group Addresses. An individual Group Address is 6 bytes long with an additional 2 bytes of padding.

A 4 byte OCTET STRING which contains the OSA-Express's functional address.

The current interface status which can be used to diagnose fluctuating problems that can occur on token rings after a station has successfully been added to the ring. Before an open is completed, this object has the value for the 'noStatusOpenNotCompleted' condition. The ibmOsaExpTRRingState and ibmOsaExpTRRingOpenStatus objects provide for debugging problems when the station can not even enter the ring. The object's value is a sum of values, one for each currently applicable condition. This information is essentially from RFC 1231. Bits: 'fourMbFullDuplex': 30, 'softError': 18, 'sRCounterOverflow': 27, 'autoRemovalError': 21, 'fourMbHalfDuplex': 31, 'reserved9': 9, 'reserved8': 8, 'reserved5': 5, 'reserved4': 4, 'reserved7': 7, 'reserved6': 6, 'reserved1': 1, 'reserved0': 0, 'reserved3': 3, 'reserved2': 2, 'hardError': 17, 'reserved15': 15, 'reserved11': 11, 'reserved10': 10, 'reserved13': 13, 'reserved12': 12, 'counterOverflow': 24, 'ringRecovery': 26, 'reserved19': 19, 'openInFDXmode': 29, 'singleStation': 25, 'lobeWireFault': 20, 'noStatusOpenNotCompleted': 14, 'removeReceived': 23, 'reserved29': 28, 'fdxProtocol': 22, 'signalLoss': 16.

This field contains the maximum token priority the ring station defined by this entry in the table is permitted to transmit.

Indicates if the ring station supports early token release. Only valid when port is running in 16Mb half duplex mode. Otherwise it is always set to false (1) Enumeration: 'false': 1, 'true': 0.

This field contains the node address of the NAUN as reported in the most recently received Beacon MAC frame. This field is valid when ibmOsaExpTRRingOpenStatus is set to beaconing. Otherwise it is ignored

The MAC-address of the up stream neighbor station in the ring (NAUN).

The current interface state with respect to entering or leaving the ring. Enumeration: 'ringFailure': 6, 'opened': 1, 'opening': 3, 'openFailure': 5, 'closed': 2, 'closing': 4.

This object indicates the success, or the reason for failure of the station's most recent attempt to enter the ring. Enumeration: 'insertionTimeout': 5, 'claimTokenRec': 13, 'ringFailed': 6, 'heartbeatFailDuringBeaconTest': 25, 'lobeMedizTestFailure': 23, 'noOpen': 1, 'standbyMonPresRec': 16, 'beaconBeforeOpen': 20, 'insertTimerExpDuringDAC': 21, 'open': 11, 'beaconing': 7, 'fDXInsDeniedDACfailOnOpen': 18, 'activeMonPresRec': 15, 'badParameter': 2, 'accessProtocolDenied': 17, 'fDXInsDeniedDACfailOnBeaconTest': 19, 'duplicateMAC': 8, 'sARecFrameNotEqualNAUNs': 12, 'requestFailed': 9, 'heartbeatFailBeforeOpenCompleted': 24, 'lobeFailed': 3, 'insertTimerExpDuringBeaconTest': 22, 'removeReceived': 10, 'ringPurgeFramRec': 14, 'recBeaconFrameWithInvalidSA': 26, 'signalLoss': 4.

This field contains the count of the total number of packets transmitted from this port since the OSA port was reset

This field contains the count of the total number of packets received by this port since the OSA port was reset

This counter is incremented when a frame or token is copied or repeated by a station, the E bit is zero in the frame or token and one of the following conditions exists: 1) there is a non-data bit (J or K bit) between the SD and the ED of the frame or token, or 2) there is an FCS error in the frame.

This counter is incremented when a station detects the absence of transitions for five half-bit timers (burst-five error).

This counter is incremented when a station receives an AMP or SMP frame in which A is equal to C is equal to 0, and then receives another SMP frame with A is equal to C is equal to 0 without first receiving an AMP frame. It denotes a station that cannot set the AC bits properly.

This counter is incremented when a station transmits an abort delimiter while transmitting.

This counter is incremented when a station recognizes an internal error.

This counter is incremented when a station is transmitting and its TRR timer expires. This condition denotes a condition transmitting station in strip mode does not receive the trailer of the frame TRR timer goes off.

This counter is incremented when a station recognizes a frame addressed to its specific address, but has no available buffer space indicating that the station is congested.

This counter is incremented when a station recognizes a frame addressed to its specific address and detects that the FS field A bits are set to 1 indicating a possible line hit or duplicate address.

This counter is incremented when a station acting as the active monitor recognizes an error condition that needs a token transmitted.

An error has been detected by the FDX protocol

The number of Soft Errors the interface has detected. It directly corresponds to the number of Report Error MAC frames that this interface has transmitted. Soft Errors are those which are recoverable by the MAC layer protocols.

The number of times this interface has detected an immediately recoverable fatal error. It denotes the number of times this interface is either transmitting or receiving beacon MAC frames.

The number of times this interface has detected the loss of signal condition from the ring.

The number of times this interface has transmitted a beacon frame.

The number of Claim Token MAC frames received or transmitted after the interface has received a frame Ring Ring Purge MAC counter signifies the number of times the ring has been purged and is being recovered back into a normal operating state.

The number of times the interface has detected an open or short circuit in the lobe data path. The adapter will be closed and ibmOsaExpTRRingState will signify this condition.

The number of times the interface has received a Remove Ring Station MAC frame request. When this frame is received the interface will enter the closed state and ibmOsaExpTRRingState will signify this condition.

The number of times the interface has sensed that it is the only station on the ring. This will happen if the interface is the first one up on a ring, or if there is a hardware problem.

This table represents the data associated with an emulated Ethernet port on an OSA-Express ATM feature. There are a maximum of 2 logical ports on each ATM feature, however, each port is shown as though it exists independently with each having an entry in the ibmOSAExpChannelTable.

Definition of a single entry in the ibmOSAExpATMPortTable. Indexed by the ifIndex of the corresponding Device interface.

The logical port number of this port

The logical port type. Enumeration: 'emulatedEthernet': 17.

The LAN state value ranges from 0 to 8. A value of 5, disabled is further explained in object ibmOsaExpATMDisabledStatus. Enumeration: 'disabled': 5, 'undefined': 0, 'configuredOffline': 8, 'enabled': 4, 'enabling': 2, 'definitionError': 7, 'linkMonitor': 6, 'disabling': 3, 'unavailable': 1.

This object indicates if the processor is in service mode or not. Enumeration: 'notInServiceMode': 0, 'inServiceMode': 1.

When the value of ibmOsaExpATMLanTrafficState is NOT disabled, the value of this object will be zero. When the value of ibmOsaExpATMLanTrafficState is disabled(5), this object explains the reason for the disabled state. The value for this object may be a combination of the bits shown. Bits: 'reserved15': 15, 'serviceProcessorRequest': 9, 'internalPortFailure': 1, 'portTemporarilyDisabled': 6, 'osasfRequest': 11, 'linkFailureThresholdExceeded': 13, 'configurationChange': 12, 'reserved14': 14, 'reserved8': 8, 'networkRequest': 10, 'reserved5': 5, 'reserved4': 4, 'reserved7': 7, 'reserved0': 0, 'reserved3': 3, 'reserved2': 2.

This is the name of the configuration that is on the OSA. It is set using OSA/SF. It is not used by OSA

A 6 byte OCTET STRING which contains the current MAC address in use on the OSA. The values are in canonical format.

A 6 byte OCTET STRING which contains the burned in MAC address on the OSA. The values are in canonical format.

Data set by the user. It is ignored by the OSA.

Name of the port as used by TCP/IP

This field contains the active Group Addresses. An individual Group Address is 6 bytes long with an additional 2 bytes of padding.

When set to Yes, this keeps data connections active when the connection to the LES is lost. Enumeration: 'yes': 1, 'no': 0.

Values range from 10-1550 and must be divided by 10 to get the proper value. A value of 1550 indicates 155.0 Mbytes/sec

Indicates whether this LAN Emulation Client should auto-configure the next time it is (re)started. In automatic (1) mode, a client uses a LAN Emulation Configuration Server to learn the ATM address of its LAN Emulation Server, and to obtain other parameters. lecConfig (LanType, MaxDataFrameSize, LanName) are used in the configure request. ibmOsaExpATMConfigLESATMAddress is ignored. In manual (2) mode, management tells the client the ATM address of its LAN Emulation Server and the value of the other parmeters. lecConfig (LanType, MaxDataFrameSize, LanName) are used in the Join request. ibmOsaExpATMConfigLESATMAddress tells the client which LES to call. Enumeration: 'manual': 2, 'automatic': 1.

The logical port type that the user configured the port for Enumeration: 'emulatedEthernet': 17.

The actual logical port type the port is running in Enumeration: 'emulatedEthernet': 17.

The maximum data frame size (in bytes) which this client will use the next time it returns to the Initial State. Auto-configuring clients use this parameter in their configure requests. Manually configured clients use it in their join requests. Enumeration: 'f4544': 3, 'f18190': 5, 'f1516': 2, 'unspecified': 1, 'f9234': 4.

The maximum data frame size (in bytes) which this client will use the next time it returns to the Initial State. Auto-configuring clients use this parameter in their configure requests. Manually configured clients use it in their join requests. Enumeration: 'f4544': 3, 'f18190': 5, 'f1516': 2, 'unspecified': 1, 'f9234': 4.

The ELAN Name this client will use the next time it returns to the Initial State. Auto-configuring clients use this parameter in their configure requests. Manually configured clients use it in their join requests.

The ELAN Name this client will use the next time it returns to the Initial State. Auto-configuring clients use this parameter in their configure requests. Manually configured clients use it in their join requests.

The LAN Emulation Server which this client will use the next time it is started in manual configuration mode. When ibmOsaExpATMConfigMode is 'automatic', there is no need to set this address, Address) and no advantage to doing so. The client will use the LECS to find a LES, putting the auto-configured address in ibmOsaExpATMActualLESATMAddress while leaving ibmOsaExpATMConfigLESATMAddress alone. Corresponds to Initial State Parameter C9. In LAN Emulation MIB, the OCTET STRING has length 0 or 20. For OSA, the length shall be 20, with the value 0 defined to mean that ibmOsaExpATMConfigMode is 'automatic'.

The LAN Emulation Server which this client will use the next time it is started in manual configuration mode. When lecConfigMode is 'automatic', there is no need to set this address, Address) and no advantage to doing so. The client will use the LECS to find a LES, putting the auto-configured address in ibmOsaExpATMActualLESATMAddress while leaving ibmOsaExpATMConfigLESATMAddress alone. Corresponds to Initial State Parameter C9. In LAN Emulation MIB, the OCTET STRING has length 0 or 20. For OSA, the length shall be 20, with the value 0 defined to mean that ibmOsaExpATMConfigMode is 'automatic'.

Control Time-out. Time out period used for timing out most request/response control frame interactions, as specified elsewhere in the LAN Emulation specification. This time value is expressed in seconds. Corresponds to Initial State Parameter C7.

Maximum Unknown Frame Count. See the description of ibmOsaExpATMMaxUnknownFrameTime below. Corresponds to Initial State Parameter C10.

Maximum Unknown Frame Time. Within the period of time defined by the Maximum Unknown Frame Time, a LE Client will send no more than Maximum Unknown Frame Count frames to the BUS for a given unicast LAN Destination, and it must also initiate the address resolution protocol to resolve that LAN Destination. This time value is expressed in seconds. Corresponds to Initial State Parameter C11.

VCC Time-out Period. A LE Client SHOULD release any Data Direct VCC that it has not used to transmit or receive any data frames for the length of the VCC Time-out Period. This parameter is only meaningful for SVC Data Direct VCCs. This time value is expressed in seconds. The default value is 20 minutes. A value of 0 seconds means that the timeout period is infinite. Negative values will be rejected by the agent. Corresponds to Initial State Parameter C12.

Maximum Retry Count. A LE CLient MUST not retry a LE_ARP_REQUEST for a given frame's LAN destination more than Maximum Retry Count times, after the first LE_ARP_REQUEST for that same frame's LAN destination. Corresponds to Initial State Parameter C13.

Aging Time. The maximum time that a LE Client will maintain an entry in its LE_ARP cache in the absence of a verification of that relationship. This time value is expressed in seconds. Corresponds to Initial State Parameter C17.

Forward Delay Time. The maximum time that a LE Client will maintain an entry for a non-local MAC address in its LE_ARP cache in the absence of a verification of that relationship, as long as the Topology Change flag C19 is true. ibmOsaExpATMForwardDelayTime SHOULD BE less than ibmOsaExpATMAgingTIme. When it is not, ibmOsaExpATMAgingTime governs LE_ARP aging. This time value is expressed in seconds. Corresponds to Initial State Parameter C18.

Expected LE_ARP Reponse Time. The maximum time that the LEC expects an LE_ARP_REQUEST/LE_ARP_RESPONSE cycle to take. Used for retries and verifies. This time value is expressed in seconds. Corresponds to Initial State Parameter C20.

Flush Time-out. Time limit to wait to receive a LE_FLUSH_RESPONSE after the LE_FLUSH_REQUEST has been sent before taking recovery action. This time value is expressed in seconds. Corresponds to Initial State Parameter C21.

Path Switching Delay. The time since sending a frame to the BUS after which the LE Client may assume that the frame has been either discarded or delivered to the recipient. May be used to bypass the Flush protocol. This time value is expressed in seconds. Corresponds to Initial State Parameter C22.

Local Segment ID. The segment ID of the emulated LAN. This is only required for IEEE 802.5 clients that are Source Routing bridges. Corresponds to Initial State Parameter C23.

Multicast Send VCC Type. Signalling parameter that SHOULD be used by the LE Client when establishing the Multicast Send VCC. This is the method to be used by the LE Client when specifying traffic parameters when it sets up the Multicast Send VCC for this emulated LAN. Corresponds to Initial State Parameter C24. Enumeration: 'constantBitRate': 3, 'variableBitRate': 2, 'bestEffort': 1.

Multicast Send VCC AvgRate. Signalling parameter that SHOULD be used by the LE Client when estabishing the Multicast Send VCC. Forward and Backward Sustained Cell Rate to be requested by LE Client when setting up Multicast Send VCC, if using Variable bit rate codings. Corresponds to Initial State Parameter C25.

Multicast Send VCC PeakRate. Signalling parameter that SHOULD be used by the LE Client when establishing the Multicast Send VCC. Forward and Backward Peak Cell Rate to be requested by LE Client when setting up the Multicast Send VCC when using either Variable or Constant bit rate codings. Corresponds to Initial State Parameter C26.

Connection Complete Timer. Optional. In Connection Establish ment this is the time period in which data or a READY_IND message is expected from a Calling Party. This time value is expressed in seconds. Corresponds to Initial State Parameter C28.

LE Client's ATM Addresses. The primary ATM address of this LAN Emulation Client. This address is used to establish the Control Direct and Multicast Send VCCs, and may also be used to set up Data Direct VCCs. A client may have additional ATM addresses for use with Data Direct VCCs. Corresponds to Initial State Parameter C1.

LE Client Identifier. Each LE Client requires a LE Client Identifier (LECID) assigned by the LE Server during the Join phase. The LECID is placed in control requests by the LE Client and MAY be used for echo suppression on multicast data frames sent by that LE Client. This value MUST NOT change without terminating the LE Client and returning to the Initial state. A valid LECID MUST be in the range X'0001' through X'FEFF'. The value of this object is only meaningful for a LEC that is connected to a LES. For a LEC which does not belong to an emulated LAN, the value of this object is defined to be 0. Corresponds to Initial State Parameter C14.

The current state of the LAN Emulation Client. Note that 'ifOperStatus' is defined to be 'up' when, and only when, this field is 'operational'. Enumeration: 'join': 4, 'configure': 3, 'busConnect': 6, 'initialState': 1, 'lecsConnect': 2, 'initialRegistration': 5, 'operational': 7.

Status code from the last failed Configure response or Join response. Failed responses are those for which the LE_CONFIGURE_RESPONSE / LE_JOIN_RESPONSE frame contains a non-zero code, or fails to arrive within a timeout period. If none of this client's requests have failed, this object has the value 'none'. If the failed response contained a STATUS code that is not defined in the LAN Emulation specification, this object has the value 'undefinedError'. The value 'timeout' is self explanatory. Other failure codes correspond to those defined in the specification, although they may have different numeric values. Enumeration: 'invalidRequestParameters': 5, 'none': 1, 'leConfigureError': 14, 'insufficientInformation': 15, 'versionNotSupported': 4, 'noConfiguration': 13, 'duplicateLanDestination': 6, 'invalidAtmAddress': 12, 'insufficientResources': 8, 'duplicateAtmAddress': 7, 'timeout': 2, 'undefinedError': 3, 'invalidRequesterId': 10, 'invalidLanDestination': 11, 'accessDenied': 9.

The state this client was in when it updated the 'ibmOsaExpATMLastFailureRespCode'. If 'ibmOsaExpATMLastFailureRespCode' is 'none', this object has the value initialState(1). Enumeration: 'join': 4, 'configure': 3, 'busConnect': 6, 'initialState': 1, 'lecsConnect': 2, 'initialRegistration': 5, 'operational': 7.

The LAN Emulation protocol which this client supports, and specifies in its LE_JOIN_REQUESTs.

The LAN Emulation protocol version which this client supports, and specifies in its LE_JOIN_REQUESTs.

Topology Change. Boolean indication that the LE Client is using the Forward Delay Time C18, instead of the Aging Time C17, to age non-local entries in its LE_ARP cache C16. For a client which is not connected to the LES, this object is defined to have the value 'false'. Corresponds to Initial State Parameter C19. Enumeration: 'false': 2, 'true': 1.

The ATM address of the LAN Emulation Configuration Server (if known) or 0 (otherwise). In LAN Emulation MIB, the OCTET STRING is either 0 length or 20 octets. For OSA-ATM, this Address has been changed to a constant 20 octets, with the value 0 equivalent to the 0 length OCTET STRING.

Indicates whether this LAN Emulation Client used the LAN Emulation Configuration Server, and, if so, what method it used to establish the Configuration Direct VCC Enumeration: 'didNotUseLecs': 4, 'gotAddressViaIlmi': 1, 'usedWellKnownAddress': 2, 'usedLecsPvc': 3.

Indicates whether this client is acting as a proxy. Proxy clients are allowed to represent unregistered MAC addresses, and receive copies of LE_ARP_REQUEST frames for such addresses. Corresponds to Initial State Parameter C4. Enumeration: 'false': 2, 'true': 1.

The number of Le PDU Octets received

The number of Non Error Le PDU Octets received

The number of Errored Le PDU Discards received

The number of Le PDU Discards sent

The number of Non Error Le PDU Discards sent

The number of Errored Le PDU Discards sent

The number of LE ARP Requests sent

The number of LE ARP Requests received over the LUNI by this LAN Emulation Client. Requests may arrive on the Control Direct VCC or on the Control Distribute VCC, depending upon how the LES is implemented and the chances it has had for learning. This counter covers both VCCs.

The number of LE ARP Responses sent over the LUNI by this LAN Emulation Client.

The number of LE ARP Responses received over the LUNI by this LAN Emulation Client. This count includes all such replies, whether solicited or not. Replies may arrive on the Control Direct VCC or on the Control Distribute VCC, depending upon how the LES is implemented. This counter covers both VCCs.

The total number of control packets sent by this LAN Emulation Client over the LUNI.

The total number of control packets received by this LAN Emulation Client over the LUNI.

The total number of outgoing LAN Emulation SVCs which this client tried, but failed, to open; incoming LAN Emulation SVCs which this client tried, but failed to establish; and incoming LAN Emulation SVCs which this client rejected for protocol or security reasons.

The interface associated with the Configuration Direct VCC. If no Configuration Direct VCC exists, this object has the value 0. Otherwise, the objects ( ibmOsaExpATMConfigDirectIntfc, ibmOsaExpATMConfigDirectVPI, ibmOsaExpATMConfigDirectVCI) identify the circuit.

If the Configuration Direct VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Configuration Direct VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

The interface associated with the Control Direct VCC. If no Control Direct VCC exists, this object has the value 0. Otherwise, the objects ( ibmOsaExpATMConfigDirectIntfc, ibmOsaExpATMConfigDirectVPI, ibmOsaExpATMConfigDirectVCI) identify the circuit.

If the Control Direct VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Control Direct VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

The interface associated with the Control Distribute VCC. If no Control Distribute VCC has been set up to this client, this object has the value 0. Otherwise, the objects ( ibmOsaExpATMControlDistIntfc, ibmOsaExpATMControlDistributeVPI. ibmOsaExpATMControlDistributeVCI) identify the circuit.

If the Control Distribute VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Control Distribute VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object contains the value 0.

The interface associated with the Multicast Send VCC. If no Multicast Send VCC exists, this object has the value 0. Otherwise, the objects ( ibmOsaExpATMMulticastSendIntfc, ibmOsaExpATMMulticastSendVPI, ibmOsaExpATMMulticastSendVCI) identify the circuit.

If the Multicast Send VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Multicast Send VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

The interface associated with the Multicast Forward VCC. If no Multicast Forward VCC has been set up to this client, this object has the value 0. Otherwise, the objects ( ibmOsaExpATMMulticastFwdIntfc, ibmOsaExpATMMulticastForwardVPI, ibmOsaExpATMMulticastForwardVCI) identify the circuit.

If the Multicast Forward VCC exists, this object contains the VPI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

If the Multicast Forward VCC exists, this object contains the VCI which identifies that VCC at the point where it connects to this LE client. Otherwise, this object has the value 0.

The compliance statement for the OSA DIrect SNMP product.

This group comprises those objects that are related to OSA-Express Channel support.

This group comprises those objects that are related to OSA-Express Performance data support.

This group comprises those objects that are related to OSA-Express PE data support.

This group comprises those objects that are related to OSA-Express Fast Ethernet and Gigabit features only

This group comprises those objects that are related to OSA-Express Token Ring feature only

This group comprises those objects that are related to OSA-Express ATM LAN Emulation feature only