CISCO-WIRELESS-P2MP-RF-METRICS-MIB

MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:

This object is used to index this table. At the head end: When a histogram is created on a per subscriber unit basis, this object should reflect the MAC address of the subscriber unit. When a histogram is created on a per channel basis, this object must be set to zero(00 00 00 00 00 00). At the subscriber end: When creating a histogram, this object must always be set to zero (00 00 00 00 00 00).

P2mpRadioSignalAttribute0 = none1 = rsaSinrMainAnt2 = rsaSinrDiversityAnt3 = rsaSinrRatio4 = rsaTimingOffset5 = rsaRxPowerMainAnt6 = rsaRxPowerDiversityAnt7 = rsaChDelaySpreadMainAnt8 = rsaChDelaySpreadDiversityAnt9 = rsaHeAmbientNoise10 = rsaSuRxPowerDeltaMainAnt11 = rsaSuRxPowerDeltaDiversityAnt12 = rsaSuTotalTxPowerThis represents the set of radio signal attributes that may be monitored in a point to multipoint system by using histograms, timelines, and thresholds. Some of these attributes are common to the head end (HE) and the subscriber unit (SU) whereas some are specific to either the HE or the SU. The attributes are: none(0) - This is a special value reserved to indicate that there is no threshold associated with a timeline. This attribute cannot be used to create a histogram, timeline, or threshold. rsaSinrMainAnt(1) - This is the Interference + Noise power level computed by the hardware at the main antenna on a burst by burst basis rsaSinrDiversityAnt(2) - This is the Interference + Noise power level computed by the hardware at the diversity antenna on a burst by burst basis. rsaSinrRatio(3) - Ratio of (Interference + Noise) in main antenna to diversity antenna rsaTimingOffset(4) - This represents the timing delay variations detected on a radio link. rsaRxPowerMainAnt(5) - This is a measure of the analog signal power received at the main antenna RF head on a burst by burst basis. rsaRxPowerDiversityAnt(6) - This is a measure of the analog signal power received at the diversity antenna RF head on a burst by burst basis. rsaChDelaySpreadMainAnt(7) - Number of samples that the channel response remains within (TBD) db of the manimun TAP in the channel response at the main antenna. rsaChDelaySpreadDiversityAnt(8) - Number of samples that the channel response remains within (TBD) db of the manimun TAP in the channel response at the diversity antenna. rsaHeAmbientNoise(19) - The ambient noise (in dB) is measured when there is no signal being received at the Headend rsaSuRxPowerDeltaMainAnt(10) - Change in received power (dB) at the main antenna of the subscriber unit on a burst by burst basis. rsaSuRxPowerDeltaDiversityAnt(11) - Change in received power (dB) at the diversity antenna of the subscriber unit on a burst by burst basis. rsaSuTotalTxPower(12) - The sum of -20 dBm (reference level out of the DAC) + Tx IF transmit gain - 13 dBm (cable compensation) + Tx RF transmit gain. This parameter does not include antenna gains. · Integer32

This objects used to index this table. It represents the attribute that is being histogrammed.

INTEGER1 = fine2 = coarse · Integer32

This object lets the user select the granularity of the histogram. The number of bins used for the capture in each category is hardware dependent.

CwrFixedPointScale1 = yocto2 = zepto3 = atto4 = femto5 = pico6 = nano7 = micro8 = milli9 = units10 = kilo11 = mega12 = giga13 = tera14 = exa15 = peta16 = zetta17 = yottaInternational System of Units (SI) prefixes. · Integer32

This variable indicates the exponent to apply to the fixed-point values in the histogram summary table.

CwrFixedPointPrecisionWhen in the range 1 to 9, CwrFixedPointPrecision is the number of decimal places in the fractional part of a fixed-point number. CwrFixedPointPrecision is 0 for non-fixed-point numbers. (0..9) · Integer32

This variable indicates the number of decimal places used for precision when interpreting the fixed-point values in the histogram summary table.

Integer32 (-2147483647..2147483647)

This object represents the maximum of the values that will be collected in the first bin of the histogram. All values <= p2mpStartBinValue are kept in the first histogram bin.

Integer32 (-2147483647..2147483647)

