CISCO-WIRELESS-IF-MIB

INTEGER0 = none1 = codec2 = framer3 = fir4 = if5 = rf6 = rfDiversity7 = ifMain8 = ifDiversity · Integer32

This object represents the point in the system where the data signal is looped back. none(0) - no loopback codec(1) - loopback at the Encoder/Decoder module. This exercises the framer, and codec modules framer(2) - loopback at the 'framer' module. fir(3) - loopback at the 'Finite Impulse Response' module. This exercises the framer, codec, and FIR modules. if(4) - loopback at the 'Internal Frequency' module using both the main and the diversity receive paths. This exercises the framer, codec, FIR, and IF modules. rf(5) - loopback at the main RF unit via the main receive path in the IF module. This exercises the framer, codec, FIR, IF, and RF modules. rfDiversity(6) - loopback at the main RF unit but route it through the diversity receive path in the IF module. This exercises the framer, codec, FIR, IF, and RF modules. ifMain(7) - loopack at the IF module using only the Main receive path. This exercises the framer, codec, FIR, and IF modules. ifDiversity(8) - loopack at the IF module using only the diversity receive path. This exercises the framer, codec, FIR, and IF modules.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

If set to true(1), then the DSP identified by cwrScopePortDsp, will redirect a portion of the output signal for the attribute identified by cwrScopeAttribute to the scope port.

INTEGER (1..8) · Integer32

This identifies the DSP that should redirect a portion of the signal data to the scope port.

Integer32 (1..2147483647)

This represents the attribute to be redirected to the scope port. The attributes that may be redirected to scope port is the same as that identified in cwrSnapshotType.

INTEGER1 = master2 = slave · Integer32

This object specifies whether the radio should act as the master or as the slave. The slave radio tracks the master's frequency.

INTEGER1 = off2 = once3 = always · Integer32

This object specifies the whether self test should be executed and if so whether to do it every time the radio link is started. Any changes made to this object will reflected the next time the radio link is started. off(1) - Self test never performed. once(2) - Self test will be performed the next time the radio link is started. always(3) - Every time the radio link is started.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether the Baseline Privacy feature is available for use on this radio interface. If true then privacy is supported.

CwrRFZeroIndexThis represents an index into the cwrRFTable. The valid values are from 1 onwards. The special value of 0 is used to indicate the absence of the associated RF resource. (0..2) · Integer32

This object specifies the index into the cwrRfTable identifying the antenna used for transmission. This index will be 0 if the associated transmit antenna is not present.

CwrRFZeroIndexThis represents an index into the cwrRFTable. The valid values are from 1 onwards. The special value of 0 is used to indicate the absence of the associated RF resource. (0..2) · Integer32

This object specifies the index of the first receive antenna identified by the cwrRfTable. This index will be 0 if the associated receive antenna is not present.

CwrRFZeroIndexThis represents an index into the cwrRFTable. The valid values are from 1 onwards. The special value of 0 is used to indicate the absence of the associated RF resource. (0..2) · Integer32

This object specifies the index of the second receive antenna in the cwrRfTable. This index will be 0 if the associated receive antenna is not present.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

When this object is set to true(1), the wireless radio uses a 10MHz external reference clock.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

For normal operation this should be set to false(2). If it set true(1), then the radio link is placed in antenna alignment mode. In this mode control signals are sent to the RF resource which enables the operator to monitor the signal received strength at the RF resource. This is mainly used for antenna steering i.e. positioning the antenna for the best possible signal reception. If set to true(1), the radio link's response to rapid changes in signal strength may potentially be affected.

INTEGER (1..2) · Integer32

This object specifies the number of antennas to be used to receive the wireless transmissions.

INTEGER (0..500000000) · Integer32 · Hz

This object specifies the bandwidth to use. Given bandwidth, the actual throughput of the radio link is determined by the cwrThroughput setting.

INTEGER1 = high2 = medium3 = low · Integer32

This represents an throughput expected of the identified radio link. There are 3 possible settings. The settings provide a tradeoff between bandwidth and the reliability of the radio link. The settings are: high(1): For a high throughput. The radio hardware will be configured such that it, favors throughput over error correction. It may not be able to correct all received errors. medium(2): This is a balance between high and low. low(3): The radio hardware is configured such that it trades off throughput for latency and error correction. It tries its very best to correct errors it detects.

INTEGER1 = bandUNII2 = bandMMDS3 = bandOther · Integer32

This object represents the portion of the frequency spectrum in which the radio PHY will operate. bandUNII(1) - The U-NII (Unlicensed National Information Infrastructure) band represents the frequency range 5725.25 to 5823.75 MHz. bandMMDS(2) - The MMDS (Multichannel Multipoint Distribution Service) band represents the frequency range 2150.75 to 2688.25 MHz. bandOther(3)- For all other frequenciy ranges.

INTEGER (0..6000000) · Integer32 · 10Khz

This object represents the center frequency that will be used to transmit data over the radio PHY. The specified transmit frequency must match the operating band and the capability of the RF resource connected to the radio.

INTEGER (0..6000000) · Integer32 · 10Khz

This object represents the center frequency that will be used to receive transmissions over the radio PHY. The specified receive frequency must match the operating band and the capability of the RF resource connected to the radio. The transmit frequency at the local end must be identical to the receive frequency at the remote end for a wireless link to be established.

INTEGER (-80..50) · Integer32 · dBm - decibel milliwatts

This object represents the power that the antenna will transmit. The minimum average transmit power for the U-NII or MMDS band is 0.01 microwatts (-80 dBm). Maximum average transmit power: For the MMDS band is 2 Watts i.e. (+33dBm). For the U-NII band is 100 milliwatts i.e. (+20dBm). The power is specified in dBm.

INTEGER (0..50) · Integer32 · dB - decibel

This object represents the measured loss in signal power in dB that is imposed by the cable connecting the radio to the antenna head. This value enables the hardware to compensate for the cable loss by adjusting the gain appropriately. A value of 0 represents no degradation in signal due to the cable. This cable loss applies to the transmit antenna identified by cwrTxRfIndex.

