ZHONE-PHY-WTN-RADIO-MIB: View SNMP OID List / Download MIB

Radio, modem and ODU configuration information. An entry is automatically created for each radio/modem/ODU interface.

Configuration entries

This object should be made equal to the Ifindex used for the radio interface.

Assigns one of N allowed frequency pairs for the radio transmitter and reciever as described in zhoneRadio-TC.mib. 5.7Ghz family (sysObjId) systems: --------------------------------- Writing to this value will change the current operating frequency. The active channel is the default channel used on power up. The channel is switched at the near end, and if possible, also at the far end, towards minimizing link down time. Every time the active channel number changes BITS WILL BE DROPPED. In poor conditions there is a risk that the new frequency assignment will fare more poorly. The user should expect alarms where the facility is terminated until the nodes re-sync. If a new active channel number is equal to the current value of active channel, the command will have no effect and no error message will result. Allowed range of allowed values: 0 - 17 This value will read back the current active channel. Note: if this value is changed to a new active channel number, and the system can not establish a radio link at this channel, the system may automatically switch to the standby channel, if wtnAutoChannelSwitchEnable is true(1), and the value of wtnStandbyChannelNumber is neither the same channel number nor zero. 23Ghz family (sysObjId) systems: ------------------------------- This variable is not used and so should not be presented to user. Use direct frequency assignments instead. See wtnActiveTransmitFrequency.

Current transmit frequency. As described in zhoneRadio-TC.mib. 23Ghz family: ( according to sysObjId ) ------------------------------------------- The transmit frequency is entered as a floating point number in Mhz, for example, 23565.5 for 23.5655Ghz. Note: receive frequency will also be affected by this parameter. The resulting receive frequency will be simultaneously set to this value +/- wtnChannelSeparation (plus or minus depending upon whether the unit is an A or B type ODU.) If the frequency entered or the calulated receive frequency outside the range of the unit, an error will be returned and the value left unchanged. If a new active frequency is equal to the current value frequency, the command will have no effect and no error message will result. Every time the active frequency changes BITS WILL BE DROPPED. In poor conditions there is a risk that the new frequency assignment will fare more poorly. The user should expect alarms where the facility is terminated until the nodes re-sync. If the link is operational, the new frequencies will be changed at the opposite end before the values at the local end are changed in an attempt to minimize payload data loss. 5.7Ghz family of systems (according to sysObjId ) ------------------------------------------------- Value will reflect the frequency of the currently active channel (wtnActiveChannelNumber). Writing to this variable will have no effect.

Assigns one of N allowed standby frequency pairs to the radio transmitter and reciever as described in zhoneRadio-TC.mib. 5.7Ghz family (sysObjId) systems: --------------------------------- Selection of one of N possible frequency pairs for the standby radio transmitter reciever. The Standby channel is the channel automatically switched to in the event of failure of the current active channel, for example, due to radio inteference. Automatic Switching must be enabled for the standby channel to be switched to by setting wtnAutoChannelSwitchEnable to true. If the standby channel is assigned a value of zero (0), the automatic switch to standby feature is effectively disabled, regardless of the value of wtnAutoChannelSwitchEnable. The channel is switched at the near end, and if possible, also at the far end, towards minimizing link down time. Allowed range of allowed values (see zhoneRadio-TC.mib ): 0 - 17 This value will read back the current standby channel. Operation - If a switch-to-standby channel event occurs, the active channel number and the standby channel number swap values. For example, before a radio failure: active channel = 1, standby channel = 7, and automatic channel switching is enabled. After a radio failure on channel 1: active channel = 7, standby channel = 1, and automatic channel switching is enabled. If both channels fail to operate, the system will bounce back and forth between the active and standby channels until the radio link is re-established. 23Ghz family sysObjId systems: ------------------------------- This variable is not used and so should not be presented to user. Use direct frequency assignments instead. See wtnStandbyTransmitFrequency.

