9500mpr user manual v1.1

8/13/2019 9500MPR User Manual v1.1

1/134

9500 MPR

Alcatel Part Number 3EM22086A

3400 West Plano ParkwayPlano, Texas 75075-5813 U.S.A.

Issue 1, February, 2008

Microwave Packet Radio

Users Manual


2/134


3/134

NORTH AMERICA CUSTOMER SERVICE CENTER24 HOURS PER DAY, 7 DAYS PER WEEK

PHONEthe CallCenter at888-252-2832(USand Canada)

or613-784-6100(International)

ALCATEL-LUCENTS PRIMARY MISSION IS

SATISFYING OUR CUSTOMERS' QUALITY EXPECTATIONS.

The Call Center Agent (CSA)Will help connect you with Technical Assistance (TAC)

Or assist you with a Repair and Return

Phone-based technical support

After-hour emergencies

On-site technical support

E-mail support [email protected]

Software and hardware upgrades

TAC

Module repair

Repair and Return

Training http://www.alcatel-lucent.com>support

Technical Training

Other Services Offered

Field Services

Installation and test

Customized and Comprehensive Service Agreements

Registration http://www.alcatel-lucent.com>MyAccess

Once registered

From MyAlcatel go to Alcatel Support Documentation Register for access to Documentation and E-mail Update notifications

For Product Change Notices (PCN), Product Documentations, etc.

Software and Hardware upgrade documentation


4/134

Telephone Assistance, Normal Working Hours(CST 8am 5pm M-F)TAC supports all Alcatel North America Microwave products. This includes routine questions andemergency service.

Telephone Assistance, Emergency After-Hours

Defined as loss of traffic, standby equipment, or network visibility on traffic-bearing systems. Available through our Customer Service Agents (CSA).

Call (888) 252-2832. Ask for the Microwave (MW) or the Network Management for Radio (NMR)emergency duty engineer.

Caller should provide the following information to the Customer Service Agent (CSA):

Company name First and last name (Please spell it for us!!)

Telephone number

City and state. Street address if applicable

Equipment type number

A brief description of the problem affecting their equipment

TL-9000 Severity (see table below).

Priority: High, Medium,or Low.

Creating a TAC Service Request (SR)

Critical

TL-9000 Severity

Major

Minor Problems not classified as critical or major.

Problems severely affecting service, traffic, capacity, or networkmanagement. They require immediate corrective action. (Ex.Loss of network management capability, loss of traffic imminentor existing).

Conditions seriously affectingsystem operation. They requireimmediate attention. (Ex. processor outage, loss of standbyequipment, loss of remote access, or network managers).

CTACTelephone Technical Support


5/134

TOC-1

Table of Contents

1 General

1.1 Introduction ...............................................................................................................1-1

1.2 Content ......................................................................................................................1-1

2 Operation

2.1 General ......................................................................................................................2-1

2.2 Turn-On .....................................................................................................................2-1

2.3 Craft Terminal (CT) Provisioning Function/Operation ..........................................2-1

2.4 Operating Procedures ...............................................................................................2-1

2.4.1 Rx Radio Protection Switching .................................................................................2-22.4.2 Tx Radio Protection Switching .................................................................................2-3

2.4.3 Equipment Protection Switching .............................................................................2-4

2.5 Turn-Off Procedure ...................................................................................................2-5

2.6 Emergency Operation ...............................................................................................2-5

2.7 Module Indicators and Connectors ...........................................................................2-5

3 Interconnect

3.1 Section INTRODUCTION ........................................................................................3-1

3.2 POWER CABLE Connection ....................................................................................3-1

3.3 E1 Connections ..........................................................................................................3-3

3.4 Ethernet Cable Connections .....................................................................................3-7

3.4.1 Automatic MDI/MDI-X Configuration .....................................................................3-7

3.4.2 Crossover Cable Option ............................................................................................3-7

3.5 USI/CONTROLLER CABLE CONNECTION to Laptop (J301) ...........................3-11

4 Initial Turnup

4.1 SECTION INTRODUCTION ....................................................................................4-1

4.2 RECOMMENDED Sequence ....................................................................................4-1

4.3 Security Management ...............................................................................................4-2

4.4 Load 9500 MPR Software on PC ..............................................................................4-2

4.5 Turn-On Procedure ...................................................................................................4-2


6/134

TOC-2

Page

4.6 Startup ......................................................................................................................4-2

4.7 PROVISIONING Radio ............................................................................................ 4-6

4.7.1 Enable Plug-In Cards ...............................................................................................4-6

4.7.2 Provision Plug-In Cards ...........................................................................................4-9

4.7.3 Provision Synchronization .....................................................................................4-13

4.7.4 Provision NE Time ..................................................................................................4-16

4.7.5 Crossconnect E1 Lines To Radio Module ..............................................................4-18

4.7.6 Provision System ....................................................................................................4-20

4.7.7 Provision Local NE IP Address ..............................................................................4-21

4.7.8 Provision Ethernet Port 4 ......................................................................................4-22

4.7.9 Provision IP Static Routing ....................................................................................4-23

4.7.10 Provision OSPF Static Routing ..............................................................................4-24

5 Maintenance

5.1 Introduction ..............................................................................................................5-1

5.2 Maintenance Philosophy ..........................................................................................5-2

5.3 PERSONAL COMPUTER (PC)/Laptop ................................................................... 5-2

5.4 Troubleshooting ........................................................................................................5-2

5.4.1 Before Going to Site Checklist .................................................................................5-2

5.4.2 Troubleshooting Basics .............................................................................................5-3

5.4.3 Troubleshooting Path Problems ............................................................................... 5-8

5.4.4 Troubleshooting Configuration Problems .............................................................5-10

5.4.5 Troubleshooting Ethernet Problems ......................................................................5-11

5.4.6 Troubleshooting TMN Problems ............................................................................5-12

5.5 Card Removal and REPLACEMENT ....................................................................5-14

5.5.1 ODU Removal and Replacement ...........................................................................5-16

5.6 CHANGING FREQUENCY ................................................................................... 5-16

5.7 CLEANING ............................................................................................................. 5-16

6 User Guide

6.1 Introduction ..............................................................................................................6-1

6.2 Cross-Connect Screen ...............................................................................................6-1

6.2.1 Helpful Hints ............................................................................................................6-2


7/134

TOC-3

Page

6.2.2 Cross-Connecting Rules and Guidelines ................................................................. 6-5

6.3 Diagnosis Menu ......................................................................................................6-18

6.3.1 Remote Inventory ...................................................................................................6-18

6.3.2 Abnormal Conditions ..............................................................................................6-19

6.3.3 Summary Block Diagram View ..............................................................................6-19

6.4 Supervision Menu ...................................................................................................6-20

6.4.1 Supervision Dropdown Menu ................................................................................. 6-20

6.4.2 Access State Menu ..................................................................................................6-20

6.4.3 MIB Management Menu ........................................................................................6-21

6.4.4 SW License ..............................................................................................................6-24

A TCO Suite Pre-ProvisioningA.1 TCO Main Menu .......................................................................................................A-1

A.1.1 Pre-Provisioning Menu .............................................................................................A-1

A.1.2 Configuration Screen Options ..................................................................................A-4

B COMMISSIONING

B.1 Commissioning Process ............................................................................................B-1

B.2 Commissioning Tests ...............................................................................................B-1

B.3 Commissioning records ...........................................................................................B-1

B.4 Tributary Functionality Test ..................................................................................B-2

B.5 Ethernet Data Channel (optional) Functionality Test ..........................................B-3

B.6 Tx Output Power and RSL ......................................................................................B-3

B.7 Hop Stability Test ....................................................................................................B-5

C Forms

D NEReport.txt


8/134

TOC-4 This page intentionally left blank.


9/134

1-1

1 GENERAL

1.1 INTRODUCTION

The information in this Users Manual is a summary of the overall Operation and Mainte-

nance Manual that is located on the attached CD. The summary information is provided to

support initial turnup, day-to-day operation, and maintenance of the 9500 MPR equip-

ment. See Figure 1 - 1.

1.2 CONTENT

Refer to Table 1 - 1.The attached CD column lists the parts of the 9500 MPR Radio Family

Operation and Maintenance Manual, PN 3EM22085AAAA. A check mark under the Users

Manual column or the attached CD column indicates where the information is located.

Table 1-1 Information Location

Location

Section/Appendix Users Manual Attached CD

Glossary General