INTEGER1 = notOperational2 = selftest3 = download4 = txOnly5 = acquiring6 = receiveUp7 = transmitUp8 = linkOperational · Integer32

This represents the current state of a radio Link. notOperational(1): The link is not operational. selftest(2) : Power on self test in progress download(3): Image download is in progress. txOnly(4): The radio link will switch to this state if the radio link is configured for transmit only. acquiring(5): Attempting to sync up with the far end transmitter. receiveUp(6): The receive side of the radio link has successfully sync'ed up with remote end. transmitUp(7): Transmit side of the radio link is up and running. linkOperational(8): The radio link is ready for duplex communication.

INTEGER (0..50) · Integer32 · dB - decibel

This object represents the measured loss in signal power in dB that is imposed by the cable connecting the radio to the antenna head. This value enables the hardware to compensate for the cable loss by adjusting the gain appropriately. A value of 0 represents no degradation in signal due to the cable. This cable loss applies to the receive antenna identified by cwrRxRf2Index.

INTEGER1 = small2 = medium3 = large · Integer32

This object defines the time duration of the data burst sent over the air. The burst size is dependant on the capability of the ODU which is represented by the cwrBurstSizeGroup variable in the cwrRfTable. The user must set this object based on the value of cwrBurstSizeGroup in the cwrRfTable. The approximate time duration for each of the burst sizes are: small(1): 50 microseconds medium(2): 100 microseconds large(3): 200 microseconds

INTEGER (1..10000) · Integer32 · 0.01 percent

This object specifies the percentage of the total radio PHY bandwidth available to the ARQ engine. Some or all of this allocated bandwidth is used to when detected errors are corrected. The percentage will be approximated to the closest value supported by the ARQ engine.

Integer32 (1..2147483647) · milliseconds

This object identifies the latency value for voice data.

Integer32 (1..2147483647) · milliseconds

This object specifies the expected latency values for data. Reducing the latency, provides the ARQ engine less time to correct codeword errors. So if latency is reduced sufficiently, the data throughput will get effected. Also note that the latency values on both ends of the link should be kept identical, else the data throughput will be effected.

Integer32 (1..63)

This object specifies the maximum number of consecutive ARQ codewords that will be transmitted. ARQ codewords are transmitted for error correction. When an ARQ codeword is transmitted, a data codeword cannot be transmitted in that time slot, resulting jitter on the received data stream. Lower the value of the burst size, lower the peak jitter values.

Integer32 (0..45000000) · bits/sec

This object specifies the typical error free bit rate that is possible on this link given the current configuration as specified in the cwrRadioPhyTable. If the radio channel is excessively noisy then the bit rate will be lower than this value

Integer32 (0..45000000) · bits/sec

This object specifies the minimum error free bit rate that is supported on this link given the current configuration as specified in the cwrRadioPhyTable and the settings in this table.

Integer32 (1..22000) · microseconds

This object specifies the maximum latency jitter introduced by the ARQ engine, based on the settings defined in this table.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object when set to true will force the PHY quality parameters to be reset from the cwrRadioPhyTable. Reading this object will always return false. This is useful when arbitrary changes to the ARQ parameters have to be reset to known consistent valid values.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object when set to true will enable the Automatic Repeat Query subsystem. Disabling the ARQ subsystem disables a major error correction mechanism of the radio, due to which an operating radio PHY may suffer large performance degradation.

Counter64 (0..18446744073709551615)

This object identifies the number of 1 byte errors that were corrected since the the radio link reached linkOperational state.

Counter64 (0..18446744073709551615)

This object identifies the number of consecutive 2 byte errors that were corrected since the the radio link reached linkOperational state.

Counter64 (0..18446744073709551615)

This object identifies the number of consecutive 3 byte errors that were corrected since the the radio link reached linkOperational state.

Counter64 (0..18446744073709551615)

This object identifies the number of consecutive 4 byte errors that were corrected since the the radio link reached linkOperational state.

Counter64 (0..18446744073709551615)

This object identifies the number of consecutive 5 byte errors that were corrected since the the radio link reached linkOperational state.

Counter64 (0..18446744073709551615)

This object identifies the number of consecutive 6 byte errors that were corrected since the the radio link reached linkOperational state.

Counter64 (0..18446744073709551615)

This object identifies the number of consecutive 7 byte errors that were corrected since the the radio link reached linkOperational state.

Counter64 (0..18446744073709551615)

This object identifies the number of consecutive 8 byte errors that were corrected since the the radio link reached linkOperational state.

Counter64 (0..18446744073709551615)

This object identifies the number of consecutive 9 byte errors that were corrected since the the radio link reached linkOperational state.

Integer32 (1..2)

This object, along with ifIndex, represents the index of this entry in the cwrRfTable.

Integer32 (1..2147483647)

Reference: Refer to CwrRfEntityTable in CISCO-WIRELESS-EXP-MIB

This object represents the index into CwrRfEntityTable. This index identifies the radio frequency resource.

INTEGER0 = rxOnly1 = txOnly2 = rxAndTx · Integer32

This object indicates if this RF resource is being used to either receive, transmit, or both.

INTEGER (215000..582500) · Integer32 · 10 kHz

This object represents the minimum frequency at which this RF resource can transmit.

INTEGER (215000..582500) · Integer32 · 10 kHz

This object represents the maximum frequency at which this RF resource can transmit.

INTEGER (215000..582500) · Integer32 · 10 kHz

This object represents the lowest transmission frequency this RF resource can receive.

INTEGER (215000..582500) · Integer32 · 10 kHz

This object represents the highest transmission frequency that this RF resource can receive.

Integer32 (-80..33) · dBm Decibel milliwatts

This object represents the minimum power that the RF subsystem can supply the antenna.

Integer32 (-80..33) · dBm Decibel milliwatts

This object represents the maximum power that the RF subsystem can supply the antenna.

CwrOscState1 = oscillatorOk2 = osccillatorBadThe current state of the oscillator. · Integer32