Standby Transmit frequency as described in zhoneRadio-TC.mib. 23Ghz family: ( according to sysObjId ) ------------------------------------------- If auto-switching is enabled, the frequency shown will be used in the event the currently active frequency fails due to low RSSI, or high BER. Note the switch will occur only if wtnAutoChannelSwitchEnable is true(1). The transmit frequency is entered as a floating point number in Mhz, for example, 23565.5 for 23.5655Ghz. If the frequency entered or the calulated receive frequency outside the range of the unit, an error will be returned and the value left unchanged. If the link is operational, the new standby frequencies will be changed at the opposite end before the values at the local end are changed. 5.7Ghz family: (according to sysObjId ) ----------------------------------------- Value will reflect the frequency of the currently active channel (wtnStandbyChannelNumber). Writing to this variable will have no effect.

true(1) - allows radio to automatically switch to the standby channel in case of active channel interference. false(2) - inhibits radio from automatically switching to the standby channel. The default value is false(2).

23Ghz family (sysObjId) systems: --------------------------------- Channel separation - the fixed difference between transmit and receive frequency. Only three values are allowed: s1232MHz(1), s1200MHz, and s1008MHz. This value is used to automatically calculate the receive frequency, when the transmit frequency is entered. Default value: s1232Mhz(1) 5.7Ghz family (sysObjId) systems: --------------------------------- Not used. ( Internally fixed at 475MHz fixed ). Default value: na(0) Enumeration: 's1232MHz': 1, 'na': 0, 's1008MHz': 3, 's1200MHz': 2.

true(1) - Enables amplifiers for transmitter and receiver. The radio will begin transmitting and receiving data. If the ODU is looped back, unable to lock onto a signal, or the ODU equipment has failed, the enable command will return an error trap and the amplifier enable state will transition to disableAmplifiers(2). false(2) - shuts down the transmit and receive amplifiers of the ODU. This will cause the link to go down. Payload will be dropped. When the amplifiers are turned off, the active and standby channel assignments may be freely changed, if necessary, but notification of such changes to the far end will not be done automatically. That is, channel assignments made when the amplifiers are disabled must be done manually at each node - near end and far end. Default value after power up is false(2).

Set point of BER alarm. When the modem BER estimate is higher than this value, a modem BER alarm will occur. The BER over threshold Causes trap wtnBerAlarm to be emitted. The alarm will stay present until the modem BER estimate is lower than this set point less the hysteresis window wtnMdmRxBERHysteresisWindow. A value of 0 disables the BER threshold alarm. Allowed range is 1.0e-1 to 1.0e-12. BER is assumed accumulated over a second.

After a wtnBerAlarm trap is sent, it is revoked using the same trap with the condition flag set to false when the modem BER estimate is lower than the set point wtnModemRxBERThresh less this value. Valid values are 0, and the range from 1.0e-1 to 1.0e-12. A value of 0 indicates no hysteresis. BER is assumed accumulated over the last second.

Initial power of transmitter is based upon antenna diameter. oneFoot(1) - a one foot dish twoFeet(2) - a two foot dish fourFeet(4) - a four foot dish sixFeet(6) - a six foot dish FCC mandates a maximimum EIRP (Effective Isotropic Radiated Power) level, which is directly dependent upon antenna size. The system will use antenna size to determine a power level in accordance to maxmimum EIRP. 5.7Ghz family ------------------- The equipment is shipped with a dish that is one of 3 sizes: twoFeet(2) - a two foot dish fourFeet(4) - a four foot dish sixFeet(6) - a six foot dish Default value sixFeet(3). 23Ghz family ------------------- The equipment is shipped with a dish that is one of 2 sizes: oneFoot(1) - a one foot dish twoFeet(2) - a two foot dish Default value: twoFeet(2). Enumeration: 'fourFeet': 4, 'twoFeet': 2, 'sixFeet': 6, 'oneFoot': 1.

The length of the coaxial cable between the Indoor Unit and the Outdoor Unit. Used internally to compensate for the coaxial cable's natural attenuation of the signal. This cable is cut to its appropriate length when the system is installed. Default value: 0 feet.