Ordering InformationFeatures and OptionsSupplied and Optional equipmentPart NumbersPhysical, Environmental, and Electrical Characteristics

Application

Functional Description

Physical Installation

InterconnectE1Ethernet

Initial TurnupRadio ProvisioningTMN Specifics

OperationControls and Indicators

Users GuideCraft Terminal Screen Descriptions

MaintenanceTroubleshooting Craft Terminal AlarmsTroubleshooting Using Performance ScreensTroubleshooting TMN AlarmsModule Replacement ProceduresPost-Replacement Test procedures

Diagrams

Rack Installation

Alarm/Status/Control

Maintenance Support ProceduresOptional Over-The-Hop Performance Tests


10/134

1-2

Figure 1-1 9500 MPR Family

MSS-8

Microwave Service Switch

ODU V2

Outdoor Unit

MSS-8

8Slots

ODU

V2

9500 MPR

Microwave Packet Radio

9500-1040P02/20/08


11/134

2-1

2 OPERATION

2.1 GENERAL

This section contains turn-on, normal operation, turn-off, and emergency operating proce-

dures plus a description of module indicators and connectors for the 9500 MPR Series

Microwave Packet Radios.

Before performing any procedures, operating personnel should become

familiar with the locations of power distribution units and circuit

breakers. If an equipment performance problem occurs during the fol-

lowing procedures, refer to the Maintenance Section.

2.2 TURN-ON

Radio power is controlled externally via rack and site circuit breakers. The radio is designed to

operate continuously without operator intervention. After initial installation and power turn-on,

operating procedures are limited to periodic visual checks and alarm checks. Turn-on proceduresare needed only if the system has been turned off due to a malfunction or during maintenance.

Until all radios in the transmission link are interconnected, turned

on, and operating properly, alarm conditions may exist.

Perform the following procedure to turn on the 9500 MPR series radios:

1. Set rack power to on.

2. Verify that no alarm indicator is lighted. If alarm indicator is lighted trou-bleshoot as described in the Maintenance Section.

2.3 CRAFT TERMINAL (CT) PROVISIONING FUNCTION/OPERATION

The Craft Terminal software is used for maintenance and support of the radio including fault

and status reporting. Refer to the Initial Turn-Up Section for instructions on loading and run-

ning the software. Refer to the Users Guide Section for descriptions and functions of the menus.

Refer to the Software Release Notes before performing any operating,

provisioning, or maintenance function on this equipment. The Soft-

ware Release Notes may contain information affecting these functions

that is not contained in this instruction manual.

2.4 OPERATING PROCEDURES

The Craft Terminal computer is the main control for the radio. If

instructions for setting up the Craft Terminal computer are needed,

refer to the Initial Turn-Up Section.


12/134


13/134


14/134


15/134

2-5

2.5 TURN-OFF PROCEDURE

The radio is designed for continuous operation. If power must be removed while perform-

ing maintenance on a particular cabinet or shelf, power can be removed by turning off

associated site/rack circuit breakers.

Normally, the turn-off procedures are not used. System design allows

maintenance of the rack without interrupting service. It is recom-

mended that turn-off be performed only in an emergency.

2.6 EMERGENCY OPERATION

If an emergency occurs, such as a short circuit or a fire, turn off the 9500 MPR as quickly

as possible.

2.7 MODULE INDICATORS AND CONNECTORS

Do not adjust controls unless instructed to do so in an instal-

lation or maintenance procedure. Unauthorized adjustment

of controls illustrated and described in this section may inter-rupt traffic and/or degrade system performance.

Module controls, indicators, and connectors used in normal operation or referenced in pro-

cedures are shown in Figure 2-4through Figure 2-6.


16/134

2-6

Figure 2-4 Core Card, Controls, Indicators, and Connectors

S-Card Status

A-NEABNORMALALM (yellow)

W-NEWarningALM (yellow)

m-NE minorALM (red)

M-NE MAJORALM (red)

ResetPushbutton

9500-1026BE01/23/08

Sync Out(Conn-Coax)

Sync In(Conn-Coax)

CraftTerminal

SFP IndicatorsL-Link

A-Actividy(Same as RJ45)

Ethernet 1-4Connectors (RJ45)

SFPConnector

(USB)(RJ45)

On-Link Up

Off-Link Down

Blinking-Tx/Rx Activity

Off-No Activity

Link Indicator Activity Indicator

RJ 45 Connector.Side view showing the small LED lights.

Alarm Status.See Core Main Module alarm status matrix.

Card Status LED.Indicates the status of the printed circuit boardas follows: Off Card not equipped, not provisioned,

or not powered Green Blinking Download, software

booting, or flash card realignment inprogress

Green In service, normal operation, andproperly provisioned

Yellow In standby, properly provisionedas EPS

Red Card fail Red Blinking Card mismatch


17/134

2-7

Figure 2-5 E1 Access Card PDH Module Indicators and Connectors

Figure 2-6 Radio Access Card Indicators and Connector

Card Status

9500-1030P01/31/08

E117-32

E11-16

Card Status LED.Indicates the status of the printed circuit board as follows: Off Card not equipped, not provisioned, or not powered Green Blinking Download, software booting, or flash card

realignment in progress Green In service, normal operation, and properly

provisioned Yellow In standby, properly provisioned as EPS Red Card fail Red Blinking Card mismatch

Card Status LED.

Indicates the status of the printed circuit board as follows:

Off Card not equipped, not provisioned, or not powered

Green Blinking Download, software booting, or flash card

realignment in progress

Green In service, normal operation, and properly

provisioned

Yellow In standby, properly provisioned as EPS

Red Card fail

Red Blinking Card mismatch

Power Emission Status LED.

Indicates output power status of ODU as follows:

Off No Output power (eg: Hot-Standby XMTR, software is

booting, or FPGA downloading is in progress

Green Normal output power (+29 dBm Nominal)

Yellow Forced squelch enabled on Craft Terminal

Red Abnormal output power (high or low limits exceeded)

IF To/From ODU(SMA)

Card Status

Power Emission Status

9500-1028P

01/31/08


18/134

2-8 This page intentionally left blank.


19/134

3-1

The information contained in this section is a summary of the infor-

mation on the enclosed CD. Refer to CD is used throughout this sec-

tion to refer the reader to the detail information on the CD.

3 INTERCONNECT

3.1 SECTION INTRODUCTION

This section gives the location and describes, power connections, signal connections, and

status and alarm connections for the 9500 MPR.

3.2 POWER CABLE CONNECTION

SeeFigure 3 - 1 and Figure 3 - 2for power cable connection. The power cable (PN 3DB18271AA)is supplied in the MSS 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 2(AWG 12).

The red (or blue) wire must be connected to -48 Vdc (live); the black wire to ground/+ve.

Figure 3-1 Power Cable and Connector

DC power connector can be shorted inadvertently if applied at

an angle. Always insert with correct alignment.


20/134

3-2

Short circuiting low-voltage, low-impedance dc circuits can

cause arcing that may result in burns or eye injury. Removerings, watches, and other metal jewelry while working withprimary circuits. Exercise caution to avoid shorting inputpower terminals.

To protect maintenance personnel from antenna tower light-ning strikes, the ground system must be integrated by bond-ing frame ground and dc battery return together.

Figure 3-2 Battery Power Connection


21/134

3-3

Do not apply battery power until it is determined that A and

B battery cables with isolated returns and power cables arewired correctly. With power applied, reverse polarity on wir-ing (+batt wired to -batt pin on connector) can cause powersupply fuse to blow.

Grounding of pole, antenna, customer interfaces, and all entrances to

the building interior shall meet local electrical code and standard

business practices.

3.3 E1 CONNECTIONS

Recommended connectorized cable assembly PN 3CC52118AA (22 AWG 34 pair shielded,jacketed cable with 68-pin SCSI connector on each end). See Figure 3-3and Figure 3-3forconnections. Refer to Table 3-1and Table 3-2for mating cable wiring.

Figure 3-3 E1 Signal Cable and Connector


22/134

3-4

Figure 3-4 E1 Cable Connection (Sheet 1 of 2)

Figure 3-4 E1 Cable Connection (Sheet 2 of 2)

E1/DS1Cable

Distributor Subrack

(Rear View)

9500-1369

11/06/07

1

E1/DS1 CableEnd 2

E1/DS1 CableEnd 1

32 E1/DS1PDH Module

Distributor Subrack

(Front View)

9500-1370

11/06/07

1

1

1


23/134

3-5

Table 3-1 Pin Function: Tributaries 1-16

Description Pin # Pin # Description

GND 1 35 GND

TTIP Trib. 1 2 36 1 Trib. TRING

RTIP Trib. 1 3 37 1 Trib. RRING
























RTIP Trib. 13 27 61 13 Trib. RRINGTTIP Trib. 14 28 62 14 Trib. TRING






GND 34 68 GND


24/134

3-6

Table 3-2 Pin Function: Tributaries 17-32

Description Pin # Pin # Description

GND 1 35 GND

































GND 34 68 GND


25/134

3-7

3.4 ETHERNET CABLE CONNECTIONS

Part numbers are assigned for unshielded, straight-through CAT5 UTP (PN 3AL48960AA-AL) and CAT5E UTP (PN 3AL15052AA-AL) cables. The CAT5 or CAT5E cables can be usedfor 10/100/1000BASE-T applications, however the CT5E cable is the recommended cable for1000BASE-T applications. The CAT5E cable has a tighter, higher quality twisting on the wirepairs and is less susceptible to crosstalk. Refer to Table 3-3and Table 3-4for pinout. SeeFigure 3-5for pair wire colors. See Figure 3-6and Figure 3-7for interconnect information.

3.4.1 Automatic MDI/MDI-X Configuration

The Ethernet PHY provides automatic Medium Dependent Interface (MDD/Medium Inde-

pendent Interface-crossover (MDI-X). Automatic MDI/MDI-X configuration eliminates the

need for crossover cables.

3.4.2 Crossover Cable Option

Crossover type cables with pin 1 wired to pin 3 and pin 2 wired to pin 6 can be used, but

are not necessary. Crossover is automatically performed by the Core Card, resulting in a

straight-through interface to the link partner.

Table 3-3 10/100BASE-T Ethernet Connector Pinout

PIN FUNCTION PORT

MDI MDI-X

1 TD+ Output Input

2 TD+ Output Input

3 RD+ Input Output

4/5 GRD N/A N/A

6 RD- Input Output

7/8 GRD N/A N/A

Table 3-4 1000BASE-T Ethernet Connector Pinout

PIN FUNCTION DIRECTION

1 TRDA+ Input/Output

2 TRDA- Input/Output

3 TRDB+ Input/Output

4 TRDB- Input/Output

5 TRDC+ Input/Output

6 TRDC- Input/Output

7 TRDD+ Input/Output

8 TRDD- Input/Output


26/134

3-8

Figure 3-5 Straight-Through Mating Cable

Figure 3-6 10/100BASE-T Interconnect

LMW-9053F

05/24/05

1

2

3

4

5

6

7

8

1

2

3

4

5

6

7

8

WHITE-GREEN

GREEN

WHITE-ORANGE

ORANGE

WHITE-BLUE

BLUE

WHITE-BROWN

BROWN

PAIR A

PAIR B

PAIR D

PAIR C

CONN 1 CONN 2

MDI Mode

TD+1 1

TD-2 2

Ethernet

I/O INTFC

Active

MDI-X Mode

Ethernet

I/O INTFC

Active

RD+3 3

RD-6 6

Active

Active

MDR-1169F05/24/05


27/134

3-9

Figure 3-7 1000BASE-T Interconnect

Transmit data (TRD) is both directions, simultaneously. Unwanted

data is cancelled.

Shelf 1

TRDA+1 1

TRDA-2 2

Ethernet

I/O INTFC

Shelf 2

Ethernet

I/O INTFC

MDR-1170F05/24/05

CC

TRDB+3 3

TRDB-6 6

CC

TRDC+4 4

TRDC-5 5

CC

TRDD+7 7

TRDD-8 8

CC

C = Cancel.Cancels XMT data in RCV output.


28/134

3-10

Follow carefully the following dos and donts to prevent

future loss of traffic.

25

MAINTAIN A MAXIMUM BEND RADIUS OF 4 TIMESCABLE DIAMETER (4PAIR CABLES).

EXCEED A 90 DEGREE BEND.

.SEITELBACNETHGITREVO.SLAVRETNIMODNARTADNAYLESOOLSEITELBACYLPPA

TRY TO MINIMIZE THE AMOUNT OF JACKET TWISTING. OVERTWIST CABLE; IT CAN LEAD TOTORN JACKETS.

.NOISNETGNILLUPFOBL52DEECXE.ELBACGNIHCTERTSDIOVA

DO

CABLE DIA.=0.20

CABLE BENDRADIUS

DO

DO

DO

DONT

DONT

DONT

DONT

MW21500281071897


29/134


30/134



31/134

4-1

The information contained in this section is a summary of the informa-

tion on the enclosed CD. Refer to CDis used throughout this sectionto refer the reader to the detail information on the CD.

4 INITIAL TURNUP

4.1 SECTION INTRODUCTION

This section describes the procedures required to turn up the 9500 MPR Microwave

Packet Radios after installation.

This provisioning part of the section describes provisioning options available with the 9500

MPR software application. Provisioning allows for the definition, editing, and storing of

specific functions.

4.2 RECOMMENDED SEQUENCEPerform the following initial turnup procedures in sequence:

A. Install software on PC.

Software installed at the factory before delivery should not be over-

written by downloading to the radio controller at initial turnup. Refer

to Maintenance section on the attached CD for procedure to upgrade

existing software.

B. Turn on the radio.

C. Establish communication between radio and Craft terminal computer.

Saving provisioning on disk provides a reference for any future

provisioning changes.

D. Provision radio.


32/134

4-2

4.3 SECURITY MANAGEMENT

A password is required to operate the 9500 MPR. The radio is shipped

with a default password and if a new password is desired, it must be

entered using the Change Password screen. Once entered initially, the

password must be entered each time the user wants to access the pro-visioning screens (level 1 craft person password required) or down-

load software (level 2 administrator password required).

The 9500 MPR application software offers user password security management using two

different levels of passwords. User security deals with access level assigned to specific

users. The level of user security affects the type and number of commands an individual

user may execute. This prevents an unqualified users access to high-level commands.

Level 1 craft person password allows the user to perform all tasks except downloading soft-

ware. Level 2 administrator password allows access to all functions and is the highestlevel.

4.4 LOAD 9500 MPR SOFTWARE ON PC

Before operating the user system interface (USI) for the first time, the programs contained

on the CD ROM must be installed on the PC. The installation process configures the PC for

its unique requirements and prepares it to run the program.

A. Insert CD ROM disk into PC.

B. On Windows desktop, double click on My Computericon. My Computer

window displays.C. In My Computerwindow, click on CD ROMicon. Files window displays

D. Load Craft Terminal software on PC.

4.5 TURN-ON PROCEDURE

For user safety, user should become familiar with locations of power

distribution units and circuit breakers associated with the 9500 MPR

radio.

Turn on the radio at the power distribution unit.

4.6 STARTUP

Follow the steps on Figure 4-1to open communication with the radio.


33/134

4-3

Figure 4-1 Startup Procedure (Sheet 1 of 3)

CloseSaveRemoveNewSet CurrentGet Current

Nes Table

Type Version IP Address

0.0.0.0

Site Name Site Location

Network Elements List - Target: MSS11

9500-1226P11/08/07

Go To

Exit

Apply

OK

Show Alarm Monitor

Site Name:

IP Address: 10.0.1.2

Type: Version:

Ne DescriptionAlarm Synthesis

Ne Info

Ne Configuration

Site Location:

Critical

Supervision

major

Minor

Warning

Indeterminate

Network element Overview

Click on the New TableDocument icon.

9500-1225P10/15/07

9500-Startup 112/15/07

Input Type, Version, IP Address,Site Name and Site Location.

Hilight the configuration line justadded and click Get Currentbutton.The information from the Get Currentconfiguration line should automaticallyfill in the IP Addresss Site Name andSite Location fields.

2

34

5

1


34/134

4-4


Show Alarm Monitor

Site Name:

I

ype:

Site Location:

ritica

Supervision

major

Minor

Warning

Indeterminate

95009-1227P10/15/07

MW0

0

9500-Startup 20/15/07

9500MSS USM

OK

The application has been started.

OK

Show Alarm Monitor

Site Name:

IP Address: 172.22.174.211

MSS11

MWLAB

Type: Version:9500MSS V010000

Ne DescriptionAlarm Synthesis

Ne InfoNe Configuration

Site Location:

Critical

Supervision

Major

Minor

Warning

Indeterminate

0

0

1

2

0

Network element Overview - MSS11

95009-1226P10/15/07

Apply

ExitShow

Click OK.

Click OK.

Click Show.

Go To

5

7

6

8


35/134

4-5


Show Alarm Monitor

ite Name:

ite Location:

Minor

Warning

In eterminate

1

95009-1227P10/15/07

95009-1227P10/15/07

Show Alarm Monitor

ite Name:

IP Addres

Type:

ite Location:

ritica

Supervision

ma or

Minor

Warning

In eterminate

500M

1

Login -

UserName

Apply Cancel

Password

JusmMSS

Loading Performance MIB...

69%

When the startup procedure is complete, Main Screen will display9500-Startup 3

11/10/07

Click to start theloading process.

Type in User Name.

Type in Password.

Loading Performance MIB andother processes loading status.

8

10

11

9


36/134

4-6

4.7 PROVISIONING RADIO

Changes to provisioning do not have to be made in any particular order.

Click on Provisioning. Check current provisioning and change as required. See Figure 4-2

for recommended sequence.

Figure 4-2 Provisioning Sequence

4.7.1 Enable Plug-In Cards

MSS E1 Access Card and Radio Access Card have to be enabled in order to communicate

what type of card is in what MSS slot to the microprocessor in the Core Card. This is

accomplished on the Settings screen for that card. The Core Card in MSS slot 1 is always

enabled. If a protection Core Card is installed in slot 2, it must be enabled. The ODU is

enabled automatically when the associated Radio Access Card is enabled. The Fan Unit is

optional and therefore, when equipped, must be enabled.

Enable MSS modules using the following procedures. See Figure 4-3through Figure 4-6.

Start

Enable Plug-In CardsParagraph 4.7.1

Provision Plug-In CardsParagraph 4.7.2

Provision NE TimeParagraph 4.7.4

Provision X-ConnectionsParagraph 4.7.5

Provision SystemParagraph 4.7.6

Provision IP/SNMPParagraphs 4.7.7 Thru 4.7.10

Provision SynchronizationParagraph 4.7.3

9500-1323P02/22/08


37/134


38/134


39/134


40/134


41/134


42/134


43/134

4-13

4.7.3 Provision Synchronization

All 9500 MPR radios in the network must be synchronized to the same clock. One radio in

the network is provisioned Master. All other radios in the network must be provisioned

Slave. The slave radios all sync to the clock provided by the master.

4.7.3.1 Normal Operation

During normal operation, the master can be provisioned to get sync clock from two sepa-

rate sources: an internal local oscillator (most common source) or external clock from cus-

tomer provided equipment. The slave radios can be provisioned to receive the sync clock

from one of two sources: clock recovered by the radio receiver or the sync clock from

another radio in the network. Normally at a repeater, the sync clock is received over the

RF path and recovered by the radio receiver. A typical slave terminal uses the clock from

an adjacent radio. See Figure 4-9for typical master terminal provisioning. See Figure 4-

15 for typical slave terminal provisioning.

4.7.3.2 Failed Primary Operation

With the exception of the master when the radio is provisioned to sync off the local oscilla-

tor, the provisioned secondary sync source is enabled if the primary source fails. When themaster, provisioned to accept sync clock at the core from an external source, fails, the inter-

nal free-running local oscillator is enabled. Provisioning choices for the secondary source

for slave radios are dependent upon the choices made from the primary source.

4.7.3.3 Sync Switching

With the exception of the master when the radio is provisioned to sync off the local oscilla-

tor, the sync clock source is switched from primary to secondary if the primary source fails.

Sync clock switching provisioning is dependent on the role of the radio in the network

(master or slave) and on user preference. A revertive switching feature is a provisioning

option that restores the sync clock to the original source when the alarm on the primarysource is cleared. If revertive switching is not selected, the secondary sync source will con-

tinue to provide sync clock, and if the secondary source fails, must be manually switched to

the primary source.


44/134

4-14

Figure 4-9 Provisioning Master With Free Run Local Oscillator as Primary Source

9500-1330P11/14/07

Alarms

Protection Schemes ConnectionsEquipment

Settings

Unused

5 MHz

All Alarms

Apply Refresh

Sync Ports

Primary Source Secondary Source

Role

Sync In Port

Sync Out Port

Master

Slave

Sync In Alarm Profile

Free Run Local Oscilator

E1/T1 Port

Sync-In Port

Radio Port

Restoration

Revertive

Not Refertive


E1/T1 Port

Sync-In Port

Role

Master Local Oscilator All Alarms Revertive

Primary Source Sync in Alarm Profile Secondary Source Restoration

NE 9500MPR-E 1.0

Synchronization Source

Synchronozations

r

ODU/MPT

LOCALOSC

RADIOPERIPHERAL

DS1/E1/DS3PERIPHERAL


RADIOPERIPHERAL

ODU

PLLCLK

SELECT

N

Core

MSS

9500-105503/14/07

SyncOut

SyncIn

Free-RunLocal Oscillator

SelectedSync Source

RadioPort

Sync-InPort

E1/T1Port


45/134

4-15

Figure 4-10 Provisioning Slave with Radio Port as Primary Source

9500-1372P11/14/07

Alarms

Protection Schemes ConnectionsEquipment

Settings

Unused

5 MHz

All Alarms

Apply Refresh

Sync Ports

Primary Source Secondary Source

Role

Sync In Port

Sync Out Port

Master

Slave

Sync In Alarm Profile


E1/T1 Port

Sync-In Port

Radio Port

Restoration

Revertive

Not Refertive


E1/T1 Port

Sync-In Port

Role

Master Local Oscilator All Alarms Revertive

Primary Source Sync in Alarm Profile Secondary Source Restoration

NE 9500MPR-E 1.0

Synchronization Source

Synchronozations

l

ODU/MPT

LOCALOSC

RADIOPERIPHERAL



RADIOPERIPHERAL

ODU

PLLCLK

SELECT

N

Core

MSS

9500-105503/14/07

SyncOut

SyncIn

Free-RunLocal Oscillator

SelectedSync Source

RadioPort

Sync-InPort

E1/T1Port


46/134

4-16

4.7.4 Provision NE Time

The user can provision either the operating system (PC/laptop) or Network Time Protocol

(NTP) servers to manage time and date stamping functions. Time and date provisioning is

accomplished using the NE Time Configuration and NTP Server Configuration screens.

4.7.4.1 Provisioning NTP Protocol

NTP Protocol can be enabled or disabled and server addresses entered on the NTP Server

Configuration Screen. The entries provisioned on the NTP Server Configuration Screen

(Figure 4-10) are displayed on the NE Time Configuration Screen (Figure 4-15).

Server protection is provided by using two servers (main and spare). Date and time stamp-

ing is provided by the main NTP server until the main server fails.

4.7.4.2 Operating System and Network Equipment Time Sync

In applications where the network is not completely synced to NTP Protocol servers, the

Network Equipment Time can be provisioned to sync to the time/date information on the

PC or laptop. This function is enabled when the Set NE Time with OS Time field on the NE

Time Configuration screen is checked


47/134

4-17

Figure 4-11 NTP Server Provisioning

CRI

0

MIN

0

MIN

0

WNG

0

IND

0

MAJ

0

COM

SUP

ALI

OS

NTP

AC

EXT

0

EQP

0

TRS

0

Equipment

Equipment

NE9500MSS 1.0

PNU

ODU Dir#3-Ch#1

ODU Dir#4-Ch#1

ODU Dir#8-Ch#1

PNU/CORE-MAIN

PNU/CORE-SPAREPNU/RADIO-Dir#3-Ch#1

PNU/RADIO-Dir#4-Ch#1

PNU/E1

PNU/E1

PNU/E1


PNU/FANS

3

357

468

5 7

4 6 8

JUSM_9500MSS_1.0 - Aneto -

Views Diagnosis Supervision SW Download Equipment Help

NE Time

Network Configuration

Alarm Severities

System Settings

XConnections

Profiles Management

NTP Configuration

Routing Information

Configuration

IP Configuration

Ethernet Configuration

Local Configuration

Enabled

172.22.64.101 Enabled

NTP protocol

Servers reachability

Main Server address

172.22.64.101 Enabled

Main Server address

NTP Server Configuration

Refresh Apply CloseHelp

95009-1373P101/19/08

Enter Main NTP

Server IP address

Check to enable

NTP Protocol.

Enter Spare NTP

Server IP adress.

Click to display a pop-up dialog

for the NTP Serverconfiguration.

4

7

6

5

2 31


48/134

4-18

Figure 4-12 NE Time Provisioning

4.7.5 Crossconnect E1 Lines To Radio Module

At provisioning, E1 lines have to be manually crossconnected to the radio module using

craft terminal crossconnect screens. Before E1 lines can be crossconnected, the individual

line must be enabled and a flow Id number assigned on the E1 Access Card settings screen.

See Figure 4 -14. Follow the steps to crossconnect E1 lines.

CRI

0

MIN

0

MIN

0

WNG

0

IND

0

MAJ

0

COM

SUP

ALI

OS

NTP

AC

EXT

0

EQP

0

TRS

0

Equipment

Equipment

NE9500MSS 1.0

PNU

ODU Dir#3-Ch#1

ODU Dir#4-Ch#1

ODU Dir#8-Ch#1

PNU/CORE-MAIN

PNU/CORE-SPARE



PNU/E1

PNU/E1

PNU/E1


PNU/FANS

3

357

468

5 7

4 6 8



NE Time

Network ConfigurationAlarm Severities

System Settings

XConnections

Profiles Management

Configuration

NTP Status

NTP Protocol:

NE Time Configuration

Refresh Apply CloseHelp

NTP Main Server address:

NTP Spare Server address:

Time

Operatng System Time

Network Equipment Time

Set NE Time with OS Time

2007/07/18 07:42:37

2007-07-18 07:42:37

172.22.175.129

172.22.64.101

Enabled

95009-1374P11/13/07

Displays status (Enabled or

Disabled) of NTP Protocol

provisioning on NTP server

Configuration screen.

If NTP Protocol is Disabled, when checked,

enables function to synchronize Operating

System and Network Equipment Times.

Click to display pop-up dialog

for NE Time configuration.

3

5

4

21


49/134


50/134


51/134

4-21

4.7.7 Provision Local NE IP Address

See Figure 4-15. Follow the steps to enter the NE IP address, allowing the network to com-

municate with the NE.

Figure 4-15 Local Configuration Provisioning

CRI

0

MIN

0

MIN

0

WNG

0

IND

0

MAJ

0

COM

SUP

ALI

OS

NTP

AC

EXT

0

EQP

0

TRS

0

Equipment

Equipment

NE9500MSS 1.0

PNU

ODU Dir#3-Ch#1

ODU Dir#4-Ch#1

ODU Dir#8-Ch#1

PNU/CORE-MAIN

PNU/CORE-SPARE



PNU/E1

PNU/E1

PNU/E1

PNU/RADIO-Dir#8-Ch#1PNU/FANS

3

357

468

5 7

4 6 8



NE Time

Network Configuration

Alarm SeveritiesSystem Settings

XConnections

Profiles Management

NTP Configuration

Routing Information

Configuration

IP Configuration

Ethernet Configuration

Local Configuration

Local Configuration

Apply Help Close

10.0.1.2

IP Address

95009-1225P10/15/07

Apply the IP Address.

Click to display pop-up dialogfor the IP Configuration.

Enter NE IP address.

4

5

21 3


52/134


53/134


54/134


55/134

4-25


56/134



57/134

5-1

The information contained in this section is a summary of the on the

enclosed CD.Refer to CDis used throughout this section to refer the

reader to the detail information on the CD.

5 MAINTENANCE

5.1 INTRODUCTION

This section contains information and procedures to aid in restoring the equipment to

its proper operating condition after it has been determined that a problem exists.

The following warnings and cautions apply while operating, performance testing, trouble-

shooting, or repairing the 9500 MPR series radios.

Short circuits in low-voltage, low-impedance dc circuits can causesevere arcing that may result in burns or eye injury. Remove rings,watches, and other metal jewelry while working with primary cir-cuits. Exercise caution to avoid shorting power input terminals.

Units with the electrostatic-sensitive (ESS) symbol contain ESS

devices. Store these units in an antistatic container when not in use,

and anyone handling a unit should observe antistatic precautions.

Refer to the Special Precautions pages in the front of the instruction

book for detailed handling information.

Ensure that all antennas are properly aligned and waveguide is in

good physical condition.

Before performing procedures that might in any way affect transmis-

sion, it is recommended that the person performing the procedure

understand the FCC Rules and Regulations pertaining to the equip-

ment and be properly authorized to operate the equipment.


58/134

5-2

5.2 MAINTENANCE PHILOSOPHY

This section provides information and procedures for equipment maintenance down to the

Card level. Card repair is not covered in this manual.

The use of maintenance procedures in this section may result from failure of a periodic

check, an alarm indication, or unacceptable performance.

5.3 PERSONAL COMPUTER (PC)/LAPTOPConnect the RS-232 Interface cable between Craft Terminal connector on the Core Card

and the PC.

5.4 TROUBLESHOOTING

This section provides guidance on:

Before Going to Site Checklist

Troubleshooting Basics

Troubleshooting Path Problems

Troubleshooting Configuration Problems

Troubleshooting Ethernet Problems

Troubleshooting TMN Problems

5.4.1 Before Going to Site Checklist

Where possible, before going to site obtain the following information:

Does the fault require immediate attention?

Determine who is the best-placed person to attend the fault.

Confirm the nature and severity of the reported fault, its location, 9500 MPR type, fre-

quency band, high/low end ODU, capacity modulation and configuration (nonprotected,

protected, diversity). Ask:

Is just one 9500 MPR link affected, or a number of links in the same geographi-

cal area?

Is the path down completely or is traffic passing but with a BER alarm?

Is only one or a number of tributaries affected?

Could the fault be in the equipment connected to 9500 MPR, rather than in

9500 MPR? Are there alarms on other, connected equipment?

Is it a hard or intermittent fault?

Do alarms confirmwhich end of an alarmed link is faulty?


59/134

5-3

Could the weather (rain, ice, high wind, temperature) be a factor in the reported fault?

If the fault suggests a rain fade or other weather related fade condi-

tion and it matches the prevailing weather conditions, do not take any

action until the weather abates.

Does link history suggest any fault trends?

Does the fault history for the link indicate a likely cause?

Is the 9500 MPR link newly installed?

Has there been any recent work done on the link?

Ensure that you have with you:

Appropriate spares. Where an equipment failure is suspected, these shouldinclude replacement Cards/plug-ins and ODU. If an ODU is suspected then

local/national climbing safety requirements must be adhered to.

A laptop PC loaded with Craft Terminal, and either an Ethernet or V.24 connec-

tion cable. If an Ethernet connection is to be used, you need the 9500 MPR

Node/Terminal IP address and also the addresses for any remote sites to be

accessed.

If login security has been enabled, you need the engineer password for the local

and also any remote sites to be accessed.

Any special test equipment that may be needed, such as a BER tester.

Toolkit.

Key(s) for access to the site.

5.4.2 Troubleshooting Basics

This section provides general guidance on 9500 MPR troubleshooting:

Check front-panel LED indications.These provide summary alarm indications, which can

help narrow down the location and type of failure. Refer to Operation section fordetails.

Where a Status LED on a plug-in is off (unlit), but power to the MS is confirmed

by LEDs on other plug-ins, check the seating of the affected plug-in.

Check Main Screen.When logging into 9500 MPR with Craft Terminal, the openingscreen is the Main Screen. Use the information provided to check for severity and

problem type. Refer to Table 5-1, Alarm Matrix, for probable cause and recommended

action.


60/134

5-4

Table 5-1 Alarm Matrix

Equipment Alarm DescriptionConfiguration/Alarm

Most ProbableCause

Action1+0 1+1 HS 1+1 FD

Core Card Card Fail Major Minor Minor Core card failed Replace Core Card

Equipment Mismatch N/A Minor Minor Card in slot does notmatch card configuredin core memory

Install correct configuredcard

Card Missing N/A Minor Minor Core card is missingfrom slot

Install Core Card in slot

Unconfigured Equipment N/A Minor Minor Card in slot is not pro-visioned (enabled)

Provision card

LOS on ETH TMN Inter-face

Minor Minor Minor No Ethernet input sig-nal detected on ETH 4on Core Card

Check link partner andcable between link part-ner and ETH 4 connector

PPP IP Fail Minor Minor Minor

LOS on Gigabit ETHInterface

Major Minor Minor Loss of Ethernet isdetected on ETH 1-4on Core Card

Check link partner andcable between link partnerand ETH 1-4 connector

Firmware Download InProgress

Minor Minor Minor Status of download Wait for downloading tocomplete

LOS on Sync Interface Minor Minor Minor No sync clk detectedat Sync in port on CoreCard

Check sync source andcable between syncsource and Sync in port

Degraded Signal onSync Interface

Minor Minor Minor Sync clk errorsdetected at Sync inport on Core Card

Check sync source forerrors

License Mismatch for

Equipment Provisioned

Major Major Major Wrong flash card

installed on Core Card

Install correct flash card

for license

E1 AccessCard

Card Fail Major Minor Minor Failure of E1 AccessCard

Replace E1 Access Card

Equipment Mismatch Major Minor Minor Card in slot does notmatch Card configuredin Core memory

Install correct configuredcard

Card Missing Major Minor Minor E1 Access Card ismissing from slot

Install E1 Access Card inslot

Unconfigured Equipment Major Major Major Card is not Enabled onthe Settings screen

Enable card

LOS on PDH Tributary Major Minor Minor No E1 input signaldetected on any one ormore of 32 lines

Check E1 source and/orcable

Degraded Signal Minor Minor Minor Errors on input signaldetected on any one ormore of 32 lines

Check E1 source

AIS on PDH Tributary(RX)

Major Major Major AIS detected by thereceive circuits on oneor more E1 lines, indi-cating upstream failure

Check for upstream E1source for errors

AIS on PDH Tributary(TX)

Major Major Major AIS detected on one ormore E1 lines at inputto PDH 32xE1 Access

Card

Check E1 source


61/134


62/134

5-6

Loss of Alignment N/A Minor Minor Delay between mainand protect RF pathsdetected

1. Replace main RadioAccess Card

2. Replace protect Radio

Access Card3. Replace main ODU4. Replace protect ODU

Demod Function Fail Major Minor Minor Internal receive circuitfailure

Replace Radio AccessCard

High BER Major Minor Minor Bit Error Rate thresh-old (10E-4) exceededon RCVR input circuitson modem

1. Verify RF path is clear,antenna is aligned,and no existingweather-related prob-lems

2. Verify RSL is aboveRCV threshold. a). Ifnot check upstreamXMTR output/trouble-

shoot XMTR. b). If ok,3.