This object represents the minimum of the values that will be collected in the last bin of the histogram. All values >= p2mpEndBinValue are kept in the last histogram bin.

CwrUpdateTimeThis is used to report statistics values measured on the wireless link with a 1 second granularity insted of timeTicks. (0..2147483647) · Integer32 · seconds

This object specifies the duration for which this histogram must be accumulated. After successfully accumulating data for this amount of time the collection stops and the p2mpHistStatus changes to statusCaptured.

CwrUpdateTimeThis is used to report statistics values measured on the wireless link with a 1 second granularity insted of timeTicks. (0..2147483647) · Integer32 · seconds

This object represents rate at which snapshots of the histogram will be available.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

The histogram data is updated every p2mpUpdateRate seconds. When set to true(1), the latest histogram data set is summed with the previous histogram data set and the p2mpHistSummaryTable will reflect cumulative values. When set to false(2), only the latest data set is made available and the p2mpHistSummarytable will reflect the latest values.

OwnerStringThis data type is used to model an administratively assigned name of the owner of a resource. This information is taken from the NVT ASCII character set. It is suggested that this name contain one or more of the following: ASCII form of the manager station's transport address, management station name (e.g., domain name), network management personnel's name, location, or phone number. In some cases the agent itself will be the owner of an entry. In these cases, this string shall be set to a string starting with 'agent'. SIZE (0..255) · OCTET STRING · hint 255a

This object identifies management station that created this histogram specification.

CwrCollectionAction1 = actionStop2 = actionStart3 = actionClear4 = actionRestartThe action to perform on the identified specification. It can be: Stop: Stop the collection specification from continuing. Start: Start the collection specification. Clear: Clear the current collection data. A collection in progress must be stopped before it can be cleared. Restart: Identical to Clear followed by a Start. · Integer32

This object represents the action to be carried out on this histogram specification. If a histogram has been successfully captured then it must be cleared before an other capture may be initiated.

CwrCollectionStatus1 = statusIdle2 = statusInProgress3 = statusStopped4 = statusCapturedThis indicates the current status of the collection specification. It can be: Idle: No action in progress. In_progress: Collection specification is currently being executed Stopped: The collection specification has been stopped before it completed successfully. Captured: The collection is complete and data is available. · Integer32

This object represents the current state of this histogram. Once the histogram collection is complete the status changes to statusCaptured and the data is available for use. None of the parameters of a histogram specification may be modified when the specification is in statusInProgress. A statusCaptured or statusStopped histogram must be actionClear'ed before it can be restarted. The histogram may be read accurately between the p2mpUpdateRate intervals. If the read spans across the update time data from the previous and current updates can be mingled.

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 may be used to create or delete a histogram control specification.

CwrUpdateTimeThis is used to report statistics values measured on the wireless link with a 1 second granularity insted of timeTicks. (0..2147483647) · Integer32 · seconds

This object represents the sysUpTime when this histogram was retrieved from hardware.

CwrFixedPointValueThis represents a fixed point number. Use values -2147483648 and +2147483647 to indicate underflow and overflow respectively. Use CwrFixedPointPrecision to indicate how many fractional digits the CwrFixedPointValue has. · Integer32

This object represents minimum value seen in this histogram.

CwrFixedPointValueThis represents a fixed point number. Use values -2147483648 and +2147483647 to indicate underflow and overflow respectively. Use CwrFixedPointPrecision to indicate how many fractional digits the CwrFixedPointValue has. · Integer32

This object represents maximum value seen in this histogram.

CwrFixedPointValueThis represents a fixed point number. Use values -2147483648 and +2147483647 to indicate underflow and overflow respectively. Use CwrFixedPointPrecision to indicate how many fractional digits the CwrFixedPointValue has. · Integer32

This object represents mean of the values in this histogram.

Integer32 (1..50)

This object represents the histogram bin number for the value in p2mpValue.

Integer32 (0..2147483647)

This object represents the value in the histogram bin p2mpHistBinIndex.

MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:

This object is used to index this table. At the head end: When a timeline is created on a per subscriber unit basis, this object should reflect the MAC address of the subscriber unit. When a timeline is created on a per channel basis, this object must be set to zero(00 00 00 00 00 00). At the subscriber end: When creating a timeline, this object must always be set to zero (00 00 00 00 00 00).