Set point of RSSI thresholdalarm. When the ODU RSSI estimate is lower than this value, a wtnRssiDeviation trap will be emitted. When the ODU RSSI estimate is higher than this set point plus the hysteresis window wtnOduRxRSSIHysteresisWindow, the same trap will be re-emitted with condition = false.. Receive signal strength (RSSI) reported by near end ODU. Typical values range from -95dB to -30dB. Tyipcal nominal value is -60dB.

After a wtnRssiDeviation Trap is sent, an the trap is re-emitted with the condition flag set to false when the ODU RSSI estimate is higher than the set point wtnOduRxRSSIThresh plus this value. Typical value of window size is 10dB.

When true(1), radio traps may be emitted. When false(2), radio traps will be absorbed. Default value is true(1) = enabled.

loopbackOn(1) - engages the loopback function at the ODU (outdoor unit). Data normally transmitted by the radio is instead returned to the IDU (indoor unit). This is useful to check the integrity of the IDU, the integrity of the cable connecting IDU to ODU, and of some portions of ODU circuitry. ifAdminStatus must be in 'testing' mode for loopbackOn to be accepted. Once the loopback is turned on verify that there is no radio alarm condition. Also, any line data received on the line interface (DS3, STM-1, E1, etc) will be looped back and transmitted to it. loopbackOff(2) - disengages the loopback function at the ODU. Causes the radio to re-acquire the signal from the far end, if any. Enumeration: 'loopbackOn': 1, 'loopbackOff': 2.

Textual description of ODU. This string typically identifies the location of antenna.

Desired transmitter signal strength (TSSI) at antenna. Note: Accuracy decreases as power levels decrease below 20dBm. FCC maximum power allowed is +30dBm.

Contains the status of the Radio, ODU and Modem.

Entries for radio, ODU and modem status.

Current radio alarm status details. BIT Hex Decimal BIT NAME Number Value Value ------ ------ ------- ---------------------- 0 0x01 1 RSSI_DEVIATION 1 0x02 2 IDU_OOL 2 0x04 4 ODU_TEMP_ALERT 3 0x08 8 RX_BER_ALARM 4 0x10 16 RX_EBNO_ALARM 5 0x20 32 (reserved) 6 0x40 64 (reserved) 7 0x80 128 (reserved) 8 0x100 256 IDU_EQUIP_FAIL 9 0x200 512 ODU_EQUIP_FAIL 10 0x400 1024 IDU_ODU_LINK_FAIL 11 0x800 2048 MC_CHANNEL_FAIL 12 0x1000 4096 (reserved) 13 0x2000 8192 (reserved) 14 0x4000 16384 (reserved) 15 0x8000 32768 SERVICE_AFFECTED IDU_EQUIP_FAIL - can be caused by: power supply failure, watchdog timeout, or other internal failure on indoor unit. IDU_ODU_LINK_FAIL - can be caused by: IDU/ODU cable failure, bad connection, or equipment failure IDU_OOL - can be caused by: intermittent loss of lock of internal clocks MC_CHANNEL_FAIL - can be caused by: Signal path (air) degradation, or internal equipment failure on near end or far end node. ODU_EQUIP_FAIL - can be caused by: Loss of frequency lock, loss of clock reference, power fault, excessive transmitter power, signal path degradation, frequency drift, or internal failure of equipment in outdoor unit. ODU_TEMP_ALERT - can be caused by: Operating temperature too high or too low. Allowable range of operating temperatures ( in ODU ) are -40C to +65C. RSSI_DEVIATION - can be caused by: signal path (air) degradation, excessive heat buildup at ODU, or frequency drift. RX_BER_ALARM - can be caused by: RF noise burst, fade burst, interference, or internal equipment failure. RX_EBNO_ALARM - can be caused by: Fade, noise burst, or internal equipment stress. SERVICE_AFFECTED - indicates a predicted loss of data or quality of service in transport due to any of the above conditions. Bits: 'iduOduLinkFail': 10, 'unused13': 13, 'unused12': 12, 'oduTempAlert': 2, 'rxBerAlarm': 3, 'oduEquipFail': 9, 'serviceAffected': 15, 'rssiDeviation': 0, 'unused5': 5, 'unused7': 7, 'unused6': 6, 'iduOOL': 1, 'mcChannelFail': 11, 'iduEquipFail': 8, 'rxEbnoAlarm': 4, 'unused14': 14.