Early Warning N/A Minor Minor 10E-9 BER detected No action is required atthis time. Monitor receivesignal for increaseddegrading

ATPC Loop Minor Minor Minor Loss of ATPC commandpath between farendXMTR and local RCVR

1. Switch farend XMTRs(in a protected sys-tem). If alarm clears,replace farend off-lineRadio Access Card

2. Check/troubleshootfarend alarms

3. Replace alarmed

Radio Access CardLink Identifier Mismatch Major Major Major Link identifier number

provisioned on RadioAccess Card settingsscreen is different fromlink identifier numberprovisioned at otherend of hop

Set numbers at both endsof hop to match

TCA on Radio Link N/A N/A Major Alarm thresholdexceeded on standbyRadio Access Card


TCA on Radio Hop Major N/A Minor Alarm thresholdexceeded on standbyRadio Access Cardafter switching frommain to standby

UAT on Radio Link N/A N/A Major 10 consecutive SES(unavailable timeperiod) detected onmain Radio AccessCard


Table 5-1 Alarm Matrix (Cont.)


Most ProbableCause



63/134

5-7

UAT on Radio Hop Major N/A Minor 10 consecutive SES(unavailable timeperiod) detected on

standby Radio AccessCard after switchingfrom admin to standby


Minor Minor Minor Download status Wait for downloading tocomplete

