Cross Connections | 121 10. Cross Connections Embedded cross connect switch The embedded cross-connect switch distributes capacity to each of the interfaces. Traffic can be distributed to any of the possible 32 interface ports as well as the integrated Ethernet interface. This provides the flexibility to reconfigure traffic as the network demand changes, or groom user traffic onto E1 / T1 bearers between equipment. The maximum number of simultaneous cross connections per terminal is 256.
Cross Connections | 122 Installing the Cross Connections application The Cross Connections application is usually started directly from SuperVisor without the need for installation. However, if you want to use the Cross Connections application offline (without any connection to the terminals), you can install it on your PC. Working offline enables you to simulate new cards or terminal capacities. The cross connections can then be configured and the resulting configuration file saved for later deployment.
Cross Connections | 123 The Cross Connections page The Cross Connections page is split into two panes with each pane displaying one terminal. The local terminal is displayed in the left pane and the remote terminal is displayed in the right pane. The local terminal is defined as the terminal that SuperVisor is logged into (not necessarily the near end terminal). The cards displayed depend on the type of cards and where they are inserted in the chassis.
Cross Connections | 124 Radio link and drop and insert capacity At the bottom of the Cross Connections page, the capacity pane displays the Radio and Drop and insert capacities for both the local and remote terminals. The Radio field shows the available radio link capacity (6696 kbit/s shown) and the shaded bar graph shows the capacity assigned for cross connections over the radio link between the terminals as a percentage of the total capacity of the radio link (22 % assigned).
Cross Connections | 125 Setting the terminal's address If the Cross Connections application is launched from SuperVisor, the terminal IP addresses are set automatically by SuperVisor, but if the application is launched from your PC independent of SuperVisor, you will need to set the application Local and Remote IP addresses to the addresses of the Local and Remote terminals you wish to connect to. To set the application local or remote IP address: 1.
Cross Connections | 126 Setting card types Note: You only need to do this when creating configurations offline (that is, there is no connection to the terminal). When you are connected to the terminal, the Cross Connections application automatically detects the card types fitted in the terminal slots. You can specify the card type for any of the slots (A-H). 1. Right-click a slot. 2. Select Card Type and then select the interface card.
Cross Connections | 127 Creating cross connections Point to point cross connections Three examples of point to point cross connections are shown below: Example 1 One 2 wire DFXO interface on the near end terminal slot E port 1 is cross connected via the radio link to a 2 wire DFXS on the far end terminal slot E port 1.
Cross Connections | 128 Example 2 One 2 wire DFXS interface on the near end terminal slot E port 1 is cross connected via the radio link to a framed E1 on the far end terminal slot D port 1 in timeslot 1. This cross connection includes four bits of signalling as the DFXS signalling is configured as 'non-multiplexed signalling' (ABCD bits). This cross connection uses 96 kbit/s of radio link capacity, 64 kbit/s for the voice and 32 kbit/s for the signalling bits.
Cross Connections | 129 Drop and insert cross connections An example of a drop and insert cross connection is shown below: Two 4 wire E&M interfaces on the near end terminal slot C ports 3 & 4 are dropped out of a framed E1 on the near end terminal slot D port 1 in timeslots 1 & 2. This cross connection includes one bit of signalling (A bit).
Cross Connections | 130 Sending cross connection configuration to the terminals You can send the entire cross connection configuration to the terminals. 1. To send the new cross connection configuration into the terminals, click ‘Send cross connection configuration to terminal’. 2. When the transfer is successfully complete, a message appears asking if you want to activate the configuration now. If you click Yes, a message warning of the activation delay.
Cross Connections | 131 Printing the cross connection configuration You can print out a summary of the cross connection configuration so that you can file it for future reference. Using the printout, you can recreate the cross connection configuration. If you don't have the configuration saved to disk see "Saving cross connection configurations" on page 130, or use it to review the cross connections without connecting to the terminal.
Cross Connections | 132 Deleting cross connections Note: It is not possible to delete the management and user Ethernet cross connections. These are made automatically and are required for correct terminal operation. To delete cross connections for an interface card: 1. Right-click over an interface card. 2. Select Delete All Connections on this Card. To delete the cross connections associated with a particular port: 1. Right-click over a port. 2. Select Delete All Connections on this Port.
Cross Connections | 133 Configuring the traffic cross connections Once you have configured the interface cards (see "Configuring the traffic interfaces" on page 77), you can configure the traffic cross connections between compatible interfaces.
Cross Connections | 134 QJET cross connections Expand the E1 / T1 display by clicking on the relevant icons. The QJET card can operate in several modes allowing you greater flexibility in tailoring or grooming traffic. The Data type selection are Off, E1, or T1 rates. Note: An unframed E1 / T1 port requires 5 bits (or 40 kbit/s) of overhead traffic per port for synchronization. An unframed E1 port with 2048 kbit/s of traffic requires 2088 kbit/s of link capacity.
Cross Connections | 135 For each port that you want to put into service, choose the required mode (either Unframed or Framed): Unframed mode Leave the Framed checkbox unticked. Select the required Data type from the drop-down list E1 or T1. Local drop and insert connections are not possible between Unframed E1 / T1 ports. Framed mode Tick the Framed checkbox.
Cross Connections | 136 E1 Framed Modes Framed Mode Description E1 – PCM 30 Provides 30 timeslots to transport traffic. Timeslot 16 carries channel associated signalling data (CAS). E1 – PCM 31 Provides 31 timeslots to transport traffic. Timeslot 16 can be used for common channel signalling or to transport traffic. E1 – PCM 30C Same as E1 – PCM 30 mode but supports CRC-4. E1 – PCM 31C Same as E1 – PCM 31 mode but supports CRC-4.
Cross Connections | 137 T1 Framed Modes Framed Mode Description T1 - SF Provides 24 timeslots to transport traffic using the G.704 12 frame Super Frame without signalling. There is no CRC capability with the SF. T1 – SF 4 Provides 24 timeslots to transport traffic using the G.704 12 frame Super Frame with 4 state signalling (AB bits). There is no CRC capability with the SF. T1 – ESF Provides 24 timeslots to transport traffic using the G.
Cross Connections | 138 T1 - ESF 4 mode T1 ESF 4 mode provides 24 timeslots to transport traffic using the G.704 24 frame Extended Super Frame with four state demultiplexed signalling using the AB bits each with a bit rate of 667 bit/s. The mapping left column is used to map timeslot bits and the timeslot table right column is used to map the CAS A&B bits for signalling (C&D bits are not used).
Cross Connections | 139 Selecting and mapping bits and timeslots This section describes how to select and map: a single bit multiple bits a 64 kbit/s timeslot multiple timeslots Selecting a single bit Each timeslot is represented by 8 rectangles (each representing a single bit). Each bit can carry 8 kbit/s. One or more consecutive bits can be selected in a timeslot if a rate of greater than 8 kbit/s is required. 1. Click on the rectangle that represents the bit you require.
Cross Connections | 140 Selecting multiple bits It is possible to select multiple consecutive bits if circuit capacity of greater than 8 kbit/s is required. 1. Click the first bit, and then hold down the Ctrl key while selecting the remaining bits. 2. Click and drag the whole block by clicking the bit on the left hand side of your selection, and drag to the required interface. Release the mouse button.
Cross Connections | 141 Selecting a 64 kbit/s timeslot 1. Click on the TSX timeslot number (where X is the desired timeslot from 1 to 31). Alternatively, right-click over any of the bits in the timeslot, and click on Select Timeslot. 2. Drag and drop in the normal way to complete the cross connection. Selecting multiple non consecutive timeslots 1. Click on one TSn timeslot number (where n is the desired timeslot 1 to 31). 2.
Cross Connections | 142 Selecting multiple consecutive timeslots 1. Click on the first TSn timeslot number (where n is the desired timeslot 1 to 31). 2. Hold down the Shift key while clicking on the last required timeslot number. 3. Drag and drop in the normal way to complete the cross connection. Selecting all timeslots in a port 1. Right-click over any of the rectangles. 2. Click Select All.
Cross Connections | 143 Q4EM cross connections 1. Expand the Q4EM display by clicking the relevant icon. 2. Set the Voice capacity by selecting 16, 24, 32, or 64 kbit/s rates. 3. Drag and drop from the Voice mapping connection box to the required partner interface to create the voice cross connection. 4. If E&M signalling is required, drag and drop from the Signalling mapping connection box to the required partner interface to create the E&M cross connection.
Cross Connections | 144 DFXS & DFXO cross connections 1. On one side of the link, expand the DFXS display, as required, by clicking . 2. On the other side of the link, expand the corresponding DFXO display, as required, by clicking 3. For the DFXS card and corresponding DFXO card, select the Signalling type as required, according to the table below. The CAS signalling between DFXO / DFXS interfaces uses 4RF proprietary allocation of control bits.
Cross Connections | 145 QV24 cross connections 1. Expand the QV24 displays, as required, by clicking the relevant icons. 2. Select the Port Baud Rate as required (default is 9600). 3. Drag and drop to the required partner interface to create the V.24 Data connection. If the partner interface is a QJET: If the V.24 Baud Rate selected is 38400 is less, drag from the QV24 mapping connection box to the QJET timeslot. The correct QJET capacity for the baud rate selected will automatically be assigned.
Cross Connections | 146 HSS cross connections 1. Expand the HSS displays, as required, by clicking the relevant icons. 2. Select the Synchronous Clock Selection mode (see “HSS synchronous clock selection modes” on page 114). 3. Set the Data rate to a value between 8 and 2048 (in multiples of 8 kbit/s). The net data rate available to the user is defined by Data Rate – overhead e.g. a date rate set to 2048 kbit/s with an overhead of 40 kbit/s provides a user data rate of 2008 kbit/s 4.
Cross Connections | 147 Cross connection example This is an example of cross connection mapping: Circuit Local port Remote port Radio management User Ethernet Capacity (kbit/s) Connection numbers 64 1 1024 2 3 wire E&M circuit Q4EM port 1 (slot C) Q4EM port 1 (slot C) 72 7/15 Unframed E1 data QJET port 1 (slot D) QJET port 1 (slot D) 2088 65 Unframed T1 data QJET port 2 (slot D) QJET port 2 (slot D) 1584 66 Loop Interface DFXO port 1 (slot E) DFXS port 1 (slot E) 72 8/32 V.
Cross Connections | 148 Symmetrical Connection Wizard The Cross Connections application has a Symmetrical Connection Wizard which simplifies the cross connection configuration when the terminals are fitted with symmetrical / matching interface types. A symmetrical connection is a connection between the local and the remote terminal where the local slot, card type, port and connection details are identical to those of the remote terminal.
Cross Connections | 149 Setting the IP address If the local or remote terminal IP addresses have been setup, they will be displayed in the Local and Remote fields. If the IP addresses are not displayed, enter the IP addresses of the local and remote terminals. Click on 'Get Configuration' to upload the existing cross connections configuration from the local terminal. The Radio bandwidth bar will show the available bandwidth and will be updated as bandwidth is assigned to cards.
Cross Connections | 150 Card Selection If the Cross Connections Application is opened from SuperVisor, existing cards installed in the local terminal that match cards installed in the remote terminal will be displayed. Mismatched cards will be shown as 'Empty Slot'. If the Cross Connections Application is opened as a stand alone application, select the card types that will be fitted in the terminal. To copy the card type selected in Slot A to all the other slots (B – H), click on the Copy Card button.
Cross Connections | 151 Interface configurations Setup the interface configurations as per the wizard instructions. Existing asymmetrical connections will be replaced with symmetrical connections if an interface parameter is changed. Q4EM QJET DFXO / DFXS QV24 HSS Ethernet To copy the port configuration selected in Port 1 to all the other ports on the card, click on the Copy Port button.
Cross Connections | 152 Symmetrical connection summary Click Finish. Send symmetrical connection configuration Click OK to send the configuration to the terminals. The process is completed. Note: The wizard may change the connection numbers of existing connections.
Protected terminals | 153 11. Protected terminals Monitored Hot Stand By (MHSB) This section describes configuring the protected terminal in MHSB mode. A protected terminal in MHSB mode comprises two radios interconnected using the tributary and RF switches as shown below: The MHSB switch protects terminals against any single failure in one radio. It also monitors the alarm output of each radio and switches between radios if major radio link alarms occur.
Protected terminals | 154 Tributary switch front panel No.
Protected terminals | 155 Tributary protection switch LEDs LED Colour Appearance Explanation A Green Solid The radio is active and is OK Green Flashing The radio is in standby mode and is OK Red Solid The radio is active and there is a fault No colour (off) - The tributary switch is in 'slave' mode and the switching is controlled by the master tributary switch Red Flashing The radio is in standby mode, and there is a fault Green Solid The radio is active and is OK Green Flashing Th
Protected terminals | 156 RF protection switch LEDs LED Colour Appearance Explanation Tx A Green Solid RF is being received from radio A Tx B Green Solid RF is being received from radio B On Blue Solid Indicates that there is power to the RF protection switch Slave tributary switches Each tributary switch protects up to eight ports. Up to three slave tributary switches may be added to a MHSB terminal to protect up to 32 ports.
Protected terminals | 157 MHSB cabling The two radios are interconnected as follows: Caution: Do not connect Transmit to Receive or Receive to Transmit as this may damage the radio or the MHSB switch. Cables supplied with MHSB The following cables are supplied with a MHSB terminal: Ethernet interface: RJ-45 ports standard TIA-568A patch cables . Alarm interface: RJ-45 ports standard TIA-568A patch cables. RF ports: two QMA male patch cables are supplied.
Protected terminals | 158 Configuring the radios for protected mode The MHSB switch does not require any special software. However, the radios connected to the MHSB switch must be configured to work with the MHSB switch. This sets the alarm outputs and inputs to function in MHSB mode. You must configure the interfaces of both radios connected to the MHSB switch identically. To perform this, you can either connect directly to the radio or use the test mode of the MHSB switch.
Protected terminals | 159 Mounting the MHSB radios and switch Once the IP addresses are correctly configured, it is important to connect the A and B radios' Ethernet and Alarm ports correctly. In general, mount radio A above the MHSB switch and radio B below the MHSB switch: There is an Ethernet connection between any of the four Ethernet ports on each radio and the Ethernet port on the Tributary switch.
Protected terminals | 160 Configuring the terminals for MHSB It is recommended that you configure the local and remote A side first, then the local and remote B side. Both the local A and B radios must be configured identically, and both the remote A and B radios must be configured identically. Tip: As illustrated below, you may find it helpful to have two browser sessions running simultaneously. You can then easily see both the A and B sides of the protected link. To configure MHSB operation: 1.
Protected terminals | 161 Clearing MHSB alarms If a switchover event occurs, the OK LED on the front panel and on the Terminal status and menu bar in SuperVisor changes to orange. 1. Select Clear Switched Alarm from the MHSB Command drop-down list. 2. Click Apply to apply changes or Reset to reset the page. Note: When MHSB mode is enabled, external alarm input 2 is used by the protection system to carry alarms from the protection switch to the radio.
In-service commissioning | 163 12. In-service commissioning Before you start When you have finished installing the hardware, RF and the traffic interface cabling, the system is ready to be commissioned. Commissioning the terminal is a simple process and consists of: 1. Powering up the terminals 2. Configuring both the local and remote terminals using SuperVisor 3. Aligning the antennas 4. Synchronizing the terminals 5. Testing the link is operating correctly.
In-service commissioning | 164 Applying power to the terminals Caution: Before applying power to a terminal, ensure you have connected the safety earth and antenna cable. Apply power to the terminals at each end of the link. When power is first applied, all the front panel LEDs will illuminate red for several seconds as the system initializes.
In-service commissioning | 165 Antenna alignment For any point-to-point link, it is important to correctly align the antennas to maximize the signal strength at both ends of the link. Each antenna must be pointing directly at the corresponding antenna at the remote site, and they must both be on the same polarization. The antennas are aligned visually, and then small adjustments are made while the link is operating to maximize the received signal.
In-service commissioning | 166 Visually aligning antennas 1. Stand behind the antenna, and move it from side to side until it is pointing directly at the antenna at the remote site. The remote antenna may be made more visible by using a mirror, strobe light, or flag. If the remote end of the link is not visible (due to smoke, haze, or local clutter, etc), align the antenna by using a magnetic compass. Calculate the bearing using a scale map of the link path.
In-service commissioning | 167 Accurately aligning the antennas Once the antennas are visually aligned, accurately align both antennas by carefully making small adjustments while monitoring the RSSI. This will give the best possible link performance. Note: Remember that it is important to align the main radiation lobes of the two antennas to each other, not any side lobes.
In-service commissioning | 168 Measuring the RSSI Measure the RSSI value with a multimeter connected to the RSSI test port on the front of the terminal (see "Front panel connections and indicators" on page 27). 1. Insert the positive probe of the multimeter into the RSSI test port, and clip the negative probe to the chassis of the terminal (earth). 2. Pan and tilt the antenna until you get the highest VDC reading.
In-service commissioning | 169 Synchronizing the terminals After you have completed the alignment of the two antennas, you must ensure the two terminals are synchronized. The terminals are synchronized when: the OK LED is green, which indicates that no system alarms are present, and the RX LED is green, which indicates a good signal with no errors, and the TX LED is green, which indicates that there are no transmitter fault conditions.
In-service commissioning | 170 Checking the fade margin The fade margin is affected by many components in the system and is closely related to the received signal strength. A link operating with a lower than expected fade margin is more likely to suffer from degraded performance during fading conditions. A reduced fade margin can be due to operating the link too close to the noise floor, or the presence of external interference.
In-service commissioning | 171 7. Record the fade margin and SNR results on the commissioning form. Note: If the transmit power is reduced using SuperVisor rather than an external attenuator, the fade margin should be recorded as “Greater than x dB” (where x = the power reduction). 8. Restore the remote terminal transmit power to normal. 9. Repeat steps 1 to 7 for the other end of the link. Note: If following all the guidelines above does not resolve the situation, contact Customer Support for assistance.
In-service commissioning | 172 Additional tests Depending on license requirements or your particular needs, you may need to carry out additional tests, such as those listed below. Refer to the relevant test equipment manuals for test details.
In-service commissioning | 173 Checking the link performance For a graphical indication of the link performance, you can use the constellation analyzer. The 'dots' are a graphical indication of the quality of the demodulated signal. Small dots that are close together indicate a good signal. If the dots become spaced further apart, this indicates that the signal quality is degrading.
In-service commissioning | 174 Viewing a summary of the link performance To view the performance summary for a terminal: Select Link or Local or Remote > Performance > Summary.
Maintenance | 175 13. Maintenance There are no user-serviceable components within the terminal. All hardware maintenance must be completed by 4RF or an authorized service centre. Do not attempt to carry out repairs to any boards or parts. Return all faulty terminals to 4RF or an authorized service centre. For more information on maintenance and training, please contact Customer Services. Caution: Electro Static Discharge (ESD) can damage or destroy the sensitive electrical components in the terminal.
Maintenance | 176 Terminal upgrades You can upgrade all software for both terminals remotely (through a management network), which eliminates the need to physically visit either end of the link. The best method of upgrading a terminal is to use the TFTP server method (see “Upgrading the terminal using TFTP” on page 177). This method downloads all the required image files into the terminal and then activates the correct files following a terminal reboot.
Maintenance | 177 Upgrading the terminal using TFTP Before upgrading the terminal, ensure that you have saved the configuration file (see "Saving the terminal's configuration" on page 66) as well as the cross connection configuration (see "Saving cross connection configurations" on page 130). Upgrading the terminal using the TFTP (Trivial File Transfer Protocol) server involves these steps: 1. Run the TFTP server. 2.
Maintenance | 178 Step 2: Log into the Local terminal Use SuperVisor to log into the Near end terminal (now the Local terminal) (see “IP addressing of terminals” on page 47) with either 'modify' or 'admin' privileges. Step 3: Run the TFTP upgrade process on the Remote terminal 1. Select Remote > Maintenance > Upload > TFTP Upgrade. 2. Enter the IP address of the TFTP server (that you noted earlier) 3.
Maintenance | 179 Step 5: Run the TFTP upgrade process on the Local terminal. 1. Select Local > Maintenance > Upload > TFTP Upgrade. 2. Enter the IP address of the TFTP server (that you noted earlier) 3. Enter the version number of the software (that you are upgrading to) for example, 7_3_2. 4. Click Apply and check the TFTP server for download activity. The Upgrade Result changes from 'Executing' to either 'Succeeded' or 'Failed'. Note: This may take several minutes when upgrading the remote terminal.
Maintenance | 180 To clear your web browser cache (Mozilla Firefox 1.x and above): 1. Select Tools > Options. 2. Select Privacy and then click Cache. 3. Click Clear to clear the cache, and then click OK to confirm.
Maintenance | 181 To clear your web browser cache (Internet Explorer 6.x and above): 1. Select Tools > Internet Options. 2. On the General tab, click Delete Files, and then click OK to confirm.
Maintenance | 182 Upgrading the terminal by uploading system files A terminal can also be upgraded by uploading specific system files: configuration files, kernel image files, software image files or firmware image files. Note: You should only upgrade components that need changing. It is not always necessary, for instance, to replace kernel or software files when upgrading a single firmware file.
Maintenance | 183 To upload a configuration file: 1. Select Local > Maintenance > Config Files > Upload Configuration 2. Browse to the location of the file required to be uploaded into the terminal *.cfg. 3. Click on Upload. The normal response is Succeeded if the file has been loaded correctly.
Maintenance | 184 Image Files Image files (.img) are loaded into the terminal and either contains code that is executed by the system processor, or contain instructions to configure the various programmable logic elements. The image file types that can be uploaded are: • Kernel image files • Software image files • Firmware image files Note: The Bootloader image file C-CC-B-(version number).srec and Flash File System image file CCC-F-(version number).img can only be changed in the factory.
Maintenance | 185 Kernel image files Kernel image files contain code that forms the basis of the microprocessor’s operating system. There can only ever be two kernel image files in the image table, the active and the inactive. Kernel filenames have the following format: C-CC-K-(version number).img e.g. C-CC-K-7_1_4.img To upload a kernel image file; 1. Select Local > Maintenance > Upload > Kernel 2. Browse to the location of the file required to be uploaded into the terminal *.img. 3. Click on Upload.
Maintenance | 186 Firmware image files Firmware image files contain instructions to configure the various programmable logic elements in the terminal. There can only ever be two firmware image files for the same HSC version in the image table, the active and the inactive. Firmware image filenames have the following format: C-fpga_Ef-x-y-z.img e.g. C-fpga_E5-0-6-4.img where f indicates the function (motherboard, interface card, etc).
Maintenance | 187 Viewing the image table To view the image table: 1. Select Link or Local or Remote > Maintenance > Image Table. The image table shows the following information: Heading Function Index A reference number for the image file Type The image is not currently being used by the system and could be deleted.
Maintenance | 188 Changing the status of an image file To change the status of an image: 1. Select Link or Local or Remote > Maintenance > Image Table. 2. Select the image you wish to change and click Edit. 3. On the Image Details, select the status from the Command drop-down list and click Apply. Status Function Active The image is currently being used by the system. Inactive The image is not currently being used by the system and could be deleted.
Maintenance | 189 Rebooting the terminal The local or remote terminals can be rebooted by SuperVisor. You can specify a ‘Soft Reboot’ which reboots the terminal without affecting traffic or a ‘Hard Reboot’ which reboots the terminal (similar to power cycling the terminal). You can specify an immediate reboot or setup a reboot to occur at a predetermined time. To reboot the terminal: 1. Select Link or Local or Remote > Maintenance > Reboot. 2. Select the Reboot Type field: None: Do nothing.
Maintenance | 190 Support summary The support summary page lists key information about the terminal, for example, serial numbers, software version, frequencies and so on. To view the support summary: Select Link or Local or Remote > Maintenance > Support Summary.
Maintenance | 191 Installing interface cards Caution: You must power down the terminal before removing or installing interface cards. Interface cards are initially installed in the factory to the customers’ requirements however, during the life of the product, additional interface cards may need to be installed. Unless the terminals are protected (see "Protected terminals" on page 163), installing new interface cards involves a substantial interruption of traffic across the link.
Maintenance | 192 Preparing the terminal for new interface cards To prepare the terminal for a new interface card: 1. Remove the terminal from service by first switching off the terminal power. For an AC powered terminal, remove the AC power connector. For a DC powered terminal, switch off the DC circuit breaker or supply fuse. 2. Remove all other cables from the terminal, marking their locations first, if necessary, to aid later restoration. The safety earth connection must be the last cable removed. 3.
Maintenance | 193 6. Remove the card securing screw from the required interface slot. 7. There are two types of interface slot blanking plates, the seven tab break off and the single slot type (newer type). If the blanking plate is the seven tab break off, remove the slot blanking tab by folding the tab to and fro until it breaks off. If the blanking plate is the single slot type, unclip the blanking plate from behind the slot (assuming that the card securing screw has already been removed).
Maintenance | 194 Installing an interface card To install an interface card: 1. Remove the interface card from its packaging and static-safe bag. Caution: To avoid static damage to the terminal or the interface card being installed, use a static discharge wristband or similar antistatic device. 2. Offer the interface card into the chassis at an angle until the front panel of the card engages in the chassis. 3.
Maintenance | 195 4. Replace the card securing screw. Note: Some interface cards may not have the bracket to accept the card securing screw. 5. Replace the fascia and top covers, restore all cables, and power up the terminal.
Maintenance | 196 Configuring a slot 1. Select Link or Local or Remote > Interface > Slot Summary. 2. Select the required slot and click Configure Slot. 'Slot' shows the slot the interface card is plugged into in the terminal (A – H). Details of the interface card currently installed in the slot are: 'H/W’ (hardware revision).
Troubleshooting | 197 14. Troubleshooting Loopbacks Loopbacks are used as a tool for testing or as part of the commissioning process and will affect customer traffic across the link. The terminal supports three types of loopbacks: RF radio loopback Interface loopbacks, set at the interface ports Timeslot loopbacks RF radio loopback The RF radio loopback provides a loopback connection between the radio Tx and radio Rx. Each terminal is looped back independently.
Troubleshooting | 198 Interface loopbacks The interface loopback provides a loopback connection for the customer-connected equipment. All traffic arriving from the customer interface is looped back. These loopbacks are applied on a port-by-port basis and can only be enabled on active ports i.e. has to be activated by assigning traffic to it by the Cross Connections application. The interface card green LED flashes while the loopback is active.
Troubleshooting | 199 Alarms The LEDs (OK, RX, and TX) on the front panel illuminate either orange or red when there is a fault condition: Orange indicates a minor alarm that should not affect traffic across the link. Red indicates a major alarm condition that could affect traffic across the link. A major or minor alarm can be mapped to the external alarm outputs (see “Configuring the external alarm outputs” on page 76).
Troubleshooting | 200 Alarm Explanation Synthesizer Status The selected transmit frequency is outside the tuning range of the transmitter synthesizer Modem Lock The terminal modem is not synchronized with the modem at the other end of the link TX Temp Shutdown The transmitter power amplifier temperature is greater than 75°C. The transmitter has shut down to prevent damage. TX Temp Warning The transmitter power amplifier temperature is greater than 70°C.
Troubleshooting | 201 Viewing the alarm history The alarm history page shows the historical alarm activity for up to 50 alarms. This page refreshes every 30 seconds. To view the alarm history: Select Link or Local or Remote > Alarms > Alarm History.
Troubleshooting | 202 Viewing interface alarms To view the alarms for a particular interface: 1. Select Link or Local or Remote > Interface > Interface Summary. 2. Select the desired interface card slot from the Interface Summary and click Alarms.
Troubleshooting | 203 Clearing alarms Select Link or Local or Remote > Alarms > Clear Alarms MHSB Command If a MHSB switchover event occurs, the OK LED on the front panel changes to orange. To clear the MHSB switchover alarm: Select Clear Switched Alarm from the MHSB Command drop-down list and click on Apply. Image Table Alarm An image table alarm appears if a problem occurred during the boot process which may have left the image table in an inconsistent state.
Troubleshooting | 204 Identifying causes of alarms The following are possible causes of an alarm.
Troubleshooting | 205 RX LED Colour Alarm condition Suggested action Orange Low RSSI Check that all antenna and feeder cables are firmly connected and not damaged or kinked Check there is no damage to the antenna Check the TX power and alarm status of the remote terminal Orange Receiver AGC Contact your local 4RF representative Red Receiver power supply Contact your local 4RF representative Colour Alarm condition Suggested action Orange Reverse power Check that all antenna and feeder cable
Troubleshooting | 206 E1 / T1 alarm conditions The QJET interface yellow LED indicates: Loss of signal (LOS) A loss of signal alarm occurs when there is no valid G.703 signal at the E1 / T1 interface RX input from the downstream system. This alarm masks the LOF and AIS received alarms. Loss Of Frame alignment (LOF) A loss of frame alignment alarm occurs when the E1 / T1 interface RX input receives a valid G.703 signal (code and frequency) but does not receive a valid G.704 signal i.e.
Troubleshooting | 207 System log SuperVisor automatically keeps a log, known as 'syslog', which captures all alarms, errors and events for each terminal. You can specify that the ‘syslog’ is saved to a particular file (see "Setting up for remote logging” on page 209). You can then email this file to customer service, if requested, to enable them to fault-find more accurately. 6 Checking the syslog To view the Syslog: 1. Select Local > Performance > Logging > Syslog.
Troubleshooting | 208 2. The system log is quite hard to decipher in Internet Explorer. If you're using Internet Explorer, select View > Source, which opens the file in a more legible layout in Notepad (see illustration below). Save or print this file, as required. 3. If you want to save the system log, you can save it from within Notepad (or Internet Explorer). Select File > Save As. Navigate to where you want to save the file.
Troubleshooting | 209 Setting up for remote logging Note: When setting up to save the system log to a specific computer, be aware that the file is constantly updated and may get quite large quite quickly. To set up a terminal for remote logging: 1. Copy the TFTP server application (tftpd32.exe, which is located in the TFTPD directory) from the terminal product CD into a suitable directory on the PC (for example, C:\Program Files\TFTP Server). 2.
Troubleshooting | 210 7. In SuperVisor, select Link or Link or Local or Remote > Terminal > Advanced. 8. In the Remote Syslog Address field, enter the IP address of the PC on which the Syslog server is running. 9. In the Remote Syslog Port field, enter 514. 10. Reboot the terminal (Link or Local or Remote > Maintenance > Reboot). 11. Open the directory where the system logs are being saved to. You should see a file called syslog.txt.
Interface connections | 211 15. Interface connections RJ-45 connector pin assignments RJ-45 pin numbering Interface traffic direction All interface traffic directions and labels used in this manual refer to the direction relative to the terminal. Refer to the diagram below. The traffic direction describes the transmit / receive paths and the direction of handshaking and clocking signals, depending on the interface.
Interface connections | 212 QJET Interface connections Pin number Pin function Direction TIA-568A wire colour 1 Transmit Output Green/white 2 Transmit Output Green 3 Not used 4 Receive Input Blue 5 Receive Input Blue/white 6 Not used Orange 7 Not used Brown/white 8 Not used Brown Orange/white RJ-45 connector LED indicators LED Status Explanation Green On Normal operation Yellow On Loss of signal (LOS) or Alarm Indication Signal (AIS) or Loss Of Frame alignment (LOF)
Interface connections | 213 Ethernet interface connections Pin number Pin function Direction TIA-568A wire colour 1 Transmit Output Green/white 2 Transmit Output Green 3 Receive Input Orange/white 4 Not used Blue 5 Not used Blue/white 6 Receive 7 Not used Brown/white 8 Not used Brown Input RJ-45 connector LED indicators LED Status Explanation Green On Ethernet activity Orange
Interface connections | 214 Q4EM Interface connections Pin number Pin function Direction TIA-568A wire colour 1 M Input Green/white 2 M1 Input Green 3 Receive (Ra/R) Input Orange/white 4 Transmit (Tb/R1) Output Blue 5 Transmit (Ta/T1) Output Blue/white 6 Receive (Rb/T) Input Orange 7 E Output Brown/white 8 E1 Output Brown RJ-45 connector LED indicators LED Status Explanation Green On Normal operation (M signal) Yellow On Alarm condition (E signal) Green Flashin
Interface connections | 215 E&M Signalling types The Q4EM E&M signalling leads are optically isolated, bi-directional lines which can be externally referenced to meet any of the EIA-464 connection types I, II,IV or V (as shown below). The M1 lead associated with the M wire detector can be externally referenced to earth or battery as required. The E1 lead associated with the E wire output can be externally referenced to earth or battery as required.
Interface connections | 216
Interface connections | 217 DFXS Interface connections The subscriber interface connects the terminal to the customer's 2 wire telephone via a 2 wire line. Each 2 wire channel has two access points: one connects to a customer; the other is a local test port. Warning: If there is a power failure at either terminal, any telephone connected at the DFXS will not operate. Please ensure that a separate telephone that is not dependent on local power is available for use in an emergency.
Interface connections | 218 DFXO Interface connections The DFXO interface connects the terminal to the telephone network via a 2 wire line. Each DFXO channel has two access points: one connects to a customer; the other is a local test port.
Interface connections | 219 HSS Interface connections The connector on the high-speed synchronous serial interface is a high density LFH-60 (as used on standard Cisco WAN port serial interface cables and equivalents). The interface specification (X.21 / V.35 etc) is automatically changed by simply changing the type of interface cable connected to the HSS.
Interface connections | 220 Synchronous cable assemblies Sync EIA/TIA-232 for DTE (Part number: Cab Sync 232MT) Pin number Pin function Direction 1 Ground - 2 TXD Input 3 RXD Output 4 RTS Input 5 CTS Output 6 DSR Output 7 Circuit DCD - 8 DCD Output 15 TXC Output 17 RXC Output 18 LTST Input 20 DTR Input 24 TXCE Input Sync EIA/TIA-232 Cable Assembly for DCE (Part number: Cab Sync 232FC) Pin number Pin function Direction 1 GND - 2 TXD Output 3 RXD Input 4
Interface connections | 221 EIA/TIA-449 Serial Cable Assembly for DTE (Part number: Cab Sync 449MT) Pin number Pin function Direction 1 Shield Ground - 4 22 SD+ SD- Input Input 5 23 ST+ ST- Output Output 6 24 RD+ RD- Output Output 7 25 RS+ RS- Input Input 8 26 RT+ RT- Output Output 9 27 CS+ CS- Output Output 10 37 LL SC Input _ 11 29 DM+ DM- Output Output 12 30 TR+ TR- Input Input 13 31 RR+ RR- Output Output 17 35 TT+ TT- Input Input 19 20 SG RC -
Interface connections | 222 EIA/TIA-449 Serial Cable Assembly for DCE (Part number: Cab Sync 449FC) Pin number Pin function Direction 1 Shield Ground _ 4 22 SD+ SD- Output Output 5 23 ST+ ST- Input Input 6 24 RD+ RD- Input Input 7 25 RS+ RS- Output Output 8 26 RT+ RT- Input Input 9 27 CS+ CS- Input Input 10 37 LL SC Output _ 11 29 DM+ DM- Input Input 12 30 TR+ TR- Output Output 13 31 RR+ RR- Input Input 17 35 TT+ TT- Output Output 19 20 SG RC -
Interface connections | 223 V.35 Serial Cable Assembly for DTE (Part number: Cab Sync V35MT) Pin number Pin function Direction A Frame Ground B Circuit Ground C RTS Input D CTS Output E DSR Output F RLSD Output H DTR Input K LT Input P S SD+ SD- Input Input R T RD+ RD- Output Output U W SCTE+ SCTE- Input Input V X SCR+ SCR- Output Output Y AA SCT+ SCT- Output Output V.
Interface connections | 224 X.21 Serial Cable Assembly for DTE (Part number: Cab Sync X21MT) Pin number Pin function Direction 1 Shield Ground - 2 9 Transmit+ Transmit- Input Input 3 10 Control+ Control- Input Input 4 11 Receive+ Receive- Output Output 5 12 Indication+ Indication- Output Output 6 13 Timing+ Timing- Output Output 8 Circuit Ground X.
Interface connections | 225 EIA-530 Serial Cable Assembly for DCE (Part number: Cab Sync 530FC) Pin number Pin function Direction 2 14 BA(A), TXD+ BA(B), TXD- Output Output 3 16 BB(A), RXD+ BB(B), RXD- Output Outputcc 4 19 CA(A), RTS+ CA(B), RTS- Output Output 5 13 CB(A), CTS+ CB(B), CTS- Input Input 6 22 CC(A), DSR+ CC(B), DSR- Input Input 1 - Shield - 8 10 CF(A), DCD+ CF(B), DCD- Input Input 15 12 DB(A), TXC+ DB(B), TXC- Input Input 17 9 DD(A), RXC+ DD(B), RXC- Input Input 18
Interface connections | 226 EIA-530 Serial Cable Assembly for DTE (Part number: Cab Sync 530MT) Pin number Pin function Direction 2 14 BA(A), TXD+ BA(B), TXD- Input Input 3 16 BB(A), RXD+ BB(B), RXD- Output Output 4 19 CA(A), RTS+ CA(B), RTS- Input Input 5 13 CB(A), CTS+ CB(B), CTS- Output Output 6 22 CC(A), DSR+ CC(B), DSR- Output Output 1 - Shield - 8 10 CF(A), DCD+ CF(B), DCD- Output Output 15 12 DB(A), TXC+ DB(B), TXC- Output Output 17 9 DD(A), RXC+ DD(B), RXC- Output Output
Interface connections | 227 Cable WAN connectors Cisco LFH-60 cable name WAN connector Connector gender Label on WAN end 232FC DB-25 female 'to DTE' 232MT DB-25 male 'to DCE' 449FC DB-37 female 'to DTE' 449MT DB-37 male 'to DCE' V35FC M34 female 'to DTE' V35MT M34 male 'to DCE' X21FC DB-15 female 'to DTE' X21MT DB-15 male 'to DCE' 530FC DB-25 female 'to DTE' 530MT DB-25 male 'to DCE'
Interface connections | 228 QV24 Interface connections Pin number Pin function Direction TIA-568A wire colour 1 RTS Input Green / white 2 DTR Input Green 3 TXD Input Orange / white 4 Ground 5 DCD / Ground Input Blue / white 6 RXD Output Orange 7 DSR Output Brown / white 8 CTS Output Brown Blue RJ-45 connector LED indicators LED Status Explanation Green On / flashing Transmit data Yellow On / flashing Receive data
Alarm types and sources | 229 16. Alarm types and sources Alarm types Note: If you need to contact customer support about any of these alarms, please supply the reference number.
Alarm types and sources | 230 Receiver alarms Ref Type Explanation B1 rxADCChEightHi The AGC voltage is high B2 rxADCChEightLo The AGC voltage is low B3 rxRSSIHi The receiver maximum input level has been exceeded B4 rxRSSILo The RSSI is below the alarm threshold setting (see page 73) B5 rxADCChSixHi The synthesizer tuning voltage is high B6 rxADCChSixLo The synthesizer tuning voltage is low B7 rxADCChSevenHi The -1.5 VDC power supply is high B8 rxADCChSevenLo The -1.
Alarm types and sources | 231 Motherboard alarms Ref Type Explanation E1 mbFan1Fail Fan 1 failure E2 mbFan2Fail Fan 2 failure E3 mbCardMismatch The expected interface card is different to the card that is fitted E4 mbHwHsc A MUX card has an unsupported HSC number QJET alarms Ref Type Explanation F1 e1AIS The E1 interface RX input has received an Alarm Indication Signal from the downstream equipment.
Alarm types and sources | 232 DFXO alarms Ref Type Explanation G1 fxoCodecOvld Codec receive signal overload detected G2 fxoBillToneOvld Billing tone overload detected G3 fxoUnplug Exchange line unplugged from interface G4 fxoCurrentOvld Loop current overload detected (greater than 100 mA) DFXS alarms Ref Type Explanation H1 fxsCalibError The phone was off-hook during the initialization phase H2 fxsDCDCError DC-DC converter low battery voltage error H3 fxsCasLock Loss of CAS lock
Alarm types and sources | 233 External alarm inputs Ref Type Explanation L1 externalAlarm1 There has been an alarm on external alarm input 1 L2 externalAlarm2 There has been an alarm on external alarm input 2 Remote terminal alarms Ref Type Explanation M1 remoteMajorAlarm There has been a major alarm on the remote terminal M2 remoteMinorAlarm There has been a minor alarm on the remote terminal Cross connect alarms Ref Type Explanation N1 ccNoBandwidth There is insufficient bandwidth
Country specific settings | 235 17. Country specific settings The following table shows the country-specific settings for the DFXO / DFXS interface cards. If the country you want is not listed, contact the local telephone company for assistance.
Country specific settings | 236 Macao 600Ω On < 500 μs > 10 MΩ 16 Vrms Malaysia 600Ω On < 500 μs > 10 MΩ 16 Vrms Malta TBR21 270Ω + (750Ω ║ 150nF) On 3 ms > 10 MΩ 16 Vrms Mexico 600Ω On < 500 μs > 10 MΩ 16 Vrms Morocco TBR21 270Ω + (750Ω ║ 150nF) On 3 ms > 10 MΩ 16 Vrms Netherlands TBR21 270Ω + (750Ω ║ 150nF) On 3 ms > 10 MΩ 16 Vrms New Zealand BT3 (370Ω + (620Ω ║ 310nF)) On < 500 μs > 10 MΩ 16 Vrms Nigeria TBR21 270Ω + (750Ω ║ 150nF) On 3 ms > 10 MΩ 16 Vrms N
Specifications | 237 18. Specifications RF specifications Frequency Bands ETSI R1 Frequency Bands FCC R1 Frequency Band 300 MHz band Frequency Band Limits 330 - 400 MHz Synthesizer Step Size 6.25 kHz 400 MHz band 400 - 470 MHz 6.25 kHz 600 MHz band 620 - 715 MHz 12.5 kHz 700 MHz band 698 - 806 MHz 25 kHz 800 MHz band 805 - 890 MHz 25 kHz 900 MHz band 850 - 960 MHz 25 kHz 1400 MHz band 1350 - 1550 MHz 12.5 kHz 2000 MHz band 1900 - 2300 MHz 62.
Specifications | 238 System performance specifications Capacity ETSI C2 Channel size 25 kHz C3 50 kHz C3 QPSK Gros s 150 kHz C4 200 kHz C5 48 kbit/s 168 kbit/s 208 kbit/s 256 kbit/s Gros s Gros s 16 kbit/s 0 kbit/s 312 kbit/s 400 kbit/s 16 kbit/s 264 kbit/s 536 kbit/s 672 kbit/s 808 kbit/s Gros s 6 tim es lots 4 tim eslots 10 tim es lots 12 tim es lots Ways ide 8 kbit/s 24 kbit/s 32 kbit/s 40 kbit/s 336 kbit/s 680 kbit/s 840 kbit/s Gros s 5 tim eslots 8 tim eslots 4 ti
Specifications | 239 Capacity FCC D1 Channel size 25 kHz D2 (20 kHz occ bw) (part 90) 100 kHz D3 (part 101) 200 kHz D4 (part 101) 250 kHz D5 (part 27) 500 kHz D5 (part 27) Note D1 Note D2 Note D3 Note D4 Note D5 QPSK Gros s T1 32 QAM 64 QAM 56 kbit/s 72 kbit/s 88 kbit/s 0 tim eslots Ways ide Gros s 16 QAM 136 kbit/s 1 tim es lots 56 kbit/s 8 kbit/s 24 kbit/s 280 kbit/s 352 kbit/s 424 kbit/s T1 2 tim eslots Ways ide 8 kbit/s 24 kbit/s 32 kbit/s 312 kbit/s 632 kbit/s 792 kbi
Specifications | 240 Receiver sensitivity R1 Channel size QPSK 25 kHz 50 kHz -109 dBm 16 QAM 32 QAM 64 QAM -105 dBm -102 dBm -99 dBm -103 dBm -100 dBm -97 dBm 75 kHz -107 dBm -101 dBm -98 dBm -95 dBm 100 kHz -106 dBm -100 dBm -97 dBm -94 dBm 150 kHz -104 dBm -98 dBm -95 dBm -92 dBm 200 kHz -102 dBm -96 dBm -93 dBm 250 kHz -101 dBm -95 dBm -92 dBm 500 kHz -99 dBm -93 dBm -90 dBm -87 dBm 1 MHz -96 dBm -90 dBm -87 dBm -84 dBm 1.
Specifications | 241 Note: The default Modem Interleaver Mode setting is on for channel sizes of 250 kHz and greater and off for channel sizes of 200 kHz and less (see “Modem Interleaver Mode” on page 63). Typical end-to-end link delay (ETSI) - interleaver off L1 Channel size QPSK 25 kHz 50 kHz 41.8 m s 16 QAM 32 QAM 64 QAM 48.3 m s 38.7 m s 34.2 m s 22.8 m s 19.2 m s 16.4 m s 75 kHz 34.8 m s 18.5 m s 16.2 m s 13.5 m s 100 kHz 26.2 m s 14.6 m s 12.0 m s 10.5 m s 150 kHz 17.
Specifications | 242 Transmitter ETSI Modulation Type Frequency bands Power output range (in 1 dB steps) +21 to +35 dBm QPSK 300, 400, 600, 700, 800, 900 & 1400 MHz bands QPSK 2000, 2500 MHz bands +20 to +34 dBm 16 QAM all bands +17 to +31 dBm 32 QAM all bands +16 to +30 dBm 64 QAM all bands +15 to +29 dBm Transmitter FCC QPSK 400 MHz band Power output range (in 1 dB steps) +21 to +35 dBm QPSK 900 MHz band +15 to +29 dBm 16 QAM 400 MHz band +17 to +31 dBm 16 QAM 900 MHz band +15
Specifications | 243 Duplexer ETSI F1 Passband Frequency Bands TX / RX Split 500 kHz 300, 400 MHz bands > 5 MHz 2 MHz 300, 400 MHz bands > 9.45 MHz 3.
Specifications | 244 Interface specifications Ethernet interface General Diagnostics Interface RJ-45 * 4 (Integrated 4-port switch) Cabling CAT-5 UTP, supports auto MDIX (Standard Ethernet) Maximum line length 100 metres on cat-5 or better Bandwidth allocation n x 8 kbit/s up to max available. n x 64 kbit/s is recommended for higher bandwidth terminals 500 kHz, 32 QAM. Maximum is 16384 kbit/s (or limited by radio bandwidth).
Specifications | 245 Q4EM Quad 4 wire E&M interface General Analogue Signalling Diagnostics Audio 64 kbit/s (PCM A-Law as per ITU G.711) 32, 24 & 16 kbit/s (ADPCM as per ITU G.726 and ANSI TI.303) E&M signalling 8 kbit/s per port Maximum line length 400 metres Transmission performance characteristics ITU G.712 E4 for an operating level range of -14 dBr to +4 dBr Input level range -14.0 dBr to +4.0 dBr in 0.5 dB steps Output level range -14.0 dBr to +4.0 dBr in 0.
Specifications | 246 DFXO Dual foreign exchange office interface General Analogue Audio 64 kbit/s (PCM as per ITU G.711) 32, 24 and 16 kbit/s (ADPCM as per ITU G.726 and ANSI TI.303) Signalling allocation 8 or 32 kbit/s allocated for CAS Companding A-Law or µ-Law Maximum line length 600 metres (2000 feet) on 0.
Specifications | 247 Pulse dialing Transparent decadic signalling at 7 - 14 PPS with break period limits of 60 - 73 % Pulse distortion 4:1 multiplexed < 2.250 ms Non-multiplexed ≤ 250 µs Reversals Line polarity reversal detection Metering level sensitivity 12 kHz / 16 kHz billing tone detection with a selectable level sensitivity of -17dBm to -40 dBm in 1dB steps into 200 Ω (60 mV rms to 5 mV rms into 200 Ω).
Specifications | 248 DFXS Dual foreign exchange subscriber interface General Analogue Audio 64 kbit/s (PCM as per ITU G.711) 32, 24 and 16 kbit/s (ADPCM as per ITU G.726 and ANSI TI.303) Signalling Allocation 8-32 kbit/s allocated for CAS Compression coding A-Law or µ-Law Maximum line length 600 metres (2000 feet) on 0.
Specifications | 249 Signalling Physical Diagnostics Feed voltage output -48 V (160 + 160 Ω voltage source current limited) Loop current limit 35 mA Seize signal Loop start only (no ground start) Loop detect threshold 10 - 12 mA (step function between on hook and off hook) Non loop current 4 - 6 mA (step function between on hook and off hook) Pulse dialing Transparent decadic signalling at 7 - 14 PPS with break period limits of 60 - 73 % (with loop current > 23 mA) Pulse distortion 4:1 mult
Specifications | 250 QV24 Quad V.24 asynchronous data interface Interface ITU-T V.24/EIA/TIA RS-232E Bandwidth allocation 8-120 kbit/s in 8 kbit/s steps (dependent on rate selected) Control line allocation 8 kbit/s Maximum line length 10 metres Data clamp Mark hold when out of sync. Control line clamp Off when loss of sync. Clock Internally generated from 2.
Specifications | 251 External alarm interfaces Alarm inputs Alarm outputs Overall Detector type Isolated current detectors Detection current 5.0 to 6.
Specifications | 252 Power specifications AC Power supply Nominal voltage Input voltage range Power consumption Max VA Frequency 115 VAC 103 - 127 Vrms 63 - 180 W 400 VA 47 - 63 Hz 230 VAC 207 - 254 Vrms 63 - 180 W 400 VA 47 - 63 Hz DC Power supply Nominal voltage Input voltage range Power consumption Maximum input current ±12 VDC 10.5 to 18 VDC 63 - 180 W 18 A ±24 VDC 20.
Specifications | 253 MHSB specifications MHSB protection RF switch Tributary switch TX relay loss ≈ 1.5 dB Splitter loss ≈ 3.
Product end of life | 255 19. Product end of life End-of-life recycling programme (WEEE) The WEEE Directive concerns the recovery, reuse, and recycling of electronic and electrical equipment. Under the Directive, used equipment must be marked, collected separately, and disposed of properly.
Abbreviations | 257 20.
Acknowledgments and licensing | 259 21. Acknowledgments and licensing The Aprisa XE product software runs the GNU Linux Operating System and incorporates several other packages in accordance with the free software philosophy. The following list identifies the licensed software used: BusyBox Description: Tiny versions of common UNIX utilities Reference: http://busybox.net/ License Type: GNU General Public License (GPL) DropBear SSH Server Description: Small and secure SSH Server Reference: http://matt.
Acknowledgments and licensing | 260 Software licensed under the GPL Some of the above packages licensed under the GPL have been modified by 4RF Communications Limited. The copyright holders of these modified packages (including 4RF Communications Limited) agree to them being distributed under the terms of the General Public License.
Acknowledgments and licensing | 261 Net-SNMP Part 1: CMU/UCD (BSD like) Copyright © 2001-2003, Networks Associates Technology, Inc All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Acknowledgments and licensing | 262 Part 3: Cambridge Broadband Ltd (BSD) Portions of this code are copyright © 2001-2003, Cambridge Broadband Ltd. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Acknowledgments and licensing | 263 Part 5: Sparta, Inc. (BSD) Copyright © 2003-2004, Sparta, Inc All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Commissioning Forms | 265 22.
Commissioning Forms | 266
Index | 267 23. Index 2 2 wire .............................................................. 91 4 4 wire .............................................................. 89 A AC power supply ............................................ 35 access rights................................................... 57 accessory kit................................................... 17 AIS................................................................ 206 alarms alarm summary........................................
Index | 268 alarm conditions ...................................... 206 framed ............................................. 135, 136 unframed ................................................. 135 earthing............................................... 22, 24, 37 EIA-530......................................................... 109 environmental requirements........................... 23 error counters ............................................... 171 Ethernet capacity ....................................
Index | 269 identifying colours.................................... 204 interface...........212, 213, 214, 217, 218, 219 RF protection switch................................ 156 tributary protection switch ....................... 155 lightning protection ......................................... 24 link budget ...................................................... 22 link capacity, assigned ................................. 124 link performance ................................... 169, 173 LOF..............
Index | 270 configuring............................................... 196 terminal...................................................... 28 SNMP ............................................................. 67 MIB details................................................. 70 setting access controls.............................. 68 setting trap destinations ............................ 69 viewing traps ............................................. 70 specifications ...........................................
Index | 271 W web browser cache, clearing........................ 180 WEEE ...........................................................