G9983-MIB

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

A desired state of the OPTIONAL Forward Error Correction (FEC) function of the G.Bond/TDIM port. A value of 'false' indicates that the FEC function SHALL be disabled. A value of 'true' indicates that the FEC function SHALL be enabled, if supported by the G.Bond/TDIM port, as indicated by the g9983PortCapFecSupported object. The g9983PortStatFecOperState object indicates the current operational state of the FEC function. For the GBS-R ports, the value of this object cannot be changed directly. This value may be changed as a result of a write operation on the g9983PortCapFecSupported object of a remote GBS-C. Modifications of this object MUST be performed when the link is 'down'. Attempts to change this object MUST be rejected if the link is 'up' or initializing, or if it is a GBS-R. This object maps to the TR-159/G.998.3 attribute aFECAdminState. ⓘ

Unsigned32 (0 | 20..255) · octets

A FEC code word size, in octets, for G.Bond/TDIM ports supporting the FEC function. This object is read-write for the GBS-C ports and read-only for the GBS-R. A value of zero SHALL be returned if the FEC function is disabled (via g9983PortConfFecAdminState) or not supported. Changing of the FEC code word size MUST be performed when the FEC-enabled link is 'down'. Attempts to change this object MUST be rejected if the link is 'up' or initializing or if the FEC function is disabled/not supported. This object maps to the TR-159/G.998.3 attribute aFECWordSize. ⓘ

Unsigned32 (0 | 2 | 4 | 8 | 16 | 20) · octets

A FEC redundancy word size, in octets, for G.Bond/TDIM ports supporting the FEC function. This object is read-write for the GBS-C ports and read-only for the GBS-R. A value of zero SHALL be returned if the FEC function is disabled (via g9983PortConfFecAdminState) or not supported. Changing of the FEC redundancy word size MUST be performed when the FEC-enabled link is 'down'. Attempts to change this object MUST be rejected if the link is 'up' or initializing or if the FEC function is disabled/not supported. This object maps to the TR-159/G.998.3 attribute aFECRedundancySize. ⓘ

INTEGER0 = none1 = block2 = convolution · Integer32

An Interleaver type for G.Bond/TDIM ports supporting the FEC function. This object is read-write for the GBS-C ports and read-only for the GBS-R. A value of none(0) SHALL be returned if the FEC function is disabled (via g9983PortConfFecAdminState) or not supported. Changing of the Interleaver type MUST be performed when the FEC-enabled link is 'down'. Attempts to change this object MUST be rejected if the link is 'up' or initializing or if the FEC function is disabled/not supported. This object maps to the TR-159/G.998.3 attribute aFECInterleaverType. ⓘ

Unsigned32 (0 | 1 | 2 | 3 | 4 | 6 | 8 | 12 | 16 | 24 | 32 | 48 | 96)

An Interleaver depth for G.Bond/TDIM ports supporting the FEC function. This object is read-write for the GBS-C ports and read-only for the GBS-R. A value of zero SHALL be returned if the FEC function is disabled (via g9983PortConfFecAdminState) or not supported. Changing of the Interleaver depth MUST be performed when the FEC-enabled link is 'down'. Attempts to change this object MUST be rejected if the link is 'up' or initializing or if the FEC function is disabled/not supported. This object maps to the TR-159/G.998.3 attribute aFECInterleaverDepth. ⓘ

G9983SvcIndexListThis textual convention represents a continuous ordered list of all the services defined for the managed G.Bond/TDIM port. The value of this object is a concatenation of zero or more (up to 60) octets, where each octet contains an 8-bit G9983SvcIndex value, identifying a particular service. An octet's position reflects the associated service position and its priority in the G.Bond/TDIM frame, with the first octet being the first service of highest priority. A zero-length octet string is object-specific and MUST therefore be defined as part of the description of any object that uses this syntax. Examples of the usage of a zero-length value might include situations where an object using this textual convention is irrelevant for a specific G.Bond/TDIM port type or where no services have been defined for this port. SIZE (0..60) · OCTET STRING · hint 1d:

Desired list of services for a G.Bond/TDIM port. This object is a list of pointers to entries in the g9983SvcTable. The value of this object is a continuous ordered list of up to 60 indices (g9983SvcIdx) of the active services carried via the G.Bond/TDIM link. The position of a service in the list determines its relative priority in cases of bandwidth degradation -- the priority decreases towards the end of the list, which means that the last service in the list would be suspended first when the bandwidth degrades. This object is writable and readable for the GBS-C ports. It is irrelevant for the GBS-R ports -- a zero-length octet string SHALL be returned on an attempt to read this object, and an attempt to change this object MUST be rejected in this case. Note that the current operational service list is available via the g9983OperSvcTable object. This object for a GBS-C port MAY be modified independently of the link's state, i.e., in-service and out-of-service. Attempts to set this object to a list with a member value that is not the value of the index for an active entry in the corresponding g9983SvcTable table MUST be rejected. ⓘ

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Indicates whether g9983SvcUp and g9983SvcDown notifications should be generated for this interface. A value of true(1) indicates that the notifications are enabled. A value of false(2) indicates that the notifications are disabled. This object maps to the TR-159 attribute aServiceUpDownEnable. ⓘ

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

FEC and Interleaver capability of the G.Bond/TDIM port. This object has a value of true(1) when the port supports the FEC and Interleaver function. A value of false(2) is returned when the port does not support the FEC and Interleaver function. This object maps to the TR-159/G.998.3 attribute aFECSupported. ⓘ

Unsigned32 (0 | 20..255) · octets

A maximum supported FEC code word size, in octets, for G.Bond/TDIM ports supporting the FEC function. A value of zero SHALL be returned if the FEC function is not supported. This object maps to the TR-159 attribute aFECWordSize. ⓘ

Unsigned32 (0 | 2 | 4 | 8 | 16 | 20) · octets

A maximum supported FEC redundancy word size, in octets, for G.Bond/TDIM ports supporting the FEC function. A value of zero SHALL be returned if the FEC function is not supported. This object maps to the TR-159 attribute aFECMaxRedundancySize. ⓘ

INTEGER0 = none1 = block2 = convolution3 = blockConvolution · Integer32

Supported Interleaver types for G.Bond/TDIM ports supporting the FEC function. Possible values are: none - the port does not support interleaving block - the port supports Block Interleaver convolution - the port supports Convolution Interleaver blockConvolution - the port supports both Block Interleaver and Convolution Interleaver This object maps to the TR-159 attribute aFECInterleaverTypesSupported. ⓘ

Unsigned32 (0 | 1 | 2 | 3 | 4 | 6 | 8 | 12 | 16 | 24 | 32 | 48 | 96)

A maximum Interleaver depth for G.Bond/TDIM ports supporting the FEC function. A value of zero SHALL be returned if the Interleaver is not supported. This object maps to the TR-159 attribute aFECMaxInterleaverDepth. ⓘ

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

A read-only value indicating the current operational state of the OPTIONAL Forward Error Correction (FEC) function for the G.998.3 port. A value of 'false' indicates that the FEC function is disabled. A value of 'true' indicates that the FEC function is enabled (and supported). This object maps to the TR-159 attribute aFECOperState. ⓘ

BITS

G.Bond/TDIM port fault status. This is a bitmap of possible conditions. The various bit positions are: serviceDown - at least one of the services defined for this aggregation group is down (due to low rate). wrongConfig - at least one BCE at the remote GBS-R is already connected to another GBS. This object is intended to supplement the ifOperStatus object in the IF-MIB and the gBondPortStatFltStatus object in the GBOND-MIB. ⓘ

Counter32

The total number of CRC-4 errors (frame header errors) on all pairs in the G.Bond/TDIM port. Simultaneous errors on M lines SHOULD be counted M times. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime as defined in the IF-MIB. This object maps to the TR-159/G.998.3 attribute aCRC4Errors. ⓘ

Counter32

The total number of CRC-6 errors (super-frame errors) on all pairs in the G.Bond/TDIM port. Simultaneous errors on M lines SHOULD be counted 1 time. Discontinuities in the value of this counter can occur at re-initialization of the local management subsystem, and at other times as indicated by the value of ifCounterDiscontinuityTime as defined in the IF-MIB. This object maps to the TR-159/G.998.3 attribute aCRC6Errors. ⓘ

Counter32

The total number of CRC-8 errors (event/message errors) on all pairs in the G.Bond/TDIM port. Simultaneous errors on M lines SHOULD be counted M times. Discontinuities in the value of this counter can occur at re-initialization of the local management subsystem, and at other times as indicated by the value of ifCounterDiscontinuityTime as defined in the IF-MIB. This object maps to the TR-159/G.998.3 attribute aCRC8Errors. ⓘ