LOS on Sync Interface Minor Minor Minor Loss of sync clockdetected

1. Replace Radio AccessCard

Degraded Signal Minor Minor Minor Bit errors haveincreased and haveexceeded degradedsignal threshold

1. Replace Radio AccessCard

License Mismatch forEquipment Provisioned

Major Major Major Modem card type doesnot match card typestored in memory onthe Core Card flashcard

Replace Radio AccessCard with correct cardtype

ODU Card Fail Major Minor Minor ODU failed Replace ODU

Equipment Mismatch Major Minor Minor ODU does not matchODU configured inCore memory

Replace ODU

RCV Function Fail Major Minor Minor ODU RCVR circuitfailed

Replace ODU

RF Frequency Mismatch Major Minor Minor Frequency out-of-range

of configured TX fre-quency

Re-configure frequency

Shifter Frequency Mis-match

Major Minor Minor Configured shiftervalue not supported byODU

Re-configure shifter value

TX Power Mismatch Minor Minor Minor Configured TX powervalue not supported byODU

Re-configure TX powervalue

Software Mismatch Minor Minor Minor Software version onODU does not matchsoftware version onCore

Download correct soft-ware version

ODU Not Responding Minor Minor Minor Loss of communication

with ODU

1. Replace ODU

2. Replace alarmedRadio Access Card