This object represents the state of the transmit oscillator. The oscillator must be in oscillatorOk(1) state for the system to function properly.

Integer32 (0..2147483647)

This object represents the index into the cwrAntennaTable. This object may be 0 if the cwrAntennaTable is not available.

CwrOscState1 = oscillatorOk2 = osccillatorBadThe current state of the oscillator. · Integer32

This object represents the state of the receive oscillator. The oscillator must be in oscillatorOk(1) state for the system to function properly.

Integer32 (-40..100) · Degrees Centigrade

This object represents the current temperature of the RF unit.

INTEGER1 = withinSpecification2 = outsideSpecification · Integer32

This object specifies whether the voltage supply to the RF unit is within specifications or not.

INTEGER1 = online2 = offline · Integer32

This object specifies whether the RF resource is functioning properly or not. If it is functioning properly then it will be online(1), else offline(2).

INTEGER1 = ok2 = notOk · Integer32

Each RF resource has an associated control channel. The control channel is used to send/receive control information to the RF resource. For the RF resouce to operate properly, the control channel must be established. This object indicates the status of the control channel ok(1) - RF resource may be controlled successfully notOk(2) - Cannot talk to the RF resource.

OCTET STRING SIZE (2)

This object indicates the range or burst sizes supported by the ODU. This information is read from the ODU EEPROM. The user may set the cwrBurstSize MIB object in the cwrRadioPhyTable based on the value of this object.

CwrOscState1 = oscillatorOk2 = osccillatorBadThe current state of the oscillator. · Integer32

This object represents the state of the IF transmit oscillator. The oscillator must be in oscillatorOk(1) state for the system to function properly.

CwrOscState1 = oscillatorOk2 = osccillatorBadThe current state of the oscillator. · Integer32

This object represents the state of the IF receive oscillator. The oscillator must be in oscillatorOk(1) state for the system to function properly.

CwrOscState1 = oscillatorOk2 = osccillatorBadThe current state of the oscillator. · Integer32

This object represents the state of the IF reference oscillator. The oscillator must be in oscillatorOk(1) state for the system to function properly.

Integer32 (1..2147483647)

Reference: Refer to CwrIntFreqEntityTable in CISCO-WIRELESS-EXP-MIB

This object represents the index into CwrIntFreqEntityTable. It identifies the intermediate frequency resource.

Integer32 (100..10000) · 10 kHz

This object represents the IF input frequency.

Integer32 (20000..50000) · 10 kHz

This object represents the IF output frequency.

Unsigned32

If the number of Codeword Errors detected in a duration of 1 Operational second, is greater than this value then that second is counted as an Errored Second.

Unsigned32

This object specifies low degraded second threshold. When the number of codeword errors detected are greater or equal than this value and less than cwrLinkHighCwDSThresh then that second is counted as a Codeword Degraded Second.

Unsigned32

This object specifies high degraded second threshold. When then number of codeword errors detected are greater than this value then that second is counted as a Codeword Severely Errored Second.

Unsigned32

When the number of severely errored codewords detected consecutively in one second equals this threshold value, the second is counted as a Consecutively Severely Errored Second.

Unsigned32

This object specifies the one hour Codeword Error Second threshold. When the number of Codeword Error Seconds in a 1 Operational Hour period exceeds this limit cwrTrapLink1HrThresh trap will be generated. Time measurement starts after the first operational second.

Unsigned32

This object specifies the one hour Codeword Severely Errored Seconds threshold. When the number of Codeword Severely Errored Seconds in a 1 Operational Hour period exceeds this limit cwrTrapLink1HrThresh trap will be generated. Time measurement starts after the first operational second.

Unsigned32

This object specifies the one hour Codeword Consecutively Severely Errored Seconds threshold. When the number of Codeword Severely Errored Seconds in a 1 Operational Hour period exceeds this limit cwrTrapLink1HrThresh trap will be generated. Time measurement starts after the first operational second.

Unsigned32

This object specifies the one hour Degraded Codeword Minute threshold. When the number of Degraded Codeword Minutes in a 1 Operational Hour period exceeds this limit cwrTrapLink1HrThresh trap will be generated. Time measurement starts after the first operational second.

Unsigned32

This object specifies the 24 hour Codeword Error Second threshold. When the number of Codeword Error Seconds in a 24 Operational Hour period exceeds this limit cwrTrapLink24HrThresh trap will be generated. Time measurement starts after the first operational second.

Unsigned32

This object specifies the one hour Codeword Severely Errored Seconds threshold. When the number of Codeword Severely Errored Seconds in a 1 Operational Hour period exceeds this limit cwrTrapLink24HrThresh trap will be generated. Time measurement starts after the first operational second.

Unsigned32

This object specifies the one hour Codeword Consecutively Severely Errored Seconds threshold. When the number of Codeword Severely Errored Seconds in a 1 Operational Hour period exceeds this limit cwrTrapLink24HrThresh trap will be generated. Time measurement starts after the first operational second.

Unsigned32

This object specifies the one hour Degraded Codeword Minute threshold. When the number of Degraded Codeword Minutes in a 1 Operational Hour period exceeds this limit cwrTrapLink24HrThresh trap will be generated. Time measurement starts after the first operational second.

Counter32

This object represents the number of Available Seconds cumulated since the link was powered up. It is equal to: Error Free Seconds + Errored Seconds - Severely Errored Seconds.

Counter32

This object represents the number of seconds that the link was not available for use. It is equal to: Severely Errored Seconds + Sync Loss Seconds.

Counter32

This object represents the number of Link Admin Up Seconds during which the radio link was out of sync with the remote end.

Gauge32 (1..10000) · 0.01 percent

This object represents the ratio of cumulative Codeword Error Free Seconds (EFS) to Link Admin Up seconds, expressed as a percentage.

Gauge32 (1..10000) · 0.01 percent

This object represents the ratio of cumulative Codeword Errored Seconds (ES) to Link Admin Up seconds, expressed as a percentage.

