CTR 8500-8300 3.5.20 CTR Portal - January2018

CTR 8500-8300
CTR Portal
Version 3.5.20
260-668241-001
CTR PORTAL
Copyright & Terms of Use

January 2018
This documentation incorporates features and functions provided with CTR 8500-8300
CTR Portal, version 3.5.20.
Copyright © 2018 by Aviat Networks, Inc.

All rights reserved.
No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval
system, or translated into any language or computer language, in any form or by any means,
electronic, magnetic, optical, chemical, manual or otherwise, without the prior written
permission of Aviat Networks Inc.
To request permission, contact [email protected].
Warranty
Aviat Networks makes no representation or warranties with respect to the contents hereof
and specifically disclaims any implied warranties or merchantability or fitness for any
particular purpose.
Further, Aviat Networks reserves the right to revise this publication and to make changes
from time to time in the content hereof without obligation of Aviat Networks to notify any
person of such revision or changes.
Safety Recommendations
The following safety recommendations must be considered to avoid injuries to persons
and/or damage to the equipment:
1. Installation and Service Personnel: Installation and service must be carried out by
authorized personnel who have the technical training and experience necessary to be
aware of any hazardous operations during installation and service, and of measures to
avoid any danger to themselves, to any other personnel, and to the equipment.
2. Access to the Equipment: Access to the equipment in use must be restricted to service
personnel only.
3. Safety Norms: Recommended safety norms are detailed in the Health and Safety
sections of the Eclipse User Manual.
4. Service Personnel Skill: Service personnel must have received adequate technical
training on telecommunications and in particular on the equipment and capabilities this
addendum refers to.
Trademarks
All trademarks are the property of their respective owners.
260-668241-001 JANUARY 2018 III

CTR PORTAL
IV AVIAT NETWORKS
CTR PORTAL
Aviat NetworksTechnical Support

Service and Technical Support:
For customer service and technical support, contact one of the regional Technical Help
Desks listed below.
Americas Technical Help Desk EMEA Technical Help Desk Asia Pacific Technical Help Desk
Aviat Networks, Inc. Aviat Networks Aviat Networks
San Antonio, TX Blantyre, Glasgow, Scotland Clark Freeport Zone
U.S.A. G72 0FB Philippines 2023
United Kingdom
Phone:+1 210 526 6345 Phone: +1 210 526 6345 Phone: +1 210 526 6345
Toll Free (USA): Fax: Fax: +63 45 599 5196
+1 800 227 8332 +44 16 9871 7204 (English)
Fax:+1 210 526 6315 +33 1 5552 8012 (French)
Email: Email: Email:
CustomerCare.Americas@aviatn [email protected] [email protected]
et.com m m
Global Support Hotline: +1 210 526 6345

Call this phone number for support from anywhere in the world. Aviat Networks' Global
Support Hotline is available 24 hours a day, 7 days a week, providing uninterrupted support
for all our customers.
When you call our Global Support Hotline:
l You will be greeted by an automated response that will ask you for your PIN#.
Request a PIN# here: http://aviatnetworks.com/contact-us/technical-
assistance/pin-request-form/.
l As soon as you enter your PIN#, you will be transferred to our Global Technical
Helpdesk that will assist you with your technical issue.
l If you do not have a PIN# your call will be answered by our Support Assurance
Desk. Your call will be supported and prioritized accordingly.
Or you can contact your local Aviat Networks office. Contact information is available on our
website at: http://www.aviatnetworks.com/services/customer-support/technical-
assistance/
260-668241-001 JANUARY 2018 V

CTR PORTAL
Sales and Sales Support:

For sales information, contact one of the Aviat Networksheadquarters, or find your regional
sales office at: HTTP://WWW.AVIATNETWORKS.COM/.
Corporate Headquarters International Headquarters

California, USA Singapore
Aviat Networks, Inc. Aviat Networks (S) Pte. Ltd.
860 N. McCarthy Blvd., Suite 200 17, Changi Business Park Central 1
Milpitas, CA 95035 Honeywell Building, #04-01
U.S.A. Singapore 486073
Phone: + 1 408 941 7100 Phone: + 65 6496 0900

Fax: + 1 408 941 7110 Fax: + 65 6496 0999>
Toll Free for Sales Inquiries: Sales Inquiries:
+ 1 888 478 9669 +1-321-674-4252
VI AVIAT NETWORKS
CTR PORTAL
Product Compliance Notes

CTR 8540, CTR 8312, CTR 8311, and CTR 8380 have been tested for and meet all applicable
EMC standards. The equipment was tested using screened cable; if any other type of cable is
used, it may violate EMC compliance.
CTR 8540, CTR 8312, CTR 8311, and CTR 8380 are Class A products. In a domestic
environment these products may cause radio interference in which case the user may be
required to take adequate measures. This equipment is intended to be used exclusively in
telecommunications centers.
Regulatory Information for 5.8 GHz Band

ODU 600
The following regulatory information applies to license-free operation on the 5.8 GHz band of
ODU 600.
FCC Notices
l ODU 600, 5.8GHz, must be professionally installed and maintained.
l This equipment has been tested and found to comply with the limits for a Class A
digital device, pursuant to Part 15 of the FCC rules. These limits are designed to
provide reasonable protection against harmful interference when the equipment
is operated in a commercial environment. This equipment generates, uses and
can radiate radio frequency energy and, if not installed and used in accordance
with the instruction manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential environment is
likely to cause harmful interference in which case the user will be required to
correct the interference at their own expense.
l ODU 600, 5.8GHz, is compliant with the relevant parts of FCC CFR47, Part
15.407.
l To ensure compliance with the FCC RF exposure requirements, a minimum
distance of 18 meters must be maintained between the antenna and any persons
whilst the unit is operational. This calculation is based on the maximum
conducted power and maximum antenna gain.
l ODU 600, 5.8GHz, has been certified for use with a parabolic antenna with a
maximum gain of 45.9dBi or a flat panel antenna with a maximum gain of 28dBi.
l The filters and software provided with this product allow for transmission only in
the frequency range 5725 – 5850 MHz to ensure compliance with Part 15.407.
l According to the conducted power limit in FCC CFR 47, Part 15.407, the power for
this device has been limited to 1W (30dBm) at the antenna port.
260-668241-001 JANUARY 2018 VII

CTR PORTAL
l FCC CFR47, Part 15.407 excludes the use of point-to-multipoint systems,

omnidirectional applications and multiple co-located intentional radiators. This
system is only for fixed, point-to-point operation.
International Use of 5.8 GHz

ODU 600 with CTR 8540, CTR 8312, CTR 8311, or CTR 8380, 5.8 GHz, does not employ DFS,
and as such the equipment cannot be deployed within Europe or any country where DFS is a
regulatory requirement for protection of radars.
Networking Devices in Electric Power Substations

For IEEE 1613 compliant products, category 7 Ethernet cables must be used in order to
ensure compliance.
WEEE Directive
In accordance with the WEEE Directive (2012/19/EU), CTR 8540, CTR 8312, CTR 8311, and
CTR 8380 is marked with the following symbol:
This symbol indicates that this equipment should be collected separately for the purposes of
recovery and/or recycling.
For information about collection and recycling of Aviat Networks equipment please contact
your local Aviat Networks sales office. If you purchased your product via a distributor please
contact the distributor for information regarding collection and recovery/recycling.
More information on the WEEE Directive is available at our website:
http://www.aviatnetworks.com/products/compliance/weee/.
(WEEE is the acronym for Waste Electrical and Electronic Equipment)
RoHS Directive
CTR 8540, CTR 8312, CTR 8311, and CTR 8380 meets the requirements of ROHS directive
2011/65/EU.
VIII AVIAT NETWORKS

CTR PORTAL
Declaration of Conformity, Radio Equipment Directive

(RED), 2014/53/EU
Aviat Networks tímto prohlašuje, že tento ODU 600/ODU 600sp with

CTR 8311, CTR 8312, CTR 8380, CTR 8540 je ve shodě se základními
Czech Republic požadavky a dalšími příslušnými ustanoveními směrnice 2014/53/EU.
Undertegnede , Aviat Networks erklærer herved, at følgende udstyr

ODU 600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540
Denmark overholder de væsentlige krav og øvrige relevante krav i direktiv
2014/53/EU.
Hiermit erklärt , Aviat Networks dass sich das Gerät ODU 600/ODU
600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540 in
Germany Austria Switzerland Belgium Übereinstimmung mit den grundlegenden Anforderungen und den
übrigen einschlägigen Bestimmungen der Richtlinie 2014/53/EU
befindet.
Luxembourg Netherlands Liechtenstein
Käesolevaga kinnitab , Aviat Networks seadme ODU 600/ODU 600sp
with CTR 8311, CTR 8312, CTR 8380, CTR 8540 vastavust direktiivi
Estonia 2014/53/EL põhinõuetele ja nimetatud direktiivist tulenevatele teistele
asjakohastele sätetele.
Hereby, Aviat Networks declares that ODU 600/ODU 600sp with CTR
8311, CTR 8312, CTR 8380, CTR 8540 is in compliance with the
United Kingdom Ireland Malta essential requirements and other relevant provisions of Directive
2014/53/EU.
Por medio de la presente Aviat Networks declara que el ODU 600/ODU
600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540 cumple con los
Spain requisitos esenciales y cualesquiera otras disposiciones aplicables o
exigibles de la Directiva 2014/53/UE.
ΜΕ ΤΗΝ ΠΑΡΟΥΣΑ, Aviat Networks ΔΗΛΩΝΕΙ ΟΤΙ ODU 600/ODU
600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540
ΣΥΜΜΟΡΦΩΝΕΤΑΙ ΠΡΟΣ ΤΙΣ ΟΥΣΙΩΔΕΙΣ ΑΠΑΙΤΗΣΕΙΣ ΚΑΙ ΤΙΣ
Greece Cyprus
ΛΟΙΠΕΣ ΣΧΕΤΙΚΕΣ ΔΙΑΤΑΞΕΙΣ ΤΗΣ ΟΔΗΓΙΑΣ 2014/53/ΕE.
Par la présente, Aviat Networks déclare que l'appareil ODU 600/ODU
600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540 est conforme
France Luxembourg Switzerland Belgium aux exigences essentielles et aux autres dispositions pertinentes de la
directive 2014/53/UE.
Con la presente , Aviat Networks dichiara che questo ODU 600/ODU
600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540 è conforme ai
Italy Switzerland requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla
direttiva 2014/53/UE.
Ar šo Aviat Networks deklarē, ka ODU 600/ODU 600sp with CTR 8311,
CTR 8312, CTR 8380, CTR 8540 atbilst Direktīvas 2014/53/ES
Latvia būtiskajām prasībām un citiem ar to saistītajiem noteikumiem,
Šiuo Aviat Networks deklaruoja, kad šis ODU 600/ODU 600sp with CTR
8311, CTR 8312, CTR 8380, CTR 8540 atitinka esminius reikalavimus ir
Lithuania kitas 2014/53/ES Direktyvos nuostatas.
260-668241-001 JANUARY 2018 IX

CTR PORTAL
Hierbij verklaart , Aviat Networks dat het toestel ODU 600/ODU 600sp
with CTR 8311, CTR 8312, CTR 8380, CTR 8540 in overeenstemming is
Netherlands Belgium met de essentiële eisen en de andere relevante bepalingen van richtlijn
2014/53/EU.
Hawnhekk, Aviat Networks, jiddikjara li dan ODU 600/ODU 600sp with
CTR 8311, CTR 8312, CTR 8380, CTR 8540 ikkonforma mal-ħtiġijiet
Malta essenzjali u ma provvedimenti oħrajn relevanti li hemm fid-Dirrettiva
2014/53/UE.
Alulírott, Aviat Networks nyilatkozom, hogy a ODU 600/ODU 600sp with
CTR 8311, CTR 8312, CTR 8380, CTR 8540 megfelel a vonatkozó
Hungary alapvetõ követelményeknek és az 2014/53/EU irányelv egyéb
elõírásainak.
Niniejszym Aviat Networks oświadcza, że ODU 600/ODU 600sp with
CTR 8311, CTR 8312, CTR 8380, CTR 8540 jest zgodny z zasadniczymi
Poland wymogami oraz pozostałymi stosownymi postanowieniami Dyrektywy
2014/53/UE.
Aviat Networks declara que este ODU 600/ODU 600sp with CTR 8311,
CTR 8312, CTR 8380, CTR 8540 LL/STR 600 está conforme com os
Portugal requisitos essenciais e outras disposições da Directiva 2014/53/UE.
Aviat Networks izjavlja, da je ta ODU 600/ODU 600sp with CTR 8311,

CTR 8312, CTR 8380, CTR 8540 v skladu z bistvenimi zahtevami in
Slovenia ostalimi relevantnimi določili direktive 2014/53/EU.
Aviat Networks týmto vyhlasuje, že ODU 600/ODU 600sp with CTR

8311, CTR 8312, CTR 8380, CTR 8540 spĺňa základné požiadavky a
Slovakia všetky príslušné ustanovenia Smernice 2014/53/EÚ.
Aviat Networks vakuuttaa täten että ODU 600/ODU 600sp with CTR
8311, CTR 8312, CTR 8380, CTR 8540 tyyppinen laite on direktiivin
Finland 2014/53/EU oleellisten vaatimusten ja sitä koskevien direktiivin
muiden ehtojen mukainen.
Härmed intygar Aviat Networks att denna ODU 600/ODU 600sp with
CTR 8311, CTR 8312, CTR 8380, CTR 8540 tår I överensstämmelse
Sweden med de väsentliga egenskapskrav och övriga relevanta bestämmelser
som framgår av direktiv 2014/53/EU.
Hér með lýsir Aviat Networks yfir því að ODU 600/ODU 600sp with CTR
8311, CTR 8312, CTR 8380, CTR 8540 er í samræmi við grunnkröfur og
aðrar kröfur, sem gerðar eru í tilskipun 2014/53/EU.
Iceland
Aviat Networks erklærer herved at utstyret ODU 600/ODU 600sp with
CTR 8311, CTR 8312, CTR 8380, CTR 8540 er i samsvar med de
grunnleggende krav og øvrige relevante krav i direktiv 2014/53/EU.
Norway
Noi, Aviat Networks, declarăm pe propria noastră răspundere că
produsul ODU 600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380,
România CTR 8540 este în conformitate cu cerinţele esenţiale şi celelalte
prevederi aplicabile ale Directivei 2014/53/UE.
Full declarations of conformity are available at:

http://aviatnetworks.com/doc/ODU600CTR8311CTR8312.pdf
http://aviatnetworks.com/doc/ODU600CTR8380.pdf
http://aviatnetworks.com/doc/ODU600CTR8540.pdf
http://aviatnetworks.com/doc/ODU600spCTR8311CTR8312.pdf
X AVIAT NETWORKS
CTR PORTAL
http://aviatnetworks.com/doc/ODU600spCTR8380.pdf
http://aviatnetworks.com/doc/ODU600spCTR8540.pdf
Country Availability Matrix

Aviat’s radios are classified under the Radio Equipment Directive (2014/53/EU) as Class 2
products. For details of where the equipment is intended to be used, see the country matrix
below. Aviat Networks intends to market this equipment where a cross (X) is shown.
Band (GHz) L6 U6 07 08 10 11 13 15 18 23 26 28 32 38 42
Austria X X X X X X X X X X X X X X X
Belgium X X X X X X X X X X X X X
Bulgaria X X X X X X X X X X X X X
Cyprus X X X X X X X X X X X X X X
Czech Republic X X X X X X X X X X X
Denmark X X X X X X X X X X X X
Estonia X X X X X X X X X X X X X X X
Finland X X X X X X X X X X X X X X
France X X X X X X X X X X X X X X
Germany X X X X X X X X X X X X X X X
Greece X X X X X X X X
Hungary X X X X X X X X X X X
Iceland X X X X X X X X X X X X X
Ireland X X X X X X X X X X X
Italy X X X X X X X X X X X X X
Latvia X X X X X X X X X X X
Lithuania X X X X X X X X X X X X X X
Luxembourg X X X X X X X X X X X X X
Malta X X X X X X X X X X X X X
Netherlands X X X X X X X X X X X
Norway X X X X X X X X X X X X X
Poland X X X X X X X X X X X X X X
Portugal X X X X X X X X X X X X
Romania X X X X X X X X X X X X X X X
Slovak Republic X X X X X X X X X X X X X
Slovenia X X X X X X X X X X X X X X
Spain X X X X X X X X X X X X
Sweden X X X X X X X X X X X
Switzerland X X X X X X X X X X X X X X
United Kingdom X X X X X X X X X X X X X
260-668241-001 JANUARY 2018 XI

CTR PORTAL
IT SHOULD BE NOTED THAT A LICENSE TO OPERATE THIS EQUIPMENT WILL BE

REQUIRED AND THE RELEVANT REGULATOR MUST BE CONTACTED PRIOR TO
INSTALLATION AND COMMISSIONING.
XII AVIAT NETWORKS

CTR PORTAL
Contents
Copyright & Terms of Use iii

Aviat NetworksTechnical Support v
Product Compliance Notes vii
Regulatory Information for 5.8 GHz Band vii
Networking Devices in Electric Power Substations viii
WEEE Directive viii
RoHS Directive viii
Declaration of Conformity, Radio Equipment Directive (RED), 2014/53/EU ix
Contents xiii
CHAPTER 1. INTRODUCTION TO CTR PORTAL 18

CLI or CTR Portal 19
CTR Portal User Interface 20
Conventions and Terminology 20
Graphic Cues 20
Font Changes 21
Common Terminology 21
CHAPTER 2. NAVIGATION AND MENUS 22

Logging into CTR Portal 23
About the Main Screen 26
Menus 29
CHAPTER 3. SYSTEM STATUS 32

Equipment 33
LEDs in the Equipment Screen 35
Alarms 37
Sensors 39
Event Log 40
Reports 42
Manufacture Details 43
CHAPTER 4. SYSTEM CONFIGURATION 44

System Information 45
Management IP Addresses 47
Date and Time 49
Connected Devices 51
Remote Syslog Targets 52
PoE Configuration 53
Backup Power 54
260-668241-001 JANUARY 2018 XIII

CTR PORTAL
TACACS+ 55
Configuration Management 58
Software Management 59
License Management 61
Admin - Script Loading 63
CHAPTER 5. SWITCHING AND ROUTING CONFIGURATION 64

Port Manager 65
Interface Configuration 67
Link Aggregation 69
Static Routes 71
VLAN 73
VLAN Introduction 73
VLAN Screen 74
Bridge Mode 74
Customer Bridge Mode 75
VLAN Screen: Customer Bridge Mode 75
VLAN by Interface Screen: Customer Bridge Mode 76
Provider Edge Bridge Mode 79
VLAN Screen: Provider Edge Bridge Mode 80
VLAN Interface Screen: Provider Edge Bridge Mode 81
C-VLAN to S-VLAN Mapping Screen 82
Provider Edge Bridge Configuration Procedure 83
Transparent Bridge Mode 85
Quality of Service - Classification 87
Quality of Service - Congestion Control 89
Quality of Service - Policing 91
Quality of Service - Scheduling 94
CHAPTER 6. OSPF 96
OSPF Routers 98
OSPF Router Screen 98
OSPF Areas 99
OSPF Area Screen 99
OSPF Interfaces 100
OSPF Interface Screen 100
CHAPTER 7. RADIO CONFIGURATION 102

Radio Links 103
Setting ATPC 108
FCC Implementation 111
Radio Link Diagnostics 114
Radio Protection 116
Radio Protection Diagnostics 119
CHAPTER 8. NETWORK SYNCHRONIZATION CONFIGURATION122

Network Synchronization - Network Clock 123
XIV AVIAT NETWORKS

CTR PORTAL
Network Synchronization - Network Sync Source 127

Interface Synchronization Configuration 129
CHAPTER 9. TDM MANAGEMENT 132

Pseudowire 133
Tributary Diagnostics 135
CHAPTER 10. STATISTICS 138

Interface Statistics 139
Quality of Service Statistics 140
Radio Link Performance 141
Radio G826 142
Radio Link History 144
ARP Cache 146
MAC Address Table 147
Clear Statistics 148
CHAPTER 11. ALARMS AND EVENTS 150

CTR Device Alarms 151
All interfaces in the layer 1 link aggregation group are down 152
Application Invalid 153
Attached RFU has a high transceiver temperature 153
Attached outdoor unit (RFU) transmit power failure 153
Bandwidth and/or standard settings are invalid 154
Bit error rate (BER) threshold of 10^-6 has been exceeded 154
The carrier-only diagnostic function has been enabled 154
Current configuration is not supported 155
Current Radio Protection Configuration Not Supported 155
Configuration has been loaded from a source that is not the startup configuration file 155
Diagnostic function is enabled for the specified E1/T1 156
Ethernet Port Link down 157
Factory Mute Enabled 157
Hardware has failed 157
The IF loopback diagnostic function has been enabled 159
Link status propagation active 159
Loss of Signal 159
MAC Address Conflict Detected on LILA Group 160
Main power supply failure 160
Manufacturing information is invalid 160
Maximum modulation is invalid 161
Module is missing 161
Module is not supported 162
Modulation is invalid 162
The modulation lock diagnostic function has been enabled 163
One or more interfaces assigned to the L1LA aggregation group are down 163
Plugin temperature has exceeded operational limits 163
Plug-in has failed to supply power to a POE port 164
260-668241-001 JANUARY 2018 XV

CTR PORTAL
Possible main power supply failure 164

