CODAN-MIB: View SNMP OID List / Download MIB

This is the MIB module for objects necessary to manage the Codan 8800 DMR device. Also NOTIFICATION-TYPEs (traps) are defined at the end of this document. Its position in the internet tree and its general structure are as follows: iso(1).org(3).dod(6).internet(1) : private(4) : enterprises(1) : codan(23304) : codanMibs(1) : minetMIB(1) : .......................................................... : : : : : : : : : : : wvStatusAndGauges(2) : wvTests(4) : wvConfiguration(1) wvPerformance(3) wvTraps(10) : :........................................................ : : : : : : : : : : wvLinkSettings(1) wvInterfaces(2) : wvManagement(3) wvRelayTable(4) : ....................................................... : : : : : : wvExternalInputTable(5) wvAlarmControl(6) wvComponentsRevisions(7) Note that in addition to the objects defined in this module, the Codan 8800 DMR supports the following objects from standard MIBs: MIB NAME GROUP OBJECT ======== ===== ====== MIB-II (RFC 1213) system sysName sysLocation sysContact sysObjectId sysDescr sysUpTime ipAddrTable ipAdEntAddr ipAdEntIfIndex ipAdEntNetMask Interfaces MIB (RFC 1573) interfaces ifNumber ifIndex ifDescr ifType ifMtu ifSpeed ifPhysAddress ifAdminStatus ifOperStatus ifLastChange ifInOctets ifInUcastPkts ifInNUcastPkts ifInDiscards ifInErrors ifInUnknownProtos ifOutOctets ifOutUcastPkts ifOutNUcastPkts ifOutDiscards ifOutErrors ifOutQLen ifSpecific snmpTraps linkUp linkDown DS1/E1 MIB (RFC 1406) dsx1ConfigTable dsx1LineIndex dsx1IfIndex dsx1LineType dsx1LineCoding dsx1LoopbackConfig dsx1TransmitClockSource dsx1LineStatus dsx1TimeElapsed dsx1CurrentESs dsx1CurrentSESs dsx1CurrentUASs dsx1CurrentDMs dsx1TotalESs dsx1TotalSESs dsx1TotalUASs dsx1TotalDMs DS3/E3 MIB (RFC 1407) dsx3ConfigTable dsx3LineIndex dsx3IfIndex dsx3LineCoding dsx3TransmitClockSource dsx3LineStatus dsx3CurrentUASs dsx3TotalUASs RS-232-like MIB (RFC 1659) rs232PortTable rs232PortIndex rs232PortInSpeed rs232PortOutSpeed rs232PortInFlowType rs232PortOutFlowType rs232PortType rs232AsyncPortTable rs232AsyncPortIndex rs232AsyncPortBits rs232AsyncPortStopBits rs232AsyncPortParity RFC 1907 snmpTraps authenticationFailure ETH-Like MIB (RFC 1643) dot3StatsTable dot3StatsIndex dot3StatsAlignmentErrors dot3StatsFCSErrors dot3StatsSingleCollisionFrames dot3StatsMultipleCollisionFrames dot3StatsSQETestErrors dot3StatsDeferredTransmissions dot3StatsLateCollisions dot3StatsExcessiveCollisions dot3StatsInternalMacTransmitErrors dot3StatsCarrierSenseErrors dot3StatsFrameTooLongs dot3StatsInternalMacReceiveErrors dot3StatsEtherChipSet NOTE: Codan 8800 DMR supports an STS-1 interface. For the purposes of this MIB, it behaves like E3/T3. Since it doesn't have a specific ifType, it's type will be 'other'.

Radio Link ID. The 2 terminals of the link must have the same linkId in order to communicate. This value should be encrypted when carried accross the network.

Radio Link Name. Limited to above size and [a-z, 0-9,-,*] because of the LCD.

Radio Link Route. Limited to above size and [a-z, 0-9,-,*] because of the LCD.

The transmit power value set for this terminal, in 1dBm steps.