Gauge32 (1..10000) · 0.01 percent

This object represents the ratio of cumulative Codeword Severely Errored Seconds (SES) to Link Admin Up seconds, expressed as a percentage.

Gauge32 (1..10000) · 0.01 percent

This object represents the ratio of cumulative Available seconds to Link Admin Up seconds, expressed as a percentage.

Gauge32 (1..10000) · 0.01 percent

This object represents the ratio of cumulative Codeword Degraded Minutes to Link Admin Up seconds, expressed as a percentage.

Counter32

This object represents number of times the radio link successfully synchronized with the far end.

Counter32

This object represents number of times the link attempted to synchronize with the far end but failed to.

Counter32

This object represents number of times the radio link layer was shutdown by operator intervention or a higher layer protocol.

Counter32

This object represents number of times the radio link was synchronized but lost synchronization with the remote end without manual or higher layer protocol layer intervention.

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

This object represents elapsed time since the radio link successfully synchronized with the remote end.

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

This object represents elapsed time since the radio link lost synchronization with the remote end.

Gauge32

This object represents the effective data throughput of this link while the link was synchronized.

Gauge32 (1..10000) · 0.01 percent

This object represents the ratio of total error free codewords received to the total codewords received as a percentage.

Integer32 (1..32)

Each entry represents the sum of the metrics from the previous 24 hour entry + the 24 hour period immdeiately prior to the most recent update.

Integer32 (1..2147483647) · seconds

This object represents time in seconds since system power up at which time this entry was updated.

CwrCwErrorFreeSecondA Codeword Error Free Second (EFS) is defined as 1 second when the radio link was synchronized and no codeword errors detected on the link. · Gauge32

This object represents the cumulative Codeword Error Free Seconds (EFS) detected since link power up, captured at cwr24HrUpdateTime.

CwrCwErroredSecondA Codeword Errored Second (ES) is defined as 1 second when the radio link was synchronized and 1 or more codeword errors were detected on the link. · Gauge32

This object represents the number of Codeword Error Seconds (ES) detected since link power up, captured at cwr24HrUpdateTime.

CwrCwSeverelyErroredSecondA Codeword Severely Errored Second (SES) is defined as 1 second when the radio link was synchronized and the codeword error rate (CER) was greater than the threshold specified by cwrLinkHighCwErrThresh. · Gauge32

This object represents the number of Codeword Severely Error Seconds (SES) detected since link power up, captured at cwr24HrUpdateTime.

CwrCwConsecutiveSevErrSecondA Codeword Consecutively Severely Errored Seconds (CSES) is defined as the metric that measures the number of times a sequence of Codeword Severely Errored Seconds(SES) crosses the cwrLinkCSESThresh value. It is independent of the length of the SES sequence. In other words this counter is incremented by one and only one for every such occurrence. · Gauge32

This object represents the number of Codeword Consecutively Severely Error Seconds (CSES) detected since link power up, captured at cwr24HrUpdateTime.

CwrCwDegradedMinuteA Codeword Degraded Minute (DM) is defined as a 60 Codeword Degraded Seconds. · Gauge32

This object represents the number of Codeword Degraded Minutes (DM) detected since link power up, captured at cwr24HrUpdateTime.

WirelessGauge64This is a temporary textual convention that will be deleted from this MIB when all references to this TC have been changed to use 'CounterBasedGauge64' defined in RFC 2856 (0..18446744073709551615) · Counter64

This object represents the total number of errored codewords detected since link power up, captured at cwr24HrUpdateTime.

WirelessGauge64This is a temporary textual convention that will be deleted from this MIB when all references to this TC have been changed to use 'CounterBasedGauge64' defined in RFC 2856 (0..18446744073709551615) · Counter64

This object represents the total number of codewords received on this link since link power up, captured at cwr24HrUpdateTime.

Integer32 (1..24)

Each entry represents the sum of the metrics from the previous 1 hour entry + the 1 hour period immdeiately prior to the most recent update.

Integer32 (1..2147483647) · seconds

This object represents time in seconds since system power up at which time this entry was updated.

CwrCwErrorFreeSecondA Codeword Error Free Second (EFS) is defined as 1 second when the radio link was synchronized and no codeword errors detected on the link. · Gauge32

This object represents the cumulative Codeword Error Free Seconds (EFS) detected since link power up, captured at cwr1HrUpdateTime.

CwrCwErroredSecondA Codeword Errored Second (ES) is defined as 1 second when the radio link was synchronized and 1 or more codeword errors were detected on the link. · Gauge32

This object represents the cumulative Codeword Errored Seconds (ES) detected since link power up, captured at cwr1HrUpdateTime.

CwrCwSeverelyErroredSecondA Codeword Severely Errored Second (SES) is defined as 1 second when the radio link was synchronized and the codeword error rate (CER) was greater than the threshold specified by cwrLinkHighCwErrThresh. · Gauge32

This object represents the cumulative Codeword Severely Errored Seconds (SES) detected since link power up, captured at cwr1HrUpdateTime.

CwrCwConsecutiveSevErrSecondA Codeword Consecutively Severely Errored Seconds (CSES) is defined as the metric that measures the number of times a sequence of Codeword Severely Errored Seconds(SES) crosses the cwrLinkCSESThresh value. It is independent of the length of the SES sequence. In other words this counter is incremented by one and only one for every such occurrence. · Gauge32

This object represents the cumulative Codeword Consecutive Severely Errored Seconds (CSES) detected since link power up, captured at cwr1HrUpdateTime.

CwrCwDegradedMinuteA Codeword Degraded Minute (DM) is defined as a 60 Codeword Degraded Seconds. · Gauge32

This object represents the cumulative Codeword Degraded Minutes detected since link power up, captured at cwr1HrUpdateTime.

WirelessGauge64This is a temporary textual convention that will be deleted from this MIB when all references to this TC have been changed to use 'CounterBasedGauge64' defined in RFC 2856 (0..18446744073709551615) · Counter64