The plugin-online lock diagnostic function has been enabled 165
Pseudowire Jitter Buffer Overrun 165
Pseudowire Malformed Packets Received 166
Pseudowire Missed Connection 166
Pseudowire Packets Lost 166
Pseudowire Packets Received Too Late 167
Network Synchronization functionality has one or more diagnostic features enabled 167
Received Alarm Indication Signal 167
Receive path has been lost 168
Receiver frequency setting is invalid 168
The RFU power supply diagnostic function has been enabled 169
RFU not detected 169
The rx-source lock diagnostic function has been enabled 169
Radio traffic path has been lost in one or both directions 170
Secondary Power Failure 170
Software synchronization with SD card failed 171
Synchronization clock is not locked to source(s) with highest priority 171
SyncE enabled on non SyncE capable SFP Module 172
System Clock is in holdover 172
The system clock setting is invalid 173
System cooling degraded 173
System cooling failed 173
Transmit path has been lost 174
Transmit power is invalid 174
Transmitter frequency setting is invalid 175
The transmitter lock diagnostic function has been enabled 175
The transmitter mute diagnostic function has been enabled 175
Valid SD card missing 176
XPD Output on BNC Diagnostic Enabled for this radio 176
XPIC settings are invalid 177
CTR Device Events 178
The active software version has changed 178
The active software does not match the software on the SD card. Software sync from the
SD card started 178
Autonegotiation procedure failed 178
Configuration download operation has failed 178
Configuration download operation was successful 179
Configuration has been loaded successfully from the startup configuration file 179
Configuration revert operation has failed 179
Configuration save operation has failed 179
Configuration save operation was successful 179
Connectivity with an SNTP server has been established 180
Device operating abnormally due to [text] 180
An ECFM defect has occurred 180
An error has occurred during software activation: [text] 180
An error has occurred during software loading: [text] 180
XVI AVIAT NETWORKS

CTR PORTAL
An error has occurred during software rollback: [text] 180

Failed to write license to SD card: [text] 181
Helpdesk file generation failed 181
Helpdesk file generation was successful 181
IDQ optimization started manually on radio interface 181
Local configuration file(s) have been updated from the SD card 181
Management VLAN was changed from [value] to [value] 182
A neighbouring device has been lost on port [text] 182
New neighbouring device discovered on port [text] 182
No response from the [text] SNTP server 182
Protection plug-in online switch from [text] to [text] due to [text] 182
Protection plugin switch blocked due to [text] 183
Protection transmitter switch from [text] to [text] due to [text] 183
Protection transmitter switch blocked due to [text]. 183
Radio set to maximum power for over [value] minutes 183
Radio set to maximum power for over [value] minutes. Cooldown reducing power by
[value].[value]dBm 183
Rx modulation was changed from [text] to [text] 184
The software has reverted to the inactive software 184
SFP module present but not configured: [text] 184
SFP module was extracted: [text] 184
SFP module was inserted: [text] 184
Software load has started 185
The system date and time has been updated via SNTP 185
System reset event occurred: [text]. 185
Tx modulation was changed from [text] to [text] 185
User has initiated a hard reset 185
User has initiated a soft reset 185
Watchdog reset occurred 186
A Y.1731 defect has occurred 186
MPLS traffic-engineering tunnel up 186
MPLS traffic-engineering tunnel down 186
MPLS traffic-engineering tunnel rerouted 186
MPLS pseudowire (L2VPN) up 186
MPLS pseudowire (L2VPN) down 187
LDP neighbour up 187
LDP neighbour down 187
MPLS LSP up 187
MPLS LSP down 187
BGP peer established 187
BGP peer state backwards transition occurred 188
APPENDIX A. GLOSSARY 190

Index 192
260-668241-001 JANUARY 2018 XVII

CONTENTS CHAPTER 1
Chapter 1. Introduction to CTR Portal

ProVision™ CTR Portal, referred to as CTR Portal is your easy to use interface for updating
and reviewing CTR 8540 and CTR 8300 devices. Installers, engineers, and administrators
can manage many functions with this web-enabled manager.
The CTR Portal enables:
●Configuration and Monitoring— Platform configuration, with views of current configuration,
system data, interfaces, and more.
●Diagnostics—Interface testing and the capture and analysis of traffic.
●Maintenance—Management of software packages and licenses.
●Monitoring events—Filter and view system log and event messages.
●Monitoring alarms—Monitor and diagnose alarm alerts for hardware or network
connections.
N O TE: CTR Por tal s uppor ts CTR 8540 and CTR 8300 devic es . The CTR
8300 family c ur r ently c ompr is es the CTR 8312 (2 RF modules ) and CTR
8311 (1 RF module).
About CTR 8500 and CTR 8300

CTR 8500 and CTR 8300 provide in one compact carrier-class platform fully integrated
microwave link, L2 switch, and L3 router functions.
l The converged operation ensures interworking between microwave and IP
network links is optimized.
l Operation is uplink agnostic with options for IF or Ethernet connected microwave,
copper, or fiber media.
Microwave applications support scalable radio transport for conventional microwave (5-42
GHz) and E-band microwave (70-80 GHz).
l For split-mount installations, IF connectivity is provided to Aviat’s ODU 600, ODU
600sp, and ODU 300hp.
l For all-indoor installations, IF connectivity is provided to Aviat's IRU 600.
l For all-outdoor installations, PoE connectivity is provided by CTR 8500 to Aviat's
family of WTM 3000 radios, or to any other external packet radio.
l When connected to an Aviat radio the features include modulations to 1024 QAM,
adaptive coding and modulation (ACM), and extensive protection and co-path
configurations.
N O TE: Some c apabilities ar e r es tr ic ted at SW r eleas e 3. 4. Contac t Aviat
Netw or ks for r ollout infor mation.
AVIAT NETWORKS JANUARY 2018 18

CHAPTER 1 CONTENTS
CLI or CTR Portal

CTR 8500 and CTR 8300 can be configured using CLI, or its menu-driven Web GUI, CTR
Portal.
l CLI is accessed using Telnet or SSH protocols from a terminal emulation
program such as the freeware 'PuTTY' or 'xterm'. See the CTR CLI Reference
Manual.
l CTR Portal is accessed through a web browser by entering the IP Address of the
device in the browser address bar. Its functionality is documented here.
Unless you are experienced in the use of CLI, CTR Portal will provide an easier, more user-
friendly configuration experience.
At the CTR 8300 3.4 SW release :
l CLI supports comprehensive configuration, and must be used to:
o Change or add user names and passwords
o Revert to factory defaults
o Configure EOAM (Link and Service)
o Configure ERPS
o Configure IP/MPLS
l CTR Portal should be used to:
o Load SW, license, and configuration files.
o Configure a radio/link
o Set plug-in slots
o Configure switch-port settings
o Configure VLANs
o Set router ports
o Set bridge mode
o Configure QoS
o Set IP addresses
o Configure OSPF (basic)
o Set date and time
o View/access alarms, diagnostics, performance, events, statistics
o Configure L1LA
o Configure pseudowires (SAToP)
o Configure Synchronous Ethernet
19 JANUARY 2018 AVIAT NETWORKS

CONTENTS CHAPTER 1
CTR Portal User Interface

The CTR Portal interface is compatible with the following web browsers:
l Internet Explorer 10.0 or later
l Mozilla Firefox 25.0 or later
l Google Chrome 30.0 or later
N O TE: To us e CTR Por tal, Javas c r ipt mus t be enabled on all br ow s er
types .
Figure 1. User Interface Sample
N O TE: Some s c r eens pr ovide ar eas to enter data; other s only dis play
s ys tem data for r eview .
Conventions and Terminology

This document uses the following conventions and terminology.
Graphic Cues
The following items have graphic cues to identify important supporting information.
N O TE: A N o te item identifies additional infor mation about a pr oc edur e or
func tion.
CAUTION: A caution item identifies important information pertaining to actions that may
cause damage to equipment, loss of data, or corruption of files.
WARNING: A warning item identifies a serious physical danger or major possible

problem.

CHAPTER 1 CONTENTS
Font Changes
Bold font is used for the names of on-screen elements such as; fields, buttons, and drop-
down selection lists, keywords, commands and for keys on the keyboard.
Courier font in blue text is used to indicate commands that the user needs to type in.
WTM4100# show radio-carrier status Carrier1/1
Any responses or report output from a command is shown as brown text and indented.
radio-carrier status Carrier1/1
oper-status up
Italic font is used to emphasize words and phrases, to introduce new terms, and for the
titles of printed publications.
Common Terminology
Click or Select: Point the mouse pointer at the item you want to select, then quickly press and
release the left mouse button.
Right-Click: Point the mouse pointer at the item you want to select, then quickly press and
release the right mouse button.

NAVIGATION AND MENUS CHAPTER 2
Chapter 2. Navigation and Menus

This section describes how to navigate in CTR Portal, and provides a list of the interface
menus. Topics include:
l Logging into CTR Portal on page 23
l About the Main Screen on page 26
l Menus on page 29

CHAPTER 2 NAVIGATION AND MENUS
Logging into CTR Portal

Logging into CTR Portal for a CTR device requires knowledge of the specific IP address for
the device, and your own user name and password.
Login Prerequisites
l Before standard users log in, an Administrator must set up basic settings using
CLI. This includes provisioning of an IP address, user-names and passwords,
VLAN configuration, etc. Refer to the CTR 8500/8300 Getting Started Guide.
l Default access is provided as out-of-band (OOB) management on VLAN 2, on
switch-port 1, using a static IP address of 192.168.1.1/255.255.255.0.
l CTR Portal requires a minimum display resolution of 1024 x 768.
l The PC setup requirements (LAN-compatible IP address and RJ-45 cable
connected) must be in place. See the detailed instructions below.
Login Notes
l The default user name and password are:
l user name - root
l password - admin123
l Users have security settings applied to their profile. Screens or menu items may
be hidden due to security settings for a user, or a "Not Authorized" page will
display. The default admin123 access provides full administrative rights.
l Although more than one user can log into a device at the same time, Aviat
Networks recommends that only one user does so to avoid potential for
configuration conflict.
PC Setup
Before you login to CTR Portal:
l Your PC must be set to have a LAN-compatible IP address (i.e., your PC must
operate as a device on the same LAN as the CTR)
l An RJ-45 (Cat5) cable must be connected from your PC Local Area Connection
port to the CTR management port, which is default switch-port 1.
Setting a compatible IP address (Windows 7):

l Click on the Internet Access icon in the System Tray of your PC screen, then
click on Open Network and Sharing Centerr. Or from the Control Panel select
Network and Sharing Center.
l Under Access Type Internet select Local Area Connection, which brings up Local
Area Connection Status.
l Select Properties.

l Highlight Internet Protocol Version 4 (TCP/IPv4) and click Properties. The

Internet Protocol (TCP/IP) Properties window is displayed.
l Proceed to Changing TCP/IP Properties, as in the example below. In this
example, the IP address of the CTR is 192.168.1.1.
N O TE: Bef ore m akin g an y ch an g es to th ese settin g s, record an d retain th e
ex istin g settin g s, w h ich m ay p ertain to you r com p an y LAN .
o Select Use the following IP address, and in the IP address field enter a LAN
compatible IP address for the CTR. For example, with a CTR IP address of
92.168.1.1, you can enter 192.168.1.2.
o Set a Subnet mask of 25.225.225.0 (same as the CTR).
o Only set a default gateway where other CTRs on the same LAN are to be
viewed via this connection.
o To save these changes and close the screen, click OK.
Login Procedure
l Connect your PC Local Area Connection port to the CTR management port
(default switch-port 1).
l Launch a web browser on your computer. Use one of the following web
browsers: Internet Explorer, Firefox, or Google Chrome.
l Enter the Switch IP address in the address bar of the web page. For example, if
the IP address of the Switch interface is 192.168.1.1, then enter
http://192.168.1.1 in the address bar.
N O TE: If HTTPS is enabled in the CL I, you c an als o enter an HTTPS
addr es s , as https ://<r adio ip addr es s >. You w ill be pr ompted to ac c ept a
s ec ur ity exc eption by the br ow s er .

l The Login page appears.
l To login, enter your user name and password from your CTR CLI user profile.
Then, click Login.
l The CTR Portal home page for the device will display, opening to the Equipment
page.

About the Main Screen

The main view of CTR Portal displays in your web browser as shown.
N O TE: Data fr om the devic e is updated w ithin 5 s ec ond inter vals under
optimal w eb c onnec tion c onditions .
Figure 2. Main Screen
The left sidebar contains the function navigation menu. Click on items and sub-items to view
and configure data for the specified device.
The header and footer include the following information and action buttons.
Table 1. Main Screen Functions
Item Details
Header
Alarms Displays any current alarms. Click on Status > Alarms in the menu to
see more.
Activities
Notes user activity and waiting unsaved changes.

Save
Click to save all changes made during this web session.

CAUTION: If not saved and the CTR is rebooted, all
configuration since the last-saved time will be lost.

Item Details
Revert Timer
Enter the Revert Timer value in seconds, and enable/disable it using

the button. The value range is 300 to 3600 seconds. The Revert Timer
action is as follows:
It is default set to Disabled.
When set and allowed to time-out it will revert to the previously
saved configuration, at which point the timer will be returned to
Disabled.
When set during a configuration process (and not timed-out) it will
re-start the countdown each time the Apply tab is clicked.
The timer can be disabled by selecting Disabled at any time up to
the time-out time. This action applies where it is clear there is no
need to revert to the previously saved configuration.
A typical application is where the configuration of remote-end
terminals has the potential to remove communication with the
remote terminal(s). With the revert timer engaged it means you
will be able to recover communications in such an event (revert to
the previously saved configuration).
User
Name/Logout
Notes name of logged in user. Also has Logout: click to log out from
this web session.
Help
Click and select a Help viewing option:

Help Contents = opens full help set
Contextual Help = opens context-sensitive help for the CTR screen
you are viewing
About = Release and licensing details.
CTR Help opens in a pop-up window. Help provides context sensitive
pop-ups of this CTR Portal Manual. Ensure pop-ups are allowed on
your browser to view the Help.
Sidebar Menu

Item Details
View/Hide Menu Click on this icon to open and close the sidebar menu view:
= Hide the sidebar menu
= Open the sidebar menu
Footer
Device IP
The IP number and name for this device.

Device Time
Length of time the device has been in operation since it was last
powered on or rebooted.
Date and Time Date and time settings for this device. Note that unless set correctly
using the System Configuration > Data & Time page, this may vary
from your local time.

Menus
This table lists the menus available using the following links:
Status Status overviews for:

o Equipment on page 33
o Alarms on page 37
o Sensors on page 39
o Event Log on page 40
o Reports on page 42
o Manufacture Details on page 43
System System specific configuration and system specific modules:
o System Information on page 45
o Management IP Address - redirects to VLAN, where this value
is set, see VLAN on page 73
o Date and Time on page 49
o Connected Devices on page 51
o PoE Configuration
o Backup Power on page 54
o Configuration Management on page 58
o Software Management on page 59
o License Management on page 61
o Admin - Script Loading on page 63
Switching & Ethernet related features and modules:
Routing o Port Manager on page 65
Configuration
o Link Aggregation on page 69
o VLAN on page 73
o Quality of Service - Classification on page 87
o Quality of Service - Policing on page 91
o Quality of Service - Scheduling on page 94

Radio Con- Radio related features:

figuration o Radio Links on page 103
o Radio Protection on page 116
o Radio Link Diagnostics on page 114
o Radio Protection Diagnostics on page 119
Network Sync o Network Synchronization - Network Clock on page 123

Configuration
o Network Synchronization - Network Sync Source on page 127
TDM Man- TDM related features:

agement o Pseudowire on page 133
o Tributary Diagnostics on page 135
Statistics This menu has sub-links for statistics of several modules and features:
o Interface Statistics on page 139
o Quality of Service Statistics on page 140
o Ethernet OAM Statistics on page 1
o Radio Link Performance on page 141
o Radio Link History on page 144
o Radio Link History on page 144
o Radio G826 on page 142
o ARP Cache on page 146
o MAC Address Table on page 147
o Clear Statistics on page 148

SYSTEM STATUS CHAPTER 3
Chapter 3. System Status

From the System Status items in the Menu, view system status for:
l Equipment on page 33
l Alarms on page 37
l Event Log on page 40
l Sensors on page 39
l Reports on page 42
l Manufacture Details on page 43

CHAPTER 3 SYSTEM STATUS
Equipment
This screen displays an overview of the device chassis with the current status of ports,
slots, LEDs, plug-ins, and any associated alarms. The Equipment view is updated within 5
second intervals under optimal web connection conditions.
The Equipment view displays accurate representations of managed devices. There are two
view options:
l Default - Standard view of device chassis.
l Remote Devices - Displays connected devices for each port. Connected device
information is populated from LLDP or entered by the user. You can right-click on
a remote device and view its information, or open the remote device in another
CTR Portal view.
Figure 3. Status - Equipment View for CTR 8540 - Default View
Figure 4. Status - Equipment View for CTR 8540 - Remote Devices

Figure 5. Status - Equipment for CTR 8300
Figure 6. Status - Equipment for CTR 8380
Procedure
l Go to Status - Equipment. Use the following functions to view equipment details.
l Alarm tags display events and alarms for the device; hover over an icon to view the
pop-up information.
l RFU status displays whether an RFU is detected on a radio port, and the RFU's
current Tx/Rx status.
l Click on a device area or plug-in to view a menu of functions specific to this area or
plug-in.
l Only licensed front panel ports are displayed. Unlicensed ports are grayed-out.
l The chassis view in the Equipment screen notes plug-ins. The Equipment screen
notes if plug-ins have changed from a previous configuration, showing the
Expected and Found plug-in. You can configure a slot to accept a detected plug-in.
Click on the slot in the Equipment screen and select Set slot to detected plug-in
type . You can also Set all slots to detected plug-in types.

Figure 7. Status - Equipment with Unexpected Plug-In
l To view information for a remote device, do the following:

o Select Remote to display the Remote view. Remote device names display by
their connected ports.
o Click on one of the indicated Remote devices and select View Info.
o The information for the remote device displays:
Click Close when you are done.

l To save a configuration, click Save in the toolbar.
LEDs in the Equipment Screen

The following equipment view items have one or more LEDs indicating status:
l ON
l OK
l Main board (logo)

l Ports 1 – 8
l SFP Ports 9 - 12
l Fan
The OK LED indicates:

l Green – Normal operation
l Amber flashing – Major alarm
l Red – Critical alarm
The FAN LED indicates:

l Green – Normal operation
l Amber – Major alarm (typically one fan of the four in alarm)
l Red – Critical alarm (two or more fans in alarm)
To view the relevant alarm(s) for an amber or red LED, hover over the corresponding alarm
icon.
Each active RJ-45 port displays a green connection LED and an orange Activity LED. The
orange Activity LED indicates a 100Mb/10Mb port when it is lit. When it is off, this indicates
that the port is 1GB.
CTR Portal software updates LED states every 5 seconds. When the CTR Portal device is
started up, or new items are plugged in, the LED color takes a moment to stabilize while the
software applies the correct state.

Alarms
This screen displays all alarms for the device chassis and plug-ins.
Procedure
l Go to Status - Alarms.
l Use Expand All to expand the screen to show all alarm events, active and non-
active.
l Use Collapse All to collapse the alarms listing to folder-level: main board, plug-
ins, protection.
l Click the Show All Alarms button to view all alarms. To exit this view, click the
Show Only Active Alarms button.
l Use Clear All to reset the capture of alarm events during the current CTR Portal
session.
o An alarm raised during the current session will have a Clear All up/down arrow
icon.
o Clicking Clear All will remove any current arrow icons.
o Arrow icons will display for any alarms raised subsequent to Clear All during
your CTR Portal session.
l Alarm severity is indicated by the color tag on each alarm:
o Green: No alarm
o Red: Critical
o Orange: Major
o Yellow: Minor
o Blue: Warning
Figure 8. Status - Active Alarms, Default View

Figure 9. Status - Active Alarms, View All
For alarm definitions, see CTR Device Alarms on page 151.

Sensors
This screen provides a view of operating thresholds and values for the chassis and plug-ins.
Values are updated at 10 second intervals.
Procedure
l Go to Status - Sensors. The Sensors values display: scroll down the screen to
view all values.
Figure 10. Sensors Screen
Table 2. Sensor Values
Field Name Description

Sensor Name of sensor.
Value Value reported by sensor, based on device type and value.
Critical High Maximum range for an operational threshold, such as temperature.
Critical Low Minimum range for an operational threshold, such as temperature.

Event Log
This screen displays events on a FIFO basis. You can:
l Filter event results by type, date/time, location, entity, and text
l Turn automatic event updating on/off by selecting the Update check box
Results are displayed at 100 to a page: at the bottom of the screen, you can navigate to
additional pages by clicking on the page numbers.
Procedure
l Go to Status - Event Log. The most recent events are shown at the top of the
screen.
l To filter on an option, click on the required option column header: Type,
Location, or Entity.
l Use the Search field to filter events by keyword or value.
l Use the Date/Time field to search on/around a specific time.
For alarm definitions see CTR Device Alarms on page 151

For Informational event definitions see CTR Device Events on page 178.
Figure 11. Status - Event Log

Table 3. Event Log Values
Column Name Description

Type Type of event, including:
Alert – Problem with system function, may include an alarm.
Critical – Serious problem with system function.
Error – Problem with system function.
Info – Informational event, does not impact system function.
Notice – Minor event or change, does not impact system function.
Select a specific event type using the drop-down menu in the header.
Location System location of the event, including:
AOS
Alarm Manager
Chassis Manager
System Log
Select a specific system location using the drop-down menu in the header.
Entity Area of the device experiencing the event. Select a specific area using the
drop-down menu in the header.
Details Detailed description of the event. You can use the Search function in
the header to search for specific event details by name, MIB, or
more.
Date/Time Date and time of the event. Click on the calendar icon in the header
to select a specific date/time range.

Reports
The Reports screen is accessed under Status. It enables generation of a Help Desk Report,
which can be used for system maintenance and support.
l It captures information on the device environment and configuration.
l The report is used to capture issues for analysis by the Aviat Networks Help Desk.
N O TE: When you have s et up CTR Por tal for the fir s t time, alw ays r un and
s ave this Repor t. It is a valuable r efer enc e that c aptur es your initial
s etup.
N O TE: G ues t us er s c annot ac c es s this func tion.
Procedure
l Go to Status - Reports.
l Click the Generate button to create a report. To save the report for archiving or
emailing, click the Download button.
Figure 12. Status - Reports

