197189894-9500mpr-user-manual-v1-1

9500 MPR

Alcatel Part Number 3EM22086A

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

Issue 1, February, 2008

Microwave Packet RadioUsers Manual

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

PHONE the Call Center at888-252-2832 (US and Canada)

or613-784-6100 (International)

ALCATEL-LUCENT’S PRIMARY MISSION ISSATISFYING 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

Telephone Assistance, Normal Working Hours (CST 8am 5pm M-F)TAC supports all Alcatel North America Microwave products. This includes routine questions and emergency 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 network management. They require immediate corrective action. (Ex. Loss of network management capability, loss of traffic imminent or existing).

Conditions seriously affecting system operation. They require immediate attention. (Ex. processor outage, loss of standby equipment, loss of remote access, or network managers).

CTACTelephone Technical Support

TOC

-

1

T

able 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-2

2.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

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

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-Provisioning

A.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

TOC-4 This page intentionally left blank.

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 √

GeneralOrdering 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

√√

1-2

Figure 1 - 1 9500 MPR Family

MSS-8

Microwave Service Switch

ODU V2

Outdoor Unit

MSS-8

8 Slots

ODU

V2

9500 MPR

Microwave Packet Radio

9500-1040P

02/20/08

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 procedures are 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 User’s 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.

2-2

After installation and turn-on, operating procedures are limited to periodic alarm checks. Automatic and manual switching are provided for equipment protection. Manual switch-ing may be accomplished using the Craft Terminal screens on the computer. The follow-ing paragraphs provide operating procedures for manual switchover of protected radio systems.

2.4.1 Rx Radio Protection Switching

See Figure 2 - 1 and follow the steps to switch receive traffic between the main and standby (spare) Radio Access Cards, manually, using the Craft Terminal.

Figure 2 - 1 Rx Radio Protection Switch

CRI

0

MIN

0

MIN

0

WNG

0

IND

0

MAJ

0

COM

SUP

ALI

OS

NTP

AC

EXT

0

EQP

0

TRS

0

Synchronization ConnectionsEquipment

Equipment

NE 9500MPR-E 1.0

Slot#0 MSS-8

ODU Dir#7-Ch#1

JUSM_9500MP-E_1.0 - MSS12 - Administrator

Slot#2Slot#3Slot#4Slot#5 MSS/E-1

Slot#1 MSS/CORE-MAIN

Slot#6Slot#7 MSS/RADIO Dir#7-Ch#Slot#8Slot#9 MSS/FANS

91

5

3

7

2

6

4

8

Remote InventoryAlarms Settings

Probable CauseSeverity Event Time Entity

Alarmed and 201-5/05/07 - 20:00 42MIN Target 9500MR3-1

Include alarms from sub-nodes

Help

Protection SchemesEquipment

Settings LoopbacksMeasurements Protection 1+1 EPSAlarms Performance Monitoring

Spare 4 StandBy None Signal

Failure

Main 3 Active None Signal

Failure

Status Command CriteriaRole Slot

Apply

Help

None

NoneManualForced

Command

Commands

Equipment Protection

Tx Radio Protection

Rx Radio Protection

Spare#0 - Slot#4

Main#1 - Slot#3

Spare#0 - Slot#4

Main#1 Slot#3

Spare#0 - Slot#4

Main#1 - Slot#3

JusmMSS Path View Slot #3

Synchronization Conne

9500-1072

01/31/08

Select None (Default) if there is no command required or to release a manual or forced switch.

Select Manual if you want to switch from Main to Standby transmitter or Standby to Main transmitter and still allow the channel to switch automatically if there is a failure.

Select Forced if you want to switch from Main to Standby transmitter or Standby to Main transmitter and disable automatic switching if there is a failure, regardless of alarms.

1

4

2

3

2-3

2.4.2 Tx Radio Protection Switching

See Figure 2 - 2 and follow the steps to switch transmit traffic between the main and standby (spare) Radio Access Cards, manually, using the Craft Terminal.

Switching the radio transmitter may momentarily interrupt traffic. Before switching the transmitter, obtain permission from the proper authority.

Figure 2 - 2 Tx Radio Protection Switch

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

NE 9500MPR-E 1.0

Slot#0 MSS-8

ODU Dir#7-Ch#1





91

5

3

7

2

6

4

8





Help




Failure


Failure


Apply

Help

None

NoneManualForced

Command

Commands


Tx Radio Protection

Rx Radio Protection

Spare#0 - Slot#4

Main#1 - Slot#3

Spare#0 - Slot#4

Main#1 Slot#3

Spare#0 - Slot#4

Main#1 - Slot#3


Synchronization Connections


Select Manual if you want to switch from Main to Standby transmitter or Standby to Main transmitter and still allow the channel to switch automatically if there is a failure.

Select Forced if you want to switch from Main to Standby transmitter or Standby to Main transmitter and disable automatic switching if there is a failure, regardless of alarms.

9500-107301/31/08

1

3

4

2

2-4

2.4.3 Equipment Protection Switching

Switching E1 Access Cards may momentarily interrupt traffic. Before switching E1 Access Cards, obtain permission from the proper authority.

See Figure 2 - 3 and follow the steps to switch transmit and receive traffic (two directions with one command) between the main and standby (spare) E1 Access Cards, manually, using the Craft Terminal.

Figure 2 - 3 Equipment Protection Switch

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

NE 9500MPR-E 1.0

Slot#0 MSS-8

ODU Dir#7-Ch#1





91

5

3

7

2

6

4

8





Help




Failure


Failure


Apply

Help

None

NoneManualForced

Command

Commands


Tx Radio Protection

Rx Radio Protection

Spare#0 - Slot#4

Main#1 - Slot#3

Spare#0 - Slot#4

Main#1 Slot#3

Spare#0 - Slot#4

Main#1 - Slot#3


Synchronization Connections

9500-1074

01/31/08


Select Manual if you want to switch from Main to Standby E1 Access or Standby to Main E1 Access and still allow the channel to switch automatically if there is a failure.

Select Forced if you want to switch from Main to Standby E1 Access or Standby to Main E1 Access and disable automatic switching if there is a failure, regardless of alarms.

1

4

2

3

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 - 4 through Figure 2 - 6.

2-6

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

S-Card Status

A-NE ABNORMALALM (yellow)

W-NE WarningALM (yellow)

m-NE minor ALM (red)

