CFIP PhoeniX Series TDM/IP Split Mount System Technical Description & Configuration Guide Product code: S0DRFMD1 SAF Tehnika JSC 2015
Table of Contents 1 Overview .................................................................................................................................... 5 1.1 CFIP PhoeniX TDM/IP split mount system .......................................................................................5 1.2 CFIP PhoeniX feature Summary .......................................................................................................6 1.2.1 1.2.2 1.2.3 1.2.4 1.2.5 1.3 1.4 1.4.1 1.4.2 1.4.3 1.4.4 1.4.
4.3.5 4.4 Advanced Protection Configuration ........................................................................................................ 53 System Configuration .................................................................................................................... 54 4.4.1 4.4.2 4.4.3 4.4.4 4.4.5 4.4.6 4.5 User Configuration .................................................................................................................................. 55 Name configuration .
8 CFIP Discovery Protocol ........................................................................................................... 110 8.1 CFIP Unit Discovery Procedure .................................................................................................... 110 8.2 Discovery Protocol Performance Examples ................................................................................. 110 8.2.1 8.2.2 8.2.
Proprietary notice The information presented in this guide is the property of SAF Tehnika, JSC. No part of this document may be reproduced or transmitted without proper permission from SAF Tehnika, JSC. The specifications or information contained in this document are subject to change without notice due to continuing introduction of design improvements. If there is any conflict between this document and compliance statements, the latter will supersede this document.
1.2 CFIP PhoeniX feature Summary 1.2.1 Main Features • Split mount system solution • Capacity: up to 363 Mbps • Channel Bandwidth: 3.5 / 7 / 14 / 28 / 40 / 56 MHz • Modulations: 4QAM / 16QAM / 32QAM / 64QAM / 128QAM / 256QAM • Interfaces: 10 / 100 / 1000 Eth + 20E1/T1 • Traffic: Ethernet only, Eth+1E1/T1 to Eth+20E1/T1 • Frequency bands: 6 / 7 / 8 / 10 / 11 / 13 / 15 / 18 / 23 / 26 / 38 GHz • ACM and ATPC with QoS four priority queues • 802.1Q VLAN support 1.2.
Figure 1.2 CFIP PhoeniX ODU 1.2.4 IRFU mechanical features • Indoor radio unit (IDU+IRFU) • 2U high • Power consumption: 13-39W • Dimensions 90x430x260 mm, weight 5.8 kg. Figure 1.3 CFIP PhoeniX IRFU 1.2.
Figure 1.4 CFIP PhoeniX IDU connectors 1.3 CFIP PhoeniX ODU Parameters • CFIP PhoeniX is a good example of latest achievements in modem and transceiver development, providing both excellent radio parameters (System Gain), due to use of QAM modulations and efficient despite it consumes small amount of power Tx/Rx part of the system. • RSL Threshold at for 6GHz ODU BER 10 , 56MHz, 256QAM, 363Mbps: -64 dBm.
• The outgoing (Tx) traffic at each site is passed to both ODUs, and both are always transmitting; • The incoming (Rx) traffic is picked from one of the ODUs; • 1+1 configuration provides hardware redundancy and mitigates multipath fading; • Both Tx and Rx switching is hitless. 1.4.
Figure 1.7 CFIP PhoeniX 1+1 SD configuration 1.4.5 CFIP PhoeniX Ring Topology • Utilization of STP protocol allows CFIP PhoeniX operation in ring topology (for Ethernet traffic only) Figure 1.8 CFIP PhoeniX ring topology configuration 10 CFIP PhoeniX Series TDM/IP Split Mount System Technical Description and Configuration Guide • Rev. 1.
1.
Ports CFIP PhoeniX ODU CFIP PhoeniX IRFU A) B) N-Type or flange Tx and Rx ports1 Antenna N-Type or flange IF to IDU N-Type SMA BNC 2-port for multi-meter RSSI Power 2-pin power port --- (over IF port) (alternative to IF port) Mechanical & Electrical Operational use Conforms to ETSI EN 300 019 Class 4.1, IP65, NEMA 4X Conforms to ETSI EN 300 019 Class 3.1E, IP20, NEMA 1 -33°C to +55°C -33°C to +55°C 288x288x80 mm / 3.5 kg 19” 2U rack 90x430x260 / 5.
Band Frequency range Duplex offset 10 GHz 10.15 – 10.68 GHz 65 MHz, 91 MHz, 300 MHz, 350 MHz 11 GHz 10.7 – 11.7 GHz 490 MHz, 500 MHz, 530 MHz 13 GHz 12.75 – 13.25 GHz 225 MHz, 266 MHz 15 GHz 14.4 – 15.35 GHz 315 MHz, 322 MHz, 420 MHz, 475 MHz, 490 MHz, 644 MHz, 728 MHz 18 GHz 17.7 – 19.7 GHz 1008 MHz, 1010 MHz, 1560 MHz 23 GHz 21.2 – 23.6 GHz 1008 MHz, 1036 MHz, 1200 MHz, 1232 MHz 26 GHz 24.25 – 27.5 GHz 800 MHz, 1008 MHz 38 GHz 38.
CFIP PhoeniX ODU CFIP ODU RSL at 10-6 (dBm) and Total Payload Capacity (Mbps) 6 7 8 10 BW**, MHz Modulation FEC*** GHz GHz GHz GHz 3.
CFIP ODU RSL at 10-6 (dBm) and Total Payload Capacity (Mbps) BW**, MHz 40 Modulation FEC*** 7 GHz 8 GHz 10 GHz 11 GHz 13 GHz 15 GHz 18 GHz 23 GHz 26 GHz 38 GHz Bit rate, Mbps 4QAM Strong -89 -87.5 -88 -87.5 -88 -88 -88 -88 -87.5 -89.5 -83.5 49 16QAM Strong -82.5 -81.5 -81.5 -81 -82 -82 -81.5 -82.5 -81 -83.5 -77 98 32QAM Strong -80 -78.5 -79 -78.5 -79.5 -79.5 -79 -79.5 -78.5 -80.5 -74.5 127 64QAM Strong -77 -76 -75.5 -75.5 -76.
1.6 Cable Requirements IDU-ODU cable IDU–ODU cable is a 50 Ω coaxial cable intended to interconnect the Indoor Unit with the Outdoor Unit. Any type of 50 Ω cable of good quality can be used; the cable should be equipped with N–type male connectors on each end. There are two N–type male connectors included in each radio unit delivery that fit RG–213 cables or other cables with a surface diameter of 10 mm.
Figure 1.10 Cable for connecting the voltmeter to the CFIP PhoeniX ODU RSSI port 1.7 Labelling The label can be found on the front side of the unit. The label contains the following information (see samples in the picture below): - Model name.
Figure 1.13 Label of the CFIP PhoeniX IRFU Low band side, operating in 6 GHz band P/N Translation for CFIP PhoeniX ODU: - “S” designates CFIP split mount series product; - “18” designates Frequency range (18 GHz) of the Unit; - “RF” designates standard power radio; - “U” designates unified band ODU operating 3.5 - 56MHz; - “05” designates the version number of the Unit; - “L” designates the band side in which ODU operates (H, L); - “A” designates the subband in which ODU operates (A, B, C).
2 Configuration and Management 2.1 Connecting CFIP PhoeniX IDU to power source In case AC/DC Power supply, 48VDC, 80W (EU - P/N I0AB4810, US – P/N I0AB4811, AUS I0AB4818) provided by SAF Tehnika JSC is used to power up CFIP PhoeniX IDU, interconnect IDU and power source through appropriate connectors. Otherwise perform the following steps to ensure that CFIP PhoeniX IDU is powered up correctly: 1.
Figure 2.1 CFIP Phoenix IDU DC Power Cable Connector of type 2ESDV-02 After successful powering of PhoeniX IDU there are four ways to adjust and read settings and operation parameters of the CFIP PhoeniX equipment: 1. using Web terminal connected to the 10/100/1000Base-T Port, 2. using Telnet terminal connected to the 10/100/1000Base-T Port, 3. using NMS or SNMP terminal, connected to the 10/100/1000Base-T Port, or 4. using ASCII console connected to the serial port. 2.1.
prompt command “system reset” Resetting with command prompt command “system reset cold” Restarts modem and CPU of the management controller. Resets all management counters. 2.3 Web Interface This section describes operation of Web interface. 2.3.1 10/100/1000Base-T Ports 10/100/1000Base-T port is used to connect CFIP PhoeniX to a PC or Ethernet network for Web, SNMP and Telnet management. (!) The length of 10/100/1000Base-T Port cable should not exceed 100m. 2.3.
• • • IE v. 6.0 Mozilla Firefox v. 2.0.0.11 Google Chrome Figure 2.4 Supported browsers: “Internet Explorer”, “Mozilla Firefox” and “Google Chrome” After web browsers selection, open it and enter address of the CFIP PhoeniX IDU (Figure 2.5). (!) The IP address of CFIP PhoeniX IDU is 192.168.205.10 Figure 2.
Figure 2.6 Web Interface - main window 2.3.4 Interface Description WEB interface consists of four parts, they are: 1. 2. 3. 4. Top panel, that allows to log out and gives information about device type, software version, device name, IP, serial number and uptime; Menu panel that is used to open links to other pages; Status summary for local and remote devices: this section is available while browsing other pages.
Figure 2.7 Web Interface - main window with section numbering 2.3.5 Command Execution There is “IP configuration” page shown in Figure 2.8. The entire page is divided into smaller fragments: 1. 2. 3. 4. 5. 6. 7. 8. The header of page; Sub-header of single type configuration parameters; Execution controls related to a single type configuration parameters.
“Execute for both” is available in “Main configuration” section during configuration of modem or ATPC parameters for local and remote radio sides simultaneously. Connection between both management CPUs must be established in order to complete successfully configuration execution for both sides. “Rollback on” feature is intended to maintain connectivity of the CFIP link by cancelling last erroneous configuration changes and reverting to previous successful configuration used.
Figure 2.9 Starting configuration wizard Initially, you can specify preferable system name, location name, passwords for guest and admin accounts. (!) Default password for “admin” account is changeme. “guest” account is disabled by default! The next time you will try to access the Web GUI management, you will be asked to enter the user name (guest or admin) and user password. (!) It is highly recommended to name the system after its geographical location.
Figure 2.11 STEP 2. Defining IP address, mask, default gateway and remote IP address The third screen of the wizard is devoted to the modem and radio configuration and requires specifying utilized bandwidth (from 3.5 to 56 MHz), modulation type (4QAM, 16QAM, 32QAM, 64QAM, 128QAM or 256QAM), E1 channel port numbers, Tx power (range depends on modulation chosen) and Tx frequency; besides, the modem and radio data status is being shown. These configuration parameters will determine overall link capacity.
Figure 2.13 STEP 4 Checking settings and executing configuration To verify the settings, we can go to ‘Status’ or the main screen, which is the first option in the navigation panel. If there are no ‘red fields’, everything is set correctly and the link is up. 2.4 Command Prompt Interface CFIP equipment can be monitored and configured by using command interface described in this chapter.
(!) Syntactic notes for command prompt commands – Commands are in bold font. – All arguments (variables) are in italic font. – Subcommands and keywords are in regular font. – Arguments in square brackets ([ ]) are optional but required arguments are in angle brackets (<>). – Alternative keywords are grouped in braces ( {} ) and separated by vertical bars ( | ). – The purpose of each command will be displayed if command is typed with “?” at the end (or any unrecognizable string) is entered, e.g.
Figure 2.15 PuTTY configuration - 1 2) Go to “Keyboard” category and change “The Backspace Key” to “Control-H”: Figure 2.16 PuTTY configuration - 2 3) Press “Open” and after pressing “Enter” key following prompt should appear: 30 CFIP PhoeniX Series TDM/IP Split Mount System Technical Description and Configuration Guide • Rev. 1.
Figure 2.17 PuTTY serial prompt Password is disabled by default. See Chapters 3...7 for available commands. 2.4.2 Telnet connection The Telnet connection to the CFIP PhoeniX is carried out using the Ethernet management connection. Please refer to Chapter 2.3.2 for Ethernet management port connection details. You can use any Telnet client. Below are connection steps with PuTTY - Windows freeware software.
Figure 2.19 PuTTY Telnet prompt See Chapters 3...7 for available commands. 2.4.3 Initial Configuration with Command Prompt Configuration steps using command prompt are as follows: 1. Check the system settings with command ‘status’ 2. Configuration required parameters: (!) Before you set the parameters listed below, you must know what frequency and bandwidth you are allowed to use and at what power you are allowed to transmit.
LED name ODU IDU Modem System Description Green – OK Yellow blinks – ODU Tx mute. Yellow – Rx level alarm; ODU Temperature failure; IDU PSU to ODU state alarm. Red – Tx PLL error alarm; Rx PLL error alarm; ODU RX LOS; ODU TX LOS; ODU RX failure; ODU TX failure; ODU Frequency failure. Red blinks – No data from ODU. Green – OK Yellow – IDU temperature fault; Main supply 48V failure; IDU PSU state alarm; PSU temperature fault; Power supply voltage failure.
3 Status Window The main window in the Web GUI is status window that shows all main system parameters, and, in case of failure or any other problems, it tints a specific parameter in red. To have a better understanding on status window, we will go through every field. Figure 3.1 “Main status” page 1. Shows the name of this CFIP PhoeniX, its IP address, serial number and uptime since the last restart. If uptime is displayed in red, the connection to CFIP management port was lost; 2.
• Rx level (or RSL) at both ends must not differ significantly from the previously calculated value. • Modulation indicates which modulation mode is used. For better operation the same modulation must be set at both ends. • Radial MSE is explained below in the Chapter 3.1.1. • LDPC is explained below in the Chapter 3.1.2. 6. ODU data status – shows if management CPU was able to read data from radio; 7. ODU side – shows the radio side of local and remote CFIP (command line – radio side); 8.
30. IDU temperature – shows the IDU internal temperature in degrees by Celsius and Fahrenheit (command line - diagnostics or status); 31. ODU temperature – shows the ODU internal temperature in degrees by Celsius and Fahrenheit (command line - odu status); 32. Modem temperature – shows the temperature on modem chip in degrees by Celsius and Fahrenheit (command line - diagnostics); 33. IDU input voltage – shows the input voltage of IDU PSU in volts (command line – diagnostics psu status); 34.
Figure 3.2 LDPC decoder structure -6 LDPC stress value thresholds @ BER 1.0⋅10 : -2 - for Strong FEC mode ~ 4.0⋅10 ; -2 - for Weak FEC mode ~ 1.0⋅10 As long as LDPC stress value is under the specified thresholds, the amount of errors (and BER itself) on the output of LDPC remains at zero level. 3.2 Alarm status Table on “Alarm status” page summarizes current alarms by showing alarm group number, date and time the alarm occurred and its name. Figure 3.
Figure 3.4 Ethernet aggregation/protection status 3.4 1. Clear max N/D time – clear maximum no data time; 2. State – displays current device state status – Active or Standby; 3. Previous state – displays previous device state status; 4. Max N/D time: - displays maximum disconnection time between devices; 5.
Figure 3.5 Diagnostics data 1. Inventory information - displays the CFIP PhoeniX IDU and ODU product code, serial number and additional hardware information; 2. Download system information - allows saving system information (output from “full system information page”) in separate txt file on your hard disk drive. Same functionality is available in “ConfigurationSystem configurationService informationDownload system information” (Chapter 4.4.6); 3.
4 Detailed Configuration in Web Graphic User Interface Configuration section in Web interface allows customizing your system to suit your specific needs. 4.1 ODU Configuration The ODU configuration window provides the configuration of CFIP PhoeniX radio part parameters. Below is a short explanation of provided customization fields. 4.1.1 Radio Configuration Figure 4.1 Radio configuration 1. ODU data status – shows if management CPU was able to read data from the radio; 2.
4.1.2 ATPC Configuration To configure ATPC, it is necessary to set Rx (remote) “min” and “max” values and enable the ATPC feature. ATPC update period and ATPC delta are recommended to be left unchanged. It is also possible to change the limit of Tx power correction. (!) Note, that ATPC is mechanism for reducing Tx power, that’s why to make proper use of ATPC, transmitter power (Tx power) must be set to the maximum value. Figure 4.2 ATPC configuration 1.
ATPC Algorithm ACM can be implemented together with automatic transmit power control (ATPC), complimentary features that enhance overall system performance. ATPC reduces the average transmitted power as well as CCI and adjacent-channel interference (ACI), which is caused by extraneous power from a signal in an adjacent channel.
4.2 IDU Configuration 4.2.1 Modem Configuration Figure 4.4 Modem configuration 1. Modem data status – shows if management CPU was able to read data from modem; 2. Modem standard – allows switching between ETSI and ANSI (FCC) standards, changing available bandwidths to 3.5/7/14/28/40/56 MHz and 5/10/20/30/40/50 MHz and changing between E1 and T1 channels respectively (command line – modem standard ); 3. Bandwidth – allows choosing between 3.5 and 56 MHz bandwidths available.
availability based on the priority. As a result, high-priority services such as voice enjoy 99.995% availability, while low-priority services like video streaming are allocated lower priorities. Use of QoS prioritizing defines which services should be transmitted under any link condition and which services should be adapted whenever the link condition is degraded and the link payload is decreased.
The following real-world example illustrates the benefits of ACM. Consider a CFIP link operating at 23 GHz with 56 MHz channel spacing and 45.9 dBi (120 cm) antenna gain. The link is operating in a moderate rain region similar to central Europe with a distance of 15 kilometers. The system operation is set to a minimal payload of 69 Mbps Ethernet for 99.995% availability. Most of the time system would support 363Mbps Ethernet connection instead of a 69 Mbps connection.
• E1 and E1 FAR loopback modes loop signal back to local end and to remote end respectively in bounds of E1 interface. E1 loopback mode must be set on the particular channel you need to test. If no E1 channels are selected, E1 loopback mode is not available. E1 loopbacks are named “interface” and “interface far” in “Loopback name” dropdown menu. • MODEM loopback mode loops signal back to local end after the modem. • IF loopback mode loops signal back to local end by linking intermediate frequencies.
4.3 Protection configuration This section describes 1+1 protection implementation for PhoeniX IDU. The possible 1+1 configuration modes are Frequency diversity (FD), Hot Standby (HSB) and Space diversity (SD). Figure 4.9 1+1 interconnection of two CFIP PhoeniX IDUs (with power protection ports – P/N S0GIPT11) For 1+1 operation two CFIP PhoeniX IDUs (“working” and “protection”) before power is supplied should be interconnected as shown in Figure 4.
Protection mode: Working Protection mode: Working F=F1 Ethernet switch Modem P1 F=F1 ODU1 ODU3 Ethernet switch Modem Protection mode: Protection Working link F=F2 Ethernet switch Modem Protection cable Eth. Protection cable P2 IDU1 192.168.205.10 P4 IDU3 192.168.205.12 Eth. Protection mode: Protection F=F2 ODU2 ODU4 Modem Ethernet switch P3 IDU2 192.168.205.11 IDU4 192.168.205.13 Protection link Port disabled Protection switch 1+1 Port disabled Protection switch 1+1 Figure 4.
Figure 4.11 CFIP PhoeniX configuration for 1+1 FD mode Please refer to Chapter 4.3.5 for details of 1+1 configuration parameters and configuration possibilities via CLI. After successful 1+1 FD configuration, the screen of ‘Protection configuration’ in Web GUI should look as follows: Figure 4.12 Protection configuration window after successful FD configuration 4.3.2 Hot Standby (HSB) and Space Diversity (SD) protection modes For HSB and SD mode two transmitters are operating at the same frequency.
Protection mode: Working Protection mode: Working P1 Ethernet switch Modem ODU1 ODU3 Ethernet switch Modem Protection mode: Protection Ethernet switch Modem IDU2 192.168.205.11 Port disabled Protection switch 1+1 Protection cable Eth. Protection cable P2 IDU1 192.168.205.10 P4 P3 ODU2 ODU4 Tx = mute Tx = mute IDU3 192.168.205.12 Eth. Protection mode: Protection Modem Ethernet switch IDU4 192.168.205.13 Port disabled Protection switch 1+1 Figure 4.13 CFIP PhoeniX HSB mode 1.
Example of configuration for HSB mode: Figure 4.14 CFIP PhoeniX configuration for 1+1 HSB mode After successful 1+1 HSB configuration, the screen of ‘Protection configuration’ in Web GUI should look as follows: Figure 4.15 Protection configuration window after successful HSB configuration Configuration for 1+1 Space Diversity Mode For 1+1 SD mode it is necessary to: • • • • Assign different IP addresses for each IDU.
• It is recommended that ‘Standby’ and ‘Activetry’ times remain default. IDU will remain in appropriate state during forcing it to another state for this specified time. Example of configuration for SD mode: Figure 4.16 CFIP PhoeniX configuration for 1+1 SD mode The same commands can be executed using Web GUI. Please refer to Chapter 4.3.5 for details. After successful 1+1 SD configuration, the screen of ‘Protection configuration’ in Web GUI should look as follows: Figure 4.
1. Value – denotes the names of CFIP PhoeniX units in 1+1 configuration. ‘Local’ and ‘Local alternate’ designates both units (working and protection) at the local side and ‘Remote’ and ‘Remote alternate’ designates both units of remote side. 2. Protection status – denotes that CFIP PhoeniX 1+1 protection is disabled. In case 1+1 Hot Standby mode is enabled the Protection Status window might look as follows: Figure 4.19 Protection status while 1+1 is enabled 1.
Figure 4.21 Advanced protection configuration 1. Protection switch – temporarily switches IDU to active or standby state (command line – prot {active|standby}); 2. Force state – permanently switches IDU to active or standby state until force state is disabled by selecting ‘Off’ (command line – prot force {active|standby|off}); 3. Standby time – allows specifying Standby time (in range 1 – 15sec) for Standby state.
4.4.1 User Configuration Figure 4.22 User configuration 1. guest – Enter new password (length: 4..30 characters) – allows entering preferable ‘guest’ account password and enabling the account. By default guest account is disabled. Maximal length of the password cannot exceed 30 symbols. Guest account has only monitoring privileges. The following Web GUI sections are available: Figure 4.23 Menu for “guest” user 2. admin – Enter new password (length: 4..
4.4.2 Name configuration Figure 4.24 Name configuration 1. System name (Max length: 16 characters) – allows entering preferable system name. Maximum length of the system name cannot exceed 16 symbols. Default name is ‘SAF’ (command line – system name ); 2. Location name (Max length: 16 characters) – allows entering preferable system location name. Maximum length of the location name cannot exceed 16 symbols. By default system location is not specified (command line – system location ); 3.
Figure 4.26 NTP configuration 1. NTP Status – shows if NTP is enabled or disabled (command line – system ntp status); 2. NTP enable – allows enabling or disabling NTP. By default this feature is disabled (command line – system ntp [enable|disable]); 3. NTP server IP address – allows to specify NTP server IP address (command line – system ntp server ); 4. NTP time zone (-12..
2. Open advanced ethernet information page / Download ethernet statistics – allows to open/save advanced Ethernet statistics. Link on the top of the page allow you to save advanced Ethernet statistics page in separate txt file on your hard disk drive; 3. System returned - in case of error or incorrectly entered parameter value, or other problems in the whole page – the info message will be displayed here. Otherwise it says “Ok”.
4.5.1 Ethernet management port IP configuration Figure 4.29 Ethernet management port IP configuration 1. IP Address – allows specifying IP address of CFIP PhoeniX you are currently logged in. Default IP address is 192.168.205.10. (command line – net ip addr ); (!) Note that CFIP PhoeniX IP addresses have to have the same subnet. 2. IP Mask – allows specifying IP mask of CFIP PhoeniX you are currently logged in. Default IP mask is 255.255.255.
Figure 4.31 Static route configuration 1. Static routes – shows the list of existing static routes, as well as allows you to choose specific route you are willing to change or delete. By default there is one route which depends on earlier entered IP settings (command line – net route); 2. Network address – allows specifying network address for the route changing/adding (command line – net route add|delete [MASK ] ); 3.
For the purpose of illustration, we use B class IP network address 10.0.10.11 for the remote side CFIP and 10.0.10.10 for the local side CFIP, while the IP address of our management PC LAN adapter will is 10.0.0.1. The steps of the configuration procedure are as follows: 1) Enter the remote side (far-end) Web GUI first (in the following case it is 192.168.205.10) and go to “IP configuration”. The configuration in this particular example will look in the following way: Figure 4.
Figure 4.34 Internet Protocol (TCP/IP) Properties 4) Go to the remote side Web GUI, choose “Tools Configuration file” and press “Cfg write”. 5) Repeat step 4) for the local side Web GUI. 4.6 Ethernet Configuration The Ethernet configuration window provides the speed settings for all four LAN ports of Ethernet switch as well as shows the current status of all four LAN ports (command line – ethernet stat). Explanation of customization fields: Figure 4.35 Ethernet status and configuration 1.
3. Link – shows whether link with appropriate port is established. If link is off, according field will be shown in red; 4. Duplex (actual) – shows if port is currently operating in full or half duplex mode; 5. Rx flow – shows if ‘flow control’ is enabled or disabled for ingress traffic; 6. Tx flow – shows if ‘flow control’ is enabled or disabled for egress traffic; 7. Rx state – shows if ingress activity is allowed; 8. Tx state – shows if egress activity is allowed; 9.
4.6.2 Protocol transparency Figure 4.37 Protocol Transparency 1. Represents four LAN (Local Area Network) ports of the CFIP PhoeniX switch, as well as WAN (Wide Area Port) connected to modem Ethernet interface; 2. STP – allows enabling/disabling Spanning Tree Protocol (STP) transparency by passing through/filtering BPDU (Bridge Protocol Data Unit) frames on specified ports (command line – ethernet transparency STP {enable | disable} { | All}); 3.
4.7 Aggregation configuration Link aggregation in n+0 mode allows utilizing up to 1000 Mbps Ethernet Layer 2 throughput by using independent frequency pair for each link. Traffic is being balanced (n+0) by internal switches of Master link. In case of link aggregation n+0 traffic distribution between n links is based upon the source and destination MAC addresses of Ethernet packets.
Figure 4.40 Ethernet aggregation configuration for Master 1. 2. 3. 4. 5. 6. 7. 8. Role – choose “Master”; Mode – choose “Aggregation” for link aggregation 2+0; Revertive mode – in case of “enabled” setting link will automatically reconfigure back to 2+0 operation when unit/cable/link failure is resolved. In case of “disabled” setting link will continue to operate in 1+0 mode; In order to activate 2+0 manually, it is necessary to press “Change state: Active” button on any of two Slave units.
Figure 4.41 Ethernet aggregation configuration for Slave 1. 2. 3. 4. 5. 6. 7. 8. Role – choose “Slave”; Mode – choose “Aggregation” for link aggregation 2+0 or “Protection” for link protection 1+1; Revertive mode – in case of “enabled” setting link will automatically reconfigure back to 2+0 operation when unit/cable/link failure is resolved.
Additionally starting from 1.63.xx firmware all ports (except WAN) by default are configured as Access VLAN ID 1. (!) When upgrading from any firmware prior to 1.63.xx you had VLAN configuration applied, management access will be available with previously specified management VLAN ID (as Default VLAN ID will remain the same), but it will be required to delete VLAN ID 1 from VLAN configuration table in order to make any further changes to VLAN configuration table. Figure 4.42 VLAN configuration 1. 802.
9. You can add VLANs by entering preferable VID, enabling appropriate port, choosing VLAN type and pressing “Add” button (command line – ethernet vlan {Delete} | {Port ); 10. Reset VLAN(-s) – resets the whole VLAN configuration (command line – ethernet vlan reset); 11. Writes to configuration file all the changes made on the whole page (command line – cfg write); 12.
When VLANs are not used (Figure 4.44), user data and management data are not separated either logically, or physically. Port 3 Mng Mng Port 1 LAN 1,2 Ext. switch 1 Port 3 Port 3 Ext. switch 2 CPU 1 Ext. switch 4 CPU 2 Port 2 User data Port 2 MM data Port 1 MM data User data Port 2 Ext. switch 3 Port 3 Port 1 MM data Int. switch 2 User data Int. switch 1 WAN Port 2 WAN CFIP2 LAN 1,2 Port 1 CFIP1 MM data User data When using VLANs (Figure 4.
Int. switch 1 Int. switch 2 LAN2 LAN1 Mng VLAN A&B VLAN B VLAN A User data LAN2 WAN User data CFIP2 WAN VLAN A CFIP1 LAN1 Mng VLAN A&B VLAN B Port 3 Port 3 Ext. switch 1 Ext. switch 2 CPU 2 Port 2 VLAN B VLAN A VLAN A VLAN B Port 2 MM data Port 1 User data MM data User data Port 1 CPU 1 Figure 4.
Figure 4.48 VLAN configuration of CFIP PhoeniX link 4.9 QoS 4.9.1 General Configuration QoS status provides control over main QoS parameters, accordingly allowing enabling or disabling QoS 802.1p, DiffServ or port based priorities and change priority queuing mode. Figure 4.49 QoS general configuration 1. QoS 802.1p – enables or disables 802.1p priorities for any available switch port – LAN1/2/3/4, WAN or Mng (command line – ethernet QoS 802.
2. DiffServ – enables or disables DiffServ (DSCP) priorities for any available switch port – LAN1/2/3/4, WAN or Mng (command line – ethernet QoS DSCP [enable | disable ] | map); 3. Port based priority – implies ingress packets on specified ports directly to priority queue set. By default port based priority queuing passes packets from all ports to lowest (1) priority queue (command line – ethernet QoS port ); 4.
If any queues are empty, the highest non-empty queue gets one more weighting. For example, if q2 is empty, q3:q2:q1:q0 becomes (8+1):0:2:1. full. In case of fixed queuing mode, highest priority buffer (q3) will pass packets as long as its buffer is By default weighted priority queuing mode is enabled. 4.9.2 QoS 802.1p Configuration QoS 802.1p provides configuration of QoS 802.1p priority mapping. You are able to map 8 different traffic 802.1p values (0 – 7) into 4 priority queues (1 – 4). Figure 4.
Figure 4.53 DSCP mapping 1. DSCP mapping – allows assigning queues for different DSCP classes. You may have up to 64 different traffic DSCP classes; 2. By pressing „Execute configuration” changes made to the corresponding section apply only for the local side CFIP PhoeniX. If „Rollback on” is selected, configuration will be reverted in case erroneous configuration changes are applied. 3. Writes to configuration file all the changes made on the whole page (command line – cfg write); 4.
4.10 Spanning Tree Configuration 4.10.1 Spanning Tree Configuration Figure 4.54 Spanning Tree Protocol – Bridge configuration Bridge configuration - Values 2-4 take effect only if a given Bridge is Root: 1. Bridge ID – value from (0..61440); this parameter and MAC address determine whether a given Bridge is Root Bridge. Advantage is given to the combination of Priority and Address, which is numerically smaller; 2. Hello Time (1..100) – time gap, between which the BPDU packets are being sent; 3.
14. Bridge ID – displays the Bridge ID of current Root bridge; 15. Root Port – currently elected root port is being shown; 16. Root Path Cost – displays the path cost from current bridge to root bridge; 17. Port 1 LAN – STP parameters of LAN port; 18. Port 2 WAN – STP parameters of WAN port: - Priority (0..240) – Port Priority. Combination of Priority, Port number and Path Cost determines whether the port will be selected as Root port or will be blocked on the occasion of loop, etc; - Path cost (1..
4. By pressing „Execute configuration” changes made to the corresponding section apply only for the local side; 5. VLAN (1 – 4094) – map VLAN ID or VLAN IDs range for each instance. Up to seven instances; 6. Write to config file - saves to configuration file all the changes made on the whole page (command line – cfg write); 7. System returned - in case of error or incorrectly entered parameter value, or other problems on the whole page – the info message is being shown here. Otherwise it says “Ok”.
4.11 SNMP v1/v2 configuration The SNMP v1/v2 configuration pages provide configuration of SNMP communities, host and trap addresses. SAF NMS system will work only when SNMP is properly configured. Explanation of customization fields: 4.11.1 SNMP community configuration Figure 4.57 SNMP community configuration 1.
Figure 4.58 SNMP allowed hosts configuration 1. SNMP host list – shows the list of available v1/v2 SNMP hosts; adds or deletes the host IP address to the CFIP SNMP v1/v2 host table. If the SNMP host connected to the CFIP is not added to the CFIP SNMP v1/v2 host table, the CFIP will not respond to the SNMP requests from that host. If „Rollback on” is selected, configuration will be reverted in case of erroneous configuration changes applied. 2.
5 Performance and Alarm Management 5.1 Alarm Management 5.1.1 Alarms and Events Structure All alarms and events are placed in indexed table. Low level raw alarms and events are placed in the first table. Raw alarms and events are merged in groups, which are placed in the second indexed group table. Raw alarm table and group table are related one to many, or one to one if each alarm has a separate group (see Figure 5.1). Group is in SET state if one or more group members are in SET state.
12 12 IDU temperature fault Temperature is out of defined range 13 13 No data from main PSU IDU ADC No data from IDU ADC connected via I2C interface 14 14 Main supply 48V failure Main supply voltage is out of defined range 15 15 IDU PSU state One of the possible PSU state "OFF","IDLE","Ok","OVERLOAD","SHORT"," FAULT" state was changed for IDU 16 16 No data from main PSU ODU ADC No data from ODU ADC connected via I2C interface 17 17 IDU PSU to ODU state One of the possible PSU state "O
No data from MODEM No data from MODEM connected via UART interface 36 Acquire status alarm Modem acquire failure status 46 37 Last acquire error status Modem last acquire failure status 47 38 Radial MSE Radial MSE is out of defined range 48 39 LDPC decoder stress LDPC decoder stress is out of defined range 49 40 Tx ACM profile was changed ACM profile was changed 50 41 RX carrier offset Error in Rx carrier offset 51 42 No data from modem temperature sensor No data from modem tempe
grouped. Complete list of alarm individual IDs and group IDs can be seen in the table above or using the command ‘alarm list’ in the command prompt. To configure representation of alarms, refer to Chapter 5.2.5. Figure 5.2 Alarm status window 5.1.4 Alarm Log To view alarms history, go to ‘Performance Alarm log’. Alarm log shows 21 latest alarm entries per page and about 2000 latest alarm entries in total.
Figure 5.4 Alarm configuration window Alarm threshold configuration screen allows you to define specific threshold levels to bound alarms to desirable values, so that you are able to adapt alarm system to your individual needs. Alarms in bold font represent group alarms and alarms in normal font – individual alarms. 85 CFIP PhoeniX Series TDM/IP Split Mount System Technical Description and Configuration Guide • Rev. 1.
Figure 5.5 Alarm threshold configuration window 5.1.6 Alarm Management Commands To manage alarms in command prompt, the commands are as follows: Alarm management commands Command Description Log show [] The management controller maintains event log, - events include configuration changes, management controller restarts, and local site alarm changes.
Alarm management commands Command Description Log filter [] Filters event list by specific alarm ID. ; works similarly to ‘log show’ command. Log file Makes event log file with specified filename. Alarm stat Lists alarm groups currently set. Alarm list Displays the list of all alarms, their group IDs and alarm IDs. Alarm groups Displays the list of all alarms and their group IDs.
Figure 5.6 Functional architecture for data collection, history and thresholding treatment 5.2.2 Performance Values Threshold Seconds (TS) The TS is defined as one second period during which the detected value is outside of predefined thresholds. The current value of the counter associated with TS should be readable by the managing system on request. In case a threshold associated to TS counter is changed, the current value of the counter should be reset to zero.
Figure 5.7 Selecting performance log parameters Figure 5.8 Performance log window Time interval can be chosen between 1 min, 15 min or 1 hr. You can also define the start time and the start date. When start values are defined, it is also possible to define the end time and the end date. TS (threshold seconds) show the amount of seconds in a chosen period (1min, 15min or 1h) when the parameter has been out of bounds set by performance thresholds in ‘Configuration Performance log configuration’.
Figure 5.9 Performance log configuration window The main advantage in terms of demonstration means is obtained from ‘Performance graphs’, which are found in ‘Performance Performance graph’ section. You are able to choose between 9 parameters – Rx level; Tx level; Radial MSE; LDPC stress; Modem temperature; IDU temperature; ODU temperature; PSU input voltage and PSU power consumption – and to view their graphs.
1. Time scale selector. User can select the scale and accuracy (1 / 15 / 60 minutes). The lower accuracy, the longer the period available for data (mechanism of the performance management system) 2. Updates the performance graph; the latest data is shown 3. Shows / hides period settings (point 5) 4. Performance data selector. Only two performance parameters can be selected at a time 5. Period settings. Allows the user to specify time period for the graph 6. Date and time fields.
Figure 5.12 Equalizer graph – normal operation During normal operation frequency response curve is smooth and the only equalizer tap towers are in the centre of equalizer taps graph, otherwise frequency response curve will appear jagged and many equalizer taps will become visible. The latter case most probably will indicate to multipath issue, which must be inspected with use of precise and accurate path profiling. An example of multipath caused equalization is shown on the picture below.
Additional performance management commands in Telnet/serial interface Command Description pm log {|{|||}} Lists performance management log with selected of 1min, 15min or 1hr. Allows choosing the number of last records to be shown () or to define start and end time and date. Note that end time and date values must be entered after entering start time or date respectively. pm select {Up_TIME . Rx_LEVEL .
2. Modem state – shows if the modem is operating correctly; 3. Clear statistics – resets all statistics counters (not available for “guest” account); 4. Truncated frames – number of truncated received frames; 5. Long events – frames having byte count greater than MAXIMUM FRAME SIZE parameter (1518, 1536 or 1916 bytes); 6. Vlan tags detected – VLAN tagged frames; 7. Unsup. opcodes – frames recognized as control frames but contained an Unknown Opcode; 8.
35. Excessive defers – packets deferred in excess of 6,071 nibble times in 100 Mbps mode, or 24,287 bit-times in 10 Mbps mode; 36. Non-exc. defers – packets deferred for at least one attempt, but less than an excessive defer; 37. Broadcasts – packets, which destination address contained broadcast address; 38. Multicasts – packets, which destination address contained multicast address; 39. Dones – transmission of packets successfully completed; 40.
Figure 5.15 Ethernet switch statistics 1. Shows the time during which statistics have been gathered; 2. Clear statistics – resets all statistics counters (not available for “guest” account); 3. TxOctets - The total number of good bytes of data transmitted by a port (excluding preamble but including FCS); 4. TxDropPkts - This counter is incremented every time a transmit packet is dropped due to lack of resources (e.g.
8. TxUnicastPkts - The number of good packets transmitted by a port that are addressed to a unicast address; 9. TxCollisions - The number of collisions experienced by a port during packet transmissions; 10. TxSingleCollision - The number of packets successfully transmitted by a port that have experienced exactly one collision; 11. TxMultiCollision - The number of packets successfully transmitted by a port that have experienced more than one collision; 12.
32. RxFCSErrors – The number of packets received by a port that have a length (excluding framing bits, but including FCS) between 64 and 1522 bytes inclusive, and have a bad FCS with an integral number of bytes; 33. RxGoodOctets – The total number of bytes in all good packets received by a port (excluding framing bits, but including FCS); 34. RxDropPkts - The number of good packets received by a port that were dropped due to a lack of resources (e.g.
6 Miscellaneous Controls in Web Graphic User Interface These controls are located in the Navigation Panel under the “Tools” item. 6.1 Ethernet/Configuration files This section allows working with CFIP configuration script. The management module has RAM and EEPROM chips on-board. When CFIP is booted up, bootstrap is loaded from the EEPROM into RAM. The bootstrap contains the parameters that were previously stored in EEPROM using write and/or cfg write commands.
Figure 6.1 Configuration (cfg & Ethernet) files 100 CFIP PhoeniX Series TDM/IP Split Mount System Technical Description and Configuration Guide • Rev. 1.
1. Download cfg file – allows downloading system configuration file and saving it on your hard drive. 2. Upload configuration file - allows uploading system configuration file to CFIP PhoeniX flash memory. In order to load configuration file from system memory, cfg restore should be used (refer to number 9); 3. Saved configuration file - shows contents of system configuration file saved in EEPROM memory. Commands contained in this configuration file are executed at every system start-up; 4.
15. Saved configuration file - shows contents of system configuration file saved in EEPROM memory. Commands contained in this configuration file are executed at every system start-up; 16. Running configuration file - shows currently running system configuration file (command line – eth config). In order to save current configuration use command cfg write; 17. File system content – shows contents of internal flash memory (command line – tfs ls); 18.
Figure 6.2 License management 1. Show active license – if non-active license is selected, pressing this button will switch selection back to currently active license (command line – license status); 2. License status – shows if management CPU was able to read license data (command line – license status); 3.
13. 28000 KHz – shows the maximum modulation that can be used together with 28 MHz channel bandwidth (command line – license status); 14. 30000 KHz – shows the maximum modulation that can be used together with 30 MHz channel bandwidth (command line – license status); 15. 40000 KHz – shows the maximum modulation that can be used together with 40 MHz channel bandwidth (command line – license status); 16.
The following files are required for the CFIP to start: – ‘boot.ini’ file, - device boot configuration file. This file is a text file and contains the name of the firmware file which must be executed on start-up. The file name can be freely changed, but its default name is ‘boot.ini’; hereinafter, it is assumed that this file has default filename.
tfs edit Edits the specified file. This command is applied for editing configuration backup files and boot configuration file (boot.ini). For example, edit boot.ini,Be – file ‘boot.ini’ will be opened for editing. ‘Be’ specifies that this file will be saved with attributes ‘B’ and ‘e’. If boot.ini file is intended to be modified, it should always be opened specifying ‘B’ and ‘e’ flags as in the example above, this will ensure that file is saved with these attributes (flags).
7 Software Update To simplify the firmware update process, SAF Tehnika JSC provides special update package, as a new version is available. This update pack is available as archive (e.g. zip), which includes firmware file (with *.elf.ezip,Ec extension), upgrade instructions, release notes and MIB files for SNMP protocol. The latest CFIP series firmwares are available in the following URL: https://saftehnika.
Use command “ls” to list files on CFIP flash disk. Use command “delete ” to delete the file from the CFIP Flash disk. 6. Proceed with steps 5. and 6. in Chapter 7.1. You can also use any preferable FTP client if you wish. 7.2 Uploading File via Serial Port (Xmodem) File upload via serial port takes much longer time compared to use of TFTP and should be used only in case Ethernet connection with the CFIP management system is not available, or does not start normally. 1.
Figure 7.3 Xmodem file send for CFIP When upload is complete, the following information will be displayed (Figure 7.4): Figure 7.4 HyperTerminal 5. Enter ‘reset’ command to exit from MicroMonitor mode and restart the CFIP. 6. Proceed with steps 5. and 6. in Chapter 7.1. 109 CFIP PhoeniX Series TDM/IP Split Mount System Technical Description and Configuration Guide • Rev. 1.
8 CFIP Discovery Protocol Discovery Protocol is Layer 3 Network protocol. This feature allows gathering information from connected CFIP devices. The protocol discovers the IP address and software version of connected CFIP unit. Discovery protocol uses UDP packets sent on port 78. Discovery Protocol feature may be useful, when the IP address of connected device is unknown and there is no possibility to establish connection through serial management port in order to find out the IP address. 8.
Figure 8.1 (!) Note that IP addresses of Ethernet adapter and CFIP units may belong to different subnets. This command sends discovery messages on broadcast address 255.255.255.255 to all devices in network. All CFIP devices connected to this network are responding with its own IP address/CIDR notation and firmware version. CIDR notation (routing prefix) is related to network mask that is also necessary in order to manage CFIP unit.
Figure 8.2 (!) Note that IP address of Ethernet adapter should belong to the same subnet as CFIP units, i.e. the subnet of CFIP units should be known. The subnet mask of Ethernet adapter and CFIP units may differ. This command sends discovery messages on specified broadcast address to all devices in the specified subnet. All CFIP devices from specified subnet are responding with its own IP address/CIDR notation and firmware version 8.2.
9 RSSI Port RSSI (Received Signal Strength Indicator) port is used to adjust the alignment of antenna for best performance (for both rough and fine adjustment); this can be done using digital multimeter which is connected to the RSSI port. The output of the RSSI port is DC voltage and varies depending on received signal level. The following chart and table shows typical relationship of the received signal level (Rx level) displayed by CFIP vs.
10 Pinouts 10.1 Ethernet RJ-45 port The pinouts of RJ45 socket are as follows: 1, 3, 4, 7, 2 6 5 8 – – – – Bi-directional Bi-directional Bi-directional Bi-directional pair pair pair pair A B C D Figure 10.1 Ethernet RJ-45 port pinouts 10.2 E1 port RJ-45 pinouts The pinouts of CFIP PhoeniX IDU RJ-45 sockets for E1 channels are shown in Figure 10.2. E1 port pinouts RJ-45 pin numbering INPUT (Rx) OUTPUT (Tx) E1 port 1 2 3 4 5 6 7 8 OUT Not IN (Rx) GND (Tx) used GND 12345678 Figure 10.
Pin type Pin number Pin type Pin number Alarm input 1 1 Ground 12 Alarm input 2 2 Ground 13 Alarm input 3 3 Alarm output 4 NC 15 Alarm input 4 4 Alarm output 3 NC 16 Alarm output 4 NO 6 Alarm output 2 NC 17 Alarm output 3 NO 7 Alarm output 1 NC 18 Alarm output 2 NO 8 Alarm output 4 COM 23 Alarm output 1 NO 9 Alarm output 3 COM 24 Ground 10 Alarm output 2 COM 25 Ground 11 Alarm output 1 COM 26 Electrical specifications of auxiliary alarm inputs • Nominal open outpu
Pins 1 2 3 4 5 6 7 8 Direction In In Out Out Out Out In In Description RINRIN+ PROT_CLK_OUT+ DODO+ PROT_CLK_OUTPROT_CLK_INPROT_CLK_IN+ Figure 10.5 1+1 protection port pinouts 10.6 1+1 protection cable Connector 1 pin 1 2 3 4 5 6 7 8 Wire Pair 1A Pair 1B Pair 2A Pair 3A Pair 3B Pair 2B Pair 4A Pair 4B Connector 2 pin 4 5 7 1 2 8 3 6 Figure 10.6 1+1 protection cable pinouts 116 CFIP PhoeniX Series TDM/IP Split Mount System Technical Description and Configuration Guide • Rev. 1.
10.7 Power protection port Figure 10.7 Power protection port and cable (P/N S0ACPR11) pinouts 117 CFIP PhoeniX Series TDM/IP Split Mount System Technical Description and Configuration Guide • Rev. 1.
11 Available Accessories Surge protection Surge Protection with gas tube P/N: CLALA001 P/N: CLALA003 AC/DC Power supply, 48VDC, 80W Flexible Waveguide UBR-PBR EU - P/N I0AB4810, US - P/N I0AB4811, AUS - P/N I0AB4818 (See the list of available test equipment below) CFIP PhoeniX 1+1 protection bus cable CAT6 0,3m P/N S0ACPP11 Power protection cable 160mm; compatible with IDU P/N S0GIP*11 IDU 1+1 grounding cable, 180 mm Ethertnet Cat5e STP patch cable P/N S0ACGD02 P/N I0ACPP02 P/N S0ACPR11 118
Coaxial attenuator 40 dB SAF adapted OMT for Arkivator antenna for dual-polarization P/N CLA40A01 (See the list of available test equipment below) RSSI cable for ODU align 1m BNC − 2 plug-in CFIP ODU Mounting Bracket P/N CLGCRS01 (for 1xODU P/N: CLGRFB05; for 2xODU P/N: CLGRFB06) Test equipment FODU RJ-45 connector 8P shield solid (See the list of available test equipment below) P/N FOACNR02 11.
7/8GHz test suite, contains two waveguide-to-coaxial adapters, two attenuators, 40 dB, coaxial cable, 40 cm long C08TST02 Test equipment 7/8 GHz C11TST02 Test equipment 10/11 GHz C15TST02 Test equipment 13/15 GHz 13/15GHz test suite, contains two waveguide-to-coaxial adapters, two attenuators, 40 dB, coaxial cable, 40 cm long C22TST02 Test equipment 18/23GHz 18/23GHz test suite, contains two waveguide-to-coaxial adapters, two attenuators, 40 dB, coaxial cable, 40 cm long C26TST02 Test equipment
12 List of Abbreviations 3G – third generation AC – Alternating Current ACI – Adjacent-Channel Interference ACM – Adaptive Coding and Modulation AGC – Automatic Gain Control ASCII - American Standard Code for Information Interchange ATPC – Automatic Transmit Power Control BER – Bit-Error Ratio BNC connector - Bayonet Neill-Concelman coaxial connector CCI – Co-Channel Interference CLI – Command-Line Interface CPU – Central Processing Unit CRC – Cyclic Redundancy Check DC – Direct Current DiffServ – Different
RAM – Random Access Memory RSL – Received Signal Level RSSI – Received Signal Strength Indicator Rx – Receive SNMP - Simple Network Management Protocol SNR – Signal-to-Noise Ratio STM-1 – Synchronous Transport Module - 1 TCP/IP – Internet Protocol Suite (Transmission Control Protocol / Internet Protocol) TDM – Time-Division Multiplexing TFTP – Trivial File Transfer Protocol TM – Tide Mark TP – Twisted Pair TS – Threshold Seconds Tx – Transmission UART – Universal Asynchronous Receiver/Transmitter USB – Univ
13 SAF Tehnika JSC Contacts SAF Tehnika A/S technical support can be reached by: - Email: techsupport@saftehnika.com - Telephone: +371 67046840 - Fax: +371 67046809 123 CFIP PhoeniX Series TDM/IP Split Mount System Technical Description and Configuration Guide • Rev. 1.