G9983SvcOrderIndexA unique value, greater than zero, for each service defined in the managed G.Bond/TDIM port, showing its relative position inside the G.Bond/TDIM frame. (1..60) · Unsigned32 · hint d

G.Bond/TDIM operational service position -- a unique index, indicating relative placement of the associated service pointed to by g9983OperSvcIdx, within the G.Bond/TDIM frame. There can be up to 60 services defined over a TDIM bonded facility. Services with lower indices have higher priority in cases of bandwidth degradation. The value of g9983OperSvcPosition for the first g9983OperSvcEntry is always 1, incrementing sequentially for each consecutive entry, i.e., 2 for the second entry, 3 for the third, etc. This objects maps to the TR-159/G.998.3 attribute aServiceID. ⓘ

G9983SvcIndexA unique value, greater than zero, for each service defined in the managed G.Bond/TDIM port. It is RECOMMENDED that values be assigned contiguously starting from 1. The value for each service MUST remain constant at least from one re-initialization of the local management subsystem to the next re-initialization. (1..255) · Unsigned32 · hint d

G.Bond/TDIM operational service index -- a read-only pointer to an existing entry in the g9983SvcTable (value of g9983SvcIdx) describing a particular service.

INTEGER1 = up2 = down · Integer32

G.Bond/TDIM service operational state. Possible values are: up - Service is up and passing traffic. down - Service is down, due to a variety of reasons, e.g., G.Bond/TDIM port is down, current link bandwidth is too low to support a particular service, etc. This objects maps to the TR-159 attribute aServiceOperState. ⓘ

G9983SvcIndexA unique value, greater than zero, for each service defined in the managed G.Bond/TDIM port. It is RECOMMENDED that values be assigned contiguously starting from 1. The value for each service MUST remain constant at least from one re-initialization of the local management subsystem to the next re-initialization. (1..255) · Unsigned32 · hint d

G.Bond/TDIM service index -- a unique index associated with a particular service entry.

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

This is a unique index within the ifTable. It represents the interface index of a service to be transmitted over the G.Bond/TDIM service instance. This objects maps to the TR-159 attribute aServiceIfIndex. ⓘ

INTEGER0 = ds11 = e12 = nxds03 = nxe04 = ds35 = e36 = clock7 = ethernet8 = atm9 = gfpNoFCS10 = gfp · Integer32

G.Bond/TDIM service type. Possible values are: ds1 - Clear Channel DS1 (synchronous) e1 - Clear Channel E1 (synchronous) nxds0 - Fractional DS1 (synchronous) nxe0 - Fractional E1 (synchronous) ds3 - DS3 (synchronous) e3 - E3 (synchronous) clock - Clock transfer (synchronous) ethernet - Ethernet (asynchronous) atm - ATM (asynchronous) gfpNoFCS - GFP encapsulated without FCS (asynchronous) gfp - GFP encapsulated with FCS (asynchronous) For the GBS-R ports, the value of this object cannot be changed directly. This value may be changed as a result of a write operation on the g9983SvcType object of a remote GBS-C. Attempts to change this object MUST be rejected for the GBS-R ports. This object maps to the TR-159/G.998.3 attribute aServiceType. ⓘ

Unsigned32 (0 | 20..255) · octets

Service size, in octets, per bonding sub-block for a specific service identified by g9983SvcIdx. For TDM (synchronous) services with variable size (e.g., fractional DS1/E1), this object represents the number of DS0/E0 channels. For asynchronous services (Ethernet, ATM, GFPnoFCS, or GFP), this object represents the maximum number of octets. For non-fractional TDM services (i.e., DS1, E1, DS3, E3, and clock), the value of this object MUST be 0. A GET operation returns the current value. A SET operation, allowed on GBS-C ports, changes the service size to the indicated value. If the service type is a fixed-rate synchronous service (g9983SvcType is nxds0, nxe0, ds1, e1, ds3, e3, or clock), the operation MUST be rejected. This object maps to the TR-159/G.998.3 attribute aServiceSize. ⓘ

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

