Page 1 Microwave Radio System Alcatel-Lucent 9500 MXC Microwave Cross Connect User Manual 3DB 23063 ADAA - Rev 004 - July 2007...
Page 2 Any warranty must be referred exclusively to the terms of the contact of sale of the equipment this handbook refers to. Alcatel-Lucent makes no warranty of any kind with regards to this manual, and specifically disclaims the implied warranties of merchantability and fitness for a particular purpose. Alcatel-Lucent will not be liable for errors contained herein or for damages, whether direct, indirect, consequential, incidental, or special, in connection with the furnishing, performance, or use of this material.
Page 3: Contact Information
Alcatel-Lucent Customer Service WTD (Wireless Transmission Division) Center Center CTAC Engineers Rue Albert Schweitzer, 1 Plano Texas Illkirch (For 9500 MXC issues you may contact the WTD directly) France Tel. +33 3 90679722 Tel: 888-252-2832 or 613-784-6100 Fax: 972-477-7240 Fax: 613-784-8905 alcare.europe@alcatel.com wstc.repair@alcatel.com...
Page 4 If any other type of cable is used, it may violate compliance. 9500 MXC is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures. This equipment is intended to be used exclusively in telecommunications centers.
Page 7: Table Of Contents
Contents About This Manual Welcome to 9500 MXC ................xxv Purpose....................... xxv Intended Audience ..................xxv What You Need To Know ................. xxvi Organization....................xxvi Conventions and Terminology..............xxvii Volume I: Health and Safety Requirements Chapter 1. Health and Safety General Health and Safety ................
Page 8 Chapter 2. 9500 MXC Terminals PDH and SDH IDUs ................... 2-1 Capacity and Bandwidth Options ............2-2 Traffic and Auxiliary Interfaces ............2-3 PDH Trib Ports ................2-4 SDH Trib Ports ................2-4 Auto Insertion of AIS or PRBS on Tribs........2-4 Aux Data Port ................
Page 9 9500 MXC User Manual IDU Service Restoration Times..........2-33 Platform Layout and Interoperation Data ..........2-34 Configuration and Diagnostics ..............2-35 9500 MXC CT Log-in ............... 2-35 Configuration..................2-36 Diagnostics ..................2-36 Software Reset ................... 2-37 Chapter 3. 9500 MXC Nodes Platforms .....................
Page 10 XPIC ....................3-102 RAC 40 Operating Guidelines............3-104 Backplane Bus Capacity............3-104 Settings, Protection and ATPC ..........3-105 Example Configurations ............3-106 Configuration and Diagnostics ............... 3-118 9500 MXC CT Log-in ..............3-118 Configuration ................... 3-119 Diagnostics ..................3-119 Alcatel-Lucent...
Page 11 ODU Data ....................4-2 Chapter 5. Configuration and Diagnostics 9500 MXC CT .................... 5-1 9500 MXC CT Feature Summary............5-2 Chapter 6. 9500 MXC Performance and Diagnostic Features 9500 MXC Node..................6-1 Platform ....................6-2 INUs ..................... 6-2 ODUs.................... 6-2 Multiplexer Modes................
Page 12 Front Panel LEDs ................6-13 Volume III: 9500 MXC Installation Chapter 1. Introduction Product Compliance..................1-1 9500 MXC Health and Safety Requirements..........1-1 Installation Overview.................. 1-2 Before Going On Site.................. 1-3 Tools and Material ................1-3 Unpacking the Equipment ..............1-4 Chapter 2.
Page 13 9500 MXC User Manual Remote-Mount Installation Procedure ........2-12 Grounding the ODU ................2-13 ODU Grounding Procedure............2-14 Installing a Coupler................... 2-14 Coupler Overview................2-14 Coupler Installation Procedure ............2-15 Unused and Disconnected Coupler Ports .......... 2-18 Installing ODU Cables and Connectors............ 2-19 ODU Cable ..................
Page 14 Chapter 2. Setting Up 9500 MXC CT Installing 9500 MXC CT on Your PC............2-1 Procedure for Installing 9500 MXC CT ..........2-2 9500 MXC CT to 9500 MXC Connection Options ........2-3 Setting Up A TCP/IP Ethernet 9500 MXC CT Connection ....2-5 Alcatel-Lucent...
Page 15 9500 MXC User Manual Setting Up Your PC TCP/IP Properties ........2-6 Setting Up A DHCP Ethernet 9500 MXC CT Connection ....2-9 Setting Up Your TCP/IP Properties for DHCP ......2-10 Setting Up 9500 MXC CT Connection Using V.24 ......2-11 Setting Up a V.24 Connection via a DB-9 Serial COM Port..
Page 16 Link Aggregation................ 7-76 Link Status Propagation Operational Characteristics ....7-81 AUX Configuration .................. 7-84 Auxiliary Data and NMS Functions ..........7-84 Data Option Overview..............7-85 NMS Option Overview............... 7-86 AUX Transport on Link Overhead and Operating Rules ... 7-87 Alcatel-Lucent...
Page 17 Procedure for Configuring Auxiliary Circuits........9-16 Chapter 10. Networking Configuration Static or Dynamic Routing................ 10-1 9500 MXC Address and Routing Options......... 10-2 Rules for Single and Interface Addressing Modes ..... 10-3 Networking Screens .................. 10-4 3DB 23063 ADAA - Rev 004 July 2007...
Page 18 DHCP Server Function ................10-13 Rules, Hints and Tips for a DHCP Server ........10-13 Configuring The DHCP Server ............10-15 Chapter 11. 9500 MXC Node and Terminal Alarm Actions Alarm Actions Screen ................11-1 Before You Begin ................11-2 Procedure for Alarm Actions Configuration ........
Page 19 Protected DAC Screens ............15-60 DAC ES and DAC GE Menu ............15-62 AUX Menu ..................15-65 Loopback Points ................15-65 Circuit Loopbacks for 9500 MXC Node ..........15-67 Parts ......................15-69 Advanced Management ................15-71 Software Reset ................. 15-72 Clear Events and History ..............
Page 20 Ring Protection ................1-14 DAC Protection ................1-15 NCC/NPC ................... 1-17 Commissioning Records ................1-18 Chapter 2. 9500 MXC Troubleshooting Introduction....................2-1 Troubleshooting Process ................2-2 Remote Diagnostics Using Remote Management ....... 2-2 Before Going to Site Checklist ............2-3 Troubleshooting Basics ...............
Page 21 9500 MXC User Manual CT Alarms....................2-16 9500 MXC Node Alarms..............2-16 NCC Alarm Hierarchy..............2-17 RAC Alarm Hierarchy..............2-18 DAC Alarm Hierarchy ............... 2-20 AUX Alarm Hierarchy ............... 2-21 NPC Alarm Hierarchy ..............2-22 DAC ES Alarm Hierarchy............2-23 DAC GE Alarm Hierarchy ............
Page 22 Radio Links ................A-23 Fiber (DAC 155oM) Links ............A-24 Wrap and Unwrap Times ............A-24 Checking Wrap and Unwrap Operation ........A-25 Appendix B. 9500 MXC Alarms NCC/IDU Alarms ..................B-2 AUX Alarms .................... B-40 Informational Events................B-58 Appendix C. INU/INUe and IDU Connector and Cable Data DAC and IDU Tributary Connectors and Cables ........
Page 23 IDU AUX Cable: Sync, IDU AUX DB9 to IDU AUX DB9, 1 mC-33 IDU AUX Alarm I/O Cable: HD15 to Wirewrap, 5 m ..... C-33 Appendix D. 9500 MXC NMS Networking Essentials General Considerations................D-1 Rules, Hints and Tips ................. D-2 Recommended Address Ranges..............
Page 24 RAC 30 ....................F-4 RAC 40 ....................F-5 ODU Cable, Interfaces and Traffic............F-7 Rx and Tx Diversity Bus ..............F-8 DAC .....................F-8 ODU 300 .....................F-9 Protected and Diversity Operation............F-10 Hot Standby ..................F-12 Space Diversity ..................F-13 Frequency Diversity................F-13 Ring Protection ..................F-15 Glossary Index xxiv Alcatel-Lucent...
Page 25: About This Manual
The 9500 MXC Terminal is optimized for single-link installations or where back-to-back network connection of terminals is preferred. Terminals may also be used to spur from a 9500 MXC Node. Different versions are available for PDH, SDH or Ethernet, on frequency bands 5 to 38 GHz.
Page 26: What You Need To Know
What You Need To Know To install and commission a 9500 MXC, we recommend you have the following knowledge and skills: • A basic understanding of the principles of microwave transmission. • Installation and maintenance experience on PDH and SDH digital microwave radio systems.
Page 27: Conventions And Terminology
9500 MXC User Manual Conventions and Terminology Graphical Cues The following icons function as graphical cues used to characterize particular types of associated supporting information: A warning icon denotes danger to life and/or limb. A caution icon denotes important information pertaining to damage to equipment, loss of data, or corruption of files.
Page 29 Volume I 9500 MXC Health and Safety Requirements...
Page 31: Chapter 1. Health And Safety
All personnel must comply with the relevant health and safety practices when working on or around the 9500 MXC radio equipment. The 9500 MXC has been designed to meet relevant US and European health and safety standards as outlined in IEC Publication 60950.
Page 32: General Health And Safety
Hazardous Materials No hazardous materials are used in the construction of the equipment. Hazardous Voltage The 9500 MXC system meets global product safety requirements for safety extra-low must voltage (SELV) rated equipment where the input voltage be 48 V nominal, 60 V maximum.
Page 33: Operator Health And Safety
Protection from RF The 9500 MXC radio does not generate RF fields intense enough to cause RF burns. Exposure: 9500 MXC However, when installing, servicing or inspecting an antenna always comply with the Protection from RF Exposure guidelines under General Hazards.
Page 34: General Hazards
9500 MXC Indoor Unit Earthing The 9500 MXC indoor unit earth must be connected directly to the dc supply system earthing conductor, or to a bonding jumper from an earthing terminal bar, or bus to which the dc supply system earthing is connected.
Page 35 Mains Power Supply Routing 9500 MXC dc power, IF, tributary, auxiliary and NMS cables are not to be routed with any AC mains power lines. They are also to be kept away from any power lines which cross them.
Page 36 Mechanical Loading When installing an indoor unit in a rack, ensure the rack is securely anchored. Ensure that the additional loading of a 9500 MXC indoor unit or units will not cause any reduction in the mechanical stability of the rack.
Page 37 9500 MXC User Manual RF Exposure Guidelines The following MPE (maximum permissible exposure) calculations have been produced in accordance with the guidelines of EN 50383/EN 50385. These calculations represent examples only and do not include every possible combination of output power and antenna gain.
Page 38 0.12 0.05 38GHz (37.0 – 39.46GHz) Transmit Power (dBm) Antenna Gain (dBi) Compliance Boundary Compliance Boundary General Public (m) Occupational (m) 17.5 48.1 5.41 2.41 17.5 39.3 1.96 0.87 -5.0 48.1 0.41 0.18 -5.0 39.3 0.15 0.07 Vol. I-1-8 Alcatel-Lucent...
Page 39 Volume II 9500 MXC System Description...
Page 41: Chapter 1. 9500 Mxc System Overview
Chapter 1. 9500 MXC System Overview This chapter introduces the features and capabilities of the 9500 MXC. Refer to: • 9500 MXC Platforms on page 1-2 • Craft Terminal Configuration and Diagnostics on page 1-14 • Antennas on page 1-14 •...
Page 42: 9500 Mxc Platforms
Chapter 1. 9500 MXC System Overview 9500 MXC Platforms 9500 MXC is available on two platform types, Terminal and Node. Both employ a split-mount architecture with a rack-mounted indoor unit and direct-mounted ODUs connected by a single coaxial cable. Refer to: •...
Page 43: Terminal Indoor Units
9500 MXC User Manual Terminal Indoor Units IDUs are available in variants to transport PDH, SDH or Ethernet on ETSI and ANSI bands. See Table 1-2. IDU Variants Table 1-2. Application Variant Capacities Modulation IDU 20x 5xE1 to 75xE1, or 4xDS1 to...
Page 44 Chapter 1. 9500 MXC System Overview IDU 20x Figure 1-2. IDU 20x is capacity licensed. The base configuration supports 20xE1/28xDS1, with higher capacities to 40xE1 or 32xDS1 obtained by requesting additional capacity upgrades at time of order or as field-downloadable software licenses.
Page 45: 9500 Mxc Node
Radio paths and customer interfaces are customized by plug-in cards, with interconnection of traffic and services supported by a backplane bus. Figure 1-5 shows a 9500 MXC Node comprising an INU (Indoor Node Unit) with three ODUs. 9500 MXC Node: INU with Three ODUs Figure 1-5.
Page 46: Node Indoor Units
Chapter 1. 9500 MXC System Overview Other traffic options include: • E3 and DS3 rates with maximums to 8xE3 or 6xDS3 respectively. • 1xSTM1/OC3 or 2xSTM1/OC3. • Ethernet and Fast Ethernet, with or without companion TDM traffic. • Gigabit Ethernet to 300 Mbps on one node, and 600 Mbps on co-located Nodes.
Page 47 9500 MXC User Manual Figure 1-6. INUe The INUe requires one NCC and two FANs, and has provision for up to ten option cards. It supports a maximum of six ODUs for six non-protected links, or up to three protected/diversity links.
Page 48: Node Plug-In Cards
Chapter 1. 9500 MXC System Overview Node Plug-in Cards This section highlights the plug-in cards for an INU/INUe. For more information on plug-ins, refer to Chapter 3. The NCC is a mandatory plug-in for an INU/INUe. It performs key node management and control functions, and provides various dc rails from the -48 Vdc input.
Page 49 9500 MXC User Manual RAC 30V3 Figure 1-10. RAC 3X RAC 3X interfaces to an ODU 300 for channel bandwidths of 40 to 56 MHz for capacity options of: • 64/75/93/100xE1 • 32/70/84/100xDS1 • 4xDS3 • 1/2xSTM1/OC3 RAC 3X Figure 1-11.
Page 50 Chapter 1. 9500 MXC System Overview DAC 16X DAC 16x supports 16xE1 or DS1 tributaries on Mini RJ-21 connectors. DAC 16x Figure 1-14. DAC 3xE3/DS3M DAC 3xE3/DS3M supports three operational modes: • E3/DS3 tributary mode. Up to three E3 or DS3 tributaries on paired BNC connectors.
Page 51 9500 MXC User Manual DAC 2x155o DAC 2x155o supports two STM1/OC3 single-mode optical tributaries on SC connectors. DAC 2x155o Figure 1-18. DAC 155oM DAC 155oM multiplexes an SDH/OC3 single-mode optical tributary to an NxE1 or NxDS1 backplane. DAC 155oM Figure 1-19.
Page 52 Data options are sync at 64 kbps or async up to 19.2 kbps. Figure 1-22. NPC provides redundancy for the NCC TDM bus management and power supply functions. Figure 1-23. For more information on the 9500 MXC Node, refer to Chapter 3. Vol. II-1-12 Alcatel-Lucent...
Page 53: 9500 Mxc Odus
• Up to 300 Mbps Ethernet • QPSK to 256QAM modulation • RAC 30, RAC 40, RAC 3X, IDUs For more information on 9500 MXC ODUs, refer to Chapter 4. 3DB 23063 ADAA - Rev 004 July 2007 Vol. II-1-13...
Page 54: Craft Terminal Configuration And Diagnostics
Configuration and diagnostics are achieved using the 9500 MXC CT, the PC based craft terminal. 9500 MXC CT (CT) is supported in the 9500 MXC system software, such that once installed on a PC, it automatically downloads support from the radio as needed to ensure CT always matches the version of system software supplied, or subsequently downloaded in any radio upgrade.
Page 55: Power Supply
9500 MXC User Manual Power Supply 9500 MXC is designed to operate from a -48 Vdc power supply (+ve earth) but will operate to specification over a voltage range of -40.5 to -60 Vdc. The dc power supply must be UL or IEC compliant for a -48 Vdc SELV (Safety Extra Low Voltage) output (60 Vdc maximum limited).
Page 56 Chapter 1. 9500 MXC System Overview Vol. II-1-16 Alcatel-Lucent...
Page 57: Pdh And Sdh Idus
Chapter 2. 9500 MXC Terminals This chapter describes features and capabilities of 9500 MXC Terminals. Refer • PDH and SDH IDUs on page 2-1 • Ethernet IDU on page 2-10 • IDU Protection on page 2-28 • Platform Layout and Interoperation Data on page 2-34 •...
Page 58: Capacity And Bandwidth Options
Chapter 2. 9500 MXC Terminals Capacity and Bandwidth Options Depending on the IDU and its capacity/bandwidth options, modulation rates are programmed for QPSK, 16QAM, 32QAM, 64QAM, or 128QAM: • Table 2-1 lists the ETSI capacity, modulation, and bandwidth options for IDU 20x.
Page 59: Traffic And Auxiliary Interfaces
9500 MXC User Manual IDU 20x ANSI System Options Table 2-2. Capacity Channel Modulation Bandwidth 4xDS1 2.5 MHz 16 QAM 8xDS1 10 MHz QPSK 8xDS1 5 MHz 16 QAM 8xDS1 3.75 MHz 32 QAM 16xDS1 20 MHz QPSK 16xDS1 10 MHz...
Page 60: Pdh Trib Ports
Chapter 2. 9500 MXC Terminals PDH Trib Ports IDU 20x trib ports are on individual RJ-45 connectors. • E1 trib options are 75 ohm unbalanced or 120 ohms balanced. • DS1 trib encoding options are AMI or B8ZS. Line impedance is fixed at 100 ohms balanced and line length is selectable.
Page 61: Aux Data Port
• Multiple input or internal events may be mapped to a common output. Mapping is achieved using IP addressing for the destination Terminal, or if the destination is a 9500 MXC Node, to its IP address plus the slot location and output number for the AUX plug-in.
Page 62 Chapter 2. 9500 MXC Terminals cable details refer to Appendix C. Alarm Inputs The active state of each TTL alarm input is configurable to be active if the voltage on the input is high, or active if the voltage is low. The alarm software detects a change in the state of each input circuit, and raises or clears an input accordingly.
Page 63: Front Panel Layout
Maint V.24 RJ-45 connector provides a V.24 serial interface option for 9500 MXC CT (CT) connection. It supports a default IP address, which means knowledge of the Terminal IP address is not required at login.
Page 64 Chapter 2. 9500 MXC Terminals Item/Label Description Alarm I/O HD-15 connector provides access to two TTL alarm inputs and four form C relay outputs. Connections are mapped in CT. ODU Status LED provides indications of: IDU power off Green Normal operation...
Page 65 Trib ports 1 to 20 RJ-45 connector assemblies for tributary connection; one RJ-45 port per E1/ DS1. E1 termination is set for unbalanced or balanced in 9500 MXC CT. DS1 is 100 ohms balanced with options for AMI or B8ZS, and trib cable length.
Page 66: Ethernet Idu
4-3 in Volume IV. IDU ES may be used in single-link and networked applications, and can be over-air interfaced to 9500 MXC Node comprising the INU, DAC ES or DAC GE, DAC 4x/16x, and ODU 300. Vol. II-2-10...
Page 67: Idu Es Capacity And Bandwidth Options
9500 MXC User Manual IDU ES Capacity and Bandwidth Options ETSI options are indicated in Figure 2-3 and detailed in Table 2-5. ANSI options are in Figure 2-4 and Table 2-6. • For IDU ES with ODU 300ep or ODU 300hp the base license is 50 Mbps.
Page 68 Chapter 2. 9500 MXC Terminals IDU ES ETSI Options Table 2-5. IDU ES License Ethernet Channel Modulation License Option Mbps BW, MHz 50 Mbps QPSK Base 50 Mbps 16 QAM Base 50 Mbps QPSK Base 50 Mbps 64QAM Base 50 Mbps...
Page 69: Idu Es Compatibility
IDU ES can be over-air interfaced to an INU/INUe fitted with a RAC 30v3 or RAC 3X. Table 2-7 indicates current compatibility for ETSI rates; Table 2-8 indicates ANSI rates. Other rates may be supported, check with Alcatel-Lucent or your supplier. At the INU/INUe: •...
Page 70 Chapter 2. 9500 MXC Terminals IDU ES / RAC Compatibility: ETSI Table 2-7. Ethernet BW MHz Modulation IDU ES RAC30v3 RAC3X Assignment 10 Mbps 7 MHz QPSK 20 Mbps 7 MHz 16QAM 20 Mbps 14 MHz QPSK 32 Mbps 7 MHz...
Page 71: Ethernet Module
• Latency on page 2-19 • Ethernet Diagnostics on page 2-20 Ethernet Traffic Configuration IDU ES is configured using CT, the 9500 MXC craft terminal. User-friendly screens prompt for channel size (Ethernet bandwidth), modes of operation, QoS settings, and interface options.
Page 72 Chapter 2. 9500 MXC Terminals Transparent Mode Port and Channel Assignment Figure 2-5. VLAN Mode VLAN or transport mode supports four separate LAN connections. Port 1 is dedicated to channel 1, and ports 2 to 4 are multiplexed to channel 2 to provide three virtual LANs (VLANs 2, 3 and 4).
Page 73: Transport Channel Configuration
9500 MXC User Manual Transport Channel Configuration Selection is provided for channel capacity on a per-channel basis: Channel capacity is selected in multiples of 2.048 Mbps or 1.544 Mbps. • For an ETSI selection each channel supports a maximum 98 Mbps. Where both channels are used the combined maximum extends to 196 Mbps.
Page 74: Flow Control
Chapter 2. 9500 MXC Terminals • 802.1p provides prioritization based on the three-bit priority field of the 802.1p VLAN tag. Each of the possible eight tag priority values are mapped into a four-level (2-bit) priority level. If packets are not tagged, then the Port Default prioritization will apply to these packets.
Page 75: Maximum Frame Size
Other contributors to overall latency are the devices connected to the 9500 MXC network, which for a VoIP circuit will include the external gateway processes of voice encoding and decoding, IP framing, packetization and jitter buffers.
Page 76: Ethernet Diagnostics
Chapter 2. 9500 MXC Terminals Ethernet Diagnostics CT diagnostics screens capture Ethernet performance and history. The data for IDU ES includes: • Port/channel status. • Configured capacities. • Graphed current Rx and Tx throughputs and discards per port and channel.
Page 77: Auxiliary Data And Alarm I/O Module
• Multiple input or internal events may be mapped to a common output. Mapping is achieved using IP addressing for the destination IDU ES terminal, or if the destination is a 9500 MXC Node, to its IP address plus the slot location and output number for the AUX plug-in.
Page 78: Idu Es Layout
Maint V.24 RJ-45 connector provides a V.24 serial interface option for 9500 MXC CT. It supports a default IP address, which means knowledge of the Terminal IP address is not required at login.
Page 79 RJ-45 connector assemblies for wayside tributary connections; one RJ-45 port to 8 per E1/DS1. E1 termination is set for unbalanced or balanced in 9500 MXC CT. DS1 is 100 ohms balanced with options for AMI or B8ZS, and trib cable length.
Page 80: Idu Es Applications
Chapter 2. 9500 MXC Terminals IDU ES Applications IDU ES may be used to provide single-hop connections or used as a radio backbone in multiple-hop star or ring networks. Refer to: • Basic Network Applications on page 2-24. • Ring Applications on page 2-26...
Page 81 9500 MXC User Manual Simple Link With External Switching While IDU ES provides comprehensive layer 2 switch functionality, it can only support a maximum of four directly connected hosts, which for most office applications is insufficient, bearing in mind each device on the LAN must be directly connected to its own port on the switch (star connected).
Page 82: Ring Applications
Chapter 2. 9500 MXC Terminals • NMS visibility between all IDU ES terminals requires linking of the Ethernet NMS ports at each site. As the IDU ES has a single Ethernet NMS port, where three or more are grouped at a site, as at Site B, a simple external hub must be used to provide the required porting capacity.
Page 83: More Information
9500 MXC User Manual IDU ES Links in a Ring Figure 2-13. RSTP IDU ES IDU ES IDU ES RSTP IDU ES IDU ES RSTP IDU ES Ethernet ring IDU ES RSTP IDU ES IDU ES IDU ES RSTP More Information For more information on IDU ES: •...
Page 84: Idu Protection
Chapter 2. 9500 MXC Terminals IDU Protection This section describes IDU protection options: Protection Options IDU 20x Hot-standby, Space Diversity, Ring IDU 155o Hot-standby, Space Diversity Tx switching is not hitless; Rx switching (voting) between the two receive data streams is hitless (errorless) on hot-standby and space diversity.
Page 85 9500 MXC User Manual • Protection is provided for all 40/32 tribs for a path / ODU failure. Each IDU normally takes its Rx data from its directly connected ODU. For a path/ODU failure, data is restored from its partner ODU/IDU via the IDU-IDU expansion cable.
Page 86: Idu Protection Switch Conditions And Criteria
Chapter 2. 9500 MXC Terminals Next: • IDU Protection Switch Conditions and Criteria • IDU Service Restoration Times IDU Protection Switch Conditions and Criteria Tx and Rx are switched separately except for a Tx online switch event where the Rx Online function will follow the Tx to put Tx Online and Rx Online on the same IDU.
Page 87 9500 MXC User Manual • The guard time halves after each period of guard time during which no switching occurs (down to the minimum). • When the guard time decays to its minimum, subsequent switch requests are actioned immediately. • There are two independent guard timers for each protection context, one associated with TX switching and one associated with RX switching.
Page 88 Chapter 2. 9500 MXC Terminals Tx Switch Criteria Switching from the online Tx to standby is initiated for the following local alarm conditions: • Software load failure • Tx path failure: • Tx synthesizer not locked • Transceiver Tx failure •...
Page 89: Idu Service Restoration Times
9500 MXC User Manual IDU Service Restoration Times Service restoration times for a transmit or receive switch are: IDU Transmit Switch: • Within 200ms for a local alarm Tx switch. • Within 20 seconds nominally for a silent Tx switch.
Page 90: Platform Layout And Interoperation Data
IDU 155o ODU 300ep/hp 16/64/128 QAM modulation for 1xSTM1/OC3 Non-protected, hot-standby, space diversity Can be linked to 9500 MXC Node (ODU 300, RAC 30v3, RAC 3X, DAC 155o, AUX) Includes auxiliary data and alarm I/O ODU 300ep/hp QPSK to 256 QAM modulation...
Page 91: Configuration And Diagnostics
Compatible with RAC 30v3 at STM1/OC3 using 128 QAM (27.5-30 MHz channel BW). Configuration and Diagnostics This section provides an overview of the 9500 MXC CT screens provided for IDU/ODU configuration and diagnostics. Refer to: • 9500 MXC CT Log-in on page 2-35 •...
Page 92: Configuration
For information on CT PC connection, Refer to Volume IV, Chapter 2. To enable 9500 MXC CT access on a new (unconfigured) IDU a V.24 connection is required at the outset. Once connected, an IP address can be configured, from which point Ethernet access can be used.
Page 93: Software Reset
9500 MXC User Manual • Alarms, with context-sensitive Helpset support for alarm description, probable cause and recommended remedial actions (For context sensitive help ‘9500 MXC Help’ must be loaded on your PC). • G.826 link performance data and G.821 BER - with built-in BER test function on PDH and SDH tribs.
Page 94 Chapter 2. 9500 MXC Terminals Vol. II-2-38 Alcatel-Lucent...
Page 95: Chapter 3. 9500 Mxc Nodes
• Protected Operation on page 3-73 • Co-channel Operation on page 3-102 • Configuration and Diagnostics on page 3-118 For information on 9500 MXC ODUs, refer to Chapter 4. Platforms This section introduces the INU and INUe platforms for slot location and usage, cross-connects, capacity, and RAC/ODU parameters.
Page 96: Platform Layout
Chapter 3. 9500 MXC Nodes Platform Layout Figure 3-1 illustrates platform support for: • Non-protected and protected/diversity links • Slot availability for option plug-ins • Over-air data types supported • ODU options INU and INUe Platforms Figure 3-1. Supports 3 non-protected links or...
Page 97: Slot Assignments
The backplane bus can operate in one of five user-programmable configurations, NxE1 (2.048 Mbps), NxDS1 (1.544 Mbps), NxDS3 (44.736 Mbps), or NxSTM1/ OC3 (155.52 Mbps). In this way, a 9500 MXC Node can be configured to be an NxE1, NxDS1, NxDS3, or NxSTM1/OC3 radio, or an Ethernet radio with or without companion TDM traffic.
Page 98 Table 3-2 summarizes the Ethernet link data and backplane maximums. While each RF path from a 9500 MXC Node can be configured support the capacities shown, where multiple RF paths are to be established the combined total from each path must not exceed the backplane bus maximum as defined under above.
Page 99 9500 MXC User Manual Relationship of Plug-in Cards to the Backplane Figure 3-3. PDH and SDH Link Options and Backplane Maximums Table 3-1. Bus Rate Link Capacity Options Backplane Max. 5x, 10x, 16x, 20x, 32x, 40x, 52x, 64x, 100x 75x, 93x, 100x...
Page 100: Capacity And Bandwidth: Pdh And Sdh
Chapter 3. 9500 MXC Nodes Capacity and Bandwidth: PDH and SDH The 9500 MXC INU and INUe provide configurable link (over-air) capacity and bandwidth options up to 100xE1 , 127xDS1, 4xDS3, 2xSTM1/OC3. Figure 3-4 shows the capacity migration options and in particular the broad coverage provided by ODU 300 and RAC 30v3/3X combinations.
Page 101: Capacity And Bandwidth: Ethernet
The same RAC and ODU combinations used to transport PDH or SDH traffic are used to transport 9500 MXC fast Ethernet and gigabit Ethernet options. These are enabled on the DAC ES and DAC GE plug-in cards, which incorporate a layer 2 (L2) switch with four user ports and two transport channels.
Page 102 Chapter 3. 9500 MXC Nodes Capacity Assignment The backplane bus setting of Nx2 Mbps (2.048 Mbps), Nx1.5 Mbps (1.544 Mbps) or Nx150 Mbps (155.52 Mbps) determines the capacity multiples used to configure the required Ethernet capacity. The Ethernet capacities selected, along with any TDM capacity, must in turn be supported within the radio or fiber link capacities that the traffic is cross-connected to.
Page 103 9500 MXC User Manual Ethernet versus Wayside Bandwidth Assignment: NxE1 Figure 3-6. Eclipse Liquid Bandwidth Assignment • Select desired Ethernet capacity and E1 wayside channels • Look up required link capacity Aggregate Link Capacity 204 Mbit/s 190 Mbit/s (Example) 130 Mbps aggregate...
Page 104 Chapter 3. 9500 MXC Nodes Higher Capacities With an Nx2 Mbps backplane one INU/INUe with one DAC ES or DAC GE supports Ethernet capacities to 200 Mbps; 200 Mbps represents the backplane maximum and the maximum that can be transported over one radio link. For Nx1.5 Mbps, 200 Mbps (128x1.544 Mbps) is the backplane maximum, but 150...
Page 105 9500 MXC User Manual Ethernet Capacity and RF Channel Bandwidths Table 3-3 and Table 3-4 summarize ETSI and ANSI RF channel bandwidth options for Ethernet capacity assignments from 40 to 300 Mbps. Nominal Ethernet capacities are used. With the RAC 40 CCDP XPIC cards, two links are operated on the same frequency channel, one using the vertical polarization, the other the horizontal.
Page 106 Chapter 3. 9500 MXC Nodes Bandwidth, Modulation and RAC Type: ANSI Table 3-4. Ethernet RF Ch. Modulation Capacity Mbps Bandwidth MHz RAC 30 RAC 30 QPSK RAC 30 RAC 30 RAC 3X RAC 30 RAC 30 RAC 30 RAC 40...
Page 107: Capacity License
9500 MXC User Manual Capacity License Node capacity is licensed according to required RAC capacity. The license is software enabled within a compact flash card, which plugs into the right side of the NCC. The same flash card also holds the configuration for the node and the embedded system software.
Page 108 Chapter 3. 9500 MXC Nodes 9500 MXC Node ODU/RAC Parameters Table 3-5. Tx Power Over-Air ODU Link Capacity Bandwidth Modulation Compatibility ODU 300ep Extended ODU 300ep, hp RAC 30 4xE1 to 75xE1 3.5 to 30 MHz QPSK to 256 QAM...
Page 109: Plug-In Cards
9500 MXC User Manual Plug-in Cards This section introduces the plug-in cards that provide Node management and service customization. Refer to: • Overview on page 3-15 • NCC on page 3-19 • FAN on page 3-21 • RAC on page 3-22 •...
Page 110 Chapter 3. 9500 MXC Nodes Unit Description An INU may be populated with a maximum of three RACs, and the INUe up Radio Access Card to six. Each RAC interfaces to a companion ODU via a single 50-ohm coaxial cable.
Page 111 9500 MXC User Manual Unit Description An INU may be populated with a maximum of three RACs, and the INUe up Radio Access Card to six. Each RAC interfaces to a companion ODU via a single 50-ohm coaxial cable. • RAC 30 interfaces to ODU 300/hp/ep for channel bandwidths to 28/30 MHz and capacities of 4xE1 to 75xE1, 4xDS1 to 100xDS1, 1xE3 to 4xE3, 1xDS3 to 3xDS3, or 1xSTM1/OC3.
Page 112 NPC provides redundancy for the NCC TDM bus management and power Node Protection Card supply functions. A minimum configured 9500 MXC Node would typically consist of an ODU, and an INU populated with an NCC, FAN, RAC, and DAC. Vol. II-3-18...
Page 113: Ncc
9500 MXC User Manual The NCC plugs into a dedicated slot in an INU/INUe. Although the NCC is field replaceable, it is not hot swappable unless an NPC is installed. Refer to: • NCC Functions on page 3-19 • NCC User Interfaces on page 3-20 NCC Plug-in Figure 3-9.
Page 114: Ncc User Interfaces
The four RJ-45 connectors provide Ethernet network management access. 9500 MXC CT login to these ports requires entry of the IP address for the INU/INUe. Ports may also used to provide NMS connectivity to co-located 9500 MXC INU/ INUes and other Alcatel-Lucent and third party radios. Ports auto-resolve for straight or cross-over cables.
Page 115: Fan
9500 MXC User Manual Item/Label Description Status LED Status LED provides indications of: INU/INUe power off Green Normal operation Orange flashing Configuration not supported or software / hardware incompatible Critical alarm One 1RU FAN card is required for an INU.
Page 116: Rac
Chapter 3. 9500 MXC Nodes Different RAC versions provide support for capacity and bandwidth options up to 2xSTM1/OC3. • Available are RAC 30V3, RAC 3X, and RAC 40. • Up to three RACs can be fitted in the INU universal slots, and six in the INUe.
Page 117 9500 MXC User Manual RAC 30V3 Plug-in Figure 3-12. RAC 3X Plug-In Figure 3-13. 3DB 23063 ADAA - Rev 004 July 2007 Vol. II-3-23...
Page 118 Chapter 3. 9500 MXC Nodes RAC Capacity and Bandwidth Options Depending on capacity/bandwidth options, modulation rates are programmed for QPSK, 16QAM, 32QAM, 64QAM, 128QAM, or 256QAM. Table 3-8 on page 3-24 lists the ETSI capacity, modulation, and bandwidth options for RAC 30V3 and RAC 3X.
Page 119 9500 MXC User Manual RAC ANSI Common Carrier System Options Table 3-9. Capacity Modulation Channel Bandwidth RAC 30V3 RAC 3X 4xDS1 QPSK 5 MHz 8xDS1 QPSK 10 MHz 8xDS1 16 QAM 5 MHz 8xDS1 32 QAM 3.75 MHz 16xDS1 QPSK...
Page 120 Chapter 3. 9500 MXC Nodes Capacity Modulation Channel Bandwidth RAC 30V3 RAC 3X 1xOC3 16 QAM 50 MHz 1xOC3 64 QAM 40 MHz 1xOC3 128 QAM 30 MHz 2xOC3 256 QAM 50 MHz Please check the Product Release Notes to confirm the availability of modem profiles.
Page 121 9500 MXC User Manual RAC3X 2STM1,56M,128Q 0.13 2STM1,50M,256Q 0.13 Link Delay Times for RAC 3X: ANSI Rates Table 3-12. RAC3X 32DS1,40M,QPSK 0.65 70DS1,40M,16Q 0.45 84DS1,50M,16Q 0.45 84DS1,40M,32Q 0.45 100DS1,50M,16Q 100DS1,40M,32Q 1OC3,50M,16Q 0.19 1OC3,40M,64Q 0.19 1OC3,30M,128Q 0.19 2OC3,50M,256Q 0.13 RAC Front Panel Layout Figure 3-14 shows the front panel layout.
Page 122 Chapter 3. 9500 MXC Nodes Item/Label Description Green RAC is online with transmit or receive active No receive signal from the ODU Status LED Status LED provides indications of: INU power off Green Normal operation Orange flashing Configuration not supported, or software / hardware...
Page 123 9500 MXC User Manual • When both ends are running 4.0 SW or later, RAC 40s auto-configure both ends to Standard. From SW release 4.0 the ‘Standard’ RAC 40 modem profile is used in all instances, except where operation with an INU/INUe running SW 3.3 or earlier is required.
Page 124 Chapter 3. 9500 MXC Nodes RACs and ODUs on the horizontal and vertical polarizations. Equal-loss couplers must be used with the protected ODUs. For information on RAC 40 operation and applications refer to Co-channel Operation on page 3-102 RAC 40 FEC incorporates Reed-Solomon encoding with interleaving, plus Viterbi encoding.
Page 125 9500 MXC User Manual Item/Label Description INU off-line or ODU transmit muted Green RAC is online with transmit or receive active No receive signal from the ODU Status LED Status LED provides indications of: INU power off Green Normal operation...
Page 126: Dac
Chapter 3. 9500 MXC Nodes DACs provide the intermediary between customer interfaces and the digital backplane. • Different DACs support different circuit rates and formats. Refer to: • DAC 4x on page 3-33 • DAC 16x on page 3-34 • DAC 3xE3/DS3M on page 3-35 •...
Page 127: Dac 4X
9500 MXC User Manual DAC 4x DAC 4x supports up to 4xE1 or 4xDS1 tributaries. • E1 options are 75 ohm unbalanced or 120 ohms balanced. • DS1 encoding options are AMI or B8ZS. Line impedance is fixed at 100 ohms balanced.
Page 128: Dac 16X
Chapter 3. 9500 MXC Nodes DAC 16x DAC 16x provides up to 16xE1 or 16xDS1 tributaries. • E1 options are 75 ohm unbalanced or 120 ohms balanced. • DS1 encoding options are AMI or B8ZS. Line impedance is fixed at 100 ohms balanced.
Page 129: Dac 3Xe3/Ds3M
G.703, G.742 and G.751. Operation is compatible with industry standard E13 multiplexers, meaning that at the E3 destination a 3rd party E13 multiplexer can be used. Allows side-by-side transport with other E1 traffic over a 9500 MXC link. 3DB 23063 ADAA - Rev 004 July 2007 Vol. II-3-35...
Page 130 E3 streams. Each of the two transparent E3 interfaces (Tx/Rx 1 and Tx/Rx 2) provides a 34.368 Mbps connection for transport as 17xE1 over a 9500 MXC NxE1 network. Allows side-by-side transport with other E1 traffic over a 9500 MXC link.
Page 131 9500 MXC User Manual DAC 3xE3/DS3M Front Panel Description Table 3-18. Item/Label Description Plug-in fastener Finger-grip screw-type fastener and card pull (2). On-Line LED On-Line LED provides indications of: INU power off Green DAC is online communicating with a remote DAC 3xE3/DS3M...
Page 132: Dac 1X155O And Dac 2X155O
• DAC 1x155o and DAC 2x155o should not installed back-to-back (trib interconnected) over more than 2 hops of 9500 MXC (not more than one DAC-DAC repeated hop). • However, there is no practical limit to the number of radio link hops (RAC-to-RAC) between the DACs.
Page 133 9500 MXC User Manual DAC 155o Plug-in Figure 3-21. Figure 3-22 shows the DAC 1x155o front panel layout. Table 3-19 on page 3-39 describes the interfaces. DAC 1x155o Front Panel Layout Figure 3-22. DAC 1x155o Front Panel Description Table 3-19.
Page 134: Dac 155Om
Ethernet data, where TVT mode is required. • Clocking options are provided for recovered-clock and internal. • 9500 MXC NMS may be transported within the MSOH or RSOH, access to which is provided within the NMS bytes on the INU backplane.
Page 135 9500 MXC User Manual DAC 155oM Plug-in Figure 3-23. The connector assembly is an LC type on an SFP (small formfactor pluggable) transceiver module, and cable options are available, as accessories, for extension to SC or FC types. LC-LC attenuator cable options are also available.
Page 136 Chapter 3. 9500 MXC Nodes DAC 155oM Front Panel Description Table 3-20. Item/Label Description Plug-in fastener Finger-grip screw-type fastener and card pull (2). On-Line LED On-Line LED provides indications of: INU power off Green DAC is online communicating with a remote DAC 155oM...
Page 137: Dac 2X155E
• DAC 2x155e should not installed back-to-back (trib interconnected) over more than 2 hops of 9500 MXC (not more than one DAC-DAC repeated hop). • However, there is no practical limit to the number of radio link hops (RAC-to-RAC) between the DACs.
Page 138 Chapter 3. 9500 MXC Nodes DAC 2x155e Figure 3-26. Figure 3-27 shows the DAC 2x155e front panel layout. Table 3-21 describes the interfaces. DAC 2x155e Front Panel Layout Figure 3-27. DAC 2x155e Front Panel Description Table 3-21. Item/Label Description Plug-in fastener Finger-grip screw-type fastener and card pull (2).
Page 139: Dac Es
9500 MXC User Manual Item/Label Description Critical alarm: Trib LOS or SW/HW failure Trib connectors Two BNC Tx/RX female connector pairings for 75 ohm unbalanced tributary connection. Includes situations where the slot configuration does not support the plug-in, or the plug-in requires a later/different version of system software.
Page 140 Chapter 3. 9500 MXC Nodes • Flow control through 802.3x pause-frame option; • Frames sizes to 1536 bytes; • Comprehensive RMON and performance indicators; • Compatibility with the DAC GE (from SW release 3.6). DAC ES Plug-in Figure 3-28. Figure 3-29 illustrates basic operational blocks within the DAC ES. Four RJ-45 customer ports connect to an Ethernet switch, which provides the bridge/switch and queueing functions between the ports and two transport channels.
Page 141 RAC (or RAC and DAC 155oM). Transparent Mode is applicable to ring networks using 9500 MXC ring-wrap protection, with one channel is assigned to the east, the other to the west.
Page 142 Chapter 3. 9500 MXC Nodes VLAN Mode VLAN Mode supports four separate network interconnections - each is held separate from the other. VLAN 1 is the same as for Mixed Mode, where dedicated transport is provided for port 1 traffic. For Ports 2, 3 and 4, three...
Page 143 9500 MXC User Manual Basic Port Settings Customer selection/confirmation is provided for the following port parameters: Enabled A port must be enabled to allow traffic flow. Name A port name or other relevant port data can be entered. Connection Type and Speed Provides selection per-port of auto or manual settings for half or full duplex operation on speeds of 10 Mbps or 100 Mbps.
Page 144 Chapter 3. 9500 MXC Nodes • 802.1p provides prioritization based on the three-bit priority field of the 802.1p VLAN tag. Each of the possible eight tag priority values are mapped into a four-level (2-bit) priority level. If packets are not tagged, then the Port Default prioritization applies to these packets.
Page 145 9500 MXC User Manual from 64 to 1536 bytes, it currently supports sizes of 1518/1522, or 1536 bytes (1518 for non-tagged frames, 1522 for tagged frames). Diagnostics CT diagnostics screens capture Ethernet performance and history. The data for DAC ES includes: •...
Page 146 Chapter 3. 9500 MXC Nodes Item/Label Description Green Normal operation Orange flashing Configuration not supported, or software / hardware incompatible Critical alarm RJ-45 Port Four RJ-45 connectors labelled Ports 1 to 4 provide 10/100Base-T access to customer Connector networks. Internally, the interface implements an ethernet bridging/switching function.
Page 147: Dac Ge
9500 MXC User Manual DAC GE The DAC GE is a Gig-Ethernet plug-in. Refer to: • DAC GE Description on page 3-53 • DAC GE Modes of Operation on page 3-56 • DAC GE Transport Channels on page 3-59 • DAC GE Basic Port Settings on page 3-60 •...
Page 148 Chapter 3. 9500 MXC Nodes • Layer 2 link aggregation (802.3ad), and layer 1 link aggregation; • Flow control through 802.3x pause-frame option; • Jumbo frames to 9600 bytes; • Comprehensive RMON and performance indicators; • Compatibility with the DAC ES for Nx1.5 Mbps and Nx2 Mbps traffic selections (from SW release 3.6).
Page 149 9500 MXC User Manual • Payload throughputs are determined by the configured port and channel speeds (bandwidth), QoS settings, and internal and external VLAN information. • Ethernet throughputs supported on the two transport channels depend on the backplane bus setting: •...
Page 150 Chapter 3. 9500 MXC Nodes DAC GE Modes of Operation DAC GE supports three operational modes, transparent, mixed or VLAN, which determine the port-to-port and port-to-channel relationships within the L2 switch. RWPR-enhanced RSTP may be enabled with transparent, mixed or VLAN modes, though for most applications transparent is selected.
Page 151 9500 MXC User Manual Aggregation weighting refers to the way the aggregation keying process allocates traffic between the aggregated link grouping. 16 keys are provided and traffic is randomly assigned to a key. With two aggregated links of equal capacity the weighting (number of keys) should be split 8/8. With three aggregated links of equal capacity the split should be 5/5/6.
Page 152 Chapter 3. 9500 MXC Nodes Transparent Mode with C1, C2 and P1 Aggregation Figure 3-38. Mixed Mode Mixed Mode provides a two-LAN solution where LAN P1-C1 provides dedicated transport for port 1 traffic. A second transparent/broadcast mode LAN connection is provided with P1, P2, P3 and C2 interconnected.
Page 153 9500 MXC User Manual VLAN Mode VLAN Mode supports four separate LANs. LAN 1 is the same as for Mixed Mode, where dedicated transport is provided for port 1 traffic. For ports 2, 3 and 4, three separate (virtual) LANs (VLANs 2, 3 and 4) are multiplexed to C2, with internal tagging of the packets ensuring correct end-to-end matching of LANs over the link.
Page 154 Chapter 3. 9500 MXC Nodes • 200 Mbps in 2 Mbps (2.048 Mbps) steps • 196 Mbps in 1.5 (1.544 Mbps) steps • 300 Mbps in 150 Mbps (155.52 Mbps) steps DAC GE Basic Port Settings Customer selection is provided for the following port parameters: Enabled A port must be enabled to allow traffic flow.
Page 155 9500 MXC User Manual DAC GE Priority Mapping Provides selection of queue-controller operation for the following options. This selection applies to all ports. • Port default. Enables the setting of a four-level port priority on each of the four ingress ports. See DAC GE Basic Port Settings above.
Page 156 For 9500 MXC two modes of link aggregation can be configured with the DAC GE, layer 2 (L2) or layer 1 (L1): •...
Page 157 9500 MXC User Manual • Normally (default), the 16 LAKs are split evenly, or near-even for an odd-number split, between the aggregated channels and/or ports. For example where two channels are configured for link aggregation 8 LAKs are assigned to each; for two channels and one port, 6 LAKs are assigned to the port and 5 to each of the channels.
Page 158 Chapter 3. 9500 MXC Nodes RWPR DAC GE incorporates RSTP in the form of RWPR-enhanced RSTP. RWPR (Resilient Wireless Packet Ring) employs a patent-pending rapid-transport-channel failure detection (RFD) mechanism to enhance the built-in DAC GE RSTP capability. RFD accelerates the normal processes used to achieve RSTP switching on an Ethernet ring/mesh to bring typical service restoration or re-convergence times of 2 to 5 seconds down to as low as 50 ms.
Page 159 9500 MXC User Manual • Graphed historical Rx and Tx throughputs, frame type and discards per port and channel. • Historical statistics per port and channel. • Comprehensive RMON performance statistics per port and channel. • Event history. For more information refer to Volume IV, Chapter 15 for: •...
Page 160: Aux
Chapter 3. 9500 MXC Nodes DAC GE Front Panel Descriptions Table 3-24. Item/Label Description Plug-in fastener Finger-grip screw-type fastener and plug-in pull (2). Status LED Status LED provides indications of: INU power off Green Normal operation Orange flashing Configuration not supported, or software / hardware...
Page 161: Auxiliary Interfaces
Figure 3-42. Auxiliary Interfaces Three auxiliary interfaces are provided. Each may be configured in 9500 MXC CT for synchronous 64 kbps data or serial data to 19.2 kbps. • Synchronous conforms to TIA/EIA-422 / V.11 at 64kbps, with selectable clock.
Page 162: Installation And Operation
Intended applications are: • Transport of 3rd party NMS (or other data) over a 9500 MXC network. • Transport of 9500 MXC NMS over a 3rd party network to a remote 9500 MXC node or network. Auxiliary Data and NMS Functions...
Page 163: Alarm I/O Interfaces
9500 MXC User Manual • For a DAC 155oM, the maximum overhead capacity is 512 kbps, but is only available when the MSOH (Multiplexer Section Overhead) NMS option is selected. If NMS data is assigned to the RSOH (Regenerator Section Overhead), the total NMS overhead is 192 kbps, meaning just one auxiliary data channel can be configured.
Page 164: Aux Front Panel
Chapter 3. 9500 MXC Nodes These are maximum values, which require de-rating if the relay is to be Note: used for frequent-switch applications. The contact voltage must be restricted to less than 60 Volts for compliance with SELV regulations. Maximum current specification applies up to 30 Volts...
Page 165: Npc
9500 MXC User Manual Includes situations where the slot configuration does not support the plug-in, or the plug-in requires a later/different version of system software. Indicates a data-affecting hardware failure. The NPC provides a protection option for the NCC with backup for TDM bus management (bus clock), and power supply.
Page 166 Chapter 3. 9500 MXC Nodes The NPC is field replaceable and hot-swappable (providing the NCC is on line). It plugs into slot 4 of an INU, or slot 10 of an INUe. An INU/INUe must always start with a valid NCC installed; the NPC will provide protection only after a node has been powered up.
Page 167: Protected Operation
• NCC Protection with NPC Option on page 3-101 For additional information on protection operation, refer to Appendix I. Protection Overview 9500 MXC Node includes options for protection of hardware, radio path, tributary, and NCC functions. Protected operation between an INU and IDUs is not supported. Where protected IDUs are to be used, they must be at both ends of the link.
Page 168 (single link) path failure events. Switching of ring-protected circuits is not hitless. 9500 MXC also supports dual-protection whereby a master protection option protects two subordinate protected links, or one protected link with one non-protected link.
Page 169: Hot Standby And Diversity
9500 MXC User Manual Tributary Protection E3/DS3 and STM1/OC3 DACs, may be paired to provide hot-standby tributary protection. The protectable DACs are: • 2xDAC 3xE3/DS3M • 2xDAC 155o or • 2xDAC 2x155o • 2xDAC 2x155e • 2xDAC 155oM Trib protection switching is not hitless.
Page 170: Dual Protection
Chapter 3. 9500 MXC Nodes • Equal-split has a nominal 3.5/3.5 dB loss per side. • Unequal-split has a nominal 1.6 /6.4 dB insertion loss. For more information on coupler losses, refer to Coupler Losses on page 7-19, Volume IV, Chapter 7.
Page 171: Ring Protection
Ring Protection 9500 MXC directly supports ring protection of NxE1 or NxDS1 traffic. 9500 MXC does not support E3/DS3 or STM1/OC3 rings. Where ring protection of such rates is required, an external add/drop mux is required. 9500 MXC directly supports RSTP protection of Ethernet traffic in ring and mesh networks using the DAC GE GigE plug-in.
Page 172: Super Pdh Rings
For information on maximum ring capacities, refer to Appendix E. Super PDH Rings 9500 MXC Node supports protected PDH ring configurations for capacities to 75xE1 or 100xDS1, with traffic switching at the INU/INUe level. The rings are implemented by east/west facing RAC and ODU combinations from a single node (INU/INUe).
Page 173 9500 MXC User Manual North Gateway or Any-to-Any Ring Topologies Super-PDH ring architecture supports configurations for North Gateway or Any-To-Any topologies. With North Gateway, one of the nodes operates as the gateway, through which all traffic on the ring is sourced and sent. For any-to-any operation, traffic can be routed from any node in the ring to any other node.
Page 174 Chapter 3. 9500 MXC Nodes Normal No-fault Operation Figure 3-47. East Node A facing Shows two of up to 64xE1 Primary ring or 84xDS1 circuits Secondary ring (unused) West facing Node B East Node D facing East facing West facing...
Page 175 Refer to Table 3-29. To avoid most instances of unacceptable delays for equipment connected to a 9500 MXC ring, the number of hops should not exceed sixteen.
Page 176 Chapter 3. 9500 MXC Nodes Typical Ring Delay Times Table 3-29. Ring Capacity 20xE1 40xE1 75xE1 Delay Per Hop 0.45 ms 0.3 ms 0.25 ms Delay for 16 Hops 7.2 ms 4.8 ms 4 ms Double Break Operation In the event there are two or more link failures on the ring, (adjacent, or non-adjacent links), the traffic will wrap up to each side of the failed points to provide limited service restoration.
Page 177 9500 MXC User Manual Point-to-Point Traffic Overlay on a Ring Point-to point overlay operation is illustrated in Figure 3-50. The additional capacity needed for overlay is required only on the overlaid links. Overlaid traffic is not ring protected. Example of a Ring Network with Point-to-Point Traffic Overlay Figure 3-50.
Page 178: 1+1 Protected Ring Links
(SD) is the required/recommended 1+1 protection mode • One, some or all links on the ring may be 1+1 protected. • An 9500 MXC ring Node may have one or both (east and/or west) ring links configured for 1+1 protection.
Page 179 9500 MXC User Manual • The path supported by a 1+1 link exhibits a path fail condition. The path failure switching criteria are the standard ring path failure criteria, with the exception of the 10 BER option . Refer to Radio Wrap Conditions on page 3-98.
Page 180: Co-Channel Xpic Operation On A Ring
Chapter 3. 9500 MXC Nodes A ring wrap occurs when the path provided by the space diversity link fails, or a Tx or Rx online switch event occurs on the space diversity link, or both space diversity receivers trigger a demodulator not locked alarm.
Page 181: Ethernet Traffic On A Ring
A spanning tree capability is required to resolve such loops. The transport solutions are provided by: • 9500 MXC Node with the DAC ES for Fast Ethernet. Ring protection options include radio-environment, and Ethernet-environment. With Ethernet-environment an external RSTP switch is normally installed at each site.
Page 182 Chapter 3. 9500 MXC Nodes Example of Radio-Environment Protection for Ethernet Traffic Figure 3-54. DAC ES Ch 2 6x2 Mbps Transport Ch Node A on ring ccts 25 to 30 Ethernet ring must not be closed Ethernet port Ch 1...
Page 183 • E1/DS1 traffic may also be configured in the ring, which may be point-to-point (not protected) or ring-wrap protected. • A single 9500 MXC Node with a DAC GE supports Gig-Ethernet rings to 150 Mbps. One DAC GE is configured to provide two transport channels, one to the east RAC, the other to the west.
Page 184 If a radio link fails: • RSTP re-directs Ethernet traffic on the ring. • 9500 MXC ring protection re-directs E1 traffic on the ring to bypass the break. When used with an external RSTP switch: • The DAC ES or DAC GE should be configured for Mixed Mode (not Transparent mode), to provide dedicated ports for each of the two (east and west) transport channels (C1 and C2).
Page 185 9500 MXC User Manual Example of RSTP and Ring-Wrap Protection on a Ring Figure 3-55. RSTP Switch Ethernet port connections Ch 1 Ch 2 16xE1 Transport Ch Node A on pt-pt ccts 1 to 16 16xE1 Transport Ch on pt-pt ccts 1 to 16...
Page 186: Dac/Tributary Protection
• TA protection must be used where two 9500 MXC INU/INUes are to be interfaced using protected DACs. The DACs are configured as primary and secondary. The primary is the default DAC for online Rx and Tx.
Page 187: Protection Switching Criteria
9500 MXC User Manual Protection Switching Criteria In this section, switching criteria and service restoration times are provided. Refer to: • Switching Guard Times • Hot-standby and Diversity Switching Criteria • Dual Protection Switching Criteria on page 3-97 • Ring Protection Switching Criteria on page 3-98 •...
Page 188 Chapter 3. 9500 MXC Nodes • Service Restoration Times for Hot Standby and Diversity on page 3-97 Transmitter Switching Transmit switching for hot-standby and space diversity is not hitless; service is restored within 200 ms. Transmit switching for frequency diversity is hitless providing the online Tx RAC is not removed.
Page 189 • RAC plug-in is missing or incorrect • RAC software load failure Manual return to primary RAC transmit requires a 9500 MXC CT command in the System/Controls screen. This should be forced for hot-standby installations using an unequal coupler where the primary RAC is assigned to the low-loss side.
Page 190 (primary) RAC/ODU is switched to become the online bus-driving RAC. This switching is not hitless, and the primary RAC remains as the online bus-driving RAC until changed within 9500 MXC CT, or a subsequent bus-drive switch event. • Switching from the online to offline Rx RAC will not be initiated if the offline Rx RAC has failed, or the offline Rx RAC has been removed or replaced by an incorrect plug-in.
Page 191: Dual Protection Switching Criteria
9500 MXC User Manual Service Restoration Times for Hot Standby and Diversity Service restoration times (detection, switching and recovery) for a switch event are: Transmit Switch • 200 ms maximum for a local alarm • 20 seconds maximum for a remote-end command (silent transmitter event) The 20 second period is set to prevent unwanted switching caused by momentary path fade or other switching events.
Page 192: Ring Protection Switching Criteria
Chapter 3. 9500 MXC Nodes Service Restoration Times for Dual Protection For the subordinate links their service restoration times as individual protected links are unaltered from those stated above for hot-standby and space diversity. The service restoration times for a master switch are as follows, and apply for a switch between: •...
Page 193 9500 MXC User Manual • Rx synthesizer not locked • Rx IF synthesizer not locked • Demodulator not locked • ODU Tx cable IF synthesizer not locked • 10 BER (user-selectable wrap and/or unwrap options) • RAC plug-in is missing •...
Page 194: Dac Protection Switching Criteria
Chapter 3. 9500 MXC Nodes setting of a time of day when an unwrap will occur providing all wrap conditions have been cleared for a period not less than that set in the Error-free Timer. This timer has a 1-hour window; if the conditions which caused the wrap are not cleared by the Error-free Timer during this window, then Delay Ring Unwrap resets for the same time the following day.
Page 195: Ncc Protection With Npc Option
9500 MXC User Manual NCC Protection with NPC Option The NPC plug-in provides protection for NCC TDM bus management (bus clock), and power supply functions. One NPC can be installed per INU/INUe. Bus protection protects all tributary and auxiliary traffic; Alarm I/O is not protected.
Page 196: Co-Channel Operation
Chapter 3. 9500 MXC Nodes Co-channel Operation This section provides data on Co-channel Dual Polarization (CCDP) operation with Cross-Polarization Interference Cancellation (XPIC). This allows two radio links of identical capacity and modulation to operate over the same path, on the same frequency channel, by operating one link on horizontal polarization, and the other on vertical.
Page 197 Example Co-Channel STM1 RAC 40 Deployment Figure 3-57. To vertical feedhead Dual Polarized Antenna To horizontal feedhead XPIC in/out connections 9500 MXC fitted with RAC 40s meets ETSI EN 301 127 requirements for 3DB 23063 ADAA - Rev 004 July 2007 Vol. II-3-103...
Page 198: Rac 40 Operating Guidelines
Chapter 3. 9500 MXC Nodes co-channel operation. This document specifies the performance of a system in the presence of cross polarization interference (XPI) coming from an opposite polarization. Refer to RAC 40 Operating Guidelines for application data and example configurations.
Page 199: Settings, Protection And Atpc
9500 MXC User Manual Settings, Protection and ATPC • Each RAC 40 in a co-channel XPIC pairing must be configured for the same frequency, capacity and modulation. • A special Tx mute function applies if one of the receive RACs fails, the RAC is withdrawn, or the XPIC cables are removed or incorrectly connected.
Page 200: Example Configurations
Chapter 3. 9500 MXC Nodes Remote Tx Mute This section sets out the special operating conditions that apply to RAC 40 CCDP links under Rx failure conditions to ensure continued operation of the remaining link. • XPIC interference cancellation cannot function if one of the RACs is withdrawn, its XPIC cables are removed or are incorrectly installed, or there is a RAC hardware failure.
Page 201 • Co-channel 2x 75xE1 or 2x 100xDS1 aggregation, as in Figure 3-59. • Co-channel 2x 75xE1 or 2x 100xDS1 9500 MXC Super-PDH ring operation. However for a typical single-gateway ring (all traffic sourced and sunk at one site on the ring), 2x 64xE1 or 2x 84xDS1 are the ring maximums.
Page 202 Chapter 3. 9500 MXC Nodes Co-channel 2+0 75xE1 Backhaul Figure 3-59. ODU 300 75xE1 ODU 300 75xE1 (V) ODU 300 75xE1 (H) 64xE1 ODU 300 RAC 40 RAC 30 XPIC Cross-Connect Cables 75xE1 RAC 40 RAC 30 150xE1 DAC 16x...
Page 203 9500 MXC User Manual • The nominal loss through each coupler is 3.5 dB, meaning an additional 7 dB loss must be included in the system gain calculations for each link. • All RAC 40 capacity options are supported for 2+2 protection: 64x, 75xE1, 70x, 84x, 100xDS1, or STM1/OC3.
Page 204 Chapter 3. 9500 MXC Nodes 4+4 Hot-standby Operation Figure 3-62 illustrates 4+4 ‘quattro’ operation where CCDP (co-channel dual polarization) and ACCP (alternate channel co-polarization) are used to support hot-standby protected operation on four co-path links. • Supports a maximum of 4x 75xE1, 4x 100xDS1, or 4x STM1/OC3 on two 28/ 30 MHz radio channels.
Page 205 Ch D Secondary Ring Node Configurations RAC 40 CCDP operation may be included within 9500 MXC ring networks to support two concentric rings on the same frequency channel. The rings may be configured for any of the capacities supported by the RAC 40, but bear in mind: •...
Page 206 Chapter 3. 9500 MXC Nodes • Co-channel ring links can be 1+1 protected using space diversity or hot-standby. • 1+1 protection of a ring-protected link is normally implemented to provide path protection as distinct from equipment protection. Hence space diversity (SD) is the required/recommended 1+1 protection mode.
Page 207 • Each INU supports two 1xSTM1 links; STM1 east and STM1 west. • Each INU ports its STM1 east and west tribs to an external SDH mux, which provides the ring protection mechanism. • 9500 MXC links are configured for point-to-point operation. Co-Channel STM1 Ring Node with Drop-Insert Figure 3-63.
Page 208 Chapter 3. 9500 MXC Nodes • DAC GE 'C' in INU 2 provides the RWPR ring switch function and hosts the local LAN. Note that the east, west and local LAN interfaces are all port-connected; the DAC GE 'C' transport channels are not configured (no backplane bus access is required).
Page 209 Co-Channel 64xE1 Ring Node Figure 3-65 illustrates co-channel ring operation. • 9500 MXC Super-PDH ring operation provides the ring protection mechanism. For single gateway rings 64xE1 or 84xDS1 are the ring capacity maximums. Co-Channel 64xE1 Ring Node with 16xE1 Drop-Insert Figure 3-65.
Page 210 Chapter 3. 9500 MXC Nodes Space Diversity Protected Co-channel Ring Links Figure 3-66 illustrates space diversity protection of co-channel ring links. • Where path protection of a ring link is required space diversity (SD) is recommended. • One or all ring links can be SD protected.
Page 211 4+4 Space Diversity Operation Using CCDP and ACCP Figure 3-67 illustrates ‘quattro’ 4+4 operation. • When used within 9500 MXC Super PDH rings this configuration supports up to four co-path space diversity protected (SD) ring links. • The combination of CCDP (co-channel dual polarization) and ACCP (alternate channel co-polarization) supports the four links on two 28/30 MHz channels.
Page 212: Configuration And Diagnostics
For more information on configuration and management, refer to Chapter 5. 9500 MXC CT Log-in The INU and INUe include Ethernet and V.24 front-panel 9500 MXC CT PC (NMS) ports. For Ethernet (10/100Base-T NMS port) there are two connection options: •...
Page 213: Configuration
CT configuration screens for 9500 MXC INUs are common to those used for IDUs (where service functionality is the same). More information: • For a summary list of configuration features, refer to 9500 MXC CT Feature Summary on page 5-2 • For information on a recommended configuration process for a new INU/INUe, refer to Procedure Overview for a New Installation on page 3-7 of Volume III.
Page 214 Chapter 3. 9500 MXC Nodes • For a list of troubleshooting processes supported by the CT Diagnostic screens, refer to Using CT Diagnostics Screens on page 2-33 of Volume V. Vol. II-3-120 Alcatel-Lucent...
Page 215: Chapter 4. Outdoor Units
• Base and cover passivated and then polyester powder coated • Compression seal for base-cover weatherproofing • Carry-handle 9500 MXC ODU 300ep Housing Figure 4-1. The ODUs include a waveguide antenna port, Type-N female connector for the ODU cable, a BNC female connector (with captive protection cap) for RSSI access, and a grounding stud.
Page 216: Odu Data
Chapter 4. Outdoor Units The ODUs, are designed for direct antenna attachment via a 9500 MXC-specific mounting collar supplied with the antennas. ODU polarization is determined by the position of a polarization rotator fitted within the antenna mounting collar (the ODU installed such that there is correct waveguide port alignment between the ODU and its antenna).
Page 217 Refer to Volume III, Chapter 2. for information on: • Installation • Lightning surge suppression • Waveguide flange data Refer to the 9500 MXC datasheets (ETSI or ANSI) for complete specifications. 3DB 23063 ADAA - Rev 004 July 2007 Vol. II-4-3...
Page 218 Chapter 4. Outdoor Units Vol. II-4-4 Alcatel-Lucent...
Page 219: Chapter 5. Configuration And Diagnostics
Chapter 5. Configuration and Diagnostics This chapter introduces features and capabilities of the craft terminal, 9500 MXC 9500 MXC is a software-driven product; there are no manual controls. 9500 MXC CT CT is a web-enabled application supported in the 9500 MXC system software.
Page 220: 9500 Mxc Ct Feature Summary
Chapter 5. Configuration and Diagnostics For an overview of configuration and diagnostic features, refer to 9500 MXC CT Feature Summary on page 5-2. For information on CT PC connection, refer to Volume IV, Chapter 2. 9500 MXC CT Feature Summary Table 5-1 summarizes configuration features, Table 5-2 diagnostic features.
Page 221 9500 MXC User Manual 9500 MXC CT Diagnostic Features Table 5-2. Diagnostic Feature Function Summary System summary The system summary screen provides a system layout and real-time status overview for a Node or Terminal. The layout options support slot assignment selection/confirmation for INU/INUe plug-in options.
Page 222 • The software reset is equivalent to a power-down reboot (power off - pause - power on), and saves a copy of the Helpdesk Data File to a default folder on your CT PC. • The clear option clears all (unwanted) historical data from the Event Browser and History screens. Vol. II-5-4 Alcatel-Lucent...
Page 223: Chapter 6. 9500 Mxc Performance And Diagnostic Features
Chapter 6. 9500 MXC Performance and Diagnostic Features This chapter highlights some of the extensive 9500 MXC performance and diagnostic features. Refer to: • 9500 MXC Node on page 6-1 • 9500 MXC Terminal on page 6-6 • Operation on page 6-7 •...
Page 224: Platform
Chapter 6. 9500 MXC Performance and Diagnostic Features Platform The Node delivers a nodal solution; one 9500 MXC platform directly supports up to six links. Radio paths and customer interfaces are customized by plug-in cards, with interconnection of traffic and services on a high-speed backplane bus.
Page 225: Capacity And Modulation
9500 MXC User Manual Capacity and Modulation Capacity and modulation can be selected up to the maximum supported by each installed RAC/ODU. TDM Transport: • For RAC 30V3, ETSI capacity options extend from 5xE1 to 75xE1, and STM1. North American options extend from 4xDS1 to 100xDS1, 1xDS3 to 4xDS3, and OC3.
Page 226: Protection
TDM Protection Options Hot-standby and diversity options are complemented by ring protection for PDH traffic, where the protection is managed within the 9500 MXC for Super-PDH ring capacities up to 75xE1 or 100xDS1; no external equipment is required. Ring protection timers are provided to set an unwrap time, which can be set to act after a period of error-free operation, or to a time of day.
Page 227: Co-Channel Xpic
9500 MXC User Manual • Traffic can be configured to ride side-by-side with E1 or DS1 traffic. DAC GE • DAC GE supports one or two transport channels with capacities selected in multiples of 2 Mbps, 1.5 Mbps, or 150 Mbps.
Page 228: Odus
ODUs on page 6-2. Inter-operation Terminals may be linked to like Terminals, and to a 9500 MXC Node to support Terminal spurring from a Node. • A 9500 MXC Node when equipped with the appropriate RAC, DAC and ODU combinations interfaces to an IDU 20x, IDU ES or IDU 155o.
Page 229: Terminal Auxiliary Data And Alarm I/O
Automatic Transmitter Power Control (ATPC) for the 9500 MXC Node and Terminal is configurable over their full dynamic range in 0.1 dB steps. ATPC is enabled/disabled through 9500 MXC CT, with the operator able to select a target fade margin, and low and high transmit power limits.
Page 230: Adaptive Equalization
Each of these registers multiply successive delayed samples of the received signal by weighting-coefficients to remove propagation induced inter-symbol interference. Tx Power Management 9500 MXC platforms provide comprehensive power management options for: • Power Output • Power Control Range • Power Monitoring Power Output Output power is band and modulation dependent.
Page 231: Power Monitoring
Viewed Tx power ranges always match the capabilities of the ODU for a given modulation. When modulation is changed, 9500 MXC CT automatically adjusts/ restricts Tx Power to be within valid range. Diagnostics Diagnostic capabilities include: •...
Page 232: System Summary
Chapter 6. 9500 MXC Performance and Diagnostic Features • Front Panel LEDs System Summary The System Summary screen provides a single-view snapshot of the configuration and health of a Node/Terminal. For the Node it presents plug-in card interconnections, capacities configured and connection status. Single click access is provided to related screens for configuration and diagnostics.
Page 233: System/Controls
9500 MXC User Manual For the Ethernet screens (DAC ES, DAC GE), RMON performance statistics are displayed for each port and channel. For a DAC 16x or DAC 4x, background circuit error performance is captured on a selected E1 trib using the CRC (Cyclic Redundancy Check) bits in the G.704 multiframe.
Page 234: Data Menu
Circuit Loopbacks The Circuit Loopback screen enables application of a both-way loopback on the TDM bus. Applies to a 9500 MXC Node only. Circuit loopbacks may be applied to E1, E3, DS1, DS3 or STM1/OC3 selections. Auxiliary data circuits are also supported. Only one Circuit Loopback can be applied at a time, and only traffic on the selected circuit is affected by circuit loopback activation.
Page 235: Front Panel Leds
Front Panel LEDs Front panel LEDs provide a quick indication of status, online, diagnostic and alarm states. Refer to 9500 MXC LEDs on page 2-10 of Volume IV for information on LED indications. 3DB 23063 ADAA - Rev 004 July 2007...
Page 236 Chapter 6. 9500 MXC Performance and Diagnostic Features Vol. II-6-14 Alcatel-Lucent...
Page 237: Volume Iii 9500 Mxc Installation
Volume III 9500 MXC Installation...
Page 239: Chapter 1. Introduction
9500 MXC is a Class A product. In a domestic environment it may cause radio interference in which case the user may be required to take adequate measures. This equipment is intended to be used exclusively in telecommunications centers.
Page 240: Installation Overview
RSL indication in 9500 MXC CT Installation can be completed up to antenna alignment without the use of 9500 MXC CT, the PC based craft terminal. 9500 MXC CT is required to check and configure a 9500 MXC Node or Terminal.
Page 241: Before Going On Site
Table 1-1. Equipment Tool/Material Description Antenna As required by the Alcatel-Lucent offers antennas from various suppliers. Refer to manufacturer the manufacturer’s data supplied with each antenna for required and recommended installation tools and equipment. 9500 MXC Basic electrician’s toolkit The kit must include a crimp tool for attaching lugs to stranded...
Page 242: Unpacking The Equipment
3. If there has been shipping damage or there are discrepancies between the equipment expected and the equipment received, contact your Alcatel-Lucent service support center or your supplier. Vol. III-1-4...
Page 243: Chapter 2. Outdoor Installations
Chapter 2. Outdoor Installations This chapter describes the following installation procedures: • Installing the Antenna • Installing the ODU • Installing a Coupler • Installing ODU Cables and Connectors • Installing Lightning Surge Suppressors • Weatherproofing Installing the Antenna Antennas must be installed in accordance with the manufacturer’s instructions. •...
Page 244: Installing The Odu
• Direct-Mount ODU Attachment Procedure on page 2-9 Overview The ODU is attached to its mounting collar using four mounting bolts, with captive 19 mm (3/4”) nuts. The ODU mounts directly to its antenna mount, as shown in Figure 2-1. Vol. III-2-2 Alcatel-Lucent...
Page 245 9500 MXC User Manual ODU and Mounting Collar Figure 2-1. Figure 2-2 shows the ODU mounting collar, pole mount and polarization rotator for an Andrew antenna. Andrew Pole Mount and ODU Mounting Collar Figure 2-2. Figure 2-3 shows the ODU mounting collar, pole mount, and polarization rotator 3DB 23063 ADAA - Rev 004 July 2007 Vol.
Page 246 Radio Waves Pole Mount and Mounting Collar Figure 2-3. Figure 2-4 shows the ODU mounting collar, pole mount, and polarization rotator for a Precision antenna. Precision Pole Mount and ODU Mounting Collar Figure 2-4. Next step: Setting the Polarization on page 2-5. Vol. III-2-4 Alcatel-Lucent...
Page 247: Setting The Polarization
The V and H settings are indicated on the rotator head. • Remote-Mounted ODUs are used where standard antennas are used (antennas are not fitted with the 9500 MXC mounting collar), or where dual-polarized antennas are installed for CCDP XPIC operation.
Page 248 Andrew ODU Collar and Polarization Rotator Figure 2-6. Vertical Polarization Horizontal Polarization Timing mark on rotator hub Collar Rotator Timing mark on rotator hub aligned with V on collar aligned with H on collar Vol. III-2-6 Alcatel-Lucent...
Page 249 9500 MXC User Manual Procedure for Radio Waves Rotator The polarization rotator is fixed by three metric Allen-head bolts. To change the polarization of the Radio Waves antenna: 1. Loosen the bolts. Refer to Figure 2-7. 2. Rotate to other end of the slots. Refer to Figure 2-7.
Page 250 ODU Orientation for Vertical or Horizontal Polarization Figure 2-8. Vertical Polarization Horizontal Polarization Waveguide feed head Mounting bolts with captive nuts An ODU should be installed with its connectors facing down. Next step: Direct-Mount ODU Attachment Procedure on page 2-9. Vol. III-2-8 Alcatel-Lucent...
Page 251: Direct-Mount Odu Attachment Procedure
9500 MXC User Manual Direct-Mount ODU Attachment Procedure This topic describes the physical attachment of an ODU to an antenna mounting collar. Related procedures are: • Installing the ODU Lightning Surge Suppressor; refer to Installing Lightning Surge Suppressors on page 2-23. This is only required for ODUs not fitted with an internal lightning surge suppressor.
Page 252: Remote-Mounted Odus
V and H antenna ports using remote mounts. The remote mount clamps to a standard 114.3 mm (4.5 ”) pole-mount, and is common to all frequency bands. Figure 2-9 shows an ODU installed on a remote mount. Remote Mount Figure 2-9. Vol. III-2-10 Alcatel-Lucent...
Page 253: Waveguide Flange Data
ODU and the brass antenna port(s) used on most standard antennas. Where a flexible-waveguide length greater than the standard length in the 9500 MXC accessories list is needed, contact your Alcatel-Lucent service support center. Next steps: •...
Page 254: Remote-Mount Installation Procedure
Installing the Remote Mount The remote mount attaches to a standard 112 mm (4”) pipe mount using two saddle clamps. It can be installed either way up, and with a left or a right offset. Firmly fasten the clamp nuts. Vol. III-2-12 Alcatel-Lucent...
Page 255: Grounding The Odu
Grounding the ODU The ODU must be installed with a lightning surge suppressor. Failure to do so can invalidate the Alcatel-Lucent warranty. Refer to Installing Lightning Surge Suppressors on page 2-23. This procedure applies where the ODU must be directly grounded, as distinct from being grounded via a suppressor support bracket.
Page 256: Odu Grounding Procedure
• For equal loss the attenuation per side is nominally 3.5 dB (3.5 / 3.5 dB), which applies to both the transmit and receive directions, meaning the additional total one-way attenuation compared to a non-protected link is 7 dB. Vol. III-2-14 Alcatel-Lucent...
Page 257: Coupler Installation Procedure
9500 MXC User Manual • For unequal loss the attenuation is nominally 1.5/6.5 dB. They have application on rain-affected bands, 13 GHz and above. When using a coupler to combine two ODUs onto a single polarization the operating channels must be chosen from within the same diplexer option. If the two ODUs are not from the same tuning/diplexer option then interference may occur, resulting in degraded link performance.
Page 258 • Installing the ODU Lightning Surge Suppressor; refer to Installing Lightning Surge Suppressors on page 2-23. • Grounding an ODU; refer to Grounding the ODU on page 2-13 Installing the ODU cable and connectors; refer to Installing ODU Cables and Connectors on page 2-19 Vol. III-2-16 Alcatel-Lucent...
Page 259 9500 MXC User Manual Coupler Fitted to Antenna Figure 2-11. Coupler Installation with ODUs Figure 2-12. 3DB 23063 ADAA - Rev 004 July 2007 Vol. III-2-17...
Page 260: Unused And Disconnected Coupler Ports
A flange-mounted termination is used to absorb the RF energy. They are needed in 1+0 and cascaded coupler applications where some ODU ports are left open/ not attached to an ODU. Terminations are available from Alcatel-Lucent. Vol. III-2-18 Alcatel-Lucent...
Page 261: Installing Odu Cables And Connectors
9500 MXC User Manual Installing ODU Cables and Connectors The ODU cable installation must comply with 9500 MXC requirements. If the cable, suppressors, grounds and weatherproofing are incorrectly installed, the Alcatel-Lucent warranty can be voided. This section includes information on: •...
Page 262: Coaxial Cable Installation Requirements
A recommended crimp tool for the connectors used with the ET 390998 cable is available from Alcatel-Lucent. When removing the jacket Take great care when removing the jacket to keep the outer - all coaxial cable conductor intact.
Page 263: Cable Grounding
9500 MXC User Manual Cable Grounding Ground kits are included in the ODU Cable Kits. For tower/mast installations the ODU cable must be grounded at: • The point where it comes on to the tower from the ODU • The point where it leaves the tower to go to the equipment building •...
Page 264 Install additional cable grounds at not more than 25m (80 ft) intervals if the height of cable on the tower exceeds 50m (165 ft) Lightning surge suppressor Cable ground Cable ground Rack ground bar Cable carrier Master ground bar INU/INUe/IDU Site grounding grid/radials Vol. III-2-22 Alcatel-Lucent...
Page 265: Jumper Cables
A jumper cable is required from the INU/INUe or IDU, to the lightning surge suppressor installed at the building entry. • For the INU/INUe (9500 MXC Node) a 3m jumper cable is included with each RAC, fitted with an SMA male connector at the RAC end and a Type N female at the suppressor end.
Page 266: Internal Odu Surge Suppressor
• Suppressor Installation at the ODU on page 2-29 Internal ODU Surge Suppressor ODUs fitted with an internal suppressor must be grounded using the ODU Grounding Procedure on page 2-14. No other special installation procedure is required. Key benefits of the internal ODU suppressor include: Vol. III-2-24 Alcatel-Lucent...
Page 267: Lightning Surge Suppressor Kit
9500 MXC User Manual • Performance comparable to that of the recommended external suppressors. Complies with IEC 61000-4-5, Class 5 and GR-10890-CORE 4.11, Type 1, 3, 5 & 6. The suppressor supports a multi-strike capability. • More consistent ODU reliability with guaranteed presence of a protection device.
Page 268 Chapter 2. Outdoor Installations BGXZ Surge Suppressor Figure 2-16. Vol. III-2-26 Alcatel-Lucent...
Page 269: Suppressor Installation At Building Entry
9500 MXC User Manual Suppressor Installation at Building Entry This topic describes the installation for the suppressor located at the building-entry end of the ODU cable. If lightning surge suppressors are not fitted, or are fitted incorrectly, the Alcatel-Lucent warranty may be voided.
Page 270: Installing Building Entry Suppressor Procedure
2. Trim the cable from the ODU at the point where the suppressor is to be installed. Terminate the cable with a Type N male connector from the ODU Accessories Kit, and connect to the Type N female connector on the Vol. III-2-28 Alcatel-Lucent...
Page 271: Suppressor Installation At The Odu
9500 MXC User Manual suppressor. 3. Connect the suppressor to the indoor radio unit (RAC or 9500 MXC Terminal) using a jumper cable. Refer to Jumper Cables on page 2-23. 4. Fit one end of the ground wire to the suppressor ground bracket using the nuts and washers supplied.
Page 272 Installation of the Suppressor on the ODU Figure 2-19. Type N connectors must be weatherproofed ODU cable attachement Ground wire for suppressor and ODU Support bracket Suppressor Ground stud Right angle RSSI connector connector Vol. III-2-30 Alcatel-Lucent...
Page 273 9500 MXC User Manual Universal Support Bracket: Vertical Suppressor Installation Figure 2-20. Universal Support Bracket: Horizontal Suppressor Installation Figure 2-21. NOTE: When the support bracket is fitted for horizontal suppressor installation access to the RSSI connector is restricted; a BNC right-angle connector must be used to gain access.
Page 274: Installing A Suppressor With A Support Bracket
2. Set in the alignment shown and firmly hand-tighten. 3. Weatherproof the connection between the right-angle connector and suppressor using the self-amalgamating tape supplied in the suppressor installation kit. Refer to Self Amalgamating Tape on page 2-39. Vol. III-2-32 Alcatel-Lucent...
Page 275 9500 MXC User Manual 4. Partially overlay the amalgamating tape with UV-protecting vinyl tape. 5. Fit the partially weatherproofed suppressor assembly to the ODU and align as shown. 6. Firmly hand-tighten the Type N connector. 7. Complete the weatherproofing of the right angle connector onto the ODU with self-amalgamating tape.
Page 276 10. Fit the support bracket to the suppressor studs and ODU ground stud. Hold in place using the ground stud nut (loosely hand tighten only). 11. Attach the lugged end of the ground wire and secure with the star washers and nuts supplied in the suppressor kit. Vol. III-2-34 Alcatel-Lucent...
Page 277 9500 MXC User Manual 12. Check the positioning of the bracket, carefully adjusting the assembly if necessary, and tighten all nuts. 13. Loop and secure the ground wire before hoisting the ODU into position. 14. Attach the terminated ODU cable to the suppressor and firmly hand tighten.
Page 278 First scrape any paint or oxidation from the tower at the clamping point to ensure there will be good low-resistance contact. 20. Apply protective grease around the ground clamp assembly. Figure 2-22 shows a correct installation. BGXZ Suppressor Installation on an ODU Figure 2-22. Vol. III-2-36 Alcatel-Lucent...
Page 279: Installing A Suppressor Without A Support Bracket
9500 MXC User Manual Installing a Suppressor Without a Support Bracket Procedure: 1. Attach the suppressor to ODU. 2. Attach the ODU cable to the suppressor and firmly hand tighten the Type N connectors. Ensure the cable is first formed (bent to fit) before it is attached to the suppressor.
Page 280: Weatherproofing
On an ODU connector, leave at least two-thirds of the smooth length of the barrel clear of pre-wrap vinyl tape, to ensure the mastic tape has sufficient area of direct grip. Vol. III-2-38 Alcatel-Lucent...
Page 281: Self Amalgamating Tape
9500 MXC User Manual 3. Wrap with mastic tape using a 75% overlay. Where possible, use not less than a 25 mm (1”) attachment onto the primary surface (25 mm past the cable sheath cut, or any pre-wrap). There must be a full seal of mastic tape onto the primary surface for weatherproofing integrity.
Page 282 Chapter 2. Outdoor Installations Vol. III-2-40 Alcatel-Lucent...
Page 283: Chapter 3. Installing The Inu And Inue
Chapter 3. Installing the INU and INUe The INU and the INU expanded (INUe) are the indoor units for the 9500 MXC Node. This chapter includes: • INU/INUe Description on page 3-1 • INU/INUe Installation Requirements on page 3-4 • Installing an INU on page 3-5 •...
Page 284: Front Panel Layout
RAC 30 fitted in slot 1 Mandatory Node Control Card (dedicated slot) Blank Panel Blanking panel fitted to slot 2 RAC 30 RAC 30 fitted in slot 4 DAC 16x 16xE1/DS1 DAC fitted in slot 3 Mandatory fan plug-in (dedicated slot) Vol. III-3-2 Alcatel-Lucent...
Page 285: Power Cable
9500 MXC User Manual Power Cable The power cable is supplied in the IDC Installation Kit. It is supplied with the connector fitted at one end and wire at the other. The cable is nominally 5 m (16 ft), and the wires are 4 mm (AWG 12).
Page 286: Inu/Inue Installation Requirements
The INU/INUe must be installed in the same premises as its dc power supply and be located in the same immediate area (such as adjacent racks or cabinets) as any other equipment that is connected to the same dc power supply. Vol. III-3-4 Alcatel-Lucent...
Page 287: Installing An Inu
Check to ensure that connection of a 9500 MXC system to an existing dc supply does not overload the supply, circuit protection devices and wiring. Where a new dc power supply is to be installed for a 9500 MXC Node, the power supply must be rated to supply: •...
Page 288 Never assume that the supply provided to the pick-up point in a rack is correct. 9500 MXC dc power, IF, tributary, auxiliary and NMS cables are not to be routed with any AC mains power lines. They are also to be kept away from any AC power lines which cross them.
Page 289 The DC power connector can be shorted inadvertently if applied at an angle. Always insert with correct alignment. Next Step The 9500 MXC Node is ready for configuration and antenna alignment. • Refer to Volume IV, Chapter 4, for configuration. • Refer to Volume III, Chapter 5, for antenna alignment.
Page 290: Plug-In Slot Configuration
* Internal (backplane) NMS access is only provided for slots 1 to 6. Do not install DAC 155oM or AUX in slots 7 to 9 if an NMS connection is required in their configuration. Installing or changing out a plug-in is a straightforward process. The Vol. III-3-8 Alcatel-Lucent...
Page 291: Plug-In Installation Requirements
DAC 155oM and AUX, which must only be installed in slots 1 to 6 when they are to be configured to carry/access 9500 MXC NMS, otherwise they can be installed in slots 7 to 9. Dedicated slots The NCC, FAN, and NPC plug-ins have dedicated slots.
Page 292 Never withdraw or insert using attached cables, as damage to the plug-in connector and its PCB attachment can occur. If not complied with, the Alcatel-Lucent warranty may be voided. Hot-swappable Plug-ins are hot-swappable. Removal of an in-service plug-in will interrupt its traffic.
Page 293 9500 MXC User Manual Function/Requirement Priority Details Removing RAC from a When removing a RAC from a powered INU, always the disengage powered INU the RAC from the backplane before disconnecting its ODU cable. Similarly before inserting an RAC, always reconnect the ODU cable before engaging the backplane.
Page 294 When handling a plug-in to or from an antistatic bag, do so at the INU/INUe and only when you are connected to the INU/ INUe via an ESD ground strap. Spare blank panels Keep any removed blanking panels for future use. Vol. III-3-12 Alcatel-Lucent...
Page 295: Chapter 4. Installing The Idu
Chapter 4. Installing the IDU The IDU is the indoor unit for the 9500 MXC Terminal. 9500 MXC Nodes are described in Chapter 3. This chapter includes: • IDU Options on page 4-1 • Power Cable on page 4-2 • IDU Installation Requirements on page 4-2 •...
Page 296: Power Cable
The IDU and its associated dc power supply must be installed in a restricted access area such as a secure equipment room, closet, cabinet or the like. Required Rack Space The IDU requires 44.5 mm (1RU) of vertical rack space and 300 mm rack depth. Vol. III-4-2 Alcatel-Lucent...
Page 297 Loading (60 Vdc maximum). Check to ensure that connection of a 9500 MXC system to an existing dc supply does not overload the supply, circuit protection devices and wiring. Where a new dc power supply is to be installed for an IDU, the power supply must be rated to supply a minimum 5 A.
Page 298: Installing An Idu
9. Connect the blue (or red) wire to -48 Vdc (live), and the black wire to ground/ +ve. The power input is polarity protected. 10. Measure the voltage on the dc power connector. The voltage should be Vol. III-4-4 Alcatel-Lucent...
Page 299 Never assume that the supply provided to the pick-up point in a rack is correct. 9500 MXC dc power, IF, tributary, auxiliary and NMS cables are not to be routed with any AC mains power lines. They are also to be kept away from any AC power lines which cross them.
Page 300 Chapter 4. Installing the IDU Vol. III-4-6 Alcatel-Lucent...
Page 301: Chapter 5. Antenna Alignment
Chapter 5. Antenna Alignment This chapter includes: • Preparation on page 5-1 • Signal Measurement on page 5-2 • Aligning the Antenna on page 5-4 • Main Beams and Side Lobes on page 5-18 Preparation Before aligning antennas ensure: • The ODUs are powered up at both ends of the link. •...
Page 302: Signal Measurement
1. Connect the voltmeter to the BNC connector. Center pin is positive. Use a low voltage range for best resolution, nominally 2.5 Vdc FSD. 2. Adjust antenna alignment until the voltmeter reading is at minimum value. 3. Repeat for the far end of the link. Vol. III-5-2 Alcatel-Lucent...
Page 303: Rsl Measurement Guidelines
RSL, do not use ATPC. RSSI filter bandwidth is not a function of, nor does it affect receiver adjacent channel C/I performance. 9500 MXC complies with relevant ETSI and FCC co and adjacent channel requirements. 3DB 23063 ADAA - Rev 004 July 2007...
Page 304: Aligning The Antenna
Refer to: • Standard Alignment Procedure • Additional Procedures for a Protected Link • Additional Procedures for CCDP XPIC links Vol. III-5-4 Alcatel-Lucent...
Page 305: Standard Alignment Procedure
9500 MXC User Manual Ensure antennas are aligned on the main beam, and not a side lobe. For guidance, refer to the sections Locating the Main Beam on page 5-18 and Tracking Path Error on page 5-19 Ensure ATPC is turned off during the alignment procedure.
Page 306 This procedure details the additional steps required to ensure that all four antennas are in correct alignment and that during the alignment process no unwanted Tx switching occurs. 1. Within the CT > Diagnostics > System/Controls screen check which RAC/ is Tx online, and which is Rx online. Vol. III-5-6 Alcatel-Lucent...
Page 307: Additional Procedures For Ccdp Xpic Links
9500 MXC User Manual • For RACs the default status has the primary RAC as Tx online, and the secondary RAC as Rx online. • For IDU 155o and IDU 20x the default status has the primary IDU as Tx and Rx online.
Page 308 90 degree twist or have a straight waveguide feed but with a polarization rotator in the feedhead. Generally the polarization rotator will act on the outer-most waveguide on the feedhead. Vol. III-5-8 Alcatel-Lucent...
Page 309 9500 MXC User Manual • For convention, if ports are not marked for V and H, it is recommended that the port that has the straight waveguide feed or is connected to the inner-most waveguide at the feedhead is selected as the horizontal antenna feed port.
Page 310 • Links are operating error-free. Where there is potential for interference from other links in the same geographical area, check by turning the far end transmitter(s) off and measuring the local end RSL on both V and H feeds. Vol. III-5-10 Alcatel-Lucent...
Page 311 9500 MXC User Manual 4. Use the cross pole discrimination (XPD) measurement provided in the Performance screen for RAC 40s to measure the actual V and H signal discrimination from each antenna. • Where measured XPDs are better than 25 dB no further adjustment is needed.
Page 312 • Use the CT > Diagnostics > System/Controls screen to check and set online Tx locks. • With an equal-loss combiner either Tx can be locked as the online Tx (The primary designated Tx is the default online Tx). Vol. III-5-12 Alcatel-Lucent...
Page 313 9500 MXC User Manual • Follow the Procedure for Dual Polarized Antennas on page 5-8. • Return the Protected Link controls to Auto/Lock Off on completion. • To check protected operation on each link, refer to Protection Switching on page 1-6, Volume V, Chapter 1. Bear in mind the remote Tx mute conditions detailed in Remote Tx Mute on page 3-123, Volume II, Chapter 3.
Page 314 Regardless of which RAC is online (primary or secondary) all RACs can be accessed to provide RSL/ RSSI/XPD data. Up to four CT screens can be displayed at once. These may be from the same INU (same IP address) or from different INUs (or IDUs). Vol. III-5-14 Alcatel-Lucent...
Page 315 9500 MXC User Manual Antenna 3, and to the secondary RACs connected to antenna 4. 8. Adjust the feedhead skew angle of the primary antenna for maximum XPD on both primary V and H RACs. If the maximums for each are at (slightly) different angles, adjust for a mid-point.
Page 316 • Check the spread of XPDs is similar between both ends of the link, sites X and • Lock all transmitters to secondary and check that all RAC XPDs are similar (nominally with 2 dB) to the XPDs obtained under primary Tx operation. Vol. III-5-16 Alcatel-Lucent...
Page 317 9500 MXC User Manual CCDP Space Diversity Link Antenna Alignment Figure 5-2. Site X Site Y ODU 300s A Primary B Primary A Secondary B Secondary INUe A RAC 40 Slot 3 Slot 1 RAC 40 RAC 40 Slot 4...
Page 318: Main Beams And Side Lobes
Figure 5-3 on page 5-19 is an example of a head-on, conceptual view of the beam signal strength, with concentric rings of side lobe peaks and troughs radiating outward from the main beam. Vol. III-5-18 Alcatel-Lucent...
Page 319: Tracking Path Error
9500 MXC User Manual Indicative head-on signal pattern for a parabolic antenna Figure 5-3. Head-on View Center of main beam provides maximum signal level Outer edge of main beam, 3-10 dB below main beam Trough between main beam and first...
Page 320 DD, or top to bottom along line EE, always ending up with the maximum signal at position 1. Example Tracking Path Signals Centered on the First Side Figure 5-5. Lobe Head-on View of Azimuth and Elevation Signal Levels for Each Track Tracking Paths Centered on the First Side Lobe Vol. III-5-20 Alcatel-Lucent...
Page 321: Volume Iv 9500 Mxc Ct
Volume IV 9500 MXC CT...
Page 323: Chapter 1. 9500 Mxc Ct Introduction
• 9500 MXC CT Auto Version on page 1-8 9500 MXC CT Screens All 9500 MXC CT (CT) screens have the look and feel of a Windows environment. For an example screen. Access to on-screen features and commands is provided by mouse click and/or quick-access key commands.
Page 324 Chapter 1. 9500 MXC CT Introduction With few exceptions a configuration change made in one screen will immediately reflect through to all other affected screens - it is not necessary to click Send to confirm a change made in one screen to see its affect in a related screen or...
Page 325: 9500 Mxc Ct Symbols
CT memorizes the size/ position for primary and secondary. 9500 MXC CT Symbols 9500 MXC CT Logos Throughout CT, standard logos are used to assist 9500 MXC module identification. Refer to Figure 1-3. 3DB 23063 ADAA - Rev 004 July 2007 Vol. IV-1-3...
Page 326 Chapter 1. 9500 MXC CT Introduction Standardized 9500 MXC Logos Figure 1-3. Vol. IV-1-4 Alcatel-Lucent...
Page 327 9500 MXC User Manual 9500 MXC CT Icons Figure 1-4 shows the system severity icons. System Alarm Icons Figure 1-4. Warning Minor Major Critical No Alarms 3DB 23063 ADAA - Rev 004 July 2007 Vol. IV-1-5...
Page 328 Chapter 1. 9500 MXC CT Introduction Figure 1-5 shows problem icons used within CT and their meanings. Problem Icons Figure 1-5. Software configuration problem Plug-in needs replacing Diagnostic or test mode is active Plug-in missing or not the expected type...
Page 329 9500 MXC User Manual 9500 MXC Node Slot Numbering Conventions The 9500 MXC Node INU and INUe icons and slot numbering conventions are detailed in Table 1-1. 9500 MXC INU and INUe Icon and Slot Numbering Conventions Table 1-1. Icon and Slot Numbering...
Page 330: 9500 Mxc Ct Naming Conventions
The auto version feature within CT ensures the CT software version running on your PC automatically matches the version of embedded (system) software installed on 9500 MXC. This avoids the need to hold multiple versions of on your PC, and to select from them when connecting to a 9500 MXC radio.
Page 331 CT to the version of 9500 MXC embedded software, are held within the embedded software set. This means that: • For a new 9500 MXC installation the version of CT supplied in the Setup CD will always match the embedded software of the equipment being installed.
Page 332 Chapter 1. 9500 MXC CT Introduction Vol. IV-1-10 Alcatel-Lucent...
Page 333: Chapter 2. Setting Up 9500 Mxc Ct
Chapter 2. Setting Up 9500 MXC CT This chapter describes how to install 9500 MXC CT and its connection options. The main topics are: • Installing 9500 MXC CT on Your PC on page 2-1 • 9500 MXC CT to 9500 MXC Connection Options on page 2-3 •...
Page 334: Procedure For Installing 9500 Mxc Ct
• TCP/IP installed and configured for LAN operation Procedure for Installing 9500 MXC CT 9500 MXC CT is delivered with an installer file on a Setup CD, supplied as part of the 9500 MXC Installation Kit. To install 9500 MXC CT on your PC: 1.
Page 335: 9500 Mxc Ct To 9500 Mxc Connection Options
There are two PC-to-9500 MXC connection options; 10/100Base-T Ethernet or V.24. To enable 9500 MXC CT access on a new (unconfigured) Node/Terminal a V.24 connection is required at the outset. Once connected, an IP address can be configured, from which point Ethernet access can be used.
Page 336 • The radio must be enabled as a DHCP server. • Your PC must have DHCP enabled (to obtain an IP address automatically). Next Step: • Setting Up A DHCP Ethernet 9500 MXC CT Connection on page 2-9. V.24 A V.24 connection applies to all 9500 MXC radios.
Page 337: Setting Up A Tcp/Ip Ethernet 9500 Mxc Ct Connection
IP address details for Nodes and Terminals, or use a V.24 connection to obtain details of the connected Node/Terminal. If you do not know the IP address of a 9500 MXC Node/Terminal, refer to Using a V.24 Connection to Obtain the Ethernet IP Address on page 2-28.
Page 338: Setting Up Your Pc Tcp/Ip Properties
Introduction Your CT PC must have a LAN-compatible address installed. Each Node/Terminal in a 9500 MXC network has a unique network address, unless connected on a LAN at the same site, so you must change your PC TCP/IP settings each time you physically connect to a different Node/Terminal.
Page 339 Refer to Example - Changing TCP/IP Properties on page 2-8 for guidance. 8. To enable viewing of other 9500 MXC Nodes/Terminals on the network, set the default gateway to be the same as the IP address of the Node/Terminal you 3DB 23063 ADAA - Rev 004 July 2007 Vol.
Page 340 The 9500 MXC you are connecting to has an IP address of 192.168.10.1 and a subnet mask of 255.255.255.0. The subnet mask indicates that the network portion of the IP address is 192.168.10, and that the host portion is 1.
Page 341: Setting Up A Dhcp Ethernet 9500 Mxc Ct Connection
MXC radio). • DHCP-enabled is the default TCP/IP connection option on most laptop PCs. To set up your CT PC to connect to a 9500 MXC Node/Terminal that has the 3DB 23063 ADAA - Rev 004 July 2007 Vol. IV-2-9...
Page 342: Setting Up Your Tcp/Ip Properties For Dhcp
• An industry-standard 10Base-T or 10/100Base-T LAN card installed on your • DHCP enabled within the TCP/IP Properties window on your PC. • DHCP server enabled on the 9500 MXC radio you are connecting to. The DHCP server function is configured in the Configuration > Networking screen.
Page 343: Setting Up 9500 Mxc Ct Connection Using V.24
COM port. With a USB port, an external 3rd party USB-to-serial adaptor is required. Setting up your 9500 MXC CT PC to connect to a 9500 MXC Node or Terminal using V.24 connection involves: • Setting Up a V.24 Connection via a DB-9 Serial COM Port on page 2-12 •...
Page 344: Setting Up A V.24 Connection Via A Db-9 Serial Com Port
Refer to Installing a COM Port Communications Cable Connection: Windows XP. Installing 9500 MXC Modem Driver for Serial COM port: Windows 2000 & 98 To install the V.24/RS-232 modem: 1. From the PC control panel, select >...
Page 345 5. Select Connect using a dial up modem. 6. Select 9500 MXC V.24 Modem 38400bps. 7. Type in an ISP Name or a name for the connection, such as 9500 MXC. 8. Enter any phone number, such as 1234567 (the dial up connection may not work if the phone number is left blank).
Page 346 Installing a COM Port Communications Cable Connection: Windows XP This procedure sets up a communications-cable connection between your CT PC and 9500 MXC. There is no need to first install the 9500 MXC modem driver. To configure the connection: 1. From the PC Control Panel, select >...
Page 347: Setting Up A V.24/Rs-232 Connection Via A Pc Usb Port
9500 MXC User Manual 13. Click OK, OK, Connect, to connect to the 9500 MXC terminal. Refer to Starting 9500 MXC CT on page 2-19. If you are not physically connected to a terminal click Cancel / Exit. 14. The maximum speed must be set for 38400 bps. The network connection and max speed can be checked by going to the Control Panel >...
Page 348 Chapter 2. Setting Up 9500 MXC CT Installing the USB-to-Serial Adapter To install the USB-to-serial adapter: 1. Plug the USB-to-Serial adapter into a USB port on your computer. The operating system detects the device and displays a Found New Hardware Wizard.
Page 349 . Click it from a list Next 4. Select and browse to the 9500 MXC Installation Kit CD to select Have Disk the 9500 MXC V.24 Modem Driver.inf file. Click Open 5. In the Install from disk window, select the CDROM drive and click 6.
Page 350 5. In Network Connection, select and click Dial-up connection Next 6. In Select a Device, select the previously installed 9500 MXC V.24 modem driver, and click Next 7. In Connection Name, enter a name, such as 9500 MXC, and click Next 8.
Page 351: Starting 9500 Mxc Ct
For a V.24 connection, a dial-up connection from your PC to 9500 MXC must first be established. Refer to Setting Up 9500 MXC CT Connection Using V.24 on page 2-11. For information on the connecting cable, refer to PC to 9500 MXC Cabling and Connectors on page 2-19.
Page 352: Using A Tcp/Ip Connection
LAN as the terminal you are connecting to. 3. Open the CT start-up screen. Refer to Figure 2-1 on page 2-21. 4. Enter the IP address of the target 9500 MXC radio in the Connect-to line, or select from the list.
Page 353: Using An Ethernet Dhcp Connection
This procedure applies to a 9500 MXC radio that is DHCP server enabled. 1. Ensure your PC is configured to obtain an IP address automatically. 2. Connect your PC to the 9500 MXC 10/100Base-T NMS port of the radio you wish to connect to.
Page 354: Using A V.24 Dial Up Connection
3. Click (Win. XP). Dial (Win. 2000/98) or Connect 4. Connection to 9500 MXC is confirmed by the connection icon in the System Tray on your PC (lower right corner). Connection Icon 5. Open the CT start-up screen. Refer to Figure 2-2 on page 2-23.
Page 355: Connection Process
When Connect is clicked, CT auto-versioning is immediately activated to ensure automatic version matching of CT software to the system software installed on 9500 MXC. Auto version progress is indicated above the connection status bar, which may show in rapid succession: •...
Page 356: Entering A Username And Password
Chapter 2. Setting Up 9500 MXC CT • Starting updated 9500 MXC CT session... For information on 9500 MXC CT Auto Version, refer to 9500 MXC CT Auto Version on page 1-8. Additionally, if access to the selected Node/Terminal has been Password protected, a password window is displayed on Connect.
Page 357: Lost Password Procedure
Read/write access. An engineer can send changes to 9500 MXC and update software, but cannot change password or security settings. operator Read only. An operator cannot send changes to 9500 MXC or update software, or change password or security settings. Procedure To login to 9500 MXC: 1.
Page 358: Connection Exceptions
4. Alcatel-Lucent will respond with a reset key file, which for an email response, should be saved to a file on your PC.
Page 359: Checking V.24 Access
If rebooting is not an option because of disruption to service, try the following: • With the V.24 cable installed, click on the 9500 MXC shortcut to open the Connect 9500 MXC window, select Properties > Networking > Internet protocol (TCP/IP) >...
Page 360: Using A V.24 Connection To Obtain The Ethernet Ip Address
Chapter 2. Setting Up 9500 MXC CT Procedure for Checking and Entering a Changed V.24 IP Address 1. Stay connected via the maintenance cable. 2. Right-click the dial-up connection icon, on your PCs system tray. Connection Icon The dial-up connection menu options are displayed.
Page 361: Next Step
3. Log-off and reconnect your PC for an Ethernet connection 4. Enter the IP address from step 2, and click Connect. Next Step Table 2-3 directs you to relevant sections of the 9500 MXC CT volume. Reference Topics Table 2-3.
Page 362 Chapter 2. Setting Up 9500 MXC CT Vol. IV-2-30 Alcatel-Lucent...
Page 363: Chapter 3. Installation And Configuration Process
Chapter 3. Installation and Configuration Process 9500 MXC CT provides the tools needed to install and commission a link between: • 9500 MXC Nodes • a 9500 MXC Node and a 9500 MXC Terminal • 9500 MXC Terminals From new each end of the link must be locally configured. Once a link has been established, both ends can be re-configured from one end providing the re-configuration does not dis-establish the link connection.
Page 364: Essential Information
(saved) on clicking the Send button. Viewed Data All data viewed in 9500 MXC CT screens is read from the CompactFlash card, except that which has changed since the last save action (Send button clicked). Vol. IV-3-2...
Page 365 Capacity and bandwidth/modulation options plus frequency range, Tx/Rx spacing, Tx high/low and Tx power limits are read from the CT connected RAC/ ODU (9500 MXC Node), Radio/ODU (9500 MXC Terminal). It is not possible to set parameters outside as-read limits.
Page 366: 9500 Mxc Ct Menus
• For the 9500 MXC Node the card is fitted in the NCC. • For 9500 MXC Terminals it is fitted through a slot in the rear of the IDU. The CompactFlash allows the configuration to be held independent of any Vol.
Page 367 When clicked, a Send window with a cancel option is displayed and will remain open until the send process has been completed. Figure 3-1 shows the menu-bar menus for a 9500 MXC Node. 3DB 23063 ADAA - Rev 004 July 2007...
Page 368 Chapter 3. Installation and Configuration Process 9500 MXC CT Menu-Bar Menus Figure 3-1. Vol. IV-3-6 Alcatel-Lucent...
Page 369: Procedure Overview For A New Installation
CT. 3. Connect your CT PC to 9500 MXC and open CT to the Start Up screen: • Connect using the supplied V.24 cable. (In the event the IP address of the radio is known, an Ethernet connection should be used to take advantage of its superior speed).
Page 370 Chapter 3. Installation and Configuration Process 4. Installation: Licensing 9500 MXC Node 9500 MXC Terminal Within 9500 MXC CT, select > Applies only to: Installation Licensing to view the licensed capabilities for the Node. • The IDU ES for Ethernet throughputs above the base 50 If licensed capabilities are not exceeded, or will not be Mbps license.
Page 371 9500 MXC User Manual 7. Configuration: Plug-ins 9500 MXC Node 9500 MXC Terminal Select > to view settings for Select > to view settings for the Configuration Plug-Ins Configuration Plug-Ins the plug-in. Terminal modules. Edit, if required, using the settings specified in the Edit, if required, using the settings specified in the installation datapack.
Page 372 Alarm Actions Alarm I/O mapping (if required). I/O mapping (if required). Refer to 9500 MXC Node and Terminal Alarm Refer to 9500 MXC Node and Terminal Alarm Actions on Actions on page 11-1 details. page 11-1 details. 12. Configuration: Date/Time...
Page 373: Configuration Changes To An Existing Installation
9500 MXC User Manual 16. Repeat steps 2 to 16 for the other end of the link. 17. Record the RSL at both ends of the link and check values against the expected RSLs in the installation datapack. 18. Complete a BER test. Loopbacks are available within CT under Diagnostics >...
Page 374 Chapter 3. Installation and Configuration Process Vol. IV-3-12 Alcatel-Lucent...
Page 375 Chapter 4. Licensing The information in this chapter applies to 9500 MXC Nodes, IDU ES, and to IDU 20x. For a 9500 MXC Node: • A license “unlocks” over-air capacity for RAC/ODUs installed in an INU or INUe. License levels allow incremental capacity selection up to100xE1 (200 Mbps Ethernet), 127xDS1 (200 Mbps Ethernet), or 2xSTM1/OC3 (300 Mbps Ethernet), for each RAC/ODU.
Page 376: Chapter 4. Licensing
This card inserts into the side of the NCC plug-in, or into the rear of an IDU. The CompactFlash also stores the configuration and support data. A CompactFlash card can be moved to another 9500 MXC Node or Terminal, which acquires the licensed capability and configuration data from the previous Node/Terminal (Terminals must be compatible).
Page 377: Idu Es License
9500 MXC User Manual Capacity Upgrade When selecting capacities for individual RAC/ODUs, it is important to ensure the maximum throughput capacity for a Node is not exceeded, and that the mix of capacities is backplane compatible. Otherwise the requested upgrade will be signalled as invalid.
Page 378: Idu 20X License
28xDS1 32xDS1 ‘Up-to’ means that an IDU 20x can be configured for any capacity less than or equal to its maximum licensed capacity. For example, a 40xE1 license also supports configuration of 5xE1, 10xE1, 20xE1, or 32xE1. Vol. IV-4-4 Alcatel-Lucent...
Page 379: License Configuration Screen
Installation Licensing shows a typical window. It provides information on the license, the licensed maximum per slot, license status, and management of a license upgrade. Typical Licensing Screen for 9500 MXC Node Figure 4-1. Item Description Indicates the license serial number and license status.
Page 380 Select a new license. Click to select and load a new license. Refer to Upgrading a License. NOTE: Where the configured capacity exceeds the licensed capacity a configuration not supported alarm and a license violation alarm is raised. These are major alarms. Vol. IV-4-6 Alcatel-Lucent...
Page 381: Upgrading A License
Upgrading a License This section describes the process required to secure an upgraded license from Alcatel-Lucent. It addresses the steps needed to confirm the required new license capacity, the upgrade price, and the purchase and delivery mechanisms. It is a software-only process. The upgrade to be loaded into the CompactFlash is provided as a file by email or on a CD.
Page 382 Procedure for Loading a License To load an upgrade license: 1. On your 9500 MXC CT PC, copy the new license file into the default 9500 MXC CT program folder C:\Program Files\9500 MXC CT or load it into a new license sub-folder such as, C:\Program Files\9500 MXC CT\License.
Page 383 9500 MXC User Manual If the required license is located in another directory, click the Change button to display your PC browser, and navigate to the required folder. Only the license (or licenses) matching the serial number of the Node/Terminal are visible.
Page 384 Chapter 4. Licensing Vol. IV-4-10 Alcatel-Lucent...
Page 385: Chapter 5. Reports
Alcatel-Lucent service personnel in troubleshooting. • When reporting a problem on a 9500 MXC Node or Terminal to an Alcatel-Lucent support center you may be asked to save and forward this file.
Page 386: Reports Screen
Once saved to your PC the report can be opened for viewing and editing in Excel. There are both defined, and not-defined entries: Defined Entries Defined entries are those which have data read into them from the Node/ Terminal. Vol. IV-5-2 Alcatel-Lucent...
Page 387: Helpdesk Data File
If a software reset is performed (see Advanced Management on page 15-71 of Diagnostics, Volume IV, Chapter 16) the helpdesk data file is automatically saved to a default folder on your CT PC at C:\Program Files\9500 MXC CT\Reset Logs\. For support center locations refer to the Contact Information in the introductory pages.
Page 389: Chapter 6. Node And Terminal Information
Chapter 6. Node and Terminal Information The Information screen provides user configurable fields for terminal and site name, site grid, contact details and notes. Refer to Figure 6-1. Information Screen Figure 6-1. The terminal name and site name set in this screen are displayed in the status bar on all screens.
Page 391: Chapter 7. Node And Terminal Plug-Ins
Chapter 7. Node and Terminal Plug-ins The plug-ins screen is used for Node and Terminal configuration. Table 7-1 lists module references used within the screens. Module References for Node and Terminal Table 7-1. Function Node/Terminal Module References Radio LINK or RING. A LINK comprises one RAC/IDU for a non-protected link, two for a protected link.
Page 392: Plug-Ins Screens
For the Terminal, the Plug-in screen opens to the Link module. Click the Plug-in line to display a submenu for other plug-ins. Figure 7-1 on page 7-2 shows an example submenu for the 9500 MXC Node. Clicking on any plug-in line within the submenu displays its configuration screen. Although the NCC and FAN can be selected, they are not CT configurable.
Page 393: Link Configuration
For a 9500 MXC Node, the Link/Ring plug-ins screen supports configuration of capacity, modulation/bandwidth, frequency, TR spacing, Tx power, and ATPC. For a 9500 MXC Terminal, the screen support is identical to that provided for the Node, dependent on Terminal type.
Page 394: Protected Links And Rings
Includes example screens for protected configurations. • Protection Settings on page 7-18. With a 9500 MXC Node there is automatic synchronization of RAC settings depending on the protection option, such that the secondary RAC is synchronized to the primary, or West with East in the case of a ring.
Page 395: Link/Ring Configuration Procedure
9500 MXC User Manual Polarization Settings Panel Figure 7-2. Co-channel links can be hot-standby or diversity protected. Refer to Figure 7-6 on page 7-17 for an example hot-standby protected screen. Link/Ring Configuration Procedure This procedure applies to non-protected, hot-standby, diversity, and ring links.
Page 396 • Higher capacity for the same modulation rate and bandwidth. Shows the bandwidth / modulation options for the selected capacity. Click to select. • A triangle icon indicates an obsolete modem setting. Vol. IV-7-6 Alcatel-Lucent...
Page 397 9500 MXC User Manual Item Description Path settings window: • Set Tx and Rx frequencies, Tx power. • Provides an ATPC option. • Indicates Tx power (measured). The displayed Tx Frequency Range, Tx high or Tx low, and the choices of Tx/ Rx spacing are read from the installed ODU.
Page 398 Legacy RAC 40 (SW version 3.3 or earlier) at the other end of the link. Only the Standard modem profile is supported and both ends of the link. With 4.0 SW and later a capability is provided to support Legacy and Standard modem profiles. Vol. IV-7-8 Alcatel-Lucent...
Page 399 9500 MXC User Manual Item Description Selection of Auto (default), Standard or Legacy is provided in the RAC 40 modem profile panel in the RAC 40 Plug-ins screen. See below. These selection options are designed to support RAC 40 to RAC 40 operation during SW upgrades (one end is upgraded before the other): •...
Page 400 • For a protected Node link, two RACs are displayed within one Link or Ring module. RACs are labelled primary and secondary for a hot standby or diversity link, or east and west for a ring configuration. Vol. IV-7-10 Alcatel-Lucent...
Page 401 9500 MXC User Manual • For a protected Terminal link, the primary and secondary Terminals are displayed on separate screens. • For a protected Node link, the degree of synchronization between RACs for frequency, modulation, Tx power and ATPC settings depends on the type of protection selected.
Page 402 • For all Node protected configurations except Ring, the selected bandwidth / modulation is common to both RACs. 9500 MXC Node modulation options are QPSK, 16QAM, 32QAM, 64QAM, 128QAM or 256QAM, but in the Bandwidth/Modulation menu only the modulation options appropriate to the selected capacity and RAC type installed are presented.
Page 403 9500 MXC User Manual • Rx frequency can be direct entered if preferred, whereupon the Tx frequency is set automatically based on the selected Tx/Rx spacing. Again, such selection is only be permitted within the constraints of the allowable frequency steps and Tx/Rx Spacing.
Page 404: Protection Options
Chapter 7. Node and Terminal Plug-ins Protection Options Table 7-2 describes 9500 MXC protection options. • The Node supports all options. • Paired IDU 155o and IDU 20x Terminals support hot standby or space diversity. Before configuring a protected LINK or RING, the protection primary/secondary pairings must first be established in the Protection screen.
Page 405 9500 MXC User Manual Example Plug-ins Screens for Protected Options The displayed data and setting options depends on the type of protection selected in the Protection screen. The larger size of the ring protection and frequency diversity screens means they open with scroll bars.
Page 406 East and West links are independently set for capacity and bandwidth/ modulation. Path settings are independently set for the East and West links. Modem profile settings are confirmed for both RACs. The Protection Settings Panel simply confirms that ring protection has been set. Vol. IV-7-16 Alcatel-Lucent...
Page 407 9500 MXC User Manual Example Plug-ins Screen for a Co-Channel Hot-standby Link Figure 7-6. Standard Standard 15.1 Standard Standard Item Description Module shows a hot-standby protected link using RAC 40s in slots 2 & 5, with RAC 2 the primary RAC and RAC 5 the secondary.
Page 408: Protection Settings
RACs. The entered data is purely informational; it does not impact operation. For protected co-channel operation: - ATPC must not be used. - An equal-loss coupler must be used. - The co-channel RACs must be set for the same capacity and modulation. Vol. IV-7-18 Alcatel-Lucent...
Page 409: Coupler Losses
9500 MXC User Manual Synchronized Node Protection Settings Synchronized RAC Protection Settings Table 7-3. Protection Type Synchronized RAC Settings Hot Standby Frequency, Capacity, Modulation, Tx Power, ATPC Space Diversity Frequency, Capacity, Modulation, Tx Power, ATPC Frequency Diversity Capacity, Modulation Ring Protection...
Page 410: Atpc Guidelines
ATPC control. ATPC Operation ATPC in 9500 MXC is based on two monitored values, Receive Signal Strength (RSL) and Signal to Noise Ratio (SNR). Each 9500 MXC terminal transmits information about its RSL and SNR levels to its partner terminal.
Page 411 9500 MXC User Manual • "If the RSL value is within range, but the SNR is low, then the transmit power is increased until the SNR is within the specified range. • ATPC power changes can occur at a rate of 6 dB/second to provide compensation for rapid fading conditions.
Page 412 Set the fade margin for the remote end Calculated remote end fade margin RSSI filter bandwidth is not a function of, nor does it affect receiver adjacent channel C/I performance. 9500 MXC complies with relevant ETSI and FCC co and adjacent channel requirements. Vol. IV-7-22 Alcatel-Lucent...
Page 413 Under normal operating conditions the Target Remote Fade Margin and the Remote Fade Margin should indicate within 2 dB of each other. Note: 9500 MXC compensates for fades of up to 6 dB per second. 3DB 23063 ADAA - Rev 004 July 2007 Vol. IV-7-23...
Page 414 3 dB to 6 dB below the Detected Tx Power. This setting will safe-limit the minimum in the event the fade conditions lead to rapid and large Tx power movement. 8. To commit the configuration, click Send Vol. IV-7-24 Alcatel-Lucent...
Page 415: Dac/Tributary Configuration
9500 MXC User Manual DAC/Tributary Configuration For a 9500 MXC Node the DAC provides the link between the user interface and the TDM backplane. Different DACs provide NxE1/DS1, NxE3/DS3, NxSTM1/ OC3, or Ethernet 10/100/1000 interfaces. E3/DS3 and STM1/OC3 DACs may be paired to provide redundancy in the event of a DAC failure.
Page 416: Naming
Tributary Protection (TT) • ‘Y’ cables connect the paired DACs/IDUs to customer equipment. • In the Rx direction (from the customer) both DAC/IDUs receive data, but only the online Rx DAC/IDU sends this data to the bus/radio. Vol. IV-7-26 Alcatel-Lucent...
Page 417 • In the transmit direction both DAC/IDUs send data to customer equipment, and the customer equipment switches between these two ‘always on’ tributaries. • TA protection can also used where two 9500 MXC INU/INUes are trib-interfaced using protected DACs, or where two pairs of protected IDUs are trib interfaced, but doing so will reduce the level of protection on offer compared to TT protection (Y cables).
Page 418: Dac 16X, Dac 4X And Idu E1/Ds1Trib Configuration
Chapter 7. Node and Terminal Plug-ins DAC 16x, DAC 4x and IDU E1/DS1Trib Configuration For 9500 MXC Node, this section describes DATA > DAC 16x and DAC 4x tributary configuration. For 9500 MXC Terminal, this section describes DATA > DAC E1/DS1 tributary configuration.
Page 419 9500 MXC User Manual Item Description Tributary Lines user-defined entries: • Commissioned. Configured tribs should be ticked as commissioned. When commissioned, LOS alarms are raised if LOS is detected, and AIS alarms are raised if AIS is detected. • Name. Each trib can be individually named/identified.
Page 420 It is recommended the trib name has the same name as its circuit, which is entered in the Circuits screen, or include a reference to it in the circuit name, so there is an easy association of trib and circuit names when setting a Circuit Loopback for a trib BER test. Vol. IV-7-30 Alcatel-Lucent...
Page 421: Dac 3Xe3/Ds3M Configuration
9500 MXC User Manual 6. Select the required tributary impedance/encoding. • For an E1 Tributary Type selection, the impedance options are 75 ohm unbalanced or 120 ohms balanced. • For a DS1 Tributary Type selection options are presented for encoding and tributary line length.
Page 422 Link to circuits screen to select backplane bus type. Icons indicate trib in/out status. Mouse-over for tooltip support. The example screen shows an LOS alarm on Trib A. Fill Selection sets all selected (high-lighted) tribs to the same setting as the top-most selected trib. Vol. IV-7-32 Alcatel-Lucent...
Page 423 9500 MXC User Manual Procedures for DAC 3xE3/DS3M 1. From the Plug-ins screen, select the required module. 2. Select the required Mode: 3xE3/DS3, E13/M13 Multiplexer, or Transparent Procedure for 3xE3/DS3 Mode Native E3 is not a supported RAC capacity (RAC 30v3, RAC 3X, RAC 40). Where E3 tribs are required, select the E13 multiplexer mode.
Page 424 Rename, and typing. The default name is ‘unnamed’. 6. Commit the configuration by clicking Send Next Step: Go to the Circuits screen to configure circuit cross-connects. Refer to Procedure for Configuring Circuits - Traffic on page 9-9, Volume IV, Chapter 9. Vol. IV-7-34 Alcatel-Lucent...
Page 425 9500 MXC User Manual Procedure for 34 Mbps Transparent 1. Select the E3 Transparent mode. 2. Check/set the Required Bus Type. For the E3 Transparent mode an E1 backplane bus is required. If not set correctly, the Required Bus Type displays a warning icon.
Page 426: Dac 155O, 2X155O And 2X155E Configuration
• DAC 2x155e. Provides two G.703 electrical STM1, 75 ohm unbalanced, BNC interfaces. For 9500 MXC IDU 155o this section describes configuration of its STM1/OC3 single mode SC optical interface. The receive-level range is -31 dBm (max sensitivity) to -7 dBm (max input power). The transmit-level range is Min -15 dBm to Max -8 dBm (as for DAC 155o).
Page 427 9500 MXC User Manual Typical DAC 2x155o Plug-ins Screen Figure 7-9. Item Description Tributary type is fixed for STM1/OC3. Link to circuits screen to select backplane bus. Bus type must be set to STM1. Tributary Lines. User-defined entries for: • Commissioned. Configured tribs must be ticked as commissioned. When commissioned LOS alarms are raised if LOS is detected.
Page 428: Dac 155Om Configuration
6, of the INUe. This does not apply to the INU; any option slot may be used. DAC 155oM Screens Figure 7-10 shows a typical Line Interface screen for the DAC 155oM. Figure 7-11 on page 7-40 shows the corresponding Backplane Ports screen. Vol. IV-7-38 Alcatel-Lucent...
Page 429 • Internal selects an internally generated clock source. NMS transport. Select between None, RSOH or MSOH. When a DAC 155oM link is installed in a 9500 MXC SDH ring, MSOH would normally be used. Signal degrade threshold. Select between the BER default of 10...
Page 430 Indicates the optical line transceiver type installed, short or long range. Typical DAC 155oM Bus Ports Screen Figure 7-11. Item Description Select between E1 or DS1 backplane mapping. The same selection must also be set as the backplane bus type in the Circuits screen. Vol. IV-7-40 Alcatel-Lucent...
Page 431 9500 MXC User Manual Item Description Ports field. Scroll down to view all ports for: • Tributary mapping. See item 3. • Commissioned. Configured tribs must be ticked as commissioned so that: • AIS, RDI, LOP, LOM, RPSLM alarms are detected, and •...
Page 432 Internal Reference and the other to Recovered 4. Use the Line Tributaries field to enter commissioned/uncommissioned, port name, and signal label data for the STM1/OC3 tributary. • Use the commissioned tick-box to set tributary port status: Vol. IV-7-42 Alcatel-Lucent...
Page 433 9500 MXC User Manual Where the tributary is Where the tributary is uncommissioned commissioned • LOS alarms are suppressed • Trib traffic is enabled • AIS alarms are suppressed • LOS alarm is raised if LOS is detected • At the optical interfaces the output is disabled •...
Page 434 NMS must be 9500 MXC. The selection options are: • None. No provision for 9500 MXC NMS transport is provided on the optical interface. • Use RSOH. 9500 MXC NMS data is assigned to the Regenerator Section Overhead.
Page 435 While TVT uses the same 010 value as bit asynchronous (V5 bits 5-7), it is a separately identified mode on compliant muxes. - Where Ethernet data is transported over a 9500 MXC PDH network to an SDH core and the SDH core network muxes do not support TVT...
Page 436: Dac Es And Idu Es Configuration
MXC DAC ES to SDH mux Ethernet LAN card). - The TVT mode is not compatible with byte synchronous mapping, though if a byte synchronous payload is injected into the 9500 MXC network through a DAC 155oM, it should be configured for TVT to try to preserve the byte alignment.
Page 437 9500 MXC User Manual Typical DAC ES Configuration screen Figure 7-12. Item Description Transport Channel Capacity: Select an E1 or DS1 channel type then one or both channels (C1 or C2) and the capacity per channel, where each E1 selection supports 2.048 Mbps, and each DS1 supports 1.544 Mbps.
Page 438 The main window displays three option tabs: • Configuration. This is the default window. • Priority Mapping. Use to select the priority mode, priority level, and priority mapping. • VLAN Tagging. Not applicable to DAC ES / IDU ES. Vol. IV-7-48 Alcatel-Lucent...
Page 439 TDM data, it is not transported over TDM. 9500 MXC incorporates a universal modem design that does not distinguish between the type of data to be transported, Ethernet or TDM, with the result that when 9500 MXC is configured for Ethernet data, or Ethernet and TDM data, the full configured capacity is available for user throughput.
Page 440 C2 may be used to support two star or ring links where each channel is assigned to its own RAC (or RAC and DAC 155oM). It is particularly applicable to ring networks using 9500 MXC ring-wrap protection, with one channel assigned to the east, the other to the west.
Page 441 IP ring where alternate-path protection is provided by an external RSTP switch. Mixed Mode Figure 7-14. Transparent mode is used where 9500 MXC ring-wrapping provides the protection mechanism. Mixed mode is used where an external RSTP switch provides the protection mechanism.
Page 442 : Sets the port priority. The options are high, medium high, 5.5 Priority medium low, and low. To change, select from the priority menu. Each port can be prioritized in this way. • This prioritization only has relevance where two or more ports use a common channel. Vol. IV-7-52 Alcatel-Lucent...
Page 443 9500 MXC User Manual • Ports with a higher priority have their traffic accepted by the queue controller ahead of traffic from lower priority ports on a 8:4:2:1 weighted basis where, for example, 8 high priority packets will be sent for every one low priority packet.
Page 444 The default mode is Port Default. Click on the Priority Mode box to view and select from the mode menu. A mode selection applies to all ports. Refer to Figure 7-16. DAC ES Priority Mapping Window Figure 7-16. Item Description Priority Mode. Select from the drop-down menu. Vol. IV-7-54 Alcatel-Lucent...
Page 445 9500 MXC User Manual Item Description Priority Table. Presents the priority mapping used to convert the 8 priority levels of 802.1p and the 63 levels of DiffServ to the 4 levels supported by the DAC ES priority stack: high, medium high, medium low, and low.
Page 446 • To return mapping to default, click Set Defaults. 11. To commit the configuration, click Send Next Step: Go to the Circuits screen to configure circuit cross-connects. Refer to Procedure for Configuring Circuits - Traffic on page 9-9, Volume IV, Chapter 9. Vol. IV-7-56 Alcatel-Lucent...
Page 447: Dac Ge Configuration
• Port and QoS options • Flow control (802.3x) • Jumbo frames to 9600 bytes With the DAC GE one 9500 MXC Node supports maximum Ethernet bandwidth assignments of: • 204 Mbps with an NxE1 / 2.048 Mbps backplane • 196 Mbps with and NxDS1 / 1.544 Mbps backplane •...
Page 448 E1 (2.048 Mbps), DS1 (1.544 Mbps), or STM1 (155 Mbps) circuits. Select mode of operation; Transparent, Mixed or VLAN. Where layer 2 link aggregation is required select from the Transparent mode options. Vol. IV-7-58 Alcatel-Lucent...
Page 449 9500 MXC User Manual Item Description Transport Channel Mode supports selection of the fast-link detection mechanism used to enable RWPR-enhanced RSTP and layer 2 link aggregation. • Rapid Failure Detection and Protection should be selected when there is a DAC GE at both ends. Both DAC GEs must be with SW release 3.6 or later.
Page 450 TDM data, it is not transported over TDM. 9500 MXC incorporates a universal modem design that does not distinguish between the type of data to be transported, Ethernet or TDM, with the result that when 9500 MXC is configured for Ethernet data, or Ethernet and TDM data, the full configured capacity is available for user throughput.
Page 451 9500 MXC User Manual • DAC 155oM supports fiber link capacities to 129 Mbps for both Nx 2 Mbps or Nx 1.5 Mbps capacity types. RAC modulation/bandwidth and Node license must support the channel capacity selected within the DAC GE plug-ins screen.
Page 452 300 Mbps links. Note that on the partner link, link aggregation is not configured, but Link Status Propagation should be enabled. More information: See Link Aggregation on page 7-76, and Link Status Propagation Operational Characteristics on page 7-81. Vol. IV-7-62 Alcatel-Lucent...
Page 453 9500 MXC User Manual Transparent Mode with C1, C2 and P1 Aggregation Figure 7-20. • supports a two-channel LAN/broadcast solution where P1-C1 Mixed Mode provides dedicated transport for port 1 traffic. A second transparent, broadcast mode connection is provided with ports 2, 3 and 4 and channel C2 interconnected.
Page 454 • Rapid Failure Detection supports RWPR-enhanced RSTP and layer 2 link aggregation. Select this option where the DAC GE at the far end only displays a tick-box option for Rapid Transport Channel Failure Detection. (The far end DAC GE is operating with SW release 3.4 or 3.5). Vol. IV-7-64 Alcatel-Lucent...
Page 455 9500 MXC User Manual • Rapid Failure Detection and Protection supports RWPR-enhanced RSTP, layer 2 link aggregation and physical (layer 1) link aggregation. Select this option where the DAC GE at the far end also displays this option. Linked DAC GEs must have the same encoding option selected.
Page 456 DAC GE/ES link. Maximum Frame Size sets the maximum frame size that can be accepted at the determines the Maximum Transmission Unit (MTU), switch interface. In turn it which determines the largest datagram than can be transmitted without it Vol. IV-7-66 Alcatel-Lucent...
Page 457 9500 MXC User Manual being broken down into smaller units (fragmented). The MTU should be larger than the largest datagram you wish to transmit unfragmented • The setable frame-size range is 64 to 9600 bytes, however it should not be set above 7500 bytes for bi-directional traffic.
Page 458 • Enabling RSTP operation on required channels/ports. • Supporting selection of a root switch (in conjunction with other DAC GEs in the RSTP network. • Supporting selection the most efficient path (shortest/fastest) to/from the root switch. Vol. IV-7-68 Alcatel-Lucent...
Page 459 9500 MXC User Manual RWPR Setting Window Figure 7-24. 10.1 columns mirror the function provided in the Basic Port, Type and Enable Port settings except that transport channels C1 and C2 are included. A port must be enabled to allow traffic flow. Channels are auto enabled based on the Channel C1 and/or Channel C2 capacity selection.
Page 460 Node/DAC GE. Bridge ID is a unique identifier for the DAC GE switch function. The most significant bits are occupied by the bridge priority setting, the remainder by the switch MAC address. Vol. IV-7-70 Alcatel-Lucent...
Page 461 9500 MXC User Manual • If DAC GEs are configured for the same priority value, or left as default, the DAC GE with the lowest MAC address becomes the root switch. Example Ring with RWPR Settings Figure 7-25. DAC GE...
Page 462 802.1p VLAN priority tags or IP DiffServ priority values. Port priority settings are made per-port in the Priority column in the Configuration > Basic Setting window. Refer to Step 6.5. • 802.1p provides prioritization based on the three-bit priority field of the Vol. IV-7-72 Alcatel-Lucent...
Page 463 9500 MXC User Manual 802.1p VLAN tag. DAC GE maps each of the possible eight priority tag values into a four-level (2-bit) priority field. Refer to Table 7-8 for default mapping assignments. • DiffServ provides prioritization based on the six bits of the IP packet DiffServ or Type of Service byte.
Page 464 LAN or VLAN and to assign a priority on its traffic. In this way up to four separate LANs (ports 1 to 4) can be carried as virtual LANs (VLANs) on a single 9500 MXC radio/fiber trunk; 9500 MXC acts both as an edge switch and as the radio trunk link to the core network.
Page 465 9500 MXC User Manual DAC GE VLAN Tagging Screen Figure 7-27. Item Description A name (if required) is entered in the DAC GE Configuration screen. VLAN Mode. Select a mode from the drop-down menu. A description for each selection is provided at the bottom of the screen.
Page 466: Link Aggregation
• To provide a similar level of redundancy without aggregation, hot-standby or diversity protection is required, but with such protection the standby equipment is not used to pass traffic. Two modes of link aggregation are supported by DAC GE, layer 2 and layer 1. Vol. IV-7-76 Alcatel-Lucent...
Page 467 9500 MXC User Manual • Layer 2 (L2) link aggregation uses source and/or destination MAC address data in the Ethernet frame MAC/LLC header. It provides excellent load balancing between the physical links under normal LAN traffic densities i.e. where there are multiple concurrent sessions between different MAC source and destination addresses.
Page 468 When a link fails, all traffic from the failed link is recovered over the remaining link, or links. If it is to more than one link, aggregation keying applies an equitable split between the links. Vol. IV-7-78 Alcatel-Lucent...
Page 469 9500 MXC User Manual When a failed link is returned to service, aggregation keying restores load sharing across all links. Figure 7-30 illustrates a 300 Mbps LAN connection over two aggregated 150 Mbps links. • The aggregation process ensures that any one traffic stream is only transported over one link.
Page 470 Whether there is one, a few or many concurrent sessions, traffic is always split between the links based on the configured capacity of the links. In the event a link is lost, its traffic is assigned to the remaining link. Vol. IV-7-80 Alcatel-Lucent...
Page 471: Link Status Propagation Operational Characteristics
9500 MXC User Manual 300 Mbps L1 Link Aggregation: Two 150 Mbps STNM1 Links Figure 7-32. DAC GE C1 port 1 Link 1 to link 1 port 1 DAC GE 150 Mbps 300 Mbps 150 Mbps DAC GE C1 port 2...
Page 472 - it should no be enabled on the DAC GE that is hosting the aggregation function. Example A: P1 & C1 are uniquely related, so link status propagation can be enabled. Vol. IV-7-82 Alcatel-Lucent...
Page 473 9500 MXC User Manual Example B: P1, P2 & C1 are not uniquely related, so link status propagation is not applicable. Example C: P1 & C1 are uniquely related. P2 & C2 are uniquely related. Link status propagation is applicable and operates simultaneously and independently.
Page 474: Aux Configuration
• The Data option supports transport of 3rd party synchronous and asynchronous data over a 9500 MXC network. • The NMS option allows 9500 MXC NMS to be ported to a 3rd party network for transport to a remote 9500 MXC node or network. This feature is not supported by 9500 MXC Terminals.
Page 475: Data Option Overview
9500 MXC User Manual Data Option Overview Each port is configured for asynchronous V.24/RS-232, or synchronous V.11/ RS-422 data and cross-connected to one of up to six overhead ports (channels) on each link (RAC or DAC 155oM) These channels share the same overhead as the NMS and radio-radio internal communication.
Page 476: Nms Option Overview
For an INUe, the AUX plug-in must be inserted in slots 1 to 6 as NMS access is only provided on these slots on its backplane. Where the NMS data function is not selected, the AUX plug-in may also be inserted in slots 7 to 9. Vol. IV-7-86 Alcatel-Lucent...
Page 477: Aux Transport On Link Overhead And Operating Rules
The NMS option is not supported by the 9500 MXC Terminals. AUX Transport on Link Overhead and Operating Rules • The link overhead supports 9500 MXC NMS, radio-radio handshaking (such as ATPC), and auxiliary data. • Auxiliary data is allocated to individual 64 kbps circuits (up to six for the INU/INUe, one for the IDUs) in the overhead.
Page 478: Aux Configuration
Only applies to a Sync setting. • Name. Enter a name/ID (optional). • Function. Select Data or NMS. • The NMS option is not available on 9500 MXC IDUs. • The NMS option forces a Sync setting. • Type. Select Sync or Async.
Page 479 2. Click on a Port row to enable its configuration options. 3. Select Function, Data or NMS. (NMS is not a 9500 MXC Terminal option) 4. Select Type, Async or Sync. This option is only provided for a Function >...
Page 480: Alarm I/O Configuration
It does not support mapping of alarm actions; what to do with an alarm input, and where to source the event(s) to activate an alarm output. For alarm action mapping, refer to 9500 MXC Node and Terminal Alarm Actions on page 11-1.
Page 481 9500 MXC User Manual AUX Alarm I/O Screen Figure 7-37 shows a typical AUX Alarm I/O screen for 9500 MXC Node. For 9500 MXC Terminal four Alarm I/O ports are displayed. Alarm I/O Screen Figure 7-37. Item Description For an INU/INUe select an input/output port combination. IDUs have one fixed combination.
Page 482 6. To commit the configuration, click Send. Next Step To configure alarm actions (mapping), go to 9500 MXC Node and Terminal Alarm Actions on page 11-1. For information on connector pinouts and I/O cable options, refer Appendix C.
Page 483: Chapter 8. Protection
Chapter 8. Protection Node and Terminal protection are considered separately. Refer to: • Node Protection on page 8-1 • Terminal Protection on page 8-17 Node Protection Link and Tributary protection mechanisms are supported. Standard Link Protection configurations are: • Hot-standby with two RACs •...
Page 484 Space Diversity Non-protected 1+1 Ring Link Protection A 9500 MXC Super-PDH ring protected network can be enhanced with one or more 1+1 protected links. • 1+1 protection of a ring-protected link is normally implemented to provide path protection as distinct from equipment protection. Therefore space diversity (SD) is the required/recommended 1+1 protection mode.
Page 485: Node Protection Configuration
Node Protection Operation and Rules This section provides data on the basic 9500 MXC link and data protection options. For additional data on dual protection and 1+1 ring protection refer to: • Additional Rules for Dual Protection on page 8-6.
Page 486 LINK. A DAC or protected DACs are identified as DATA. 4. Partner plug-ins will only be permitted within the slot conventions for the INU and INUe. Refer to 9500 MXC Node Slot Numbering Conventions on page 1-7 of this Volume.
Page 487 9500 MXC User Manual • When a protected hot-standby or diversity link is returned to two non-protected links, the circuit connections established for the protected link will stay with what was the primary RAC. There will be no circuit connections assigned to what was the secondary RAC. Similarly, for protected DACs the circuit connections established will stay with what was the primary DAC.
Page 488: Additional Rules For Dual Protection
4. Each of the subordinated links are first configured for the protection option required. Refer to Table 8-1 on page 8-2. Once configured the option to protect is applied to one of the protected links, whereupon all valid protection partners are presented for selection. Vol. IV-8-6 Alcatel-Lucent...
Page 489: Additional Rules For 1+1 Ring Protection
9500 MXC User Manual 5. Each subordinated link may operate on different channel bandwidths, and/or different frequency bands. 6. Each of the subordinated links operates as a normal link of that configuration. 7. Under dual protection only one link of the two subordinated links is sending received data to the Node bus at one time.
Page 490 Chapter 8. Protection • A 9500 MXC ring Node may have one or both (east and/or west) ring links configured for 1+1 protection. 3. 1+1 protection may be applied to co-channel ring links. • Using RAC 40s two concentric, autonomous rings of equal capacity/ bandwidth can be configured to operate on the same frequency using the V and H polarizations.
Page 491 9500 MXC User Manual • A subordinate space diversity link operates independently of the ring operation. Specifically, a wrapped ring link does not inhibit normal 1+1 operation of the space diversity link. Switch Management Heirachy: SD + SD Subordinated Links Figure 8-1.
Page 492: Link And Data Protection Configuration Screen
Figure 8-5 on page 8-13 shows a Protection Selection Window for a DATA/DAC selection. For configuration procedures refer to: • Description of Node Protection Configuration Screen on page 8-14 • Configuring Node Protection Options on page 8-14 Vol. IV-8-10 Alcatel-Lucent...
Page 493 9500 MXC User Manual Typical INUe Protection Screen Figure 8-3. Item Description The Protection screen identifies all protectable plug-ins and all plug-ins that have been configured for protected operation. Once a link is protected, the options are to break protection or to swap primary with secondary.
Page 494 LINK capacities. In this example the east and west RACs have been configured for a capacity of 64xE1, but with a ring capacity of 48xE1. (Note that a 1xE1/DS1 capacity is auto-configured when ring protection is first set). Vol. IV-8-12 Alcatel-Lucent...
Page 495 9500 MXC User Manual Item Description Shows balance of circuits available (16xE1) for use as additional ring-protected circuits, or as point-to-point circuits. Ring wrap and unwrap settings. If Delay Ring Unwrap is selected, both wrap and unwrap criteria default to standard.
Page 496: Description Of Node Protection Configuration Screen
If you are configuring protection on co-channel XPIC links, refer to the guidelines provided in Co-channel Operation on page 3-102, Volume II, Chapter 3. To view and configure protection options: 1. Identify the LINK, DATA, or LINK/DATA pairings you wish to convert to Vol. IV-8-14 Alcatel-Lucent...
Page 497 9500 MXC User Manual protected operation. 2. For LINK or DATA protection, identify which is to become primary. This is important where you wish to maintain any existing circuit connections; the LINK or DATA assigned as primary will retain its existing connections, and circuit assignments for the secondary will automatically be configured to match the primary.
Page 498 Changing the protection type or changing the primary and secondary selection may cause existing circuits to be disconnected. When making a change, always check any existing circuit connections to/from the affected plug-ins and reconfigure as necessary. Vol. IV-8-16 Alcatel-Lucent...
Page 499: Terminal Protection
9500 MXC User Manual Terminal Protection The protectable Terminals are: Protection Options IDU 20x Hot-standby, Space Diversity IDU 155o Hot-standby, Space Diversity Tx protection switching is not hitless. Rx path switching (voting) is hitless (errorless) between the two receive data streams on hot-standby and space diversity.
Page 500 IDU will be established as the online IDU. Alarm I/O remote actions are transported via the NMS. Connects its partner IDU and a co-located link or other NMS port for next-hop NMS. Vol. IV-8-18 Alcatel-Lucent...
Page 501 9500 MXC User Manual 15. A unique IP address must be entered for the IDU partners (each must be seen as a separate device on the management network). • The network portion of the IP address must be common. The host portion must be unique (both IDUs are on the same LAN).
Page 502: Idu Protection Configuration
At this point, once configurations have been confirmed by clicking Send, CT screens for both IDUs can be opened using a CT connection to one of the IDUs . Log into one IDU and select its partner by selecting File > New CT > Partner IDU. Vol. IV-8-20 Alcatel-Lucent...
Page 503 9500 MXC User Manual 5. Alarm Actions (if required) 6. Date/Time. 7. Software Management (both partners must be loaded with the same software release) 8. To commit the configurations click Send. 9. Check the partner configurations. The Configuration > Protection screen confirms the IP address for the viewed IDU and partner IDU, and whether set for primary or secondary.
Page 504 Ensure that one IDU is configured as Primary and the other as Secondary. Example screens show an IDU 20x pairing. To easily open a CT session with a protection partner click File > New CT > IDU Partner. Select the tributary protection type. Vol. IV-8-22 Alcatel-Lucent...
Page 505 9500 MXC User Manual Additional Procedures for IDU 20x The IDU 20x supports normal terminal protection for capacities to 20xE1 or 16xDS1 using the Hot Standby: Tributary Y-cable, or Hot Standby: Tributary Always-On options. Follow the standard IDU protection configuration procedures.
Page 506 IDUs appear each time a protected IDU pairing is opened IDU 20x: Normal Data Flow Figure 8-7. 20xE1 / 16xDS1 20xE1 / 16xDS1 Tribs Tribs Expansion Cable Secondary Primary Primary Secondary Expansion Cable 20xE1 / 16xDS1 20xE1 / 16xDS1 Tribs Tribs Vol. IV-8-24 Alcatel-Lucent...
Page 507 9500 MXC User Manual IDU 20x: Data Flow with Offline Rx ODU Failure Figure 8-8. 20xE1 / 16xDS1 20xE1 / 16xDS1 Tribs Tribs Expansion Cable Secondary Primary Primary Secondary Expansion Cable 20xE1 / 16xDS1 20xE1 / 16xDS1 Tribs Tribs 3DB 23063 ADAA - Rev 004 July 2007...
Page 508 Chapter 8. Protection Vol. IV-8-26 Alcatel-Lucent...
Page 509: Chapter 9. Circuits
Before circuits are configured you should have at hand a listing of all circuits to be configured, including circuit names. The circuits screen applies to 9500 MXC INU/INUe, and to IDU ES. IDU ES circuits functionality for Ethernet, E1/DS1 tributaries, and AUX is similar to an INU/INUe fitted with 1xRAC, 1xDAC 16x, and 1xAUX plug-ins.
Page 510: Circuits Configuration - Traffic
• Circuits Configuration on page 9-5 • DAC ES/GE Circuit Configuration Screen on page 9-6 • Ring-Node Circuit Configuration Screen on page 9-7 Refer to Procedure for Configuring Circuits - Traffic on page 9-9 for the configuration process. Vol. IV-9-2 Alcatel-Lucent...
Page 511: Typical Circuits Configuration Screen
9500 MXC User Manual Typical Circuits Configuration Screen Figure 9-1shows a circuits screen for a typical aggregation node comprising a 40xE1 link interconnecting with a 16xE1 link, a 20xE1 link and a DAC 16x: 9500 MXC Node 16xE1 40xE1 20xE1...
Page 512: Expanded Circuits Configuration Screen
Figure 9-2. Use scroll bar to view all circuits Item Description Click and drag the bar to adjust the window heights. With toggles in the down position, circuit connections are displayed port-to-port. Circuit names can be user-defined. Vol. IV-9-4 Alcatel-Lucent...
Page 513: Circuits Configuration
9500 MXC User Manual Item Description From, To and Port tabs are used to set circuit connections for unallocated tribs, or to disconnect tribs. The disconnect option supports bulk Link or Data disconnection with the toggle up, or circuit-by-circuit disconnection with the toggle down.
Page 514: Dac Es/Ge Circuit Configuration Screen
STM1 circuits. For DAC ES/GE, refer to Additional Rules for DAC ES and DAC GE on page 9-13. The IDU ES Ethernet function mirrors the DAC ES. Its 8x E1/DS1 function mirrors the DAC 16x. Vol. IV-9-6 Alcatel-Lucent...
Page 515: Ring-Node Circuit Configuration Screen
9500 MXC User Manual Example Circuit Connections with a DAC ES Figure 9-4. Item Description A DAC ES requires an E1 or DS1 backplane. Shows a DAC ES (DAC ES in slot 4). Shows the circuit connection for the DAC ES. In this example 16x 2.048 Mbps circuits are assigned to Link 1 to provide a 32 Mbps Ethernet connection.
Page 516 • This leaves spare point-to-point capacity of 33xE1 towards the west, and 2xE1 east. The circuits screen for this example is shown in Figure 9-6 on page 9-9. Example Circuit Requirements for a Ring Figure 9-5. 9500 MXC Node WEST EAST DAC 155oM RAC 30...
Page 517: Procedure For Configuring Circuits - Traffic
9500 MXC User Manual Example Circuits Screen for Figure 9-5 Requirements Figure 9-6. Item Description In this example the maximum possible ring capacity is 32xE1 (32xE1 has been configured on the east RAC and 63xE1 is available on the west DAC 155oM).
Page 518 To module, the From and To port buttons will prompt for a 16xE1 bulk allocation. If such a bulk allocation is not intended, then select the 1st port-to-port circuit using the Port drop-down menus, and proceed as above. Vol. IV-9-10 Alcatel-Lucent...
Page 519 9500 MXC User Manual 5. Click Apply The newly connected circuit is shown in the port-to-port connections box, and the number of circuits unallocated is reduced accordingly. • Continue to click Apply to establish subsequent new circuit connections between the same modules. This connection is made in ascending numerical order on the port numbers first established.
Page 520: Additional Rules For An East-West Pdh Ring
NxE1 or NxDS1 configurations. 2. The connections box defines connections from a Link to a DAC as drop and insert circuits. Circuits which are connected through (east - west) are termed pass-through circuits. Vol. IV-9-12 Alcatel-Lucent...
Page 521: Additional Rules For Dac Es And Dac Ge
9500 MXC User Manual 3. Circuits are default connected for pass-through. To assist your planning of circuits on a ring refer to Planning a Ring Network, Appendix A. Additional Rules for DAC ES and DAC GE The following applies to DAC ES and DAC GE when configured for an E1 or DS1 channel type.
Page 522: Additional Rules For Dac 3Xe3/Ds3M
• DS3 front-panel Tx/Rx 2 to DS1 ports 29 to 56 4. For E13/M13 mode, where the E1/DS1 streams are to be transported end-to-end over a 9500 MXC link or links, the E1 or DS1 circuits should, for ease of identification, be in contiguous blocks of 16xE1 or 28xDS1 respectively.
Page 523 9500 MXC User Manual Auxiliary Circuits Screen Figure 9-8 is an example of an auxiliary screen showing AUX ports 1 and 3 configured for DATA transport, and port 2 configured for NMS. Only Data circuits can be configured in this screen. NMS ports are shown only to provide a complete picture of all AUX ports.
Page 524: Procedure For Configuring Auxiliary Circuits
NMS capacity within the overhead will be reduced to its 128 kbps minimum. If on the other hand the AUX data channel is configured for port 1, then available NMS capacity will be 448 kbps (512 less 64 kbps). Vol. IV-9-16 Alcatel-Lucent...
Page 525: Chapter 10. Networking Configuration
Appendix D. Static or Dynamic Routing Each 9500 MXC Node or Terminal functions as a router to manage the NMS IP routing between nodes, and from nodes to other management connected devices, such as other Alcatel-Lucent radios, or other vendor products or management networks.
Page 526: 9500 Mxc Address And Routing Options
Where an OSPF-routed network is interfaced to a RIP-routed network, OSPF and RIP must only be enabled on the interfacing router (9500 MXC terminal). • If both OSPF and RIP are enabled on multiple 9500 MXC terminals in a network, routes installed by one protocol are propagated by the other, resulting in a proliferation of conflicting routes.
Page 527: Rules For Single And Interface Addressing Modes
NMS connectivity. 4. Interface (advanced) IP addressing and static or dynamic routing: • Use of a separate IP address for each 9500 MXC NMS interface: Ethernet, Link(s), V.24. • Selection of static or dynamic routing options, as above.
Page 528: Networking Screens
• Selection of dynamic routing options of OSPF, RIP1 or RIP2. • Enable DHCP server. Tabs provide access to Interface Addressing, and to Static Routing or Trap Destination screens. On selection of OSPF routing, the option to Enable OSPF Area is un-greyed. If Vol. IV-10-4 Alcatel-Lucent...
Page 529 9500 MXC User Manual the NMS network into which the Node/Terminal is to be installed has been segmented for OSPF area operation, its area number must be entered. Otherwise leave unchecked. Figure 10-1 shows a typical IP Addressing screen. The example shows entry of a single IP address, and no selection of dynamic routing, indicating static routing has been chosen.
Page 530: Configuring Single Ip Addressing And Dynamic Routing
Configuring Single IP Addressing and Dynamic Routing 1. In the opening screen enter an IP Address and Subnet mask for the 9500 MXC Node or Terminal. This is the address for the Ethernet interface on the 9500 MXC router; all other interfaces on the router assumes this Ethernet address.
Page 531 • No static routes are required from Nodes/Terminals to address NOC host devices (PCs, Server), meaning NMS PCs (9500 MXC CT) can be added/ removed from the NOC LAN without affecting network visibility. • At the NOC, each of the LAN hosts (PCs, Server) are also configured with a default gateway in their TCP/IP properties.
Page 532 Procedure 1. In the IP Addressing screen enter a single IP Address and Subnet mask for the 9500 MXC Node or Terminal. This defines the Ethernet port address for the Node/Terminal, and all other interfaces assume this address. If you are using an Ethernet connection for your CT PC and you re-configure the IP address of the radio to put it on a different subnet, a new CT session will be needed to log back in after the Send button is clicked.
Page 533: Configuring Interface Ip Addressing And Routing
The V.24 port is only to be configured when used for connection to a router, or similar device. For V.24 connection to a 9500 MXC CT PC, no configuration is required.
Page 534 The screen opens with line entries for the Ethernet port, the Link(s), and the V.24 maintenance port. For the 9500 MXC Node the number of Link lines match the number of links installed (non-protected and protected each count as one link).
Page 535: Interface Addressing Screen Description
Configuring Trap Destinations The Trap Destinations screen supports identification of a network management server to which traps can be sent from 9500 MXC via its network management network. Two modes are supported, ProVision or Third Party: • ProVision Mode sends a common trap for all alarms, alerting the ProVision element manager to break its polling cycle and go straight to the alarmed 9500 MXC.
Page 536 Default is 10, maximum 120, minimum 1. 5. In Operation Mode, select Provision or Third Party. 6. Click Enable Destination. 7. Click Send to commit the configuration. Vol. IV-10-12 Alcatel-Lucent...
Page 537: Dhcp Server Function
The DHCP server function is used to support Ethernet NMS access for your CT PC whereby 9500 MXC-to-PC connection is established under DHCP; the DHCP server on 9500 MXC assigns an IP address for your CT PC, which is configured to obtain and IP address automatically.
Page 538 DHCP and direct IP addressing are available, although DHCP provides a much more straightforward connection process. • For protected 9500 MXC Terminals (two co-located IDUs), or where there are other local 9500 MXC devices (INU, INUe, IDU) on the same NMS LAN (NMS 10/100Base-T ports interconnected), all devices may be configured as DHCP servers, except at sites such as a NOC (Network Operations Center).
Page 539: Configuring The Dhcp Server
When considering the address range, bear in mind that where there are two or more 9500 MXC devices on the NMS LAN, such as a protected IDU pairing or back-to-back INU/IDUs, the server address range should be different and non-overlapping, so that there is no potential for the devices trying to issue the same IP address.
Page 540 • The range would normally start with the next LAN IP address after the server address (the IP address of the radio). • Where two or more 9500 MXC devices are on the LAN and are DHCP enabled, ensure the LAN address range for each device is non-overlapping.
Page 541 9500 MXC User Manual • Valid example for protected IDUs (both DHCP server enabled): IDU 1 9500 MXC Ethernet IP address: 192.168.0.1 (255.255.255.0) First: 192.168.0.3 Last: 192.168.0.10 IDU2 9500 MXC Ethernet IP address: 192.168.0.2 (255.255.255.0) First: 192.168.0.11 Last: 192.168.0.20 3. Click Send to commit the configuration.
Page 542 Chapter 10. Networking Configuration Vol. IV-10-18 Alcatel-Lucent...
Page 543: Chapter 11. 9500 Mxc Node And Terminal Alarm Actions
• TTL alarm inputs can be mapped to an output on the same AUX or to another AUX within a 9500 MXC network. • Internal alarms can be mapped to relay output on any AUX in a 9500 MXC network.
Page 544: Before You Begin
Chapter 11. 9500 MXC Node and Terminal Alarm Actions Alarm Actions Screen Figure 11-1. Item Description Summarizes the setup for each alarm destination. Example of a new, non-configured destination. Shows an alarm tree for local Node/Terminal. Click the triggers to activate or de-activate alarm events to be mapped to selected destinations.
Page 545: Procedure For Alarm Actions Configuration
Node. This updates the entry in the Alarm Actions Destination panel. Where the destination is a 9500 MXC Terminal, the Terminal resolves slot location; any valid slot number (1 to 9) entered in the originating 9500 MXC is default connected to the AUX I/O function in the destination Terminal.
Page 547: Chapter 12. Date And Time Configuration
Chapter 12. Date and Time Configuration The Date/Time configuration screen, provides options for: • Direct entry of date and time. • Selection from calendar and time zone prompts. • Synchronization with the CT PC date/time (Synchronize With Computer). • Synchronization with an external Simple Network Time Protocol (SNTP) server.
Page 548 A date time can be direct-entered, or set from the CT PC clock. Subsequent timing is maintained by the internal Node/Terminal clock. SNTP Operation supports connection to one or more external SNTP time servers via the NMS network. Vol. IV-12-2 Alcatel-Lucent...
Page 549 9500 MXC User Manual • The server is identified by its IP address. When first configuring the time server option, the Synchronize Now button should be used, which will immediately reset the Node/Terminal time to the server time. • Thereafter the built-in SNTP client automatically establishes connection to the time server each hour.
Page 550 Chapter 12. Date and Time Configuration Vol. IV-12-4 Alcatel-Lucent...
Page 551: Chapter 13. Software Management
Refer to: • Software Version Control • Software Management Screen. The customer is responsible for any decision to update 9500 MXC software to a later version. Software Version Control When a 9500 MXC Node or Terminal is shipped the software installed and the...
Page 552: Software Management Screen
Refer to Typical Loading Sequence on page 13-3 and to the Software Management Screen in Figure 13-1 on page 13-6. • For the 9500 MXC Node the load destinations are the NCC and ODU, or ODUs. • Load destinations are not user selectable - all destinations are loaded.
Page 553: Typical Loading Sequence
9500 MXC User Manual Refer to: • Typical Loading Sequence • Software Rollback Typical Loading Sequence Having selected the software pack to load and a transfer/activate option, the new software installation process is initiated by clicking the Start button. Sequences are described for the three transfer/activate options: •...
Page 554 LEDs and cycling of front panel LEDs. 5. At the end of this period 9500 MXC returns to normal operation. There is no requirement to reset a 9500 MXC Node or Terminal on completion of a software load - the new version automatically replaces the old version.
Page 555: Software Rollback
• 9500 MXC maintains two software load spaces on the CompactFlash card. • One load space is always reserved for the active (current) software load.
Page 556 Software Status shows the active version for each load destination, and any current load activity. Example shows a software load in progress. Shows the active software versions (ODUs and NCC/Control Module). Select an action option for software transfer and/or activate. Vol. IV-13-6 Alcatel-Lucent...
Page 557 9500 MXC User Manual Item Description The Select button opens a browser on your PC to locate and select software to load. To select the software rollback option click the Advanced button. Software rollback is not supported by ODU 300hp.
Page 558 Chapter 13. Software Management Vol. IV-13-8 Alcatel-Lucent...
Page 559: Chapter 14. Security Configuration
Read only. An operator cannot send changes to 9500 MXC or update software, or change password or security settings. 3DB 23063 ADAA - Rev 004 July 2007 Vol. IV-14-1...
Page 560 To reset a lost password, follow the procedure in Lost Password Procedure on page 2-28 of this Volume. Figure 14-2 shows the opening screen for a password protected 9500 MXC when opened with an admin username and password. • Only administrators can manage/edit passwords.
Page 561 9500 MXC User Manual Login Screen for Admin Figure 14-2. 3DB 23063 ADAA - Rev 004 July 2007 Vol. IV-14-3...
Page 563: Chapter 15. Diagnostics
Chapter 15. Diagnostics The CT diagnostics screens are used to source status and performance information about 9500 MXC Nodes and Terminals, and to set diagnostic modes for testing and fault-finding. The screens included in the 9500 MXC CT Diagnostic Menu are: •...
Page 564: System Summary
System Summary The System Summary screen is the CT opening screen. It provides a real time overview of system status for the 9500 MXC Node or Terminal, and for a Node the tools to set the system layout. See System Summary Navigation on page 15-3.
Page 565: System Summary Navigation
System Functions Panel Each Node/Terminal system function is separately identified by a module. Colors used for module icons reflect alarm severity, and 9500 MXC problem icons are presented to assist problem identification with links into the relevant Alarms screen. For the Node, circuit connections are shown between traffic plug-ins, the color of which also reflects the alarm severity associated with the module at one or both ends of its connection.
Page 566 Problem Icons • Mouse-over for tooltip advice. • For a list of problem icon types, refer to 9500 MXC CT Symbols on page 1-3. Quick-entry to Other Screens • Right click on any module to view a short menu of selected options. Left-click a selection to go direct to the option.
Page 567 • Mouse-over a module to view its location in the INU/INUe Replaceable Units graphic (Node only). Replaceable Units Panel Replaceable Units shows the physical layout for a 9500 MXC Node. • Allows easy identification of plug-in types and location. Unconfigured slots are shown as blanks.
Page 568: System Layout Configuration: Node
Chapter 15. Diagnostics System Layout Configuration: Node This procedure: • Only applies to a 9500 MXC Node. It enables slot plug-in options to be installed, un-installed or changed it type. • Only applies where a module conflict has arisen: • A vacant but configured slot is indicated as shown: •...
Page 569: Event Browser
The Event Browser, in Figure 15-2, provides a real time view of all events, both active and cleared, for the selected 9500 MXC Node or Terminal. The browser has a nominal capacity of 5000 events, after which time new events replace earliest events on a one-for-one basis.
Page 570 Help for Event. Click to view context-sensitive help. The helpset for 9500 MXC must be loaded on your CT PC for this operate. Click to enable the All Occurrences and Description views. The Description view mirrors the event description for a selected event. Vol. IV-15-8 Alcatel-Lucent...
Page 571: Event Browser Screen Description
9500 MXC User Manual Event Browser Screen Description The screen opens to an event listing, which scrolls down to the latest event, unless auto-scroll is turned off. Other lists (boxes) can be enabled using tabs on the lower right. Event box provides a date/time-stamped listing for each new event (alarm and informational).
Page 572 • The Helpset folder is installed from ‘Install Helpset’ on the 9500 MXC Setup CD. It default installs to C drive > Program Files > 9500 MXC Help, but can be installed to any location on your PC, as CT will find it •...
Page 573 9500 MXC User Manual • If the Helpset is not available (has not been loaded on your PC), the Help for Event tab will remain greyed-out and a Help Not Installed message will appear below the Help for Event tab.
Page 574 (highlighted) in the Events box. Show Description Click tab to open the Description box. Currently replicates the selected event. Box heights for Show Occurrences and Show Description may be changed by clicking and dragging on the divider bars. Vol. IV-15-12 Alcatel-Lucent...
Page 575: Alarms
9500 MXC User Manual Alarms The Alarms screen provides a tree view of alarm history for a selected module since logon or since a History reset as shown in Figure 15-4. Only alarms relevant to the selected module are displayed. See Alarms Screen Navigation on page 15-14.
Page 576: Alarms Screen Navigation
(requires installation of HSX Help on your PC). Alarms Screen Navigation Module. The Alarms screen for the 9500 MXC Node opens on the first filled slot in an INU/INUe. Clicking the Select new module tab brings up a menu of links and cards installed.
Page 577 • The Helpset folder is installed from ‘Install Helpset’ on the 9500 MXC Setup CD. It default installs to C drive > Program Files > 9500 MXC Help, but can be installed to any location on your PC, as CT will find it •...
Page 578: History
The Graph screen as shown in Figure 15-5 provides a link-based view of operational status. Figure 15-5 shows a screen for a protected link, which includes data from both protection partners. Example History Screen with 15 Minute Resolution Figure 15-5. Vol. IV-15-16 Alcatel-Lucent...
Page 579 9500 MXC User Manual Item Description Select a resolution type, 15-minute or Daily. Complete History view. Up to one weeks worth or 15 minute bins, or one month of daily bins. Select the view type, Graph or Report. The Detail window shows 12 hours worth of 15 minute data bins, or 1 week of 24 hour bins.
Page 580: History / Graph Screen Navigation
History data is held on a FIFO basis. Data in excess of the 15 minute or daily bin maximums is deleted in favor of new-in data. The history screen has a 1.5 second sampling rate for RSL capture. Events of less than this duration may not be presented. Vol. IV-15-18 Alcatel-Lucent...
Page 581: History / Reports Screen: Racs
9500 MXC User Manual History / Reports Screen: RACs The Reports screen provides summary data over a user-selectable period for G.826, G.821, RSL, Events, and Configuration Changes. G.826 is the default. See Figure 15-7. • Stay with the report range set in the Graph view, or select a report range in the Complete History view.
Page 582: History / Report Screen Navigation
Figure 15-8 shows a typical opening screen. Screens have the same appearance and function for DAC ES, IDU ES and DAC GE. It default opens to 15 minute resolution. Refer to Table 15-2 for a description of the numbered items. Vol. IV-15-20 Alcatel-Lucent...
Page 583 9500 MXC User Manual History Screen: DAC ES Figure 15-8. Ethernet History Screen Function Table 15-2. Item Description Port/Channel summary windows. Data is displayed from right to left in time order. See Item 2. Higher resolution data for the selected port/channel is displayed in the Detail window to the right, see Item 3.
Page 584 • The edges (start and finish times) can be separately set. • The selected period (number of bins) can be moved within the widow by dragging the crossed arrow icon, which is displayed when your mouse is moved to the top of the selected period. Vol. IV-15-22 Alcatel-Lucent...
Page 585 9500 MXC User Manual Item Description Detail window. Presents higher resolution data and the ability to select a report range. The most recent data is to the right side of the window. Data is separately displayed for Tx and Rx traffic and for events.
Page 586 Chapter 15. Diagnostics Item Description Ethernet Stats report. Rx and Tx statistics are displayed for the report range selected in the Detail window. Vol. IV-15-24 Alcatel-Lucent...
Page 587 Events are mirrored from the Events Browser screen. They apply to the INU/ INUe/IDU - they are not specific to the Ethernet module. Use to help determine if any abnormal Ethernet traffic activity may be attributable to 9500 MXC link operation.
Page 588 • A configuration change is a change made in CT to the INU/INUe/IDU configuration. • A software change is a change made to the system software; new 9500 MXC SW has been loaded. • Configuration changes and software changes are also confirmed in the...
Page 589: Performance
Excel compatible CSV file on your CT laptop. If the CSV delimiter parameter has not previously been set on your laptop, when the Export tab is first clicked the Edit > Preferences window will be presented. Refer to 9500 MXC CT Menus on page 3-4 of Volume IV.
Page 590 Data is updated at 2 second intervals. The cross polarization discrimination entry only applies to RAC 40. G.826 Monitors. Set with the Start, Stop and Clear tabs. Click Export to save the data to your PC as a .csv file. Vol. IV-15-28 Alcatel-Lucent...
Page 591 9500 MXC User Manual Example Performance Screen for a Protected Link Figure 15-10. Item Description Status Monitors provide a real time view of operational status/performance for both RACs. • Detected Tx power is only shown for the online transmitter (s). The primary Tx is default online for hot-standby and space diversity.
Page 592 • Where both RACs in a protected link are operating error-free, the data in both RAC columns will be identical. When this is not the case the RAC data will be different, but data for the online RAC will always be the same as that shown for Protection. Vol. IV-15-30 Alcatel-Lucent...
Page 593: Ncc Performance
CT is logged on, or until the Stop or Clear buttons are selected. Data is updated at 2 second intervals. For the 9500 MXC Node the Performance Monitor screen can be enabled for all links on the node. Viewing other CT screens does not affect the aggregation of performance data.
Page 594 Figure 15-12. Item Description Click to enable tributary performance monitoring. Select a trib and a monitored direction. Line facing monitors error performance on the E1 stream from the trib interface. Bus facing is from the backplane bus. Vol. IV-15-32 Alcatel-Lucent...
Page 595: Dac Es And Idu Es Performance
9500 MXC User Manual Item Description Shows the elapsed time since monitoring was enabled, and the error counts. The Frame Alignment Errored Seconds counts invalid framing or no framing (no circuit connection to the source E1 multiplexer or other G.704 device).
Page 596 The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent them being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space. Vol. IV-15-34 Alcatel-Lucent...
Page 597 9500 MXC User Manual Statistic Description Out UCast Pkts The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent.
Page 598 Dot3 Stats Excessive A count of frames for which transmission on a particular Collisions interface fails due to excessive collisions. This counter does not increment when the interface is operating in full-duplex mode. Vol. IV-15-36 Alcatel-Lucent...
Page 599 9500 MXC User Manual Statistic Description Dot3 Stats Multiple A count of successfully transmitted frames on a particular Collision Frames interface for which transmission is inhibited by more than one collision. A frame that is counted by an instance of this object is also...
Page 600 The total number of frames transmitted with a length of Octets between 128 and 255 octets inclusive, including those with errors. Switch Stats Out 511 The total number of frames transmitted with a length of Octets between 256 and 511 octets inclusive, including those with errors. Vol. IV-15-38 Alcatel-Lucent...
Page 601: Dac Ge Performance
9500 MXC User Manual Statistic Description Switch Stats Out 1023 The total number of frames transmitted with a length of Octets between 512 and 1023 octets inclusive, including those with errors. Switch Stats Out Max Total frames transmitted with a length of between 1024 and Octets 1522 octets inclusive, including those with errors.
Page 602 Dot3 MultipleCollisionFrames Number of transmitted frames that experienced more than one collision. Dot3 SingleCollisionFrames Number of transmitted frames that experienced exactly one collision. Dot3 DeferredTransmissions Number of transmitted frames that were delayed because the medium was busy. Vol. IV-15-40 Alcatel-Lucent...
Page 603 9500 MXC User Manual Name Description InBadOctets Total data octets received in frames with a valid FCS. Undersize and oversize frames are included. The count includes the FCS but not the preamble. UndersizedFrames Total frames received with a length of less than 64 octets but with a valid FCS.
Page 604 512 and 1023 octets inclusive, including those with errors OutMaxOctets Total frames transmitted with a length of between 1024 and 1522 octets inclusive, including those with errors. Collisions Total number of collisions during the frame transmission. Vol. IV-15-42 Alcatel-Lucent...
Page 605: System/Controls
9500 MXC User Manual System/Controls The System/Controls screen presents Node and Terminal diagnostic menus for LINK (RAC/Radio), DATA (DAC/Trib), and AUX modules. Information is provided on: • Link Menu on page 15-43 • Ring Menu on page 15-52 • DAC/Tributary Menu on page 15-56 •...
Page 606 • For a TX mute the ODU Status flashes orange. System/Controls Screens for Protected RACs and IDUs Figure 15-14 shows a System/Controls screen for a protected 9500 MXC Node link Figure 15-15 shows a System/Controls screen for a protected 9500 MXC Terminal.
Page 607 9500 MXC User Manual Protected Link System/Controls Screen: INU/INUe Figure 15-14. Item Description Screen default opens to Link Protection. Tabs provide access to controls for RAC Tx mute and loopbacks. Graphic indicates RAC settings. The default settings have the primary RAC as Tx online and the secondary RAC as Rx online.
Page 608 Tx and Rx online protection controls. For IDUs, the default protection configuration has the primary IDU as online for Tx and Rx. Locks are supported by a safety timer. (The example screen shows that the secondary IDU is online for Tx and Rx). Vol. IV-15-46 Alcatel-Lucent...
Page 609 9500 MXC User Manual Item Description IDU Tx mute and loopback controls window. Link Sys/Controls Screen: Protected 40xE1 IDU 20x Figure 15-16. Item Description Screen default opens to Unit Protection. A Tab provides access to controls for IDU Tx mute and loopbacks.
Page 610: Link Menu Operation
For the IDU 155o and IDU 20x, when a change to Tx online is made the Rx online will follow providing Rx online locks are off (Rx online lock is Off/Auto). Vol. IV-15-48 Alcatel-Lucent...
Page 611 9500 MXC User Manual Tx Mute and Loopback Selection A Tx Mute applied on the online Tx of a hot standby or space diversity protected pair will be interpreted by the remote receiver as a signal/path failure and result in a ‘silent transmitter’ switch action (remote Node/Terminal signals the local Node/Terminal to switch transmitter).
Page 612 • The safety timer operation has not been enabled to default to the last setting used in the Edit > Preferences menu. This selection applies to all CT sessions. See 9500 MXC CT Menus on page 3-4, Volume IV, Chapter 3. The safety timer steps, related to Figure 15-17, are:...
Page 613 9500 MXC User Manual Safety Timer Operation Figure 15-17. Do not ask me this again (use this setting as default) is linked directly to the Edit > Preferences setting for Diagnostic safety timers default to last setting used. However, unlike the timer default enabled in the safety timer window above, the Edit >...
Page 614: Ring Menu
Refer to Figure 15-25 on page 15-66 for data on loopback points and loopback directions. The Event Browser and Alarm screens capture the application and subsequent release of diagnostic options, and while active, the diagnostic icon is displayed in the CT status bar, and the NCC Test LED flashes orange. Vol. IV-15-52 Alcatel-Lucent...
Page 615 9500 MXC User Manual Ring System/Controls Screen Figure 15-18. Item Description Tabs to Tx mute and Loopback locks. Protection Controls window. Graphic depicts the operational status for the node. This example shows normal [unwrapped] operation. Countdown timer indicates the time to go before an unwrap can occur. (No countdown is indicated in this exampl)e.
Page 616 (Counts down to zero). Applies to both the Error-free Timer and Delay Ring Unwrap Timer settings. Both timers are configured in the Protection screen. Refer to Node Protection Operation and Rules, Volume IV, Chapter 8. For safety timer operation refer to Safety Timer Operation on page 15-50. Vol. IV-15-54 Alcatel-Lucent...
Page 617 9500 MXC User Manual Ring Protection Locks Figure 15-19. Online Lock West Offline Lock West RAC/DAC East or West Diagnostics For a RAC the East / West tabs provide access to Tx Mute, and to bus-facing IF or digital loopbacks.
Page 618: Dac/Tributary Menu
Chapter 15. Diagnostics DAC/Tributary Menu For a 9500 MXC Node and an IDU ES a DAC tributary screen opens to reflect the DAC type selected. For 9500 MXC PDH and SDH Terminals the tributary type (NxE1/DS1, STM1/ OC3) is fixed for the IDU type.
Page 619 9500 MXC User Manual DAC 16xE1 System Controls Screen Figure 15-20. Item Description Looped icon confirms that a line facing loopback is applied to trib 1. Looped icon confirms that a radio facing loopback is applied to trib 3. The highlighted trib has PRBS enabled.
Page 620: Loopback And Ais Safety Timer Operation
When a both-way test is to be established, the PRBS data for the DAC/IDU first turned on accrues errors until PRBS on the second DAC/IDU is activated. The second DAC/IDU should display no errors after its 10 second stabilization period. To restart a PRBS count, click Reset. Vol. IV-15-58 Alcatel-Lucent...
Page 621: Auto Insertion Of Ais Or Prbs On Tribs
9500 MXC User Manual While PRBS Generation is ON: • INU/INUe: The NCC Test LED flashes orange and the diagnostic icon is displayed in the CT status bar. • IDU: The IDU Status LED flashes orange and the diagnostic icon is displayed in the CT status bar.
Page 622: Protected Dac Screens
AIS and PRBS functionality displayed in Figure 15-20 on page 15-57 for a non-protected DAC. • It is possible to set this functionality for one or both DACs, but valid data will only be presented by the online DAC. Vol. IV-15-60 Alcatel-Lucent...
Page 623 9500 MXC User Manual Protected 2xSTM1 Screens Figure 15-21. Item Description Protected 3xE3/DS3 DACs Protection window provides a graphic of protected DAC status, and locks for Tx and Rx Online. DAC windows support loopbacks, AIS, and G.821 BER testing per trib.
Page 624: Dac Es And Dac Ge Menu
Dashboard Overview selected. Provides an overview of the status, performance, and connections for all ports and channels. Example shows P1 enabled for 100 Mbps. Dashboard graph shows a 100 Mbps Rx throughput (data into port), and 50 Mbps Tx. Vol. IV-15-62 Alcatel-Lucent...
Page 625 9500 MXC User Manual Item Description 3, 4 Example shows that P1 is mapped to C1 using the Mixed operational mode. C1 capacity (link capacity) is set to 50 Mbps (49.4 Mbps), which is why the C1 graph indicates a 50 Mbps Tx discard rate; there is 100 Mbps ingressing P1, but C1 capacity only supports a max throughput of 50 Mbps.
Page 626 Frame counts are captured from the time a DAC ES or DAC GE is configured providing it remains powered-up. Figure 15-24 shows an example screen. Port status displays in the upper frame, and Channel status in the lower. Vol. IV-15-64 Alcatel-Lucent...
Page 627: Aux Menu
9500 MXC User Manual DAC GE Port/Channel Status Screen Figure 15-24. AUX Menu The AUX System/Controls screen supports line and radio facing loopbacks on each of the available communications channels; three for an AUX plug-in, one for an IDU AUX module. Safety timers are not currently supported.
Page 628 • Circuit loopbacks can only be set for a Node, and are applied per circuit. Only one circuit loopback can be set at a time. For information on circuit loopbacks, refer to Circuit Loopbacks for 9500 MXC Node on page 15-67. Note: An ODU cable loopback is not included. Instead, confirmation of ODU cable integrity is provided by: •...
Page 629: Circuit Loopbacks For 9500 Mxc Node
Loopbacks provide a user-friendly tool for tracing and checking a circuit through a 9500 MXC network. To permit straight-forward identification of a circuit within a 9500 MXC network, each circuit must have a unique name. A circuit name is entered in the Circuits screen, and the same name should be entered at all Nodes carrying that circuit.
Page 630 Only circuits configured in the Circuits screen can be viewed and selected. Circuits can be selected by finding and clicking a circuit line in the main panel. Circuits are listed alphabetically. Each circuit is identified by name, its port-to-port connection, and circuit type (tributary or auxiliary). Vol. IV-15-68 Alcatel-Lucent...
Page 631: Parts
9500 MXC User Manual To assist location of a circuit name, use the search options: • Search-by-name can be optioned for ‘Starts with’ or ‘Contains’. • For-component provides a sub-menu of installed circuit-carrying modules; LINKs, DACs, AUX. Select one to view only its circuits in the main panel.
Page 632 Chapter 15. Diagnostics Example Parts Screen Figure 15-27. Vol. IV-15-70 Alcatel-Lucent...
Page 633: Advanced Management
9500 MXC User Manual Advanced Management The advanced management screen supports two functions: • Software reset, which provides a hard reset for all software-resettable modules. Refer to Advanced Management Screen on page 15-71. • Clear Events and History, which clears all historical data from the Event Browser and History screens.
Page 634: Software Reset
- effectively a last resort option. It can be likened to a reboot for a PC. • Relevant 9500 MXC alarm descriptions include a reboot prompt where all other recommended actions fail to produce a result. • 9500 MXC alarm descriptions are prompted within: •...
Page 635 9500 MXC User Manual When Clear is clicked: • Both the Event Browser and History screens are updated to show only events/ data subsequent to the Clear command. • Both Event Browser and History screens display an information line, which remains for the current CT session unless a full recover is actioned.
Page 636 Chapter 15. Diagnostics Vol. IV-15-74 Alcatel-Lucent...
Page 637 Volume V Commissioning and Troubleshooting...
Page 639: Chapter 1. Commissioning
• Is operating to plan and running alarm and error-free • Has had all relevant commissioning data recorded • Is ready for traffic carrying duty The nodal design of 9500 MXC means that one INU/INUe usually supports multiple links. • Compared with a traditional single-link commissioning procedure, where the link is signed-off as one entity, for 9500 MXC a combination node-and-link procedure is required, using the node as the common reference.
Page 640 Refer to Commissioning Records on page 1-18. Final inspection and sign-off Completion of ‘paperwork’ recording installation hand-over for operational use, and/or any remedial action needed to complete an installation. Refer to Commissioning Records on page 1-18 Vol. V-1-2 Alcatel-Lucent...
Page 641: Ber
• Tributary BER measurement, where customer traffic on a trib is replaced by a BER test pattern. Refer to Trib BER Measurement on page 1-4. Background Error Measurement 9500 MXC provides background G.826 error measurements on the radio paths, from RAC to RAC. Such tests run continuously in the background (in both directions).
Page 642: Trib Ber Measurement
• For a both-way test, a PRBS generator on one DAC is G.821 received on its remote DAC, and vice-versa. No loopback is required. Within 9500 MXC, loopbacks can be set within DACs, RACs, and on the TDM bus. For information on these options refer to System/Controls on page 15-43, Volume IV, and to Circuit Loopbacks for 9500 MXC Node on page 15-67.
Page 643 For 9500 MXC, a fade margin test involves reducing the Tx power at one end of the link, and checking the error performance at the other using the G.826 data presented in the CT Performance Screen.
Page 644: Protection Switching
If the measured fade margin is significantly less than the expected margin, reasons can include: • Accuracy of measurement not taken into account. For 9500 MXC, the margin for error can be up to 3 to 4 dB, given the limitations of software-set power control, RSL measurement and G.826 error capture.
Page 645: Test Measurement
• The procedures provide confirmation of switch action using errored-second time resolution. • Confirmation of switching times with millisecond accuracy is a FAT (factory acceptance test) procedure. Contact Alcatel-Lucent or your supplier for details. The check procedures described refer to G.821 BER and G.826 link performance error measurement: •...
Page 646: Link And Ring Protection Logic
• Rx path switching is hitless (hot-standby and space/frequency diversity), providing the online Rx RAC is not withdrawn. The least errored data stream from the online and standby receivers is selected on a frame-by-frame basis within the online Rx RAC. Vol. V-1-8 Alcatel-Lucent...
Page 647 9500 MXC User Manual • The Rx protection switch function is contained within the RACs and is transferred between RACs to always be with the online Rx RAC (bus driving RAC). • Changing the online status from one RAC to the other using the locks in the...
Page 648: Confirming Link And Ring Protection
• For each switch event that is not designed to be hitless, the Errored Second count increments by 1, or depending on the counter time boundary relative to the event, a maximum of 2. Refer to Test Measurement on page 1-7. Vol. V-1-10 Alcatel-Lucent...
Page 649: Hot-Standby And Space Diversity
9500 MXC User Manual • For most tests Available/Unavailable time should not change, and the Severely Errored Second count will mirror the Errored Second count. Before You Begin • Ensure the link is operating alarm-free, and that path conditions are normal.
Page 650 8. Use the System/Controls screen to return to default online status (primary RAC Tx and secondary RAC Rx), and if an unequal coupler is used with a hot-standby installation, check that the online Tx is selected for the low-loss side. Vol. V-1-12 Alcatel-Lucent...
Page 651: Frequency Diversity
9500 MXC User Manual Rx Switching Procedure The procedure requires disconnection, in turn, of the RAC ODU cables. Test procedure: 1. Go to Diagnostics > Performance > Start All for the protected link. Ensure unavailable second and errored second counts are at zero.
Page 652: Ring Protection
5 minutes. At the instant it returns to normal, un-wrapped operation, service is restored within a count of one errored second (possibly two). 6. Repeat steps 2 to 5 for the West RAC. For more information on commissioning a ring network, refer to Appendix A. Vol. V-1-14 Alcatel-Lucent...
Page 653: Dac Protection
In the transmit direction both DACs send data to customer equipment, and the customer equipment switches between these two “always on” tributaries. TA protection must be used where two 9500 MXC INU/INUes are to be interfaced using protected DACs. 3DB 23063 ADAA - Rev 004 July 2007...
Page 654 5. On completion of the tests ensure the remote loopback(s) are disabled, or will time-out. The tests can also be completed for a situation where the local DAC pairing has one DAC online for Tx and the other for Rx. Use the System/Controls screen Vol. V-1-16 Alcatel-Lucent...
Page 655: Ncc/Npc
9500 MXC User Manual commands to set the required online combination before commencing the tests. NCC/NPC The NPC provides redundancy for NCC TDM bus clock and power supply functions. • For an NCC bus clock failure the NPC provides protection for tributary and auxiliary traffic;...
Page 656: Commissioning Records
Excel compatible format. Use this report to capture configuration and other site/installation data for appending to a final commissioning report. Support is available from Alcatel-Lucent to assist pre and post installation planning, as-built, and record keeping processes. Vol. V-1-18 Alcatel-Lucent...
Page 657 When on-site, CT is the primary troubleshooting tool. For information on CT diagnostic screens refer to Diagnostics, Volume IV, Chapter 15. User Prerequisites This guide is for use by personnel who have attended a 9500 MXC training course. 3DB 23063 ADAA - Rev 004 July 2007...
Page 658: Chapter 2. 9500 Mxc Troubleshooting
• Auto Insertion of AIS or PRBS on Tribs on page 2-9 Remote Diagnostics Using Remote Management Where a 9500 MXC is network managed under and EMS or NMS, use the features available to view indications of: • Alarm severity •...
Page 659: Before Going To Site Checklist
(Node or Terminal), frequency band, high/low end ODU, capacity, modulation and configuration (non-protected, protected, diversity, ring). Ask: • Is just one 9500 MXC link affected, or a number of links in the same geographical area? • Is the path down completely or is traffic passing but with a BER alarm? •...
Page 660: Troubleshooting Basics
LEDs on other plug-ins, check the seating of the affected plug-in. • Check System Summary screen. When logging into 9500 MXC with CT, the opening screen is System Summary. Use the information provided to check the alarm location, its severity, and problem type: •...
Page 661 NCC/IDU. • Hardware/software compatibility alarms will be raised when a new plug-in is installed that needs a later version of 9500 MXC software. • A configuration not supported alarm will be raised if the installed license is incompatible with the configured RAC/radio capacity.
Page 662: Troubleshooting Path Problems
For more information refer to Commissioning, Chapter 1. • Where dynamic NMS routing is configured, allow not less than 5 minutes for the 9500 MXC router address-table auto-update to complete. Troubleshooting Path Problems A path-related problem, with the exception of interference, is characterized by traffic being similarly affected in both directions.
Page 663: Path Problems On A New Link
9500 MXC User Manual For a remote-mounted ODU, check its antenna feeder. • New path obstruction Where all other parameters check as normal, and the path has potential for it to be obstructed by construction works, view/survey the path for possible new obstructions.
Page 664 Appendix A. Where the problem is not obvious, use a bus-loopback BER test to track a single circuit through a 9500 MXC network, beginning at the Node closest to the Node applying the BER test. • Incorrect circuit naming and commissioning...
Page 665 • Configuration Locked In the unlikely event a 9500 MXC device does not respond to normal CT commands the reset options include: • Power recycle: remove power to the radio off, pause for 10 seconds, and power-on.
Page 666 • 9500 MXC software updates LED states at least once every second. • Fleeting LED states are extended by software to ensure that a user has time to recognize a change in status.
Page 667: Inu/Inue Leds
9500 MXC User Manual INU/INUe LEDs Table 2-1 summarizes INU/INUe LED behavior. Empty cells in this table indicate that the associated LED state is not used. INU/INUe LED Alarm Table Table 2-1. State NCC Status NCC Test DAC Status RAC Status...
Page 668 Diagnostic mode selected/active. Check/remove mode using CT System flashing: Controls screen. DAC Status Orange Either: 9500 MXC software does not support the flashing: (new) DAC. Install latest 9500 MXC • Configuration corrupt software. • Configuration not supported • Hardware / software...
Page 669 Possible Causes Recommended Action RAC Status Orange Either: 9500 MXC software does not support the flashing: (new) DAC, or 9500 MXC software is • Configuration corrupt currently being installed via CT. Where new software is not being installed, new (latest) •...
Page 670: Idu Leds
Chapter 2. 9500 MXC Troubleshooting Indication Possible Causes Recommended Action AUX Status Orange Either: 9500 MXC software does not support the flashing: (new) AUX. Install latest 9500 MXC • Configuration corrupt software. • Configuration not supported • Hardware / software...
Page 671 9500 MXC User Manual IDU LED Alarm Triggers Table 2-3. Indication Possible Causes Recommended Action IDU Status Orange Either: Where the cause is not obvious, use CT to see flashing: detail at a lower alarm level. • Configuration corrupt • Configuration not supported •...
Page 672 • If you are viewing within the Helpset, you can return to this page by clicking the left arrow at the top of the page. • If you are viewing within an online pdf copy of the 9500 MXC User Manual, you can return to this page by clicking the left arrowhead in the toolbar (ensure ‘view history’...
Page 673: Ncc Alarm Hierarchy
9500 MXC User Manual • NPC Alarm Hierarchy on page 2-22 • DAC ES Alarm Hierarchy on page 2-23 • DAC GE Alarm Hierarchy on page 2-24 • DAC 155oM Alarm Hierarchy on page 2-25 • FAN Alarm Hierarchy on page 2-26...
Page 674: Rac Alarm Hierarchy
Chapter 2. 9500 MXC Troubleshooting Configuration Corrupt Configuration Not Supported (All) Software/Hardware Incompatible (All) Date and Time Not Set Slot Management Slot n Slot Plug-in Missing Slot Plug-in Incorrect Diagnostic TDM Clock Locked to NCC Circuit Loopback NMS Configuration Error...
Page 675 9500 MXC User Manual Demodulator Failure (RAC) ADC Failure (ODU) ODU component failure ADC Failure (ODU) FPGA Software Load Failure (All) Power supply RAC -48V Supply ODU -48V Supply Temperature IF Temperature Power Detector Temperature Transceiver RX Temperature ODU Communications Failure...
Page 676: Dac Alarm Hierarchy
Chapter 2. 9500 MXC Troubleshooting TX IF Synthesiser Not Locked Modulator Not Locked RAC TX Cable IF Synth Not Locked ODU TX Cable IF Synth Not Locked ODU TX Cable Unplugged Rx path failure ODU TX Cable Unplugged RX IF Synthesiser Not Locked...
Page 677: Aux Alarm Hierarchy
9500 MXC User Manual Software Configuration Not Supported (All) Software/Hardware Incompatible (All) Diagnostic Traffic Tributary Tributary n Trib n Output AIS Enabled Trib n Radio Facing Loopback Trib n Line Facing Loopback Trib n Link Test Enabled Protection TX Manual Lock...
Page 678: Npc Alarm Hierarchy
Chapter 2. 9500 MXC Troubleshooting Auxiliary Channel (n) Clock Failure Software Configuration Not Supported (All) Software/Hardware Incompatible (All) Diagnostic Auxiliary Auxiliary 1 AUX (n) Bus Facing Loopback AUX (n) Line Facing Loopback Auxiliary 2 AUX (n) Bus Facing Loopback AUX (n) Line Facing Loopback...
Page 679: Dac Es Alarm Hierarchy
9500 MXC User Manual Software/Hardware Incompatible (All) Diagnostic TDM Clock Locked to NPC DAC ES Alarm Hierarchy DAC ES Hardware Component failure FPGA Software Load Failure (All) EEPROM Failure (All) Switch Access Failure Software Configuration Not Supported (All) Software/Hardware Incompatible (All)
Page 680: Dac Ge Alarm Hierarchy
Chapter 2. 9500 MXC Troubleshooting Link Failure (DAC ES, DAC GE) Dropped frames Dropped Frames Ratio (DAC ES, DAC GE) DAC GE Alarm Hierarchy DAC GE Hardware Component failure FPGA Software Load Failure (All) EEPROM Failure (All) LIU Failure ICPU Failure...
Page 681: Dac 155Om Alarm Hierarchy
9500 MXC User Manual Link Down Link Degraded Port failure Port n Link Failure (DAC ES, DAC GE) Dropped frames Dropped Frames Ratio (DAC ES, DAC GE) DAC 155oM Alarm Hierarchy DAC 155oM Hardware Component failure FPGA Software Load Failure (All)
Page 682: Fan Alarm Hierarchy
FAN Alarm Hierarchy Hardware Fan Failure (FAN) 9500 MXC Terminal Alarms The following listing shows 9500 MXC Terminal alarm-tree hierarchy. Click only on tree-ends, in italics, to view alarm details. Refer to: • IDU Alarm Hierarchy on page 2-27 Vol. V-2-26...
Page 683: Idu Alarm Hierarchy
9500 MXC User Manual • Radio Alarm Hierarchy on page 2-28 • Tributary Alarm Hierarchy on page 2-29 • AUX Alarm Hierarchy on page 2-30 • Ethernet Alarm Hierarchy on page 2-31 • Terminal FAN Alarm Hierarchy on page 2-32...
Page 684: Radio Alarm Hierarchy
Chapter 2. 9500 MXC Troubleshooting Radio Alarm Hierarchy Radio Hardware Component failure IDU component failure ADC Failure (ODU) Modulator Failure Demodulator Failure (RAC) ODU component failure ADC Failure (ODU) RAC -48V Supply Power supply ODU -48V Supply Temperature IF Temperature...
Page 685: Tributary Alarm Hierarchy
9500 MXC User Manual Traffic Path Down Path failure Tx path failure TX Synthesiser Not Locked Transceiver TX Failure TX IF Synthesiser Not Locked Modulator Not Locked ODU TX Cable Unplugged RAC TX Cable IF Synth Not Locked ODU TX Cable IF Synth Not Locked...
Page 686: Aux Alarm Hierarchy
Chapter 2. 9500 MXC Troubleshooting LIU Failure Software Configuration Not Supported (All) Diagnostic Traffic Tributary Tributary n Trib n Output AIS Enabled Trib n Radio Facing Loopback Trib n Line Facing Loopback Trib n Link Test Enabled Tributary Tributary failure...
Page 687: Ethernet Alarm Hierarchy
9500 MXC User Manual Auxiliary 1 AUX (n) Bus Facing Loopback AUX (n) Line Facing Loopback Ethernet Alarm Hierarchy Ethernet Hardware Component failure Switch Access Failure Software Configuration Not Supported (All) Diagnostic Traffic Channel Channel n Channel PRBS Test Active...
Page 688: Terminal Fan Alarm Hierarchy
Chapter 2. 9500 MXC Troubleshooting Terminal FAN Alarm Hierarchy Hardware Fan Failure (FAN) Vol. V-2-32 Alcatel-Lucent...
Page 689: Using Ct Diagnostics Screens
9500 MXC User Manual Using CT Diagnostics Screens CT Diagnostics screens provide tools for locating and diagnosing 9500 MXC problems. Table 2-4 provides a summary of essential functions. Click on screen type in the Screen column to open a full description.
Page 690 (path on your CT PC. Otherwise, view this alarm degradation or a problem with the information from within the 9500 MXC remote Tx), or a fault within the Alarms section of this chapter (for PC-based...
Page 691 9500 MXC User Manual Screen Function Tips History Adds extra dimension to Events Browser and Use the report range options to select a time Alarms screens, by presenting a histogram of period within the complete history view to G.806 link performance data, together with...
Page 692: Informational Events
• If you are viewing within the Helpset, you can return to this page by clicking the left arrow at the top of the page. • If you are viewing within an online pdf copy of the 9500 MXC user Manual, you can return to this page by clicking the left arrowhead in the toolbar (ensure ‘view history’...
Page 693 9500 MXC User Manual Software File Received Software Changed Automatic Learning Disabled Configuration User Reverted Configuration Changed Watch Dog Expired Power On POST Failed Generic Trap CT User Logged Off Protection Switch Protection Switch Failure Low Memory Event Action Created...
Page 694 Chapter 2. 9500 MXC Troubleshooting Event Log Activitiy Suspended Event Log Activitiy Resumed ATPC Active ATPC Inactive AIS Transmitted AIS Transmission Ceased Rx Performance Monitoring Reset ATPC Max Power for 15 Minutes Set Power Out of Range ATPC Max Power Out of Range...
Page 695 9500 MXC User Manual Alarm Output 4 Deactivated Event System Restart Unsupported Configuration Event Log Activitiy Suspended Event Log Activitiy Resumed DAC ES Event System Restart Event Log Activitiy Suspended Event Log Activitiy Resumed Traffic Alignment Error Excessive Dropped Frames...
Page 696: Idu Informational Events
Chapter 2. 9500 MXC Troubleshooting Event System Restart Unsupported Configuration Event Log Activitiy Suspended Event Log Activitiy Resumed IDU Informational Events The following is a listing of the informational events for the IDU. IDU Terminal Event System Restart CT User Logged Off...
Page 697 9500 MXC User Manual User Authentication Enabled User Authentication Disabled Protected Partner Mismatched Software Version Protection Switch Protection Switch Failure License Entered Incorrect License Entered Date/Time Changed By SNTP Event System Restart Unsupported Configuration Event Log Activitiy Suspended Event Log Activitiy Resumed...
Page 698 Chapter 2. 9500 MXC Troubleshooting Event Log Activitiy Resumed AIS Transmitted AIS Transmission Ceased Event System Restart Unsupported Configuration Event Log Activitiy Suspended Event Log Activitiy Resumed Alarm Output 1 Activated Alarm Output 1 Deactivated Alarm Output 2 Activated Alarm Output 2 Deactivated...
Page 699: Volume Vi Appendices
Volume VI Appendices...
Page 701: Appendix A. Ring Network Planning And Implementation
- Use of the DAC 155oM for fiber closures - Inclusion of non-ring-protected point-to-point traffic on a ring Until this time, refer to instruction provided in the 9500 MXC User Manual under: - Volume II,Chapter 3. Protected Operation Description - Volume IV, Chapter 7, Plug-ins...
Page 702: Essential Ring Nomenclature And Rules
For NxE1 or NxDS1 (Super PDH) rings the failure detection and circuit re-routing is managed by the 9500 MXC Node, no external switching device is required. Refer to Essential Ring Nomenclature and Rules.
Page 703 • For any-to-any operation, traffic can be routed from any node in the ring to any other node. Operation of a 9500 MXC ring is described in 9500 MXC User Manual, Volume II, Chapter 3. Protected Operation. The wrapping action within a 9500 MXC Node is described in 9500 MXC User Manual, Appendix F.
Page 704: Planning A Ring Network
• The ring circuit numbers to be passed-through. Figure A-1 shows an example of a ring topology planning sheet for a North-South ring. Figure A-2 shows an excerpt from the circuit allocation planning sheet for the example provided in Figure A-1. Vol. VI-A-4 Alcatel-Lucent...
Page 705 9500 MXC User Manual North-South Ring Topology Planning Sheet Example Figure A-1. 3DB 23063 ADAA - Rev 004 July 2007 Vol. VI-A-5...
Page 706 Excerpt from a Circuit Allocation Sheet for the Example Ring in Figure A-1 Figure A-2. Vol. VI-A-6 Alcatel-Lucent...
Page 707: Installing A Ring Network
Until all links are operational, circuits configured on the network will remain wrapped at nodes either side of ring sections still to be completed. For information on 9500 MXC Installation, including antenna alignment, refer to 9500 MXC User Manual, Volume III, Installation.
Page 708: Configuring A Ring Network
Configuring a Ring Network CT, the 9500 MXC craft terminal, is used to configure a network. The configuration process is presented in the following order: • Layout on page A-8 • Licensing on page A-8 • Protection on page A-9 •...
Page 709: Protection
• Partner plug-ins will only be permitted within the slot conventions for the INU and INUe. For details refer to 9500 MXC Node Slot Numbering Conventions, Volume IV, Chapter 1. • Once a protected link is configured and saved (Sent), one or both RACs may be withdrawn without affecting the saved configuration.
Page 710: The Protection Screen
• LINK for non-protected radio links, and for hot-standby and diversity radio links. • DATA for a non-protected DAC 155oM fiber link. Figure A-3 shows typical protection screen for a ring selection. Protection Screen Showing a Ring Selection for an INUe Figure A-3. Vol. VI-A-10 Alcatel-Lucent...
Page 711: Configuring Ring Protection
9500 MXC User Manual Item Description Shows a ring pairing with its configured ring capacity and balance of available LINK capacities. Ring capacity has been set for 16xE1 (A 1xE1/DS1 capacity is auto-configured when ring protection is first set). Shows balance of circuits available for use as ring-protected circuits, or as point-to-point circuits.
Page 712 Applies to both the Error-free Timer and Delay Ring Unwrap Timer. (Counts down to zero). 5. To reverse the East and West roles, click on the ‘Swap East with West’ tab. 6. Click Send to save the configuration. Vol. VI-A-12 Alcatel-Lucent...
Page 713: Plug-Ins
For more information, refer to 9500 MXC User Manual, Volume II, Chapter 3. • Where east and west ring links at one node are operating in the same frequency band, good frequency planning dictates they should both be Tx high, or Tx low.
Page 714 Path settings are independently set for the East and West links. Modem profile settings are confirmed for both RACs. The Protection Settings Panel simply confirms that ring protection has been set. Vol. VI-A-14 Alcatel-Lucent...
Page 715: Circuits
9500 MXC User Manual Circuits The Configuration > Circuits screen supports two windows, one for Traffic Circuits, the other for Auxiliary Circuits. Ring-specific data for Auxiliary circuits will be included in a latter release of this appendix. Comprehensive data on Auxiliary configuration is included in CT >...
Page 716 Balance of protected ring circuits (10xE1) are passed-through. Alternative view shows all 16xE1 circuits assigned to the Ring; there are no circuits available for Pt-to-Pt. Local connections to DATA 2 remain at 4xE1, resulting in pass-through circuits incrementing to 12xE1 Vol. VI-A-16 Alcatel-Lucent...
Page 717 9500 MXC User Manual The important points to note in the example Traffic Circuits window (main view) are: • The East and West RACs have both been configured for a capacity of 16xE1. • The ring has been configured with a capacity of 14xE1, leaving 2xE1 available as point-to-point capacity in the East and West directions.
Page 718 3. To add or change a circuit name, highlight the existing name entry and type. View of a Connection in the Port-to-Port Connections Box Figure A-6. Item Description Toggle down to view individual circuit details. Highlight and type-over to enter a circuit name. To change existing circuits: Vol. VI-A-18 Alcatel-Lucent...
Page 719: Networking
OSPF. • The ring-interfacing LINK port must be set for static routing. For information on the Networking screen, refer to 9500 MXC User Manual, Volume IV, Chapter 4.
Page 720: Date/Time
Select Dynamic Routing (OSPF or RIP) for each node in the ring. The Static routing option must not be selected for ring networks. Date/Time The Configuration > Date/Time screen is standard for all 9500 MXC network configurations. For details, refer to Volume IV, Chapter 12. Vol. VI-A-20...
Page 721: Commissioning And Troubleshooting A Ring Network
9500 MXC User Manual Commissioning and Troubleshooting a Ring Network Guidelines are provided to confirm correct ring network operation. A pre-requisite is to confirm that all links on the ring are: • Operating error-free • Correctly configured for NMS networking •...
Page 722: Integrity Of Individual Ring Links
• NMS addressing and routing may be set incorrectly. If no nodes other than the local node are visible, check the gateway setting on your CT PC. Refer to 9500 MXC User Manual, Volume 4, Chapter 2. • One or more links on the ring are down, and ring wrapping has not occurred.
Page 723: Confirming Ring Wrapping And Unwrapping
9500 MXC User Manual 3. Leave a BER test on overnight (or other specified period) to confirm error-free ring operation. • If a BER test shows errors, cross-check against the G.826 stats in the Performance screens for all nodes in the ring.
Page 724: Fiber (Dac 155Om) Links
• ODU Tx cable IF synthesizer not locked • 10 BER (user selectable wrap and unwrap options) • RAC plug-in is missing • RAC software load failure Fiber (DAC 155oM) Links Conditions for ring wrapping: • Loss of SDH/SONET frame •...
Page 725: Checking Wrap And Unwrap Operation
9500 MXC User Manual go before the ring will unwrap. Applies to both the Error-free Timer and Delay Ring Unwrap Timer. (Counts down to zero) Checking Wrap and Unwrap Operation To simulate a ring radio-link failure: • A Tx mute can be invoked in Diagnostics > System Controls, for the east or west RAC.
Page 726 Applying a Tx mute to a West RAC will cause a wrap even when the secondary ring is not in use, for the reason all nodes need to be transparent to the possibility of a wrap occurring at another node on the ring. Vol. VI-A-26 Alcatel-Lucent...
Page 727: Appendix B. 9500 Mxc Alarms
Appendix B. 9500 MXC Alarms 9500 MXC alarms are presented under eight headings. Within each, the order of alarms is as they appear in the CT Alarms screen hierarchy. The alarms include information on probable cause, recommended actions, and where appropriate, additional information.
Page 728: Ncc/Idu Alarms
• EEPROM Failure • Configuration Not Supported • Software/Hardware Incompatible. This alarm information should be used in conjunction with 9500 MXC Troubleshooting, which for electronic copy includes links to this appendix under its CT Alarms section. To view alarms and informational events from within the Helpset, use the links from the Troubleshooting Guide.
Page 729 9500 MXC User Manual • During power-up. • When a new software version is loaded that includes an update to the FPGA. • When a RAC, DAC or AUX is installed in a powered Node. • Depending on the plug-in, FPGA loading may occur during a reconfiguration of Node backplane and/or RAC/DAC capacity.
Page 730 The ADC on the NCC is used to monitor voltage and temperature levels presented on, or to the NCC/IDU. RTC Failure Loss of communication with the RTC (realtime clock). This is a warning alarm. Probable Cause Equipment malfunction. Vol. VI-B-4 Alcatel-Lucent...
Page 731 9500 MXC User Manual Recommended Actions 1. Check for other alarms to determine how critical the alarm is. Depending on the malfunction, the Node/Terminal may otherwise operate satisfactorily. 2. If there are no other alarms to indicate a general NCC/IDU failure, check configuration of the clock in the CT Date/Time screen.
Page 732 1. Check for other alarms to determine how critical the alarm is. Depending on the malfunction, the Node/Terminal may otherwise operate satisfactorily. 2. Replace the NCC/IDU. +2.5V Digital Supply (NCC) +2.5 volt digital supply out of tolerance. This is a warning alarm. Probable Cause Equipment malfunction. Vol. VI-B-6 Alcatel-Lucent...
Page 733 9500 MXC User Manual Recommended Actions 1. Check for other alarms to determine how critical alarm is. Depending on the malfunction, the node may otherwise operate satisfactorily. 2. Replace the NCC. -48V Supply (NCC/IDU) -48 volt supply out of tolerance. This is a warning alarm.
Page 734 4. If there are no other alarms, the ambient temperature is OK and the airflow is not restricted, then suspect the temperature sensing circuit. Replace the NCC/ IDU. Expansion NCC Communications Failure Can’t cooperate with expansion NCC. This is a major alarm. Vol. VI-B-8 Alcatel-Lucent...
Page 735 9500 MXC User Manual Probable Cause Expansion cable unplugged or equipment malfunction. Recommended Actions Check the cable. Replace the affected NCC. Fan Failure (NCC) FAN plug-in alarm. This is a warning alarm. Probable Cause FAN plug-in malfunction, most likely a failure of one of its two axial fans.
Page 736 3. If the alarm is permanent, and the Flash Card Failure alarm is not active, replace the NCC/IDU. Additional Information A checksum is used to determine configuration status during power-up and software reloads. It may also be prompted during a reconfiguration. Vol. VI-B-10 Alcatel-Lucent...
Page 737 9500 MXC User Manual Configuration Not Supported (All) Configuration is not compatible with the hardware or its licensed capacity. This is a major alarm. Probable Cause 1. Incorrect Node plug-in installed for the configuration, such as DAC 16x, AUX, or a RAC installed in a slot configured for a DAC 155o.
Page 738 Summary screen, then configure the plug-in. TDM Clock Locked to NCC TDM clock is locked to the NCC. This is a warning alarm. Probable Cause TDM bus clock has been locked to the NCC using the lock command in CT System Controls. Vol. VI-B-12 Alcatel-Lucent...
Page 739 9500 MXC User Manual Recommended Actions To remove the alarm, remove the lock. Additional Information This alarm will only present when an NPC has been installed and the lock is applied. Circuit Loopback Circuit loopback has been applied. This is a warning alarm.
Page 740 Check the setup and operation of the relevant DAC plug-in. RAC/Radio Alarms Fuse Blown RAC fuse supplying -48 Vdc to ODU has blown. This is a critical alarm. Probable Cause 1. Short circuit on the ODU cable. Vol. VI-B-14 Alcatel-Lucent...
Page 741 9500 MXC User Manual 2. Component failure (short circuit) within the ODU. Recommended Actions 1. Disconnect the ODU cable at the RAC front panel and use a multimeter to check the resistance between inner and outer conductors of the ODU cable. It should measure approximately 0.3 Megohms.
Page 742 Tx. Tx muting can be checked in the CT Performance screen. Demodulator Failure (RAC) No communications with the demodulator. This is a critical alarm. Probable Cause Equipment or process malfunction. Recommended Actions Check for other alarms: Vol. VI-B-16 Alcatel-Lucent...
Page 743 9500 MXC User Manual • If there are no other alarms except downstream Demodulator Not Locked, and path warning alarms, reboot (power-off, pause, power on). • If other hardware alarms are present, check for a common cause, such as an NCC power supply or process failure.
Page 744 ODU connector, or at the ODU end of the cable. Inadvertently shorting the inner to outer will blow the surface-mounted PCB fuse on the RAC, which is not a field replaceble item. Repair will not be covered by warranty. Vol. VI-B-18 Alcatel-Lucent...
Page 745 9500 MXC User Manual IF Temperature Modem / IF temperature out of tolerance. This is a warning alarm. Probable Cause 1. The ODU is faulty, either with an overheating problem or with a faulty temperature sensor. 2. Environmental temperature excessive. The ambient must not exceed 55 (131 F), which is a shaded temperature limit (no solar gain).
Page 746 Detected Tx Power should be within 2 dB (typically within 1 dB) of the Tx power setting in a RAC Plug-ins screen when ATPC is disabled. In situations where ATPC is selected, refer to the commissioning record for guidance on a normal Tx power indication. Vol. VI-B-20 Alcatel-Lucent...
Page 747 9500 MXC User Manual Transceiver RX Temperature Transceiver RX temperature is out of range. This is a warning alarm. Probable Cause 1. The ODU is faulty with an overheating problem or a faulty temperature sensor. 2. ODU temperature excessive. Recommended Actions 1.
Page 748 • If an AUX plug-in is configured for the link, check the Auxiliary Channel Clock Fail alarm(s). If active, it also indicates loss of the overhead channel. • If there are no RAC/Radio or ODU alarms to indicate a local process or Vol. VI-B-22 Alcatel-Lucent...
Page 749 9500 MXC User Manual component failure, check alarms at the remote site. • Check to see if the communications failure is a both-way or one-way problem. If both-way, the problem is more likely to be within an NCC/ IDU. If one-way the problem is more likely to be within one of the ODUs or RAC/Radios at the mux (Tx) or demux (Rx) stages.
Page 750 Bus facing digital loopback is active. This is a warning alarm. Probable Cause Digital Loopback has been selected in CT System Controls. Recommended Actions To remove the alarm, remove the loopback. TX Synthesiser Not Locked Transmitter is not on frequency. This is a critical alarm. Vol. VI-B-24 Alcatel-Lucent...
Page 751 9500 MXC User Manual Probable Cause Equipment malfunction. Recommended Actions Confirm that transmitter power has been muted using the Detected Tx Power measurement in the CT Performance screen. Replace the ODU. Additional Information This alarm will mute the transmitter to prevent spurious transmission.
Page 752 RAC. If the ODU Tx Synth Not Locked alarm is also active it confirms a fault with the RAC 10 MHz clock. ODU TX Cable IF Synth Not Locked ODU TX cable IF synthesiser not locked. This is a critical alarm. Probable Cause Equipment malfunction. Vol. VI-B-26 Alcatel-Lucent...
Page 753 9500 MXC User Manual Recommended Actions Replace the ODU. Additional Information An ODU TX cable IF synthesiser failure affects all communications to the remote-end terminal. Remote end path alarms (BER, ES, SES, ESR, and SESR) will also be on. ODU TX Cable Unplugged Cannot detect ODU cable.
Page 754 Always check upstream, towards the ODU, path and remote radio, to ascertain the cause. The demodulator is located in the RAC. An unlocked demodulator will activate downstream path failure and path warning alarms. Tuner Not Locked Receive path tuner has failed. This is a critical alarm. Vol. VI-B-28 Alcatel-Lucent...
Page 755 9500 MXC User Manual Probable Cause Equipment malfunction. Recommended Actions Reboot (power off, pause, power on). If the alarm remains, replace the ODU. Additional Information The Tuner supports I/Q demodulation. Failure will affect all receive traffic. Downstream alarms will be active: Demodulator Not Locked, ODU Cable Modulator Not Locked, RAC Cable Demodulator Not Locked, and Rx path failure and warning alarms.
Page 756 ESR (errored second ratio) is the ratio of ES to total seconds in available time during a fixed measurement interval. For 9500 MXC the measurement interval is 60 seconds, and the ESR alarm threshold is set at 20%.
Page 757 SESR is the ratio of SES to total seconds in available time during a fixed measurement interval. For 9500 MXC the measurement interval is 60 seconds, and the alarm threshold is 10 percent. BER Threshold Exceeded...
Page 758 Rain fade is the likely cause of fade for links 13 GHz and higher. Diffraction and multipath/ducting for links 11 GHz and lower. If these alarms are persistent, there could be a problem with the link design or original installation. Vol. VI-B-32 Alcatel-Lucent...
Page 759 9500 MXC User Manual Check that all other link health indicators are normal before investigating an interference problem. Then check for any new link installations in the same geographical area, on the same frequency band, which coincide with the onset of BER alarms.
Page 760 ODU temperature alarms and/or an abnormal Forward Power measurement. Noise and errors may also be introduced on the transmitted signal, which may show as abnormal BER and ES figures at the remote end. Vol. VI-B-34 Alcatel-Lucent...
Page 761 9500 MXC User Manual Traffic Path Down The radio path is down. True for non-protected and for protected/diversity configurations. This is a critical alarm. Probable Cause Path loss or equipment malfunction. Recommended Actions 1. Check for path loss. • Traffic will be affected in both directions.
Page 762 Recommended Actions For a 9500 MXC Node, withdraw the DAC from its backplane, pause, and re-insert. If the alarm persists, replace the DAC. For a Terminal, reboot (power off, pause, power on). If the alarm persists, replace the IDU. Additional Information Depending on the DAC/Trib, the LIU function includes selection of E/DS rate, balanced/unbalanced, and line impedance.
Page 763 9500 MXC User Manual the AIS signal, or upstream of that equipment. In this user-enabled instance, AIS can be used to test traffic or alarm continuity on uncommissioned (non-traffic carrying) tribs, or to send a signal downstream to indicate traffic has been interrupted (for example, a service check is being performed).
Page 764 RAC is in diagnostic mode. Lock(s) set in the System/Controls screen. Recommended Actions Remove the lock(s). RX Manual Lock A receive diagnostic is active. This is a warning alarm. Probable Cause RAC is in diagnostic mode. Lock(s) set in the System/Controls screen. Recommended Actions Remove the lock(s). Vol. VI-B-38 Alcatel-Lucent...
Page 765 9500 MXC User Manual Trib n LOS Loss of signal on a commissioned tributary. This is a critical alarm. Probable Cause The failure may be within the attached equipment, the trib cable, or the radio. Recommended Actions 1. Check for alarms on trib-attached equipment, which may indicate loss of signal input from this source.
Page 766: Aux Alarms
Terminal. This is a warning alarm. Probable Cause AUX alarm input is active. Recommended Actions Investigate the cause of the activating event. Additional Information This alarm draws attention to a changed, active state on a configured AUX alarm Vol. VI-B-40 Alcatel-Lucent...
Page 767 9500 MXC User Manual input. Auxiliary Channel (n) Clock Failure Auxiliary channel clock failure, where ‘n’ may be 1 to 3 for a Node, or 1 for a Terminal. This is a warning alarm. Probable Cause No clock has been detected on an auxiliary port configured for synchronous data.
Page 768 Unable to program the clock generator. This is a critical alarm. Probable Cause Equipment malfunction. Recommended Actions 1. Check for other alarms to determine how critical the alarm is. Depending on the malfunction, the link may otherwise operate satisfactorily. 2. Replace the NPC. Vol. VI-B-42 Alcatel-Lucent...
Page 769 9500 MXC User Manual Additional Information The clock generator sets the timing for the FPGA. +5V Digital Supply (NPC) +5 volt digital supply out of tolerance. This is a warning alarm. Probable Cause Equipment malfunction. Recommended Actions 1. Providing the NCC is maintaining supply to the node (is not alarmed), replace the NPC.
Page 770 3. Check the NCC -48 Vdc alarm, and the ODU -48 V supply in the CT Performance screen. • If all indications match, the power supply for the node is at fault. Confirm with a voltmeter check. Vol. VI-B-44 Alcatel-Lucent...
Page 771 9500 MXC User Manual • If the supply voltage is correct, suspect the voltage sensor circuit in the NPC. Replace the NPC. Additional Information A node will operate to specification with a supply voltage between -40.5 and -60 Vdc. Providing the NCC is maintaining power supply to the node, an NPC may be replaced without affecting traffic.
Page 772 DAC ES / DAC GE channel data looped back to radio path. This is a warning alarm. Probable Cause A radio facing (bus facing) loopback has been established on a DAC ES / DAC GE channel using commands in the CT System/Controls screen. Vol. VI-B-46 Alcatel-Lucent...
Page 773 9500 MXC User Manual Recommended Actions To remove the alarm, deselect the loopback. Port Loopback Active DAC ES port data looped back to channel/radio path. This is a warning alarm. Probable Cause A channel/radio facing (TDM bus facing) loopback has been established on a DAC ES port using commands in the CT System Controls screen.
Page 774 Additional Information Switch packet errors are determined over a DAC ES / DAC GE link, which may exist across multiple radio paths; error checking is between local and remote DAC ES / DAC GE plug-ins. Vol. VI-B-48 Alcatel-Lucent...
Page 775 9500 MXC User Manual High switch packet errors will reduce Ethernet traffic throughput, which in turn may raise Dropped Frame alarms, particulary so where the available bandwidth was already limited. Link Failure (DAC ES, DAC GE) The DAC ES / DAC GE Ethernet port is down. This is a warning alarm.
Page 776 There is a version mismatch in the CPU software. Recommended Actions DAC GE requires SW release 3.1 or later. SW must be upgraded to to 3.4 or later to secure access to RWPR and to advanced link aggregation. Replace the DAC GE. Vol. VI-B-50 Alcatel-Lucent...
Page 777 9500 MXC User Manual Link Down A channel link in the DAC GE is down. This is a major alarm. Probable Cause Traffic received on the alarmed channel is errored. The errors may be caused by equipment/circuit malfunction or radio path degradation.
Page 778 A ring lock has been established using commands in the CT System/Controls screen. Recommended Actions To remove the alarm, deselect the lock(s). RDI In Remote degrade/defect indication in this section. This is a major alarm. Probable Cause Problem with the transmitted signal. Vol. VI-B-52 Alcatel-Lucent...
Page 779 9500 MXC User Manual Recommended Actions Check for other alarms. Replace the DAC 155oM or its optical transceiver. Additional Information Indicates a remote degrade/defect in this section. K2[6..8] = "110" for 3 frames. This alarm is returned to the transmitting-end (local) mux upon detection at the remote-end mux of an incoming signal degrade/defect.
Page 780 Loss of Frame (LOF) alarm detected in the regenerator. This is a critical alarm. Probable Cause Pier equipment malfunction. Recommended Actions Check presence of other alarms to help determine if the problem is cable or equipment based. Vol. VI-B-54 Alcatel-Lucent...
Page 781 9500 MXC User Manual Check remote-end mux/regenerator operation. Additional Information Occurs when an OOF state persists, typically for 3 mS. Clears when an in-frame condition exists continuously - typically 3 milliseconds. Out of Frame (OOF) alarm detected in the regenerator. This is a critical alarm.
Page 782 Container x RDI Remote degrade/defict indication (RDI) in container x. This is a minor alarm. Probable Cause There is a problem with the transmitted signal in this container. Recommended Actions Check for other higher-level alarms, such as RDI-in. Vol. VI-B-56 Alcatel-Lucent...
Page 783 9500 MXC User Manual Replace the DAC 155oM. Additional Information This alarm is returned to the transmitting-end (local) mux upon detection at the remote-end mux of an incoming LOS, LOF, or AIS defect. Container x RPSLM Receive Path Signal Label Mismatch (RPSLM) for container x. Received C2 not equal to Expected C2 byte value.
Page 784: Informational Events
AIS Transmitted AIS is being transmitted to customer connected equipment. The log entry includes a reference to the affected tributary. Alarm Output 1 Activated Alarm output one has been activated. The note field indicates if the output circuit Vol. VI-B-58 Alcatel-Lucent...
Page 785 9500 MXC User Manual is high or low. Alarm Output 1 Deactivated Alarm output one has been deactivated. The note field indicates if the output circuit is high or low. Alarm Output 2 Activated Alarm output two has been activated. The note field indicates if the output circuit is high or low.
Page 786 CT User Logged Off User logged off from the terminal or the session expired. Includes an indication if the user logged off or the session expired. CT User Logged On User logged on to the terminal. Vol. VI-B-60 Alcatel-Lucent...
Page 787 9500 MXC User Manual Date / Time Changed A user has changed the date and/or the time on the INU. Date/Time Changed By SNTP The date/time on the INU has been changed by SNTP. Event Action Accepted Event action accepted.
Page 788 Ring Manual Mode Enabled The manual ring wrap or unwrap mode has been configured by the user. The log entry serves as a warning that no automatic ring switching will take place while this mode is active. Vol. VI-B-62 Alcatel-Lucent...
Page 789 9500 MXC User Manual Rx Performance Monitoring Reset The Rx performance monitoring values for RSSI maximum and minimum have been reset. Set Power Out of Range The Tx power set was above the maximum power or below the minimum power capabilities.
Page 790 User Authentication Enabled User authentication enabled. User Authentication Failed User authentication failed. User Authentication Successful User authentication successful. User Password Admin Reset User password admin reset. Watch Dog Expired The INU has detected that some processes are not responding. Vol. VI-B-64 Alcatel-Lucent...
Page 791 9500 MXC User Manual 3DB 23063 ADAA - Rev 004 July 2007 Vol. VI-B-65...
Page 793: Appendix C. Inu/Inue And Idu Connector And Cable Data
• NMS Connectors and Cables • Auxiliary and Alarm Connectors and Cables 9500 MXC tributary, auxiliary and NMS cables are not to be routed with any AC mains power lines. They are also to be kept away from any power lines which cross them.
Page 794 Ensure correct orientation of the Mini RJ-21 connector before pushing it home. This can be checked by the scalloped key to one side of the connector. Additionally, a trib cable supplied by Alcatel-Lucent has the cable exiting to the right side when viewed from the front...
Page 795 9500 MXC User Manual Figure C-2 shows the cable label data. Unbalanced Cable Label Data Figure C-2. Label arrow towards the DATA1/9 BNC shows data out (DAC Tx) Label arrow away from DATA1/9 the BNC shows data in (DAC Rx)
Page 796 Crossover cable assemblies are used to interconnect one DAC or IDU RJ-45 port to another. • Mini RJ-21 to 8xRJ-45 Connectors, Crossover, 1m, Part No: 3CC52037AAAA • Mini RJ-21 to 8xRJ-45 Connectors, Crossover, 5m, Part No: 3CC52041AAAA Vol. VI-C-4 Alcatel-Lucent...
Page 797 9500 MXC User Manual Figure C-4 shows the assembly. Each assembly supports up to eight tribs. Two cable assemblies are required per DAC 16x if more than 8xE1/DS1tribs are to be connected. DAC 16x Mini RJ-21 to RJ-45 Balanced Trib Cable Assembly for 8xE1/DS1 Tribs Figure C-4.
Page 798 Figure C-6 shows the cable data for the straight cable assembly. DAC 16x Mini RJ-21 to RJ-45 Balanced Straight Cable Data Figure C-6. Vol. VI-C-6 Alcatel-Lucent...
Page 799 9500 MXC User Manual Figure C-7 shows the cable data for the crossover cable assembly. DAC 16x Mini RJ-21 to RJ-45 Balanced Crossover Cable Data Figure C-7. 3DB 23063 ADAA - Rev 004 July 2007 Vol. VI-C-7...
Page 800 Figure C-8 shows the assembly. Each assembly supports up to 8 tribs. Two cable assemblies are required per DAC 16x if more than 8xE1/DS1tribs are to be connected. DAC 16x Mini RJ-21 to Wire Wrap Cable Assembly Figure C-8. Vol. VI-C-8 Alcatel-Lucent...
Page 801 9500 MXC User Manual Figure C-9 shows the color coding for the cable pairs. The 1/9 in Figure C-9 indicates it is for trib 1 if the cable assembly is used with the trib 1-8 connector, or trib 9 if used with the trib 9-16 connector. Similarly for 2/10, 3/11 and so on, up to 8/16.
Page 802 Tributary 2 transmit tip (center) Common Ground Tributary 2 transmit ring (shield) Tributary 5 transmit tip (center) Common Ground Tributary 5 transmit ring (shield) Tributary 6 transmit tip (center) Common Ground Tributary 6 transmit ring (shield) Tributary 1 receive tip (center) Vol. VI-C-10 Alcatel-Lucent...
Page 803 9500 MXC User Manual Function Common Ground Tributary 1 receive ring (shield) Tributary 2 receive tip (center) Common Ground Tributary 2 receive ring (shield) Tributary 5 receive tip (center) Common Ground Tributary 5 receive ring (shield) Tributary 6 receive tip (center)
Page 804 Tributary 10 transmit ring (shield) Tributary 13 transmit tip (center) Common Ground Tributary 13 transmit ring (shield) Tributary 14 transmit tip (center) Common Ground Tributary 14 transmit ring (shield) Tributary 9 receive tip (center) Common Ground Tributary 9 receive ring (shield) Vol. VI-C-12 Alcatel-Lucent...
Page 805 9500 MXC User Manual Function Tributary 10 receive tip (center) Common Ground Tributary 10 receive ring (shield) Tributary 13 receive tip (center) Common Ground Tributary 13 receive ring (shield) Tributary 14 receive tip (center) Common Ground Tributary 14 receive ring (shield)
Page 806 • DAC 4x and IDU RJ-45 to RJ-45 Crossover Cable on page C-17 • DAC 4x and IDU RJ-45 to Wire Wrap Cable Assembly on page C-18 • DAC 4x and IDU RJ-45 Connector Pin Assignments on page C-19 Vol. VI-C-14 Alcatel-Lucent...
Page 807 9500 MXC User Manual DAC 4x and IDU RJ-45 to BNC Cable Assembly The assembly is provided as a kit of three cables. Each kit provides: • One RJ-45 to 2 x BNC female, 0.5m long. Refer to Figure C-11.
Page 808 Straight cable assemblies are used when connecting to RJ-45 patch panels, which have a built-in crossover function. DAC 4x RJ-45 to RJ-45 Straight Cable Connections Figure C-12. Function Receive Ring Receive Tip Optional Ground Transmit Ring Transmit Tip Optional Ground Ground Ground Vol. VI-C-16 Alcatel-Lucent...
Page 809 9500 MXC User Manual DAC 4x and IDU RJ-45 to RJ-45 Crossover Cable Connectors are wired such that Receive Ring and Tip at one end connect to Transmit Ring and Tip respectively, at the other. Refer to Figure C-13. Pins 3, 6, 7, 8 remain the same.
Page 810 Receive Ring White / Orange Receive Tip Orange / White Optional Ground White / Green Transmit Ring Blue / White Transmit Tip White / Blue Optional ground Green / White Ground White / Brown Ground Brown / White Vol. VI-C-18 Alcatel-Lucent...
Page 811 9500 MXC User Manual DAC 4x and IDU RJ-45 Connector Pin Assignments Table C-4 shows the pin assignments for each front panel RJ-45 trib connector. Refer to Figure C-14 for connector pin numbering. TX or Transmit refers to an output from the IDU and specifies towards the user.
Page 812 • Ethernet cable, RJ-45 to RJ-45, 5m: Part No: 3CC52006AAAA • Ethernet cable, RJ-45 to RJ-45, 15m: Part No: 3CC52007AAAA The crossover RJ-45 to RJ-45 cables available for the DAC 4x and IDU are not suitable for use as crossover Ethernet cables. Vol. VI-C-20 Alcatel-Lucent...
Page 813 • NMS 10/100Base-T Connector on page C-21 • Maintenance V.24 Connector on page C-22 NMS 10/100Base-T Connector The NMS connector provides Ethernet access for 9500 MXC CT. Pin assignments represent industry-standard LAN cable assembly for a 10/100Base-T, RJ-45 connector. Straight Ethernet cables are available as optional accessories: •...
Page 814 Orange Maintenance V.24 Connector The V.24 connector provides serial data access for 9500 MXC CT. One 2 meter industry-standard RJ-45 to DB-9 V.24 Maintenance Cable is included with every INU/IDU, Part No: 3CC52000AAAA. A 5 meter cable is available as an option, Part No: 3CC52001AAAA.
Page 815 9500 MXC User Manual Auxiliary and Alarm Connectors and Cables Data is included for AUX Plug-in (Node) IDU (Terminal) auxiliary interfaces and cable-sets. Alarm and Auxiliary cables should not terminate to equipment outside the shelter or building. Use approved surge suppression equipment when connecting to un-protected external inputs and outputs.
Page 816 AUX Data Cable: Async, HD26 to Wirewrap, 2 m Part No: 3CC52109AAAA AUX HD26, 2M, Async, Wirewrap Cable Data Table C-7. Vol. VI-C-24 Alcatel-Lucent...
Page 817 9500 MXC User Manual AUX Data Cable: Sync, HD26 to Wirewrap, 2 m Part No: 3CC52110AAAA AUX HD26, 2M, Sync, Wirewrap Table C-8. 3DB 23063 ADAA - Rev 004 July 2007 Vol. VI-C-25...
Page 818 AUX Data Cable: Async, HD26 to 3 X DB9, 1 m Part No: 3CC52111AAAA AUX HD26 TO 3 X DB9, 1M, Async Table C-9. Vol. VI-C-26 Alcatel-Lucent...
Page 819 9500 MXC User Manual AUX Data Cable: Sync, HD26 to 3 X DB9, 1 m Part No: 3CC52112AAAA AUX HD26 to 3 X DB9, 1m, Sync Table C-10. 3DB 23063 ADAA - Rev 004 July 2007 Vol. VI-C-27...
Page 820 AUX Data Cable: Async, AUX HD26 to AUX HD26, 1 m Part No: 3CC52113AAAA AUX TO AUX, HD26, 1M, ASYNC Table C-11. Vol. VI-C-28 Alcatel-Lucent...
Page 821 9500 MXC User Manual AUX Data Cable: Sync, AUX HD26 to AUX HD26, 1 m Part No: 3CC52114AAAA AUX TO AUX, HD26, 1m, Sync Table C-12. 3DB 23063 ADAA - Rev 004 July 2007 Vol. VI-C-29...
Page 822 TTL Input 2 Red/Orange Relay 1 Pole/TTL Input 6 Red/Green Relay 2 NC Green/Red Relay 2 NO Orange/White Relay 3 Pole/TTL Input 4 White/Orange Relay 4 NC White/Green Relay 4 NO Green/White Wire White/Blue, Blue/White Colors Not Used: Vol. VI-C-30 Alcatel-Lucent...
Page 823 9500 MXC User Manual IDU Auxiliary Connector and Cable Data Refer to: • IDU AUX Cable Data: Async, DB9 to Wirewrap, 2 m on page C-31 • IDU AUX Cable Data: Sync, DB9 to Wirewrap, 5 m on page C-32 •...
Page 824 Part No: 3CC52106AAAA IDU AUX, DB9, 5M, SYNC, WIREWRAP Table C-15. IDU AUX Cable Data: Async, IDU AUX DB9 to IDU AUX DB9, 1 m Part No: 3CC52103AAAA IDU AUX to IDU AUX, DB9, 1m, Async Table C-16. Vol. VI-C-32 Alcatel-Lucent...
Page 825 9500 MXC User Manual IDU AUX Cable: Sync, IDU AUX DB9 to IDU AUX DB9, 1 m Part No: 3CC52104AAAA IDU AUX TO IDU AUX, DB9, 1M, SYNC Table C-17. IDU AUX Alarm I/O Cable: HD15 to Wirewrap, 5 m This cable is identical to the Node (AUX Plug-in) Alarm I/O cable.
Page 827 Appendix D. 9500 MXC NMS Networking Essentials This appendix provides an overview of the characteristics of a 9500 MXC management network and guidance on IP addressing for small to medium size networks. Refer to: • General Considerations on page D-1 •...
Page 828 9500 MXC node or terminal. Unless otherwise mentioned, reference to the node in this appendix includes the terminal. • Each 9500 MXC node is hosted behind its Ethernet NMS port IP address: the node address is the Ethernet port address.
Page 829 CT screen, changes to the newly entered address once the Send button is clicked. • Over 9500 MXC radio links a proprietary protocol is used for network management Communication transport. As a consequence, network addressing rules for two routers (9500 MXC Parameters nodes) connected on the same radio network do not apply.
Page 830 LAN IP address and routing rules apply. • The CT PC must be hosted on the same LAN as the 9500 MXC it is connected to, meaning the TCP/IP settings within the CT PC must be set to have: The same network portion IP address as the 9500 MXC Node/Terminal;...
Page 831 Dynamic routing would normally be used in preference to static routing (it easier to set and maintain). • Each 9500 MXC node counts as just one IP hop (one metric hop) for RIP hop count purposes, and applies regardless of whether single IP addressing or interface IP addressing is selected.
Page 832 Rules, Hints, and Tips • Dynamic routing is recommended for 9500 MXC star/tree networks, except where just one or a few 9500 MXC links are to be installed in an existing network, which uses static routing. • Dynamic routing is a requirement for 9500 MXC ring networks.
Page 833 NOC LAN segments. • The address range of 192.168.255.0 to 192.168.255.255 must not be used as it is used for internal (embedded) addressing within 9500 MXC. Example Networks The following examples provide guidance on IP addressing and routing options for 9500 MXC Nodes.
Page 834 PC TCP/IP settings to support access to Node A. The default gateway avoids the need to enter a static route for Node A on the PC (using DOS commands). 9500 MXC Node Routing Example 1 Figure D-1. 9500 MXC Nodes A and B...
Page 835 9500 MXC User Manual Small Four Node Network Figure D-2 shows a small 9500 MXC-only network. Both static and dynamic routing options are shown. • Class C network addressing is used. • This example shows that dynamic routing is a much easier option.
Page 836 Static Routing Screen for Node B in Figure D-2 Figure D-3. Lyons Dpt 192.168.2.1 Vol. VI-D-10 Alcatel-Lucent...
Page 837 9500 MXC User Manual Network with Static and Default Gateway Routing These examples also show NOC NMS settings. The default gateway option can be used in conjunction with static routing to reduce data entry requirements and support flexible adding/changing of PC connections at the NOC LAN •...
Page 838 Link 1 NMS 0.0.0.0 Default Gateway: Enabled Interface Next Hop ----- ----- NOC TCP/IP Properties IP Address Subnet Mask Default Gateway Server: 192.168.4.2 255.255.255.0 192.168.4.1 PC1: 192.168.4.3 255.255.255.0 192.168.4.1 PC2: 192.168.4.4 255.255.255.0 192.168.4.1 PC3: 192.168.4.5 255.255.255.0 192.168.4.1 Vol. VI-D-12 Alcatel-Lucent...
Page 839 9500 MXC User Manual Static Routing with Default Gateways: NOC LAN off Router Figure D-5. 192.168.1.1 192.168.5.1 255.255.255.0 Node A 255.255.255.0 Node D Link 1 Link 1 Radio Radio 192.168.4.1 Link 1 255.255.255.0 Link 2 Radio Radio Node B Node C...
Page 840 Complex Networks Figure D-6 on page D-15 shows a more complex network of 9500 MXC and other radio terminals. In this example it has been assumed that the other terminals are static routed and that the 9500 MXC nodes are to be similarly configured.
Page 841 9500 MXC User Manual 9500 MXC Node Static Routing Example 3 Figure D-6. 9500 MXC Nodes: A, B, C, D Other Radios in Network: U, V, X, Y CT PC 192.168.51.1 192.168.50.1 255.255.255.0 Terminal V Terminal Y 255.255.255.0 Ethernet Radio Radio 192.168.3.1...
Page 842 Static Routing Screen for Node A in Figure D-6 Figure D-7. Johns Road [Link 2] NMS Johns Road [Link 2] NMS Johns Road [Link 2] NMS Johns Road [Link 2] NMS 192.168.1.1 Vol. VI-D-16 Alcatel-Lucent...
Page 843 9500 MXC User Manual Split Static and Dynamic Routing Example Figure D-8. 9500 MXC Nodes: A, B, C, D Other Radios in Network: U, V, X, Y Greyed blocks indicates static routing : ungreyed, dynamic 10.10.19.6 255.255.255.0 10.10.17.3 Terminal V Terminal Y 10.10.18.2...
Page 844 Interface Addressing Screen for Node A in Figure D-8 Figure D-9. 10.10.16.2 Static Routing Screen for Node A in Figure D-8 Figure D-10. 10.10.16.2 Vol. VI-D-18 Alcatel-Lucent...
Page 845 9500 MXC User Manual Ring Network Figure D-11 shows 9500 MXC Nodes in a ring network. All nodes in a 9500 MXC ring must be configured for one of the dynamic routing options, OSPF or RIP. Single IP Addressing would normally be used. An exception would be where the north-bound interface (Node A) must interface with a network which is static routed.
Page 846 Vol. VI-D-20 Alcatel-Lucent...
Page 847 Appendix E. Node Capacity Rules The TDM bus capacity and the access to it determines the traffic handling maximums for a 9500 MXC node. These capacity maximums apply equally to the INU and INUe. • The primary determinant of node capacity is its bus capacity.
Page 848 100xE1 Bus Capacity RAC 30 16xE1 8xE1 RAC 30 DAC 16x 8xE1 For a simple aggregation node using a single RAC 30V3 towards the network core (75xE1, 100xDS1 or STM1/OC3 maximums), bus capacity issues will not arise. Vol. VI-E-2 Alcatel-Lucent...
Page 849 9500 MXC User Manual However, capacity issues must be considered where co-channel operation is required, given the available RAC 40 capacity options of: • Co-channel 64/75xE1 • Co-channel 84/100xDS1 • Co-channel STM1/OC3 As one INU/INUe has a maximum backplane bus capacity of 100xE1, 128xDS1,...
Page 850 • Rings with point-to-point traffic overlay. See Rings With Pt-to-Pt Traffic Overlay on page E-6. Examples shown are for NxE1, or NxDS1 rings. While 9500 MXC may be used to implement an STM1/OC3 protected ring, the ring protection mechanism is performed within a paired SDH mux;...
Page 851 9500 MXC User Manual Rings Without Pt-to-Pt Overlay At the ring network nodes: • Each drop-insert circuit uses three bus timeslots. This may also be stated as: each drop-insert circuit uses the equivalent of one-and-one-half bus circuits. • Pass-through circuits use the standard two-timeslots, one for Tx and one for Rx (one circuit on the bus).
Page 852 • Where all traffic on the ring is ring-protected, the number of E1/DS1 circuits used on a 9500 MXC backplane equates to the number of circuits on the ring plus half the number of circuits drop-inserted on the backplane. The total must not exceed 100 or 128 respectively.
Page 853 9500 MXC User Manual Ring with Point-to-Point Overlay Figure E-6. Node A 32xE1 link Node G Node B 32xE1 links: Protected ring 64xE1 links: Point-to-point Node F Node C Node E 64xE1 link 32xE1 ring-protected traffic 32xE1 pt-to-pt traffic Point-to-point...
Page 854 P = Pt-to-Pt capacity (total dropped) = 32xE1 R = Ring capacity = 48xE1 d = Ring drop-insert capacity = 24xE1 Bus capacity used = 32 + 48 + 24 = 104, which is not valid. Refer to Figure E-8. Vol. VI-E-8 Alcatel-Lucent...
Page 855 9500 MXC User Manual Example Ring Node with Overlay at Maximum Bus Capacity Figure E-8. 48xE1 Ring 64xE1 64xE1 16xE1 48xE1 Pt-to-Pt Drop-Insert DAC ES DAC 16x DAC 16x DAC 16x Bus capacity required = 104xE1 When checking capacity validity, always first check the capacity required at the node which is drop-inserting the highest capacity.
Page 856 Vol. VI-E-10 Alcatel-Lucent...
Page 857 Appendix F. System Block Diagrams and Descriptions This chapter provides high-level block diagrams and system descriptions for 9500 MXC Node in non-protected, hot-standby, diversity and ring configurations. For the plug-ins, information on function, interfaces, and configurable options is provided in Volume II, Chapter 3.
Page 858 • Backplane on page F-4 • TDM Bus on page F-4 • RAC 30 on page F-4 • RAC 40 on page F-5 • Rx and Tx Diversity Bus on page F-8 • DAC on page F-8 Vol. VI-F-2 Alcatel-Lucent...
Page 859 Compact Flash The CompactFlash card plugs into the right side of the NCC, or at the rear of the IDU (9500 MXC Terminal). It holds the system configuration (CT config.), system software (embedded software) and, for the 9500 MXC Node, the licensed level.
Page 860 311 MHz IF carrier. This IF is passed to the N-Plexer, where it is combined with telemetry and reference oscillator signals, plus 48Vdc power, to go to the ODU. Vol. VI-F-4 Alcatel-Lucent...
Page 861 9500 MXC User Manual RAC 30 Receive Receive traffic is carried on a 126 MHz IF from the ODU. It is extracted at the N-Plexer, along with telemetry data, which goes directly to the NCC. The 126 MHz IF is passed to an analog to digital converter via a gain controlled amplifier, which compensates for losses in the ODU cable.
Page 862 The 126 MHz signal is passed to a gain controlled amplifier, which compensates for losses in the ODU cable. Two data streams are taken from the amplifier: • One is directed to the demodulator via an A/D converter. Vol. VI-F-6 Alcatel-Lucent...
Page 863 9500 MXC User Manual • The other is directed to the XPIC OUT connector on the front panel. This is the sample of the received signal, which are used by the paired RAC 40 for its use in removing signal corruption caused by lack of polarization discrimination.
Page 864 E1 (or DS1) data format, and passed to the LIU. The Bus Mux also supports AIS insertion, and a PRBS generator and receiver function for trib BER measurement The PRBS function is a scheduled capability. Vol. VI-F-8 Alcatel-Lucent...
Page 865 9500 MXC User Manual ODU 300 ODU 300 platforms for 6 to 15 GHz, and 18 to 38 GHz, differ in respect of the synthesizers used to derive the signal sources for the Tx and Rx mixer stages. For the 6 to 15 GHz ODU, separate synthesizers are used. For 18 to 38 GHz, a common synthesizer is used.
Page 866 Tx/Rx split. The split options provided are based on ETSI and FCC plans for each frequency band. The actual frequency range per band and the allowable Tx/Rx splits are range-limited within 9500 MXC to prevent incorrect user selection. A power monitor circuit is included in the common port of the diplexer assembly to provide measurement of transmit power.
Page 867 9500 MXC User Manual INU Protected or Diversity System Block Diagram with NPC Option Figure F-4. V.24 Maint. LAN 1-4 Backplane Ethernet Compact Switch Flash Timing -48Vdc DC-DC Processor Converter DAC 16x Monitoring Trib1 ODU Telemetry Supply rails FIFO -48Vdc...
Page 868 RAC. This switching from online primary Rx RAC to the secondary RAC is not hitless; there is a maximum 500 ms detection, acquisition and recovery period (service restoration time). The Tx diversity bus is not used for hot-standby. Vol. VI-F-12 Alcatel-Lucent...
Page 869 9500 MXC User Manual Hot Standby Protection Figure F-5. Tx PA Mute Online Online Primary RAC Secondary RAC TDM Bus Tx Diversity Bus Rx Diversity Bus Space Diversity Space diversity protection operation is identical to hot standby except for the use of two vertically separated antennas.
Page 870 RAC is missing/incorrect, or there is a software load failure. When either occurs, the transmit data is uplifted directly from the TDM bus by the secondary RAC. Frequency Diversity Figure F-6. Online Online Primary RAC Secondary RAC TDM Bus Tx Diversity Bus Rx Diversity Bus Vol. VI-F-14 Alcatel-Lucent...
Page 871 The east, west, clockwise and anti-clockwise descriptors are conventions used to describe and configure 9500 MXC ring operation. The physical implementation of a ring may be quite different. Wrapping can occur at the east-facing or west-facing RAC connections to the TDM bus. In this way, should a ring-break be due to a fault within a RAC/ODU, the failed RAC will not participate in the traffic re-direction.
Page 872 Break between Nodes B & C Primary ring wrapped to secondary at Node B Break No break Secondary ring wrapped to primary at Node C Pass-through circuits Local add Local drop Primary Secondary not used Secondary used Vol. VI-F-16 Alcatel-Lucent...
Page 873 9500 MXC User Manual 3DB 23063 ADAA - Rev 004 July 2007 Vol. VI-F-17...
Page 875 Glossary This section defines terms and acronyms used in the 9500 MXC documentation. 1+1 protected system Two ODUs and two IDUs are used at each end of a link to protect against transmission failure. If a data transmission fails on the operating ODU/IDU, it is transferred to the backup ODU/IDU.
Page 876 North (such as, horizontal direction); used in reference to antenna alignment. B3ZS Binary 3 zeros substitution. A “1” is substituted for every 3 zeros. B8ZS Binary 8 zeros substitution BAPT Bundesamtfur Post Und Telekommunikation (German Telecom Regulatory Agency) Alcatel-Lucent...
Page 877 9500 MXC User Manual aseband Processing Bose-Chaudhuri-Hochquenghem code A multilevel, cyclic, error-correcting, variable-length digital code used to correct errors up to approximately 25% of the total number of digits. beamwidth The beamwidth of an antenna is defined as the angle between the two half-power (-3 dB) points on either side of the main lobe of radiation (half power beamwidth).
Page 878 There are typically two community strings accommodated by a device, one for reading values and one for writing (setting) values. These are normally set to “Public” or “Private”, but can be set to other values as a form of security. Component Alcatel-Lucent...
Page 879 (capacity, frequency band, option) that was ordered by the customer. Digital to Analog 1) For 9500 MXC: Digital Access plug-in Card; 2) Digital to Analog Converter The abbreviation for decibel; the standard unit of measure for relative signal power.
Page 880 32.064 Mb/s, the Japanese T3 designator. ANSI digital signal level x 1) Data Terminal Equipment. Devices acting as data source, data sink, or both; 2) Date Terminal Equipment DTMF Dual Tone Multi-frequency Dual Link A protection mode also known as 2+0. Alcatel-Lucent...
Page 881 9500 MXC User Manual The main and standby radios are transmitting simultaneously and are tuned to different frequencies to avoid interference. Under normal operating conditions, the primary radio carries traffic for tributaries 1 through 8 and the standby radio carries traffic for tributaries 9 through 16. A fault detected in the traffic of the first eight tributaries results in an automatic switch of those tributaries to the standby radio, disabling tributaries 9 through 16.
Page 882 The amount of attenuation a link can suffer before link performance is effected. The amount of fade margin available on an operation link can be calculated as follows: (RX sensitivity – RSSI). Fan plug-in card for the 9500 MXC INU/INUe. FCAPS...
Page 883 9500 MXC User Manual Federal Communications Commission The Federal Communications Commission (FCC) is an independent United States government agency, directly responsible to Congress. The FCC was established by the Communications Act of 1934 and is charged with regulating interstate and international communications by radio, television, wire, satellite and cable. The FCC's jurisdiction covers the 50 states, the District of Columbia, and U.S.
Page 884 A microprocessor monitors the on-line circuitry and switches to the back-up circuitry if a failure is detected. Having the back-up powered-up means it is ready for immediate operational service. Alcatel-Lucent...
Page 885 Internet Control Message Protocol. The transport protocol used for ping requests. Indoor Chassis This is the chassis for the 9500 MXC Node, with backplane, into which the various plug-ins are installed. The IDC is a 1RU chassis. The IDCe (IDC expanded) is a 2RU chassis.
Page 886 A civil international organization established to promote standardized telecommunications. Intelligent Node Unit. 9500 MXC Node is a split-architecture platform comprising a direct-mount ODU and a rack-mounted indoor unit, connected by a single coaxial cable. The INU is a 1U chassis (the IDC) fitted with mandatory cards plus option cards. It supports up to three ODUs for three non-protected links, or one protected/diversity link and one non-protected link.
Page 887 9500 MXC User Manual Light Emitting Diode Indicator lights on the IDU’s front panel that give operating status and alarm information. Light Emitting Diode (LED) Indicator lights on the IDU’s front panel that give operating status and alarm information. Link A link is a RF path between two terminals.
Page 888 To send two or more signals over the same channel. Mute Mute the remote radio to stop it from transmitting. Multiplexer North Bound Interface Node Control Card Network Element Network Elements Level in the TMN model. Network operator The organization responsible for installing and maintaining a radio network. Alcatel-Lucent...
Page 889 Network Operations Center Node A 9500 MXC INU/INUe with one or more ODUs. Plug-in cards provide multiple link and tributary options. Capacity extends from 4xE1/DS1 to 2xSTM1/OC3. Modulation options extend from QPSK to 256QAM. Protection options support hot standby, space diversity, frequency diversity, or ring.
Page 890 A radio path refers to the path travelled by radio waves between transmitting and receiving devices. Personal Computer Printed Circuit Assembly printed circuit board Pulse Code Modulation Modulation in which a signal is sampled, quantized and then digized for transmission over a common transmission medium. Alcatel-Lucent...
Page 891 9500 MXC User Manual Personal Communications Service A set of capabilities that provides a combination of terminal mobility, personal mobility, and service profile management. Personal Digital Assistant Portable Document Format Plesiochronous Digital Hierarchy Personal Communications Service (PCS) A set of capabilities that provides a combination of terminal mobility, personal mobility, and service profile management.
Page 892 Phase Shift Keying R&D Research and Development Radio Access plug-in Card for the 9500 MXC INU/INUe. Rack A rack represents a physical storage unit in which a number of devices can be stored. At a large site, you may have several physical racks installed.
Page 893 9500 MXC User Manual The member of the radio installation team responsible for installing the antenna and cabling on the transmission tower. Radio Interface Module Routing Information Protocol RIP is used by IP network devices to automatically share information about their internal routing tables.
Page 894 If a fault occurs in the receiving end of the link, the traffic is switched to the standby radio without causing errors (hitless receive switching). As in Hot Standby mode, a fault detected in the online transmitter causes that transmitter to mute and the standby radio to unmute. Alcatel-Lucent...
Page 895 9500 MXC User Manual Structured Query Language Software-Software Compatibility Secure Sockets Layer Static Routing Static routing requires manual configuration of the routing table and any subsequent reconfiguration. They are normally used within simple networks or in networks where it is required for security purposes.
Page 896 Telnet is a common way to remotely control Web servers. Terminal A 9500 MXC IDU with associated ODU. Different versions are available for PDH, SDH or Ethernet traffic. TFTP rivial File Transfer Protocol...
Page 897 9500 MXC User Manual A program interrupt, usually caused by some exceptional situation in the user program. In most cases, the operation system performs some action, then returns control to the program. Used for event notification with SNMP. Trib Tributary A common semiconductor technology for building discrete digital logic Transistor-Transistor Logic.
Page 898 Volts Direct Current (Vdc) Typically used to express the external power supply voltage requirements. Virtual Private Network VSWR Voltage Standing Wave Ratio Wide Area Network Wireless Application Protocol Web-based Maintenance Terminal Cross-Polar Discrimination XPIC Cross Polarized Interference Cancellation Extensible Mark-up Language Alcatel-Lucent...
Page 899 Vol. IV-4-7 diagnostic Vol. II-6-10 Node Vol. II-1-5, Vol. II-3-1 alarms plug-in cards Vol. II-1-8 9500 MXC radio Vol. VI-B-1 ODUs Vol. II-1-13 Configuration Not Supported Vol. V-2-8 platforms Vol. II-1-2 CT Vol. V-2-16 radio alarms Vol. VI-B-1 Node Vol.
Page 900 ATPC Vol. II-6-7 ODU cable installation Vol. III-2-19 guidelines Vol. IV-7-20 cable assembly interference of Vol. IV-7-21 RJ-21 to wire wrap Vol. VI-C-8 RAC 40 Vol. II-3-105 cable connector settings Vol. IV-7-22 type N Vol. III-2-23 troubleshooting Vol. V-2-9 cable grounding Alcatel-Lucent...
Page 901 ODU cable Vol. III-2-21, Vol. III-2-22 losses Vol. IV-7-19 cable options commissioning ODU Vol. III-2-19 DAC protection tests Vol. V-1-15 cable support Vol. III-2-11 process Vol. V-1-1 capacity and bandwidth protection switching tests Vol. V-1-6 Node PDH and SDH Vol. II-3-6 before starting Vol.
Page 902 Vol. VI-A-8 connection exceptions Vol. IV-2-26 ring protection Vol. VI-A-11 connection options Vol. IV-2-3 ring traffic circuits Vol. VI-A-17 connection process Vol. IV-2-23 confirming connection via DHCP Vol. IV-2-21 ring wrapping Vol. VI-A-23 connection via V.24 dial-up Vol. IV-2-22 Alcatel-Lucent...
Page 903 DAC 155oM NMS transport Vol. IV-7-44 ring network Vol. VI-A-13 DAC 155oM trib ports Vol. II-3-42 procedure for installing Vol. IV-2-2 DAC 16x Vol. II-3-34 program folder for 9500 MXC license DAC 16x and DAC 4x configuration Vol. IV-4-8 Vol. IV-7-28 protection DAC 16x front panel Vol.
Page 904 Vol. IV-7-67 RJ-21 to wire wrap basic port settings Vol. IV-7-65 cable assembly Vol. VI-C-8 flow control Vol. IV-7-67 RJ-45 L2 link aggregation settings Vol. IV-7-61 cable connector, pin numbering link aggregation options and application Vol. VI-C-5 Vol. IV-7-76 Alcatel-Lucent...
Page 905 Vol. IV-10-1 DAC GE alarm hierarchy Vol. V-2-24 configuration Vol. IV-7-57 earthing data 9500 MXC indoor unit Vol. I-1-4 protection configuration Vol. IV-8-10 equal split coupler Vol. IV-7-18 date and time screen Vol. VI-A-20 equipment date/time discrepancies Vol. III-1-4 configuration Vol.
Page 906 ODU Vol. III-2-13 Vol. II-2-35 ODU cable Vol. III-2-21 CT login overview Vol. II-2-35 guard times Vol. II-3-93 front panel layout guidelines PDH and SDH IDUs Vol. II-2-7 RF exposure Vol. I-1-7 fuse Vol. II-2-7, Vol. II-2-22 viii Alcatel-Lucent...
Page 907 PDH & SDH traffic and auxiliary interfaces datapack Vol. III-5-18 Vol. II-2-3 IDU Vol. III-4-1 PDH and SDH Vol. II-2-1 overview for new 9500 MXC installation PDH tribs Vol. II-2-4 Vol. IV-3-7 platform layout and interoperation tools and equipment Vol. III-1-3 Vol.
Page 908 Vol. III-3-8 Vol. IV-8-10 IP addressing and routing options Vol. IV-10-2 link aggregation Vol. II-3-62, Vol. IV-7-76 link performance Vol. IV-15-27 load destinations software Vol. IV-13-2 Java Runtime Vol. IV-2-2 loading new 9500 MXC software Vol. IV-13-2 Alcatel-Lucent...
Page 909 locks safety timer operation Vol. IV-15-50 logos naming CT Vol. IV-1-4 module Vol. IV-7-26, Vol. IV-15-5 loopbacks naming a module Vol. IV-7-13 bus loopbacks Vol. IV-15-67 naming conventions circuit loopbacks Vol. IV-15-67 CT Vol. IV-1-8 digital Vol. IV-15-43 NCC Vol. II-1-8, Vol. II-3-19 IF Vol.
Page 910 Vol. IV-2-24, Vol. IV-14-1 path attachment procedure Vol. III-2-9 incorrect calculations Vol. V-2-7 cable disconnection at RAC Vol. III-3-10 reflections Vol. V-2-7 cable ground locations Vol. III-2-22 path problems cable grounding Vol. III-2-21 commissioned link Vol. V-2-6 Alcatel-Lucent...
Page 911 Vol. V-2-7 RAC 40 Vol. II-1-9 troubleshooting Vol. V-2-6 plug-in cards Vol. II-1-8 plug-ins Vol. II-3-15 9500 MXC CT installation Vol. IV-2-1 AUX Vol. II-3-66 CT PC hardware requirements Vol. IV-2-1 DAC Vol. II-3-32 CT PC software requirements Vol. IV-2-2 DAC 155oM Vol.
Page 912 CT Vol. IV-2-2 ring network Vol. VI-A-9 overview for new 9500 MXC installation protective grease Vol. IV-3-7 weather-protecting Vol. III-1-3 protected operation Vol. II-3-73 protection additional rules for 1+1 ring protection Vol. IV-8-7 alarm hierarchy Vol. V-2-18 additional rules for dual protection Vol. IV-8-6 plug-ins Vol.
Page 913 renaming protection configuration Vol. IV-7-4, module Vol. IV-15-5 Vol. VI-A-11 report protection controls operation Vol. IV-15-54 as built Vol. IV-5-1 protection locks Vol. IV-15-52 restricted access Vol. I-1-6 ring intersection Vol. II-3-83 RF exposure guidelines Vol. I-1-7 ring wrap forcing Vol. IV-15-54 ring super PDH Vol.
Page 914 Vol. II-6-6 status bar PDH & SDH traffic and auxiliary interfaces CT Vol. IV-1-1 Vol. II-2-3 status LEDs Vol. V-2-10 protected Vol. II-2-28 super PDH rings Vol. II-3-78 protected operation and rules Vol. IV-8-17 surface protection Vol. II-2-28 Alcatel-Lucent...
Page 915 criteria Vol. II-2-30 troubleshooting Vol. V-2-1 service restoration times Vol. II-2-33 antenna alignment Vol. V-2-6 switch conditions Vol. II-2-30 antenna feed problem Vol. V-2-6 protection configuration Vol. IV-8-17, basics Vol. V-2-4 Vol. IV-8-20 configuration problems Vol. V-2-7 terminal guidance on process Vol. V-2-4 alarms IDU LEDs Vol.
Page 916 Vol. IV-2-27 CT connection via PC DB-9 COM port Vol. IV-2-12 CT PC cable Vol. IV-2-19 obtain IP 9500 MXC address Vol. IV-2-28 setting up CT connection Vol. IV-2-11 setting up V.24 USB port connection Vol. IV-2-15 viewing alarms Vol.

Alcatel-Lucent 9500 MXC User Manual

About this Manual

Chapter 1. Health and Safety

Chapter 3. 9500 MXC Nodes

Chapter 4. Outdoor Units

Chapter 5. Configuration and Diagnostics

Chapter 6. 9500 MXC Performance and Diagnostic Features

Volume III 9500 MXC Installation

Chapter 2. Outdoor Installations

Volume IV 9500 MXC CT

Chapter 7. Node and Terminal Plug-Ins

Quick Links

Troubleshooting

Related Manuals for Alcatel-Lucent 9500 MXC

Summary of Contents for Alcatel-Lucent 9500 MXC