Manufacture Details
This screen provides manufacturing information for the CTR chassis and plug-ins. Data
includes serial numbers, names, time in service, and manufacturing name and date.
Procedure
l Click Status > Manufacture Details.
l The manufacturing values for the device and the plug-ins display.
Figure 13. Status - Manufacture Details

SYSTEM CONFIGURATION CHAPTER 4
Chapter 4. System Configuration

The System screens include the following:
l System Information on page 45
l Management IP Addresses on page 47
l Date and Time on page 49
l Connected Devices on page 51
l Remote Syslog Targets on page 52
l PoE Configuration
l Backup Power on page 54
l TACACS+ on page 55
l Admin Configuration
o Configuration Management on page 58
o Software Management on page 59
o License Management on page 61
o Admin - Script Loading on page 63

CHAPTER 4 SYSTEM CONFIGURATION
System Information
This screen displays essential system hardware and software values, and fields for
entering a Contact and Location.
See Manufacture Details on page 43 for plug-in information.
Procedure
l Click System Configuration > System Information.
l To configure the values, enter or select the desired values, then click Apply. To
clear any entered values before applying, click Clear. Values are defined below.
l To save changes, click the Save icon.

Figure 14. System Information
Table 4. System Information Values

Hardware Version Hardware version number.
Software Version Software version number. Click on the version to go to the
Software management screen.
Firmware Version Firmware version number.
Node Name Enter the name of the device node, up to 15 characters.
Switch MAC The switch MAC number for the device.

Contact Enter the contact person details for this device, up to 255
characters, and click Apply.
Location Enter the name of the device's location, up to 255 characters,
and click Apply.

Management IP Addresses
You can view and set the management IP address(es) for CTR.
l Interfaces assigned a management address can be used to access the CTR for
management purposes.
Management addresses are shown for VLANs assigned a management address and for
interfaces configured as router ports.
l The default management addresses are VLAN based with VLAN 1 assigned an
(invalid) address of 0.0.0.o, and VLAN 2 an address of 192.168.1.1/24.
o An IP address changed in this screen will be reflected in the VLAN screen and
vice-versa.
l Router ports are configured in the Interfaces screen. See Interface Configuration
on page 67.
o An IP address changed in this screen will be reflected in the Interface
Configuration screen and vice-versa.
Procedure
l Click System Configuration > Management IP Address.
l Enable the Revert Timer.
l Reset the IP address and subnet mask, then click Apply. To clear an entered
value before applying, select it and click Clear. Values are defined below.

l Disable the Revert Timer.
Figure 15. Connected Devices

Table 5. Management IP Address Configuration

Status Green icon - line protocol is up / connected
Red icon - line protocol is down. For a RAC port it can mean radio receive
path is lost.
Blank icon - port is shutdown / disabled
Interface Interface ID
IP Address Enter/change the management address.
Subnet mask Enter the subnet mask.
Broadcast The broadcast address is automatically identified.
Address

Date and Time

This screen provides the ability to view and update current date and time and to set the clock
source for Local or SNTP.
Procedure
l Click System Configuration > Date and Time .
l Check that the main System Date and Time values are correct.
l To configure these values, enter or select the desired values in Configure Date
and Time , then click Apply. To clear an entered value before applying, select it
and click Clear. Values are defined below.

Figure 16. Date and Time Configuration
Table 6. Date and Time Values

Clock Time Source Local or SNTP. If you select SNTP, an SNTP configuration table
appears with prompts for:
Server address. A maximum two servers can be entered, with
one set as the primary.
SNTP version 3 or 4.
Date Select the date (day, month, year) using the drop-down
menus or the calendar.

Time Enter the time (hour, minutes, seconds).

Timezone Select the international time zone using the drop-down
menu.

Connected Devices
This screen enables you to review, add, and delete connected devices. A connected device is
a device that is connected to the CTR 8540 or 8300 managed by this CTR Portal instance.
Procedure
l Click System Configuration > Connected Devices.
l To add a new device, click Add. A new data row displays.
l To configure connected devices values, enter or select the desired values, then
click Apply. To clear an entered value before applying, select it and click Clear.
You can delete a device by selecting its row and clicking Remove . Values are
defined below.

Figure 17. Connected Devices
Table 7. Connected Device Values

Local Port Note the local port where the remote device connects to this CTR device.
Address Type Select the address type using the drop-down menu: Unknown, IPv4.
Address Enter the specific device address.
Description Add a text description of this device.

Remote Syslog Targets

This screen enables you to review, add, and delete remote syslog targets to capture Event
Log events.
N O TE: O nly IPv4 s ys log tar gets c an be added.
Procedure
l Click System Configuration > Remote Log.
l To add a new target, click Add. A new data row displays.
l To configure a remote syslog, enter or select the desired values, then click
Apply. To clear an entered value before applying, select it and click Clear. You
can delete a device by selecting its row and clicking Remove . Values are defined
below.

Figure 18. Remote Syslog Targets
Table 8. Remote Syslog Targets

Address Enter the specific device address.
Port Enter the port ID.
Protocol Select the protocol using the drop-down menu: TCP or UDP.
Security Check this to enable security for the target.

PoE Configuration
Access to the PoE Configuration screen is provided under System Configuration. It supports
PoE configuration of the PoE plug-in Ethernet interface.
To enable the required PoE interface(s) go to the Port Manager screen. See Port Manager
on page 65.
N O TE: This s c r een is only available for CTR 8540 devic es .
Procedure
l Click System Configuration > PoE Configuration to access the PoE Configuration
screen.
l To configure these values, enter or select the desired values, then click Apply.
Values are defined below.

Figure 19. PoE Configuration
Table 9. PoE Values

Select Choose the required interface.
Interface Name the interface (optional)
Power Mode Select the Power Mode. Options are:
Auto- Supplies power to the interface when a valid device is connected.
Never - Data interface only. Power is never supplied to the interface.
Max Milliwatts Set/limit the power maximum in milliwatts. Do not exceed a value of
70,000 milliwatts (70W).
Status Power status of the port.
Class Class of power supported by the plugged-in device.

Backup Power
Access to the Backup Power screen is provided under System Configuration. It supports
configuration of the plug-in power card option.
Procedure
l Click System Configuration > Backup Power to access the Backup Power screen.
To clear values before applying, select an item and click Clear. Values are
defined below.
Table 10. Backup Power Values

Slot Slot that contains the Power plug-in. Only slot 1 is permitted for this
card.
Power Expec- Specify if the backup plug in card is Expected or Not Expected to
ted deliver power.
Voltage Incoming voltage supplied to the plug in card. Nominally 48 Vdc.
Current Current through the plug in card (load current plus power consumed
by the card).
Temperature Temperature of the plug in card.

TACACS+
TACACS+ (Terminal Access Controller Access-Control System) can be used to perform
remote Authentication, Authorisation and Accounting (AAA) of a user, where the users login
credentials are stored on a remote TACACS+ server. This screen enables users to
configure and register the TACACS+ servers.
Procedure
l Click System > Admin > TACACS+ to access the TACACS+ screen.
l To configure the TACACS+ server(s), enter or select the desired values, then
click Apply. To clear any entered values before applying, click Clear. Values are
defined below.

Figure 20. TACACS+
Table 11. TACACS+ Values

TACACS+ (Global)

Authentication Mode The Authentication Mode controls whether TACACS+

or local authentication procedures are to be used for
user authentication processing. The options are:
Enabled – Authentication of the user will be
attempted by interrogating the registered TACACS+
servers. If a server cannot be contacted, the login
authentication will fail.
Enable and Fallback to Local – Authentication of the
user will be performed by interrogating the
registered TACACS+ servers. If a TACACS+ server
cannot be contacted then local authentication of the
user will be attempted.
Disabled – Authentication of the user will be
attempted by local authentication procedures.
TACACS+ will not be used to authenticate the user.
Enable Accounting Select the check box to enable logging of login, logout,
and CLI command execution events at the active
registered TACACS+ server. If the check is removed, no
logging of events will occur.
Timeout Enter the maximum time period in seconds for which
an attempt to contact a TACACS+ server will be made.
If contact with the server is not established within this
time period, it is assumed the server is not
contactable. The value range is 1 – 10 seconds. But, a
value of 3s or less is recommended in order to reduce
delays introduced to the login process if servers are
uncontactable.
If a server timeout occurs in this way, another server
may be tried if more than one servers are registered. It
may fallback to local authentication procedures if
Authentication Mode is set to Enable and Fallback to
Local.
TACACS+
This section allows for up to three TACACS+ servers to be registered. The inform-
ation here has to match the parameters of the available TACACS+ servers.
# The number in this column (1,2 or 3) indicates
the priority of the server, with 1 being the highest
priority and 3 the lowest. The server with the
highest priority will always be contacted first. The
GUI will create server entries in priority order.
Address The IP address of the server.
Port The port upon which the server will listen for
TACACS+ protocol messages. The default port number
is 49.

Key The shared key which is used to create secure

encrypted communication with the TACACS+ server.
This key must match the key configured in the
TACACS+ server. The key can contain any printable
ASCII character except whitespace or double-quotes.

Configuration Management
This screen provides a configuration backup mechanism by saving a configuration to your
PC for subsequent restoration - if and when required.
N O TE: The Rever t Timer mus t be s et (is pr ompted) befor e a Res tor e is
allow ed to pr oc eed.
Procedure
l Click System Configuration > Admin > Configuration Management.
l To download a configuration backup, click Download. Save the backup file in a
secure location.
l To restore the configuration, first set the Revert Timer for a minimum 300
seconds (5 minutes). If the revert timer is not manually disabled before time-
out, the previous (saved) configuration will be loaded. For revert-timer
operation see About the Main Screen on page 26.
Figure 21. Configuration Management
Table 12. Configuration Management Values
Item Value
Config Backup Click Download to save a backup of the configuration to
the Downloads folder on your PC.
Config Restore Restore From - choose Local File or Configuration
Repository
Config File - Browse to select the required Config File on
your PC
Restore - Click to Restore the configuration from the
selected file. This action is blocked until the revert timer has
been set.

Software Management
This screen enables users to upgrade system software and, if required, to rollback to a
previous version of software.
Procedure
l Click System > Admin > Software Management to access the Software
Management screen.
Values are defined below.

Figure 22. Software Management
Table 13. Software Management Values

Software Status
Active Version Version number of the active software.
Inactive Version Version number of previously installed software that is
now inactive, or the version number of software that
has been transferred and awaiting activation.
Rollback Rollback to the previous software version (the
inactive version).
Software Upgrade
Status Status of the software install.

Overall Progress Progress of software install.

Local File or Software Repository Select the location of the software pack - a local or
File remote file.
Software Pack For a Local File selection, browse to the location of the
software pack.
For a Remote File, enter its URI.
Load Control Select the load and activate action. Options are:
Transfer. A Transfer will update (replace) the
Inactive Version of software with the transferred
version.
Activate. Use to activate the transferred version;
currently the Inactive Version.
Transfer and Activate. Use to transfer and activate
the software pack. Unless Schedule Activation has
been selected, activation will commence as soon as
the transfer has been completed.
Schedule Activation Set the date and time for activation. Selection
applies to Transfer and Activate, and to Activate.
Start, Abort Click these buttons to select an action for the software
upgrade:
Start - Starts the software upgrade using the option
selected in Load Control.
Abort - Aborts a software installation. Abort can be
performed at any time up to 100% of Overall
Progress. Thereafter, Rollback must be used to
revert to the previous build.

License Management
This screen enables users to view and update the licensed capability of the device.
License details are available from your Aviat Networks representative.
l Licenses are specific to the serial number of the SD card installed into the CTR.
l A new license (.lic file type) from Aviat is loaded onto your PC, from which point it
is brought into the license management screen for uploading to the CTR.
l Once a license is uploaded it is committed. A license cannot be unloaded from a
CTR.
Procedure
l Click System Configuration > Admin > License Management.
l Drag and drop the new license file from your PC into the License Management
screen, or select it using the Choose Files option.
l Click Upload to upload to the CTR.
l Confirm that the newly uploaded license is listed under Licensed Features.

Figure 23. License Management
Table 14. License Management Values
Item Value
Serial Number The license serial number of the device - as defined by the
SD card.
Licensed Features Installed capacity and feature licenses.

Item Value
Unlicensed Features Available features - licensed features that are available
from Aviat Networks.
Upload License Drag-and-drop or choose new licenses into this section, then
click Upload.

Admin - Script Loading

This screen enables users to load CLI configuration scripts directly to the CTR.
Prerequisites
The Revert Timer should always be enabled for this action. Click to set and enable in the
tool-bar (top of screen).
The selected .txt script must have enabled entered in the 1st line.
The .txt script must use ANSI text encoding (ANSI encoding is the default for a .txt file).
Procedure
l Click System > Admin > Script Loading to access the Script Loading screen.
l To select your .txt script file, click Choose File . Locate and open your file.
l Copy and paste, or drag and drop, the .txt file into the Script Loading area.
l Enable the Revert Timer.
l Click Upload & Execute. The script is loaded and executed.
l If CTR operation is as required/expected, click Disable in the Revert Timer.
Unless disabled before time-out, CTR operation will revert to its previous
config.

SWITCHING AND ROUTING CONFIGURATION CHAPTER 5
Chapter 5. Switching and Routing Configuration

This section describes the switching and routing configuration functions, including Ethernet
configuration.
Topics include:
l Port Manager on page 65
l Interface Configuration on page 67
l Link Aggregation on page 69
l Static Routes on page 71
l VLAN on page 73
l Quality of Service - Classification on page 87
l Quality of Service - Congestion Control on page 89
l Quality of Service - Policing on page 91
l Quality of Service - Scheduling on page 94

CHAPTER 5 SWITCHING AND ROUTING CONFIGURATION
Port Manager
This screen supports basic Ethernet switch port settings on a per-port basis for chassis
switch ports and PoE plug-in ports.
Procedure
l Go to Switching and Routing Configuration - Port Manager.
l Select the desired values, then click Apply. Values are defined below.

Figure 24. Ethernet Port Basic Settings
Table 15. Ethernet Port Basic Settings
Field Description
Red icon - line protocol is down. For a RAC port it can mean radio receive path is lost.
Port Displays the port (interface) number. Numbers Gi 0/1 to Gi 0/8 refer to the front panel RJ-
45 user ports. Numbers Gi 0/9 to Gi 0/12 refer to the front panel SFP ports. Other numbers
reflect the slot location and ports provided on CTR 8540 plug-in modules, and for CTR
8300, the in-built radio ports provided.
Enable Notes if the port is enabled or not. Click to enable (tick). Untick to disable.
CAUTION: Do not disable (untick) the management port, default port Gi0/1, and click
Apply. Doing so will drop your CTR Portal connection with no possibility to reconnect using
CTR Portal, unless the revert-timer has been set. Otherwise a serial port connection and
CLI will be required to re-enable the management port.
Description Brief description of the port, up to 70 characters. Optional.

Speed - Duplex Chassis switch port options are:

Auto - Default setting (recommended). Both interfaces (i.e., both sides of the cable link)
must be set toAuto.
2.5 Gbps
1 Gbps
100 Mbps - Full
100 Mbps - Half
10 Mbps - Full
10 Mbps - Half
PoE port options are:
Auto
1 Gbps
100 Mbps - Full
10 Mbps - Full
N O TE: The s elec tion options available on SFP por ts
depend on the SFP type ins talled.
MAC Address Displays the MAC address of the interface.

Interface Configuration
This screen supports basic Interface configuration on a per-port basis for chassis switch
ports and PoE plug-in ports.
Procedure
l Go to Switching and Routing Configuration - Interface Configuration.

Figure 25. Interface Configuration
Table 16. Interface Configuration
Field Description
Red icon - line protocol is down. For a RAC port it can mean radio receive path is lost.
Interface Displays the port (interface) number. Numbers Gi 0/1 to Gi 0/8 refer to the front panel RJ-
45 user ports. Numbers Gi 0/9 to Gi 0/12 refer to the front panel SFP ports. Other numbers
reflect the slot location and ports provided on CTR 8540 plug-in modules, and for CTR
8300, the in-built radio ports provided.
Enable Notes if the port is enabled or not. Click to enable (tick). Untick to disable.
CAUTION: Do not disable (untick) the management port, default port Gi0/1, and click
Apply. Doing so will drop your CTR Portal connection with no possibility to reconnect
using CTR Portal, unless the revert-timer has been set. Otherwise a serial port connection
and CLI will be required to re-enable the management port.

Port Type Type of port applied.

The default type is Switch Port.
The type can be changed to Router Port once the Revert Timer has been set. Ensure the
Revert Timer is disabled on completion of the change.
Router Port selection prompts for an IP address and mask.
Ports set as Router Ports appear in the Management IP Address Configuration
screen.
Ports set as Router ports are excluded from VLAN membership.
Port Context Port context, automatically identified based on port type.
Description Brief description of the port, up to 70 characters. Optional.
MTU Enter the MTU for the interface. This value defines the largest PDU that can be passed by
the interface without any need for fragmentation. The configurable value ranges between
46 and 10214 bytes. Default is 1542 bytes.
NOTE: A port must be disabled (unticked) to permit a change to MTU.

Link Aggregation
This screen supports Layer 1 link aggregation by enabling users to group radio links and
protected radio links into a single logical interface.
L1LA implementation on the CTR is very hardware specific. Note the following
requirements for CTR 8540:
l A maximum of 2 groups can be configured.
l If one group is configured a maximum of eight interfaces (radio or protected) may
be grouped together.
l If two groups are configured, each group may only contain four interfaces (radio
or protected).
l Only radio ports can be included, not Ethernet ports.
l Only radio ports or protected interfaces may be added to a L1LA group.
l The far end configuration must match that of near end.
l When two L1LA groups are configured each group can only have a maximum of
two odd and two even numbered interfaces.
o Being odd or even is defined by the port number, e.g., interface 1/2/1 (chassis
1, slot 2, port 1) is an odd interface.
o For a protected link, being odd or even is determined by the lowest port
number of the protected pairing, e.g., primary 4/2, secondary 4/1, counts as
odd.
n With four links per group there must be two odd and two even
interfaces.
n With three links per group there can be two odd and one even numbered
interface, or vice versa.
n With two links per group there can be two odd, two even, or one odd and
one even.
o CTR Portal guards against an incorrect selection.
Note the following requirements for CTR 8300:

l A maximum of 1 group can be configured.
l A maximum of 2 interfaces may be grouped together.
l Only radio ports can be included, not the Ethernet ports or Protected interfaces.
l The far end configuration must match that of near end.
Procedure
l Go to Switching and Routing Configuration - Link Aggregation.
l To add a new Link Aggregation, click the Add button.


l To delete a group, select it and click Remove. To clear all changes that have
been made and not applied, click Clear.
Figure 26. Link Aggregation Settings
Table 17. Link Aggregation Group Settings
Field Description
Group ID Automatically assigned group ID. (Is user defined)
Group id [1 - 2].
N O TE: If 2 is c hos en and gr oup 1 does not exis t
aggr egation r ules s pec ific to having tw o L 1L A gr oups
s till apply.
Description A text description of the group, up to 70 characters.
Enable Notes if the group is enabled or not. Click to enable. Untick to disable.
Max Capacity Maximum capacity of this L1LA group.
Interfaces Select the ports included in this interface. Follow the rules noted in the limitations above.

Static Routes
This screen enables you to review, add, and delete static routes.
Procedure
l Click Switching & Routing Configuration > Static Routes.
l To add a new device, click Add. A new data row displays.
l To configure static route values, enter or select the desired values, then click
Apply.
l To clear an entered value before applying, select it and click Clear.

l Applied values cannot be edited. To reset values click Remove and re-enter all
values. Values are defined below.
l Related dynamic routes display at the bottom of the screen. These are for
reference only: you cannot edit these.

Figure 27. Static Routes
Table 18. Static Routes

Context Router Context selection in CTR Portal is currently restricted to the default
routing table.
Using CLI CTR supports Virtual Routing and Forwarding (VRF) to allow
multiple instances of the routing table to coexist on the platform (up to
10). A VRF created using CLI will be available for selection in the Static
Routes screen.
Management interfaces are (must be) assigned to the default routing
table.
Destination Enter the address for the destination network. An address entry is
Address matched against the prefix (CIDR) setting.
Prefix Enter the prefix.
Next Hop The interface through which the destination network can be reached
is entered from a drop-down menu of interfaces configured as VLANs
or router ports. The field immediately to the right allows you to enter
an IP address for next hop, which applies where the next-hop device
is Ethernet (LAN) connected.
Administrative Set the administrative distance. The default value is 1.
Distance

VLAN
The VLAN tab opens two screens, VLAN and VLAN by Interface. These screens are inter-
dependent - where applicable a change made in one will be matched in the other.
l VLAN and VLAN by Interface screens are presented for Customer Bridge mode
and Transparent Bridge mode.
l For Provider-Edge Bridge mode a screen for C-VLAN to S-VLAN Mapping is
additionally presented.
Refer to:
l VLAN Introduction on page 73
l VLAN Screen on page 74
o Bridge Mode on page 74
l Customer Bridge Mode on page 75
o VLAN Screen: Customer Bridge Mode on page 75
o VLAN by Interface Screen: Customer Bridge Mode on page 76
l Provider Edge Bridge Mode on page 79
o VLAN Screen: Provider Edge Bridge Mode on page 80
o VLAN Interface Screen: Provider Edge Bridge Mode on page 81
o C-VLAN to S-VLAN Mapping Screen on page 82
l Transparent Bridge Mode on page 85
VLAN Introduction
Default Configuration
At initial boot up all switch ports are untagged interfaces and are members of the default
VLAN, which makes them all part of the same broadcast domain. This allows any network
device connected to any switch port to communicate with other devices on other switch
ports.
l Ingressing untagged and tagged frames are available to all ports as members of
VLAN 1. At egress (on untagged interfaces) all tags are stripped.
VLAN Types Supported