M-NE MAJOR ALM (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 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

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


• Red – Card fail

• Red Blinking – Card mismatch

d

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


• 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-1028P01/31/08

2-8 This page intentionally left blank.

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

See Figure 3 - 1 and Figure 3 - 2 for 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 mm2 (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.

3-2

Short circuiting low-voltage, low-impedance dc circuits can cause arcing that may result in burns or eye injury. Remove rings, watches, and other metal jewelry while working with primary circuits. Exercise caution to avoid shorting input power 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

3-3

Do not apply battery power until it is determined that A and B battery cables with isolated returns and power cables are wired correctly. With power applied, reverse polarity on wir-ing (+batt wired to -batt pin on connector) can cause power supply 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 - 3 and Figure 3 - 3 for connections. Refer to Table 3 - 1 and Table 3 - 2 for mating cable wiring.

Figure 3 - 3 E1 Signal Cable and Connector

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/DS1 PDH Module

Distributor Subrack

(Front View)

9500-1370

11/06/07

1

1

1

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































GND 34 68 GND

3-6

Table 3 - 2 Pin Function: Tributaries 17-32

Description Pin # Pin # Description

GND 1 35 GND

































GND 34 68 GND

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 used for 10/100/1000BASE-T applications, however the CT5E cable is the recommended cable for 1000BASE-T applications. The CAT5E cable has a tighter, higher quality twisting on the wire pairs and is less susceptible to crosstalk. Refer to Table 3 - 3 and Table 3 - 4 for pinout. See Figure 3 - 5 for pair wire colors. See Figure 3 - 6 and Figure 3 - 7 for 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

3-8

Figure 3 - 5 Straight-Through Mating Cable

Figure 3 - 6 10/100BASE-T Interconnect

LMW-9053F05/24/05

12345678

12345678

WHITE-GREEN

GREEN

WHITE-ORANGE

ORANGE

WHITE-BLUE

BLUE

WHITE-BROWN

BROWN

PAIR A

PAIR B

PAIR DPAIR 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

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.

3-10

Follow carefully the following do’s and don’ts to prevent future loss of traffic.

25

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

EXCEED A 90 DEGREE BEND.

.SEIT ELBAC NETHGITREVO.SLAVRETNI MODNAR TA DNA YLESOOL SEIT ELBAC YLPPA

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

.NOISNET GNILLUP FO BL 52 DEECXE.ELBAC GNIHCTERTS DIOVA

DO

CABLE DIA.=0.20”

CABLE BENDRADIUS

DO

DO

DO

DON’T

DON’T

DON’T

DON’T

MW215–0028–1071897

3-11

3.5 USI/CONTROLLER CABLE CONNECTION TO LAPTOP (J301)

Recommended connectorized cable assembly – PN 695-7848-001 through 004 (24 AWG 6 pair shielded, jacketed cable with DEMM-9P connector on each end).

4-1

The information contained in this section is a summary of the informa-tion on the enclosed CD. “Refer to CD” is used throughout this section to 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 SEQUENCE

Perform 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.

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 user’s 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 highest level.

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 Computer icon. My Computer window displays.

C. In My Computer window, click on CD ROM icon. 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 - 1 to open communication with the radio.

4-3

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

CloseSaveRemoveNewSet CurrentGet Current

Nes Table

Type Version IP Address0.0.0.0

Site Name Site Location

Network Elements List - Target: MSS11

9500-1226P

11/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 Table Document icon.

9500-1225P

10/15/07

9500-Startup 1

12/15/07

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

Hilight the configuration line just added and click Get Current button. The information from the Get Current configuration line should automatically fill in the IP Addresss Site Name and Site Location fields.

2

34

5

1

4-4


Show Alarm Monitor

Site Name:

IP

Type:

Ne DescriptioNe DescriptioNe Descriptioarm Synthesisarm Synthesisarm Synthesis

Ne InfoNe InfoNe Info

Ne ConfigurationNe ConfigurationNe Configuration

Site Location:

Critical

Supervision

major

Minor

Warning

Indeterminate

95009-1227P

10/15/07

LABMWLAB

0

6

1

0

0

9500-Startup 2

0/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 Info

Ne Configuration

Site Location:

Critical

Supervision

Major

Minor

Warning

Indeterminate

0

0

1

2

0

Network element Overview - MSS11

95009-1226P

10/15/07

Apply

ExitShow

Click OK.

Click OK.

Click Show.

Go To

5

7

6

8

4-5


Show Alarm Monitor

Site Name:

NNN

NNN


Site Location:

major

Minor

Warning

Indeterminate

MSS11

LABMWLAB

6

1

0

0

95009-1227P

10/15/07

95009-1227P

10/15/07

Show Alarm Monitor

Site Name:

IP Address

Type:

Ne DescriptionNe DescriptionNe DescriptionAlarm SynthesisAlarm SynthesisAlarm Synthesis

Ne InfoNe InfoNe Info


Site Location:

Critical

Supervision

major

Minor

Warning

Indeterminate

9500M

MSS1

LAMWLA

0

6

1

0

0

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 the loading process.

Type in User Name.

Type in Password.

Loading Performance MIB and other processes loading status.

8

10

11

9

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 - 3 through 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

4-7

4.7.1.1 Enable E1 Access Card

See Figure 4 - 3. Follow the steps to enable the E1 Access Card(s).

Figure 4 - 3 Enabling E1 Access Card


Equiment Type

Alarm Profile Help

P32E1DS1 Apply

?EmptyP32E1DS1All Alarms

CRI

0

MIN

0

MIN

0

WNG

0

IND

0

MAJ

0

COM

SUP

ALI

OS

NTP

AC

EXT

0

EQP

0

TRS

0

Protection Schemes Synchronization ConnectionsEquipment

Equipment

NE 9500MPR-E 1.0

Slot#0 MSS-8

ODU Dir#7-Ch#1





91

5

3

7

2

6

4

8




9500-1355P10/27/07

Help

MSS/E1Module

Settings Tab.Click to see this screen.

Click to apply changes.

Choose radio module from dropdown menu.

1

3

4

2

4-8

4.7.1.2 Enable Radio Access Card

See Figure 4 - 4. Follow the steps to enable the Radio Access Card(s).

ODU is automatically enabled when Radio Access Card is enabled.

Figure 4 - 4 Enabling Radio Access Card


Equiment Type

Alarm Profile Help

MD300 Apply

?EmptyMD300All Alarms

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

NE 9500MPR-E 1.0

Slot#0 MSS-8

ODU Dir#7-Ch#1





91

5

3

7

2

6

4

8




9500-1356P10/27/07

Help

MSS/E1Module

Settings Tab.Click to see this screen.


Choose radio module from dropdown menu.

1

3

4

2

4-9

4.7.1.3 Enable Fan Unit

See Figure 4 - 5. Follow the steps to enable the Fan Unit.

Figure 4 - 5 Enabling Fan Unit

4.7.2 Provision Plug-In Cards

See Figure 4 - 6 through Figure 4 - 8 to provision MSS plug-in card parameters after the cards have been enabled.


Equiment Type

Alarm Profile Help

Fans Apply

?EmptyFANSAll Alarms

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

NE 9500MPR-E 1.0

Slot#0 MSS-8

ODU Dir#7-Ch#1





91

5

3

7

2

6

4

8




9500-1354P10/27/07

Help

MSS/FansModule

ClickSettings Tab


Choose FANS from dropdown menu.

1

3

4

2

4-10

4.7.2.1 Provision Core Card

See Figure 4 - 6. Follow the steps to provision Ethernet ports 1-4.

Figure 4 - 6 Core Card 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

NE 9500MPR-E 1.0

Slot#0 MSS-8

ODU Dir#7-Ch#1





91

5

3

7

2

6

4

8





Help

Loopback Protection 1+1 EPSAlarms-Settings

01

02

03

04

Enabled

Enabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

1000 Mb/s - Full Duplex

1000 Mb/s - Full Duplex

Enabled

Enabled

Enabled

Enabled

SettingsAlarms

Alarm Profile Bad Value

Configuration Other

Apply

Help

Apply Restart

Enabled

Port Status

Auto Negotiation Status

Adressed Capability

Rate Auto Negotiation Flow ControlPort Number Status

E1 Port#01

E1 Port#02

E1 Port#03

E1 Port#04

JusmMSS Pdh View Slot #8

Port 03

10 Mb/s - Half Duplex

10 Mb/s - Full duplex

100 Mbs - Half duplex



Enabled

Flow control Enabled

44

y

MMMM

MSS/CORE-MAINCurrent Screen.

Current provisioning for ethernet Ports #01 - #04.Area updates when Apply buttons are clicked. Click this Apply button after steps

6-7 above are accomplished.

Check to enable NE auto-negotiation functions.

Check to allow communication at the selected data rate between two locations. Choose half duplex for only one direction at a time, or full duplex for communication in both directions at the same time.

Check to enable the selected port. Uncheck to disable first in order to change any settings.

Check to enable input and output pause features.

Click Apply button after steps 1-5 above are accomplished.

Double Left Click

2

1

3

B1

B2

A1A2A3

A4

9500-1353P10/27/07

4-11

4.7.2.2 Provision E1 Access Card

See Figure 4 - 7. Follow the steps to provision E1 lines (ports) 1-32.

Figure 4 - 7 E1 Access Card Provisioning

0 00 0 00

COM

SUP

ALI

OS

NTP

AC

0 0 0


Equipment

NE9500MSS 1.0

PNU

ODU Dir#5-Ch#1

Slot#1 PNU/CORE-MAINSlot#2Slot#3Slot#4Slot#5 PNU/RADIO Dir#5-Ch#1Slot#6 PNU/E1Slot#7Slot#8Slot#9 PNU/FANS

ODU Dir#4-Ch#1

ODU Dir#8-Ch#1

91

5

3

7

2

6

4

8




95009-1324A10/02/07

Loopback Protection 1+1 EPSAlarms-Settings

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

Unframed

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

Disabled

11 TDM2TDM

SettingsAlarms

Port Number 01

Apply

Apply To AllApply

11

Flow Id (2 4080)

Flow Id

All Alarms

Alarm Profile

UnframedSignal Mode

256Payload Size

ADAPTIVETDM Clock Source

TDM2TDMService Profile

ECID Tx

ECID Rx

Flow Id Service Profile Payload Size TDM Clock SourcePort Number Signal Mode

E1 Port#01

E1 Port#02

E1 Port#03

E1 Port#04

E1 Port#05

E1 Port#06

E1 Port#07

E1 Port#08

E1 Port#09

E1 Port#10

E1 Port#11

E1 Port#12

E1 Port#13

E1 Port#14

E1 Port#15

E1 Port#16

E1 Port#17

E1 Port#18

E1 Port#19

E1 Port#20

E1 Port#21

E1 Port#22

E1 Port#23

E1 Port#24

E1 Port#25

E1 Port#26

E1 Port#27

E1 Port#28

E1 Port#29

E1 Port#30

E1 Port#31

E1 Port#32

JusmMSS Pdh View Slot #8

9500-1324B10/02/07

6

Double left click

Single left mouse click will highlight the resource. This selection causes the activation of the E1 module in the resource list area by outlining the module in blue.

Apply the Flow ID number.

Flow ID number required to transport E1 data. Enter any number between 2 and 4020.

Choose TDM2TDM if radio is being used to transport E1 data only (no Ethernet. Choose TDM2ETH if radio is being used to transport just Ethernet or Ethernet plus E1 data.

Select Adaptive to sync TDM output to packets.

Select to sync TDM output to NE Synchronization source.

Select TDM Line In to sync TDM output to TDM input.

The purpose of TMN Clock Source provisioning is to select the mode that will be used to sync TDM #1 data to the node Synchronization source. The user can select one of three modes: Adaptive, Differential, and TDM_Line_In.

1

2

3

6

4

5

79 8

9500-1324AB02/15/08

CAUTION

Possibility ofService

Interruption

Flow ID number is system unique and must not be repeated in radio network. Loss of E1 data can occur.

4-12

4.7.2.3 Provision Radio Access Card

See Figure 4 - 8. Follow the steps to provision the Radio Access Card.

Figure 4 - 8 Radio Access Card Provisioning

Alarms

JusmMSS Radio Main Fiew Slot #7 - MSS12

Direction #7 Channel #1

Settings Performance Monitoring Measurements Loopback

Capacity 104 Mb/s

Modulation 32QAM

Ch Spacing 27 50 MHzShifter

Range Tx Freq 10688750

TxFreq (KHz) 108000000

RxFreq (KHz) 113800000

Enabled

ATPC Enabled

Link Identifier Configuration

Enabled

Expected Identifier 0

Sent Identifier 0

Apply Help Refresh

Routing IP Protocol

OSPF None

OSPF Area

Remote Address

0.0.0.0

Alarm Profile

All Alarms

Tx Mute

Local

Remote

Enabled

Enabled

Auto

Alarm Profile

All Alarms

Off

500 MHz

Tx Power(d8m) 15.0

RTPC (4.0..21.5

Frequency

PPP RF

Help

COM

SUP

ALI

OS

NTP

AC


Equipment

NE9500MSS 1.0

PNU

ODU Dir#5-Ch#1

Slot#1 PNU/CORE-MAINSlot#2Slot#3Slot#4Slot#5 PNU/RADIO Dir#5-Ch#1Slot#6 PNU/E1Slot#7Slot#8Slot#9 PNU/FANS

ODU Dir#4-Ch#1

ODU Dir#8-Ch#1

91

5

3

7

2

6

4

8




95009-1324A10/02/07

to

Double left click

Click to go to this screen.

Enter XMT RF Frequency within allowed range

TX power range with ATPC disabled

Check to enable ATPC

Displays RCV RF Frequency.Result of calculation: RX Freq - TX Freq - Shifter Freq

Settings Tab.Click to open.

Select XMT (Go) and RCV (return)

Separation Frequency from drop down list.

490.0 MHz

500.0 MHz

530.0 MHz

Undefined

Select XMT (Go) and RCV (return)

Separation Frequency from drop down list

490.0 MHz

500.0 MHz

530.0 MHz

Undefined

1

2

43

5

6

789

3

95009-1371P01/19//08

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 - 9 for 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 the master, 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 primary source 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.

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

ou

ng

Po

c

nc

Syn

O

Pr

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

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

e

n

Pr

e

Free Run Local Os

T1 Port

e

a

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

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 sync’ed 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

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-SPARE

PNU/RADIO-Dir#3-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 TimeNetwork ConfigurationAlarm SeveritiesSystem SettingsXConnectionsProfiles Management

NTP Configuration

Routing Information

Configuration

IP ConfigurationEthernet 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 Server configuration.

4

7

6

5

2 31

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




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

4-19

Figure 4 - 13 E1 Crossconnect

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

Views Configuration Diagnosis Supervision SW Download Equipment

NE 9500MPR-E 1.0

Slot#0 MSS-8

ODU Dir#7-Ch#1





91

5

3

7

2

6

4

8

Remote InventorySettings

Probable CauseSeverity

Alarmed and 201-5/05/07 - 20:00 42MIN

Help

Cross Connections

Slot #5 PDH

Slot #7 RADIO

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

Refresh CloseApply

Ok AllCancel

ALL11 12 0 0

ALL0 0 0 0

ALL0 0 0 0

ALL0 0 0 0

ALL0 0 0 0

ALL0 0 0 0

ALL0 0 0 0

ALL0 0 0 0

a

55

77

Click on PDH box (source)

and drag line to radio box

(destination)

Double left click anywhere

on line to open line select

dialog box

Click to open Cross

Connections Screen

1

2

3

4

Flow ID required to transport

9500-1396-REV01/31/08

4-20

4.7.6 Provision System

See Figure 4 - 14. Follow the steps to provision tributary port impedance, quality of service classification, and enter NE MAC address.

Figure 4 - 14 System Setting

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

Views Configuration Diagnosis Supervision SW Download Equipment

NE 9500MPR-E 1.0

Slot#0 MSS-8

ODU Dir#7-Ch#1





91

5

3

7

2

6

4

8


Severity Event Time

MIN

Help

NE Time

Network Configuration

Alarm Severities

System Settings

Cross Connections

Profiles Management

NE Configuration

System Settings

Unbalance 75 Ohm

Balance 120 Ohm

HelpClose

Apply

Tributary Port Configuration

Impedance

Unbalance 75 Ohm

Priority Apply

Tributary Port Configuration

QoS Classification

00:00:00:00:00:00

NE MAC Address

Bridge Address

Disabled

Priority

Differentiate Services

atioon

1

3

5 6

4

2

Read-only field indicates source address for TDM2ETH connection that is stored on the flash card (installed on the Core Card).

Select Balance 75 Ohm if tributary cable is coax.

Select Balance 120 Ohm if tributary cable is twisted pair.

Priority forwarding disabled

Each packet is classified based on presence of valid 802.1p user priority tag.

Each packet is classified based on DSCP field in IP header to determine priority.

9500-108502/20/08

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/FANS

3

357

468

5 7

4 6 8




NTP Configuration

Routing Information

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 dialog for the IP Configuration.

Enter NE IP address.

4

5

21 3

4-22

4.7.8 Provision Ethernet Port 4

See Figure 4 - 16. Follow the steps to provision Ethernet Port 4 on the Core Card to carry SNMP data.

Figure 4 - 16 Ethernet 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/FANS

3

7 8

5 7

4 6 8




Local ConfigurationNTP Configuration

Routing Information

Configuration


Ethernet Configuration


Port 4 (Core) Ethernet Configuration


IP Routing Protocol OSPF Area NumberStatic Routing 0

IP Address IP Mask172.22.174.219 255.255.255.192

TMN Ethernet MAC AddressEnabled 00113FC0D04D

IP Routing Protocol OSPF Area NumberStatic Routing 0

IP Address IP Mask10.0.2.2 255.255.255.0

TMN Ethernet MAC AddressEnabled 00113FC0D04D

Refresh Help CloseApply

95009-1331P01/18/08

Click to display pop-up dialog for the IP Configuration.

Enter IP address for radio

Enter IP Mask

Select Static Routing for manual routing. Select OSPF (Open Shortest Path First protocol) for automatic routing.

21 3

5

4

7

6

4-23

4.7.9 Provision IP Static Routing

See Figure 4 - 17. Follow the steps to provision.

Figure 4 - 17 IP Static Routing 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

NE 9500MPR-E 1.0

Slot#0 MSS-8

ODU Dir#7-Ch#1


Slot#2Slot#3Slot#4


Slot#6Slot#7 MSS/RADIO Dir#7-Ch#1Slot#8Slot#9 MSS/FANS

91

5

3

7

2

6

4

8




HelpViews Diagnosis SupervisionConfiguration

NE Time


Alarm Severities

System Settings

Cross Connections

Profiles Management

Local Configuration

NTP Configuration


IP Configuration

Routing InformationIP Static Routing Configuration

OSPF Area Configuration

IP Point to Point Configuration

IP Static Routing Configuration

Interface TypeIP Address IP Mask

Gateway0.0.0.0. 0.0.0.0.

IP Address

Default Gateway or Point To Point I/F Choice

IP Mask

Default Gateway IP Address Interface Type

Host or network Address Choice

Default Gateway

172.22.174.193

Host Network

Default Gateway IP Address

0.0.0.0. Gateway

Point to Point Interface Index

CloseHelpDeleteCreate

Route to a specific IP address.

Input IP address

List of RF path directions.Click to view drop down list.

Create new or change existing IP static routes.

IP Mask

Click now to display pop-up

IP interface to a host or network. Typically used at a spur to interface a host over the RF path. In this scenario, the Default Gateway IP Address is 0.0.0.0 and the IP Mask (greyed out) is 0.0.0.0. Also typically used at an end terminal in a radio link for interface with the network.

1 2

3 4

5

6

8

10

7

9

95009-1352P11/5/07

4-24

4.7.10 Provision OSPF Static Routing

See Figure 4 - 18. Follow the steps to provision Open Shortest Path First (OSPF) protocol static (automatic) routing.

Figure 4 - 18 OSPF Static Routing 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

NE 9500MPR-E 1.0

Slot#0 MSS-8

ODU Dir#7-Ch#1




Slot#6Slot#7 MSS/RADIO Dir#7-Ch#1Slot#8Slot#9 MSS/FANS

91

5

3

7

2

6

4

8




95009-1351P11/5/07

HelpViews Diagnosis SupervisionConfiguration

NE Time


Alarm Severities

System Settings

Cross Connections

Profiles Management

Local Configuration

NTP Configuration


IP Configuration

Routing InformationIP Static Routing Configuration


IP Point to Point Configuration


Stub FlagId OSPF Area Address

False0 0.0.0.0.

0.0.0.0.

new

OSPF Area Address

False

OSPF Area Stub Flag

DeleteCreateApply CloseHelp

IP Static Routing Configuration screen. Click to display pop-up

1 2

3 4

5-1

The information contained in this section is a summary of the on the enclosed CD. “Refer to CD” is 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 cause severe 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.

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)/LAPTOP

Connect 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 confirm which end of an alarmed link is faulty?

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 should include 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 for details.

• 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 opening screen 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.

5-4

Table 5 - 1 Alarm Matrix

Equipment Alarm DescriptionConfiguration/Alarm Most Probable

CauseAction

1+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 not match card configured in core memory

Install correct configured card

Card Missing N/A Minor Minor Core card is missing from 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 4 on Core Card

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

PPP IP Fail Minor Minor Minor

LOS on Gigabit ETH Interface

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

Check link partner and cable between link partner and ETH 1-4 connector

Firmware Download In Progress

Minor Minor Minor Status of download Wait for downloading to complete

LOS on Sync Interface Minor Minor Minor No sync clk detected at Sync in port on Core Card

Check sync source and cable between sync source and Sync in port

Degraded Signal on Sync Interface

Minor Minor Minor Sync clk errors detected at Sync in port on Core Card

Check sync source for errors

License Mismatch for Equipment Provisioned

Major Major Major Wrong flash card installed on Core Card

Install correct flash card for license

E1 Access Card

Card Fail Major Minor Minor Failure of E1 Access Card

Replace E1 Access Card

Equipment Mismatch Major Minor Minor Card in slot does not match Card configured in Core memory


Card Missing Major Minor Minor E1 Access Card is missing from slot

Install E1 Access Card in slot

Unconfigured Equipment Major Major Major Card is not Enabled on the Settings screen

Enable card

LOS on PDH Tributary Major Minor Minor No E1 input signal detected on any one or more of 32 lines

Check E1 source and/or cable

Degraded Signal Minor Minor Minor Errors on input signal detected on any one or more of 32 lines

Check E1 source

AIS on PDH Tributary (RX)

Major Major Major AIS detected by the receive circuits on one or more E1 lines, indi-cating upstream failure

Check for upstream E1 source for errors

AIS on PDH Tributary (TX)

Major Major Major AIS detected on one or more E1 lines at input to PDH 32xE1 Access Card

Check E1 source

5-5

Loss of CESoETH Frame Major Major Major Packets are not being received by the emula-tion circuits

1. Check/troubleshoot farend alarms

2. Replace alarmed E1 Access Card

Jitter Buffer Overrun Major Major Major Packet overflow caus-ing buffer spill. Could be caused by sync problem or E1 Access Card circuit failure

1. Verify sync provision-ing at both ends of hop


2. Troubleshoot sync problem between local and farend

Jitter Buffer Underrun Major Major Major Buffer spill. Could be caused by sync prob-lem or E1 Access Card circuit failure

1. Verify sync provision-ing at both ends of hop


2. Troubleshoot sync problem between local and farend


Minor Minor Minor Status of download Wait for downloading to complete

Fans Unit Card Fail Major – – Fan failed Replace fan unit

Card Missing Major – – Fan unit is missing from slot

Install fan unit

Unconfigured Equipment Minor Minor Minor Unit is not Enabled on the Settings screen

Enable fan unit

Radio Access Card

Card Fail Major Minor Minor Radio Access Card failed

Replace radio Access Card

Equipment Mismatch Minor Minor Minor Card in slot does not match card configured in Core memory


Card Missing Major Minor Minor Radio Access Card is missing from slot

Install Radio Access Card in slot

Unconfigured Equipment Minor Minor Minor Card is not Enabled on the Settings screen

Enable card

PNU Cable Loss Major Minor Minor Bad cable connection at IF in/out connector on Radio Access Card

Check/repair IF cable connection on alarmed Radio Access Card

Loss of Radio Frame Minor Minor Minor Farend XMTR prob-lems, RF path prob-lems, or local circuit failures have caused BER to increase to the point that frames are being lost

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


3. Replace alarmed Radio Access card

Table 5 - 1 Alarm Matrix (Cont.)


CauseAction

1+0 1+1 HS 1+1 FD

5-6

Loss of Alignment N/A Minor Minor Delay between main and protect RF paths detected

1. Replace main Radio Access Card

2. Replace protect Radio Access Card

3. Replace main ODU4. Replace protect ODU

Demod Function Fail Major Minor Minor Internal receive circuit failure

Replace Radio Access Card

High BER Major Minor Minor Bit Error Rate thresh-old (10E-4) exceeded on RCVR input circuits on modem

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

2. Verify RSL is above RCV threshold. a). If not – check upstream XMTR output/trouble-shoot XMTR. b). If ok,

3.

Early Warning N/A Minor Minor 10E-9 BER detected No action is required at this time. Monitor receive signal for increased degrading

ATPC Loop Minor Minor Minor Loss of ATPC command path between farend XMTR and local RCVR

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


3. Replace alarmed Radio Access Card

Link Identifier Mismatch Major Major Major Link identifier number provisioned on Radio Access Card settings screen is different from link identifier number provisioned at other end of hop

Set numbers at both ends of hop to match

TCA on Radio Link N/A N/A Major Alarm threshold exceeded on standby Radio Access Card


TCA on Radio Hop Major N/A Minor Alarm threshold exceeded on standby Radio Access Card after switching from main to standby

UAT on Radio Link N/A N/A Major 10 consecutive SES (unavailable time period) detected on main Radio Access Card




CauseAction

1+0 1+1 HS 1+1 FD

5-7

UAT on Radio Hop Major N/A Minor 10 consecutive SES (unavailable time period) detected on standby Radio Access Card after switching from admin to standby


Minor Minor Minor Download status Wait for downloading to complete

LOS on Sync Interface Minor Minor Minor Loss of sync clock detected

1. Replace Radio Access Card

Degraded Signal Minor Minor Minor Bit errors have increased and have exceeded degraded signal threshold

1. Replace Radio Access Card

License Mismatch for Equipment Provisioned

Major Major Major Modem card type does not match card type stored in memory on the Core Card flash card

Replace Radio Access Card with correct card type

ODU Card Fail Major Minor Minor ODU failed Replace ODU

Equipment Mismatch Major Minor Minor ODU does not match ODU configured in Core memory

Replace ODU

RCV Function Fail Major Minor Minor ODU RCVR circuit failed

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 shifter value not supported by ODU

Re-configure shifter value

TX Power Mismatch Minor Minor Minor Configured TX power value not supported by ODU

Re-configure TX power value

Software Mismatch Minor Minor Minor Software version on ODU does not match software version on Core

Download correct soft-ware version

ODU Not Responding Minor Minor Minor Loss of communication with ODU

1. Replace ODU2. Replace alarmed

Radio Access Card


Minor Minor Minor Download status Wait for downloading to complete

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



CauseAction

1+0 1+1 HS 1+1 FD

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.3 for 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 before replacing, 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 a plug-in is replaced.

5.4.3 Troubleshooting Path Problems

A path-related problem, with the exception of interference, is characterized by traffic being similarly 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.

5-9

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

• Only in worst case situations, such as an antenna knocked out of alignment, 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, and the path has potential for it to be obstructed 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.

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 planning stage, 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 incorrect for the configuration.

SW/HW Incompatible: Typically raised when new hardware is plugged into an existing 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 assignments for 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.

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 - 2 for detail trouble-shooting using the LEDs locally at the alarmed site.

Table 5 - 2 Troubleshooting Ethernet Problems

LED Indication Probable Cause Corrective Action

ETH IN LOS

Green LED Not Lit

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

1. Cable between link partner and radio is disconnected/broken.

Connect/repair cable.

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

1. Check local Ethernet provisioning screen.

2. Check link partner provisioning.

ETH OUT LOS

Green LED Not Lit

Loss of Ethernet XMT/radio RCV signal out. 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 Tx Out ok?Yes - Check path, antenna, waveguide/cablingNo - Check/replace farend radio Access Card.

2. Loss of Ethernet input to radio Access Card

Check farend for Ethernet alarms.Are any alarms indicated?Yes - Troubleshoot farend alarmsNo - Check farend Ethernet status. Is only abnormal status indicated?Yes - Troubleshoot farend Ethernet status.No - 1. Replace local alarmed Core Card.2. Replace local radio Access Card.

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 observed by 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 - 3 for detail TMN network troubleshooting.

5-13

Table 5 - 3 TMN Network Troubleshooting

Problem Possible Cause Possible Solution

Unusually slow communica-tion in radio network

1. Normal network management traffic is saturating the communi-cations channel.

1. There may be too many radios being managed within a single region. Split the radio network management into different regions and backhaul the traffic for each region through sepa-rate channels.

2. Polling radios for PM data or missed alarms too rapidly

2. Poll the radios more slowly.

3. Multiple remote software down-loads in process

3. Download to fewer radios at a time.

4. IP traffic other than network management traffic being routed through radio network

4 Configure external routers to allow only network management related traffic through the Man-agement network of the radios. Dynamic route updates (OSPF, RIP) may attempt to reroute high speed traffic through the TMN network if a high speed ink fails.

Unable to operate controls using SNMP

To perform control operations, the Manager must be registered as a craft device.

Register the Manager as a craft device. Manager registration type can be changed as needed to type ‘ct’ to allow control operation and then be changed back to ‘nml’ for normal operation.

Can Read SNMP objects but cannot Write to SNMP objects

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

2. Insufficient SNMPv3 privileges 2. Use the correct privileges:a) The TMN Interface supports 4