Minor Minor Minor Download status Wait for downloading tocomplete

EPS Equipment Protection SwitchingLOS Loss of SignalRPS Radio Protection SwitchingTCA Threshold Crossing AlarmUAT Un-Available Time

Table 5-1 Alarm Matrix (Cont.)


Most ProbableCause



64/134

5-8

Check the basics first.

For example, if multiple alarms are present, and these include power supply

voltage or hardware alarms, always check their cause before looking at result-

ant down-stream path failure or path warning (signal) alarms.

Similarly, if a path-related failure is indicated (no hardware or software

alarms), investigate the path. Go to the Craft Terminal History screen (15

minute view) to check supporting data, such as low RSL and incidence of inter-mittent pre-failure BER alarms, which if present are evidence of a path-related

failure. Refer to Para. 5.4.3for more information.

Check if symptoms match the alarm.Alarms reflect the alarm state, but in exceptional cir-cumstances an alarm may be raised because of a failure to communicate correctly with

the alarm source, or a failure in alarm management processing. Always check to see if

symptoms match the alarm, using LED indications and the Craft Terminal.

Check if recent work may be a cause.Recent work at the site may be a cause or contribut-ing factor. Check for a configuration change, software upgrade, power recycling (reboot),

or other site work:

Many hardware alarms are only initiated as a loss-of-communications alarm

during a reboot, software upgrade, or reconfiguration. By not being able to com-

municate with the Core, their settings cannot be loaded. The fault may be at the

hardware device (most likely), communications to it, or the Core.

Hardware/software compatibility alarms will be raised when a new plug-in is

installed that needs a later version of 9500 MPR software.

Hardware incompatible alarms will be raised when a plug-in is installed in a

slot that has been configured for a different plug-in.

MSS before an ODU.If there is doubt about whether a fault is in the MSS or ODU,always replace the MSS first; it is quicker and easier.

Hot-pluggable.MSS cards are hot-pluggable. There is no need to power-down beforereplacing, but traffic will be lost unless the plug-in is protected.

Plug-in restoration time.Ensure adequate time is allowed for services to resume when aplug-in is replaced.

5.4.3 Troubleshooting Path Problems

A path-related problem, with the exception of interference, is characterized by traffic beingsimilarly affected in both directions. Generally, if you are experiencing only a one-way

problem, it is not a path problem.

A path extends from ODU antenna port to ODU antenna port.


65/134

5-9

Normally a path problem is signalled by a reduced RSL, anddepending on its severity, a high BER.

Only in worst case situations, such as an antenna knocked out ofalignment, will a path fail completely, and stay that way.

For weather-related problems, such as rain or ducting, the path

problem will disappear as the weather returns to normal.

5.4.3.1 Path Problems on a Commissioned Link

A path problem on an existing link, one that has ben operating satisfactorily may be

caused by:

Weather-related path degradation

If BER alarms are fleeting/not permanent and RSL returns to its normal, commissioned

level after the alarm is cleared, rain, diffraction, or multipath fading is indicated. Rain

fade is the likely cause of fade for links 13 GHz and higher. Diffraction and multipath/duct-

ing for links 11 GHz and lower. If these alarms are persistent, there could be a problem

with the link design or original installation.

Changed antenna alignment or antenna feed problem

If RSLs do not return to commissioned levels after a period of exceptionally strong winds,

suspect antenna alignment. Also, check the antenna for physical damage, such as may

occur with ice-fall. For a remote-mounted ODU, check its antenna feeder.

New path obstruction

Where all other parameters check as normal, andthe path has potential for it to beobstructed by construction works, view/survey the path for possible new obstructions.

Interference from other signal sources

Interference usually affects traffic in just one direction. Unlike other path problems, RSL

is not affected. If suspected, check for new link installations at, or in the same geograph-

ical area, as the affected site. Ultimately, a spectrum analyzer may have to be used to

confirm interference, which is not an easy task given the need to connect directly to the

antenna port, after removing the ODU.

