MEF-SOAM-TC-MIB

TEXTUAL-CONVENTION

This enumeration data type defines the availability of a session, measured by a loss measurement session. The valid enumerated values associated with this type are: available(1) indicates the MEP is available. unavailable(2) indicates the MEP is unavailable. unknown(3) indicates the availability is not known, for instance because insufficient time has passed to make an availability calculation, the time has been excluded because of a maintenance interval, or because availability measurement is not enabled.

TEXTUAL-CONVENTION

This enumeration data type defines the connectivity status of a Maintenance Entity (ME) or a Maintenance Entity Group (MEG). The valid enumerated values associated with this type are: inactive(1) indicates an inactive connectivity state of a group and refers to the inability to exchange SOAM PDU frame among any of the entities in a group. active(2) indicates an active connectivity state of a group and refers to the ability to exchange SOAM PDU frames among all the entities in a group partiallyActive(3) indicates a partially active connectivity state of a group and refers to the ability to exchange SOAM PDU frames among some entities of a group. This enumerated value is only applicable for Multipoint-to-Multipoint MEG.

TEXTUAL-CONVENTION

This enumeration data type indicates the type of data pattern to be sent in an OAM PDU Data TLV. The valid enumerated values associated with this type are: zeroPattern(1) indicates the Data TLV contains all zeros onesPattern(2) indicates the Data TLV contains all ones

TEXTUAL-CONVENTION

This enumeration data type is used to distinguish between measurement bins for Frame Delay, Frame Delay Range, and Inter-frame Delay variation. The valid enumerated values associated with this type are: twoWayFrameDelay(1) indicates a measurement bin for two-way Frame Delay. forwardFrameDelay(2) indicates a measurement bin for one-way Frame Delay in the forward direction. backwardFrameDelay(3) indicates a measurement bin for one-way Frame Delay in the backward direction. twoWayIfdv(4) indicates a measurement bin for two-way Inter-frame Delay Variation. forwardIfdv(5) indicates a measurement bin for one-way Inter-frame Delay Variation in the forward direction. backwardIfdv(6) indicates a measurement bin for one-way Inter-frame Delay Variation in the backward direction. twoWayFrameDelayRange(7) indicates a measurement bin for two-way Frame Delay Range. forwardFrameDelayRange(8) indicates a measurement bin for one-way Frame Delay Range in the forward direction. backwardFrameDelayRange(9) indicates a measurement bin for one-way Frame Delay Range in the backward direction.

TEXTUAL-CONVENTION

This enumeration data type defines the AIS/LCK transmission time interval for an Alarm Indication Signal (AIS) or LCK frame. The valid enumerated values associated with this type are: oneSecond(1) indicates a one second transmission interval. oneMinute(2) indicates a one minute transmission interval.

TEXTUAL-CONVENTION

Indicates the transmission time between the SOAM PM frames for a PM session, in ms.

TEXTUAL-CONVENTION

This enumeration data type indicates the format of the MEG ID that is sent in the OAM PDUs. Types 1-4 are more fully explained in [CFM] 17.5. Type 32 is from [Y.1731] Annex A. The valid enumerated values associated with this type are: primaryVid(1) Primary VLAN ID. 12 bits represented in a 2-octet integer: - 4 least significant bits of the first byte contains the 4 most significant bits of the 12 bits primary VID - second byte contains the 8 least significant bits of the primary VID 0 1 2 3 4 5 6 7 8 +-+-+-+-+-+-+-+-+ |0 0 0 0| (MSB) | +-+-+-+-+-+-+-+-+ | VID LSB | +-+-+-+-+-+-+-+-+ charString(2) RFC2579 DisplayString, except that the character codes 0-31 (decimal) are not used. (1..45) octets unsignedInt16 (3) 2-octet integer/big endian rfc2865VpnId(4) RFC 2685 VPN ID 3 octet VPN authority Organizationally Unique Identifier followed by 4 octet VPN index identifying VPN according to the OUI: 0 1 2 3 4 5 6 7 8 +-+-+-+-+-+-+-+-+ | VPN OUI (MSB) | +-+-+-+-+-+-+-+-+ | VPN OUI | +-+-+-+-+-+-+-+-+ | VPN OUI (LSB) | +-+-+-+-+-+-+-+-+ |VPN Index (MSB)| +-+-+-+-+-+-+-+-+ | VPN Index | +-+-+-+-+-+-+-+-+ | VPN Index | +-+-+-+-+-+-+-+-+ |VPN Index (LSB)| +-+-+-+-+-+-+-+-+ iccBased (32) ICC-based MEG ID Format, thirteen octet field

TEXTUAL-CONVENTION

This enumeration data type indicates the operation type start or end time to indicate when an OAM operation is initiated or stopped. The valid enumerated values associated with this type are: none(1) The operation is never started or is stopped immediately if used to indicate a start time, or the operation never ends if it is used to indicate an end time immediate(2) The operation is to begin immediately relative(3) The operation is to begin at a relative time from the current time or stop a relative time after it has started fixed(4) The operation is to begin/stop at the given UTC time/date

TEXTUAL-CONVENTION

This enumeration data type defines the status of PM session of a MEP. The valid enumerated values associated with this type are: proactive(1) indicates the measurement instance is Proactive onDemand(2) indicates the measurement instance is On-demand

TEXTUAL-CONVENTION

This enumeration data type defines the status of PM session of a MEP. The valid enumerated values associated with this type are: active(1) indicates the measurement instance is active notActive(2) indicates the measurement instance is not active

TEXTUAL-CONVENTION

This enumeration data type indicates the type of test pattern to be sent in an OAM PDU Test TLV. The valid enumerated values associated with this type are: null(1) Null signal without CRC-32 nullCrc32(2) Null signal with CRC-32 prbs(3) PRBS 2^31-1 without CRC-32 prbsCrc32(4) PRBS 2^31-1 with CRC-32