Default (Native) VLAN
The default VLAN is VLAN 1. It has all the features of any VLAN, except that you cannot
rename (change its VID) or delete it.

l Ingressing untagged traffic is assigned the PVID of the default VLAN (is tagged by
the PVID of the default VLAN).
o At switch egress on an untagged interface the VLAN tag is stripped.
o At switch egress on a tagged interface the VLAN tag is retained.
o See Untagged and Tagged Interfaces below.
l The default VLAN can be changed away from VLAN 1 on any interface i.e. port
membership of VLAN 1 can be removed/changed.
Management VLAN
The management VLAN is a VLAN configured to access the management capabilities of a
switch. The VLAN is assigned an IP address and subnet mask.
Data VLAN
A data VLAN refers to VLAN tagged traffic where the VLAN is configured to carry user-
generated traffic.
Untagged and Tagged Interfaces

Untagged Interface
Untagged and tagged frames are allowed to ingress, but only untagged frames are allowed
to egress; ingressing tagged frames have their tag stripped at egress.
Tagged Interface
Tagged and untagged frames are allowed to ingress, but only tagged frames are allowed to
egress.
l Ingressing tagged frames retain their tag at egress.
l Ingressing untagged frames retain the default tag applied at ingress.
Setting of untagged and tagged interfaces between the VLAN and VLAN by Interface screens
is inter-dependent. Warnings are raised when conflicts occur.
VLAN Screen
This screen supports VLAN Configuration and VLAN Global Configuration.
VLAN Global default opens to Customer (802.1Q) bridge mode.
Bridge Mode
Global provides options to change to:
l Provider-Edge (802.1ad) Bridge mode. See VLAN on page 73.
l Transparent VLAN Bridge mode. See Transparent Bridge Mode on page 85

Customer Bridge Mode

Refer to:
l VLAN Screen: Customer Bridge Mode on page 75
l VLAN by Interface Screen: Customer Bridge Mode on page 76
VLAN Screen: Customer Bridge Mode

The VLAN Configuration view default opens to show VLAN 1 and the management VLAN,
VLAN 2.
l VLAN 1 port membership includes all ports as untagged interfaces. It is default
assigned an IP address of 0.0.0.0.
l VLAN 2 (on port 1) is the default (primary) management VLAN and is default
assigned an IP address of 192.168.1.1. and mask of 255.255.255.0.
The configuration options enabled through this view include:

l Changing the management IP address and setting the primary management
VLAN. The revert timer must be enabled to allow management address change.
l Add the VLANs to be recognized on the bridge through the setting of their VID,
name (optional), management IP address (where applicable), and membership of
tagged or untagged interfaces. For each VLAN a member interface can be tagged,
or untagged - not both.
o Interfaces selected as tagged allow the ingress of tagged and untagged
frames but only tagged frames are allowed to egress.
o Interfaces specified as untagged allow the ingress of untagged and tagged
frames but only untagged frames are allowed to egress.
o Untagged frames ingressing on tagged or untagged interfaces are tagged by
the default VLAN. The default VLAN is VLAN 1.
o The default VLAN can be changed per interface in the VLAN by Interface
screen. However, to permit such a change the new default VLAN must first be
added in the VLAN screen.
l A Forbidden Interface selection is available to block the selected interface(s) from
being added to the VLAN where dynamic VLANs are configured through GVRP (not
supported at SW release 3.4).
l If ports are configured as Router Ports (Interface by VLAN screen) such ports will
not appear in the Interfaces selection menu.
l A Remove VLAN function is included. Note that it is not possible to change a VLAN
VID - change requires VLAN removal and a new VLAN added with the new VID.

Figure 28. VLAN Screen - Customer Bridge Mode
Table 19. VLAN Screen Values
Field Description
VLAN ID VLAN identification.
Name VLAN name. Optional. Assign a name by typing in the field. Can be up to 32 characters.
Management IP Address Sets an IP address for the management VLAN. VLAN membership will determine which
interface(s) can be used to access the device. To enable access to management IP address
configuration, set the revert timer.
Primary Management Click to move the primary management VLAN to the specified VLAN. A management IP address
must first be set for the target VLAN and the revert timer set.
Tagged Interfaces Tagged interfaces for this VLAN. Click to select tagged interfaces.
Untagged Interfaces Untagged interfaces for this VLAN. Click to select untagged interfaces. An interface can be set
as untagged or tagged - not both.
N O TE: T he De fa ult P V ID fo r i ng re ssi ng unt a g g e d t ra ffi c i s

se t fro m V LA N b y Int e rfa ce o n p a g e 1 .
Forbidden Interfaces Forbidden interfaces for this VLAN. If an interface is forbidden, its ports are blocked from being
added to a VLAN if dynamic VLANs are configured.
VLAN Screen Configuration Procedure

l Click Add to add a VLAN
l Set a Name (optional).
l If the VLAN is to be used for management, click to enable and add an IP
address. The Revert Timer must first be set.
l Add Tagged and/or Untagged Interfaces. If required, set Forbidden Interfaces.
l Go to the VLAN by Interface screen to complete the configuration.
VLAN by Interface Screen: Customer Bridge Mode

This screen provides a view of VLAN membership by interface with configuration options
for:

l Port Mode, with options of Hybrid, Access, or Trunk.