5.4.3.2 Path Problems on a New Link

For a new link, potential problems can extend to also include:

Incorrect antenna alignment

One or both antennas incorrectly aligned. Refer to Installation alignment procedure

on CD.

Mismatching antenna polarizations

Given a typical polarization discrimination of 30 dB, for most links it is not possible to cap-

ture a signal to begin the antenna alignment process.


66/134

5-10

Incorrect path calculations

If the RSLs are too low or too high, antenna alignment is correct, and Tx power settings

are correct, check the path calculations used to determine the link performance. A good

calculation match is +/-2dB. Disagreements in excess of 3 dB should be investigated.

Reflections

Reflection (path cancellation) problems may not have been picked up at the path planningstage, particularly if the survey was a simple line-of-sight. If suspected, resurvey the path.

5.4.4 Troubleshooting Configuration Problems

Configuration problems should only occur during the setup of a new link, or reconfigura-

tion of an existing link. The more common problems may be broadly categorized as:

Compatibility Problems

The two alarms that may activate are Configuration Not Supported and SW/HW Incom-

patible:

Configuration Not Supported:The plug-in installed is not enabled or is incorrectfor the configuration.

SW/HW Incompatible:Typically raised when new hardware is plugged into anexisting MSS that has software from an earlier release. To remove the alarm,

compatible 9500 MPR software is required; install the latest software.

Incorrect circuit connections

No alarms are activated for incorrect circuit connections. An incorrect assignment means

the expected end-to-end circuit connectivity will not happen. Re-check circuit assignmentsfor all nodes carrying the lost circuit(s).

Take extra care when configuring ring circuits.

Where the problem is not obvious, use the Tributary Loopback BER Test to track a single

circuit through a 9500 MPR network, beginning at the node closest to the node applying

the BER test.

Incorrect ID naming and commissioning

All traffic-carrying circuits must have a unique flow ID for the cross-connect capability to

operate.

Incorrect/incompatible trib settings

Trib line interface settings incorrect, or line levels incompatible. While no alarm activates

for an incorrect setting, its effect may result in line levels being too low (LOS alarm), or too

high, resulting in a high BER.

ATPC settings

Ensure ATPC settings are correct, specifically that the target fade margin allows adequate

headroom for local Tx power, while ensuring an adequate fade margin.


67/134

5-11

5.4.5 Troubleshooting Ethernet Problems

This section gives general guidance on troubleshooting problems related to the four Ether-

net ports on the Core Card.

The most common Ethernet problems are network and connectivity related and therefore

always check the following first:

Verify link partner capability, provisioning, and connection

Verify radio provisioning matches link partner

Verify cabling between radio and link partner

The LEDs on the Core Card front panel for each Ethernet connector are a good indicator of

correct connectivity and activity on the Ethernet port. Refer to Table 5-2for detail trouble-

shooting using the LEDs locally at the alarmed site.

Table 5-2 Troubleshooting Ethernet ProblemsLED Indication Probable Cause Corrective Action

ETH INLOS

Green LEDNot Lit

Loss of Ethernet RCV/radio XMT signalin. Most probable causes:

1. Cable between link partner andradio is disconnected/broken.

Connect/repair cable.

2. Speed/Mode provisioning mis-match between link partner andradio

1. Check local Ethernet provisioningscreen.

2. Check link partner provisioning.

ETH OUTLOS

Green LEDNot Lit

Loss of Ethernet XMT/radio RCV signalout. Most probable causes:

1. Loss of RF input to radio Access Card Check local RSL screen on CT. Is RSL ok?Yes - Check farend for Ethernet alarm.No - Check farend Tx output. Is farend TxOut ok?Yes - Check path, antenna, waveguide/cablingNo - Check/replace farend radio AccessCard.

2. Loss of Ethernet input to radio AccessCard

Check farend for Ethernet alarms.Are any alarms indicated?Yes - Troubleshoot farend alarmsNo - Check farend Ethernet status. Is onlyabnormal status indicated?Yes - Troubleshoot farend Ethernet status.No -

1. Replace local alarmed Core Card.

2. Replace local radio Access Card.


68/134

5-12

In order for the green Link LED to light:

1 Cable must be connected to Ethernet port

2 Ethernet port must be enabled (provisioned Enabled on Core Settings Screen)

3 Speed and mode (on Core Settings Screen) must be provisioned the same as

the link partner.

The yellow LED opposite the green on the connector indicates activity only. The flashing

yellow LED is not an indicator of signal type or quality.

5.4.6 Troubleshooting TMN Problems

This section gives general guidance on troubleshooting TMN problems related to Ethernet

port 4 on the Core Card. Ethernet port 4 on the Core Card can be used to transport SNMP

IP data. Troubleshoot port 4 connectivity alarms the same as Ethernet ports 1-3. Refer to

Para. 5.4.5.

The most common TMN problems are network related and first alert is normally observedby improper operation at the SNMP master. Always check the following first:

Verify master is properly registered in NE to receive traps.

Verify SNMP version matches system requirements

Verify correct community string and privileges

Verify proper network routing.

Refer to Table 5-3for detail TMN network troubleshooting.


69/134

5-13

Table 5-3 TMN Network Troubleshooting

Problem Possible Cause Possible Solution

Unusually slow communica-tion in radio network

1. Normal network managementtraffic is saturating the communi-cations channel.

1. There may be too many radiosbeing managed within a singleregion. Split the radio network

management into differentregions and backhaul the trafficfor each region through sepa-rate channels.

2. Polling radios for PM data ormissed alarms too rapidly

2. Poll the radios more slowly.

3. Multiple remote software down-loads in process

3. Download to fewer radios at atime.

4. IP traffic other than networkmanagement traffic being routed

through radio network

4 Configure external routers toallow only network management

related traffic through the Man-agement network of the radios.Dynamic route updates (OSPF,RIP) may attempt to reroute highspeed traffic through the TMNnetwork if a high speed ink fails.

Unable to operate controlsusing SNMP

To perform control operations, theManager must be registered as acraft device.

Register the Manager as a craftdevice. Manager registration typecan be changed as needed to typect to allow control operation andthen be changed back to nml for

normal operation.Can Read SNMP objectsbut cannot Write to SNMPobjects

1. Incorrect community string 1. Use the correct communitystring.

2. Insufficient SNMPv3 privileges 2. Use the correct privileges:

a) The TMN Interface supports 4view levels. Use a SNMPv3 useraccount that supports writeaccess to the selected SNMPobject.

b) Use the correct Authentication

mode.c) Use the correct Privacy pass-

phrase.

3. If the TMN Interface is config-ured for SNMPv2, the write com-munity string is probably wrong.

3 Use the correct write communitystring.


70/134


71/134

5-15

Plug-ins must be withdrawn and inserted using their finger-

grip fastener/pulls. Never withdraw or insert using attachedcable(s). Pulling on the cables may damage the cable, plug-in connector, and/or plug-in card connector attachment.

When installing a plug-in, ensure its backplane connector is

correctly engaged before applying sufficient pressure tobring the plug-in panel flush with the front panel. Improperalignment can result in damaged pins on the backplane con-nector and/or damage to the plug-in connector.

All slots must be filled with either a peripheral plug-in card ora blank panel. Failure to do so will compromise EMC integrity

and cooling air from the fan.

Use extreme caution when connecting or disconnecting the

ODU cable on the Radio Access Card. The shelf battery voltageis present on the center conductor of the connector. When

removing or replacing a radio Access Card, withdraw the

card from the shelf before disconnecting the cable to the ODU.

Failure to follow these cautions may cause arcing and/or pos-

sible power spikes that could affect traffic on other links

installed at the node.


72/134

5-16

Removing an in-service card in an unprotected link will cause

loss of traffic. Removing an in-service card in a protected linkrequires switching the traffic onto the standby (protection)

channel.

The main Core Card, standby Core Card, and fan card have dedicated slots.

The E1 Access Card and Radio Access Cards (peripherals) can be installed in any of

the universal slots (3 through 8).

The MSS-8 can be configured with a maximum of six peripherals; three protected

links, six non-protected links, or a combination of protected and non-protected links.

For protected links, main and standby (spare) peripherals must be plugged in side-by-side.

All plug-ins can be removed and installed with power applied.

5.5.1 ODU Removal and Replacement

Refer to the attached CD.

5.6 CHANGING FREQUENCY

Refer to the attached CD.

5.7 CLEANING

Do not use acid, alcohol, or brushes to clean cards because

damage to the silkscreen labeling and antistatic coating can