This object controls the creation, modification, or deletion of the associated entry in the g9983SvcTable per the semantics of RowStatus. If an 'active' entry is referenced via g9983OperSvcIdx or a g9983PortConfAdminServices instance, or indexes a g9983SvcPm*Entry, the entry MUST remain 'active'. An 'active' entry SHALL NOT be modified. In order to modify an existing entry, it MUST be taken out of service (by setting this object to 'notInService'), modified, and set to 'active' again.

HCPerfValidIntervalsThe number of near end intervals for which data was collected. The value of an object with an HCPerfValidIntervals syntax will be 96 unless the measurement was (re-)started within the last 1440 minutes, in which case the value will be the number of complete 15 minute intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy) it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available. (0..96) · Integer32

A read-only number of 15-minute intervals for which the performance data was collected. The value of this object will be 96 or the maximum number of 15-minute history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 15-minute intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available. This object partially maps to the TR-159 attribute aGroupPerf15MinValidIntervals. ⓘ

HCPerfInvalidIntervalsThe number of near end intervals for which no data is available. The value of an object with an HCPerfInvalidIntervals syntax will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations). (0..96) · Integer32

A read-only number of 15-minute intervals for which the performance data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available. This object partially maps to the TR-159 attribute aGroupPerf15MinInvalidIntervals. ⓘ

HCPerfTimeElapsedThe number of seconds that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock or the addition of a leap second, the duration of the current interval exceeds the maximum value, the agent will return the maximum value. For 15 minute intervals, the range is limited to (0..899). For 24 hour intervals, the range is limited to (0..86399). (0..86399) · Integer32 · seconds

A read-only count of seconds that have elapsed since the beginning of the current 15-minute performance interval. This object partially maps to the TR-159 attribute aGroupPerfCurr15MinTimeElapsed. ⓘ

HCPerfCurrentCountA gauge associated with a performance measurement in a current 15 minute measurement interval. The value of an object with an HCPerfCurrentCount syntax starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the gauge is stored in the first 15 minute history interval, and the gauge is restarted at zero. In the case where the agent has no valid data available for the current interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfCurrentCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the object's value also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64

A read-only count of CRC-4 errors (frame header errors) on all active pairs in the G.Bond/TDIM port during the current 15-minute performance interval. Simultaneous errors on M lines SHOULD be counted M times. Note that the total number of CRC-4 errors is indicated by the g9983PortStatCrc4Errors object. This object is inhibited during Severely Errored Seconds (SES) or Unavailable Seconds (UAS). ⓘ

HCPerfCurrentCountA gauge associated with a performance measurement in a current 15 minute measurement interval. The value of an object with an HCPerfCurrentCount syntax starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the gauge is stored in the first 15 minute history interval, and the gauge is restarted at zero. In the case where the agent has no valid data available for the current interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfCurrentCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the object's value also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64

A read-only count of CRC-6 errors (super-frame errors) on all active pairs in the G.Bond/TDIM port during the current 15-minute performance interval. Simultaneous errors on M lines SHOULD be counted 1 time. Note that the total number of CRC-6 errors is indicated by the g9983PortStatCrc6Errors object. This object is inhibited during Unavailable Seconds (UAS). ⓘ

HCPerfCurrentCountA gauge associated with a performance measurement in a current 15 minute measurement interval. The value of an object with an HCPerfCurrentCount syntax starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the gauge is stored in the first 15 minute history interval, and the gauge is restarted at zero. In the case where the agent has no valid data available for the current interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfCurrentCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the object's value also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64

A read-only count of CRC-8 errors (event/message errors) on all active pairs in the G.Bond/TDIM port during the current 15-minute performance interval. Simultaneous errors on M lines SHOULD be counted M times. Note that the total number of CRC-8 errors is indicated by the g9983PortStatCrc8Errors object. This object is inhibited during Unavailable Seconds (UAS). ⓘ

Unsigned32 (0..7)

A read-only number of 1-day intervals for which data was collected. The value of this object will be 7 or the maximum number of 1-day history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 1-day intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available. ⓘ

Unsigned32 (0..7)

A read-only number of 1-day intervals for which data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available. ⓘ

HCPerfTimeElapsedThe number of seconds that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock or the addition of a leap second, the duration of the current interval exceeds the maximum value, the agent will return the maximum value. For 15 minute intervals, the range is limited to (0..899). For 24 hour intervals, the range is limited to (0..86399). (0..86399) · Integer32 · seconds

A read-only count of seconds that have elapsed since the beginning of the current 1-day performance interval. ⓘ