o Hybrid, the default Port Mode, permits egress of tagged and untagged and
priority tagged frames.
n The associated Acceptable Frame Type allows selection of All (default),
Tagged, or Untagged and Priority Tagged frames.
n If changed to Tagged the interface becomes a tagged interface and this will
be matched against the VLAN screen.
n If changed to Untagged and Priority Tagged the interface becomes an
untagged interface and this will be matched against the VLAN screen.
n NOTE: A warning will be provided where a conflict occurs at a change of
Acceptable Frame Type. Bear in mind that an interface can be tagged or
untagged - not both, and that an interface can be a member of multiple
VLANs some of which may have tagged member interfaces and others
untagged.
o Access permits egress of untagged or priority tagged frames. Selection of
Access sets the interface as untagged, and this will be matched against the
VLAN screen.
n A priority tagged frame does not carry a VLAN ID; the 802.1Q tag specifies
only a priority and is referred to as a priority tag.
o Trunk permits egress of tagged frames only. Selection of an interface as
Trunk sets that interface as a member of all configured VLANs.
o NOTE: A warning will be provided where a conflict occurs at a change of Port
Mode, such as will occur on a change to Access (untagged or priority tagged
frames only) if the interface is a tagged member of a VLAN.
l Acceptable Frame Type provides an option with Hybrid Port Mode to select All
(tagged, untagged or priority tagged frames, tagged only, or untagged or priority
tagged only - as above. For port modes of Access or Trunk it confirms the
acceptable frame type indicated above.
l Default Priority is used to set the 802.1p priority bits within the VLAN tag for
frames to be tagged by the switch. 8 levels are provided, with 0 the lowest (best
effort) and 7 the highest. 0 is the default.
o Operation applies to ingressing untagged frames, which are tagged at ingress
by the Default VLAN PVID.
l Default VLAN is the VLAN (PVID) applied per interface on untagged frames. The
default is VLAN 1. If this is to be changed, the new default VLAN must first be
added in the VLAN screen.
l VLAN Membership indicates the VLAN membership for each of the interfaces as
set in the VLAN screen. A drop-down menu lists all VLANs configured in the VLAN
screen with an option to include the interface as a tagged or untagged member of
a configured VLAN, or to exclude the interface from a VLAN membership. Any
changes made in this menu are matched against the VLAN screen and any

conflicts arising are notified on-screen.

l When an interface row is clicked, all other interfaces that the selected row is
connected to are identified by a colored tag.
Figure 29. VLAN by Interface Screen
Table 20. VLAN by Interface Screen Values
Field Description
Interface Interface ID.
Port Mode Select form options of:
Hybrid (default) - Port can accept untagged and tagged frames, and allows users to configure
acceptable frame types.
Access - Port accepts only untagged tagged or priority tagged frames.
Trunk - Port accepts only tagged frames. Port becomes tagged member of all configured
VLANs.
Acceptable Frame Type Configures which Ethernet frame is acceptable at ingress to the interface. This is only
configurable if Port Mode is configured as Hybrid. Options include:
All (Tagged and untagged)
Tagged
Untagged or Priority Tagged
Default Priority Default Priority is assigned to ingressing untagged frames on the interface. If no priority is
assigned, this displays as 0.
Note that QoS must be configured on the interface for the priority to be respected.
Default VLAN (PVID) The Default PVID (Port VLAN ID) setting for the interface, is applied to untagged frames at
ingress to the interface.
VLAN Membership Customer Bridge VLANs: Shows the VLAN ID and its membership with a color tag per
membership to aid identification.

Provider Edge Bridge Mode

A provider edge bridge is used at the edge of a service provider network to provide
demarcation between customer and provider networks. At ingress customer VLANs (C-
VLANs) are encapsulated inside a provider VLAN (S-VLAN), and the provider VLAN is used
to determine traffic forwarding within the provider network. At egress the provider VLAN tag
is stripped.
The provider edge bridge is logically divided into C-VLAN (customer) and S-VLAN (service
provider) components, with internal mapping between.
l The designation of a port as a Customer Edge Port (CEP) implies Provider Edge
Bridge functionality and, specifically, the existence of a C-VLAN component
associated with that port.
l At ingress the C-VLAN bridge component supports selective frame acceptance
(filtering) and identification based on the presence of customer VLAN tagged
frames.
o The filtering includes options of tagged only, or untagged and tagged.
l The S-VLAN bridge component is responsible for tagging customer frames with
S-VLAN tags in the ingress direction and removing S-VLAN tags in the egress
direction.
o It is also responsible for running the provider's bridge protocols.
o Each customer is assigned to one service instance (S-VLAN), which can apply
to multiple VLANs (C-VLANs) per customer.
o Up to 10 service bridge instances can be configured per CTR.
o Ingressing C-VLANs are tagged by the S-VLAN (frames are double tagged).
o Ingressing untagged customer traffic are tagged by the S-VLAN.
o Options are provided to remove the C-Tag at ingress and/or to remove C-Tag
at egress.
To allow continued local PC management access, the port type for management access
when in Provider Edge Bridge mode must be set to Proprietary Provider Network Port, and
is auto set to this port type at initiation of Provider Edge Bridge mode.
Enabling Provider Edge Bridge Mode

l Set the Revert Timer.
l Click on Provider-Edge Bridge Mode.
l Click Apply.
The following advisory screen appears:

N O TE: A c hange to Pr ovider Edge Br idge c annot be undone us ing CTR

Por tal. To c hange bac k to Cus tomer Br idge mode us e the CL I c ommand
for r etur n to fac tor y defaults . Note that the management IP addr es s w ill
r etur n to 192. 168. 1. 1. Us e a s er ial c able c onnec tion to enter the r etur n
to defaults c ommand and to r es et the management IP addr es s . Refer to
the CTR 8500 8300 G etting Star ted Configur ation Guide.
l Click Start.
l The VLAN screen is returned with any VLAN configuration removed except for
VLAN 1 and the management VLAN, default VLAN 2.
Refer to:
l VLAN Screen: Provider Edge Bridge Mode on page 80
l VLAN Interface Screen: Provider Edge Bridge Mode on page 81
l C-VLAN to S-VLAN Mapping Screen on page 82
l Provider Edge Bridge Configuration Procedure on page 83
VLAN Screen: Provider Edge Bridge Mode

Configuration Overview
The VLAN screen presents the S-VLAN bridge component; VLANs added are service-
provider VLANs, those used to encapsulate customer VLANs for tunneling over the provider
network.
l Normally multiple customer VLANs are tunneled over an S-VLAN.
l Customer VLANs are identified in the C-VLAN to S-VLAN Mapping screen.
The VLAN by Interface screen opens to show all ports as Provider Network ports, except
the local management port, which is set as a Proprietary Provider Network port, default
port gi 0/1.

l Provider edge operation is initiated by configuring one or more ports as a

Customer Edge port.
l The customer is connected on a Customer Edge port; the provider network is
connected on a Provider Network port.
o The Customer Edge Port allows ingress of C-Tagged (0x8100) and Untagged
frames.
o The Provider Network Port allows ingress of acceptable frame types of: S-
Tagged (0x88A8) or Untagged, S-Tagged only, or Untagged only.
l A Port Type of Proprietary Provider Network Port is auto-set for the local
management port to retain PC management access.
l Two other customer Port Type options are provided: Customer Network Port
(Port Based) and Customer Network Port (S-Tagged). A brief description of each
is provided on-screen.
With a Customer Edge port configured, the C-VLAN to S-VLAN Mapping screen functions
become applicable.
l The C-VLAN to S-VLAN Mapping screen provides mapping of customer VLANs to
a service provider VLAN.
l Multiple instances of mapping of customer VLANs to a service provider VLAN is
permitted.
VLAN Interface Screen: Provider Edge Bridge Mode

The screen below illustrates the setting of interfaces for customer and provider network
connections.
l gi o/3, 0/4, 0/5 are set as Customer Edge, and gi 0/6 and gi 0/8 as Provider
Network.
l Customer Edge interfaces have an untagged S-VLAN Membership. Note that the
S-VLANs of 44, 55, 66 were previously set using the VLAN screen.
l Provider Network interfaces have been set for an Acceptable Frame Type of S-
Tagged, and have a tagged S-VLAN Membership.

Figure 30. VLAN by Interface Screen
C-VLAN to S-VLAN Mapping Screen

The figure below illustrates the matching C to S VLAN mapping.
l The three customer interfaces have had mappings assigned as shown.
l gi 0/5 shows the prompt for a newly added C-VLAN. There is a drop-down menu
selection for the S-VLAN, and the Id of the C-VLAN is manually entered.

Figure 31. C-VLAN to S-VLAN Mapping Screen
Table 21. Mapping Screen Values
Field Description
C-VLAN ID Customer VLAN identification.
S-VLAN The linked Service VLAN.
Map Untagged Frames Select to map untagged customer frames to this C-VLAN / S-VLAN mapping.
Remove C-Tag at Egress Click to remove C-Tag (untag) frame when exiting this interface towards
customer network.
Remove C-Tag at Ingress to Switch Cick to remove C-Tag (leaving only S-Tag) when entering switch.
S-VLAN Priority Click to select the S-VLAN priority, if required. Options are:
None
Fixed Priority
Copy C-VLAN Priority
Provider Edge Bridge Configuration Procedure

l In the VLAN screen click Add to enter a new VLAN (S-VLAN). Note that under
Provider Edge Bridge mode the VLAN screen configures the S-VLAN.
l Enter the VLAN Id for the new S-VLAN. One or more S-VLANs can be entered.
l Click Apply.
l Go to the VLAN by Interface screen to configure required ports for customer and
provider connection.
l Select the interface(s) for customer network connection and using the Port Type

drop-down menu change Port Type to Customer Edge Port.

o Click on its S-VLAN Membership tag and from the drop-down menu select
the S-VLAN Id set in the VLAN screen and click to Untagged.
o The untagged S-VLAN membership determines that the S-Tag is stripped at
egress from the provider network. The untagged setting for the S-VLAN is
now also shown on return to the VLAN screen.
l Select the interface(s) for service provider network connection. Use the default
Port Type of Provider Network Port.
o Under S-VLAN Membership select from the drop-down menu the VLAN or
VLANs required and click to Tagged.
o For the default Acceptable Frame Type of S-Tagged (0x88A8) or Untagged,
or for the Untagged only selection, Default S-VLAN PVID and Default Priority
settings are required. These apply to ingress of untagged frames on the
provider network port.
n Normally only S-tagged frames should be ingressing on the provider
network port, in which case select the Acceptable Frame Type to S-
Tagged (88A8).
n If untagged frames are to be allowed the Default S-VLAN PVID must
match the PVID of the S-VLAN set for S-VLAN Membership, or in the
case of multiple membership, the PVID of one of the members. The
Priority setting is the priority applied to ingressing untagged frames over
the provider network.
l Click Apply.
l Go to the C-VLAN to S-VLAN screen click on a configured customer interface.
Only interfaces set as Customer Edge Port are presented.
o Click Add to add a mapping row. The S-VLAN is displayed with a prompt to
enter the customer C-VLAN Id.
o Enter a C-VLAN Id for one of the VLANs identified by the customer to the
service provider.
o If untagged frames received on the customer interface are to be forwarded,
click Map Untagged Frames. If the C to S mapping is to two or more S-
VLANs the mapping can be selected to one of the S-VLANs.
o Options are provided per C-VLAN to Remove C-Tag at Egress, and/or
Remove C-Tag at Ingress.
o Enter an S-VLAN Priority to assign a priority on the C-VLAN tunneled over
the provider network.
l Click Apply, and Save.

Transparent Bridge Mode

Transparent Bridge mode is a non-native mode. It operates through a special port
membership configuration on a customer bridge to ensure tagged and untagged traffic is
forwarded without modification.
Operation is enabled by:
l Creation of VLAN 4094 to which all interfaces are added as untagged interfaces.
o The Default VLAN PVID (VLAN by Interface screen) is set to 4094 on all
interfaces EXCEPT the local 'out-of-band' NMS interface.
n The local management interface retains its PVID, which is default VLAN 2
on interface gi 0/1.
o Untagged frames received on one member port are forwarded to all other
member ports of VLAN 4094.
o The internal VLAN 4094 tag (default VLAN) applied at ingress is stripped at
egress, to provide transparent communication for untagged frames.
o NOTE: VLAN 4094 must not be used as a customer data or management VLAN.
l The use of VLAN 1 to which all interfaces (including all tagged NMS interfaces)
are added as tagged ports.
o Tagged frames received on one member port are forwarded to all other
member ports of VLAN 1.
o Tagged frames retain their tag at egress to provide transparent
communication for tagged frames.
l Any existing/user configured VLANs configured on the bridge (those added in the
VLAN screen) operate as normal. For example if VLAN 77 is configured and has
ports gi 0/5 and gi 0/6 as members, only gi 0/5 and gi 0/6 will egress this VLAN.
Such VLANs do not operate transparently across all interfaces.
o This also applies to the management VLAN for VLAN aware NMS. On the
bridge the management VLAN must be manually configured.
l The Port Mode / Acceptable Frame Type is set to Hybrid / All on all interfaces.
l If a plug-in module is subsequently installed into a CTR8540, its interface(s) must
be manually added to support transparent mode.
Enabling Transparent Bridge Mode

l Set the Revert Timer.
l Click on Transparent VLAN Mode.
l Click Apply.

Figure 32. Example VLAN Screen for Transparent Bridge Mode

Quality of Service - Classification

This screen displays QoS - Classification. Users can configure priority mapping and
classification for VLANs and interfaces. Supported classification includes priority types for
802.1p, DSCP and IP ToS .
Note that VLANs and interfaces with identical classification configurations are grouped
together.
Procedure
l Go to Switching and Routing Configuration - Quality of Service - Classification.
l Priority mapping and classification settings display by classification type.
Interfaces and VLANs that have identical configurations are grouped together.
l To view and configure QoS - Classification, click on the display bar for a
classification to expand it. The values for the classification display. You can
change:
l Enabled status of a Priority mapping
l Ingress priority to Internal Priority mapping
l Pre-Color
l Policy Map
l To create a new classification, click Add. A new classification displays.
l In the new classification, click the first popup to select priority type :
l VLAN 802.1P
l IP ToS
l IP DSCP
WARNING: Pr ior ity Type c annot be c hanged after it is c r eated.
l Click the second button to select whether this applies to Interfaces or VLANs.
Then, select the relevant interface/VLANs. Again, the type of interface cannot be
changed after it is created, but membership within the type can be changed.
l When you are done making changes, click Apply. To save changes, click the
Save icon.

Figure 33. Quality of Service - Classification
Table 22. QoS Policing Values
Field Description
QoS Group Click on a classification to display the values for a QoS group.
Internal Priority Displays the internal priority assigned to ingressing traffic for the
interface/VLAN. Default is 0, lowest priority.
Enable Check the box to enable this priority level. Each priority mapping creates a
rule on the switch. As there are limited rules, it is recommended that for
IP DSCP only the priorities in use should be enabled.
Pre-Color Set the pre-color policing value from the drop-down menu.
None
Red
Yellow
Green
Policy map/policing Set policing values for policy map ID and policing mode. Options displayed are
policies configured viaQuality of Service - Policing on page 91 . Note that a
policy must be configured for traffic to flow. Default configuration contains
Policy 1 with no metering.

Quality of Service - Congestion Control

Users can set QoS congestion control for each enabled QoS interface.
Algorithm Options
There are four commands to configure congestion management behavior on queues:
taildrop byte mode, taildrop packet mode, RED, and WRED.
l Tail Drop Bytes - All newly arriving bytes will be dropped, beyond the maximum
depth of the queue.
l Tail Drop Frames - All newly arriving packets will be dropped, beyond the
maximum depth of the queue.
l RED - On packet arrival, a weighted random early detection algorithm is executed
which will randomly drop a packet. With RED you only specify one set of values for
minimum threshold, maximum threshold and mark probability denominator.
l WRED - On packet arrival, a weighted random early detection algorithm is
executed which will randomly drop a packet. In WRED you can specify three sets
of values. The drop precedence will determine which one of the three is used for
the packet enqueuing.
Procedure
l Go to Switching and Routing Configuration - Quality of Service - Congestion Control.
l To view and configure QoS Congestion Control, select an option and click on its
table row. The values display. You can change Drop Algorithm and Queue Limits
(see the table below).
Save icon.
Figure 34. Quality of Service - Congestion Control Configuration

Table 23. QoS Congestion Control Configuration
Field Description
Template ID Assign an ID number to each template.
Drop Algorithm Select the algorithm from the drop-down menu: Tail Drop Bytes, Tail Drop
Frames, RED, or WRED, as defined above.
Queue Limits Set the queue limit.
Number of Queues Using Number of established QoS queues using this template.
Template

Quality of Service - Policing

This screen displays Quality of Service - Policing. Users can set QoS Policing values and
create new Policing configurations.
For each Policy ID, the Meter Type enables/requires the Policing rate and size settings, and
associated conform, exceed and violate action settings.
About PIR/PBS Values

CTR Portal does not allow direct configuration of PIR/PBS parameters. The PIR/PBS are
calculated internally using EIR/EBS, and entering EIR/EBS values will also set up PIR/PBS
values.
This screen is where users enter EIR and EBS values. Note that:
EIR = PIR – CIR
EBS = PBS - CBS
Procedure
l Go to Switching and Routing Configuration - Quality of Service - Policing.
l The available QoS policing configurations display. Each policy has its own table
row with QoS data.
l You can configure QoS - Policing. Begin by selecting the Meter Type . The
selected Meter Type enables or disables other values in the Policing row. Edit
these other data types as required.
l To create a new Policing configuration, click Add. A new classification displays.
Select the Meter Type and enter a unique ID for the Policy. Then, edit the other
data types as required. Note that certain Meter Types display with ranges or
limitations:
Save icon.

Figure 35. Quality of Service - Policing
Table 24. QoS Policing Values
Field Description
Policy ID QoS policy ID.
Meter Type Select policing meter type:
None (metering not in use)
Single Token Bucket
Single Rate Three Color Marker
Two Rate Three Color Marker (see Note below)
Dual Bucket MEF Decoupled
Dual Bucket MEF Coupled
N O TE: The s elec ted meter type enables or
dis ables other values in this data table. Set
other values as r equir ed.
N O TE: For Tw o Rate Thr ee Color Mar ker - the

input is EIR, EBS w hic h differ s fr om the
r elated CL I of PIR, PBS. To adjus t for this , EIR
and EBS c an be c alc ulated: EIR = PIR - CIR,
EBS = PBS - CBS.
Color Aware Select the check box to enable Color Aware status. With Color Aware active,
metering is performed with regard to frames having been metered and marked
at a previous step.
CIR (Kbit/s) Set the value for Committed Information Rate in kbit/s. Disabled if metering is
set to None.
CBS (Bytes) Set the value for Committed Burst Size in bytes.
Disabled if metering is set to None.
EIR (Kbit/s) Set the value for Excess Information Rate in kbit/s.
Disabled if metering is set to None, Simple Token Bucket or Single Rate Three
Color.
EBS (bytes) Set the value for Excess Burst Size in bytes.

Conform Action Select the action applied when data conforms to set values.
None
Remark IP to ToS
Remark IP DSCP
Remark VLAN 802.1P
Exceed Action Select the action applied when data exceeds set values.
None
Remark IP to ToS
Remark IP DSCP
Remark VLAN 802.1P
Violate Action Seelct the action applied when data violates set values.
Drop
Remark IP to ToS
Remark IP DSCP
Remark VLAN 802.1P
Note that for Remark actions:

l IP TOS - Enter a value between 0 -7
l VLAN 802.1P - Enter a value between 0 -7
l IP DCSP - Enter a value between 0 - 64

Quality of Service - Scheduling

This screen displays scheduling action by enabled interface. Users can set QoS Scheduling
algorithms and congestion control for each enabled QoS interface. There are 8 queues for
each interface.
Procedure
l Go to Switching and Routing Configuration - Quality of Service - Scheduling.
Configured QoS scheduler type with internal priority and weighting values are
available for each enabled interface.
l To view and configure a QoS Schedule, click on its table row. The values for the
Scheduler display. You can view Internal Priority and Weight values. You can
change:
l Scheduler - Select the Scheduler algorithm. Options are listed in the table below.
l Congestion Control - Select either None or one of the configured queue templates.
Save icon.
Figure 36. Quality of Service - Scheduling
Table 25. QoS Scheduling Values
Field Description

Scheduler Select the QoS Scheduling algorithm:

Strict Priority
Round Robin
Weighted Round Robin
Weighted Fair Queuing
Strict Round Robin
Strict Weighted Round Robin
Strict Weighted Fair Queuing
CIR EIR - Committed and excess rate algorithm
Strict CIR EIR - Strict committed and excess rate algorithm
CAUTION: CIR EIR options are not supported on radio, L1LA or
protection interfaces.
Internal Priority Displays the Internal Priority setting for each queue.
Weight Displays the weighting applied to weighted scheduler actions by queue. A color
dot displays the apportionment of weighting by weighted queue.
N O TE: Configur able only for s c heduling
algor ithms that us e w eights . For Weighted Fair
Q ueuing and Str ic t Weighted Fair Q ueuing - the
w eight mus t be lar ger than the inter fac e's
MTU.
Congestion Control Enable congestion control by selecting an option, from the list of configured
queue templates. Configure these from Quality of Service - Congestion
Control on page 89.

OSPF CHAPTER 6
Chapter 6. OSPF
OSPF is a link state protocol that distributes routing information between routers within a
single IP domain, or 'autonomous system' (AS). Each router (CTR) maintains a database
describing the topology of the AS, with each participating router maintaining an identical
database from the perspective of that router.
OSPF routers exchange state, cost, and other relevant interface information with neighbors
through maintenance of tables for:
l A neighbor table that contains all the recognized OSPF neighbors.
l A link state database (LSDB) topology table that contains all routers in the
network and their attached links.
l A routing table ( forwarding database) that contains a list of the best paths to
various destinations.
From the LSDB, each router constructs a tree of shortest paths, using itself as the root. The
shortest path tree provides the route to each destination in the AS. When several equal-cost
routes to a destination exist, traffic can be distributed among them. The cost of a route is
described by a single metric.
An AS can be divided into multiple areas to provide improved scalability.
l An area is a logical collection of networks, the topology of which is concealed
from the other areas in the AS to reduce OSPF protocol traffic.
l The benefits can be a significant reduction in the size of the routing table and
associated decrease in OSPF route calculation time and LSDB size.
Within a multi-access (broadcast) network segment, a designated router (DR) and backup
designated router are elected. Each non-DR or non-BDR router exchanges routing
information only with the DR and BDR, instead of exchanging updates with every router in the
area. The DR then distributes topology information to every other router inside the same
area resulting in much reduced OSPF traffic.
The OSPF backbone area, area 0.0.0.0, must be contiguous and all other areas must be
connected to the backbone area. The backbone distributes routing information between
areas.
Routing in the AS takes place on two levels, depending on whether the source and
destination of a packet reside in the same area (intra-area routing) or different areas (inter-
area routing).
l With intra-area routing packets are routed solely on information obtained within
the area; no routing information obtained from outside the area is used, and every
router that belongs to the same area has an identical topological database for that
area.
l With inter-area routing the routers that belong to more than one area are 'area
border routers' (ABRs). These maintain separate topological databases for each
area they are connected to.

CHAPTER 6 OSPF
CAUTION: The CTR Portal OSPF screens for SW release 3.4 are intended for routed NMS
instances only.
N O TE: The CTR Por tal OSPF s c r eens s uppor t bas ic OSPF c onfigur ation.
For advanc ed c onfigur ation CL I mus t be us ed. Refer to the CTR
8500/8300 O SPF Configur ation Us er Manual.
For configuration refer to:

l OSPF Routers on page 98
l OSPF Areas on page 99
l OSPF Interfaces on page 100

OSPF CHAPTER 6
OSPF Routers
For an introduction to OSPF see OSPF on page 96.
OSPF Router Screen

The OSPF Router screen is used to enable OSPF and set the router ID.
l Router Context selection in CTR Portal is currently restricted to the default routing
table. Using CLI, CTR supports Virtual Routing and Forwarding (VRF) to allow
multiple instances of the routing table to coexist on the platform (up to 10).
l Router ID is entered as an explicit address.
Figure 37. OSPF Router Screen

CHAPTER 6 OSPF
OSPF Areas
OSPF Area Screen

The OSPF Area screen enables configuration of Area (Area ID) and Area Type.
l Area ID is the dot-decimal notation of the area.
l Area Type is selected from options of:
o Normal: The device is included in the backbone 0.0.0.0 area or other area,
such as 0.0.0.1. It is not within a Stub or Not So Stubby area. Co-joined areas
are linked via an ABR (Area Border Router).
o Stub: The area is linked by one ABR to the rest of the AS (Autonomous System).
o Not So Stubby: The area allows external routes (from outside the AS) to be
flooded within the area: the area hosts an ASBR (Autonomous System Border
Router) with links to an external network.
Figure 38. OSPF Area Screen

OSPF CHAPTER 6
OSPF Interfaces
OSPF Interface Screen

The OSPF Interface screen configures the interfaces used to link to an area together with a
priority and password option.
Figure 39. OSPF Interface Screen
Field Description
Router Context Router Context selection in CTR Portal is currently restricted to the default routing table.
Using CLI, CTR supports Virtual Routing and Forwarding (VRF) to allow multiple
instances of the routing table to coexist on the platform (up to 10). A VRF created using
CLI will be available for selection in the OSPF Interface screen.
Management interfaces are (must be) assigned to the default routing table.
Interface The interface for which the other screen settings apply. The interfaces available for
selection are the ports and VLANs configured with an IP address.
Area Select the OSPF area for the interface from the areas configured in the OSPF Area
screen.
Priority Set an OSPF priority, 1 to 255. Default is 1. The router with highest priority within
the network becomes the designated router (DR) for the network. The router with
the next highest priority is the backup designated router (BDR).
Interface Type Select from:
Broadcast: Specifies that the network supports many routers together with the
capability to address a single physical message to all of the routers (broadcast).
NBMA: Non-Broadcast Multi-Access. Applicable to a network supporting many routers
but having no broadcast capability.
PTOMP: Point-to-Multipoint.Treats a non-broadcast network as a collection of point-to-
point links.
PTOP: Point to Point. Specifies messaging between a single pair of routers.
Authentication Sets the authentication algorithm and keys. Options are – None, Simple Pass-
word, or Crypto > MD5. A Key ID and Authentication Key is required for MD5.

RADIO CONFIGURATION CHAPTER 7
Chapter 7. Radio Configuration

This section lists radio configuration functions. Topics include:
l Radio Links on page 103
l Radio Protection on page 116
l Radio Link Diagnostics on page 114
l Radio Protection Diagnostics on page 119

CHAPTER 7 RADIO CONFIGURATION
Radio Links
The Radio Link screen supports configuration of radio interfaces on a CTR 8300, and on
enabled RACx2 and RACx1 modules on a CTR 8540. You can alternate between ETSI and
ANSI profiles.
To set up protected link operation, see Radio Protection on page 116.
Procedure
l Go to Radio Configuration - Radio Links. From the Radio Links screen select the
required radio link interface from the available (installed) RACs (boxes at the top
of the screen) to view and edit.
l Click Apply to enable entered value(s). To remove a value before it is applied,
click Clear.

Figure 40. Radio Configuration Screen (partial)

Table 26. Radio Link Configuration Values
Item Value
Interface
Enable To enable the radio interface, select the check box.
Removing the check shuts down the interface.
N O TE: Dis abling the
inter fac e s tops the
inter fac e fr om s ending
tr affic , it does not s top the
r adio fr om tr ans mitting.
Us e Fac tor y Tx Mute, or
Diagnos tic Tx Mute to
s hutdow n tr ans mis s ion.
Description Name of the radio link (optional).
ACU (Visible only if the attached RFU is an IRU with Antenna Coupler Unit)
Tx Center Frequency (MHz) Enter the listed transmit centre frequency parameter
of the associated ACU.
Tx Filter Bandwidth (MHz) Enter the listed transmit filter bandwidth parameter of
the associated ACU.
TX Insertion Loss (dBM) Enter the insertion loss characteristics of the
associated ACU for the transmit path.
Rx Center Frequency (MHz) Enter the listed receive centre frequency parameter of
the associated ACU.
Rx Filter Bandwidth (MHz) Enter the listed receive filter bandwidth parameter of
the associated ACU.
RX Insertion Loss (dBM) Enter the insertion loss characteristics of the
associated ACU for the receive path.
Capacity
Regulatory Standard Choose ANSI or ETSI.

Item Value
Bandwidth Bandwidth options are dependent on the ODU
connected to the Radio Port.
An example of the ETSI bandwidth options:
7MHz
14 MHz
28 MHz
40 MHz
55 MHz
XPIC Select the check box to enable XPIC (RACx2 only).
N O TE: This is dis abled if
not lic ens ed (XPIC lic ens e)
and hidden if the inter fac e
is on an RACx1 plugin, or
if the s elec ted bandw idth
does not s uppor t XPIC
Modulation Mode Choose Fixed or ACM. ACM requires an ACM feature
license. ATPC must be selected for ACM operation -
see below.
Modulation Base and Max With ACM selected, Modulation Base and Modulation
Max selections are presented.
Modulations between QSPK and 256QAM inclusive
require an ACM 256 license (or an ACM 1024 license).
Modulations between 512QAM and 1024QAM inclusive
require an ACM 1024 license.
Select the base and maximum modulation values
from:
QSPK
16QAM
32QAM
64QAM
128QAM
256QAM
512QAM
1024QAM High Gain
The ACM operation range is determined by the Base
(lowest) to Max selection. All intermediary
modulations are included in the range. For example if
the range selected was QPSK to 1024QAM High Gain,
ACM would operate over 8 modulation steps.
Modulation Mask Select the modulation mask. Applies to ETSI ACM
operation only. The mask sets the modulation rate that
determines the maximum allowable Tx power within
the ACM operation range.

Item Value
Max RF Capacity The maximum air-link capacity for this link.
Calculated based on the selected Bandwidth and
Modulation.
Assigned Licensed Capacity Licensed capacity assigned to this link. The link will
only operate up to the user-assigned capacity
regardless of the maximum capacity.
Available Licensed Capacity Unused licensed capacity.
Frequency
Tx Frequency Range The MHz range for this link, determined by the
connected ODU.
Tx Frequency Band The high or low band for this link, High or Low.
Determined by the connected ODU.
Tx Frequency Specific Tx frequency for the link, must be within the
MHz range specified above. Mouse-over to view range.
Rx Frequency Specific Rx frequency for the link, must be within the
specified MHz range. Mouse-over to view range.
Tx /Rx Spacing (MHz) Displays the spacing between entered Tx and Rx
frequencies.
Transmit Power Transmit power value and status for the selected
interface, as shown below. For protected link oper-
ation both protected interfaces will be displayed.
High Power Select the check box to enable high power, which
increases the maximum Tx power available. ODU 600
only. Requires an FPM License (Flexible Power Mode).

Item Value
ATPC See Setting ATPC on page 108. With ATPC enabled
the following values display:
FCC Compliant - FCC Compliant option is enabled.
Selection applies only to link operation under FCC
jurisdiction where the coordination notice permits a
coordinated Tx power less than the maximum Tx
power under ATPC. See FCC Implementation on
page 111.
Target Remote Fade Margin (dBm) - Set the target
remote fade margin
Detected Remote Fade Margin (dBm) - Displays
the detected actual remote fade margin
Tx Power - Min and Max - enter values to set the
minimum and maximum transmit power under
ATPC
ATPC must be enabled for ACM (Base and Max
modulation not set to same value).
TX Power (dBm) Enter the configured transmit power (no ATPC).
IRU Power Offset (dBm) Enter the single frequency output power calibration
offset.
N O TE: This field is vis ible
only w hen the attac hed
RFU is an IRU 600v3
devic e.
Detected Tx Power The detected Tx power in dBm.
Factory Tx Mute Select the check box to disable transmission from the
radio.
Payload Encryption (Licensed feature- visible only when license enabled)
Link ID Enter the password used to encrypt data.

Encrypt Tx Traffic Select the check box to encrypt traffic. When you select
this Check box, the fields below become visible.
KeyLifeTime (days) Enter the number of days after which the key will be
changed.

Item Value
KeyLifeTimeRemaining The number of days remaining after which the key will
be changed.
TxKeyId The Id of the current key that is in use.
Change Keys Select the check box to reset the key.
Receive Power Receive power value and status for the selected
interface, as shown below. For protected link oper-
ation both protected interfaces will be displayed.
RSL Received Signal Level.

SNR Signal-to-noise ratio.
Active RX Time The accumulated time the link has been receiving
data. Valid only when a link is not Tx Muted.
RX Sync Loss Time The accumulated time the link has lost connection
with the far end of the radio link. Valid only when a link
is not Tx Muted.
N O TE: IRU operati on requ i res CT R 8540 RA C x1 or
RA C x2. For th e L 6 an d U6 IRU 600v 3 EHP RFU a
degraded th resh old appli es on small n on -stan dard T /R
spaci n gs (less th an 150 MHz).
Setting ATPC
N O TE: Refer als o to ATPC G uidelines for Adaptive Modulation on page 110
This procedure is based on the prevailing path conditions being typical during the setup
procedure, that is, not subject to rain fade or other fade conditions and assumes the Target
Fade Remote Margin is the primary driver for establishing the settings.
The objective is to check that the Target Remote Fade Margin and the Detected Tx Power are
within +/- 3 dB of the planned figures for the link, and that there is appropriate Tx Power
headroom for correct ATPC operation.
Target Remote Fade Margin

This is the desired fade margin for the remote-end RAC/RFU. Depending on the path design
this should be set at a level which will allow head room for the local Tx power, while
ensuring an adequate fade margin. Not doing so can cause Tx power to rise to the maximum
permitted, and to stay at maximum.
Detected Remote Fade Margin

Detected using RSL and SNR data received from the remote radio.

If the RSL and/or SNR values are too low then the local Tx power is increased until the
Target Fade Margin is achieved, or until the maximum Tx power setting is reached,
whichever occurs first.
Similarly, if the RSL value is too high, then the local Tx power is decreased until the target
fade margin is achieved, or until the minimum Tx power setting is reached, whichever
occurs first.
Under normal operating conditions the Target Remote Fade Margin and the Remote Fade
Margin should indicate within 2 dB of each other.
Tx Power
Mouse-over for the permitted maximum and minimum values for the ODU/RFU. Maximum
values are band specific, and modulation dependent. It is also license dependent for FPM
ODUs/RFUs.
l The operating license for the link may limit Max Tx Power to a setting below the
maximum permitted by the ODU/RFU.
l The minimum power must be set such that under normal operating conditions a
satisfactory fade margin is preserved (it should not be set too low).
l Max to min represents the Tx power control range for the ODU/RFU.
Detected Tx Power
This is the detected/measured Tx power. With ATPC enabled it provides an indication of the
actual Tx power, which under normal conditions should be inside the maximum and
minimum Tx power settings (not hard up against the max and min). When ATPC is disabled,
the Detected Tx Power indication should be within 0.2 dB of the set Tx Power.
N O TE: O n CCDP/XPIC links ATPC s hould be OFF on both links to help
optimize XPIC oper ation. This es pec ially applies w her e antenna c r os s -
pol dis c r imination (XPD) is les s than 25 dB, or the link path is
long/diffic ult.
N O TE: Similar ly, adaptive modulation, w hic h r equir es ATPC (is default
fixed to O N) s hould not be us ed on CCDP/XPIC links w her e antenna
c r os s -pol dis c r imination (XPD) is les s than 25 dB, or the link path is
long/diffic ult.
N O TE: Wher e a link lic ens e s pec ifies a maximum Tx pow er , the maximum
Tx pow er s etting for ATPC mus t be s et no higher than the lic ens ed
maximum.
To Ensure Correct ATPC Operation:

l Initially set Max Tx Power at or near to the maximum for the capacity and
bandwidth option of the link, and set Min Tx Power towards the minimum.
l Set the Target Remote Fade Margin to the figure indicated in the path planning
data sheet for the link.

l To confirm the Max/Min Tx Power and Target Remote Fade Margin, click Apply.
l Read the resulting Remote Fade Margin and verify it is within 3 dB of the planned
fade margin for the link.
l Read the Detected Tx Power for the link and verify it is within 3 dB of the planned
Tx power for the link.
l Reset the Max Tx Power, if required, to a lower level. A lower level may be
specified within the link operating license issued by the local regulatory
authority. Max Tx Power should be set not less than 7 dB above the Detected Tx
Power, to provide headway for ATPC action in the event of a path fade.
l Reset the Min Tx Power to the normal (prevailing) Detected Tx Power, or to a
level not more than 3 dB to 6 dB below the Detected Tx Power. This setting will
safe-limit the minimum if the fade conditions lead to rapid and large Tx power
movement.
l To commit the configuration, click Apply and Save .
l Monitor ATPC operation to ensure it is providing the expected benefits under the
prevailing path conditions. Where indicated, ATPC settings should be optimized,
or in situations of frequent, fast and high fading it may be best to disable ATPC.
ATPC Guidelines for Adaptive Modulation

ATPC is required for an adaptive modulation (ACM) selection. The ATPC user-entry fields are
identical to those supported for fixed modulation.
Under adaptive modulation, ATPC is optimized to improve received SNR at the far end,
and consequently push for a modulation increase (up to the maximum configured
modulation).
Modulation changes are primarily determined by receiver SNR thresholds. Each
configured modulation has an improve SNR threshold and a degrade SNR threshold.
l SNR is the sole criteria for step-downs (degrade).
l SNR with ATPC settings are used for step-ups (improve).
When the receiver SNR reaches the improve threshold, and the target remote fade margin
is maintained, a modulation switch request is sent to the remote transmitter which results
in the transmitted modulation from the remote end changing to the next higher throughput
modulation. Similarly, if the receiver SNR goes below the degrade threshold, a modulation
switch request is sent, resulting in the transmitted modulation from the remote end
changing to the next lower throughput modulation.
l The improve and degrade thresholds incorporate a level of hysteresis to prevent
modulation oscillations occurring.
Adaptive modulation should not be used on CCDP/XPIC links where the V+H antenna cross-
pol discrimination (XPD) is less than 25 dB, or the link path is long/difficult. Link XPD is
available in the Statistics > Radio Link screen.

Under adaptive modulation the ATPC Target Remote Fade Margin (TRFM) maximum is
limited on some modulation and Tx power combinations to ensure modulation step-up
(improve) operates as intended.
FCC Implementation
N O TE: The FCC Compliant ATPC s elec tion applies only to link oper ation
under FCC jur is dic tion w her e the c oor dination notic e per mits a
c oor dinated Tx pow er les s than the maximum Tx pow er under ATPC.
FCC guidelines support use of ATPC to establish a coordinated Tx power, a power lower than
a maximum Tx power, for the purposes of calculating interference into victim receivers.
These guidelines are provided within TIA TSB 10-F, Interference Criteria for Microwave
Systems.
From TIA TSB 10-F, the Tx powers associated with an ATPC system included on the
coordination notice may be summarized as:
l Maximum Transmit Power. The Tx power that will not be exceeded at any time.
l Coordinated Transmit Power. The Tx power selected by the ATPC system
licensee as the power to be used in calculating interference levels into victim
receivers. The Coordinated Transmit Power is restricted to a 0 to 10 dB range
below the Maximum Transmit Power.
l Nominal (Normal) Transmit Power. The Tx power at or below the Coordinated
Transmit Power at which the system will operate in normal, unfaded conditions.
The Normal Transmit Power must be less than or equal to the Coordinated
Transmit Power.
At least a 10 dB fade must occur before the Coordinated Transmit Power is exceeded.
In order to claim a coordinated Tx power less than the maximum Tx power, certain
restrictions on the time that this power is exceeded during the course of one year must be
met, and a timer function applies to ensure that maximum power is not sustained for more
than five continuous minutes.
l The annual restrictions set out the time permitted (as an annual percentage)
above the coordinated Tx Power.
l These time percentages are determined using applicable reliability calculations.
l The process determines the lowest permitted coordinated Tx power (within a
range of 0 to 10 dB below maximum Tx power).
l The timer function ensures Tx power under ATPC control is not sustained at
maximum power for more than five continuous minutes so as to prevent a
condition from holding Tx power at the maximum for an extended period of time
without advice to the link/network operator.
l ATPC operation must be RSL based only.
Within CTR this process is supported by an FCC Compliant tickbox, which is made available
whenever ATPC is enabled. When FCC Compliant is selected it enables:

l A five minute timer function. When maximum Tx power is sustained for 5

continuous minutes, Tx power is momentarily reduced by 10 dB and an
informational event of "ATPC Pwr temporarily reduced by 10 dB" is logged in the
management system Events Browser.
o If operating conditions continue to cause the link to operate at maximum Tx
power for 5 consecutive minutes, the process of reducing maximum Tx power
by 10dB and logging an informational event is applied again.
o If the Tx power is reduced from maximum during a 5 minute countdown, the
timer function is reset.
l RSL-only ATPC operation.
Note that:
l FCC Compliant need only be selected when a coordinated power less than max
power has been approved for the link.
l If the coordinated power = max power, ATPC is not required.
l If coordinated power = max power and you still wish to use ATPC, you do not need
to select FCC Compliant.
l The informational event logged on 5 minute timeout at maximum Tx power must
be visible to the network operator (not excluded from reported events).
Where fading events, such as rain fading, can cause maximum Tx power periods much
longer than five continuous minutes, the path might best be coordinated at maximum Tx
power.
ATPC Settings for a Coordinated or Normal Transmit Power

N O TE: ATPC oper ation mus t ens ur e that c oor dinated and maximum Tx
pow er s c omply w ith r equir ements s et out in the lic ens e c oor dination
notic e.
CTR ATPC settings enable configuration of maximum Tx power, minimum Tx power, and a
target remote fade margin.
The target remote fade margin (TRFM) sets the ATPC trigger point, the point at which Tx
power begins to ramp up, dB for dB during a path fade (increments/decrements are in 0.1
dB steps). The TRFM is used to establish a normal Tx power 10 dB below coordinated to
satisfy the requirement that at least a 10 dB fade must occur before coordinated power is
exceeded.
l Maximum (and minimum) Tx power setting is ODU/RFU and frequency band
specific. Refer to CTR ANSI datasheets.
l The Tx power control range (maximum to minimum) under ATPC is modulation
dependent.
l Coordinated Tx power is not provided as an ATPC setting. It is established at its
licensed level by setting normal Tx power at a point 10 dB below coordinated Tx
power. This is to ensure that a 10 dB fade occurs before the coordinated Tx power

is exceeded.
l For example, if the maximum Tx power is 25 dBm, and the coordinated Tx power
is 5 dB lower at 20 dBm, the normal Tx power should be established 10 dB lower
at 10 dBm. This setting of normal Tx power means the required 10 dB fade (down
from normal) occurs before the coordinated Tx power is exceeded.
l Normal Tx power is established using the ATPC target remote fade margin
(TRFM) setting. This sets the desired fade margin for the remote-end ODU/RFU.
Tx power is adjusted so that the TRFM is met. Actual (measured) fade margin is
confirmed by the remote fade margin (RFM). No adjustment of Tx power occurs
when RFM nominally matches the TRFM.
l Minimum Tx power can be set at normal Tx power - or no lower than 5 dB below
normal Tx power. This is to safe-limit the minimum when fade conditions lead to
rapid and large Tx power movement. Note that like maximum Tx power, minimum
Tx power is control range limited.
l On completion of the settings, monitor ATPC operation to ensure it is providing
expected operation under the prevailing path conditions.

Radio Link Diagnostics

This screen enables diagnostics on radio links.
N O TE: To view link per for manc e data s ee Statistic s > Rad io Link .
Procedure
l Go to Radio Configuration - Radio Link Diagnostics.
l Select the required diagnostic(s) and duration, then click Start.
l A duration time can be canceled at any time by clicking the check box and
selecting Off, then clicking Apply.

Figure 41. Radio Link Diagnostics
Table 27. Radio Link Diagnostics Values
Item Value
Radio Link Name and port location of radio link.
RFU Details Associated RFU.
RFU Mute Applies a Tx mute for the set duration.
Modulation Lock Use the timer to set the modulation to be locked-on for a set duration.
Applies only on an adaptive modulation link. The selection options are
the Base-to-Max modulation range as set in the Radio Link screen.

Item Value
IF Loopback Use the timer to set a loopback duration. The IF loopback applies a
loopback at the RAC-to-ODU/RFU IF interface. A Tx mute is applied. All
traffic is affected.
XPD on BNC Use the timer to set the duration for an XPD voltage to be available on
the ODU BNC connector, replacing the RSSI voltage. Applicable during
antenna alignment on CCDP/XPIC links.
Carrier Only Use the timer to set a RF carrier-only signal (no modulation).
Applications include frequency measurement and true RMS power
measurement using external measurement devices.
RFU Power Disable Use the timer to disable the RFU power. Applicable during change-
out of an ODU/RFU. The -48 Vdc supply is disconnected to pre-
vent arcing/surging during device disconnection/connection to
thereby ensure traffic on other ports is not affected.
IDQ Optimization Enables quiescent current (IDQ) optimization. If this is available, the
button is active as shown:
This button only displays for an ODU or IRU that has a GaN Power
Amplifier, currently all 6 GHz and 11 GHz, ODU 600, ODU 600T, and IRU
600 Eclipse devices. This button resets the IDQ on the PA to a value that
equates to optimum transmitted SNR.
Note that:
During the optimization process all traffic on the link is interrupted
for between 0.5 and 3 seconds.
This is only required when link SNR is found to be degraded under
normal path conditions. Check these values every quarter.
On a protected 1+1 or space diversity link the optimization process
must be performed separately on online and offline ODUs/IRUs.
When it is performed on an online ODU/IRU a protection
switch is forced.
It can be performed on the offline ODU/IRU without
impacting the online ODU/IRU.

Radio Protection
This screen supports the creation and configuration of protected radio interfaces. It allows
protection between ports on the same RACx2 module or between ports on separate RACx2
or RACx1 modules.
N O TE: Capac ity lic ens ing on a pr otec ted r adio link applies to the link -
s ee L ic ens e Management on page 61. When alloc ating c apac ity lic ens e to
a pr otec ted link, only the fir s t inter fac e (nor mally ODU1) is r equir ed to
be lic ens ed. Any c apac ity alloc ated to the s ec ond inter fac e w ill be
deduc ted fr om the available c apac ity lic ens e, but w ill not be us ed by the
pr otec ted link.
Radio protection rules are that:

l A RACx1 can only be protected with another RACx1.
l A RACx2 allows protection between interfaces on same RACx2 or between
interfaces on different another RACx2 modules.
o One protected instance can be enabled using ODU1 with ODU1, or ODU2 with
ODU2.
n The unused ODU interfaces on the RACx2 modules must also be
configured for protection, even though they are not used.
o Two protection instances can be enabled using ODU1 with ODU1, and ODU2
with ODU2.
n Each protected instance is unique - the radio parameters and protection
type (hot standby or space diversity) can be different for each.
l When protecting between two RAC modules (2x RACx1 or 2x RACx2), synchronous
mode (SyncE) must be configured on the protected interfaces (does not apply to
unused interfaces on a RACx2 pairing).
Procedure
l Go to Radio Configuration - Radio Protection.
l To add a new link for protection, click the Add button. A new row displays.
l Select the required protection values, then click Apply.
l Existing values can also be edited from this view.
l To remove a protected link, highlight the row and click Remove.

l Where the protection is between RACs, proceed to the Network Sync Source
screen to complete configuration of synchronous mode on the protected
interfaces.
o At one end of the protected link configure the protected radio interfaces for

ESMC Enabled using the Interface Synchronization settings. Do not set (Add)
these interfaces as a Network Sync Source. This establishes SyncE mode on
these interfaces with clocking from the internal (default) clock.
o At the other end of the protected link configure the protected radio interfaces
for ESMC Enabled using the Interface Synchronization settings (as above)
and set (Add) these interfaces as a Sync Source. This establishes SyncE
mode on these interfaces with clocking from the remote end via the local
protected radio interfaces.
Figure 42. Radio Link Protection
Table 28. Radio Link Protection Values
Item Value
Prot Interface Prot interface name.
Primary Interface Primary interface for the protected link.
Secondary Interface Secondary interface for the protected link.
Type Link Type.
Splitter Type Choose Equal or Unequal.
Primary Splitter Loss (dB) Enter the acceptable primary splitter loss value.
Secondary Splitter Loss Enter the acceptable primary splitter loss value.
(dB)
Revert Mode Choose to select a preference to return online Tx to the Primary
Interface. Tx switching is not hitless.
No Revert. The link will not revert to Primary Interface Tx.
Duration. The link will revert to Primary Interface Tx on
expiration of the Revert Duration timer.
Time of Day. The link will revert to Primary Interface Tx at the
assigned time of day PLUS the period entered into Revert
Duration.

Item Value
Revert Duration Duration range is 20 to 86400 seconds (24 hrs).
A revertive switch will occur if the primary Tx has been free
of the alarms that trigger a Tx switch, for the set duration.
Should an alarm occur during the Revert Duration period,
the timer will reset.
Revert Time of Day When Revert Time of Day is selected, this field and the Revert
Duration field are live for entering values.
A revertive switch will occur on time-out of the Time of Day
and Revert Duration timers.
On expiration of Time of Day, the Revert Duration timer is
engaged.
A revertive switch will occur on alarm-free expiry of the
Revert Duration period.
Should an alarm occur during the Revert Duration period,
the timer will reset.
Revert Timer Shows the countdown in seconds of the Revert Duration timer.

Radio Protection Diagnostics

This screen enables diagnostics on protected links. See Radio Protection on page 116
Procedure
l Go to Radio Configuration - Radio Protection Diagnostics.
l Select the required diagnostic(s) and duration, then click Apply.
l A duration time can be canceled at any time by clicking it to Off, then clicking
Apply.

Figure 43. Radio Link Diagnostics Protection
Table 29. Radio Link Diagnostics Values
Item Value
Protected Interface Name of protected interface.
Radio Interfaces Names of protected radio interfaces.
Locked Online Plugin Applies where the protection is set across two plug-ins.
Options are:
Slot
Duration (set days, hours, minutes)
Advanced: select Indefinite if required
Locked Receive Path Sets which of the two Rx paths to lock to. Options are:
Slot

Item Value
Locked Transmit Path Sets which of the two Tx paths to lock to. Options are:
Slot

NETWORK SYNCHRONIZATION CHAPTER 8
CONFIGURATION
Chapter 8. Network Synchronization Configuration

The Network Synchronization screens include the following:
l Network Synchronization - Network Clock on page 123
l Network Synchronization - Network Sync Source on page 127
l Interface Synchronization Configuration on page 129

CHAPTER 8 NETWORK SYNCHRONIZATION CONFIGURATION
Network Synchronization - Network

Clock
Network Synchronization functions provide a synchronization signal to CTR network
resources that may require this signal. The Network Clock supports configuration of the
network clock. This provides timing for data packet delivery.
N O TE: This func tion r equir es a Sync E lic ens e.
Procedure
l Click Network Synch Configuration > Network Clock to access the Network Clock
screen.
To clear values before applying, select an item and click Clear.

CONFIGURATION
Table 30. Global Network Clock Data

Equipment Clock Select the clock option from the available networked options. This is a
global setting - it applies to all SyncE enabled interfaces. The
selection must match that which has been enabled on the network.
Option 1 - Limits Rx Quality and Tx Quality options as shown in
Network Synchronization - Network Sync Source on page 127 to
the following options: QL-PRC, QL-SSU-A, QL-SSU-B, QL-SEC, and
QL-DNU.
Option 2 - Limits all Rx Quality and Tx Quality fields in Network
Synchronization - Network Sync Source on page 127 to the
following options: QL-PRS, QL-STU, QL-ST2, QL-TNC, QL-ST3E, QL-
ST3, QL-SMC, QL-ST4, QL-PROV, QL-DUS
Clock Mode Identifies the clock mode of the selected Equipment Clock.
Free Running - Clock is running without a network reference input.
Locked - Linked to, and controlled by, a network reference, and
locked to the values of that reference.
Holdover - Was linked to a network reference and has lost the link to
that reference: is using stored data from the reference to control its
time.
Free Run QL Select the quality level that will be transmitted when the clock is free-
running. The options available in the drop-down menu depends on
whether Option 1 or Option 2 is selected from the Equipment Clock
drop-down menu.
If Option 1 is selected, the following options are available: QL-PRC,
QL-SSUA, QL-SSUB, QL-SEC, and QL-DNU.
If Option 2 is selected, the following options are available: QL-PRS,
QL-STU, QL-ST2, QL-TNC, QL-ST3E, QL-ST3, QL-SMC, QL-ST4, QL-
PROV, and QL-DUS.
Handover QL Select the quality level that will be transmitted when the clock is in
the holdover state. The options available in the drop-down menu
depends on whether Option 1 or Option 2 is selected from the
Equipment Clock drop-down menu.
If Option 1 is selected, the following options are available: QL-PRC,
QL-SSUA, QL-SSUB, QL-SEC, and QL-DNU.
If Option 2 is selected, the following options are available: QL-PRS,
QL-STU, QL-ST2, QL-TNC, QL-ST3E, QL-ST3, QL-SMC, QL-ST4, QL-
PROV, and QL-DUS.
Holdoff Time Configures a global hold-off timer specifying the amount of time
that the CTR waits when a Synchronous Ethernet clock source
fails before taking action. If a clock source goes down, the CTR
waits for a specific hold-off time before removing the clock
source from the clock selection process. By default, the value of
hold-off time is 300 milliseconds (ms).


Wait to Restore Configures a global wait-to-restore timer for Synchronous Eth-
Time ernet clock sources. The timer specifies how long the CTR waits
before including a restored clock source in the clock selection pro-
cess. Valid values are 0 to 12 minutes. The default value is 5
minutes.
Switchover Mode The clock selection algorithm is restarted on a switchover. Dur-
ing switchover, the CTR goes into holdover mode. Switchover
can be configured in two modes: revertive and nonrevertive. In
revertive mode, the link switchover is triggered automatically
while in nonrevertive mode the link switchover should be
triggered manually by the user. The CTR goes into hold-over
mode during switchover and restarts clock selection when the
switchover is complete.
Enable PTP End-to- Enables the PTP Transparent Clock functionality on the device. This
End Transparent can then be enabled on any Ethernet or radio port via the Interface
Clock Synchronization page. A Transparent Clock is neither a master or
slave and will adjust every PTP event message with a calculated
residence time.
N O TE: This c hec k box is dis abled if
PTP Tr ans par ent Cloc k is not lic ens ed.
Table 31. System Clock Status Details
Data presented in this table reflects the selections made in the Network Sync Source Config
screen and current operational status.

Source Name Name of clock source
ESMC Capable Options are:
No SSM/ESMC
TxRx ESMC
Source State Displays source state.
Quality Level Active quality level, based on the quality settings enabled for the
Equipment Clock above.
Selected Src. Up Time Total time for which this clock has been live in days, hours,
minutes, and seconds.
Lock to Source Displays whether this clock is locked to its source.
Last Holdover Duration Duration in seconds of the most recent holdover.
(sec)
Current Holdover Duration in seconds of the current holdover.
Duration (sec)

CONFIGURATION

Changed QL Up Reports the number of times the T0 clock source has been
changed by the clock selection algorithm, to a clock source with
equal or greater QL than the previous clock source. Count is reset
upon system startup.
Changed QL Down Reports the number of times the T0 clock source has been
changed by the clock selection algorithm, to a clock source with
lesser QL than the previous clock source. Count is reset upon
system startup.

Network Synchronization - Network Sync

Source
The Network Sync Source screen enables users to set an interface as a synchronous source.
Note that the source must have synchronous mode enabled. Up to four sources can be
enabled.
Procedure
l Click Network Synch Configuration > Network Sync Source to access the Network
Sync Source screen.
l At least one source must be present to configure these values. Click Add to
create a new source.
To clear values before applying, select an item and click Clear. Values are
defined below.
Table 32. Network Synchronization Source Values

Network Synchronization Source Configuration
Status Current source status, available (green) or unavailable (red).
Port Port name / ID.
Priority Priority level, from 1 to 4.

CONFIGURATION
Synchronization Two sets of three options are available:

Mode For TDM ports:
No Synchronization
SSM Disabled - Disables the TDM Synchronous Messaging Channel.
SSM Enabled - Enables the TDM Synchronous Messaging Channel.
For Ethernet ports:
No Synchronization
ESMC Disabled - Disables the Ethernet Synchronous Messaging
Channel.
ESMC Enabled - Enables the Ethernet Synchronous Messaging Channel.
Source State Current state of the synchronization source. Oprions are:
Available
Not Available
Fail
Holdoff
Wait to Restore
Quality Level Rx Sets the configured received quality level. Received configured qual-
ity level is used in clock selection process if ESMC or SSM capability
are disabled for the source or diagnostic functionality is configured.
Operational Current transmitted clock quality level for the synchronization
Quality Level Tx source.
Operational Current received clock quality level for the synchronization source.
Quality Level Rx
Internal Quality Current internal received clock quality level for the synchronization
Level Rx source.
Wait to Restore The time remaining for this source if the source is in the 'wait-
torestore' state. This value is 0 if the source is not in the 'wait-
torestore' state.
Active Time The time this clock source has been the active clock source for the
node. Count is reset upon system startup.
Lock to Source Forces a switch to a clock source regardless of clock availability or quality.
Interface Synchronization
Port Port name of the synchronization source.
Source State Current state of the synchronization source.
Synchronization Three options are available:
Mode No Synchronization
ESMC Disabled - Disables the Ethernet Synchronous Messaging Channel.
ESMC Enabled - Enables the Ethernet Synchronous Messaging Channel.
Operational Current transmitted clock quality level for the synchronization
Quality Level Tx source.
Operational Current received clock quality level for the synchronization source.
Quality Level Rx

Interface Synchronization Configuration

The Interface Synchronization screen enables users to set an interface as a synchronous
source. Note that the source must have synchronous mode enabled.
l Thus screen reflects applicable settings made in the Network Synchronization -
Network Sync Source screen.
Procedure
l Click Network Synch Configuration > Interface Synchronization to access this
screen.
l The screen provides an interface view of the sync source settings made in the
Network Synchronization - Network Sync Source screen. Select the PTP Enable
check box for interfaces that are part of a Transparent Clock.
N O TE: Sync E mus t be enabled and pr oper ly c onfigur ed for PTP to oper ate
over a r adio inter fac e.
Figure 44. Interface Synchronization Configuration (CTR 8540)

CONFIGURATION
Figure 45. Interface Synchronization Configuration (CTR 8300v2)

TDM MANAGEMENT CHAPTER 9
Chapter 9. TDM Management

This section describes the TDM Management functions.
Topics include:
l Pseudowire on page 133
l Tributary Diagnostics on page 135

CHAPTER 9 TDM MANAGEMENT
Pseudowire
Via CTR Portal, you can configure E1 Pseudowire related parameters.
N O TE: This func tion r equir es a s pec ific lic ens e, and at leas t one TDM
bloc k lic ens e. See L ic ens e Management on page 61.
Prerequisite: SyncE Enabled

This function requires that SyncE has been enabled for the Pseudowire interface.
SeeNetwork Synchronization - Network Sync Source on page 127
Or, edit the SyncE source via the CLI commands as follows:
aos(config)# int ra 2/1
aos(config-if)# synchronous mode esmc-enabled
aos(config-if)# exit
See the CTR 8300/8540 CLI Command Guide for more details.
N O TE: STM SFP c annot be us ed as a s ync E s our c e.
Procedure
l Click TDM Management > Pseudowire to access the Pseudowire screen.
l The CTR may be configured as a clock generator to supply clock to externally
connected TDM devices. To configure the CTR as a clock output, select the
desired tributary from the TDM Clock Output drop-down menu, and click Apply.
N O TE: N O TE: This is only intended to be us ed in c as es w her e no
Ps eudow ir es ar e c onfigur ed but a r efer enc e c loc k is s till needed by
exter nal equipment.
l To create a new Pseduowire interface click Add. A data row is created that can
be configured by entering or selecting desired values.
l To configure these values, enter or select the desired values.
l Click Apply to apply these values to the system; click Clear to remove all
selected values from a row before applying. Click Remove to delete a selected
row of data. Values are defined below.

Figure 46. TDM - Pseudowire
Table 33. Pseudowire Values

Pseudowire Global Settings
Switch MAC Displays the MAC address of the CTR terminal.
Mode The TDM standard to configure: T1 - North America, E1 - Europe.
Recovery Select 25MHz - MEF8 standard, 125MHz -Increased accuracy mode.
Check Freq
TDM Clock Port to generate a T1 or E1 reference clock.
Output
Pseudowire Configuration
Port Select the port for the pseudowire.
(Pseudowire)
Type Displays the type of pseudowire. Currently only Metro Ethernet
Forum 8 pseudowires are supported.
Enable Select the check box to enable this pseudowire.
Description Enter a brief description as a reference.
Destination Enter the MAC destination address.
MAC Address
ECID Enter the number for the ECID. The ECID must be a unique number
per destination MAC Address.
VLAN Select the VLAN ID number for the associated VLAN.
Clock Recov- Select the clock recovery type: Differential or Adaptive.
ery
Jitter Buffer Enter a value in milliseconds for the jitter buffer.
Framing Configures the framing. Currently only E1 Unframed is supported.
Line Mode Select the line mode value from the drop-down options.
Line Settings Select the line setting value from the drop-down options.

CHAPTER 9 TDM MANAGEMENT
Tributary Diagnostics
This screen supports PRBS testing on an enabled T1/E1 interface.
N O TE: The built-in PRBS diagnos tic tes t func tion c an be enabled on
multiple tr ibs .
Procedure
l Go to TDM Configuration - Tributary Diagnostics.
l Configure the following values to view Tributary Diagnostics.
l Select a Trib (columns 1 - 16).
l To run a Link Test, select the ... button in the Tributary row. A pop-up displays,
prompting you to select:
l Direction of Line Facing or Radio Facing.
l Duration of the diagnostic test.
l Use Start and Stop buttons to start/stop/restart a test.
l Insert Error button - Inserts a Single Bit Error into the PRBS test for test
confirmation purposes.
l Line Facing Loopback - Sets a line facing loopback on the selected trib. Set days,
hours, and minutes.
l Radio Lacing Loopback - Sets a radio facing loopback on the selected trib. Set
days, hours, and minutes.
l Gen AIS - Sets AIS generation on the selected trib. Set days, hours, and minutes.
l Reset Stats button - Clears the stats back to zero on the selected column / trib

Figure 47. Tributary Diagnostics

STATISTICS CHAPTER 10
Chapter 10. Statistics

Statistics are provided on the following topics:
l Interface Statistics on page 139
l Quality of Service Statistics on page 140
l Radio Link History on page 144
l Radio G826 on page 142
l Radio Link History on page 144
l ARP Cache
l MAC Address Table on page 147
l Clear Statistics on page 148

CHAPTER 10 STATISTICS
Interface Statistics
This screen presents RMON interface stats for Ethernet and radio interfaces.
l Data is default presented in real-time with data accruing at nominal 3 second
intervals from the last bootup.
l A Captured option provides a facility to capture statistics for a user-required
period. Restarting the Captured option clears the previous capture.
l Using the Captured option does not interfere with the aggregation of real-time
statistics.
l Leaving this statistics screen will affect captured statistics: remain on this screen
while capturing data.
Procedure
l Go to Statistics - Interface Statistics. Select Real-Time or Captured. For
Captured, click Start Calculation. The data displays.
l The example below shows the initial rows of data. Scroll down in the screen to
view the full report.
l To export the data as a .CSV file, click Export.
Figure 48. Statistics - Interface

Quality of Service Statistics

This screen presents Quality of Service statistics for all Ethernet, L1LA, radio, port channel
and protection interfaces.
l Data is default presented in real-time with data accruing at nominal 3 second
statistics.
Procedure
l Go to Statistics - Quality of Service . Select Real-Time or Captured. For Captured,
click Start Calculation. The data displays.
Figure 49. Statistics - Quality of Service

Radio Link Performance

This screen presents radio link stats for radio link interfaces.
l Data is presented by default in real-time with data accruing at nominal 3 second
statistics.
Procedure
l Go to Statistics - Radio Link Performance . Select Real-Time or Captured. For
Captured, click Start Calculation. The data displays.
Figure 50. Radio Link Performance

Radio G826
This screen presents radio link stats for G826 data.
l Data is presented by default in real-time with data accruing at nominal 3 second
statistics.
Procedure
l Go to Statistics - Radio G826 . Select Real-Time or Captured. For Captured, click
Start Collection. The data displays.
Figure 51. Radio Link G826
Errored Blocks - Number of blocks of data where one or more bits of data are in error.

Errored Seconds - Number of one-second periods with one or more errored blocks or at
least one defect.
Errored Seconds Ratio - Ratio of errored seconds to available seconds
Severely Errored Seconds - Number of one-second periods which contain at least 30%
errored blocks or at least one defect.
Severely Errored Seconds Ratio - Ratio of severely errored seconds to available seconds
Background Block Errors - Number of errored blocks not occurring as part of an SES.
Background Block Errors Ratio - Ratio of background errored blocks to available seconds
Available Seconds Total - available time during the captured period (or since statistics reset
if real-time)
Unavailable Seconds Total - unavailable time during the captured period (or since statistics
reset if real-time)

Radio Link History

This screen presents radio link performance data for RACx2 and RACx1 links.
l Data capture options of Real-time, Quarter Hour, or Daily, are provided.
o Real-time data is captured into approximately 25 minutes worth of nominal 3
second bins.
o Under Quarter Hour data is captured into 7 days worth of 15 minute bins.
o Daily data is captured into one months worth of daily bins.
l Bin data retention is on a FIFO basis.
l Real-time data is captured by CTR Portal and is not retained once the user leaves
the page.
l Qhour and Daily data is captured by the device and is available at any time.
Procedure
l Go to Statistics - Radio Link History. Select the link to view, and the required
resolution: Real-time, Quarter Hour, or Daily. The data displays.
l The examples below show completed performance views.
Figure 52. Radio History
Item Description
1 Resolution selection: Real-time, Quarter Hour, or Daily
2 Complete history view. Up to 25 minutes (approx) of 3 second bins, one
weeks worth or 15 minute bins, or one month of daily bins.

Item Description
3 Set the range for the expanded view (4). Left-click and drag edges to
set. Once set the position of the 'box' can be reset by clicking within the
box and dragging. The default range for the expanded view is the same
as the complete-history view.
4 Expanded, higher-resolution view.
5 Click within the expanded view to select a bin time-slot. The data for this
bin is displayed below (6) & (7).
6 RSL and BER data. Max and Min display the max and min values within
the time slot. Mean represents the average value over the slot period.
7 G.826 statistics for the selected time slot.
Table 34. Display Values
Item Value
Current RSL Current operating Received Signal Level (RSL) in dBm.
RSL Mean Average of the Received Signal Level (RSL) in dBm.
RSL Max Maximum RSL during the selected date range.
RSL Min Minimum RSL during the selected date range.
Current BER Current Background Error Measurement during the selected
date range.
BER Mean Average of the Background Error Measurement during the
selected date range.
BER Max Maximum Background Error Measurement during the selected
date range.
BER Min Minimum Background Error Measurement during the selected
date range.
Errored Blocks A block of data where one or more bits of data are in error.
Available Seconds Total available time during the selected date range.
Unavailable Seconds Total unavailable time during the selected date range.
Errored Seconds A one-second period with one or more errored blocks or at least
one defect.
Severely Errored Seconds A one-second period which contains at least 30% errored
blocks or at least one defect.
Background Block Errors An errored block not occurring as part of an SES.

ARP Cache
To view this screen, go to Statistics - ARP Cache . It displays the Address Resolution Protocol
cache for the device.
To export the data as a .CSV file, click Export.
Figure 53. Statistics - ARP Cache

MAC Address Table

To view this screen, go to Statistics-MAC Address Table .
It displays MAC addresses, learnt or associated, against a VLAN. You can:
l Filter these by VLAN or Port
l Search for specific MAC addresses (full or partial: use the wildcard **; as
required)
l Turn automatic updating on/off by selecting the Update check box
Results are displayed at 100 to a page: at the bottom of the screen, you can navigate to
additional pages by clicking on the page numbers.
To export the data as a .CSV file, click Export.

Figure 54. Statistics - MAC Address Table

Clear Statistics
From this screen you can clear all or selected interface counters, and all or selected radio
history bins.
Procedure
l Go to Statistics - Clear Statistics.
l To clear interface statistics, go to Clear Interface Counters and select either All
or Interface. Then, click the Clear button for this selection.
l To clear radio history bins, go to Clear Radio History Bins and select from the
following:
l Radio Link - Select all or selected interface.
l G826/Rx - Select G826, Rx, or Both.
l Bin Type - Select the bin type: All, Real-time, Quarter
Hour, or Daily.
Then, click the Clear button for this selection.

l The affected counters/bins are set to zero, ready for new data capture.
Figure 55. Statistics - Clear Interface Statistics

ALARMS AND EVENTS CHAPTER 11
Chapter 11. Alarms and Events

This section lists alarms, events, and MIBs for CTR devices:
l CTR Device Alarms on page 151
l CTR Device Events on page 178

CHAPTER 11 ALARMS AND EVENTS
CTR Device Alarms

This section lists the CTR device alarms. Note the following:
l In the CLI view alarms may be referred to by their alarm number.
l Definitions for Security Type, Event Type, Severity, and Possible Causes generally
follow those specified by the ITU.
l Do not remove SD cards from units when the units are powered on.
l This section lists CTR alarms for both 8300 and 8540 devices. Some alarms do
not display for 8300: these are noted in the alarm description.
In this section, alarms are listed in alphabetical order:

l All interfaces in the layer 1 link aggregation group are down on page 152
l Attached RFU has a high transceiver temperature on page 153
l Attached outdoor unit (RFU) transmit power failure on page 153
l Bandwidth and/or standard settings are invalid on page 154
l Bit error rate (BER) threshold of 10^-6 has been exceeded on page 154
l The carrier-only diagnostic function has been enabled on page 154
l Configuration has been loaded from a source that is not the startup configuration
file on page 155
l Current configuration is not supported on page 155
l Diagnostic function is enabled for the specified E1/T1 on page 156
l Ethernet Port Link down on page 157
l Factory Mute Enabled on page 157
l Hardware has failed on page 157
l The IF loopback diagnostic function has been enabled on page 159
l Link status propagation active on page 159
l Loss of Signal on page 159
l MAC Address Conflict Detected on LILA Group on page 160
l Main power supply failure on page 160
l Manufacturing information is invalid on page 160
l Maximum modulation is invalid on page 161
l Modulation is invalid on page 162
l The modulation lock diagnostic function has been enabled on page 163
l Module is missing on page 161
l Module is not supported on page 162
l Network Synchronization functionality has one or more diagnostic features
enabled on page 167
l RFU not detected on page 169
l One or more interfaces assigned to the L1LA aggregation group are down on page

163
l The plugin-online lock diagnostic function has been enabled on page 165
l Plugin temperature has exceeded operational limits on page 163
l Plug-in has failed to supply power to a POE port on page 164
l Possible main power supply failure on page 164
l Radio traffic path has been lost in one or both directions on page 170
l Receive path has been lost on page 168
l Received Alarm Indication Signal on page 167
l Receiver frequency setting is invalid on page 168
l The RFU power supply diagnostic function has been enabled on page 169
l The rx-source lock diagnostic function has been enabled on page 169
l Secondary Power Failure on page 170
l Software synchronization with SD card failed on page 171
l SyncE enabled on non SyncE capable SFP Module on page 172
l Synchronization clock is not locked to source(s) with highest priority on page 171
l System Clock is in holdover on page 172
l The system clock setting is invalid on page 173
l System cooling degraded on page 173
l System cooling failed on page 173
l Transmit path has been lost on page 174
l Transmit power is invalid on page 174
l Transmitter frequency setting is invalid on page 175
l The transmitter lock diagnostic function has been enabled on page 175
l The transmitter mute diagnostic function has been enabled on page 175
l Valid SD card missing on page 176
All interfaces in the layer 1 link aggregation group are

down
Security Event: No
Event Type: Communications alarm
Severity:Critical
Possible Causes:
1 -Loss of signal on all interfaces in the layer 1 link aggregation group.

Cause - Loss of signal on all more interfaces assigned to the L1L aggregation group.

Remedy - Check the layer 1 link aggregation group configuration and connections for all
interfaces assigned to the group.
Application Invalid
Security Event: No
Event Type: Event Processing error
Severity: Critical
Possible Causes:
1 - Application Compromised
Cause - Software integrity check failed.
Remedy - Contact manufacturer for technical support.
Attached RFU has a high transceiver temperature

Security Event: No
Event Type: Equipment alarm
Severity: Major
Possible Causes:
1 - Attached RFU has a high transceiver temperature

Cause - Temperature unacceptable
Remedy - Check for related alarms. If the alarm persists, replace the RFU
Attached outdoor unit (RFU) transmit power failure

Security Event: No
Severity: Major
Possible Causes:
1 - Attached RFU transmit power failure

Cause - Transmit power problem
Remedy - Check RFU operation and replace if confirmed faulty

Bandwidth and/or standard settings are invalid

Security Event: No
Event Type: Operational violation
Severity: Critical
Possible Causes:
1 - Bandwidth and/or standard settings not supported

Cause - Config or customisation error
Remedy - Change the bandwidth and/or standard settings to supported values
Bit error rate (BER) threshold of 10^-6 has been

exceeded
Security Event: No
Severity: Warning
Possible Causes:
1 - Bit error rate (BER) threshold of 10^-6 has been exceeded

Cause - Path degradation due to signal fade (rain or multipath), equipment malfunction, or
signal interference
Remedy - Use the radio link performance and history screens, and check for other alarms
to determine the likely cause
The carrier-only diagnostic function has been enabled

Security Event: No
Event Type: Other
Severity: Warning
Possible Causes:
1 - The carrier-only diagnostic function has been enabled for this radio interface
Cause - Diagnostic enabled
Remedy - Disable diagnostic function

Current configuration is not supported

Security Event: No
Severity: Critical
Possible Causes:
1 - Configuration is mismatched between the near and far end radios

Remedy - Change the near and/or far end configurations so they match
Current Radio Protection Configuration Not Supported

Security Event: No
Event Type: Communications Alarm
Severity: Critical
Possible Causes:
1 - Protection configuration is invalid

Cause - Either protection is not configured, or the selected protection type is not compatible
with the attached RFU hardware.. Can also be a configuration or customisation error.
Remedy - Configure a radio protection type that is compatible with the attached hardware.
Configuration has been loaded from a source that is

not the startup configuration file
Security Event: No
Event Type: Processing error
Severity: Major
Possible Causes:
1 - A configuration revert snapshot was present at startup and was used as the con-
figuration source

Remedy - An attempt to reconfigure the unit was not completed successfully. Either the
configuration revert timer was left to expire following a configuration change/load, or the
unit was reset while the configuration timer was active. Attempt the configuration
change/load again, or save the running configuration (as loaded from the revert snapshot)
using the Save Configuration command.
2 - The startup configuration file was corrupt or missing, configuration was loaded
from the backup startup configuration file
Remedy - Load configuration from a configuration file that has been saved to your PC, or
reconfigure the unit manually. Once the unit is configured correctly, save the configuration
using the Save Configuration command
3 - The startup configuration file was corrupt or missing, factory default con-
figuration was loaded
Remedy - Load configuration from a configuration file, or reconfigure the unit manually.
Once the unit is configured correctly, save the configuration using the Save Configuration
command.
Diagnostic function is enabled for the specified E1/T1

Security Event: No
Event Type: Other
Severity: Warning
Possible Causes:
1 - The Radio-facing Loop-Back diagnostic function has been enabled for this E1/T1
Remedy - Disable diagnostic function(s)
2 - The Line-facing Loop-Back diagnostic function has been enabled for this E1/T1
3 - The Link-Test diagnostic function has been enabled for this E1/T1

4 - The Alarm Indication Signal (AIS) generation diagnostic function has been enabled
for this E1/T1
Ethernet Port Link down

Security Event: No
Severity: Major
Possible Causes:
1 - Loss of signal on interface

Cause - Loss of signal
Remedy - Check cable connection(s)
Factory Mute Enabled

Security Event: No
Event Type: Other
Severity: Warning
Possible Causes:
1 - Transmitter factory mute setting has been enabled for this radio interface.
Cause - As above.
Remedy - Disable the Factory Mute option.
Hardware has failed

Security Event: No
Severity: Critical
Possible Causes:
1 - Attached outdoor unit (ODU) hardware has failed

Cause - External equipment failure

Remedy - Replace ODU
2 - Hardware failure (IRU 600) of one or more fans

Cause - Cooling fan failure
Remedy - Replace fan unit as soon as possible
3 - Fans (IRU 600) are being serviced (cover removed)

Cause - Fan cover removed
Remedy - Finish servicing fan unit and replace cover
5 - Unit has no free space left

Cause - Storage capacity problem
Remedy - Replace CTR chassis
6 - Unit has a problem with it's internal storage

Cause - File system is corrupted
7 - Unit has opened to many files

Cause - Equipment malfunction
8 - Unit cpu is overloaded

Cause - CPU is overloaded
Remedy - Upgrade software or replace CTR chassis if not fixed
9 - Unit has a problem with it's internal storage

Cause - Storage capacity problem
10 - The SD card has been removed

Cause - SD card is missing
Remedy - Replace missing SD card
N O TE: All s oftw ar e is s tor ed on the SD c ar d. It is r ec ommended that you
do not ever r emove this c ar d w hile the unit is pow er ed on.

The IF loopback diagnostic function has been enabled

Security Event: No
Event Type: Other
Severity: Warning
Possible Causes:
1 - The IF loopback diagnostic function has been enabled for this radio interface
Link status propagation active

Security Event: No
Severity: Major
Possible Causes:
1 - Port on remote device is down

Cause - REMOTE NODE TRANSMISSION ERROR
Remedy - Check remote device for equipment failure
2 - Connectivity to remote device lost

Cause - Transmission error
Remedy - Check network path to remote device
Loss of Signal
Security Event: No
Severity: Critical
Possible Causes:
1 - Loss of signal on the interface

Cause - Loss of signal
Remedy - Check connection to far end equipment.

MAC Address Conflict Detected on LILA Group

Security Event: No
Event Type:Communications alarm
Severity: Major
Possible Causes:
1 - More than one Remote engine MAC address detected.

Cause - While the interfaces at this end of the link may all be in the same layer 1 aggregation
group, the remote interfaces may be members of different layer 1 aggregation groups. This
configuration error will result in this alarm.
Remedy - Configure channel interfaces at each end to belong to only one layer 1 link
aggregation group. Confirm at both ends of the link.
Main power supply failure

N O TE: This alar m is for the CTR 8540 only.
Security Event: No
Event Type:Equipment alarm
Severity: Critical
Possible Causes:
1 - Switched to backup power supply

Cause - Power supply failure
Manufacturing information is invalid

Security Event: No
Event Type: Other
Severity: Critical
Possible Causes:
1 - Failed to read manufacturing information because it is missing or corrupted

Cause - Equipment malfunction
Remedy - Replace the CTR

2 - Hardware version may not match the software version

Cause - Version mismatch
Remedy - Upgrade the software to a more recent version
Maximum modulation is invalid

Security Event: No
Severity: Critical
Possible Causes:
1 - Maximum modulation setting is invalid for the attached ODU

Remedy - Change the maximum modulation to a value supported by the attached ODU
2 - Maximum modulation setting is invalid for the selected bandwidth

Remedy - Change the maximum modulation to a value supported by the selected bandwidth
Module is missing
Security Event: No
Severity: Major
Possible Causes:
1 - SFP module is missing

Cause - Replaceable unit missing
Remedy - Insert the expected SFP module in the slot or shutdown the associated interface
2 - Plug-in module is missing

Remedy - Insert the expected plug-in module in the slot or configure the slot as empty

Module is not supported

Security Event: No
Severity: Warning
Possible Causes:
1 - Module is not supported in this slot

Cause - REPLACEABLE UNIT TYPE MISMATCH
Remedy - Insert the module in the correct slot
2 - Module incompatible
Remedy - Update hardware or software
3 - Unsupported SFP inserted

Remedy - Insert SFP with a supported part number
Modulation is invalid
Security Event: No
Severity: Critical
Possible Causes:
1 - Modulation setting is invalid for the attached ODU

Remedy - Change the modulation to a value supported by the attached ODU
2 - Modulation setting is invalid for the selected bandwidth

Remedy - Change the modulation to a value supported by the selected bandwidth
3 - Maximum modulation configured lower than base modulation

Remedy - Change the modulations so the maximum modulation is higher than the minimum
modulation

The modulation lock diagnostic function has been

enabled
Security Event: No
Event Type: Other
Severity: Warning
Possible Causes:
1 - The modulation lock diagnostic function has been enabled for this radio interface
One or more interfaces assigned to the L1LA

aggregation group are down
Security Event: No
Severity: Major
Possible Causes:

Cause - Loss of signal on one or more interfaces assigned to the L1LA aggregation group.
Remedy - Check connections for interfaces assigned to the group.
Plugin temperature has exceeded operational limits

Security Event: No
Severity: Critical
Possible Causes:
1 - Plugin too hot, powered down

Cause - Cooling failure

Remedy - Check for FAN unit alarm status, ambient temperature excessive, airflow
restrictions
Plug-in has failed to supply power to a POE port

Security Event: No
Severity: Critical
Possible Causes:
1 - Current draw is outside of acceptable range

Cause - Power demand of connected equipment is excessive
Remedy - Only use devices that are standards compliant with POE port
2 - POE equipment is too hot

Cause - Temperature unacceptable
Remedy - Check: fan tray alarms, ambient temperature excessive, cooling vents restricted
3 - Plug-in power supply failure

Remedy - Replace POE plug-in
4 - POE power supply time cutoff failure

Cause - In-rush (surge) current to connected device excessive
Remedy - Only use devices that are standards compliant with POE port
Possible main power supply failure

Security Event: No
Severity: Warning
Possible Causes:

Cause - Power problem

Remedy - Use the Sensors screen to check operation of the main power supply
The plugin-online lock diagnostic function has been

enabled
Security Event: No
Event Type: Other
Severity: Warning
Possible Causes:
1 - The plugin-online lock diagnostic function has been enabled for this protection
interface
Pseudowire Jitter Buffer Overrun

Security Event: No
Severity: Critical
Possible Causes:
1 - Jitter buffer overrun

Cause - The percentage of jitter buffer overruns persists above a defined level for
configurable period of time.
Remedy - Check the pseudowire connection.

Pseudowire Malformed Packets Received

Security Event: No
Severity: Critical
Possible Causes:
1 - Malformed frames
Cause - The percentage of malformed CSEoP frames persists above a defined level for
configurable period of time.
Pseudowire Missed Connection

Security Event: No
Severity: Critical
Possible Causes:
1 - Misconnection
Cause - The percentage of stray frames persists above a defined level for configurable
period of time.
Pseudowire Packets Lost

Security Event: No
Severity: Critical
Possible Causes:
1 - Loss of frames
Cause - The Frame Loss Ratio persists above a defined threshold for a configurable period
of time.

Pseudowire Packets Received Too Late

Security Event: No
Severity: Critical
Possible Causes:
1 - Late frames
Cause - The percentage of frames arriving too late to be played out exceeds a defined level
for a configurable period of time.
Network Synchronization functionality has one or

more diagnostic features enabled
Security Event: No
Event Type: Other
Severity: Warning
Possible Causes:
1 - Diagnostic functionality enabled

Received Alarm Indication Signal

Security Event: No
Severity: Major
Possible Causes:
1 - Reception of AIS signal on trib interface

Cause - AIS received
Remedy - Check status of connected equipment

2 - Far end equipment is detecting AIS in receive direction

Cause - AIS received over trib link
Remedy - a) Check if AIS is being passed through from the local end trib interface b) Check if
an AIS diagnostic has been set at the local end
Receive path has been lost