The frequency channel to work on. Each channel corresponds to a given pair of transmit and receive frequencies, depending on the ODU's Standard (US/European), Spectrum Range Allocation (38 Ghz, 23 Ghz, 18 Ghz, etc...), Duplex Spacing (700 Mhz, 1200 Mhz, 1010 Mhz, etc...) and Frequency Band (1, 2, 3 or 4) (see wvOduPartNo below). The channel nos. spacing follow the h/w resolution, that is 0.25 Mhz. According to the FCC standard, each chosen frequency has a minimum spacing of 2.5 Mhz, therefore on FCC allocations the first and last allowed frequency centers are 1.25 Mhz from the start/end of the below specified bands, leaving 5 channels on start side and 4 on the end side not selectable (maybe more, depending on additional restrictions specific to each Duplex Spacing). According to the ETSI standard, each chosen frequency has a minimum spacing of 3.5 Mhz, therefore on ETSI allocations the first and last allowed frequency centers are 1.75 Mhz from the start/end of the below specified bands, leaving 7 channels on start side and 6 on the end side not selectable (maybe more, depending on additional restrictions specific to each Duplex Spacing). ******************************************************* *** For 38 Ghz, according to ITU-R F.749.1 standard *** ******************************************************* ### In the American (FCC) model ### === Duplex Spacing: 700 Mhz === The 38600-40000 Mhz frequency space is divided into 4 350 Mhz bands: 1. 38600-38950 2. 38950-39300 3. 39300-39650 4. 39650-40000 Since the h/w resolution is 0.25 Mhz, we have the 350 Mhz on each band sub-divided into 0 - 1399 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 38600.00 + (Band - 1) * 350 + wvChannelNo * 0.25 for Band = 1,2,3,4 Since the spacing between Tx and Rx is 700 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 700 Rx2 = Tx2 + 700 Rx3 = Tx3 - 700 Rx4 = Tx4 - 700 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 1400-first ### In the European (ETSI) model ### === Duplex Spacing: 1260 Mhz === The 37000-39500 Mhz frequency space is divided into 4 560 Mhz bands (after subtracting 260 MHz guard bands): 1. 37058-37618 2. 37618-38178 3. 38318-38878 4. 38878-39438 Since the h/w resolution is 0.25 Mhz, we have the 560 Mhz on each band sub-divided into 0 - 2239 channels (with 0 sitting on the START of each band). The corresponding Operating frequencies (center point) are calculated by: TxBand = 37058.00 + (Band - 1) * 630 + wvChannelNo * 0.25 for Band = 1,3 and TxBand = 37618.00 + (Band - 2) * 630 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 1260 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 1260 Rx2 = Tx2 + 1260 Rx3 = Tx3 - 1260 Rx4 = Tx4 - 1260 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 2240-first. ******************************************************** *** For 23 Ghz, according to ITU-R 637.2 standard *** ******************************************************** ### In the American (FCC) model ### === Duplex Spacing: 1200 Mhz === The 21200-23600 Mhz frequency space is divided into 4 600 Mhz bands: 1. 21200-21800 2. 21800-22400 3. 22400-23000 4. 23000-23600 Since the h/w resolution is 0.25 Mhz, we have the 600 Mhz on each band sub-divided into 0 - 2399 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 21200.00 + (Band - 1) * 600 + wvChannelNo * 0.25 for Band = 1,2,3,4 Since the spacing between Tx and Rx is 1200 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 1200 Rx2 = Tx2 + 1200 Rx3 = Tx3 - 1200 Rx4 = Tx4 - 1200 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 2400-first ### In the European (ETSI) model ### === Duplex Spacing: 1008 Mhz === On the 22000-23600 Mhz frequency space there are 2 592 Mhz bands (named bands 1 and 3 for compatibility), with a not used 'hole' of 400 Mhz in the middle, and additional guards on start and end of each band, depending on the channel spacing used (note that not all the 592 Mhz space is used): 1. 22000-22592 3. 23008-23600 Since the h/w resolution is 0.25 Mhz, we have the 592 Mhz on each band sub-divided into 0 - 2367 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 22000.00 + (Band - 1) * 504 + wvChannelNo * 0.25 for Band = 1,3 Since the spacing between Tx and Rx is 1008 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 1008 Rx3 = Tx3 - 1008 The first/last allowed wvChannelNo depends on the used channel spacing and is given in the following table: wvChannelSpacing First Last ================ ===== ==== 3.5 Mhz 18 2356 7.0 Mhz 46 2342 14.0 Mhz 60 2300 28.0 Mhz 88 2216 56.0 Mhz 312 2104 === Duplex Spacing: 1200 Mhz === The 21200-23600 Mhz frequency space is divided into 4 600 Mhz bands: 1. 21200-21800 2. 21800-22400 3. 22400-23000 4. 23000-23600 Since the h/w resolution is 0.25 Mhz, we have the 600 Mhz on each band sub-divided into 0 - 2399 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 21200.00 + (Band - 1) * 600 + wvChannelNo * 0.25 for Band = 1,2,3,4 Since the spacing between Tx and Rx is 1200 Mhz, the the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 1200 Rx2 = Tx2 + 1200 Rx3 = Tx3 - 1200 Rx4 = Tx4 - 1200 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 2400-first === Duplex Spacing: 1232 Mhz === The 21200-23600 Mhz frequency space is divided into 4 560 Mhz bands, with not used 'holes' of 24 Mhz in the beginning and end of the range and 112 Mhz in the middle: 1. 21224-21784 2. 21784-22344 3. 22456-23016 4. 23016-23576 Since the h/w resolution is 0.25 Mhz, we have the 560 Mhz on each band sub-divided into 0 - 2239 channels (with 0 sitting on the START of each band). The corresponding Operating frequencies (center point) are calculated by: TxBand = 21224.00 + (Band - 1) * 616 + wvChannelNo * 0.25 for Band = 1,3 and TxBand = 21784.00 + (Band - 2) * 616 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 1232 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 1232 Rx2 = Tx2 + 1232 Rx3 = Tx3 - 1232 Rx4 = Tx4 - 1232 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 2240-first. ******************************************************** *** For 18 Ghz, according to ITU-R F.595-5 standard *** ******************************************************** ### In the American (FCC) model ### === Duplex Spacing: 1560 Mhz === On the 17700-19700 Mhz frequency space there are 2 440 Mhz bands (named bands 1 and 3 for compatibility), with a not used 'hole' of 1120 Mhz in the middle: 1. 17700-18140 3. 19260-19700 Since the h/w resolution is 0.25 Mhz, we have the 440 Mhz on each band sub-divided into 0 - 1759 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 17700.00 + (Band - 1) * 780 + wvChannelNo * 0.25 for Band = 1,3 Since the spacing between Tx and Rx is 1560 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 1560 Rx3 = Tx3 - 1560 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 1760-first ### In the European (ETSI) model ### === Duplex Spacing: 1010 Mhz === The 17700-19700 Mhz frequency space is divided into 2 522.5 Mhz bands (Bands 1 and 3) and 2 467.5 Mhz bands (Bands 2 and 4) with a not used 'hole' of 20 Mhz in the middle, and additional guards (proportionally to the channel spacing used) on start of bands 1/3 and on end of bands 2/4: 1. 17700.0-18222.5 2. 18208.75-18690.0 3. 18710.0-19232.5 4. 19218.75-19700.0 Since the h/w resolution is 0.25 Mhz, we have the 522.5 Mhz on bands 1,3 sub-divided into 0 - 2090 channels and the 481.25 Mhz on bands 2,4 sub-divided into 0 - 1925 channels (with 0 sitting on the START of each band). The corresponding Operating frequencies (center point) are calculated by: TxBand = 17700.00 + (Band - 1) * 505 + wvChannelNo * 0.25 for Band = 1,3 and TxBand = 18208.75 + (Band - 2) * 505 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 1010 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 1010 Rx2 = Tx2 + 1010 Rx3 = Tx3 - 1010 Rx4 = Tx4 - 1010 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*4 - wvChannelSpacing/14 for Bands 1,3 first = wvChannelSpacing*2 - wvChannelSpacing/28 for Bands 2,4 last = 2090 - first(2,4) for Bands 1,3 last = 1925 - first(1,3) for Bands 2,4 *********************************************************** *** For 26 Ghz, according to EN 300 431 v1.3.1 standard *** *********************************************************** ### In the European (ETSI) model ### === Duplex Spacing: 1008 Mhz === The 24500-26500 Mhz frequency space is divided into 4 448 Mhz bands: 1. 24549-24997 2. 24997-25445 3. 25557-26005 4. 26005-26453 Since the h/w resolution is 0.25 Mhz, we have the 448 Mhz on each band sub-divided into 0 - 1791 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 24549.00 + (Band - 1) * 504 + wvChannelNo * 0.25 for Band = 1,3 TxBand = 24597.00 + (Band - 2) * 504 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 1008 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 1008 Rx2 = Tx2 + 1008 Rx3 = Tx3 - 1008 Rx4 = Tx4 - 1008 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 1792-first ************************************************************** *** For 15 Ghz, according to CEPT/ERC/REC 12-07 E standard *** ************************************************************** ### In the European (ETSI) model ### === Duplex Spacing: 728 Mhz === The 14500-15350 Mhz frequency space is divided into 2 112+7 Mhz bands: 1. 14508-14620 3. 15229-15348 Since the h/w resolution is 0.25 Mhz, we have the 119 Mhz on each band sub-divided into 0 - 475 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 14501.00 + (Band - 1) * 364 + wvChannelNo * 0.25 for Band = 1,3 Since the spacing between Tx and Rx is 728 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 728 Rx3 = Tx3 - 728 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: wvChannelSpacing First Last ================ ===== ==== 3.5 Mhz 7 441 7.0 Mhz 14 434 14.0 Mhz 56 448 28.0 Mhz 56 392 56.0 Mhz 112 336 ************************************************************** *** For 15 Ghz, according to ITU-R F.636-3 standard *** ************************************************************** ### In the European (ETSI) model ### === Duplex Spacing: 420 Mhz === The 14500-15350 Mhz frequency space is divided into 2 224 Mhz bands (Bands 1 and 3) and 2 210 Mhz bands (Bands 2 and 4) : 1. 14501-14725 2. 14718-14928 3. 14921-15145 4. 15138-15348 Since the h/w resolution is 0.25 Mhz, we have the 224 Mhz on bands 1,3 sub-divided into 0 - 895 channels and the 210 Mhz on bands 2,4 sub-divided into 0 - 839 channels (with 0 sitting on the START of each band). The corresponding Operating frequencies (center point) are calculated by: TxBand = 14501 + (Band - 1) * 210 + wvChannelNo * 0.25 for Band = 1,3 and TxBand = 14718 + (Band - 2) * 210 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 420 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 420 Rx2 = Tx2 + 420 Rx3 = Tx3 - 420 Rx4 = Tx4 - 420 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: Band 1,3 Band 2,4 wvChannelSpacing First Last First Last ================ ===== ==== ===== ==== 3.5 Mhz 7 861 7 805 7.0 Mhz 14 854 14 798 14.0 Mhz 56 840 28 812 28.0 Mhz 56 840 84 756 56.0 Mhz 112 784 140 700 ************************************************************** *** For 15 Ghz, ??? *** ************************************************************** ### In the European (ETSI) model ### === Duplex Spacing: 315 Mhz === The 14628-15228 Mhz frequency space is divided into 2 139 Mhz bands (Bands 1 and 3) and 2 151 Mhz bands (Bands 2 and 4) : 1. 14628-14767 2. 14760-14911 3. 14943-15082 4. 15075-15226 Since the h/w resolution is 0.25 Mhz, we have the 139 Mhz on bands 1,3 sub-divided into 0 - 555 channels and the 151 Mhz on bands 2,4 sub-divided into 0 - 603 channels (with 0 sitting on the START of each band). The corresponding Operating frequencies (center point) are calculated by: TxBand = 14628 + (Band - 1) * 157.5 + wvChannelNo * 0.25 for Band = 1,3 and TxBand = 14760 + (Band - 2) * 157.5 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 315 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 315 Rx2 = Tx2 + 315 Rx3 = Tx3 - 315 Rx4 = Tx4 - 315 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: Band 1,3 Band 2,4 wvChannelSpacing First Last First Last ================ ===== ==== ===== ==== 3.5 Mhz 10 528 14 588 7.0 Mhz 24 528 28 588 14.0 Mhz 80 472 56 560 28.0 Mhz 136 472 56 504 56.0 Mhz 192 416 112 448 ************************************************************** *** For 13 Ghz, according to CEPT/ERC/REC 12-02 E standard *** ************************************************************** ### In the European (ETSI) model ### === Duplex Spacing: 266 Mhz === The 12750-13250 Mhz frequency space is divided into 4 112 Mhz bands: 1. 12751-12863 2. 12863-12975 3. 13017-13129 4. 13129-13241 Since the h/w resolution is 0.25 Mhz, we have the 112 Mhz on each band sub-divided into 0 - 447 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 12751.00 + (Band - 1) * 133 + wvChannelNo * 0.25 for Band = 1,3 TxBand = 12863.00 + (Band - 2) * 133 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 266 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 266 Rx2 = Tx2 + 266 Rx3 = Tx3 - 266 Rx4 = Tx4 - 266 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 448-first ************************************************************** *** For 8 Ghz, according to ITU-R F.386-6 standard *** ************************************************************** ### In the European (ETSI) model ### === Duplex Spacing: 126 Mhz === The 8275-8500 Mhz frequency space is divided into 4 49 Mhz bands: 1. 8279-8328 2. 8321-8370 3. 8405-8454 4. 8447-8496 Since the h/w resolution is 0.25 Mhz, we have the 49 Mhz on each band sub-divided into 0 - 195 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 8279.00 + (Band - 1) * 63 + wvChannelNo * 0.25 for Band = 1,3 TxBand = 8321.00 + (Band - 2) * 63 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 126 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 126 Rx2 = Tx2 + 126 Rx3 = Tx3 - 126 Rx4 = Tx4 - 126 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 196-first Valid wvChannelSpacing are 3.5MHz,7MHz & 14MHz. ************************************************************** *** For 8 Ghz, according to ITU-R F.386-6 standard *** ************************************************************** ### In the European (ETSI) model ### === Duplex Spacing: 119 Mhz === The 8275-8500 Mhz frequency space is divided into 4 56 Mhz bands: 1. 8279-8335 2. 8321-8377 3. 8398-8454 4. 8440-8496 Since the h/w resolution is 0.25 Mhz, we have the 56 Mhz on each band sub-divided into 0 - 223 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 8279.00 + (Band - 1) * 59.5 + wvChannelNo * 0.25 for Band = 1,3 TxBand = 8321.00 + (Band - 2) * 59.5 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 119 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 119 Rx2 = Tx2 + 119 Rx3 = Tx3 - 119 Rx4 = Tx4 - 119 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 224-first Valid wvChannelSpacing are 14MHz & 28MHz. ************************************************************** *** For 8 Ghz, according to ITU-R F.386-6 standard *** ************************************************************** ### In the European (ETSI) model ### === Duplex Spacing: 311.32 Mhz === The 7725-8275 Mhz frequency space is divided into 4 127 Mhz bands: 1. 7725.00-7852.00 2. 7844.00-8971.00 3. 8036.25-8163.25 4. 8155.25-8282.25 The channel number set from the following table: ( The numbers are transmit center frequency in MHz ) Ch # Band 1 Band 2 Band 3 Band 4 0 7725.4625 7844.0625 8036.7825 8155.3825 15 7729.1687 7847.7687 8040.4887 8159.0887 30 7732.8750 7851.4750 8044.1950 8162.7950 45 7736.5812 7855.1812 8047.9012 8166.5012 60 7740.2875 7858.8875 8051.6075 8170.2075 75 7743.9937 7862.5937 8055.3137 8173.9137 90 7747.7000 7866.3000 8059.0200 8177.6200 105 7751.4062 7870.0062 8062.7262 8181.3262 120 7755.1125 7873.7125 8066.4325 8185.0325 135 7758.8187 7877.4187 8070.1387 8188.7387 150 7762.5250 7881.1250 8073.8450 8192.4450 165 7766.2312 7884.8312 8077.5512 8196.1512 180 7769.9375 7888.5375 8081.2575 8199.8575 195 7773.6437 7892.2437 8084.9637 8203.5637 210 7777.3500 7895.9500 8088.6700 8207.2700 225 7781.0562 7899.6562 8092.3762 8210.9762 240 7784.7625 7903.3625 8096.0825 8214.6825 255 7788.4687 7907.0687 8099.7887 8218.3887 270 7792.1750 7910.7750 8103.4950 8222.0950 285 7795.8812 7914.4812 8107.2012 8225.8012 300 7799.5875 7918.1875 8110.9075 8229.5075 315 7803.2937 7921.8937 8114.6137 8233.2137 330 7807.0000 7925.6000 8118.3200 8236.9200 345 7810.7062 7929.3062 8122.0262 8240.6262 360 7814.4125 7933.0125 8125.7325 8244.3325 375 7818.1187 7936.7187 8129.4387 8248.0387 390 7821.8250 7940.4250 8133.1450 8251.7450 405 7825.5312 7944.1312 8136.8512 8255.4512 420 7829.2375 7947.8375 8140.5575 8259.1575 435 7832.9437 7951.5437 8144.2637 8262.8637 450 7836.6500 7955.2500 8147.9700 8266.5700 465 7840.3562 7958.9562 8151.6762 8270.2762 480 7844.0625 7962.6625 8155.3825 8273.9825 495 7847.7687 7966.3687 8159.0887 8277.6887 Since the spacing between Tx and Rx is 311.32 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 311.32 Rx2 = Tx2 + 311.32 Rx3 = Tx3 - 311.32 Rx4 = Tx4 - 311.32 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = 15 for 7MHz, 30 for 14MHz , 60 for 28MHa last = 510 - first Valid wvChannelSpacing are 14MHz & 28MHz NOTES: 1. Valid channel numbers are n*15 n= 1,2,3...,32 2. When we display the transmit frequency the format is MMMM.KK and we trunk the least significant numbers. ************************************************************** *** For 7 Ghz, according to ITU-R F.385-6 standard *** ************************************************************** ### In the European (ETSI) model ### === Duplex Spacing: 245 Mhz === The 7425-7900 Mhz frequency space is divided into 4 112 Mhz bands: 1. 7428-7540 2. 7540-7652 3. 7673-7785 4. 7785-7897 Since the h/w resolution is 0.25 Mhz, we have the 56 Mhz on each band sub-divided into 0 - 447 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 7428.00 + (Band - 1) * 122.5 + wvChannelNo * 0.25 for Band = 1,3 TxBand = 7540.00 + (Band - 2) * 122.5 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 245 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 245 Rx2 = Tx2 + 245 Rx3 = Tx3 - 245 Rx4 = Tx4 - 245 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 448-first ************************************************************** *** For 7 Ghz, according to ITU-R F.385-6 standard *** ************************************************************** ### In the European (ETSI) model ### === Duplex Spacing: 154 Mhz === The 7125-7425 or 7425-7725 or 7250-7558 or 7550-7850 Mhz frequency space is divided into 2 84 Mhz bands (Bands 1 and 3) and 2 56 Mhz bands (Bands 2 and 4) : 1. 7128-7212 or 7428-7512 or 7253-7337 or 7553-7637 2. 7212-7268 or 7512-7568 or 7337-7393 or 7637-7693 3. 7282-7366 or 7582-7666 or 7407-7491 or 7707-7791 4. 7366-7422 or 7666-7722 or 7491-7547 or 7791-7847 Since the h/w resolution is 0.25 Mhz, we have the 84 Mhz on bands 1,3 sub-divided into 0 - 335 channels and the 56 Mhz on bands 2,4 sub-divided into 0 - 223 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = (7128.00 or 7428.00 or 7253 or 7553) + (Band - 1) * 77.0 + wvChannelNo * 0.25 for Band = 1,3 TxBand = (7212.00 or 7512.00 or 7337 or 7637) + (Band - 2) * 77.0 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 154 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 154 Rx2 = Tx2 + 154 Rx3 = Tx3 - 154 Rx4 = Tx4 - 154 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 336-first for bands 1,3 last = 224-first for bands 2,4 ************************************************************** *** For 7 Ghz, according to ITU-R F.385-6 standard *** ************************************************************** ### In the European (ETSI) model ### === Duplex Spacing: 161 Mhz === The 7124.5-7425.5 or 7424.5-7725.5 Mhz or 7249.5-7550.5 frequency space is divided into 2 84 Mhz bands (Bands 1 and 3) and 2 56 Mhz bands (Bands 2 and 4) : 1. 7124.5-7208.5 or 7424.5-7508.5 or 7249.5-7333.5 2. 7208.5-7264.5 or 7508.5-7564.5 or 7333.5-7389.5 3. 7285.5-7369.5 or 7585.5-7669.5 or 7410.5-7494.5 4. 7369.5-7425.5 or 7669.5-7725.5 or 7494.5-7550.5 Since the h/w resolution is 0.25 Mhz, we have the 84 Mhz on bands 1,3 sub-divided into 0 - 335 channels and the 56 Mhz on bands 2,4 sub-divided into 0 - 223 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = (7124.50 or 7424.50 or 7249.50) + (Band - 1) * 80.5 + wvChannelNo * 0.25 for Band = 1,3 TxBand = (7208.50 or 7508.50 or 7333.50) + (Band - 2) * 80.5 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 161 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 161 Rx2 = Tx2 + 161 Rx3 = Tx3 - 161 Rx4 = Tx4 - 161 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 336-first for bands 1,3 last = 224-first for bands 2,4 ### In the European (ETSI) model 15GHz Australia ITU-R F.636-3### === Duplex Spacing: 644 Mhz === On the 14500-15350 Mhz frequency space there are 2 196 Mhz bands (named bands 1 and 3 for compatibility), with a not used 'hole' of 448 Mhz in the middle, and additional guards on start and end of each band, depending on the channel spacing used : 1. 14501-14697 3. 15145-15341 Since the h/w resolution is 0.25 Mhz, we have the 196 Mhz on each band sub-divided into 0 - 783 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 14501.00 + (Band - 1) * 98 + wvChannelNo * 0.25 for Band = 1,3 Since the spacing between Tx and Rx is 644 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 644 Rx3 = Tx3 - 644 The first/last allowed wvChannelNo depends on the used channel spacing and is given in the following table: first = wvChannelSpacing*10/5 last = 784-first ### In the European (ETSI) model 15GHz Australia ### === Duplex Spacing: 490 Mhz === On the 14403-15348 Mhz frequency space there are 4 224 Mhz bands (named bands 1 to 4 for compatibility): 1. 14403-14627 2. 14627-14821 3. 14893-15117 4. 15117-15341 Since the h/w resolution is 0.25 Mhz, we have the 224 Mhz on each band sub-divided into 0 - 895 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 14403.00 + (Band - 1) * 112 + wvChannelNo * 0.25 for Band = 1,3 and TxBand = 14627.00 + (Band - 2) * 112 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 490 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 490 Rx2 = Tx2 + 490 Rx3 = Tx3 - 490 Rx4 = Tx4 - 490 The first/last allowed wvChannelNo depends on the used channel spacing and is given in the following table: first = wvChannelSpacing*10/5 last = 896-first ### In the European (ETSI) model 15GHz Australia ### === Duplex Spacing: 322 Mhz === The 14634-15229 Mhz frequency space is divided into 2 126 Mhz bands (Bands 1 and 3) and 2 140 Mhz bands (Bands 2 and 4) : 1. 14634-14760 2. 14767-14907 3. 14956-15082 4. 15089-15229 Since the h/w resolution is 0.25 Mhz, we have the 126 Mhz on bands 1,3 sub-divided into 0 - 504 channels and the 140 Mhz on bands 2,4 sub-divided into 0 - 560 channels (with 0 sitting on the START of each band). The corresponding Operating frequencies (center point) are calculated by: TxBand = 14634 + (Band - 1) * 63 + wvChannelNo * 0.25 for Band = 1,3 and TxBand = 14760 + (Band - 2) * 70 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 322 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 322 Rx2 = Tx2 + 322 Rx3 = Tx3 - 322 Rx4 = Tx4 - 322 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 504-first (for band 1,3) last = 560-first (for band 2,4) ### In the European (ETSI) model 10GHz Australia ITU-R F.747### === Duplex Spacing: 65 Mhz === On the 10550-10680 Mhz frequency space is divided into 2 35 Mhz bands (Bands 1 and 3) and 2 30 Mhz bands (Bands 2 and 4) :: 1. 10550-10585 2. 10582.5-10615 3. 10615-10650 4. 10647.5-10680 Since the h/w resolution is 0.25 Mhz, we have the 35 Mhz on bands 1,3 sub-divided into 0 - 139 channels and the 32.5 Mhz on bands 2,4 sub-divided into 0 - 129 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 10550 + (Band - 1) * 32.5 + wvChannelNo * 0.25 for Band = 1,3 TxBand = 10582.5 + (Band - 2) * 32.5 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 65 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 65 Rx2 = Tx2 + 65 Rx3 = Tx3 - 65 Rx4 = Tx4 - 65 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 140-first for bands 1,3 last = 130-first for bands 2,4 ### In the European (ETSI) model 10GHz Australia ITU-R F.747### === Duplex Spacing: 91 Mhz === On the 10500-10680 Mhz frequency space is divided into 4 42 Mhz bands: 1. 10500.5-10542.5 2. 10542.5-10584.5 3. 10591.5-10633.5 4. 10633.5-10675.5 Since the h/w resolution is 0.25 Mhz, we have the 42 Mhz on each band sub-divided into 0 - 167 channels (with 0 sitting on the START of each band). The corresponding Operating Frequencies (center point) are calculated by: TxBand = 10500.5 + (Band - 1) * 45.5 + wvChannelNo * 0.25 for Band = 1,3 TxBand = 10542.5 + (Band - 2) * 45.5 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 119 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 91 Rx2 = Tx2 + 91 Rx3 = Tx3 - 91 Rx4 = Tx4 - 91 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*10/5 last = 168-first ### In the European (ETSI) model 18GHz ### === Duplex Spacing: 1008 Mhz === The 17720.5-19680.5 Mhz frequency space is divided into 2 500.5 Mhz bands (Bands 1 and 3) and 2 451.5 Mhz bands (Bands 2 and 4) with a not used 'hole' of 56 Mhz in the middle. 1. 17702.5-18221.0 2. 18221.0-18672.5 3. 18728.5-19229.0 4. 19229.0-19700.5 Since the h/w resolution is 0.25 Mhz, we have the 500.5 Mhz on bands 1,3 sub-divided into 0 - 2002 channels and the 451.5 Mhz on bands 2,4 sub-divided into 0 - 1806 channels (with 0 sitting on the START of each band). The corresponding Operating frequencies (center point) are calculated by: TxBand = 17702.5 + (Band - 1) * 500.5 + wvChannelNo * 0.25 for Band = 1,3 and TxBand = 18221.0 + (Band - 2) * 451.5 + wvChannelNo * 0.25 for Band = 2,4 Since the spacing between Tx and Rx is 1010 Mhz, the Rx frequency is deduced from the Tx frequency as follows: Rx1 = Tx1 + 1008 Rx2 = Tx2 + 1008 Rx3 = Tx3 - 1008 Rx4 = Tx4 - 1008 The first/last allowed wvChannelNo depends on the used channel spacing and is calculated as follows: first = wvChannelSpacing*4 - wvChannelSpacing/14 for Bands 1,3 first = wvChannelSpacing*2 - wvChannelSpacing/28 for Bands 2,4 last = 2002 - first(2,4) for Bands 1,3 last = 1806 - first(1,3) for Bands 2,4 wvChannelNo's default is the first allowed Channel No, according to the chosen channel spacing.

