
This chapter describes the cables needed for QSR installation and provides information on the following:
- Attaching module cables
- Connecting and reading Central Office alarms
Customer-Supplied Cables
Customer-supplied cables connect modules installed in the SSR chassis to customer equipment. All customer-supplied cables must be available at the time of installation. See Table 4-1 for a list of customer-supplied cables.
Avici-Supplied Cables
Avici includes a kit of external cables for use in troubleshooting with each QSR. These cables allow console access to QSR components. Refer to Table 4-2 for descriptions of Avici-supplied cables.
.
Dongle Cable Specifications
The dongle cables required include a 10BaseT for RJ-45 connections to the network management system. This straight-through connector is a standard Category 5 patch cable. Maximum cable length is 100 meters.
Console Cable Specifications
The console cables required include a 10BaseT for RJ-45 connections to the network management system. This straight-through shielded connector is a standard Category 5 patch cable. Maximum cable length is 100 meters.
Fiber Cable Routing
Single- or multi-mode fiber optic cables provide the interface between router modules and customer equipment. Route the fiber optic cables through the horizontal cable management tray on the front of the QSR.
Fiber Management
The customer is responsible for purchasing and installing overhead fiber management frames to manage their fiber optic cables. We recommend Siecor Fiber Management System for overhead cable routing in multiple- QSR configurations.
Module Cables
The following cabling applies to a minimum system configuration consisting of one route controller module and one router module.
The cables required for route controller module connections include:
- One Category 5 100BaseT Ethernet cable to connect to one router module
- One Category 5 10BaseT Ethernet cable to connect to one bay controller module
- One Category 5 10BaseT Ethernet cable (customer supplied) or console cable to connect to an external network management system
RS-232 Serial Interface Connector
Connecting a console to a route controller module requires the following:
- Two DB-9 RJ-45 adapters - one male, one female
- A twisted-pair cable with two RJ-45 connectors
The RS-232 connector on the server is a 9-pin DB-9 female connector that supports a limited data communications equipment (DCE) pinout. Refer to Figure 4-1 for pinout details.
PROCEDURE: Use the following steps to connect the server console port to a console:
Step 1 Attach the cable with two RJ-45 connectors to the RJ-45 ports on the two adapters.
Step 2 Attach the DB-9 male connector to the female port on the route controller module.
Step 3 Attach the DB-9 female connector to the male port on the console (PC).
Figure 4-1. Serial Cable Pinouts
![]()
RS-232 supports the following terminal settings:
- Bits: 8
- Parity: N
- Stop bit: 1
- Flow control: None
- Speed: 9600 BAUD
Bay Controller Backplane
In the QSR, the bay controller module interfaces directly with the backplane. The backplane provides the interface between:
- Bay controller modules and cooling modules
- Bay controller modules and backplanes (for communication between server and router modules)
- Bay controller modules and the breaker switches (to monitor power and alarm LEDs)
- Bay controller modules in adjacent chassis (multiple-chassis configurations only)
The QSR chassis uses dual -48 Vdc power inputs that filter and distribute redundantly throughout the chassis. Redundancy prevents the failure of one power input from affecting another and minimizes power outages.
Main power from customer battery packs and rectifier stacks (customer power distribution system) supplies power to the QSR at the terminal strip.
Grounding Communication Links
The SSR chassis uses three main types of communications cables:
- Fiber-optic cables
- Twisted-pair cables
- Coaxial cables
![]()
CAUTION (C:4-1) In a system with an Isolated Bonding Network (IBN) grounding topology, take care that communications cables going into and out of the system do not violate the topology. To prevent signal errors or damage to the circuitry, isolate links to avoid signals being referenced to different ground potentials.
Potential differences can occur when signals and/or shields are connected to different ground references. This requires specific installation measures to offset possible risks or violations.
NOTE Installation measures needed to eliminate different ground references are beyond the control of the equipment supplier or installer. These measures are in reference to the grounding topology of the customer's central office. Customers have different methods of supplying and connecting these site- specific grounds. This statement is intended only as a reminder to customers that there are possible risks involved when connecting to different ground sources.
For additional information on grounding network-communication links, refer to the International Telecommunications Union standards ITU-TS.
Central Office Alarms
Central office alarms for the QSR set off remote audible and visual indicators in the Central Office (CO), and visual indicators (LEDs) on the faceplate of the bay controller module (see Figure 4-2).
When connected at the CO, central office alarms report the occurrence of events such as a component failure. Alarms originate in either a bay controller module or route controller module.
The bay controller module sets and clears alarms as well as maintains an alarm database. A DB-15 connector on the bay controller backplane lets you connect visual and audible alarms to your remote central office system.
CO Alarm Levels
Three levels of central office alarms exist. They are:
- Critical - indicates the occurrence of a severe, service-affecting condition and requires immediate corrective action. Two Bellcore examples of critical alarms are a fire or the failure of both route controller modules or power feeds to the QSR.
- Major - indicates serious hardware or software conditions such as disruption of service or failure of an important circuit. A major alarm requires immediate attention to restore full performance, but has less immediate impact on service or system operation than a critical alarm. A Bellcore example of a major alarm is a Public Packet Switch Network (PPSN) trunk "declared link failure."
- Minor - indicates a problem that has no serious affect on service to customers or trouble with a circuit that is not essential to system operation. All non-service affecting issues are minor alarms. A Bellcore example of a minor alarm is a line carrier problem where transmission was switched to a protection line.
Bellcore GR-474-CORE states that each problem requiring a crafts person action shall result in an alarm condition and shall be reported by three concurrent methods.
Table 4-3. QSR CO Alarm Bellcore Requirement QSR CO Alarm Solution Automatic output message to both a USI1 device and an Operating System (OS)
The QSR logging system automatically outputs a message to both a USI and OS. In addition, the logging system meets the additional requirement of automatic messages being inhibitable (R2-19).
Visual indication at the network element
The QSR visually indicates a problem with a Critical, Major, or Minor LED. The QSR also activates CO audible alarms. The severity of the event determines which LED lights.
Audible and visual indications at various CO locations under the control of the network element
The QSR visually indicates a problem by lighting a Critical, Major, or Minor LED. The QSR also activates CO audible alarms. The severity of the event determines which LED lights.
1A USI is an intelligent workstation or dumb terminal that is directly connected to network equipment. CO Alarm LEDs and Audible Bells
Remote CO alarms are both visual and audible. Local alarms are visually shown by four labeled LEDs on the bay controller module. See Figure 4-2.
Figure 4-2. Locating Central Office Alarm LEDs and Controls
![]()
Critical and major LEDs are red; the minor LED is amber. LEDs remain lit until all detected events are cleared.
Whether the alarm signal originates from the route controller module or bay controller module, the appropriate LED, or visual and sound combination in the central office are activated. Message logging occurs when an alarm is activated.
IPriori provides CLI commands to silence sounding alarms, to display alarms, and to test QSR bay LEDs. For more information about IPriori and CLI commands for the CO alarms, see "IPriori Configuration Guide."
Connecting Remote Central Office Alarm Cables
Central office alarm cables are routed to the QSR using customer- supplied alarm cables. The alarm cables connect to the QSR via a D-type, 15-pin port on the backplane.
PROCEDURE: Use the following steps to remove the rear I/O cover and connect the central office alarm to the QSR:
Step 1 Using a #2 Phillips screwdriver, remove the 3 screws on the I/O cover and remove it from the chassis (see Figure 4-3).
Figure 4-3. I/O Cover Removal
![]()
Step 2 Attach the DB-15 central office alarm cable to the P28 alarm out port on the bay controller backplane (see Figure 4-4).
Figure 4-4. Locating the CO Alarm Port
![]()
Step 3 To isolate the customer alarm system from the QSR during service or repair, by-pass the alarm by inserting a switch between the alarm cable and the alarm system. Reset the switch to on after completing the service or repair.
- When using long cables, verify that cable resistance does not impede the alarm system.
Step 4 Using a #2 Phillips screwdriver, reinstall the 3 screws on the I/O cover and secure it from the chassis (see Figure 4-3).
Configuring Remote Central Office Alarm Cable Connections
The QSR has three sets of relays to generate central office alarms. When connected at the CO, the relays provide audible (bells, chimes, gongs) and visual (red, amber) indicators in the CO. Refer to Figure 4-5 for pinouts.
Figure 4-5. DB-15 Pinouts
![]()
Normally CLOSED/OPEN refers to the unenergized relay position.
If no power is supplied to the bay controller module:
- Critical_LED_Normally_Closed is shorted to Critical_LED_Common pin.
- Critical_Alarm_Normally_Closed is shorted to Critical_Alarm_Common pin.
- Under normal power and operating conditions: Critical_LED_Normally_Closed is open to Critical_LED_Common pin.
- Critical_Alarm_Normally Closed is open to Critical_Alarm_Common pin.
If an alarm condition occurs, press the Alarm cut-out push button on the front of the bay controller module. Pressing the button deactivates Critical, Major, and Minor alarm remote relays while leaving the LED relays active. LED relays remain activated until the fault condition is cleared by software. All relay contacts are capable of maximum current rating of 2A at 30 Vdc, 0.5A at 115VAC.
Copyright © 2003
Avici Systems Inc.
Avici® and TSR®
is a registered trademark of Avici Systems Inc.
IPriori, Composite Links, SSR, QSR, and NSR® are
trademarks of Avici Systems Inc.
Source
File Name: c4-instcbls.fm
HTML File Name: c4-instcbls.html
Last Updated: 04/11/03 at 09:08:22