Security Event: No
Severity: Major
Possible Causes:
1 - Demodulator is not locked

Cause - Path loss (fade), or local end receive or far end transmit failures
Remedy - Check for related alarms to confirm cause and the action required
Receiver frequency setting is invalid

Security Event: No
Severity: Critical
Possible Causes:
1 - Receiver frequency setting is invalid for the attached ODU

Remedy - Change the receive frequency to a value supported by the attached ODU

The RFU power supply diagnostic function has been

enabled
Security Event: No
Event Type: Other
Severity: Warning
Possible Causes:
1 - The RFU power supply diagnostic function has been enabled for this radio inter-
face
RFU not detected

Security Event: No
Severity: Critical
Possible Causes:
1 - RFU not detected

Remedy - Replace RFU or restore connection to its RAC module
The rx-source lock diagnostic function has been

enabled
Security Event: No
Event Type: Other
Severity: Warning
Possible Causes:
1 - The rx-source lock diagnostic function has been enabled for this protection inter-
face

Radio traffic path has been lost in one or both

directions
Security Event: No
Severity: Critical
Possible Causes:
1 - Demodulator is not locked

Cause - Path loss (fade), or local end receive or far end transmit failures
Remedy - Check for related alarms
2 - Remote demodulator is not locked

Cause - Far end receiver failure or local end transmit failure
Remedy - Check for related local end and far end alarms to confirm cause and the action
required
Secondary Power Failure