Terminal Link chosen bit rate. Enables reduced capacity work for a given installed plug-in (according to wvInstalledPlugInPartNo). All subsets of a given plug-in are allowed. Its default is the installed plug-in full capacity. Enumeration: 'eth10-100PlusTwoE1': 20, 'sixteenE1': 5, 'eth10-100PlusOneE1': 19, 'e3PlusOneE1': 7, 'eth10-100Only': 18, 'twoE1': 2, 'e3PlusTwoE1': 8, 'fourE1': 3, 'eth10-100PlusFourE1': 21, 't3PlusTwoT1': 15, 'twoT1': 10, 'eth10-100PlusTwoT1': 23, 'eth10-100PlusOneT1': 22, 'eightT1': 12, 't3PlusFourT1': 16, 'eightE1': 4, 'oneE1': 1, 'fourT1': 11, 'e3': 6, 'oneT1': 9, 'sts1': 17, 't3': 14, 'eth10-100PlusFourT1': 24, 'sixteenT1': 13.

When 'on', disables this terminal's transmission to the link. Note that disabling transmission sets off an alarm. Enumeration: 'on': 1, 'off': 2.

When 'on', disables this terminal's reception from the link. Since disabling reception is regarded as a kind of alarm, setting of this variable causes a trap. Enumeration: 'on': 1, 'off': 2.