This object represents the cumulative errored codewords detected since link power up, captured at cwr1HrUpdateTime.

WirelessGauge64This is a temporary textual convention that will be deleted from this MIB when all references to this TC have been changed to use 'CounterBasedGauge64' defined in RFC 2856 (0..18446744073709551615) · Counter64

This object represents the cumulative total received codewords detected since link power up, captured at cwr1HrUpdateTime.

Integer32 (1..60)

Each entry represents the sum of the metrics from the previous 1 minute entry + the 1 minute period immdeiately prior to the most recent update.

Integer32 (1..2147483647) · seconds

This object represents time in seconds since system power up at which time this entry was updated.

CwrCwErrorFreeSecondA Codeword Error Free Second (EFS) is defined as 1 second when the radio link was synchronized and no codeword errors detected on the link. · Gauge32

This object represents the cumulative Codeword Error Free Seconds (EFS) detected since link power up, captured at cwr1MinUpdateTime.

CwrCwErroredSecondA Codeword Errored Second (ES) is defined as 1 second when the radio link was synchronized and 1 or more codeword errors were detected on the link. · Gauge32

This object represents the cumulative Codeword Errored Seconds (ES) detected since link power up, captured at cwr1MinUpdateTime.

CwrCwSeverelyErroredSecondA Codeword Severely Errored Second (SES) is defined as 1 second when the radio link was synchronized and the codeword error rate (CER) was greater than the threshold specified by cwrLinkHighCwErrThresh. · Gauge32

This object represents the cumulative Codeword Severely Errored Seconds (SES) detected since link power up, captured at cwr1MinUpdateTime.

CwrCwConsecutiveSevErrSecondA Codeword Consecutively Severely Errored Seconds (CSES) is defined as the metric that measures the number of times a sequence of Codeword Severely Errored Seconds(SES) crosses the cwrLinkCSESThresh value. It is independent of the length of the SES sequence. In other words this counter is incremented by one and only one for every such occurrence. · Gauge32

This object represents the cumulative Codeword Consecutively Severely Errored Seconds (CSES) detected since link power up, captured at cwr1MinUpdateTime.

CwrCwDegradedSecondA Codeword Degraded Second (DS) is defined as a 1 second interval during which the CER was between cwrLinkLowCwErrThresh and cwrLinkHighCwErrThresh. · Gauge32

This object represents the cumulative Codeword Degraded Seconds (DS) detected since link power up, captured at cwr1MinUpdateTime.

WirelessGauge64This is a temporary textual convention that will be deleted from this MIB when all references to this TC have been changed to use 'CounterBasedGauge64' defined in RFC 2856 (0..18446744073709551615) · Counter64

This object represents the cumulative errored codewords detected since link power up, captured at cwr1MinUpdateTime.

WirelessGauge64This is a temporary textual convention that will be deleted from this MIB when all references to this TC have been changed to use 'CounterBasedGauge64' defined in RFC 2856 (0..18446744073709551615) · Counter64

This object represents the cumulative total received codewords detected since link power up, captured at cwr1MinUpdateTime.

Integer32 (1..60)

Each entry represents the sum of the metrics from the previous 1 second entry + the 1 second period immdeiately prior to the most recent update.

Integer32 (1..2147483647) · seconds

This object represents time in seconds since system power up at which time this entry was updated.

WirelessGauge64This is a temporary textual convention that will be deleted from this MIB when all references to this TC have been changed to use 'CounterBasedGauge64' defined in RFC 2856 (0..18446744073709551615) · Counter64

This object represents the cumulative total number of codewords received by this radio link at the time this entry was updated.

WirelessGauge64This is a temporary textual convention that will be deleted from this MIB when all references to this TC have been changed to use 'CounterBasedGauge64' defined in RFC 2856 (0..18446744073709551615) · Counter64

This object represents the cumulative uncorrectable codewords emitted by the Reed-Solomon error correction engine at the time this entry was updated. This is also called Pre ARQ codeword error.

Gauge32

This object represents the cumulative number of uncorrectable codewords consumed by the Automatic Repeat Query error correction engine at the time this entry was updated. This is also called as Post ARQ codeword error.

Gauge32

This represents the cumulative number of unique RR's (Retransmit Requests) received (from the remote end) at the time this entry was updated. The remote end issues a Retransmit Request if it receives an uncorrectable codeword.

Gauge32

This object represents the cumulative number of RRs (Retransmit Requests) that were serviced at the time this entry was updated.

Gauge32

This object represents cumulative number of unique ARQ's that were received by the transmit side of the local end at the time this entry was updated. This provides an indication of how error free the transmisisons of the local end of the link are from the the remote end's perspective.

Gauge32

This object represents cumulative number of ARQ's that were serviced at the time this entry was updated. A serviced ARQ results in a re-transmitted codeword.

Gauge32

This object represents the cumulative number of corrected sync byte errors, at the time this entry was updated.

Gauge32

This object represents the size of the larget block of consecutive codeword errors received since this entry was last updated.

WirelessGauge64This is a temporary textual convention that will be deleted from this MIB when all references to this TC have been changed to use 'CounterBasedGauge64' defined in RFC 2856 (0..18446744073709551615) · Counter64

This object represents the cumulative number of error free codewords emitted by the Automatic Repeat Query error correction engine at the time this entry was updated. Also called as Post ARQ good codewords.

Integer32 (1..2147483647)

This object, along with ifIndex, is the index into this table and represents one entry in the table. The entry in this table for which cwrHistIndex = x is associated with the entry in cwrHistSummaryTable and the entry in cwrHistDataTable for which the index variable in those tables has the same value, x.