Security Event: No
Severity: Major
Possible Causes:
1 - Backup power supply not detected

Remedy - Connect secondary power supply to power plug-in
2 - Voltage supplied is outside of acceptable range

Remedy - Correct secondary power supply attached to power plug-in
3 - Current draw is outside of acceptable range

Cause - Power problem on power plug-in or main chassis

Remedy - Replace power plug-in. If the alarm persists replace the chassis.
Software synchronization with SD card failed

Security Event: No
Severity: Critical
Possible Causes:
1 - A file system error occurred while attempting to sync

Cause - file error
Remedy - Load and activate a software pack to replace the failed system software
2 - A watchdog software revert has occurred, sync was not attempted

Cause - software error
Remedy - Load and activate a software pack to replace the failed system software
3 - The software contained on the SD card is incompatible with the hardware

Cause - An incorrect SD card has been detected
Remedy - Insert a compatible SD card
4 - SD card contains corrupt software

Cause - Data on the SD card has been corrupted
Remedy - Replace the SD card
Synchronization clock is not locked to source(s) with

highest priority
Security Event: No
Severity: Warning
Possible Causes:
1 - Synchronization signal on primary reference(s) is lost

Cause - Sync source mismatch
Remedy - Check signal integrity and clock quality levels on source(s) with highest priority