Sets the terminal radio modulation. Not all values apply to all models. Enumeration: 'qam4': 3, 'qam64': 7, 'qam128': 8, 'cp4fsk': 2, 'qam8': 4, 'qam32': 6, 'qam16': 5.

Defines whether to force Alarm Indication Signal (all 1's) on the link upon either occurence of a link BER Warning or BER Error alarm or unconditionally. Enumeration: 'always': 4, 'never': 1, 'onBerError': 3, 'onBerWarning': 2.

Enables/disables the Forward Error Correction option. Enumeration: 'on': 1, 'off': 2.

Enables/disables Automatic Error Correction on receive. Enumeration: 'on': 1, 'off': 2.

Specifies the Forward Error Correction level on transmit. - for LAN plug-in the values are 10 or 20. - for PDH plug-in the values are read only.

Specifies the allowed frequency spacing between adjacent channels for the ETH 10/100 plug-in, as a function of the ODU standard (American vs. European) and chosen wvLinkCapacity. The user may specify a given spacing only if the chosen wvLinkCapacity is one of the specified on its right. Note that on the 18 Ghz Spectrum Range the actual values may be different than on the other ranges, and those are specifically mentioned where applicable. When working with ETH 10/100 plug-in, wvChannelSpacing reflects this object's value. Enumeration: 'seven': 8, 'twentyEight': 10, 'twentyFive': 5, 'twelveAndAHalf': 4, 'fifty': 6, 'fourteen': 9, 'sevenAndAHalf': 3, 'twoAndAHalf': 1, 'five': 2, 'fiftySix': 11, 'threeAndAHalf': 7.

Enables/disables the ATPC feature. Enumeration: 'disabled': 2, 'enabled': 1.

Defines the targeted working RSL value, for ATPC.

Defines the upper threshold for which, if the RSL value is greater than it for more than 10 seconds, the ATPC mechanism (if enabled) will decrease the remote TX power to get the RSL to wvAtpcRslOptimalValue.

Defines the lower threshold for which, if the RSL value is less than it for more than 10 seconds, the ATPC mechanism (if enabled) will increase the remote TX power to get the RSL to wvAtpcRslOptimalValue.

Enables/disables the Pause Transmitter feature. Enumeration: 'disabled': 2, 'enabled': 1.

Defines the time in seconds to hold the pause for the transmitter in mute state.

set E1 port to 75ohm. Enumeration: 'on': 1, 'off': 2.

Enables/disables the ATPC TimeOut feature. Enumeration: 'disabled': 2, 'enabled': 1.

Atpc TimeOut timer feature.

Enables/disables the ATPC TimeOut alarm. Enumeration: 'disabled': 2, 'enabled': 1.

declare the ATPC TimeOut alarm level. Enumeration: 'message': 1, 'fatal': 3, 'error': 2.

Disable the ATPC if TimeOut alarm in active. Enumeration: 'on': 1, 'off': 2.

Enable the Space Diversity feature in 1+1 mode. Enumeration: 'on': 1, 'off': 2.

Defines the data ports connections mode. In Auto Sensing mode the system automatically detects which ports are connected. In Manual mode user choices are reflected through the interfaces wvTributaryPortConnection settings (see below). Enumeration: 'manual': 1, 'autoSensing': 2.

A table for private extensions to standard interface MIBs (like dsx1/dsx3).

Entry in the wvTributaryPortTable.

The value of this object is equal to the value of ifIndex for the corresponding interface on the Interfaces table of MIB-II. Note that the possible wvTributaryPortIfIndex values depend on the available interfaces, according to wvInstalledPlugInPartNo.

Determines if this port is connected or not. Note that the maximum number of connected ports is a subset of the available data ports (according to wvInstalledPlugInPartNo), and can not exceed the chosen wvLinkCapacity. The default connections are the first ones available. Applicable only when wvTributaryPortConnectionsMode is set to manual. Enumeration: 'disabled': 1, 'enabled': 0.

Determines if this line has inverted alarm enabled. A line with inverted alarm enabled will report an alarm if either 'no LOS' or 'AIS' is detected (meaning that the line is alive). This condition is indicated as Unexpected Signal Detection alarm. The default is disabled (not inverted). Enumeration: 'disabled': 2, 'enabled': 1.

Specifies the prefix string for Tributary Port.

Defines the cable length range of the DS3/E3 line, for proper interface support. Enumeration: 'moreThan225Feet': 2, 'upTo225Feet': 1.

Defines the type of SLIP connection to the IDU. ??? Couldn't this be self detectable ??? Enumeration: 'modem': 2, 'direct': 1.

Specifies the telephone number for dial-back purposes (e.g., for TFTP connection).

Specifies the prefix string for modem dial up .

Specifies the string to be sent to the modem for initialization .

Specifies General ETH 10/100 Board controls. Bits: 'aging': 0, 'crcCheck': 1, 'flowCtrl': 2.

Specifies ETH 10/100 Board Aging Time. Given value will be rounded down to highest multiple of 8.

A table for ETH 10/100 ports.

Entry in the wvEth10-100PortTable.

The value of this object is equal to the value of ifIndex for the corresponding interface on the Interfaces table of MIB-II. Note that the possible wvEth10-100PortIfIndex values depend on the available interfaces, according to wvInstalledPlugInPartNo.

Specifies specific ETH 10/100 Port controls. Bits: 'forceDisconnectOnLinkDown': 3, 'fastSpeed': 0, 'fullDuplex': 1, 'autoNegotiation': 2.

Keeps the specific ETH 10/100 Port status. Bits: 'cslAlarm': 2, 'imteAlarm': 4, 'fastSpeedOn': 0, 'ecAlarm': 3, 'imreAlarm': 5, 'fullDuplexOn': 1.

Setting of this object clears the specific ETH 10/100 port statistics. The value given with the object is not relevant and it's not checked.

Specifies specific ETH 10/100 Port Throughput controls. Enumeration: 'unlimited': 1, 'limit8M': 8, 'limit1M': 5, 'limit128K': 2, 'limit512K': 4, 'limit2M': 6, 'limit256K': 3, 'limit4M': 7.

Shows the link capacity available for the ETH 10/100, after deducting the capacity used by the DS1s from the total available spectrum.

A list of port entries. The number of entries is given by the value of rs232Number.

Status and parameter values for a port.

Same as original rs232PortIndex: The value of ifIndex for the port. By convention and if possible, hardware port numbers map directly to external connectors. The value for each port must remain constant at least from one re-initialization of the network management agent to the next.

The port's hardware type. Same as original rs232PortType, but read-write and with restricted values. Enumeration: 'rs232': 2, 'rs422': 3.

The port's input/output speed in bits per second. Note that non-standard values, such as 9612, are probably not allowed on most implementations. Same as original rs232PortInSpeed and rs232PortOutSpeed.

The port's type of input flow control. 'none' indicates no flow control at this level. Same as original rs232PortInFlowType and rs232PortOutFlowType, but with different values. Enumeration: 'none': 1, 'xonXoff': 2.

The port's number of bits in a character. Same as original rs232AsyncPortBits, but with restricted values.

The port's number of stop bits. Same as original rs232AsyncPortStopBits, but with restricted values. Enumeration: 'two': 2, 'one': 1.

The port's sense of a character parity bit. Same as original rs232AsyncPortParity, but with restricted values. Enumeration: 'even': 3, 'none': 1, 'odd': 2.

Initializes a configuration update process from the manager to either the Active or one of the Saved Configurations on the terminal. The actual updated configuration is specified through the community in the request, as explained below on the wvCommunityTable Description. If the Update is to one of the Saved Configurations then it is saved on non-volatile memory. If the Update is to the Active Configuration then the changed parameters are activated. The value given with the object is not relevant and it's not checked.

Initializes a configuration transfer process on the terminal from one of the Saved Configurations to the Active Configuration, according to wvActivateTerminalConfigurationTime (see below). The actual activated configuration is specified through the community in the request, as explained below on the wvCommunityTable Description. The value given with the object is not relevant and it's not checked.

Activates a cold/warm reset at the terminal. A cold reset is performed at both the IDU and the ODU and stops all communications with the device. A warm reset affects only IDU NMS operation and doesn't interrupt data communications. A cold switch-over reset, in addition to performing a cold reset, causes the IDU to restart with the stand-by software (see wvSwModuleTable) becoming the active one, and the active software becoming the stand-by one. Enumeration: 'terminalSwitchOver': 4, 'coldSwitchOver': 3, 'running': 5, 'warm': 2, 'cold': 1, 'oduSwitchOver': 6.

Defines the time, relative to sysUpTime, when the wvActivateTerminalConfiguration request should be performed. If when set this value is 0 then the the activation is performed immediately.

Specifies which of the Saved Configurations currently reflects the Active Configuration. It is set to 'none' following a successful wvUpdateTerminalConfiguration to the Active Configuration. It is set to any of the other values following a successful wvActivateTerminalConfiguration request, according to the specified configuration. Enumeration: 'savedConfiguration1': 1, 'savedConfiguration2': 2, 'savedConfiguration3': 3, 'none': 5, 'factoryDefault': 4.

For 1+1 systems only: Simulates a 'Switch-Out' request on the current unit. If not a 1+1 system, the request is rejected. The value given with the object is not relevant and it's not checked.

Specifies the Password for User privilege Front Panel access.

Specifies the Password for Admin privilege Front Panel access.

Specifies the Password for Supervisor privilege Front Panel access.

Activates an ODU only cold reset. This will cause the link to be restarted. A cold switch-over reset, in addition to performing a cold reset, causes the ODU to restart with the stand-by software (see wvSwModuleTable) becoming the active one, and the active software becoming the stand-by one. Enumeration: 'cold': 1, 'running': 3, 'coldSwitchOver': 2.

The terminals' Slip-In IP address.

The subnet mask associated with wvSlipInIPAddress. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

The terminals' Slip-Out IP address.

The subnet mask associated with wvSlipOutIPAddress. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

The terminals' LAN IP address.

The subnet mask associated with wvLanIPAddress. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

The terminals' link IP address.

The subnet mask associated with wvLinkIPAddress. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

The terminals' ETH 10/100 IP address.

The subnet mask associated with wvEth10-100ManIPAddress. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

The peer terminals' Slip-In IP address.

The subnet mask associated with wvPeerSlipInIPAddress. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

The peer terminals' Slip-Out IP address.

The subnet mask associated with wvPeerSlipOutIPAddress. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

The peer terminals' LAN IP address.

The subnet mask associated with wvPeerLanIPAddress. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

The peer terminals' link IP address.

The subnet mask associated with wvPeerLinkIPAddress. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

The peer terminals' ETH 10/100 IP address.

The subnet mask associated with wvPeerEth10-100ManIPAddress. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

The IP address of the destination connected to the Slip-In port.

The subnet mask associated with wvSlipInDestIPAddress. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

The IP address of the destination connected to the Slip-Out port.

The subnet mask associated with wvSlipOutDestIPAddress. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

The companion terminals' link IP address. VAlid only if system is a '1+1', according to wvOnePlusOneStatus.

The Companion Eth(LAN)IP address in '1+1' system.

A table of the user defined static routes.

Entry in the wvUserRoutesTable. The table has a variable size, limited to the range specified by wvUserRoutesIndex below. Deletion of a row is achieved by setting wvUserRoutesType to value. Creation of a new route is achieved by setting any of the read-write fields with a index = Current-Last-Index + 1.

The entry index.

The route destination.

The route hop.

The route mask.

Set requested interface for the route . Enumeration: 'eth10-100': 2, 'nms-in': 4, 'sys-choice': 6, 'link': 3, 'eth': 1, 'nms-out': 5.

Set for route deleting . Enumeration: 'valid': 1, 'invalid': 2.

The number of entries in User Routes Table.

This object identifies the current successful invocation of the set operation.

This object synchronizes between several cooperating manager stations, to coordinate their use of the set operation. If it is set to 'setDisabled' no SNMP set operations are performed by the agent. Enumeration: 'setEnabled': 1, 'setDisabled': 2.

The entity which currently has the 'ownership' required to perform set operations.

A bit is set for a family by the agent to indicate that a configuration parameter in the corresponding family has been changed. It is the manager's responsibility to reset set bits. Bits: 'wvManagement': 9, 'dsx1ConfigTable': 6, 'filler': 0, 'interfaces': 3, 'wvInterfaces': 2, 'ifTestTable': 4, 'system': 10, 'wvExternalInputTable': 12, 'dsx3ConfigTable': 7, 'wvRelayTable': 11, 'wvTests': 14, 'wvAlarmControl': 13, 'rs232': 8, 'ipAddrTable': 5, 'wvLinkSettings': 1.

A table of SNMP community settings.

Entry in the wvCommunityTable. The table has a variable size, limited to the range specified by wvCommunityId below. Deletion of a row is achieved by setting wvCommunityName to the NULL string. Creation of a new row is achieved by setting wvCommunityName with a non-existing index to a non-NULL string. Setting of wvCommunityPrivilege with a non-existing index is rejected.

The entry index.

The name of the community.

Sets the privilege of the community which name is given by wvCommunityName . Enumeration: 'readWrite': 2, 'readOnly': 1.

A table of SNMP trap managers IP addresses.

Entry in the wvTrapRecipientsTable. The table has a variable size, limited to the range specified by wvTrapRecipientsId below. Deletion of a row is achieved by setting wvTrapRecipientsId to 0.0.0.0. Creation of a new row is achieved by setting wvTrapRecipientsId with a non-existing index to any value different than 0.0.0.0.

The entry index.

The IP Address of the manager to receive the trap.

Defines the IP Address of the TFTP server.

When disabled no TFTP can be performed. This allows a high privilege authority to disallow lower privilege managers to initialize TFTP from this terminal. Note that since the agent has no notion of privilege levels (user/admin/supervisor) it has no means to check authentication of the entity setting this object, and the privilege distinctions are made at the managers' level. Enumeration: 'disabled': 2, 'enabled': 1.

Determines the no. of retries to be performed by the terminal upon TFTP failures. A value of 0 means to try forever until successful or deliberately stopped.

Defines the full name of the file to be TFTP'ed.

Defines the desired delay time, in time-ticks, before the TFTP is started. When TFTP is on, either on delay or started, setting wvTftpStartTime to 0 forces a premature stop.

Defines the ongoing remaining time before the TFTP starts.

The Terminal Software Modules table.

Entry in the wvSwModuleTable.

An index to the Software Modules Table.

The software module name. For example: Kernel, Agent.

The module active software revision. This string will have a zero length if the revision is unknown.

The module active software check-sum.

The module stand-by software revision. This string will have a zero length if the revision is unknown.

The module stand-by software check-sum.

When setting to 'on' it will Reset the Performance parameters. Reading this object will return allways 'off'. Enumeration: 'on': 1, 'off': 2.

A table of relays settings. There are 7 entries in the table: 5 actual relays, a buzzer as 6th entry and a general purpose external TTL output as 7th entry.

Entry in the wvRelayTable.

The entry index.

Enables/disables given relay. Enumeration: 'disabled': 2, 'enabled': 1.

Defines the normal state of the relay or TTL out. Buzzer normal state is always off, and can not be chosen. Enumeration: 'open': 1, 'closed': 2.

Manually activates the relay. Enumeration: 'on': 2, 'off': 1.

Bits in the list set to on will cause the given relay to be activated when any of the corresponding local alarms occur.

Bits in the list set to on will cause the given relay to be activated when any of the corresponding remote alarms occur.

Describes the current state of the given relay. Enumeration: 'open': 1, 'closed': 2.

A table of external inputs settings.

Entry in the wvExternalInputTable.

The entry index.

Enables/disables given external input. Enumeration: 'disabled': 2, 'enabled': 1.

Sets the sense on which the input alarm is defined as active. Enumeration: 'high': 2, 'anyChange': 3, 'low': 1.

Defines the alarm severity of given input. Enumeration: 'fatal': 3, 'warning': 1, 'error': 2.

Describes the current state of the given input. Enumeration: 'active': 1, 'notActive': 2.

Defines the severity level of the alarms to be asynchronoulsy reported by the agent to the managers specified in the wvTrapRecepientsIpTable. Enumeration: 'all': 1, 'errorAndFatal': 2, 'fatalOnly': 3, 'none': 4.

Defines the severity level of the alarms to be displayed at the front panel LCD. Enumeration: 'all': 1, 'errorAndFatal': 2, 'fatalOnly': 3, 'none': 4.

Limits the number of alarms to be displayed at the front panel LCD.

Defines the high water mark above which the terminal enters the link BER warning alarm state. If wvLinkxxxBER in a given wvLinkThresholdMeasurementInterval gets above this value a wvlinkBERWarningAlarm is set, to be canceled if the value gets below wvLinkBERWarningThresholdLow (see below).

Defines the low water mark below which the terminal exits the link BER warning alarm state.

Defines the high water mark above which the terminal enters the link BER error alarm state. If wvxxxlinkBER in a given wvLinkThresholdMeasurementInterval gets above this value a wvlinkBERFailureAlarm is set, to be canceled if the value gets below wvLinkBERErrorThresholdLow (see below).

Defines the low water mark below which the terminal exits the link BER error alarm state.

Defines the high water mark above which the terminal enters the link Blocks Error Rate alarm state. If wvLinkxxxBLER in a given wvLinkThresholdMeasurementInterval gets above this value a wvlinkBLERAlarm is set, to be canceled if the value gets below wvLinkBLERAlarmThresholdLow (see below).

Defines the low water mark below which the terminal exits the link Blocks Error Rate alarm state.

Defines the high water mark above which the terminal enters the link Blocks Background Error Rate alarm state. If wvLinkxxxBBER in a given wvLinkThresholdMeasurementInterval gets above this value a wvlinkBBERAlarm is set, to be canceled if the value gets below wvLinkBBERAlarmThresholdLow (see below).

Defines the low water mark below which the terminal exits the link Blocks Error Rate alarm state.

Defines the high water mark above which the terminal enters the link Not Corrected Blocks Error Rate alarm state. If wvLinkxxxNCBLER in a given wvLinkThresholdMeasurementInterval gets above this value a wvLinkNCBLERAlarm is set, to be canceled if the value gets below wvLinkNCBLERAlarmThresholdLow (see below).

Defines the low water mark below which the terminal exits the link Not Corrected Blocks Error Rate alarm state.

Defines the high water mark above which the terminal enters the link Errored Seconds alarm state. If wvLinkxxxESs in a given wvLinkThresholdMeasurementInterval gets above this value a wvLinkESAlarm is set, to be canceled if the value gets below wvLinkESAlarmThresholdLow (see below). The value is expressed as a percentage x 100 of the elapsed time specified by wvLinkThresholdMeasurementInterval.

Defines the low water mark below which the terminal exits the link Errored Seconds alarm state. The value is expressed as a percentage x 100 of the elapsed time specified by wvLinkThresholdMeasurementInterval.

Defines the high water mark above which the terminal enters the link Severely Errored Seconds alarm state. If wvLinkxxxSESs in a given wvLinkThresholdMeasurementInterval gets above this value a wvLinkSESAlarm is set, to be canceled if the value gets below wvLinkSESAlarmThresholdLow (see below). The value is expressed as a percentage x 100 of the elapsed time specified by wvLinkThresholdMeasurementInterval.

Defines the low water mark below which the terminal exits the link Severely Errored Seconds alarm state. The value is expressed as a percentage x 100 of the elapsed time specified by wvLinkThresholdMeasurementInterval.

Defines the high water mark above which the terminal enters the link Degraded Minutes alarm state. If wvLinkxxxDMs in a given wvLinkThresholdMeasurementInterval gets above this value a wvLinkDMAlarm is set, to be canceled if the value gets below wvLinkDMAlarmThresholdLow (see below). The value is expressed as a percentage x 100 of the elapsed time specified by wvLinkThresholdMeasurementInterval.

Defines the low water mark below which the terminal exits the link Degraded Minutes alarm state. The value is expressed as a percentage x 100 of the elapsed time specified by wvLinkThresholdMeasurementInterval.

Defines the high water mark above which the terminal enters the link Unavailable Seconds alarm state. If wvLinkxxxUASs in a given wvLinkThresholdMeasurementInterval gets above this value a wvLinkUASAlarm is set, to be canceled if the value gets below wvLinkUASAlarmThresholdLow (see below). The value is expressed as a percentage x 100 of the elapsed time specified by wvLinkThresholdMeasurementInterval.

Defines the low water mark below which the terminal exits the link Unavailable Seconds alarm state. The value is expressed as a percentage x 100 of the elapsed time specified by wvLinkThresholdMeasurementInterval.

Defines the high water mark above which the terminal enters the link rslLow alarm state. If wvLinkxxxRSL in a given wvLinkThresholdMeasurementInterval gets above this value a rslLow is set, to be canceled if the value gets below wvlinkRSLLowAlarmThresholdLow (see below).

Defines the low water mark below which the terminal exits the link rslLow alarm state.

Defines the high water mark above which the terminal enters the link averageRSLLow alarm state. If wvLinkxxxAverageRSL in a given wvLinkThresholdMeasurementInterval gets above this value a averageRSLLow is set, to be canceled if the value gets below wvlinkAverageRSLLowAlarmThresholdLow (see below).

Defines the low water mark below which the terminal exits the link averageRSLLow alarm state.

Defines the periodical interval against which the link performance alarm thresholds are to be checked. A value of zero means no link performance alarms should be issued.

Defines the high water mark above which the terminal enters the ETH 10/100 Carrier Sense Lost alarm state. If dot3StatsCarrierSenseErrors for any ETH 10-100 port gets above this value in a given wvEth10-100ThresholdMeasurementInterval, a eth10-100PortCSLAlarm is set, to be canceled if the value gets below wvEth10-100CSLAlarmThresholdhLow (see below).

Defines the low water mark below which the terminal exits the ETH 10/100 Carrier Sense Lost alarm state.

Defines the high water mark above which the terminal enters the ETH 10/100 Excessive Collisions alarm state. If dot3StatsExcessiveCollisions for any ETH 10-100 port gets above this value in a given wvEth10-100ThresholdMeasurementInterval, a eth10-100PortECAlarm is set, to be canceled if the value gets below wvEth10-100ECAlarmThresholdhLow (see below).

Defines the low water mark below which the terminal exits the ETH 10/100 Excessive Collisions alarm state.

Defines the high water mark above which the terminal enters the ETH 10/100 Internal MAC Transmit Errors alarm state. If dot3StatsInternalMacTransmitErrors for any ETH 10-100 port gets above this value in a given wvEth10-100ThresholdMeasurementInterval, a eth10-100PortIMTEAlarm is set, to be canceled if the value gets below wvEth10-100IMTEAlarmThresholdhLow (see below).

Defines the low water mark below which the terminal exits the ETH 10/100 Internal MAC Transmit Errors alarm state.

Defines the high water mark above which the terminal enters the ETH 10/100 Internal MAC Receive Errors alarm state. If dot3StatsInternalMacReceiveErrors for any ETH 10-100 port gets above this value in a given wvEth10-100ThresholdMeasurementInterval, a eth10-100PortIMREAlarm is set, to be canceled if the value gets below wvEth10-100IMREAlarmThresholdhLow (see below).

Defines the low water mark below which the terminal exits the ETH 10/100 Internal MAC Receive Errors alarm state.

Low threshold of the actual no. of bits being transmitted by the ETH 10/100 ports to the Link interface.

High threshold of the actual no. of bits being transmitted by the ETH 10/100 ports to the Link interface.

Low threshold of the actual no. of bits being received by the ETH 10/100 ports from the Link interface.

High threshold of the actual no. of bits being received by the ETH 10/100 ports from the Link interface.

Defines the periodical interval against which the ETH 10/100 alarm thresholds are to be checked. A value of zero means no link performance alarms should be issued.

use SET wvClearAlarmLog to Clear the alarm log and insert alarm that 'Alarm log was cleared by user' and GET wvClearAlarmLog to get the number of entries in the alarm log.

The 8800 DMR Plug-In Part No. is defined as PIN-'xyztu', as follows: x - interface type: x=1 - T1/T3, x=2 - E1/E3, x=3 - STS1, x=4 - 10/100Base-T + T1s, x=5 - 10/100Base-T + E1s, x=6, 7, ...- reserved. y - connector type: for x=1/2, T1/E1 connector type - y=1 - BNC, y=2 - RJ48, y=7 - SCSI, y=8 - SCSI + T3/E3 - BNC for x=4/5, 10/100Base-T + T1/E1 connectors types y=1 - 10/100Base-T - RJ45 + T1/E1 - BNC, y=2 - 10/100Base-T - RJ45 + T1/E1 - RJ48, if no T1/E1s available then y=1 y=3 - 10/100Base-FX - (FIBER) + T1/E1 - BNC, y=4 - 10/100Base-FX - (FIBER) + T1/E1 - RJ48, if no T1/E1s available then y=3 zt- # of T1/E1 interfaces: for x=1/2/3 zt = 00, 01, 02, 04, 08 or 16 for x=4/5 zt = 00, 01, 02, or 04 u - # of high band interfaces: for x=1/2/3, # of T3/E3 interfaces - u = 0 or 1. for x=4/5, # of 10/100Base-T ports - u = 1, 2 or 4.

Plug-In Hardware Revision.

The 8800 DMR DIU Part No. is defined as IDU-'xyzt' (exact definition of xyzt TBD).

IDU Hardware Revision (in fact reflects the ICB - IDU Control Board - revision).

IDU Software Revision.

Sent together with the software being updated.

The Codan 8800 DMR ODU Part No. is defined as ODU-'xwyzt', as follows: x - Standard: x=1 - FCC(US), x=2 - ETSI(European) w - Duplex Spacing: standard frequency left digit value duplex FCC 38 1 700 FCC 23 1 1200 FCC 18 1 1560 ETSI 38 1 1260 ETSI 26 1 1008 ETSI 23 1 1200 ETSI 23 2 1008 ETSI 23 3 1232 ETSI 18 1 1010 ETSI 18 2 1008 ETSI 15 1 315 ETSI 15 2 420 ETSI 15 3 728 ETSI 15 4 644 ETSI 15 5 490 ETSI 15 6 322 ETSI 13 1 266 ETSI 10 1 65 ETSI 10 2 91 ETSI 10 3 65 ETSI 10 4 65 ETSI 10 5 91 ETSI 10 6 91 ETSI 10 7 91 ETSI 8 1 311.32 ETSI 8 2 126 ETSI 8 3 119 ETSI 7 1 154 (7125-7425) ETSI 7 2 154 (7425-7725) ETSI 7 3 161 (7125-7425) ETSI 7 4 161 (7425-7725) ETSI 7 5 245 ETSI 7 6 161 (7250-7550) y - Frequency Band: y=1-4 - Band 1-4 zt- Spectrum Range Allocation (in Ghz): 38, 23, 18, etc... Example: ODU-2-1-4-23 = ETSI, duplex spacing 1200MHz / band 4, 23GHz. The rules governing the Frequency Band correlation of the 2 terminals usage of a given link depend on the Spectrum Range of the link.

ODU Hardware Revision.

ODU Software Revision.

Sent together with the software being updated.

The IPB (IDU Panel Board) Hardware Revision.

BOOT Software Revision.

IDU Alternate Software Revision.

Describe the manufacture of this system. '1' - Codan. ... future OEM.

The OEM IDU Part No. is defined as IDU-'xx-xxxxx-xxx'.

The OEM ODU Part No. is defined as ODU-'xx-xxxxx-xxx'.

The OEM Plug-in Part No. is defined as Plug-in-'xx-xxxxx-xxx'.

Keeps the status of the Idu-Odu communication. Enumeration: 'fault': 3, 'notOperational': 4, 'warning': 2, 'ok': 1.

Keeps the state of the system from the firmware point-of-view. Enumeration: 'systemFailure': 2, 'ok': 1.

Keeps the current status of the Idu-Odu cable. Enumeration: 'open': 4, 'warning': 2, 'ok': 1, 'short': 3.

Reports the current status of the IDU. Bits: 'iduPowerSupplyLowValue': 1, 'iduNotOperational': 6, 'selfTestFault': 5, 'iduTxSynthesizerOutOfLock': 2, 'iduRxSynthesizerOutOfLock': 3, 'externalInputsActive': 4, 'filler0': 0.

Reports the current status of the ODU. Bits: 'averageRSLLow': 7, 'oduNotResponding': 13, 'rslLow': 6, 'anyOtherOduFault': 12, 'oduTxSynthesizerOutOfLock': 8, 'oduRxSynthesizerOutOfLock': 9, 'txOnMuteState': 2, 'oduRfSynthesizerOutOfLock': 10, 'rxFailure': 5, 'oduPowerSupplyOutOfRange': 1, 'oduTemperatureViolation': 11, 'rxOnMuteState': 3, 'txFailure': 4, 'filler0': 0.

Reports the general current status of the remote terminal. Bits: 'remoteTerminalFailure': 1, 'remoteTerminalNotResponding': 2, 'remoteTerminalWarning': 0.

Keeps the modem current status. Enumeration: 'ok': 1, 'noAnswer': 7, 'notResponding': 2, 'noDialTone': 3, 'connected': 5, 'anyOtherFault': 6, 'lineBusy': 4.

Reports the current security status. Bits: 'passwordBypass': 2, 'filler0': 0, 'linkIdViolation': 1.

Describes the status of last TFTP operation. If no TFTP has been performed its status is dwnlStatusUnknown. Enumeration: 'dwnlSuccess': 3, 'dwnlInProcess': 2, 'dwnlTftpFilePasswordError': 10, 'dwnlSwIncompatibleImage': 7, 'dwnlTftpProtocolError': 9, 'dwnlNoResponseFromServer': 5, 'dwnlConfigIncompatibleImage': 8, 'dwnlStatusUnknown': 1, 'dwnlChecksumError': 6, 'dwnlCancelByUser': 11, 'dwnlGeneralError': 4.

Reports the status of link performance related alarms. Bits: 'wvLinkBLERAlarm': 7, 'eth10-100RxLinkUsageLow': 10, 'wvLinkSESAlarm': 2, 'wvLinkBERFailureAlarm': 6, 'wvLinkDMAlarm': 4, 'wvLinkUASAlarm': 3, 'eth10-100TxLinkUsageLow': 12, 'eth10-100RxLinkUsageHigh': 11, 'wvLinkNCBLERAlarm': 9, 'wvLinkBBERAlarm': 8, 'wvLinkBERWarningAlarm': 5, 'eth10-100TxLinkUsageHigh': 13, 'wvLinkESAlarm': 1, 'filler0': 0.

Specifies the current Spectrum Range Allocation x 100, in Mhz (3800000, 2300000, 1800000, etc...) The value is extracted from the terminal's wvOduPartNo.

Specifies the current frequency band, as read from preset jumpers at the ODU. The value read should be compatible with the peer's Link Terminal, so that if one side has 1 or 3 the other side must have 2 or 4, accordingly. Enumeration: 'bandOne': 1, 'bandFour': 4, 'bandTwo': 2, 'bandThree': 3.

Specifies the frequency spacing between adjacent channels, as a function of the ODU standard (American vs. European) and chosen wvLinkCapacity. Note that on the 18 Ghz Spectrum Range the actual values may be different than on the other ranges, and those are specifically mentioned where applicable. Enumeration: 'seven': 8, 'twentyEight': 10, 'twentyFive': 5, 'twelveAndAHalf': 4, 'fifty': 6, 'fourteen': 9, 'sevenAndAHalf': 3, 'twoAndAHalf': 1, 'five': 2, 'fiftySix': 11, 'threeAndAHalf': 7.

The transmit power value read at this terminal's ODU output.

The receive signal value read on this terminal.

The margin on the receive signal level, as a function of the Automatic Gain Control read( min(wvRxSignalLevel) - wvRxSignalLevel ).

The measured ODU temperature. The units and possible values depend on the ODU model. The shown range is American Fahreneit. The European range is -50..100 Centigrades.

The current state of the IDU LEDs. Bits: 'localCableFault': 8, 'powerOn': 1, 'remoteFrontPanelDisplay': 15, 'relay3On': 5, 'localOduFault': 12, 'remoteIduFault': 11, 'relay4On': 6, 'remoteCableFault': 9, 'relay1On': 3, 'localIduFault': 10, 'relay5On': 7, 'localFrontPanelDisplay': 14, 'remoteOduFault': 13, 'linkOperational': 2, 'relay2On': 4, 'filler0': 0.

The measured Modem Automatic Frequency Control. This is an implementation specific value, mainly for diagnostic purposes.

The measured Receive Pll Frequency. This is an implementation specific value, mainly for diagnostic purposes.

Specifies the actual working frequency x 100, in Mhz (3897875, 2122550, 1873875, etc...) The value depends on the chosen wvChannelNo, the terminal's wvOduPartNo and wvFrequencyBand.

This value present the maximum Tx power that can be achieved by the system (this parameter is the maximum value that the user can set for the 'wvTxPowerSetting').

This value present the minimum Tx power that can be achieved by the system (this parameter is the minimum value that the user can set for the 'wvTxPowerSetting').

The serial number of ODU.

The serial number of IDU.

Reports the current status of various 1+1 related signals and s/w detected conditions. Bits: 'unitActive': 5, 'alternateIduOk': 4, 'swIduFail': 7, 'upperUnit': 8, 'primaryUnit': 2, 'frequencyDiversityOn': 6, 'onePlusOneOn': 1, 'manualModeOn': 3, 'filler0': 0.

Reports the current status of support 2T1 and 2E1 capacity. Enumeration: 'support2T1and2E1Disable': 1, 'support2T1and2E1Enable': 0.

The Last Update Configuration Timestamp in system ticks

The IDU serial number for OEM manufacture.

The ODU serial number for OEM manufacture.

Reports the current connector type that connected to the plug-in's in the new 1+1 system. Enumeration: 'iau75': 2, 'iauDb25': 1, 'yCable': 0.

The number of events from last reset

The Log Event table.

An entry in the Log Event table.

A number between 1 and 64, where 1 is the last (new) event in queue and 64 is the first (old) event in queue. (assuming that all 64 events are valid).

Defines the event time, relative to sysUpTime

Defines the alarm severity. Enumeration: 'warningEnd': 5, 'messageStart': 1, 'messageEnd': 4, 'warningStart': 2, 'fatalEnd': 6, 'fatalStart': 3.

The event description. For example: IDU Tx synt. Fail.

Specifies the terminal's cummulative Bit Error Rate since link last start-up.

Specifies the terminal's cummulative Corrected Blocks Rate since link last start-up.

Specifies the terminal's cummulative Background Blocks Error Rate since link last start-up.

Specifies the terminal's cummulative Not Corrected Blocks Error Rate since link last start-up.

Specifies the number of Errored Seconds, encountered by the interface Link since link last start-up.

Specifies the number of Severely Errored Seconds, encountered by the interface Link since link last start-up.

Specifies the number of Unavailable Seconds, encountered by the interface Link since link last start-up.

Specifies the number of Degraded Minutes, encountered by the interface Link since link last start-up.

Specifies the average Receive Signal Level, encountered by the interface Link since link last start-up.

Specifies the maximum Receive Signal Level, encountered by the interface Link since link last start-up.

Specifies the minimum Receive Signal Level, encountered by the interface Link since link last start-up.

The number of previous intervals for which valid data was collected. The value will be 96 unless the interface was brought on-line within the last 24 hours, in which case the value will be the number of complete 15 minute intervals since the interface has been online.

The number of Errored Seconds, encountered by the interface Link in the current 15 minute interval.

The number of Severely Errored Seconds, encountered by the interface Link in the current 15 minute interval.

The number of Unavailable Seconds, encountered by the interface Link in the current 15 minute interval.

The number of Degraded Minutes, encountered by the interface Link in the current 15 minute interval.

The Bit Error Rate encountered by the interface Link in the current 15 minute interval.

The Corrected Blocks Rate encountered by the interface Link in the current 15 minute interval.

The Background Blocks Error Rate encountered by the interface Link in the current 15 minute interval.

The Not Corrected Blocks Error Rate encountered by the interface Link in the current 15 minute interval.

Specifies the average Receive Signal Level, encountered by the Link interface in the current 15 minute interval.

Specifies the maximum Receive Signal Level, encountered by the Link interface in the current 15 minute interval.

Specifies the minimum Receive Signal Level, encountered by the Link interface in the current 15 minute interval.

Specifies the no. of seconds elapsed since the beginning of the current 15 minute interval.

The Link Interval table.

An entry in the Link Interval table.

A number between 1 and 96, where 1 is the most recently completed 15 minute interval and 96 is the least recently completed 15 minutes interval (assuming that all 96 intervals are valid).

The number of Errored Seconds encountered by the Link interface in one of the previous 96, individual 15 minute, intervals.

The number of Severely Errored Seconds encountered by the Link interface in one of the previous 96, individual 15 minute, intervals.

The number of Unavailable Seconds encountered by the Link interface in one of the previous 96, individual 15 minute, intervals.

The number of Degraded Minutes (DMs) encountered by the Link interface in one of the previous 96, individual 15 minute, intervals.

The Bit Error Rate encountered by the Link interface in one of the previous 96, individual 15 minute, intervals.

The Corrected Blocks Rate encountered by the Link interface in one of the previous 96, individual 15 minute, intervals.

The Background Blocks Error Rate encountered by the Link interface in one of the previous 96, individual 15 minute, intervals.

The Not Corrected Blocks Error Rate encountered by the Link interface in one of the previous 96, individual 15 minute, intervals.

Specifies the average Receive Signal Level, encountered by the Link interface in one of the previous 96, individual 15 minute, intervals.

Specifies the maximum Receive Signal Level, encountered by the Link interface in one of the previous 96, individual 15 minute, intervals.

Specifies the minimum Receive Signal Level, encountered by the Link interface in one of the previous 96, individual 15 minute, intervals.

The number of Errored Seconds encountered by the Link interface in the previous 24 hour interval.

The number of Severely Errored Seconds encountered by the Link interface in the previous 24 hour interval.

The number of Unavailable Seconds encountered by the Link interface the previous 24 hour interval.

The number of Degraded Minutes (DMs) encountered by the Link interface in the previous 24 hour interval.

The Bit Error Rate encountered by the Link interface in the previous 24 hour interval.

The Corrected Blocks Rate encountered by the Link interface in the previous 24 hour interval.

The Background Blocks Error Rate encountered by the Link interface in the previous 24 hour interval.

The Not Corrected Blocks Rate encountered by the Link interface in the previous 24 hour interval.

Specifies the average Receive Signal Level, encountered by the Link interface in the previous 24 hour interval.

Specifies the maximum Receive Signal Level, encountered by the Link interface in the previous 24 hour interval.

Specifies the minimum Receive Signal Level, encountered by the Link interface in the previous 24 hour interval.

Specifies the total number of kilobits received by the Link interface.

Specifies the total number of errors received by the Link interface, before FEC Correction.

Specifies the total number of errored blocks received by the Link interface, before FEC Correction.

Specifies the total number of blocks that could not be corrected by the FEC, received by the Link interface.

The time (in hundredths of a second) since when Link related performance is calculated. It behaves like sysUpTime and is reset to 0 whenever Link characteristics (Capacity, Modulation, etc...) is changed.

The Instantaneous Bit Error Rate encountered by the Link interface. This is the value adaptively calculated to reach a 1% measurement precision.

Shows the actual no. of bits being transmitted by the ETH 10/100 ports to the Link interface.

Shows the actual no. of bits being received by the ETH 10/100 ports from the Link interface.

Shows the calculated ETH 10/100 Link percentage Tx usage (100 X wvEth10-100TxLinkUsage / total channel capacity).

Shows the calculated ETH 10/100 Link percentage Rx usage (100 X wvEth10-100RxLinkUsage / total channel capacity).

Defines the type of loopback to be performed on the terminal.

Defines the desired delay time, in time-ticks, before the loopbacks specified by wvLoopbackType are activated. When any loopback is on, either on delay or started, 0 forces a premature stop.

Defines the desired duration of the loopback. Setting a value of 0 means it should run until deliberately stopped.

Defines the ongoing remaining time before the loopbacks specified by wvLoopbackType are activated.

Defines the ongoing remaining duration of the loopback activation.

Defines the type of next self-tests to be performed on the terminal. Local restrictions may limit the tests that can be performed simultaneously. Bits: 'ramTest': 1, 'sccTest': 10, 'modemTest': 5, 'epromTest': 3, 'fpTest': 4, 'fecTest': 6, 'ibTest': 8, 'flashTest': 2, 'muxTest': 7, 'bertTest': 9, 'noTest': 0.

Defines the desired delay time, in time-ticks, before the tests specified by wvSelfTestType are started. When any test is running, 0 forces a premature stop.

Keeps the time, relative to sysUpTime, when the tests in the wvLastSelfTestTable were last performed.

A table of last self tests.

Entry in the wvLastSelfTestTable. There is one for each of the last run self-tests.

The self-test type for this entry. Enumeration: 'ramTest': 1, 'sccTest': 10, 'modemTest': 5, 'epromTest': 3, 'fpTest': 4, 'fecTest': 6, 'ibTest': 8, 'flashTest': 2, 'muxTest': 7, 'bertTest': 9, 'noTest': 0.

The status of the test specified in wvLastSelfTestType. Enumeration: 'failed': 1, 'passed': 2.

Defines the ongoing remaining time before the tests specified by wvSelfTestType start.

Defines the line(s) on which a special BER test signal is inserted. Proper loopbacks are assumed to be previously set for the test to succeed. If no loopback is selected, the test results are checked at the peer terminal. The actual lines applicable depend on wvLinkCapacity. In addition, only the following combinations can be simultaneously tested: - 1 T1/E1 line - T3/E3 line - the eth10-100 board (both ports) - all existing lines/ports (full capacity). Bits: 'eth10-100': 18, 'dsx1-13': 13, 'dsx1-12': 12, 'dsx1-11': 11, 'dsx1-10': 10, 'dsx1-16': 16, 'dsx1-15': 15, 'dsx1-14': 14, 'dsx1-3': 3, 'dsx1-2': 2, 'dsx1-1': 1, 'dsx1-7': 7, 'dsx1-6': 6, 'dsx1-5': 5, 'dsx1-4': 4, 'dsx3': 17, 'dsx1-9': 9, 'dsx1-8': 8, 'filler0': 0.

Defines the desired delay time, in time-ticks, before the tests on the lines specified by wvInsertTestSignalLine are started. When any test is on, 0 forces a premature stop.

Defines the desired duration of the tests. Setting a value of 0 means it should run until deliberately stopped.

Defines the time, relative to sysUpTime, when the insert test signal was last performed.

Specifies the Bit Error Rate from last test signal activation.

Defines the ongoing remaining time before the tests on the lines specified by wvInsertTestSignalLine start.

Defines the ongoing remaining duration of the tests.

This object defines the address on the IDU physical memory from which wvGenericDiagnosticsParameterValue below is read. The given address will be aligned to long, if needed. Attempt to set it to a non-valid address will be rejected.

Reading of this object returns the 4 bytes (long) value on the address specified by wvGenericDiagnosticsParameterAddress above.

A trap indicating Idu or Odu cable fail

A trap indicating restoring from wvIduOduCableFaultStart

A trap indicating Idu internal fail: RX or TX synthesizer out of lock or power supply fail

A trap indicating restoring from wvIduInternalFaultStart

A trap indicating Odu internal fail: RX or TX synthesizer out of lock or power supply fail

A trap indicating restoring from wvOduInternalFaultStart

A trap indicating that MUX or MODEM is not synchronized

A trap indicating restoring from wvLinkDownStart

A trap indicating that the last received peer Link ID does not match the local Link ID

A trap indicating restoring from wvIdViolationStart

A trap indicating that the remote terminal is not accessable

A trap indicating restoring from wvRemoteAccessStart

A trap indicating that the local Odu is not responding

A trap indicating restoring from wvLocalOduAccessStart

A trap indicating that the local RSL is out of the lower range

A trap indicating restoring from wvReceiveSignalLowerLevelStart

A trap indicating that the relay was switched to on

A trap indicating that the relay was switched to off

A trap indicating that the port transmit AIS

A trap indicating restoring from wvLineAisStart

A trap indicating that there is an LOS on the specified line

A trap indicating restoring from wvLineLosStart

A trap indicating that the local BER is out of range

A trap indicating restoring from wvBerStart

A trap indicating that the local BER is out of range

A trap indicating restoring from wvBerStart

A trap indicating that the external input is active

A trap indicating restoring from wvExternalInputsStart

A trap indicating that the link UAS is out of range

A trap indicating restoring from wvLinkUasStart

A trap indicating that there was TFTP operation fault

A trap indicating that the last TFTP operation was successful

A trap indicating that the ODU temperature is out of range

A trap indicating restoring from wvOduTempViolationStart

A trap indicating that the ODU transmitter is in mute state

A trap indicating restoring from wvOduTxMuteStart

A trap indicating that theIDU ha power supply problems

A trap indicating restoring from wvIduPowerSupplyStart

A trap indicating that the IDU's configuration does not match the current hardware

A trap indicating that the bank switchover had occured

A trap indicating that the corresponding poer is in loopback state

A trap indicating restoring from wvIduPortLoopbackStart

A trap indicating that the corresponding poer is in loopback state

A trap indicating restoring from wvIduPortBertStart

Serial Numbers: Odu, Idu; HeartBit Values ( string): A HeartBit trap

A trap indicating that the port receives AIS

A trap indicating restoring from wvAisReceiveStart

A trap indicating that the Rx Link Usage is out of low range

A trap indicating that the Rx Link Usage is in low range

A trap indicating that the Rx Link Usage is out of High range

A trap indicating that the Rx Link Usage is in High range

A trap indicating that the Tx Link Usage is out of Low range

A trap indicating that the Tx Link Usage is in Low range

A trap indicating that the Tx Link Usage is out of High range

A trap indicating that the Tx Link Usage is in High range

This object defines the keep alive traps period in minutes.

This object defines the port munber that refers to wvLineAisStart/wvLineAisStop /wvAisReceiveStart/wvAisReceiveStop, this number should be used as wvTributaryPortIfIndex in the wvTributaryPortTable.

This object defines the port munber that refers to wvLineLosStart/wvLineLosStop, this number should be used as wvTributaryPortIfIndex in the wvTributaryPortTable.

This object defines the external input munber that refers to wvExternalInputsStart/wvExternalInputsStop.

This object defines the relay id munber that refers to wvRelayStart\wvRelayStop, this number should be used as wvRelayId in the wvRelayTable.

Private traps mapping. Bits: 'wlUasStop': 29, 'wlRelayStart': 16, 'wlPortBertStop': 43, 'wlPortLoopBckStop': 41, 'wlLosStart': 20, 'wlBerErrStop': 25, 'wlUasStart': 28, 'wlBerWarnStop': 23, 'wlEth10x100TxLinkUsageHighStop': 54, 'wlRmtTermAccsStart': 10, 'wlEth10x100TxLinkUsageLowStart': 51, 'wlTftpSuss': 31, 'wlOduTempStop': 33, 'wlAisStop': 19, 'wlPortLoopBckStart': 40, 'wlEth10x100TxLinkUsageHighStart': 53, 'wlExtInputsStart': 26, 'wlEth10x100RxLinkUsageHighStart': 49, 'wlRcvSignLowLevlStart': 14, 'wlRmtTermAccsStop': 11, 'wlLosStop': 21, 'wlEnd': 55, 'wlIdViolationStop': 9, 'wlOduCableFaultStart': 0, 'wlAisReceiveStart': 45, 'wlAisStart': 18, 'wlOduIntnlFaultStart': 4, 'wlEth10x100TxLinkUsageLowStop': 52, 'wlLoclOduAccsStart': 12, 'wlLinkDownStart': 6, 'wlRcvSignLowLevlStop': 15, 'wlIdViolationtStart': 8, 'wlRelayStop': 17, 'wlHeartBit': 44, 'wlLoclOduAccsStop': 13, 'wlOduIntnlFaultStop': 5, 'wlPwrSupplyStop': 37, 'wlAisReceiveStop': 46, 'wlIduIntnlFaultStart': 2, 'wlLinkDownStop': 7, 'wlEth10x100RxLinkUsageLowStart': 47, 'wlPortBertStart': 42, 'wlTxMuteStop': 35, 'wlBerWarnStart': 22, 'wlIduIntnlFaultStop': 3, 'wlEth10x100RxLinkUsageLowStop': 48, 'wlPwrSupplyStart': 36, 'wlEth10x100RxLinkUsageHighStop': 50, 'wlOduTempStart': 32, 'wlBerErrStart': 24, 'wlExtInputsStop': 27, 'wlBankSw': 39, 'wlOduCableFaultStop': 1, 'wlCfgMismatch': 38, 'wlTftpFail': 30, 'wlTxMuteStart': 34.

Keep Alive trap variables mapping. Bits: 'vRSL': 0, 'vUAS': 2, 'vEnd': 3, 'vBER': 1.

A verbal string send with the wvIduHeartBit trap Has the following format: Serial Numbers: \ [RSL = ] [BER = ] [UAS = ]