Time Stamp of last change of critical alarm status wtnRadioCriticalAlmStatus.

Current radio alarm status details. BIT Hex Decimal BIT NAME Number Value Value ------ ------ ------- ---------------------- 0 0x01 1 RSSI_DEVIATION 1 0x02 2 IDU_OOL 2 0x04 4 ODU_TEMP_ALERT 3 0x08 8 RX_BER_ALARM 4 0x10 16 RX_EBNO_ALARM 5 0x20 32 (reserved) 6 0x40 64 (reserved) 7 0x80 128 (reserved) 8 0x100 256 IDU_EQUIP_FAIL 9 0x200 512 ODU_EQUIP_FAIL 10 0x400 1024 IDU_ODU_LINK_FAIL 11 0x800 2048 MC_CHANNEL_FAIL 12 0x1000 4096 (reserved) 13 0x2000 8192 (reserved) 14 0x4000 16384 (reserved) 15 0x8000 32768 SERVICE_AFFECTED IDU_EQUIP_FAIL - can be caused by: power supply failure, watchdog timeout, or other internal failure on indoor unit. IDU_ODU_LINK_FAIL - can be caused by: IDU/ODU cable failure, bad connection, or equipment failure IDU_OOL - can be caused by: intermittent loss of lock of internal clocks MC_CHANNEL_FAIL - can be caused by: Signal path (air) degradation, or internal equipment failure on near end or far end node. ODU_EQUIP_FAIL - can be caused by: Loss of frequency lock, loss of clock reference, power fault, excessive transmitter power, signal path degradation, frequency drift, or internal failure of equipment in outdoor unit. ODU_TEMP_ALERT - can be caused by: Operating temperature too high or too low. Allowable range of operating temperatures ( in ODU ) are -40C to +65C. RSSI_DEVIATION - can be caused by: signal path (air) degradation, excessive heat buildup at ODU, or frequency drift. RX_BER_ALARM - can be caused by: RF noise burst, fade burst, interference, or internal equipment failure. RX_EBNO_ALARM - can be caused by: Fade, noise burst, or internal equipment stress. The SERVICE_AFFECTING bit should always = 0 on this variable because, by definition, minor alarms may not affect service. Bits: 'iduOduLinkFail': 10, 'unused13': 13, 'unused12': 12, 'oduTempAlert': 2, 'rxBerAlarm': 3, 'oduEquipFail': 9, 'serviceAffected': 15, 'rssiDeviation': 0, 'unused5': 5, 'unused7': 7, 'unused6': 6, 'iduOOL': 1, 'mcChannelFail': 11, 'iduEquipFail': 8, 'rxEbnoAlarm': 4, 'unused14': 14.

Time Stamp of last change of minor alarm status wtnRadioMinorAlmStatus.

Current temperature measured at local outdoor unit, in degrees Celsius (Centigrade).

Current frequency at which radio receiver is set.

Table augments the wtnConfigTable

Device information entries for the radio, modem and ODU.

Manufacturing Serial Number for Outdoor Unit. Format of the serial number is XXXXX, where X = 0 to F.

CLEI code for Outdoor Unit.

Table to collect statistics at radio demodulator of wireless transport node.

Entry into wireless transport local radio status table. No rows may be added to this table.

Current Received Signal Strength in dB as registered at the near end Outdoor Unit. This number is updated about once per second. Typical values range from -95dB to -30dB. Tyipcal nominal value is -60dB.