2 - Received clock quality on primary reference(s) too low

Cause - Sync source mismatch
Remedy - Check received source quality level on highest priority source(s)
SyncE enabled on non SyncE capable SFP Module

Security Event: No
Severity: Major
Possible Causes:
1 - Enabled SyncE on non SyncE capable SFP module

Cause - Replaceable unit type mismatch
Remedy - Insert the expected SFP module type (SyncE capable SFP module) in the slot or
disable synchronous mode on the interface
System Clock is in holdover

Security Event: No
Severity: Minor
Possible Causes:
1 - Synchronization signal was lost

Cause - Loss of sync
Remedy - Check signal integrity on all sources that are part of the clock selection process

The system clock setting is invalid

Security Event: No
Event Type: Processing error
Severity: Minor
Possible Causes:
1 - The date and time has not been set

Remedy - Set the system date and time to a valid value
2 - The date and time setting appears to be invalid

Remedy - Set the system date and time to a valid value
System cooling degraded

Security Event: No
Severity: Major
Possible Causes:
1 - Hardware failure of one fan

Cause - Cooling fan failure
Remedy - Change fan tray as soon as possible
System cooling failed


Security Event: No
Severity: Critical
Possible Causes:
1 - Hardware failure of multiple fans

Cause - Cooling fan failures
Remedy - Change fan tray immediately
2 - Fan tray missing

Remedy - Insert fan tray immediately
Transmit path has been lost

Security Event: No
Severity: Major
Possible Causes:
1 - Remote demodulator is not locked

Cause - Far end receiver failure or local end transmit failure
Remedy - Check for related local end and far end alarms to confirm cause and the action
required
Transmit power is invalid

Security Event: No
Severity: Critical
Possible Causes:
1 - Transmit power setting is invalid for the attached ODU

Remedy - Change the transmit power to a value supported by the attached ODU

Transmitter frequency setting is invalid

Security Event: No
Severity: Critical
Possible Causes:
1 - Transmitter frequency setting is invalid for the attached ODU

Remedy - Change the transmit frequency to a value supported by the attached ODU
The transmitter lock diagnostic function has been

enabled
Security Event: No
Event Type: Other
Severity: Warning
Possible Causes:
1 - The transmitter lock diagnostic function has been enabled for this protection inter-
face
The transmitter mute diagnostic function has been

enabled
Security Event: No
Event Type: Other
Severity: Warning
Possible Causes:
1 - The transmitter mute diagnostic function has been enabled for this radio interface
Remedy - Disable diagnostic function.

Valid SD card missing

Security Event: No
Event Type: Environment alarm
Severity: Critical
Possible Causes:
1 - No SD card detected
Cause - Missing card
Remedy - Insert valid SD card
2 - Invalid SD card detected

Cause - Incorrect or faulty card
Remedy - Insert valid SD card
XPD Output on BNC Diagnostic Enabled for this radio

Security Event: No
Event Type: Other
Severity: Warning
Possible Causes:
1 -Diagnostic is enabled
Cause - The XPD output on BNC diagnostic function has been enabled for this radio interface

XPIC settings are invalid

Security Event: No
Event Type: Environment alarm
Severity: Critical
Possible Causes:
1 - XPIC not supported

Cause - XPIC is not supported for the selected bandwidth and/or standard settings
Remedy - Disable XPIC or select a bandwidth and/or standard setting
which supports XPIC.
2 - XPIC enablement required

Cause - XPIC must be enabled for the selected bandwidth and/or standard settings.
Remedy - Enable XPIC or select a bandwidth and/or standard setting which
does not require XPIC.

CTR Device Events

This section lists informational and warning Events. These may appear in the Event Log on
page 40.
Some events are only for CTR 8540 devices. These events are noted.
The active software version has changed

Description: The active version of the software has changed, in response to a new software
load or a software reversion.
Severity: Informational
Recommended Action: None required.
The active software does not match the software on

the SD card. Software sync from the SD card started
N O TE: T h is even t is f or th e C T R 8540 on l y.
Description: The system has identified a discrepancy between the running software on the
device and the software on the SD card. It has begun to sync the software, using the SD card
as a source.
Severity: Warning
Recommended Action: Allow software sync to proceed.
Autonegotiation procedure failed

Description: An attempt to auto-negotiate speed and duplex for an interface has failed.
Severity: Warning
Recommended Action: Check that the remote end supports auto-negotiation.
Configuration download operation has failed

Description: An attempt to download a configuration file to the device has failed.
Severity: Error
Recommended Action: Check that the URI and filename were specified correctly. Try to ping
the remote device to verify connectivity. Check local IP interface and routing configuration.

Configuration download operation was successful

Description: A configuration file has been downloaded to the device successfully.
Configuration has been loaded successfully from the

startup configuration file
Description: The startup configuration file data has loaded successfully onto the device.
Configuration revert operation has failed

Description: An attempt to revert to an earlier system configuration has failed. This may be
caused by configuration file corruption or a process malfunction.
Severity: Error
Recommended Action: Check for related events. Recreate the configuration file and attempt
to repeat the operation.
Configuration save operation has failed

Description: An attempt to store the current device configuration to file has failed. This may
be caused by system corruption or problems with the file system.
Severity: Error
Recommended Action: Check for related events and attempt to repeat the operation. If the
problem persists, obtain a new SD card.
Configuration save operation was successful

Description: The current device configuration was successfully stored to file.

Connectivity with an SNTP server has been established

Description: The device has successfully contacted an SNTP server.
Device operating abnormally due to [text]

Description: The device is not functioning as expected due to the specified cause.
Severity: Warning
Recommended Action: Review cause of abnormality, look for related alarms and events, and
take appropriate action.
An ECFM defect has occurred

Description: An ECFM defect has occurred on the specified Maintenance Domain (MD),
Maintenance Association (MA) and Maintenance End Point (MEP).
Severity: Critical
Recommended Action: Check the specified defect and take appropriate action.
An error has occurred during software activation:

[text]
Description: A specific error has been identified during software activation.
Severity: Error
Recommended Action: Check the SD card for errors and attempt a software reload.
An error has occurred during software loading: [text]

Description: A specific error has been identified during software loading.
Severity: Error
An error has occurred during software rollback: [text]

Description: A specific error has been identified during software rollback.
Severity: Error

Failed to write license to SD card: [text]

Description: Details relating to licensed features could not be written to the SD card.
Severity: Warning
Recommended Action: Attempt to reinstall the license. Obtain a replacement SD card if the
problem persists.
Helpdesk file generation failed

Description: The Helpdesk file failed to generate.
Severity: Error
Recommended Action: Attempt to regenerate Helpdesk file.
Helpdesk file generation was successful

Description: The Helpdesk file was successfully generated.
Recommended Action: No Recommended Action required.
IDQ optimization started manually on radio interface

Description: IDQ optimisation started manually on radio interface.
Severity: The IDQ optimisation task was manually started on radio interface #/#
Recommended Action: No Recommended Action required.
Local configuration file(s) have been updated from the

SD card
N O TE: This event is for the CTR 8540 only.
Description: Local configuration files on flash have been updated from the SD card.

Management VLAN was changed from [value] to

[value]
Description: The management VLAN value has been changed as noted.
A neighbouring device has been lost on port [text]

Description: A neighbouring device discoveredusing LLDP has been disconnected on the
specified port.
Recommended Action: None
New neighbouring device discovered on port [text]

Description: A new neighbouring device broadcasting information using LLDP has been
discovered on the specified port.
Recommended Action: None
No response from the [text] SNTP server

Description: The specified SNTP server is not responding.
Severity: Warning
Recommended Action: Check the configured IP address for the SNTP server. Ping the SNTP
server IP address to see if it responds. Check all local IP interface and route configurations.
Protection plug-in online switch from [text] to [text]

due to [text]
Description: The active protected plugin has switched as noted.

Protection plugin switch blocked due to [text]

Description: An attempt to switch the online protected slot has failed for the specified
reason.
Severity: Warning
Recommended Action: Check the specified reason and take appropriate action.
Protection transmitter switch from [text] to [text] due

to [text]
Description: Protection transmitter switch values were changed as noted.
Protection transmitter switch blocked due to [text].

Description: An attempt to switch a protected transmitter over has failed for the specified
reason.
Severity: Warning
Recommended Action: Check the specified reason and take appropriate action.
Radio set to maximum power for over [value] minutes

Description: The radio has been transmitting at maximum power for an extended period of
time.
Severity: Warning
Recommended Actions: Check the power output and look for other alarms and events.
Radio set to maximum power for over [value]

minutes. Cooldown reducing power by [value].
[value]dBm
Description: The radio has been transmitting at maximum power for an excessive period of
time, and a cooldown cycle has commenced which will reduce power output.

Severity: Warning
Recommended Action: Check the power output configuration, and look for other alarms and
events.
Rx modulation was changed from [text] to [text]

Description: Rx modulation values were changed as noted.
The software has reverted to the inactive software

Description: The device software has reverted to a previous version due to a rollback
request, or an error condition.
Severity: Warning
Recommended Action: If the event was due to an error, check for related events and correct
any problems found, then attempt to reload and reactivate the most current software.
SFP module present but not configured: [text]

Description: An SFP module has been detected in the specified slot, but has not been
configured.
Recommended Action: Configure the slot to expect the SFP that is inserted, or remove the
SFP.
SFP module was extracted: [text]

Description: An SFP module was removed from the specified slot.
SFP module was inserted: [text]

Description: An SFP module was inserted in the specified slot.

Software load has started

Description: Software is being loaded onto the device.
Recommended Action: Do nothing with the device until the software load is complete.
The system date and time has been updated via SNTP
Description: The local device system date and time has been updated via SNTP.
System reset event occurred: [text].

Description: A system reset has occurred for the specified reason.
Tx modulation was changed from [text] to [text]

Description: Tx modulation values were changed as noted.
User has initiated a hard reset

Description: The user has done a hard reset/factory of the device, wiping data and reverting
to the default settings.
User has initiated a soft reset

Description: The user has carried out a soft reset of the device, wiping any unsaved
configuration changes.

Watchdog reset occurred

Description: An unrecoverable problem with the system was detected and a software reset
has occurred.
Severity: Warning
Recommended Action: Check other events for warnings and errors related to the reset.
A Y.1731 defect has occurred

Description: A Y.1731 defect has occurred on the specified Maintenance Entity Group (MEG),
Maintenance Entity (ME) and Maintenance End Point (MEP).
Severity: Critical
Recommended Action: Check the specified defect and take appropriate action.
MPLS traffic-engineering tunnel up

Description: A MPLS traffic-engineering tunnel has come up.
MPLS traffic-engineering tunnel down

Description: A MPLS traffic-engineering tunnel has gone down.
Severity: Error
Recommended Action: Ensure that a valid path is available in the traffic engineering
database.
MPLS traffic-engineering tunnel rerouted

Description: A MPLS traffic-engineering tunnel has been rerouted.
MPLS pseudowire (L2VPN) up

Description: A MPLS pseudowire (L2VPN) has come up.

MPLS pseudowire (L2VPN) down

Description: L2VPN down
Severity: Error
LDP neighbour up
Description: An LDP neighbour has come up.
LDP neighbour down

Description: An LDP neighbour has gone down.
Severity: Warning
Recommended Action: Ensure the LDP neighbour is still connected and configured correctly.
MPLS LSP up
Description: A MPLS LSP has come up.
MPLS LSP down

Description: An MPLS LSP has gone down.
Severity: Error
Recommended Action: Ensure the network path is still valid and available. For traffic-
engineering LSPs, ensure that enough bandwidth is allocated for the path.
BGP peer established

Description: A BGP peer connection has been established.

BGP peer state backwards transition occurred

Description: A BGP peer state backwards transition has occurred.
Severity: Error
Recommended Action: Ensure the peer is still connected and the peer configuration is
correct.

CTR PORTAL
Appendix A. Glossary
260-668241-001 JANUARY 2018 190

CTR PORTAL
Events
viewing 40
Expected plug-ins 34
Index F
Found plug-ins 34
A
I
adaptive modulation
Interface
guidelines 110
Statistics 139
Admin - Configuration 58
Admin - License Management 61 J
Admin - Script Loading 63
Admin - Software 55, 59 Javascript required 20
Alarms 151
viewing 37 L
ARP Cache 146
Layer 2 Port Manager
ATPC
available functions 65
adaptive modulation guidelines 110
License Management 61
settings 108
Link Aggregation 69
B Logging In 23
Backup Power 54 M
Browser Types 20
MAC Address Table 147
C N
CLI
Navigation
loading scripts from CTR Portal 63
menus 29
CLI script loading 63
Network Clock 123
Configuration Restore and Backup 58
Network Sync Sources 127
Connected Devices 51
Network Synchronization
CTR 8500
clock 123
introduction 18
sources 127
radio view 33
Web GUI Use Requirements 20 P
D Power over Ethernet 53
Power Settings
Date and time setting 45
Backup Power 54
E PoE Configuration 53
Pseudowire 133
Equipment view
default 33 Q
remote devices 33
Quality of Service
Event Log 40
Policing 91
260-668241-001 JANUARY 2018 192

Scheduling 94 T
Quality of Service - Classification 87
tacacs+
R tacacs 55
TACACS + 55
Radio Configuration Terminal Access Controller Access-Con-
overview 102
trol System 55
radio link configuration 103
trademarks iii
radio link diagnostics 114
radio link performance 144
Radio G826 Statistics 142 U
Radio Link Configuration 103
Radio Link Diagnostics 114 User Access 23
Radio Link History 144
V
Remote Devices
opening 33 VLAN
view information for 35 router VLAN configuration view 73
viewing 33 VLAN view screen 73
Reports
help desk reports 42
Revert Timer settings 58
Security
logging in 23
SerialNumbers 61
Software Status 55, 59
Software Upgrading 55, 59
Statistics
clear statistics 148
Interface 139
overview 138
Radio Link 141
Status
alarms view 37
equipment view 33
event log 40
System Information
location settings 45
overview 45
save status 45
time settings 45
values 45
System Performance
viewing 39
193 AVIAT NETWORKS

260-668241-001
WWW.AVIATNETWORKS.COM

CTR 8500-8300 3.5.20 CTR Portal - January2018

Uploaded by

Copyright:

Available Formats

CTR 8500-8300 3.5.20 CTR Portal - January2018

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CTR 8500-8300 3.5.20 CTR Portal - January2018

Uploaded by

Copyright:

Available Formats

CTR 8500-8300

Copyright & Terms of Use

Copyright © 2018 by Aviat Networks, Inc.

260-668241-001 JANUARY 2018 III

Aviat NetworksTechnical Support

Global Support Hotline: +1 210 526 6345

260-668241-001 JANUARY 2018 V

Sales and Sales Support:

Corporate Headquarters International Headquarters

Phone: + 1 408 941 7100 Phone: + 65 6496 0900

Product Compliance Notes

Regulatory Information for 5.8 GHz Band

260-668241-001 JANUARY 2018 VII

l FCC CFR47, Part 15.407 excludes the use of point-to-multipoint systems,

International Use of 5.8 GHz

Networking Devices in Electric Power Substations

VIII AVIAT NETWORKS

Declaration of Conformity, Radio Equipment Directive

Aviat Networks tímto prohlašuje, že tento ODU 600/ODU 600sp with

Undertegnede , Aviat Networks erklærer herved, at følgende udstyr

260-668241-001 JANUARY 2018 IX

Aviat Networks izjavlja, da je ta ODU 600/ODU 600sp with CTR 8311,

Aviat Networks týmto vyhlasuje, že ODU 600/ODU 600sp with CTR

Full declarations of conformity are available at:

Country Availability Matrix

260-668241-001 JANUARY 2018 XI

IT SHOULD BE NOTED THAT A LICENSE TO OPERATE THIS EQUIPMENT WILL BE

XII AVIAT NETWORKS

Copyright & Terms of Use iii

CHAPTER 1. INTRODUCTION TO CTR PORTAL 18

CHAPTER 2. NAVIGATION AND MENUS 22

CHAPTER 3. SYSTEM STATUS 32

CHAPTER 4. SYSTEM CONFIGURATION 44

260-668241-001 JANUARY 2018 XIII

CHAPTER 5. SWITCHING AND ROUTING CONFIGURATION 64

CHAPTER 7. RADIO CONFIGURATION 102

CHAPTER 8. NETWORK SYNCHRONIZATION CONFIGURATION122

XIV AVIAT NETWORKS

Network Synchronization - Network Sync Source 127

CHAPTER 9. TDM MANAGEMENT 132

CHAPTER 10. STATISTICS 138

CHAPTER 11. ALARMS AND EVENTS 150

260-668241-001 JANUARY 2018 XV

Possible main power supply failure 164

XVI AVIAT NETWORKS

An error has occurred during software rollback: [text] 180

APPENDIX A. GLOSSARY 190

260-668241-001 JANUARY 2018 XVII

Chapter 1. Introduction to CTR Portal

About CTR 8500 and CTR 8300

AVIAT NETWORKS JANUARY 2018 18

CLI or CTR Portal

19 JANUARY 2018 AVIAT NETWORKS

CTR Portal User Interface

Conventions and Terminology

WARNING: A warning item identifies a serious physical danger or major possible

AVIAT NETWORKS JANUARY 2018 20

21 JANUARY 2018 AVIAT NETWORKS

Chapter 2. Navigation and Menus