HCPerfCurrentCountA gauge associated with a performance measurement in a current 15 minute measurement interval. The value of an object with an HCPerfCurrentCount syntax starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the gauge is stored in the first 15 minute history interval, and the gauge is restarted at zero. In the case where the agent has no valid data available for the current interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfCurrentCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the object's value also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64

A read-only count of CRC-4 errors on the G.Bond/TDIM port in the current 1-day performance interval. This object is inhibited during Severely Errored Seconds (SES) and Unavailable Seconds (UAS).

HCPerfCurrentCountA gauge associated with a performance measurement in a current 15 minute measurement interval. The value of an object with an HCPerfCurrentCount syntax starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the gauge is stored in the first 15 minute history interval, and the gauge is restarted at zero. In the case where the agent has no valid data available for the current interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfCurrentCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the object's value also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64

A read-only count of CRC-6 errors on the G.Bond/TDIM port in the current 1-day performance interval. This object is inhibited during Unavailable Seconds (UAS).

HCPerfCurrentCountA gauge associated with a performance measurement in a current 15 minute measurement interval. The value of an object with an HCPerfCurrentCount syntax starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the gauge is stored in the first 15 minute history interval, and the gauge is restarted at zero. In the case where the agent has no valid data available for the current interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfCurrentCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the object's value also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64

A read-only count of CRC-8 errors on the G.Bond/TDIM port in the current 1-day performance interval. This object is inhibited during Unavailable Seconds (UAS).

Unsigned32 (1..96)

Performance data interval number. 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are OPTIONAL. This object partially maps to the TR-159 attribute aGroupPerf15MinIntervalNumber. ⓘ

HCPerfTimeElapsedThe number of seconds that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock or the addition of a leap second, the duration of the current interval exceeds the maximum value, the agent will return the maximum value. For 15 minute intervals, the range is limited to (0..899). For 24 hour intervals, the range is limited to (0..86399). (0..86399) · Integer32 · seconds

A read-only count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (900 seconds), except in a situation where performance data could not be collected for any reason.