CwrRadioSignalAttribute1 = rsaIN2 = rsaINR3 = rsaConstellationVariance4 = rsaTimingOffset5 = rsaReceivedPower6 = rsaGainSettingsIF7 = rsaGainSettingsRF8 = rsaFreqOffset9 = rsaTotalGain10 = rsaSyncStatusThis represents the set of radio signal attributes that may be monitored by using histograms, timelines, and thresholds. The attributes are: rsaIN(1) - This is the Interference + Noise power levels computed by the hardware on a burst by burst basis. This is available for a dual antenna system only. rsaINR(2) - This is the ratio of the interference+noise power levels captured by first antenna to that captured by the second antenna on a burst by burst basis. The values reported are in log to base 2. rsaConstellationVariance(3) - Constellation variance(CV) is the average energy of the constellation error signal. The constellation error signal is the error between the received (noisy) constellation symbol and the nearest ideal constellation symbol. CV is a measure of the Signal to Interference+noise ratio, (SINR) for that tone. On a Single antenna system it represents (1/SINR). On a Dual antenna system it represents a composite histogram providing (1/SINR). rsaTimingOffset(4) - This represents the histogram of timing delay variations detected in radio link. rsaReceivedPower(5) - This is a measure of the analog signal power received by the radio system on a burst by burst basis. rsaGainSettingsIF(6) - This represents the change in the automatic gain control loop maintained by the hardware. This may be captured for each antenna and at the intermediate frequency (IF) module. Units: Integral values rsaGainSettingsRF(7) - This represents the change in the automatic gain control loop maintained by the hardware. This may be captured for each antenna and at both the intermediate frequency (IF) and radio frequency (RF) modules. Units: Integral values rsaFreqOffset(8) - This represents the frequency offset calculations made to keep the receive frequency on a slave radio in sync with the master radio. Units: Integral values. rsaTotalGain(9) - This represents the change in the automatic gain control loop maintained by the hardware. This may be captured for each antenna. Units: Integral values rsaSyncStatus(10) - This represents the sync status. · Integer32

This object represents the attribute that is being histogrammed.

CwrRFZeroIndexThis represents an index into the cwrRFTable. The valid values are from 1 onwards. The special value of 0 is used to indicate the absence of the associated RF resource. (0..2) · Integer32

This object identifies the RF resource for which this histogram specification applies. If this is 0, the agent will automatically use the most logical value for the specified cwrHistClass. If 0 has been specified then on reading this object the agent will return the RF resource id for which the histogram is being captured.

INTEGER (0..8) · Integer32

This object identifies the DSP on which to create the histogram. If 0 is specified then the agent will automatically use the most logical DSP for the specified cwrHistClass parameter. If 0 has been specified then on reading this object the agent will return the DSP number that is being used to capture this histogram.

Integer32 (-2147483647..2147483647)

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

Integer32 (2..2147483647) · Powers of 2

This object represents the range of values of the sampled data that should be accounted for in one histogram bin. For example all data samples between x..y (where y = x + cwrBinDelta - 1), will be counted and placed in the same bin.

Integer32 (1..508)

This object represents total number of bins to be created for the histogram.

Integer32 (1..2147483647) · seconds

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

Integer32 (1..2147483647) · 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 cwrHistStatus changes to statusCaptured.

OwnerStringThis data type is used to model an administratively assigned name of the owner of a resource. Implementations must accept values composed of well-formed NVT ASCII sequences. In addition, implementations should accept values composed of well-formed UTF-8 sequences. It is suggested that this name contain one or more of the following: IP address, management station name, network manager'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 'monitor'. SNMP access control is articulated entirely in terms of the contents of MIB views; access to a particular SNMP object instance depends only upon its presence or absence in a particular MIB view and never upon its value or the value of related object instances. Thus, objects of this type afford resolution of resource contention only among cooperating managers; they realize no access control function with respect to uncooperative parties. SIZE (0..127) · OCTET STRING

This object identifies management station that created this histogram specification.

INTEGER (0..32) · Integer32

This object represents the number of bits by which the signal count is right shifted before it is stored in the histogram bin. This provides a mechanism to uniformly scale the collected histogram to account for overflows.

INTEGER1 = cwrCirculate2 = cwrAverage3 = cwrSpecific · Integer32

This object identifies which tone in a burst should be sampled for capturing the data. cwrCirculate(1): The successive tones will be used for every successive burst. cwrAverage(2): The value of every tone in a burst will be averaged. cwrspecific(3): The identified tone is used.

Integer32 (0..216)

If cwrHistToneSelection is cwrSpecificTone then this object identifies tone that should be used for sampling.

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 collection. Once the histogram collection is complete the status changes 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 another histogram specification may be started. The histogram may be read accurately between the cwrUpdateRate 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.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

The histogram data is updated every cwrUpdateRate seconds. When this object is set to true(1), the latest histogram data set is summed with the previous histogram data set and the cwrHistSummaryTable will reflect cumulative values. When set to false(2), only the latest data set is made available and the cwrHistSummarytable will reflect the latest values.

Integer32 (1..2147483647) · seconds

This object represents the time in seconds since power up when this histogram snapshot was retrieved from the hardware.

Integer32

This object represents the minimum value of the data sample seen for this histogram.

Integer32

This object represents the maximum value of the data sample seen for this histogram.

Integer32

This object represents the arithemetic mean of the data sample values for this histogram.

INTEGER (1..508) · Integer32

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

Integer32 (0..2147483647)

This object represents the value in the histogram bin cwrHistBinIndex.

Integer32 (1..2147483647)

This object, along with ifIndex, identifies this entry.