view levels. Use a SNMPv3 user account that supports write access to the selected SNMP object.

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 community string.

5-14

5.5 CARD REMOVAL AND REPLACEMENT

The basic rules for installing plug-in cards are as follows:

Never install, change or remove a card without first connect-ing to the shelf with an ESD grounding cable. Failure to do so may cause ESD damage to the cards.

No traps being received from NE

1. Manager not registered in NE to receive traps

1. Register Manager with NE.

2. Communication failure in net-work

2. Check network connectivity. Check redundant network paths and routing. Traceroute (tracert) is useful for locating path or rout-ing faults.

Unable to communicate with the NE through the radio network (unable to ‘ping’ the NE)

Possible communication path failure or routing failure within the radio net-work

Use traceroute (tracert) to help locate for communication path or routing problems.

Can ‘ping’ the TMN Inter-face but cannot communi-cate with the NE using SNMP, or can only see a few SNMP objects in the NE.

1. Using incorrect SNMP version at manager

1. Note the TMN card ships in SNMPv3 mode. If SNMPv2 operation is desired, it must be provisioned for SNMPv2 using the TUI.

2. If using SNMPv2, using the wrong community string. If using SNMPv3 using wrong user-name/passphrase pair

2. Verify community string or user-name/passphrase.

Table 5 - 3 TMN Network Troubleshooting (Cont.)