HCPerfIntervalCountA gauge associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. Let X be an object with HCPerfIntervalCount syntax. Let Y be an object with HCPerfCurrentCount syntax. Let Z be an object with HCPerfTotalCount syntax. Then, in a system supporting a history of n intervals with X(1) and X(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of X(n) - the value of X(i) becomes that of X(i-1) for n >= i > 1 - the value of X(1) becomes that of Y. - the value of Z, if supported, is adjusted. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfIntervalCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the value of the object also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64

A read-only count of CRC-4 errors on the G.Bond/TDIM port during the 15-minute performance history interval. This object is inhibited during Severely Errored Seconds (SES) and Unavailable Seconds (UAS).

HCPerfIntervalCountA gauge associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. Let X be an object with HCPerfIntervalCount syntax. Let Y be an object with HCPerfCurrentCount syntax. Let Z be an object with HCPerfTotalCount syntax. Then, in a system supporting a history of n intervals with X(1) and X(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of X(n) - the value of X(i) becomes that of X(i-1) for n >= i > 1 - the value of X(1) becomes that of Y. - the value of Z, if supported, is adjusted. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfIntervalCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the value of the object also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64

A read-only count of CRC-6 errors on the G.Bond/TDIM port during the 15-minute performance history interval. This object is inhibited during Unavailable Seconds (UAS).

HCPerfIntervalCountA gauge associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. Let X be an object with HCPerfIntervalCount syntax. Let Y be an object with HCPerfCurrentCount syntax. Let Z be an object with HCPerfTotalCount syntax. Then, in a system supporting a history of n intervals with X(1) and X(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of X(n) - the value of X(i) becomes that of X(i-1) for n >= i > 1 - the value of X(1) becomes that of Y. - the value of Z, if supported, is adjusted. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfIntervalCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the value of the object also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64

A read-only count of CRC-8 errors on the G.Bond/TDIM port during the current 15-minute performance interval. This object is inhibited during Unavailable Seconds (UAS).

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU-C MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database. This object partially maps to the TR-159 attribute aGroupPerf15MinIntervalValid. ⓘ

Unsigned32 (1..7)

Performance data interval number. 1 is the most recent previous interval; interval 7 is 7 days ago. Intervals 2..7 are OPTIONAL. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalNumber. ⓘ

HCPerfTimeElapsedThe number of seconds that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock or the addition of a leap second, the duration of the current interval exceeds the maximum value, the agent will return the maximum value. For 15 minute intervals, the range is limited to (0..899). For 24 hour intervals, the range is limited to (0..86399). (0..86399) · Integer32 · seconds

A read-only count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (86400 seconds), except in a situation where performance data could not be collected for any reason. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalMoniSecs. ⓘ

HCPerfIntervalCountA gauge associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. Let X be an object with HCPerfIntervalCount syntax. Let Y be an object with HCPerfCurrentCount syntax. Let Z be an object with HCPerfTotalCount syntax. Then, in a system supporting a history of n intervals with X(1) and X(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of X(n) - the value of X(i) becomes that of X(i-1) for n >= i > 1 - the value of X(1) becomes that of Y. - the value of Z, if supported, is adjusted. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfIntervalCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the value of the object also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64

A read-only count of CRC-4 errors on the G.Bond/TDIM port during the 1-day performance history interval. This object is inhibited during Severely Errored Seconds (SES) and Unavailable Seconds (UAS).

HCPerfIntervalCountA gauge associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. Let X be an object with HCPerfIntervalCount syntax. Let Y be an object with HCPerfCurrentCount syntax. Let Z be an object with HCPerfTotalCount syntax. Then, in a system supporting a history of n intervals with X(1) and X(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of X(n) - the value of X(i) becomes that of X(i-1) for n >= i > 1 - the value of X(1) becomes that of Y. - the value of Z, if supported, is adjusted. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfIntervalCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the value of the object also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64

A read-only count of CRC-6 errors on the G.Bond/TDIM port during the 1-day performance history interval. This object is inhibited during Unavailable Seconds (UAS).

HCPerfIntervalCountA gauge associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. Let X be an object with HCPerfIntervalCount syntax. Let Y be an object with HCPerfCurrentCount syntax. Let Z be an object with HCPerfTotalCount syntax. Then, in a system supporting a history of n intervals with X(1) and X(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of X(n) - the value of X(i) becomes that of X(i-1) for n >= i > 1 - the value of X(1) becomes that of Y. - the value of Z, if supported, is adjusted. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfIntervalCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the value of the object also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64

A read-only count of CRC-8 errors on the G.Bond/TDIM port during the current 1-day performance interval. This object is inhibited during Unavailable Seconds (UAS).

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU-C MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalValid. ⓘ

HCPerfValidIntervalsThe number of near end intervals for which data was collected. The value of an object with an HCPerfValidIntervals syntax will be 96 unless the measurement was (re-)started within the last 1440 minutes, in which case the value will be the number of complete 15 minute intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy) it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available. (0..96) · Integer32

A read-only number of 15-minute intervals for which the performance data was collected. The value of this object will be 96 or the maximum number of 15-minute history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 15-minute intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available. This object partially maps to the TR-159 attribute aGroupPerf15MinValidIntervals. ⓘ

HCPerfInvalidIntervalsThe number of near end intervals for which no data is available. The value of an object with an HCPerfInvalidIntervals syntax will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations). (0..96) · Integer32

A read-only number of 15-minute intervals for which the performance data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available. This object partially maps to the TR-159 attribute aGroupPerf15MinInvalidIntervals. ⓘ

HCPerfTimeElapsedThe number of seconds that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock or the addition of a leap second, the duration of the current interval exceeds the maximum value, the agent will return the maximum value. For 15 minute intervals, the range is limited to (0..899). For 24 hour intervals, the range is limited to (0..86399). (0..86399) · Integer32 · seconds

A read-only count of seconds that have elapsed since the beginning of the current 15-minute performance interval. This object partially maps to the TR-159 attribute aGroupPerfCurr15MinTimeElapsed. ⓘ

HCPerfCurrentCountA gauge associated with a performance measurement in a current 15 minute measurement interval. The value of an object with an HCPerfCurrentCount syntax starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the gauge is stored in the first 15 minute history interval, and the gauge is restarted at zero. In the case where the agent has no valid data available for the current interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfCurrentCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the object's value also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · seconds

A read-only count of seconds in the current 15-minute performance interval during which a particular TDIM service was 'down', as indicated by the g9983OperSvcState object. This object is inhibited during Unavailable Seconds (UAS).

Unsigned32 (0..7) · days

A read-only number of 1-day performance history intervals for which the data was collected. The value of this object will be 7 or the maximum number of 1-day history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 1-day intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available. ⓘ

Unsigned32 (0..7) · days

A read-only number of 1-day performance history intervals for which the performance data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available. ⓘ

HCPerfTimeElapsedThe number of seconds that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock or the addition of a leap second, the duration of the current interval exceeds the maximum value, the agent will return the maximum value. For 15 minute intervals, the range is limited to (0..899). For 24 hour intervals, the range is limited to (0..86399). (0..86399) · Integer32 · seconds

A read-only count of seconds that have elapsed since the beginning of the current 1-day performance interval. ⓘ

HCPerfCurrentCountA gauge associated with a performance measurement in a current 15 minute measurement interval. The value of an object with an HCPerfCurrentCount syntax starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the gauge is stored in the first 15 minute history interval, and the gauge is restarted at zero. In the case where the agent has no valid data available for the current interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfCurrentCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the object's value also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · seconds

A read-only count of seconds in the current 1-day performance interval during which a particular TDIM service was 'down', as indicated by the g9983OperSvcState object. This object is inhibited during Unavailable Seconds (UAS).

Unsigned32 (1..96)

Performance data interval number. 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are OPTIONAL. This object partially maps to the TR-159 attribute aGroupPerf15MinIntervalNumber. ⓘ

HCPerfTimeElapsedThe number of seconds that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock or the addition of a leap second, the duration of the current interval exceeds the maximum value, the agent will return the maximum value. For 15 minute intervals, the range is limited to (0..899). For 24 hour intervals, the range is limited to (0..86399). (0..86399) · Integer32 · seconds

A read-only count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (900 seconds), except in a situation where performance data could not be collected for any reason.

HCPerfIntervalCountA gauge associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. Let X be an object with HCPerfIntervalCount syntax. Let Y be an object with HCPerfCurrentCount syntax. Let Z be an object with HCPerfTotalCount syntax. Then, in a system supporting a history of n intervals with X(1) and X(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of X(n) - the value of X(i) becomes that of X(i-1) for n >= i > 1 - the value of X(1) becomes that of Y. - the value of Z, if supported, is adjusted. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfIntervalCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the value of the object also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · seconds

A read-only count of seconds in the 15-minute performance history interval during which a particular TDIM service was 'down', as indicated by the g9983OperSvcState object. This object is inhibited during Unavailable Seconds (UAS).

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU-C MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database. This object partially maps to the TR-159 attribute aGroupPerf15MinIntervalValid. ⓘ

Unsigned32 (1..7)

Performance data interval number. 1 is the most recent previous interval; interval 7 is 7 days ago. Intervals 2..7 are OPTIONAL. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalNumber. ⓘ

HCPerfTimeElapsedThe number of seconds that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock or the addition of a leap second, the duration of the current interval exceeds the maximum value, the agent will return the maximum value. For 15 minute intervals, the range is limited to (0..899). For 24 hour intervals, the range is limited to (0..86399). (0..86399) · Integer32 · seconds

A read-only count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (86400 seconds), except in a situation where performance data could not be collected for any reason. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalMoniSecs. ⓘ

HCPerfIntervalCountA gauge associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval, the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist. Let X be an object with HCPerfIntervalCount syntax. Let Y be an object with HCPerfCurrentCount syntax. Let Z be an object with HCPerfTotalCount syntax. Then, in a system supporting a history of n intervals with X(1) and X(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of X(n) - the value of X(i) becomes that of X(i-1) for n >= i > 1 - the value of X(1) becomes that of Y. - the value of Z, if supported, is adjusted. This count represents a non-negative integer, which may increase or decrease, but shall never exceed 2^64-1 (18446744073709551615 decimal), nor fall below 0. The value of an object with HCPerfIntervalCount syntax assumes its maximum value whenever the underlying count exceeds 2^64-1. If the underlying count subsequently decreases below 2^64-1 (due, e.g., to a retroactive adjustment as a result of entering or exiting unavailable time), then the value of the object also decreases. Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short- term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · seconds

A read-only count of seconds in the 1-day performance history interval during which a particular TDIM service was 'down', as indicated by the g9983OperSvcState object. This object is inhibited during Unavailable Seconds (UAS).

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU-C MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalValid. ⓘ