P2mpRadioSignalAttribute0 = none1 = rsaSinrMainAnt2 = rsaSinrDiversityAnt3 = rsaSinrRatio4 = rsaTimingOffset5 = rsaRxPowerMainAnt6 = rsaRxPowerDiversityAnt7 = rsaChDelaySpreadMainAnt8 = rsaChDelaySpreadDiversityAnt9 = rsaHeAmbientNoise10 = rsaSuRxPowerDeltaMainAnt11 = rsaSuRxPowerDeltaDiversityAnt12 = rsaSuTotalTxPowerThis represents the set of radio signal attributes that may be monitored in a point to multipoint system by using histograms, timelines, and thresholds. Some of these attributes are common to the head end (HE) and the subscriber unit (SU) whereas some are specific to either the HE or the SU. The attributes are: none(0) - This is a special value reserved to indicate that there is no threshold associated with a timeline. This attribute cannot be used to create a histogram, timeline, or threshold. rsaSinrMainAnt(1) - This is the Interference + Noise power level computed by the hardware at the main antenna on a burst by burst basis rsaSinrDiversityAnt(2) - This is the Interference + Noise power level computed by the hardware at the diversity antenna on a burst by burst basis. rsaSinrRatio(3) - Ratio of (Interference + Noise) in main antenna to diversity antenna rsaTimingOffset(4) - This represents the timing delay variations detected on a radio link. rsaRxPowerMainAnt(5) - This is a measure of the analog signal power received at the main antenna RF head on a burst by burst basis. rsaRxPowerDiversityAnt(6) - This is a measure of the analog signal power received at the diversity antenna RF head on a burst by burst basis. rsaChDelaySpreadMainAnt(7) - Number of samples that the channel response remains within (TBD) db of the manimun TAP in the channel response at the main antenna. rsaChDelaySpreadDiversityAnt(8) - Number of samples that the channel response remains within (TBD) db of the manimun TAP in the channel response at the diversity antenna. rsaHeAmbientNoise(19) - The ambient noise (in dB) is measured when there is no signal being received at the Headend rsaSuRxPowerDeltaMainAnt(10) - Change in received power (dB) at the main antenna of the subscriber unit on a burst by burst basis. rsaSuRxPowerDeltaDiversityAnt(11) - Change in received power (dB) at the diversity antenna of the subscriber unit on a burst by burst basis. rsaSuTotalTxPower(12) - The sum of -20 dBm (reference level out of the DAC) + Tx IF transmit gain - 13 dBm (cable compensation) + Tx RF transmit gain. This parameter does not include antenna gains. · Integer32

This object represents the attribute for which a timline capture is requested. When a timeline is requested p2mpBufSize worth of data will be captured.

P2mpRadioSignalAttribute0 = none1 = rsaSinrMainAnt2 = rsaSinrDiversityAnt3 = rsaSinrRatio4 = rsaTimingOffset5 = rsaRxPowerMainAnt6 = rsaRxPowerDiversityAnt7 = rsaChDelaySpreadMainAnt8 = rsaChDelaySpreadDiversityAnt9 = rsaHeAmbientNoise10 = rsaSuRxPowerDeltaMainAnt11 = rsaSuRxPowerDeltaDiversityAnt12 = rsaSuTotalTxPowerThis represents the set of radio signal attributes that may be monitored in a point to multipoint system by using histograms, timelines, and thresholds. Some of these attributes are common to the head end (HE) and the subscriber unit (SU) whereas some are specific to either the HE or the SU. The attributes are: none(0) - This is a special value reserved to indicate that there is no threshold associated with a timeline. This attribute cannot be used to create a histogram, timeline, or threshold. rsaSinrMainAnt(1) - This is the Interference + Noise power level computed by the hardware at the main antenna on a burst by burst basis rsaSinrDiversityAnt(2) - This is the Interference + Noise power level computed by the hardware at the diversity antenna on a burst by burst basis. rsaSinrRatio(3) - Ratio of (Interference + Noise) in main antenna to diversity antenna rsaTimingOffset(4) - This represents the timing delay variations detected on a radio link. rsaRxPowerMainAnt(5) - This is a measure of the analog signal power received at the main antenna RF head on a burst by burst basis. rsaRxPowerDiversityAnt(6) - This is a measure of the analog signal power received at the diversity antenna RF head on a burst by burst basis. rsaChDelaySpreadMainAnt(7) - Number of samples that the channel response remains within (TBD) db of the manimun TAP in the channel response at the main antenna. rsaChDelaySpreadDiversityAnt(8) - Number of samples that the channel response remains within (TBD) db of the manimun TAP in the channel response at the diversity antenna. rsaHeAmbientNoise(19) - The ambient noise (in dB) is measured when there is no signal being received at the Headend rsaSuRxPowerDeltaMainAnt(10) - Change in received power (dB) at the main antenna of the subscriber unit on a burst by burst basis. rsaSuRxPowerDeltaDiversityAnt(11) - Change in received power (dB) at the diversity antenna of the subscriber unit on a burst by burst basis. rsaSuTotalTxPower(12) - The sum of -20 dBm (reference level out of the DAC) + Tx IF transmit gain - 13 dBm (cable compensation) + Tx RF transmit gain. This parameter does not include antenna gains. · Integer32