Problem Possible Cause Possible Solution

5-15

Plug-ins must be withdrawn and inserted using their finger-grip fastener/pulls. Never withdraw or insert using attached cable(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 to bring the plug-in panel flush with the front panel. Improper alignment 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 or a 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 voltage is 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.

5-16

Removing an in-service card in an unprotected link will cause loss of traffic. Removing an in-service card in a protected link requires 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.

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

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

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

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 Guidelines

6.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 E1 ports that can be cross-connected.

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

3 Each E1 port to be cross-connected must be Enabled on the E1 provisioning screen.

4 Each E1 port to be cross-connected must have a Flow ID number assigned to it 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 checked for 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 direction of 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 radio or 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 data capacity that can be cross-connected.

2 The Ethernet port (source) and Radio Access Card (destination) must be Enabled on the respective Core Card and Radio Access Card provisioning screens.

3 The Ethernet port to be cross-connected must have a Flow ID number assigned 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.

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 the Ethernet data that can be cross-connected.

2 The Ethernet port (source) and E1 Access Card (destination) must be Enabled on the respective Core Card and E1 access Card provisioning screens.

3 The Ethernet port to be cross-connected must have a Flow ID number assigned 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 checked for each Ethernet port to be cross-connected.

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

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.

6-20

6.4 SUPERVISION MENU

6.4.1 Supervision Dropdown Menu

See Figure 6 - 4 for the Supervision dropdown menu.

Figure 6 - 4 Supervision Dropdown Menu

6.4.2 Access State Menu

See Figure 6 - 5 for 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 manage from the Craft Terminal is received (via LAC) and granted. The request is initiated by the user clicking on the Requested button on the menu and then answering yes to 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 manage starts a timer. If the OS doesn’t answer a CT request to manage in 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).

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 NE