CwrRadioSignalAttribute1 = rsaIN2 = rsaINR3 = rsaConstellationVariance4 = rsaTimingOffset5 = rsaReceivedPower6 = rsaGainSettingsIF7 = rsaGainSettingsRF8 = rsaFreqOffset9 = rsaTotalGain10 = rsaSyncStatusThis represents the set of radio signal attributes that may be monitored by using histograms, timelines, and thresholds. The attributes are: rsaIN(1) - This is the Interference + Noise power levels computed by the hardware on a burst by burst basis. This is available for a dual antenna system only. rsaINR(2) - This is the ratio of the interference+noise power levels captured by first antenna to that captured by the second antenna on a burst by burst basis. The values reported are in log to base 2. rsaConstellationVariance(3) - Constellation variance(CV) is the average energy of the constellation error signal. The constellation error signal is the error between the received (noisy) constellation symbol and the nearest ideal constellation symbol. CV is a measure of the Signal to Interference+noise ratio, (SINR) for that tone. On a Single antenna system it represents (1/SINR). On a Dual antenna system it represents a composite histogram providing (1/SINR). rsaTimingOffset(4) - This represents the histogram of timing delay variations detected in radio link. rsaReceivedPower(5) - This is a measure of the analog signal power received by the radio system on a burst by burst basis. rsaGainSettingsIF(6) - This represents the change in the automatic gain control loop maintained by the hardware. This may be captured for each antenna and at the intermediate frequency (IF) module. Units: Integral values rsaGainSettingsRF(7) - This represents the change in the automatic gain control loop maintained by the hardware. This may be captured for each antenna and at both the intermediate frequency (IF) and radio frequency (RF) modules. Units: Integral values rsaFreqOffset(8) - This represents the frequency offset calculations made to keep the receive frequency on a slave radio in sync with the master radio. Units: Integral values. rsaTotalGain(9) - This represents the change in the automatic gain control loop maintained by the hardware. This may be captured for each antenna. Units: Integral values rsaSyncStatus(10) - This represents the sync status. · Integer32

This represents the attribute of a radio link which needs to be thresholded. For each of these attributes, the cwrThreshType 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 cwrThreshAttribute. An event is generated when the following condition is met.

CwrRFZeroIndexThis represents an index into the cwrRFTable. The valid values are from 1 onwards. The special value of 0 is used to indicate the absence of the associated RF resource. (0..2) · Integer32

This object identifies the RF resource for which this threshold should be defined.

Integer32 (-2147483647..2147483647)

This object represents the value to be compared against. The cwrThreshType determines the way in which it is used. It is used as follows: if cwrThreshType is .. highThresh : Notify if data sample exceeds the cwrThreshValue. lowThresh : Notify if data sample recedes below the cwrThreshValue. upChange : Notify if data sample increases by more than cwrThreshValue. downChange : Notify if data sample decreases by more than cwrThreshValue. upLimit : Notify if data sample crosses cwrThreshValue while increasing in value. lowLimit : Notify if data sample crosses cwrThreshValue 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. Notifications are not generated due to any threshold value which is reached/exceeded/crossed/etc. during this wait time

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

This object specifies the amount of time for which the radio signal should stabilize before a trap is sent to indicate that the radio signal has stabilized.

INTEGER (1..8) · Integer32

This object indicates the DSP used to monitor this threshold.

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 cwrThreshAttrClass one threshold of cwrThreshType on one DSP may be created.

Integer32 (1..2147483647)

This object, along with ifIndex, is the index into this table and represents one entry in the table. The entry in this table for which cwrTlIndex = x is associated with the entry in cwrTlSummaryTable and the entry in cwrTlDataTable for which the index variable in those tables has the same value, x.

CwrRadioSignalAttribute1 = rsaIN2 = rsaINR3 = rsaConstellationVariance4 = rsaTimingOffset5 = rsaReceivedPower6 = rsaGainSettingsIF7 = rsaGainSettingsRF8 = rsaFreqOffset9 = rsaTotalGain10 = rsaSyncStatusThis represents the set of radio signal attributes that may be monitored by using histograms, timelines, and thresholds. The attributes are: rsaIN(1) - This is the Interference + Noise power levels computed by the hardware on a burst by burst basis. This is available for a dual antenna system only. rsaINR(2) - This is the ratio of the interference+noise power levels captured by first antenna to that captured by the second antenna on a burst by burst basis. The values reported are in log to base 2. rsaConstellationVariance(3) - Constellation variance(CV) is the average energy of the constellation error signal. The constellation error signal is the error between the received (noisy) constellation symbol and the nearest ideal constellation symbol. CV is a measure of the Signal to Interference+noise ratio, (SINR) for that tone. On a Single antenna system it represents (1/SINR). On a Dual antenna system it represents a composite histogram providing (1/SINR). rsaTimingOffset(4) - This represents the histogram of timing delay variations detected in radio link. rsaReceivedPower(5) - This is a measure of the analog signal power received by the radio system on a burst by burst basis. rsaGainSettingsIF(6) - This represents the change in the automatic gain control loop maintained by the hardware. This may be captured for each antenna and at the intermediate frequency (IF) module. Units: Integral values rsaGainSettingsRF(7) - This represents the change in the automatic gain control loop maintained by the hardware. This may be captured for each antenna and at both the intermediate frequency (IF) and radio frequency (RF) modules. Units: Integral values rsaFreqOffset(8) - This represents the frequency offset calculations made to keep the receive frequency on a slave radio in sync with the master radio. Units: Integral values. rsaTotalGain(9) - This represents the change in the automatic gain control loop maintained by the hardware. This may be captured for each antenna. Units: Integral values rsaSyncStatus(10) - This represents the sync status. · Integer32

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

CwrRFZeroIndexThis represents an index into the cwrRFTable. The valid values are from 1 onwards. The special value of 0 is used to indicate the absence of the associated RF resource. (0..2) · Integer32

This object identifies the RF resource for which this timeline specification applies. If this is 0 then the agent will automatically the most logical value for the specified cwrHistClass. If 0 has been specified then on reading this object the agent will return the RF resource id for which the timeline is being captured.

INTEGER (0..8) · Integer32

This object identifies the DSP on which this timeline needs to be captures. If 0 is specified then the agent will automatically use the most logical DSP for the specified cwrTlClass parameter. If 0 has been specified on create then on reading this object the agent will return the DSP number that is being used to capture this timeline.

INTEGER (1..2147483647) · Integer32 · 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 cwrTlDataTable.

Integer32 (0..2147483647)

This object represents the number of successive data samples to be added and returned. This enables larger data sets to be captured even with limited cwrTlNumDataValues.

Integer32 (0..32)

This object represents the number of bits by which the raw data data should be right shifted before applying cwrTlDecimationFactor. This provides a mechanims of controlling overflow due to summation.