This object, along with p2mpTlThreshType, identifies the threshold in the p2mpThresholdTable responsible for trigerring this timeline. When this object's value is none(0), it implies that there is no threshold associated with this timeline.

CwrThreshLimitType1 = upChange2 = downChange3 = highThresh4 = lowThresh5 = upLimit6 = lowLimitThis object represents the kind of change that needs to be monitored for a thresholdable attribute . An event is generated when the following condition is met. The kinds of change that may be setup in the radio hardware are: upChange : Monitored value changes by a positive amount. downChange : Monitored value changes by a negative amount. highThresh : Monitored value exceeds specified threshold. lowThresh : Monitored value receeds below a threshold. upLimit : Monitored value crosses the specified threshold when increasing in value. lowLimit : Monitored value crosses the specified threshold when decreasing in value. · Integer32

This object, along with p2mpTlThreshAttribute, identifies the threshold in the p2mpThresholdTable responsible for trigerring this timeline. When this object's value is none(0), it implies that there is no threshold associated with this timeline.

Integer32 (1..2147483647) · number of data values

This object indicates the number of data values to be captured for this timeline. The captured data can be viewed by reading the p2mpTlDataTable.

CwrFixedPointScale1 = yocto2 = zepto3 = atto4 = femto5 = pico6 = nano7 = micro8 = milli9 = units10 = kilo11 = mega12 = giga13 = tera14 = exa15 = peta16 = zetta17 = yottaInternational System of Units (SI) prefixes. · Integer32

This variable indicates the exponent to apply to the fixed-point values in the timeline data table.

CwrFixedPointPrecisionWhen in the range 1 to 9, CwrFixedPointPrecision is the number of decimal places in the fractional part of a fixed-point number. CwrFixedPointPrecision is 0 for non-fixed-point numbers. (0..9) · Integer32

This variable indicates the number of decimal places used for precision when interpreting the fixed-point values in the timeline data table.

Integer32 (0..2147483647) · milliseconds

This lets the user specify the time in milliseconds between consecutive timeline samples. The special value of '0' indicates that the timeline will be sampled on every burst of data. The number of bursts in one milliseconds depends on the modulation profile.

CwrCollectionAction1 = actionStop2 = actionStart3 = actionClear4 = actionRestartThe action to perform on the identified specification. It can be: Stop: Stop the collection specification from continuing. Start: Start the collection specification. Clear: Clear the current collection data. A collection in progress must be stopped before it can be cleared. Restart: Identical to Clear followed by a Start. · Integer32

This object represents the action to be carried out on this timeline specification. If a timeline has been successfully captured then it must be cleared before another capture may be initiated.

INTEGER1 = preTrigger2 = postTrigger · Integer32

Once a trigger fires, this object determines which portion of the collected data to capture for use. If it is: preTrigger(1) : Then most of the data collected prior to trigger is captured. postTrigger(2): Then most of the data collected after the trigger is captured.

OwnerStringThis data type is used to model an administratively assigned name of the owner of a resource. This information is taken from the NVT ASCII character set. It is suggested that this name contain one or more of the following: ASCII form of the manager station's transport address, management station name (e.g., domain name), network management personnel's name, location, or phone number. In some cases the agent itself will be the owner of an entry. In these cases, this string shall be set to a string starting with 'agent'. SIZE (0..255) · OCTET STRING · hint 255a