RECTANGULAR SHAPE

CT is managing NE

9500-107801/31/08

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 file onto the NE.

Figure 6 - 9 Restore Screen

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 Backup File

6.4.3.4 Activate MIB File

See Figure 6 - 11. This screen allows the user to activate a previous removal or restore action.

Figure 6 - 11 Activate MIB File

6-24

6.4.4 SW License

See Figure 6 - 12 for the SW License screen. This screen is a read-only screen that shows all the license key information on the flash card installed on the main Core Card.

Figure 6 - 12 SW License

A-1

A TCO SUITE – PRE-PROVISIONING

Please refer to the Software Package Installation section on the enclosed CD which explains how to prepare the TCO Suite and Craft Terminal environment in your PC.

A.1 TCO MAIN MENU

A.1.1 Pre-Provisioning Menu

Create and modify provisioning files using the Pre-Provisioning Tool.

Figure A - 1 TCO Main Menu

Open Java runtime environment and start pre-provisioning.

9500-110102/28/08

A-2

Figure A - 2 Java Runtime Environment Loading

A-3

After loading the JRE package, the screen below will display.

Figure A - 3 TCO Tool Screen

Click the Open button to open a previously downloaded file.

Click the Create button to create a new provisioning file. 9500-1086

02/25/08

1

Step 1 of 8