Estimated transmitter signal strength (TSSI) at antenna. Note: maximum level allowed by FCC is 30dBm.

Current received BER at local Indoor Unit demodulator over the previous 250ms.

Current local demodulator (rcvd) Energy-bit per noise. Conveys energy in each bit as compared to energy in noise.

Critical indoor equipment failure trap. Can be caused by: power supply failure, watchdog timeout, or other internal failure on indoor unit.

Non-critical indoor equipment failure trap. Can be caused by: spurious power supply failure, or other temporary internal failure on indoor unit.

Critical failure of IDU to ODU communications link trap. can be caused by: IDU/ODU cable failure, bad connection, or equipment failure.

Intermittent failure of IDU to ODU communications link trap. can be caused by: IDU/ODU cable failure, bad connection, or spurious equipment failure.

Permanent or persistant loss of lock of internal clocks in indoor unit.

Spurious or intermittant loss of lock of internal clocks in indoor unit.

Radio overhead channel failure trap. May be caused by signal path degradation, or equipment failure on local or far end node.

Spurious or intermittant radio overhead channel failure trap. May be caused by signal path degradation or equipment failure on local or far end node.

Critical ODU hardware failure trap. Possible causes: Synthesizer has lost desired frequency. Could be loss of reference signal from IDU or hardware error. Synthesizer hardware fault. Possible component fault.

Spurious or intermittant ODU hardware failure trap. Could be loss of reference signal from IDU or hardware error.

Significant deviation of ODU temperature from specified limits May be power amp heating up or environment heat buildup, or environment ice or frost.

Warning to indicate that ODU is approaching a significant deviation of ODU temperature from specified limits. May be power amp heating up or environment heat buildup, or environment ice or frost.

Receive signal strength at the odu is lower (in dB) than wtnOduRxRSSIThresh. This alarm will persist until the RSSI rises above wtnOduRxRSSIThresh - wtnOduRxRssiHysteresisWindow. May be from signal path degradation. May be power amp heating up or environment heat buildup.

Modem reports temporary BER > threshold alarm. Condition is true when current BER > wtnMdmRxBERThresh. Condition will persist until current BER < ( wtnMdmRxBERThresh - wtnMdmRxBERHysteresisWindow ). Probable fade burst. Could be interference. Could be incipient hardware fault

Modem reports temporary post-detection signal to noise ratio below preset threshold wtnMdmRxEbNoThresh. This condition will persist until the radio signal quality rises above wtnMdmRxEbNoThresh - wtnMdmRxEbnoHysteresisWindow. Probable fade or noise burst.

Sent with wireless traps to indicate whether condition has arrived or has gone away. Enumeration: 'conditionCleared': 2, 'conditionPresent': 1.

Flag sent with each trap to indicate whether service may be affected by this particular trap condition. Service affecting means that payload data (DS3, etc) MAY be affected. Since a node does not have visibility into the payloads this flag is determined by contingencies such as signal quality measurements and introspective hardware. This flag should be ignored when the trap is sent to indicate the trap condition has gone away. Enumeration: 'serviceNotAffected': 2, 'serviceAffected': 1.

Table of current statistics in the style of rfc2493 current table.

Set of basic statistics for radio interface.

Number of seconds the radio link detected bit errors since the system has been up, or since last reset. If the BER is above the user set threshhold then the readioCurrentSES count will be incremented instead of this one. If the radio link is down or a loss of signal is declared this count will not be incremented. Writing any value to this counter will reset the count.

Count of the number of seconds the radio endured severe conditions since system came up or value was reset. A severe condition occurs if: 1 - received BER is greater exceeds the BER threshold and has not yet dropped below the BER hysteresis window. 2- radio link failure. Radio signal cannot be detected. Writing any value to this counter will reset the count.

Unavailable seconds. This value is incremented once per second after ten consecutive radioCurrentSES (severe-error seconds) are counted. An equipment failure will also increment this value. Writing any value will cause the count to be reset.

Module for radio provisioning and status.