This object identifies the management station that created this timeline specification.

CwrCollectionStatus1 = statusIdle2 = statusInProgress3 = statusStopped4 = statusCapturedThis indicates the current status of the collection specification. It can be: Idle: No action in progress. In_progress: Collection specification is currently being executed Stopped: The collection specification has been stopped before it completed successfully. Captured: The collection is complete and data is available. · Integer32

This object represents the current state of this timeline. Once the timeline collection is complete the status changes to statusCaptured and the data is available for use. None of the parameters of a timeline specification may be modified when the specification is in statusInProgress. A statusCaptured or statusStopped timeline must be actionClear'ed before it can be restarted.

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 may be used to create or delete a timeline control specification. Once created data sampling starts based on the value of p2mpTlAction.

CwrUpdateTimeThis is used to report statistics values measured on the wireless link with a 1 second granularity insted of timeTicks. (0..2147483647) · Integer32 · seconds

This object represents the sysUpTime when this timeline capture was completed.

Integer32 (0..2147483647)

This object represents the number of values available in the timeline

Integer32 (0..2147483647)

This object contains the value of p2mpTlValueIndex which represents the entry in the p2mpTlDataTable that caused the stop trigger to fire, thereby resulting in this timeline to be collected.

Integer32 (1..2147483647)

This object is the index into the timeline data.

CwrFixedPointValueThis represents a fixed point number. Use values -2147483648 and +2147483647 to indicate underflow and overflow respectively. Use CwrFixedPointPrecision to indicate how many fractional digits the CwrFixedPointValue has. · Integer32

This object represents the radio signal data sampled.

MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:

This object is used to index this table. At the head end: When a threshold is created on a per subscriber unit basis, this object should reflect the MAC address of the subscriber unit. When a threshold is created on a per channel basis, this object must be set to zero(00 00 00 00 00 00). At the subscriber end: When creating a threshold , this object must always be set to zero (00 00 00 00 00 00).

P2mpRadioSignalAttribute0 = none1 = rsaSinrMainAnt2 = rsaSinrDiversityAnt3 = rsaSinrRatio4 = rsaTimingOffset5 = rsaRxPowerMainAnt6 = rsaRxPowerDiversityAnt7 = rsaChDelaySpreadMainAnt8 = rsaChDelaySpreadDiversityAnt9 = rsaHeAmbientNoise10 = rsaSuRxPowerDeltaMainAnt11 = rsaSuRxPowerDeltaDiversityAnt12 = rsaSuTotalTxPowerThis represents the set of radio signal attributes that may be monitored in a point to multipoint system by using histograms, timelines, and thresholds. Some of these attributes are common to the head end (HE) and the subscriber unit (SU) whereas some are specific to either the HE or the SU. The attributes are: none(0) - This is a special value reserved to indicate that there is no threshold associated with a timeline. This attribute cannot be used to create a histogram, timeline, or threshold. rsaSinrMainAnt(1) - This is the Interference + Noise power level computed by the hardware at the main antenna on a burst by burst basis rsaSinrDiversityAnt(2) - This is the Interference + Noise power level computed by the hardware at the diversity antenna on a burst by burst basis. rsaSinrRatio(3) - Ratio of (Interference + Noise) in main antenna to diversity antenna rsaTimingOffset(4) - This represents the timing delay variations detected on a radio link. rsaRxPowerMainAnt(5) - This is a measure of the analog signal power received at the main antenna RF head on a burst by burst basis. rsaRxPowerDiversityAnt(6) - This is a measure of the analog signal power received at the diversity antenna RF head on a burst by burst basis. rsaChDelaySpreadMainAnt(7) - Number of samples that the channel response remains within (TBD) db of the manimun TAP in the channel response at the main antenna. rsaChDelaySpreadDiversityAnt(8) - Number of samples that the channel response remains within (TBD) db of the manimun TAP in the channel response at the diversity antenna. rsaHeAmbientNoise(19) - The ambient noise (in dB) is measured when there is no signal being received at the Headend rsaSuRxPowerDeltaMainAnt(10) - Change in received power (dB) at the main antenna of the subscriber unit on a burst by burst basis. rsaSuRxPowerDeltaDiversityAnt(11) - Change in received power (dB) at the diversity antenna of the subscriber unit on a burst by burst basis. rsaSuTotalTxPower(12) - The sum of -20 dBm (reference level out of the DAC) + Tx IF transmit gain - 13 dBm (cable compensation) + Tx RF transmit gain. This parameter does not include antenna gains. · Integer32