A-4

A.1.2 Configuration Screen Options

The screen below is a generic one that depicts all of the pull-down options possible depend-ing on which card is selected in the card slot. Protections options shown below are for all cards. See the screens shown below for more information.

Figure A - 4 Configuration Options Screen

9500-108702/25/08

2

Protections options for the Core cards

Protections options shown for Slot 3 and Slot 4



Step 2 of 8

A-5

Figure A - 5 Core Configuration (Sheet 1 of 2)

E1 Access Card Icon

When checked this feature enables input and output pause features

Check to enable auto negotiation

9500-108802/25/08

Note: 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.

Ethernet Icon

Check to enable the selected port

Check to allow communication at data rate but in only one direction at a time.

Check to allow communication at data rate in both directions at the same time.

Radio Access Card Icon

Step 3 of 8

A-6

Figure A - 5 Core Configuration (Sheet 2 of 2)

9500-108902/25/08

Select TMN if ETH Port 4 on the Core Card is used for SNMP data.

Select Transport if ETH Port 4 on the Core Card is used to transport Ethernet data.

Each packet is based on DSCP field in IP header to determine priority.

Priority forwarding disabled.

Step 3 of 8

The Quality Of Service feature enables priority forwarding in the Core Card switch based on how the packets are tagged: not tagged or tagged 802.1p or DiffServ. For general traffic, the packets are not tagged and QOS can be disabled. The user has to know if the packets are tagged, and if tagged 802.1p or DiffServ in order to know which QOS function to chose.