INTEGER1 = cwrCirculate2 = cwrAverage3 = cwrSpecific · Integer32

This object identifies which tone in a burst should be used to sample data for the timeline. cwrCirculate(1): The successive tone will be used for every successive burst. cwrAverage(2): The value of every tone in a burst will be averaged. cwrspecific(3): The identified tone is used. DEFVAL { cwrAverage }

Integer32 (0..216)

If cwrTlToneSelection is cwrSpecificTone then this object identifies the tone that should be used for sampling.

Integer32 (0..2147483647)

This object specifies the index of the threshold that when triggered will start the data capture for this timeline. For a timeline data capture to be triggered by a threshold, the threshold must be defined on the same DSP as the timeline. If cwrTlThreshIndex is 0 then there is no threshold associated with this timeline and the data samples are captured and returned immediately. If cwrTlThresIndex is not 0, then the data samples are captured when the threshold fires.

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 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 timeline collection. Once the timeline collection is complete the status changes 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 histogram must be actionClear'ed before another timeline specification may be started.

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.

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 cwrTlAction. The data capture depends on the value of cwrTlThreshIndex. The actual data is collected based on the cwrTlThreshIndex, if cwrTlThreshIndex is 0 then there is no stop trigger associated with this timeline and the data samples are captured and returned immediately. If cwrTlThresIndex is not 0, then the data samples are captured when the threshold fires.

Integer32 (1..2147483647) · seconds

This object represents the time in seconds since power up when this timeline capture was completed.

Integer32 (0..2147483647)

This object represents the number of values available in the timeline.

Integer32 (1..2147483647)

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

INTEGER (1..2147483647) · Integer32

This object, along with ifIndex and cwrTlIndex, is the index into the timeline data table.

Integer32

This object represents the radio signal data sampled.

INTEGER (1..8) · Integer32

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

Integer32 (1..2147483647)

This object represents the attribute that is being snapshoted by the hardware. When a snapshot request is issued up to 4 simultaneous radio signal attribute may be captured at once. The 4 attributes are specified by bit OR'ing the snapshot types identified below. When a snapshot specification is started all the specified attributes are captured simultaneously. The TX and RX types cannot be mixed. RX, Sync types can be mixed. 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) - - Sync - FreqCorr(x8000) - FLL_FFT_Sp(x20000) TX CodecIn(x200) IFFTIn(x400) =============================================== =============================================== Type Set3 Set4 =============================================== RX Y2k(x8) Y1k(x4) h1n(x10) h2n(x20) zhat(x100) - Sync FreqOffCF(x2000)(*) BrstTimeCF(x1000)(*) - TT_FCorr(x10000) TX - RoundOut(x800) =============================================== (*) BrstTimeCF cannot be mixed with Set2 (*) FreqOffCF cannot be mixed with Set1 Note that only the Tx* attributes may be captured on DSP's 1, 2. The attributes are: RxRawBurstAnt1Y1n(0x01): This represents a snapshot of the received signal for RF resource 1. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. RxRawBurstAnt2Y2n(0x02): This represents a snapshot of the received signal for RF resource 2. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. RxSpectrumAnt1Y1k(0x04): This represents a snapshot of the spectrum of the received signal for RF resource 1. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. RxSpectrumAnt2Y2k(0x08): This represents a snapshot of the spectrum of the received signal for RF resource 2. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. RxTimeDomainChannelAnt1H1n(0x10): This represents a snapshot of the time domain channel for RF resource 1. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. RxTimeDomainChannelAnt2H2n(0x20): This represents a snapshot of the time domain channel for RF resource 2. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. RxFreqDomainChannelAnt1H1k(0x40): This represents a snapshot of the frequency domain channel for RF resource 1. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. RxFreqDomainChannelAnt2H2k(0x80), This represents a snapshot of the frequency domain channel for RF resource 2. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. RxConstellationZHatk(0x100): 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. TxCodecInput(0x200): This represents a snapshot of input values to the Tx Code. Units: Real values. Value: 32 bit quantities. TxIFFTInput(0x400): This represents a snapshot of the IFFT signal for the Transmitted data. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. TxRoundOutput(0x800): This represents a snapshot of the Rounded Constellation signal for the Transmitted data. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. SyncBurstTimeCostFunc(0x1000): This represents the timing cost function for Sync bursts. Units: Real values. Value: 32 bit quantities. SynFreqOffsetCostFunc(0x2000): This represents a snapshot of the frequeny offsets. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. SyncFllFreqCorrelation(0x8000): This represents a snapshot of Frequency correlation. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. SyncFllTrainToneCorrelation(0x10000): This represents a snapshot of Frequency locked loop's Training tone correlation. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities. SyncFllFFTSpectrum(0x20000): This represents a snapshot of Frequency locked loop, FFT Spectrum. For every sample the real and imaginary components are captured. Units: (I, q) Value: 32 bit quantities.

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 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 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 first snapshot attribute value.

Integer32 (0..4096)

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

Integer32 (1..2147483647)

This object represents the second snapshot attribute value.

Integer32 (0..4096)

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

Integer32 (1..2147483647)

This object represents the third snapshot attribute value.

Integer32 (0..4096)

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

Integer32 (1..2147483647)

This object represents the third snapshot attribute value.

Integer32 (0..4096)

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

INTEGER (1..4096) · Integer32

This object represents the snapshot entry index number.

Integer32

The data sample value. Real part.

Integer32

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

Integer32 (1..16)

This object represents the index of this entry in the cwrAntennaTable.

Integer32 (1..96) · Inches

This object represents the dimension of the antenna in the X direction.

Integer32 (1..96) · Inches

This object represents the dimension of the antenna in the Y direction.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

This object represents antenna type for example 'dish-antenna'.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

This object describes the antenna.

Integer32 (0..60) · dBi : decibel Isotropic

This object represents the gain of this antenna.

INTEGER1 = vertical2 = horizontal · Integer32

This object represents the electrirc polarization of the antanna.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

The explanation string for the event trap cwrEventId.