This represents the attribute of a radio link which needs to be thresholded. For each of these attributes, the p2mpThreshType identifies the type of change to monitor. When that threshold is exceeded a Trap with appropriate parameters will be generated.

CwrThreshLimitType1 = upChange2 = downChange3 = highThresh4 = lowThresh5 = upLimit6 = lowLimitThis object represents the kind of change that needs to be monitored for a thresholdable attribute . An event is generated when the following condition is met. The kinds of change that may be setup in the radio hardware are: upChange : Monitored value changes by a positive amount. downChange : Monitored value changes by a negative amount. highThresh : Monitored value exceeds specified threshold. lowThresh : Monitored value receeds below a threshold. upLimit : Monitored value crosses the specified threshold when increasing in value. lowLimit : Monitored value crosses the specified threshold when decreasing in value. · Integer32

This object represents the kind of change that needs to be monitored for the p2mpThreshAttribute. An event is generated when the specified condition is met.

Integer32 (-2147483647..2147483647)

This object represents the value to be compared against. The p2mpThreshType determines the way in which it is used. It is used as follows: if p2mpThreshType is .. highThresh : Notify if data sample exceeds the p2mpThreshValue. lowThresh : Notify if data sample recedes below the p2mpThreshValue. upChange : Notify if data sample increases by more than p2mpThreshValue. downChange : Notify if data sample decreases by more than p2mpThreshValue. upLimit : Notify if data sample crosses p2mpThreshValue while increasing in value. lowLimit : Notify if data sample crosses p2mpThreshValue while decreasing in value.

TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32

When radio signals oscillate around threshold values, they potentially flood the system with notifications. This object specifies the amount of time to wait before sending an identical notification if the oscillations continue.

TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32

It is desirable to know when a radio signal has stabilized. This object specifies the amount of time that the radio signal should stay below the threshold after crossing it. If it does then a 'clear' notification is sent.

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 represents the status of this threshold entry. It may be used to create a new threshold specification. For every p2mpThreshAttribute one threshold of p2mpThreshType on one DSP may be created.

Integer32 (1..8)

This object represents the DSP on which the snapshot needs to be collected.

P2mpSnapshotAttributeThis represents the set of radio signal attributes that may be monitored by using a snapshot. The user can capture upto 4 radio signal attributes simultaneously, by picking at most one signal from each of the sets below and setting the bit corresponding to each selected signal. When a snapshot request is issued up to four radio signal attributes may be requested at once, one from each set: =============================================== Type Set1 Set2 =============================================== RX y1n(x1) y2n(x2) H2k(x80) H1k(x40) =============================================== =============================================== Type Set3 Set4 =============================================== RX Y2k(x8) Y1k(x4) h1n(x10) h2n(x20) zhat(x100) - =============================================== The attributes are: rxRawBurstAnt1Y1n(0) - This represents a snapshot of the received signal for the main RF resource. For every sample, the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. rxRawBurstAnt2Y2n(1) - This represents a snapshot of the received signal for the diversity RF resource. For every sample, the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. rxSpectrumAnt1Y1k(2) - This represents a snapshot of the spectrum of the received signal for the main RF resource. For every sample, the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. rxSpectrumAnt2Y2k(3) - This represents a snapshot of the spectrum of the received signal for the diversity RF resource. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. rxTimeDomainChannelAnt1H1n(4) - This represents a snapshot of the time domain channel for the main RF resource. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. rxTimeDomainChannelAnt2H2n(5) - This represents a snapshot of the time domain channel for the diversity RF resource. For every sample, the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. rxFreqDomainChannelAnt1H1k(6) - This represents a snapshot of the frequency domain channel for the main RF resource. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. rxFreqDomainChannelAnt2H2k(7) - This represents a snapshot of the frequency domain channel for the diversity RF resource. For every sample, the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. rxConstellationZHatk(8) - This represents a snapshot of the soft decisions. For every sample, the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. SIZE (1) · OCTET STRING