Each packet is classified based on presence of valid 802.1p user priority tag.

A-7

Figure A - 6 E1 Configuration

9500-109002/25/08

Choose TDM2TDM if radio is being used to transport E1 data only (no Ethernet).

Choose TDM2ETH if radio is being used to transport just Ethernet or Ethernet plus E1 data.

Flow ID is unique to network. No two Flow IDs in a network can be the same.

Rx Over-the-hop ID. Must match Rx/Tx ID at other end.

Select Unbalance 75 Ohm if tributary cable is coax.

Select Balance 120 Ohm if tributry cable is twisted pair.

The purpose of TMN Clock Source provisioning is to select the mode that will be used to sync TDM E1 data to the node Synchronization source. The user can select one of three modes: Adaptive, Differential, and TDM_Line_In.

Select Adaptive to sync TDM output to packets.

Select Differential to sync TDM output to NE Synchronization source.

Select TDM_Line_In to sync TDM output to TDM input.

Tx Over-the-hop ID

Step 4 of 8

A-8

Figure A - 7 Radio Provisioning (Sheet 1 of 2)

Step 5 of 8

Select Not Revertive if you want traffic on the protection channel to stay on the protection channel when alarms clear or a switch command is released. Traffic can be manually switched back to the main channel.

Select Revertive feature if you want traffic on the protection channel to automatically switch back to the main channel when alarms clear or a switch command is released.

9500-109102/27/08

Select Static Routing for manual routing.

Check to enable radio ID mismatch function.

Enter number from 1 to 100 for Transmitter ID. Must match associated Transmitter ID at other end of hop.

Enter number from 1 to 100 for Receiver ID. Must match associated Receiver ID at other end of hop.

Click to enable Open Shortest Path First protocol.

Check to enable PPP RF port. When not checked (disabled) user cannot change:

• Routing IP Protocol• OSPF Area• Remote Address

A-9

Figure A - 7 Radio Provisioning (Sheet 2 of 2)

Step 5 of 8

Select nominal bit rate for quantity of E1 lines being used.

Read-only field for modulation scheme

9500-109202/27/08

TX RF Frquency is automatically entered by ODU when ODU is connected to MSS. If the ODU is not connected to the MSS, enter the TX RF frequency, within allowed range.

Check to enable ATPC.

Select TX (Go) and RX (Return) separation frequency from drop-down list.

Power detected at output of TX filter on ODU.

Check to enable ATPC.

A-10

Figure A - 8 Synchronization Configuration

Step 6 of 9

Synchronization Role. Master or Slave.

9500-110202/28/08

RevertiveSwitches sync source back to primary source after alarm on primary source clears.

Non-RevertiveDoes not switch back to primary source after primary alarm clears and stays on secondary sync source.

Free Run Local OscillatorLocal oscillator on Core Card. Normal Master primary sync source.

Any Available E1Clock from E1 source via E1 peripheral.

Synch-Out Port ConfigurationConnector that can be used to provide sync to another radio or ancillary equipment.

Synch-In PortSClock from external source received on the Sync In connector on the Core card.

A-11

Figure A - 9 Cross Connections Configuration (Sheet 1 of 6)

Step 7 of 9

White ETH icons: A white icon indicates the source/destination is unavailable. Check to make sure the card is enabled.

Blue ETH icons: 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 portswill be accepted.

Green ETH icons: A green icon indicates that the source and destination are available and the destination can accept more E1 ports.

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

9500-1094

02/28/08

A-12


Step 7 of 9

Black Line: E1 to Radio connection.Click on this line to display the popup window shown below.

Indicates Flow ID has been created on the Radio Access Card Settings screen. A Radio Access line must have a Flow ID to be cross-connected. Flow ID is unique to network. No two Flow IDs in a network can be the same. Flow ID number is required to transport E1 data. Enter any number between2 and 4080.

9500-1096

02/28/08

A-13


Step 7 of 9

E1 Access Card icon.A green icon indicates that the source and destination are available and the destination can accept more E1 ports.

Black Line: E1 to Radio connection.

9500-1097

02/28/08

A-14

Figure A - 9 Cross Connections Configuration (Sheet 4of 6)

Step 7 of 9

Enter MAC address of link partner (External Ethernet Equipment).

The purpose of TMN Clock Source provisioning is to select the mode that will be used to sync TDM E1 data to the node Synchronization source. The user can select one of three modes: Adaptive, Differential, and TDM_Line_In. Select Adaptive to sync TDM output to packets. Select Differential to sync TDM output to NE Synchronization source. Select TDM_Line_In to sync TDM output to TDM input. Click now for more details.

Flow ID is unique to network. No two Flow IDs in a network can be the same.

Tx Over-the-hop ID.

Blue Line: E1 to Ethernet connection.

Rx Over-the-hop ID. Must match Rx/Tx ID at other end.

9500-1098

02/28/08

A-15

Figure A - 9 Cross Connections Configuration (Sheet 5of 6)

Step 7 of 9

Indicates Flow ID has been created on the Radio Access Card Settings screen. A Radio Access line must have a Flow ID to be cross-connected. Flow ID is unique to network. No two Flow IDs in a network can be the same. Flow ID number is required to transport E1 data. Enter any number between2 and 4080.


9500-1099

02/28/08

A-16



9500-1100

02/28/08

Step 7 of 9

A-17

Figure A - 10 Network Configuration