result. Cleaning should be confined to the removal of dust and

dirt using a damp cloth.

Cleaning should normally be confined to the removal of dust and dirt using a soft bristled

(natural fiber) brush and a low velocity blower (such as a vacuum cleaner with a plastic

blower nozzle). Do not use acid or synthetic bristled brushes to clean cards that contain

electrostatic-sensitive components.


73/134

6-1

The information contained in this section is a summary of the infor-

mation on the enclosed CD. Refer to CD is used throughout this sec-

tion to refer the reader to the detail information on the CD.

6 USER GUIDE

6.1 INTRODUCTION

Some menu functions are purposely faded to indicate they are not cur-

rently available. Only available functions are described.

This section contains descriptions of screens not used or described in other sections.

6.2 CROSS-CONNECT SCREEN

The cross-connect screen is used to configure switching of packetized data through the

Core Card. Using this screen, the operator can switch:

E1 (ports) lines from/to an E1 Access Card to/from a Radio Access Card and/or any of

four Ethernet ports on the Core Card.

Ethernet data from/to an external source to/from a Radio Access card and/or to/from an

E1 Access Card.

The screen allows the operator to select E1, Ethernet, and/or radio ports as source and des-

tination ports and provides a graphical presentation of the switch functions.

A PDH or radio peripheral can be installed in slots 3 through 8.

Valid X-Connect Rel 1.0

PDH -to- Radio

PDH -to-ETH

ETH -to-Radio


74/134

6-2

6.2.1 Helpful Hints

Icon Shapes

The shape of the icon identifies the card in the slot as Radio Access Card or E1 Access

Card, or one of four Ethernet connectors on the Core Card.

Icon Colors

The colors of the icons on the cross-connect screen can be used to quickly determine the

current state of the source and destination. For example:

A white icon indicates the source/destination is unavailable. Check to make sure the card

is enabled.

A blue icon indicates the destination is full. The limits granted by the license key have

been exceeded. A message is also displayed stating that no more E1 ports will be accepted.

A green icon indicates that the source and destination are available and the destination

can accept more E1 ports.

Slot #4

Slot #6

Slot #8

Slot #3

Slot #5

Slot #7

ETH#1 ETH#2 ETH#3 ETH#4

ETH

SW

9500-1061a12/27/07

CORE


75/134

6-3


76/134

6-4

Line Colors

The drag and drop line the operator inserts between icons indicates an electrical connec-

tion. The color of the line indicates type of data and direction.

Black Line E1 to Radio

Blue Line E1 to Ethernet

Red Line Radio to Radio

Green Line Radio to Ethernet


77/134

6-5

Mouse Operation

Single Left click A single left button click highlights (selects) the resource and opens up

an information window.

Single Right Click A single right button click highlights (selects) the resource and opens

up an information window.

6.2.2 Cross-Connecting Rules and Guidelines6.2.2.1 Cross-Connecting E1 Lines

The following rules and guidelines apply to switching E1 ports 1 through 32 on the E1

Access Card through the Core Card to the Radio Access Card:

1 The license key installed on the Core Card determines the number of E1ports that can be cross-connected.

2 The E1 access Card (E1 source) and Radio Access Card (destination) must beEnabledon the respective card provisioning screens.

3 Each E1 port to be cross-connected must beEnabledon the E1 provisioningscreen.

4 Each E1 port to be cross-connected must have aFlow IDnumber assigned toit on the E1 provisioning screen. Refer to Flow ID number rules.

5 The Flow ID number check box on the cross-connect screen must be checkedfor each E1 port to be cross-connected.

6.2.2.2 Flow ID Number Rules

The Flow ID number entered by the operator on the E1 provisioning screen is one of the

parameters the software management uses to determine source, destination, and directionof the E1 port when the data is switched in the Core Card. The following rules apply to the

Flow ID:

1 Number is unique to the entire network. It cannot be used in any other radioor hop in the network.

6.2.2.3 Cross-Connecting Ethernet to Radio Access Card

The following rules and guidelines apply to switching Ethernet ports 1 through 4 on the

Core Card through the Core card to the Radio Access Card:

1 The license key installed on the Core Card determines the Ethernet datacapacity that can be cross-connected.

2 The Ethernet port (source) and Radio Access Card (destination) must beEnabledon the respective Core Card and Radio Access Card provisioning

screens.

3 The Ethernet port to be cross-connected must have aFlow IDnumberassigned to it on the Core Card provisioning screen. Refer to the Flow ID

Number rules.

4 The Flow ID number check box on the cross-connect screen must be checked

for the Ethernet port to be cross-connected.


78/134

6-6

6.2.2.4 Cross-Connecting Ethernet to E1 Access card

1 The license key installed on the Core Card determines the capacity of theEthernet data that can be cross-connected.

2 The Ethernet port (source) and E1 Access Card (destination) must beEnabledon the respective Core Card and E1 access Card provisioning

screens.

3 The Ethernet port to be cross-connected must have aFlow IDnumberassigned to it on the Ethernet provisioning screen. Refer to the Flow ID Num-

ber rules.

4 The Flow ID number check box on the cross-connect screen must be checkedfor each Ethernet port to be cross-connected.


79/134

6-7


80/134

6-8


81/134

6-9


82/134

6-10


83/134

6-11


84/134

6-12


85/134

6-13


86/134

6-14


87/134

6-15


88/134

6-16


89/134

6-17


90/134

6-18

6.3 DIAGNOSIS MENU

Figure 6-1 Diagnosis Dropdown Menu

6.3.1 Remote Inventory

See Figure 6 -2. This screen is a read-only screen, that shows all the information on the

equipment.

Figure 6-2 Remote Inventory Screen


91/134

6-19

6.3.2 Abnormal Conditions

See Figure 6-3. This screen is a read-only screen that lists non-usual conditions present in

the NE. Events that cause an abnormal condition:

Forced switch (EPS, RPS, TPS)

Lockout (EPS, RPS, TPS)

Loopback activation

Local radio Tx mute (manual)

Local radio Tx mute (automatic)

Remote radio Tx mute (manual)

Figure 6-3 Abnormal Condition List

6.3.3 Summary Block Diagram View

Refer to CD for diagrams. These screens show functional block diagrams and signal flows

of the current configuration (1+0 with/without Ethernet, 1+1 Hot-Standby, 1+1 Frequency

Diversity), and include switching and loopback functions where applicable.


92/134

6-20

6.4 SUPERVISION MENU

6.4.1 Supervision Dropdown Menu

See Figure 6 -4for the Supervision dropdown menu.

Figure 6-4 Supervision Dropdown Menu

6.4.2 Access State Menu

See Figure 6 -5for the Access State Menu

Figure 6-5 Access State Menu

The NE can be managed by the Operating System (OS) or by the Craft Terminal (CT). The

selection of the NE manager is controlled by the Local Access Control (LAC) function. The

OS manages the NE until a request to managefrom the Craft Terminal is received (via

LAC) and granted. The request is initiated by the user clicking on theRequestedbutton on

the menu and then answeringyesto the resulting confirmation message. The LAC request

can be denied by the OS (if for example the OS is in a state of recovery from a temporary

loss of communication with the NE).

The request to managestarts a timer. If the OS doesnt answer a CT request to managein a

predefined time, the CT automatically becomes the NE manager. The predefined time is

set by the user on the LAC Time Out Period screen (See Figure 6-6).


93/134

6-21

The manager currently managing the NE is indicated on the Craft Terminal screen by the

shape of the icon with the key symbol.

Figure 6-6 LAC Time Out Period

6.4.3 MIB Management Menu

See Figure 6-7. The Management Information Base (MIB) includes all system configura-

tion data, except routing configuration data.

Figure 6-7 MIB Management Menu

CIRCULAR SHAPE

OS is managing NERECTANGULAR SHAPE

CT is managing NE

9500-107801/31/08


94/134

6-22

6.4.3.1 Backup Screen

See Figure 6 -8. This screen allows the user to save the NE configuration on a backup file.

The backup file can then be loaded on a disk or CD for backup following a crash or re-start.

Figure 6-8 Backup Screen

6.4.3.2 Restore Screen

See Figure 6 -9. This screen allows the user to download a previously created backup fileonto the NE.

Figure 6-9 Restore Screen


95/134

6-23

6.4.3.3 Remove MIB Backup File

See Figure 6-10.This screen allows the user to delete a previously created backup file.

Figure 6-10 Remove MIB Ba

9500mpr user manual v1.1

Documents