This identfies the set of radio signal attributes being monitored in this snapshot.

CwrFixedPointScale1 = yocto2 = zepto3 = atto4 = femto5 = pico6 = nano7 = micro8 = milli9 = units10 = kilo11 = mega12 = giga13 = tera14 = exa15 = peta16 = zetta17 = yottaInternational System of Units (SI) prefixes. · Integer32

This variable indicates the exponent to apply to the fixed-point values in the snapshot data table.

CwrFixedPointPrecisionWhen in the range 1 to 9, CwrFixedPointPrecision is the number of decimal places in the fractional part of a fixed-point number. CwrFixedPointPrecision is 0 for non-fixed-point numbers. (0..9) · Integer32

This variable indicates the number of decimal places used for precision when interpreting the fixed-point values in the snapshot data table.

OwnerStringThis data type is used to model an administratively assigned name of the owner of a resource. This information is taken from the NVT ASCII character set. It is suggested that this name contain one or more of the following: ASCII form of the manager station's transport address, management station name (e.g., domain name), network management personnel's name, location, or phone number. In some cases the agent itself will be the owner of an entry. In these cases, this string shall be set to a string starting with 'agent'. SIZE (0..255) · OCTET STRING · hint 255a

This object identifies management station that created this snapshot specification.

CwrCollectionAction1 = actionStop2 = actionStart3 = actionClear4 = actionRestartThe action to perform on the identified specification. It can be: Stop: Stop the collection specification from continuing. Start: Start the collection specification. Clear: Clear the current collection data. A collection in progress must be stopped before it can be cleared. Restart: Identical to Clear followed by a Start. · Integer32

This object represents the action to be carried out on this snapshot specification. If a snapshot has been successfully captured then it must be cleared before another capture may be initiated.

CwrCollectionStatus1 = statusIdle2 = statusInProgress3 = statusStopped4 = statusCapturedThis indicates the current status of the collection specification. It can be: Idle: No action in progress. In_progress: Collection specification is currently being executed Stopped: The collection specification has been stopped before it completed successfully. Captured: The collection is complete and data is available. · Integer32

This object represents the current status of this snapshot specification. When the status in statusInProgress none of the snapshot parameters can be configured. When the status is statusCaptured then data is available for use.

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 may be used to create or delete this snapshot specification.

Integer32 (1..2147483647)

This object represents the bit in the P2mpSnapshotAttribute bitmask that identifies the first attribute value.

Integer32 (0..4096)

This object represents the number of values captured for the snapshot p2mpSnapAttr1Id.

Integer32 (1..2147483647)

This object represents the bit in the P2mpSnapshotAttribute bitmask that identifies the second attribute value.

Integer32 (0..4096)

This object represents the number of values captured for the snapshot p2mpSnapAttr2Id.

Integer32 (1..2147483647)

This object represents the bit in the P2mpSnapshotAttribute bitmask that identifies the third attribute value.

Integer32 (0..4096)

This object represents the number of values captured for the snapshot p2mpSnapAttr3Id.

Integer32 (1..2147483647)

This object represents the bit in the P2mpSnapshotAttribute bitmask that identifies the fourth attribute value.

Integer32 (0..4096)

This object represents the number of values captured for the snapshot p2mpSnapAttr4Id.

Integer32 (1..4096)

This object represents the snapshot entry value number. The hardware provides a maximum of 1024 data points for any snapshot attribute. Since we can capture a maximum of 4 attributes in a single snapshot, this object can have a maximum value of 4096 (1024 * 4).

CwrFixedPointValueThis represents a fixed point number. Use values -2147483648 and +2147483647 to indicate underflow and overflow respectively. Use CwrFixedPointPrecision to indicate how many fractional digits the CwrFixedPointValue has. · Integer32

The data sample value. Real part.

CwrFixedPointValueThis represents a fixed point number. Use values -2147483648 and +2147483647 to indicate underflow and overflow respectively. Use CwrFixedPointPrecision to indicate how many fractional digits the CwrFixedPointValue has. · Integer32

The data sample value. Imaginary part of the attribute is represented by a complex number.