Step 8 of 9

9500-110402/29/08

Enter local IP Address.

Enter IP Address for radio.

Enable TMN VLAN feature on Core.

Displays status (Enabled when checked) of NTP Protocol provisioning on NTP Server Configuration screen.

Displays the IP address of the Main NTP server entered as Main Server address on the NTP Server Configuration screen.

Displays the IP address of the Spare (standby) NTP server entered as Spare Server address on the NTP Server Configuration screen.

Select Static Routing for manual routing. Select OSPF (Open Shortest Path First Protocol) for automatic routing.

A-18

Figure A - 11 Typical Report Panel

Step 9 of 9

9500-110302/28/08

B-1

B COMMISSIONING

This appendix provides a summary of the commissioning process and commissioning tests for the 9500 MPR.

B.1 COMMISSIONING PROCESS

Commissioning ensures the 9500 MPR:

• Is installed correctly

• Is configured correctly

• Has passed all tests

• Is operating to plan and running error-free

• Has had all relevant data recorded

• Is ready to carry traffic

B.2 COMMISSIONING TESTS

Tests are described for:

• BER

• E1 Port Error Measurements

• Ethernet Port Error Measurements

• TX Output Power and RSL Measurements

B.3 COMMISSIONING RECORDS

Refer to Appendix B for a recommended commissioning form. Refer to Appendix C for an alternate method of recording provisioned data using the radio built-in record keeping function NERexport.txt.

B-2

B.4 TRIBUTARY FUNCTIONALITY TEST

PURPOSE:

Verify the point to point Tributaries quality

REQUIRED INSTRUMENTS:

2 E1 error analyzer/pattern generators

PROCEDURE:

a. At local end of hop, on E1 patch panel, connect error analyzer/pattern generator 1 output to E1 #1 IN connector.

b. At local end of hop, on E1 patch panel, connect error analyzer/pattern generator 2 input to E1 #1 OUT connector.

c. Perform one minute BER test.

d. Verify zero errors on analyzer/pattern generator 2.

e. Repeat steps a through d for E1 #2 through #32.

Figure B - 1 E1 Line BER Test Setup

9500-137611/19/07

LocalRemote

IN

OUT

Error Analyzer/ Pattern Generator 2

Error Analyzer/ Pattern Generator 1

E1 #1

IN

OUT

CablePN - TBD

E1 #1

Looop

B-3

B.5 ETHERNET DATA CHANNEL (OPTIONAL) FUNCTIONALITY TEST

PURPOSE

Verify the point to point Ethernet Data Channels quality

REQUIRED INSTRUMENTS

2 Ethernet Data Analyzers

PROCEDURE

a. At local end of hop, on core module, connect Ethernet data analyzer to Ethernet port 1.

b. At remote end of hop, on core module, connect Ethernet data analyzer to Ethernet port 1.

c. Perform 10 minute BER test on Ethernet port 1.

d. Verify zero errors on Ethernet data analyzer.

e. Repeat steps a through d for Ethernet ports 2, 3, and 4.

Figure B - 2 Ethernet BER Test Setup

B.6 TX OUTPUT POWER AND RSL

PURPOSE

Verify via CT the Transmitted (Ptx) and received (Prx) power


PC with Craft Terminal software

9500-137711/27/07

LocalRemote

Ethernet DataAnalyzer

Ethernet DataAnalyzer

B-4

PROCEDURE

a. Connect CT to MSS main core module.

b. Open Measurements screen for Direction # and Channel #. See Figure B - 3

c. In the Sample time (sec), select suitable measurement polling time.

d. Press Start. Pressing “Start” will prompt a graphic monitoring view of the transmitted and received levels. See Figure B - 4.

Figure B - 3 Opening Measurements Screen

JusmMSS Radio Main View Slot#7 - MSS12

LoopbackMeasurementsPerformance MonitoringSettingsAlarms

Log file: CT_V00.07.06\MPRE_CT_V00.07.06\MSS12_MWLAB_Dir#7_ch#1.txt

Sample Time (sec) 2 Start

Help

Create File

Views

Radio

Direction #7

Channel #1


LoopbackMeasurementsPerformance MonitoringSettingsAlarms

Days:


Sample Time (sec) 2 Start

Help

Create File Read File Select File

Views

Radio

Direction #7

Channel #1


Performance MonitoringSettingsAlarms

Days:


7

Sample Time (sec)

Hours: 0 Minutes: 0

Measurement Interval

Direction#7 Channel#1

2 Start

Help

Create File Read File Select File

Views

Radio

Direction #7

Channel #1

RR o o

ee

aa

tt

VV

9500-1993

11/26/07

1

2

3

4

5 6

B-5

Figure B - 4 Tx and Rx Power Levels

B.7 HOP STABILITY TEST

PURPOSE

Verify the Hop stability


E1 Error Analyzer/Pattern Generators

PROCEDURE

The Hop stability test is performed during two consecutive hours, one time, on any one Tributary, in working condition regardless of the protection configura-tion (1+ 0 or 1+1).

The two hours stability test must be free of error in normal propagation condi-tions (out of fading period)

Refer to Para A.4. Repeat procedure for selected E1 tributary for 2 hours.

B-6 This page intentionally left blank.

C-1

Customer’s Logo

C FORMS

C-2

Customer’s Logo

C-3

Customer’s Logo

C-4

Customer’s Logo

C-5

Customer’s Logo

C-6

Customer’s Logo

C-7

Customer’s Logo

C-8 This page intentionally left blank.

D-1

D NEReport.txt

Report file NEReport.txt is created automatically by radio software and available on the web for customers approval of provisioning. The report can be opened by using the follow-ing URL:

http://Radio IP Address

The report is password protected. Enter the password assigned to the radio at provision-ing. Refer to the sample report NEReport.txt in this appendix.

a. On main browser screen, type in url: http://IP address of NE. Password screen displays.

b. Enter NE user ID and password (same as user ID and password entered on CT).

c. On Main menu, select Configuration Info. NEReport.txt screen (Figure D - 1) displays. Refer to Figure D - 2 for a sample report.

D-2

Figure D - 1 NEReport.txt

File Edit View Favorites Tools Help

9500MSS Web Server: Active Alarms - Internet Explorer

NE Report.txt - Notepad

File HelpFormat ViewEdit

9500-139211/21/07

Address http://172.22.174.219/

Main MenuConfiguration

> Date & Time Setting> Configuration Setting> Configuration Info> Get Configuration file

Alarms> Active alarms

Administration

Logout

> License Info

11

12

13

D-3

NEReport.txt

Figure D - 2 Sample Report (Sheet 1 of 4)

D-4

NEReport.txt


D-5

NEReport.txt


D-6

NEReport.txt


197189894-9500mpr-user-manual-v1-1

Documents

emergency service

affecting service

loss of standby equipment

customer service agent

loss of traffic imminent

customer service agents

network managers

technical assistance