CTR 8540 - 8300 E0.3.4

CTR8540/8300 L2
INSTALLATION,
OPERATION AND
MAINTENANCE
AVIAT “NO PRODUCTION NETWORK ACCESS” POLICY
What does this mean?

• Any student that needs to perform job
While attending a training activities related to their production
session, Aviat Networks does not networks needs to perform those
allow any student to be logged while physically outside the training
room or labs.
into any network element or
system that is connected to a • No exceptions.
production network or carrying
production traffic. This is Why are we doing this?
applicable for all sessions • Network outages caused by students
conducted at Aviat training sites who were unknowingly performing
or at customer sites. training related tasks/changes on
production networks or systems due
to multi-tasking.
2 AVIAT NETWORKS
COURSE OBJECTIVES
AVIAT NETWORKS
OBJECTIVES
• Upon completion of this module, participants would be able to :

• Configure CTR 8540 and 8300 for initial operation, RF Link operation, and
Carrier Ethernet operation with both CLI and CTR Portal
• Perform detailed performance analysis of Radio and Ethernet links
• Perform advanced troubleshooting and maintenance techniques
4 AVIAT NETWORKS
COURSE AGENDA
1. Module 1 CTR 8540, 8300 System & RF Overview
2. Module 2 Basic Access and Network management
3. Module 3 Radio Link and ODU Configuration
4. Module 4 POE Configuration
5. Module 5 CTR Deployment Scenarios
6. Module 6 VLANs
7. Module 7 Ethernet QoS Configuration
8. Module 8 Layer 1 Link Aggregation
9. Module 9 Maintenance
10. Module 10 Diagnostics and Troubleshooting
11. Module 11 Synchronization
12. Module 12 E1 and T1 Pseudowires
5 AVIAT NETWORKS
Module 1
CTR 8540, 8312
System & RF Overview
AVIAT NETWORKS
SYSTEM FEATURES OVERVIEW
• Aviat Networks CTR (Converged Transport Router) 8540, 8300
Integrated Microwave Switch/Router
• Microwave transport options up to 80 GHz
• Advanced Carrier Ethernet features Including VLANs, QinQ,
QOS, OAM, ERP, Sync-E, and MEF-8 Pseudowires
• Nodal Operation supporting up to 8 microwave channels
• Adaptive Coding and Modulation with 1024 QAM
• Multi Channel Layer 1 and 2 Link Aggregation
7 AVIAT NETWORKS
CTR 8540/8300 ODU/ODR OUTDOOR RF OPTIONS
ODU/ODR ODU/ODR
Coax/Ethernet Coax/Ethernet
Cable Cable
CTR8312
CTR8540
8 AVIAT NETWORKS
CTR 8540 IRU 600 INDOOR RF OPTIONS
All Indoor IRU 600
Waveguide
Coax
Cable IRU600
CTR
9 AVIAT NETWORKS
NODAL ARCHITECTURE
• A Nodal System consists of a single Nodal Unit which is capable of interfacing with
multiple RF units and transporting on multiple RF channels
• TDM traffic is dropped/inserted or cross-connected at the site
• IP traffic can be switched or routed between links
• Multiple links over the same path may be used to aggregate Ethernet/IP
ODU/RFU 1 ODU/RFU 2
Link 2
Link 1
Nodal Terminal
10 AVIAT NETWORKS
SYSTEM HARDWARE ARCHITECTURE (CTR 8500)
• Aviat Networks CTR8540 Chassis consists of:
• Routing/Switching Engine
• 8 RJ-45 GigE interfaces + 4 SFP Slots
• 16 T1/E1 tributary interfaces
• 4 slots for various plug-in modules
• Slot for fan module
• Advanced Carrier Ethernet Features
• SD card for software images, configuration, and license keys
• Integrated Power Supply
11 AVIAT NETWORKS
CTR8540 CHASSIS OVERVIEW
1. Fan Module (mandatory)

2. RJ-45 V24 Maintenance Port
3. Status LEDS
4. Power Connector (-40 to -57 VDC)
5. Slot 1. PWR module (installed)
6. 8x Switch Ports
7. Slot 2. RACx2 module (installed) Fan Module
8. Slot 3. RACX2 module (installed)
12 AVIAT NETWORKS
CTR8540 CHASSIS OVERVIEW
9. 4x SFP Switch Ports

10. Protection Port
11. Diversity Port
12. Tributary Connectors
13. Tributary Connectors
14. Slot 4. PoEx2 module (installed)
13 AVIAT NETWORKS
CTR8540 PLUG IN CARDS
PWR MODULE
• Provides Redundant Power Supply (-40 to -57VDC input range)
• Must be installed in slot 1
• Protection is hitless
14 AVIAT NETWORKS
RACx1 and RACx2 Modules
• Provides one or two IF SMA ports for connection to Aviat Radios
• Supports Aviat ODU600, IRU600, and ODU300hp
• Supports modulation to 1024QAM
• Supports Hot Standby and Space Diversity
• Supports XPIC Co-Channel operation
• Supports L1 Link aggregation
• May be installed in any slot
15 AVIAT NETWORKS
POEx2 Module
• Provides two 65W POE++ ports
• Supports Aviat WTM3100, 3200, and 3300 series ODRs and compliant 3rd party devices
• 10/100/1000 Full Duplex
• May be installed in any slot
16 AVIAT NETWORKS
SYSTEM HARDWARE ARCHITECTURE (CTR 8300)
• Ultra-compact, ultra-powerful CTR 8300

microwave router
• >1 Gbit/s throughput in one tiny box Ultra-compact 1RU, ½ rack-width
• Advanced radio features, including Convection cooled – no fans
1024QAM ACM 1x or 2x IF options
• IF Interface Connections for up to 2x Compatible with Aviat ODU600,
split-mount ODUs or IRU 600 RFUs ODU600sp, IRU600 and ODU300hp
radios
• CTR 8311 – 1 IF interface
• CTR 8312 – 2 IF Interfaces
•Support for ODRs with external POE
injector
• Range of configuration options,
including 1+0, 1+1 HSB, HSB+SD,
2x(1+0) repeater & ring, 2+0
CCDP/XPIC
17 AVIAT NETWORKS
CTR 8300 CHARACTERISTICS
• Flexible interface options: 4x GE (SFP and Electrical); 16x T1/E1, Alarm I/O, and
Management
• TDM Pseudowire (MEF8) services
• Advanced Carrier Ethernet (L2) services: VLANs, STP/MSTP, LACP, ERP, OAM
• Synchronization options including T1/E1, IEEE 1588v2 and Synchronous Ethernet (SyncE)
• Ethernet and serial (console) management access
18 AVIAT NETWORKS
CTR 8300 FRONT PANEL
Alarm I/O
4 O/P & 2 I/P
Console port
1 x RJ-45 Serial &
1 x Micro USB
4 x Gigabit Ethernet ports

2 x Electrical & 2 x SFP
16 x TDM ports (T1 or E1)
IF connections for ODU/IRU (single IF as standard)
- 48VDC power
Mounting bracket with earth stud
19 AVIAT NETWORKS
LICENSING
• Capacity and Feature licensing provides access to extended CTR functionality
• License is based on the SD card’s serial number
• License is transferred to spare hardware via the SD card
• Licensing in field upgradable
• Capacity licensing in various increments of 50 - 2000mbps
• Feature License examples:
• Select Carrier Ethernet services
• 4 additional Electrical GigE ports (base includes 4)
• 4x SFP ports
• 8x or 16x T1/E1 tributaries
• ODU600 Flexible Power mode
• Adaptive Modulation
• L1 Link aggregation
• Payload encryption
SD Slot in back of CTR chassis
• Strong Security
20 AVIAT NETWORKS
RAC TO RFU COAX CONNECTION
• RACx1 and RACx2 SMA coax connectors
• Maximum cable length up to 300 Meters
• 311 MHz TX IF signal (RAC to RFU)
• 126 MHz RX IF signal (RFU to RAC)
• Pair of bi-directional telemetry signals for local
communication
• -48 VDC to power RFU
21 AVIAT NETWORKS
ODU600
• Supports all common 5 to 42 GHz frequency bands
• Flexible Power Mode (FPM) - base & high power
ODU600 operational modes in a single platform
• High Power Mode = 3dB increase in Power
• Supports QPSK to 1024QAM
• Supports Channel BW up to 80MHz
• Can be deployed in 1+0 unprotected, 1+1 MHSB,
1+1 SD, 1+1 FD, and 2+0 XPIC configurations
• Integrated Surge Suppressor
5 to 42 GHz • Over air compatibility with ODU 300hp and

QPSK to1024 QAM IRU600
• 5 GHz model has an N-Type antenna interface
22 AVIAT NETWORKS
IRU 600 V3 INDOOR RF UNIT
• CTR 8540 support for L6, U6, and 11GHz ANSI frequency bands
• Standard and High power modes from same RFU with software/license control
• Receives all power via the IF cable
• 1 RU module, 2 RU chassis
• Wideband transceiver with Tx High & Tx Lo operation set via software
• Four cooling fans with temperature dependent speed
• ACU contains Custom Tuned Diplexer (TX and RX Filters)
• Operating frequency range is defined by the transceiver module but limited by the TX
and RX filters in the ACU
23 AVIAT NETWORKS
ODU600T
• Modified ODU 600 with TX/RX filters
ODU600T and Circulator removed.
• Dedicated TX and RX coaxial
connectors
• Mounts to an Outdoor Branching Unit
(OBU)
• OBU contains filters and circulators
• Various Co-polar and Dual-Polar
options
• Supports Space Diversity
• Available in 5, L6. U6, 7, 8, and 11
GHz bands
24 AVIAT NETWORKS
ODU PROTECTION
ODU Coupler Unit (OCU)
• Used for single-antenna hot-standby &
frequency diversity links
• Direct mounting of ODUs
• Mounts directly to antenna
• Equal Loss 3.5 / 3.5 dB splitter
• Un-Equal Loss 1.5 / 6.5 dB splitter
• Splitter losses effect both Tx and Rx
• Also used for 2+0 co-polar arrangements
25 AVIAT NETWORKS
OUTDOOR BRANCHING UNIT (OBU)
• Used for Trunking Radio Configurations
where multiple RF channels are
combined onto one antenna and radio
Path
• Interfaces for up to 4 ODU600T
• Waterproof compartment contains
Filters and Branching connections
• Filters are custom Tuned
• Options for:
• 4+0 single Polarization
• Any combination up to 4 dual polarization
• 8+0 Dual Polarization with 2 OBUs
• Space Diversity
26 AVIAT NETWORKS
ODU PART NUMBERS
• ODUs are frequency band specific, but capacity independent within the band
• ODUs are fixed for TX low or TX high operation
• ODUs are sub-banded by their internal diplexers
Example ODU Part Numbers and description (See ODU600 Tuning Guide)
Lower 6 GHz - 252 MHz T-R Split - ANSI - Wideband Diplexer
EEH-06-A252-011 ODU 600, ANSI, 06GHz,T-R 0252MHz, 5930-6020MHz, TX LOW
EEH-06-A252-012 ODU 600, ANSI, 06GHz,T-R 0252MHz, 6182-6273MHz, TX HIGH
27 AVIAT NETWORKS
ODU 600
• Compact design for
reduced footprint*:
• 5kg
• 265mm x 265mm
x 125mm
• 0.009 m3
• Low DC power
consumption
(< 40 W)
• -33 to + 55°C
operating
temperature range
* Specifications shown for 13-

38GHz ODU600
28 AVIAT NETWORKS
ODU 600 POLARIZATION
29 AVIAT NETWORKS
ODU/IRU Features
• Synthesized Local Oscillators for software controlled

frequency settings
• Internal Detector for automatic level control and monitoring
Transmit Power levels
• RSSI port for antenna alignment
RSSI Measurement
VDC 0.25 0.5 0.75 1.0 1.25 1.5 1.75 2.0 2.25 2.5
RSL -10 -20 -30 -40 -50 -60 -70 -80 -90 -100
30 AVIAT NETWORKS
MULTIPLE MW CHANNELS ON THE SAME PATH 2+0
V V V
V
H H
Multiple Channel Alternate Channel Co-Channel

Single Polarization Alternate Polarization Dual Polarization
RACx2 or 2 x RACx1 RACx2 or 2 x RACx1 RACx2 with XPIC
31 AVIAT NETWORKS
MODULATION, CAPACITY AND SYSTEM GAIN
TX Power: 30dBm, 1W • System Gain – Difference between Max
Power and RX Threshold
0dBm, 1mw • Fade Margin – Difference between RSL

and RX Threshold
RX Overload: -22dBm
System
Gain • Capacity – Total amount of data throughput
Normal RSL: -40dBm • Low level modulation (QPSK)

Fade • High System Gain/Low Capacity
Margin
• High level modulation (1024 QAM)
RX Threshold -70dBm
• High Capacity/Low System Gain
Example Specifications
32 AVIAT NETWORKS
EXAMPLE CAPACITY AND SYSTEM GAIN SPECIFICATIONS
Modulation Scheme Airlink Capacity Max Transmit Power 10-6 RX Threshold

QPSK 39 mbps 32 dBm -88.75 dBm
16 QAM 90 mbps 31.5 dBm -82.00 dBm
32 QAM 108 mbps 31.5 dBm -79.00 dBm
64 QAM 135 mbps 31.5dBm -76.25 dBm
128 QAM 155 mbps 31 dBm -73.75 dBm
256 QAM 180 mbps 31 dBm -70.50 dBm
512QAM 210 mbps 29 dBm -66.50 dBm
1024 QAM HG 230 mbps 28 dBm -63.00 dBm
Specifications for ODU 600, High Power, L6 GHz, 30MHz BW (ANSI)

(Subject to change, check latest data sheets for actual specifications)
33 AVIAT NETWORKS
EXAMPLE CAPACITY AND SYSTEM GAIN SPECIFICATIONS
Modulation Scheme Airlink Capacity Max Transmit Power 10-6 RX Threshold

QPSK 38 mbps 32 dBm -89.00 dBm
16 QAM 73 mbps 31 dBm -83.50 dBm
32 QAM 112 mbps 30.5 dBm -78.00 dBm
64 QAM 121 mbps 29.5dBm -77.00 dBm
128 QAM 158 mbps 29 dBm -73.00 dBm
256 QAM 181 mbps 28 dBm -69.75 dBm
512QAM 203 mbps 27.5 dBm -66.75 dBm
1024 QAM HG 212 mbps 27dBm -63.75dBm
Specifications for ODU 600, High Power, 7GHz, 28MHz BW (ETSI)

(Subject to change, check latest data sheets for actual specifications)
34 AVIAT NETWORKS
ADAPTIVE CODING AND MODULATION
35 AVIAT NETWORKS
Module 2
BASIC ACCESS AND
NETWORK MANAGEMENT
AVIAT NETWORKS
FIRST TIME CONNECTION TO THE CTR
• Full CTR configuration is supported under CLI where two

management connection options are supported:
• Serial connection to V.24 front panel port
• Telnet to front panel switch port 1 (Default Ethernet Management Port)
• Basic CTR configuration is also supported using the CTR
Portal Web Browser through the Ethernet management port
Switch port 1 for telnet connection

(CLI) or web interface
connection(GUI)
V.24 front panel for
serial connection
37 AVIAT NETWORKS
SERIAL CONNECTION
V.24 front panel for

serial connection
(serial port pin-out is
identical to Eclipse)
• Connect PC serial port to CTR Maintenance V.24 port

using the DB-9/RJ45 adapter, included in the CTR
package, and a straight Ethernet cable
• A USB to Serial adapter is required if the PC does not
have a built in serial port
• CRT 8312 also has a Micro USB port for a direct USB
serial connection
38 AVIAT NETWORKS
CLI SERIAL CONNECTION
• Use a Terminal Emulation

program such as Hyper Terminal,
Putty, or Tera Term
• Settings are:
Baud Rate 115200
8 Data Bits
No Parity
1 Stop Bit
No Flow Control
Using Tera Term as the serial

connection to login to the CTR8540
39 AVIAT NETWORKS
CONNECTION VIA IP FOR TELNET OR CTR PORTAL

connection(GUI)
• Connect PC Ethernet port to switch port 1 of the CTR8540

and 8311/12 for telnet or CTR Portal connection
• Default IP address and subnet mask:
• IP address: 192.168.1.1
• Subnet Mask: 255.255.255.0
• PC must be in the same subnet as the CTR8540
40 AVIAT NETWORKS
CONNECTION VIA IP FOR TELNET OR CTR PORTAL

connection(GUI)
• The default login for the CTR8540 and 8311/12:

• Username: root
• Password: admin123
• The default Management VLAN is VLAN 2
• The default IP address and management VLAN can only be
changed via the CLI on SW version 2.5 and earlier
41 AVIAT NETWORKS
DEFAULT SETTINGS VIA CLI
• By default VLAN 2 is used for management and is assigned to interface
Gigabit Ethernet “Gi 0/1”
• To show the current management vlan and port, type the following command:
Action Command Remark
Show management config aos# show management Will show the Management Vlan
and the port associated to this
Vlan
• Result
--------------------------------------------------------
Current Management VLAN = 2
--------------------------------------------------------
Member Ports : Port Type
--------------------------------------------------------
Gi0/1 : out-of-band
42 AVIAT NETWORKS
DEFAULT SETTINGS VIA CLI
• To show the current management VLAN 2 and its IP

address run the following command
Show management IP aos# show running-config This will show you the CTR IP
address interface vlan 2 address and subnet mask
• Result
#Building configuration...
interface vlan 2
ip address 192.168.1.1 255.255.255.0
!
• Note: In a working network the management Vlan can be different than the default one
43 AVIAT NETWORKS
SCRIPT LOADING
• In addition to configuration via entering individual CLI commands,
configuration can be done by loading scripts
• Scripts are simply individual lines of code (CLI commands) that
are pasted into the terminal Emulation program
• Scripts are typically stored as text files
• Script text files can also be uploaded via the GUI, CTR Portal
Example scripts in the training material will be shown in a light green box
# example script for IP address change#
Configure terminal
interface vlan 2
ip address 10.20.1.101 255.255.255.0
end
44 AVIAT NETWORKS
CHANGING MANAGEMENT IP ADDRESS
• Commands to change the management IP address:

Configuration mode aos# configure terminal
Connecting to the Vlan interface aos(config)# interface vlan 2 Connecting to the
management Vlan interface
Changing the IP address and aos(config-if)# ip address Mask must be set as :
subnet mask <ip address> <mask> 255.xxx.xxx.xxx
Exiting configuration mode aos(config-if)# end Exit configuration mode
45 AVIAT NETWORKS
CHANGING MANAGEMENT IP ADDRESS
EXAMPLE
• aos# configure terminal
• aos(config)# interface vlan 2
• aos(config-if)# ip address 192.168.1.101 255.255.255.0
• aos(config-if)# end
# script for IP address change#

Configure terminal
interface vlan 2
ip address 192.168.1.101 255.255.255.0
end Value to change according
need
46 AVIAT NETWORKS
CHANGING MANAGEMENT ACCESS
• Management access can be changed:
Management VLAN
Management Port
Management Address
• As an example, we will change:

• Management port to port Gi 0/4
• Management VLAN ID to 20
• Management IP address to 10.10.1.10 255.255.255.0
• This example is Out-Of-Band management where the

management interface is not connected to the microwave
channel or any other trunk ports
47 AVIAT NETWORKS
• Step 1: Remove VLAN 2 (default vlan) from Management

Enter Config mode aos# configure terminal
Go to VLAN config mode aos (config)# vlan 2 Go to existing VLAN 2
configuration mode
Remove VLAN from aos (config-vlan)# no management Remove VLAN 2 from
Management Management group
exit aos (config-vlan)# exit Exit VLAN 2 configuration mode
• This configuration must be done only when connected with the serial port otherwise you will loose the
connection to the switch
48 AVIAT NETWORKS
• Step 2: Remove Interface VLAN 2

Go to int VLAN 2 Config aos (config)# interface vlan 2 Go to existing INT VLAN 2
Mode configuration Mode
Shutdown Int VLAN 2 aos (config-if)#shutdown Shutdown Interface VLAN 2
Exit aos (config-if)# exit Exit Interface VLAN 2

configuration mode
Remove VLAN interface aos (config)# no int vlan 2 Remove interface VLAN 2
49 AVIAT NETWORKS
• Step 3: Add VLAN 20, Add Interface VLAN 20 IP Address
Create VLAN 20 aos (config)#vlan 20 Create VLAN 20 and go to
VLAN 20 configuration mode
Add Ports aos (config-vlan)#ports gi 0/4 untagged Add port GI 0/4 and an
gi 0/4 untagged interface
exit aos (config-vlan)#exit Exit VLAN 20 Configuration

mode
Int VLAN 20 aos (config)#int vlan 20 Enter Interface VLAN 20
Configuration mode
IP Address aos (config-if)#ip address 10.10.1.10 Configure an IP address for
255.255.255.0 int VLAN 20
Enable port aos (config-if)# no shut Enable int gi 0/4
exit aos (config-if)#exit Exit int vlan 20 config mode
50 AVIAT NETWORKS
• Step 4: Set up Physical interface (GI 0/4)
Enter Interface aos (config)# interface gi 0/4 GI 0/4 Config Mode
configuration mode
Give the interface a aos (config-if)# description Name int Gi 0/4 MGMT_Port
description (name) MGMT_Port
Enable switchport PVID aos (config-if)#switchport pvid Tag incoming frames with PVID 20
tagging 20
Set Switchport accectable aos (config)# switchport Set untagged and priority tagged as the
frame type acceptable-frame-type acceptable frame type for incoming frames
untaggedAndPrioritytagged
Enable the port aos (config)# no shutdown Enable interface Gi 0/4
Leave interface config aos (config)# exit Exit int config mode
mode
51 AVIAT NETWORKS
CHANGING MANAGEMENT ACCESS (SCRIPT)
Configure terminal
vlan 2
No management
exit
Interface vlan 2
Shutdown
exit
No interface vlan 2
vlan 20
ports gi 0/4 untagged gi 0/4
exit
interface vlan 20
ip address 10.10.1.10 255.255.255.0
no shut
exit
interface gi 0/4
description MGMT_Port
switchport pvid 20
switchport acceptable-frame-type untaggedAndPrioritytagged
no shut Value to change according to
exit individual site
52 AVIAT NETWORKS
ADDING A STATIC ROUTE OR DEFAULT GATEWAY
• An IP route may be needed to reach the management network
• Configured as the management routers interface IP address:

Config mode aos# configure terminal
Adding static route aos(config)# ip route <network> The gateway must be the
<mask> <gateway> router port ip address
Getting out config mode aos(config-if)# end
• IP 0.0.0.0 and subnet 0.0.0.0 are used to set a default gateway for management
For Example:
aos(config)# ip route 0.0.0.0 0.0.0.0 192.168.100.1
53 AVIAT NETWORKS
IN BAND MANAGEMENT
• In cases where management is required to be passed over the
microwave channel, simply add the radio interface to the
management VLAN as tagged (default)

Enter the global configuration aos# configure terminal
mode
Enter the vlan Interface aos(config)# vlan 20 (interface <vlan number>)
configuration mode
Add the vlan interface to the radio aos(config-vlan)# ports add ra This command adds int VLAN 20
channel 3/1 to the radio channel ra 3/1
Exit config mode aos(config-vlan)# end
To show management status aos# show management
54 AVIAT NETWORKS
SAVING CONFIGURATION
• All modification to the configuration made via the CLI are made
to the running-config file. The modified configuration is active
as soon as changes are made and are updated in the running-
config file.
• However, the running-config file in NVRAM is not updated, so
if the router were to reboot, the old, non-modified configuration
would replace it
• The command ‘copy running-config startup-config’ or ‘write
startup-config’ will save the configuration in the RAM to
configuration in the NVRAM
aos# copy running-config startup-config (short command : aos# c r s)
or
aos# write startup-config (short command : aos# w s)
or
aos(config)# config save
55 AVIAT NETWORKS
CTR8540 USER MANAGEMENT
mode
Set the username and privilege aos(config)# username engineer The privilege is from 1 – 15 with
and type enter to be prompted for password privilege 15 15 being the highest.
the password password: <enter password> The privilege applies restriction to
the user for accessing the CLI
commands. For example, a user
id configured with privilege level
as four can access only the
commands having privilege id
less than or equal to 4
End to go to Privilege EXEC aos(config)# end
56 AVIAT NETWORKS
SNMP CONFIGURATION FOR PROVISION NMS
• Run the following commands. In this example the read community string is public and
the write community string is private
• Optional is the addition of a username and password to be used by ProVision
aos# configure terminal

aos(config)# snmp-server view all 1 included
aos(config)# snmp-server community public version both read all notify all
aos(config)# snmp-server community private version both read all write all
notify all
aos(config)# logging <SNMP Server address>
aos(config)# w s
############
Optional
aos(config)# username provision password privilege 15
Password:
• The default logging port is 514, for both CTR and Provision
57 AVIAT NETWORKS
OTHER USEFUL COMMANDS
Commands Description
aos# show interface status Shows the status of the interfaces
aos# show history Shows the recently typed commands
aos# show running-config Displays the configuration file

aos# show vlan Displays VLAN and the member ports
aos# copy running-config startup-config Saves the running configuration
aos# configure terminal Goes into the global configuration mode
aos# exit Goes back one context

aos# end Goes back to privileged EXEC mode aos#
aos# locateme (or no locateme) Flashes the Aviat Logo on the CTR Chassis
? or help Provides help or guideline to configuration steps
58 AVIAT NETWORKS
RESETING THE CONFIGURATION TO FACTORY DEFAULT
• Resetting the configuration to factory

default deletes the configuration files and
reloads the CTR with the factory default
configuration.
> revert-timer
The revert-timer command takes a snapshot of the current configuration and set the configuration
revert timer. If the revert timer expires, the CSR software will be reset and its configuration will be
reverted to this snapshot. The user will then be able to permanently save the snapshot, or load a
different configuration file.
The intent of this command is to prevent losing access to the CSR while performing configuration
changes that may cause loss of connectivity. Starting the revert-timer before changing any
configuration that may affect access to unit is recommended.
59 AVIAT NETWORKS
RESETING THE CONFIGURATION TO FACTORY
It is necessary to set the revert-timer to be able to reset the configuration to
factory default. The switch will not accept the factory reset command if a revert-timer
is not configured.
• To revert to the out-of-box default factory settings:

aos(config)# config load factory-defaults revert-timer <seconds>
• The system will reboot with a default configuration file.

If satisfied with the result, the revert-timer should be cancelled otherwise after its expiration
the configuration will be reverted to the last saved one.
• To cancel the revert timer.

aos(config)# no revert-timer
60 AVIAT NETWORKS
LAB SESSION 1 (SEE LAB WORKBOOK)
61 AVIAT NETWORKS
Module 3
RADIO AND ODU
CONFIGURATION
AVIAT NETWORKS
RAC AND ODU CONFIGURATION
• CTR Portal supports limited configuration, and can be used to:
Load SW, license, and configuration files
Configure a radio/link
Set plug-in slots
Configure switch-port basic settings
Set local date and time
View/access alarms, diagnostics, performance, events, statistics
Configure L1LA
Configure Synchronous Mode
Configure VLANs
Configure QoS
63 AVIAT NETWORKS
CONNECTION TO CTR VIA THE CTR PORTAL
Set the CTR IP

address
Login and password

for the CTR
Default
Login: root
Password: admin123
64 AVIAT NETWORKS
RADIO CONFIGURATION VIA CTR PORTAL
• The CTR is logged in via switch port 1 using the
default IP and login details.
• The Status/Equipment view is the default view
and indicates the status of the equipment before
configuration
65 AVIAT NETWORKS
• To configure the radio link, the slot that houses the RAC card has
to be activated
• right click on the slot and set the slot, or all slots, to the detected
plugin type
66 AVIAT NETWORKS
• To configure the Radio Link, right click on the detected plugin slot and
click on ‘Configure Radio Links’
• For ease of configuration, Aviat recommends using CTR Portal for radio
link configuration
67 AVIAT NETWORKS
RAC AND ODU CONFIGURATION VIA CTR PORTAL
Select the interface

you want to configure
Interface activation
Radio link parameters
XPIC setting is greyed

out when not
supported
68 AVIAT NETWORKS
Radio link parameters
RSL and SNR direct

reading from the radio
69 AVIAT NETWORKS
• Clicking on the Clear function will

just erase the latest modifications
that have not been applied yet
(equivalent to refresh on Eclipse)
• Clicking on Apply will save the

changes in the active
configuration
• Don’t forget to click on save when

the configuration is completed,
this action will save the config in
the start up configuration
(Equivalent to “Write to Start-up”
in CLI mode
70 AVIAT NETWORKS
RADIO CONFIGURATION VIA CLI
Configure the card type to the aos(config)# slot 3 RACx2 Slot 3 will now expect a
slot RACx2
Select the interface on the RAC aos(config)# interface radio 3/1 Slot Number/IF Port Number
Configure an Interface aos(config-radio)# description Give the interface a

description <SITEA-SITEB_NEMSID> description (Name)
Configure regulatory standard aos(config-radio)# bandwidth Set the radio bandwidth to
and bandwidth ansi 30 ANSI standard, 30 MHz
Configure the modulation aos(config-radio)# modulation Set the modulation to

acm base qpsk max 1024qam-hg adaptive mode with base and
mask none max mod, no mask
71 AVIAT NETWORKS
RADIO CONFIGURATION VIA CLI (CONT)
Configure allocated licensed aos(config-radio)# capacity max Max automatically allocates
capacity to use on the link maximum available capacity
Configure Transmit and Receive aos(config-radio)# frequency In MHz
Frequency transmit <TX FREQ> receive <RX
FREQ>
Activate of the high power mode aos(config-radio)# high-power Activates the high power
option for the radio (must be
licensed) (+3db boost)
Activate and Configure ATPC aos(config-radio)# atpc power Min xx: minimum power
min <Min> max <Max> Max xx: max power
fademargin <TFM> Fademargin xx: target remote
fade margin
activation of the FCC aos(config-radio)# atpc fcc- Set when coordinated power
compliance feature compliant is less than Max power
Remove factory mute aos(config-radio)# no factory- One time factory mute on
mute initial confuguration
72 AVIAT NETWORKS
RADIO CONFIGURATION VIA CLI (CONT)
Enable ingress filtering on radio aos(config-radio)# switchport
Ethernet interface ingress filter
Set ingress filtering to Tagged aos(config-radio)# switchport
only acceptable-frame-type tagged
Enable Radio Ethernet interface aos(config-radio)# no shut Port is default disabled
Exit Configuration mode aos(config-radio)# end Configuration is completed
Save the config to the start-up aos# w s
73 AVIAT NETWORKS
RADIO CONFIGURATION VIA CLI MODE
# Example script for configuring a radio link#
configure terminal
slot 3 RACx2
System mtu 2100
interface radio 3/1
description SITEA-SITEB
bandwidth ansi 30
modulation acm base qpsk max 1024qam-hg mask None
Value to change according to
capacity max need
frequency transmit 11015 receive 11505 Some more commands may be
high-power added or changed according to
atpc power min 20 max 30 fademargin 10.0
the configuration required
no atpc fcc-compliant
no factory-mute
switchport ingress-filter
switchport acceptable-frame-type tagged
no shut
exit
ws
74 AVIAT NETWORKS
USEFUL CLI COMMANDS
Checking the link config aos# show radio link interface ra 3/1 Checking the radio link
configuration configuration
aos# show radio link interface rad 3/1
Reported Status
---------------
Radio Link 1/3/1 Up
TX Power: 11.9 dBm
RSL: -50.0 dBm
Configuration [Capabilities]
----------------------------
Factory Mute: Disabled
ATPC: Enabled
TX Power: 12.0 - 20.0 dBm
[12.0 - 32.0 dBm, Minimum Step: 0.1 dBm]
High Power License: Enabled
ATPC Target Fade Margin: 10.0 dBm
Modulation Type: ACM1024
Licensed Capacity: 500Mbps
TX Frequency: 7361.000 MHz
[7358.500 - 7363.500 MHz, Minimum Step: 0.031250 MHz]
RX Frequency: 7200.000 MHz
[7197.500 - 7202.500 MHz, Minimum Step: 0.031250 MHz]
Channel Bandwidth: 55.000 MHz ETSI
[Maximum: 56.000 MHz]
Selected Modulations: 16QAM, 32QAM, 64QAM, 128QAM, 256QAM, 512QAM, 1024QAM-HG
[Maximum: 1024QAM]
Modulation Mask: 16QAM
XPIC: Disabled
aos#
75 AVIAT NETWORKS
RADIO LINK PROTECTION
• The CTR8540 and 8312 supports 2 modes of Protection:

HSB (Hot StandBy)
• Protection against equipment failure
SD (Space Diversity) – in this mode, the CTR8540 combines

the Hot Standby and Space Diversity modes respectively
• Protection against equipment failure and propagation issues
76 AVIAT NETWORKS
RADIO LINK PROTECTION SET-UP VIA CTR PORTAL
Select the Radio Click Add to add a new

Protection from Menu protection instance
77 AVIAT NETWORKS
Select with the

dropdown menu the
secondary interface
Select with the

Chose an ID number dropdown menu the
and should be unique primary interface
per protection (1 to 4)
• Note: Care should be taken when selecting the primary interface, as the configuration of the primary
will be copied to the secondary
• Often protection is configured before radio link configuration
78 AVIAT NETWORKS
Enter the Configuration

Splitter Loss of the Revert
Mode & Timer
Select the protection

type
If using a Coupler, select the
Splitter Type
• When the configuration is completed click

Apply and don’t forget to Save at the end
79 AVIAT NETWORKS
• After validating the link protection you must come back in the Radio link menu to re-enable the
interface (Now the interface does not appear as a radio link but as Protected interface 1)
The link is in Protected
mode but the interface
is Down
Interface must be re-

enabled
Link protected and UP
80 AVIAT NETWORKS
RADIO PROTECTION CONFIGURATION VIA CLI
Configure the protection aos(config)# set prot 1 type hot- Up to 4 instances
instance, type, and interfaces standby primary 3/1 secondary Intra and inter RAC
3/2 supported
Enter interface configuration aos(config)# int prot 1 Now called prot 1
mode
Enable Interface aos(config-prot)# no shutdown Default Disabled

Exit config mode aos(config-prot)#exit
Save the configuration aos# w s
81 AVIAT NETWORKS
SYNCHRONOUS MODE FOR PROTECTED INTERFACES
• Enable synchronous mode on prot 1 - synchronous mode is
required on the protected interfaces:
• At the master end (which can be either end):
aos(config)# int prot 1
aos(config-prot)# synchronous mode esmc-enabled
aos(config-prot)# exit
• At the remote end:
aos(config)# int prot 1
aos(config-prot)# synchronous mode esmc-enabled
aos(config-prot)# exit
aos(config)# network-clock input-source 1 int prot 1
aos(config)# network-clock wait-to-restore 0
aos(config)# network-clock hold-off 1800
aos(config)# end
82
AVIAT NETWORKS
RADIO PROTECTION CONFIGURATION VIA CLI
# Example script for setting protection#

Configure terminal
set prot 1 type hot-standby primary 3/1 secondary 3/2
interface radio 3/1
no shutdown
end Value to change according to
ws need
Some more commands may be
added or changed according to
the configuration required
83 AVIAT NETWORKS
USEFUL CLI COMMANDS
Checking the protection config aos# show prot interface prot 1 Checking the protection
configuration
aos# show prot interface prot 1

Interface: prot 1
Status: Active
Protection type: Hot standby
Primary interface: Ra1/3/1 (Tx Online)
Secondary interface: Ra1/3/2
Tx switch guard timer: Inactive
Revert mode: No revert
aos#
84 AVIAT NETWORKS
85 AVIAT NETWORKS
Module 4
PoE CONFIGURATION
AVIAT NETWORKS
POE CONFIGURATION
POEx2 Module
• Provides two 65W POE+ ports
• Supports Aviat WTM3xxx series ODRs and compliant 3rd party devices
• Provides two 10/100/1000 Full Duplex ports
• May be installed in any slots 1 – 4 of the CTR8540
• Two configuration options are possible

1. Using GUI
2. Using CLI
Note: POE card ports can be used as switch ports if more ports are required on the chassis
87 AVIAT NETWORKS
POE CONFIGURATION VIA GUI
In the tree menu or from the main

screen right click on the slot and select
“configure PoE”
88 AVIAT NETWORKS
POE CONFIGURATION VIA GUI
• The PoE is configured to deliver power to the All-outdoor IP radios
(WTM3100/3200/3300 or any third party all outdoor IP radios).
Two power modes are available

Auto
• The maximum power must be
defined and the status and class
is automatically generated.
Never
• No DC power is sent to the
ODR. In this case the port is
used a normal switch port
Note: The unit of power set here is in Milliwatts

89 AVIAT NETWORKS
ACTIVATING POE PORTS
• To activate the ports on the PoE
card, scroll to Ethernet
Configuration > Port Manager >
Enable PoE ports.
• In this screen shot the PoE ports
are in Gi2/1 and Gi2/2, this
means that the card is in slot 2
and there are 2 PoE ports for
each card that can be activated
90 AVIAT NETWORKS
POE CONFIGURATION VIA CLI MODE
Setting the POE to provide DC power to the ODR
Checking the card slot aos# show slot Showing the plugin inserted
in slots
Config mode aos#!
Interface activation aos(config)# slot 1/2 poex2 Enabling the interface
Selecting the interface aos(config)# interface Connecting to the interface
gigabitethernet 2/1 on the POE card
Mapping the interface to the aos(config-int)# map switch Mapping the interface to the
switch default switch
Configuring the bandwidth aos(config-int)# no shut Activating the interface
Configuring the power on the aos(config-int)# power inline auto Setting up the power to be
interface max 55000 delivered on the interface
Saving the config to the start-up aos# w s
91 AVIAT NETWORKS
Setting the POE to use ports as switch port only
Checking the card slot aos# show slot Showing the plugin inserted
in slots
Config mode aos#!
Interface activation aos(config)# slot 1/2 poex2 Enabling the interface
Selecting the interface aos(config)# interface Connecting to the interface
gigabitethernet 2/1 on the POE card
Mapping the interface to the aos(config-int)# map switch Mapping the interface to the
switch default switch
Configuring the bandwidth aos(config-int)# no shut Activating the interface
No PoE over the port aos(config-int)# power inline Not activation the PoE on the
never port
Saving the config to the start-up aos# w s
92 AVIAT NETWORKS
Script to activate the power on PoE slot 2 port 1
# script for configuring the PoE#

!
Slot 1/2 poex2
interface gigabitethernet 2/1
no shutdown
map switch default Value to change according to
power inline auto max 55000 need
end
ws
Script if PoE slot 2 port 1 is used as switch port only
# script for configuring the PoE#
!
Slot 1/2 poex2
interface gigabitethernet 2/1
no shutdown
map switch default
power inline never
end
ws
93 AVIAT NETWORKS
POE USEFUL CLI COMMANDS
• To view the slot status via CLI:
• Command
aos# show slot
• Result
aos# show slot
Slot 1
Expected module: None
Detected module: PWR - Secondary Power Supply
Warning, slot may be configured incorrectly.
Slot 2
Expected module: POEx2 - Dual Power over Ethernet
Detected module: POEx2 - Dual Power over Ethernet
interface gi 2/1
interface gi 2/2
Slot 3
Expected module: RACx2 - Dual Radio Access
Detected module: RACx2 - Dual Radio Access
interface radio 3/1
interface radio 3/2
Slot 4
Expected module: None
Detected module: None
94 AVIAT NETWORKS
• To view the PoE via CLI:

• Command
aos# show power inline
• Result
Interface Admin Status Class Power Max (Watts)

--------- ------ ----------------- -------- -----------------
Gi2/1 auto delivering power Class 4 55.000
Gi2/2 never disabled n/a n/a
95 AVIAT NETWORKS
• To view the port status:
• Command
aos# show interfaces status
• Result
Port Status Duplex Speed Negotiation Capability
---- ------ ------ ----- ----------- ----------
Gi0/1 connected Full 100 Mbps Auto Auto-MDIX on
Gi0/2 not connected - - Auto Auto-MDIX on
Gi2/1 connected Full 1 Gbps Auto Auto-MDIX on
Tx Cap Max Cap
Port Status (Mbps) (Mbps) Protection
---- ------ ------- ------- ----------
Ra3/1 - - - Prot1: Pri
Ra3/2 - - - Prot1: Sec
Prot1 up 435.6 435.6
96 AVIAT NETWORKS
Module 5
CTR8540/8300
DEPLOYMENT
SCENARIOS
AVIAT NETWORKS
AVIAT BACKHAUL SOLUTIONS
ODU 600
ODU 600
PRE- AGGREGATION
6-42 GHz
ODU 600
CTR 8540
WTM 3300
WTM 3300
WTM 3300
WTM 3200 WTM 3200
6-42 GHz 70/80 GHz
70/80 GHz
WTM 3200
MACRO-CELL SMALL-CELL
98 AVIAT NETWORKS
CTR 8500 PRIMARY APPLICATIONS (MOBILE EXAMPLE)
EDGE
CTR 8540 serves as an access
device at the edge of the ACCESS PRE-AGGREGATION
microwave or fiber network
Carrier Ethernet & MPLS
AGGREGATION
NODAL CTR 8540 serves to aggregate
CTR 8540 serves a dual role: downstream sites and provides typically
both an edge access device redundant upstream trunking
and a repeater/trunking node
99 AVIAT NETWORKS
ACCESS PRE-AGGREGATION
8540 NODAL APPLICATION
Carrier Ethernet &

MPLS
1-2 IF ports
1-2 IF ports
1-2 Microwave Radios

(Downstream) Microwave Radio
CTR 8540 with optional
Edge Cell Site Access
protection
• TDM (upstream)
• Ethernet
Access:
Ethernet Ports: 6+
E1/T1 Ports: 4-8
Same as
Ethernet Ports: 6+ Trunking:
previous ‘Edge’
application
E1/T1 Ports: 4-8 IF Ports: 2-4
100 AVIAT NETWORKS

1+0 NON- PROTECT
101 AVIAT NETWORKS

1+1 HOT-STANDBY (INTRA RAC)
102 AVIAT NETWORKS

1+1 HOT-STANDBY (INTER RAC)
103 AVIAT NETWORKS

1+1 INTER RAC REPEATER
104 AVIAT NETWORKS

2+0 AND 4+0 SOLUTIONS (XPIC AND NON-XPIC)
105 AVIAT NETWORKS

106 AVIAT NETWORKS

Module 6
VLANs
AVIAT NETWORKS
VLAN PROTOCOL DESCRIPTION
• Virtual LAN (VLAN) technology logically segments the shared
media LAN, forming virtual workgroups
VLANs offer a number of advantages over traditional LANs,
they are:
Performance
Formation of Virtual Workgroups
Simplified Administration
Reduced Cost
Security
• CTR 8540/8300 Supports two bridging modes: Customer Bridge Mode

and Provider Edge Bridge Mode
• Customer Bridge Mode is the default Mode
108 AVIAT NETWORKS
VLAN TAGGING
Untagged Ethernet MAC MAC
EtherType Payload FCS
frame DA SA
802.1Q tagged frame MAC MAC

C-Tag EtherType Payload FCS
DA SA
TPID (Tag Protocol Identifier) =
4 Bytes total PC 0x8100
TPID CFI VID PCP (Priority Code Point) = 0 – 7
P
VID (VLAN Identifier) = 0 - 40951
802.1ad tagged MAC MAC S- C-

EtherType Payload FCS
(Q in Q) frame DA SA Tag2 Tag3
4 Bytes total PC TPID (Tag Protocol Identifier) =

TPID CFI VID 0x88a8
P
1A frame tagged with VID = 0 is regarded as “priority-tagged”; it does not belong to a VLAN and the C-
Tag or S-Tag only specifies a QoS priority via PCP element
2 Interchangeably referred to as Service Tag, Provider Tag, PE (Provider Equipment) Tag, or Outer Tag
3 Interchangeably referred to as Customer Tag, CE (Customer Equipment) Tag, or Inner Tag
109 AVIAT NETWORKS

CUSTOMER BRIDGE MODE PORT BASED VLANS
• The CTR can be designed to support port based VLANs
Port must be associated to a VLAN
Untagged traffic ingressing the CTR ports will be tagged with
the port VID and traffic egressing those ports will have their
tag stripped (removed)
The radio ports may be set up as tagged and will retain the
switchport generated PVID over the link
In the case of out-of-band management, the radio ports will
exclude the management VLAN
• Note: On CTR the default VLAN - VLAN 1 – cannot be deleted

from the switch but may be excluded from ports
110 AVIAT NETWORKS
SCENARIO – UNTAGGED TRAFFIC ARRIVING TO THE CTR
•Trunk Ports
Transport one or more VLANs between switches/routers (VLAN pass-through)
Frames are tagged
VLAN 300
VLAN 200
• Access Ports
• Provide connectivity to
a single user VLAN
• Frames ingressing or
egressing the port are
untagged.
111 AVIAT NETWORKS

SCENARIO – VLAN TAGGING AND TRUNKING
mode
Create the VLAN and enter VLAN aos(config)# vlan 200 In this case the VLAN is created
configuration mode because it wasn’t previously
configured
Add member ports to the VLAN aos(config-vlan)# ports gi 0/2 Ports by default are added as
untagged gi 0/2 tagged ports. For a port to be an
aos(config-vlan)# ports ra 2/1 untagged port the untagged
command must be added at the
end of the command. Untagged
Ports will have thier VLAN Tag
stripped (removed) at Egress.
Exit from the VLAN configuration aos(config-vlan)# exit Exit VLAN Configuration Mode
mode
112 AVIAT NETWORKS

Create another VLAN aos(config)# vlan 300
Add member ports to new VLAN aos(config-vlan)# ports add gi Ports by default are added as
0/3 untagged gi 0/3 tagged ports. For a port to be an
aos(config-vlan)# ports add ra untagged port the untagged
2/1 command must be added at the
end of the command. Untagged
Ports will have thier VLAN Tag
stripped (removed) at Egress.
Exit from the VLAN configuration aos(config-vlan)# exit Exit VLAN Configuration Mode
mode
113 AVIAT NETWORKS

Enter the interface configuration aos(config)# int gi 0/2
mode for port gi 0/2
Configure the frame type of the aos(config-if)# switchport This ensures that only untagged
port as untagged/priority tagged acceptable-frame-type frames are received on port gi 0/2
Configure the PVID that is to be aos(config-if)# switchport pvid The switch will VLAN TAG all
assigned to untagged/priority- 200 untagged frames ingressing this
tagged frames port with the PVID
Enable the port aos(config-if)# no shutdown Enables Interface
Exit to go to Privileged EXEC aos(config-if)# exit Exit interface Configuration Mode
mode
114 AVIAT NETWORKS

Configure the frame type of the aos(config-if)# switchport This ensures that only untagged
port as untagged/priority tagged acceptable-frame-type frames are received on port gi 0/3
Configure the PVID that is to be aos(config-if)# switchport pvid The switch will VLAN TAG all
assigned to untagged/priority- 300 untagged frames ingressing this
tagged frames port with the PVID
Exit to go to Privileged EXEC aos(config-if)# end End Configuration Mode
mode
Save the configuration to startup- aos# w s Save configuration to startup-
config config
115 AVIAT NETWORKS

116 AVIAT NETWORKS

CUSTOMER BRIDGE MODE VLAN BRIDGING
CTR CUSTOMER VLAN BRIDGING
• In this mode, ports that receive or transmit frames for a customer are
configured as CUSTOMER BRIDGE PORTS
• Customer VLANs are transported using their original tags
• Ingressing frames (tagged with customer VLAN IDs) are passed-through
• Customer VLAN tags are configured in the service provider network
• Radio Interfaces are configured as tagged and retain the customer VLAN
across the link
• Customer VLANs can also be configured to pass between two ports and
not over the radio link
Untagged traffic can be configured to be dropped at ingress or

tagged with the Port VID
117 AVIAT NETWORKS
SCENARIO – TAGGED TRAFFIC ARRIVING TO THE CTR
•Tagged Ports
Transport one or more Pre-tagged VLANs between switches/routers (VLAN pass-through)
Frames are tagged
VLAN 200
VLAN 300
VLAN 200
VLAN 200
VLAN 300
118 AVIAT NETWORKS

mode
Create the VLAN and enter the aos(config)# vlan 200
VLAN configuration mode
Add tagged member ports to aos(config-vlan)# ports add gi Because both ports are going to
VLAN 0/2 ra 2/1 be tagged (default) ports, they
can be configured on the same
line
Exit from the VLAN configuration aos(config-vlan)# exit
mode
119 AVIAT NETWORKS

Create the VLAN and enter the aos(config)# vlan 300
VLAN configuration mode
Add tagged member ports to aos(config-vlan)# ports add gi Because both ports are going to
VLAN 0/2 gi 0/3 be tagged (default) ports, they
can be configured on the same
line
mode
120 AVIAT NETWORKS

Configure the frame type of the aos(config-if)# switchport This ensures that only tagged
port as untagged/priority tagged acceptable-frame-type tagged frames are allowed to ingress port
gi 0/2
Exit to go to Privileged EXEC aos(config-if)# exit
mode
121 AVIAT NETWORKS

gi 0/2
Exit to go to Privileged EXEC aos(config-if)# exit
mode
122 AVIAT NETWORKS

Enter the interface configuration aos(config)# int ra 2/1
gi 0/3
Enable the Interface aos(config-if)# no shutdown Enables Interface
Exit aos(config-if)# exit
Enter VLAN 1 Config Mode aos(config-if)# VLAN 1 Optional Remove ports from
VLAN 1
Remove VLAN 1 ports aos(config-vlan)# no ports Remove all ports from VLAN 1
aos(config-if)# end
Save the configuration aos# w s
123 AVIAT NETWORKS

CONFIGURATION (SCRIPT)
Configure terminal
vlan 200
ports add gi 0/2 ra 2/1
exit
vlan 300
ports add gi 0/2 gi 0/3
exit
int gi 0/2 Value to change according to
need
no shut
exit
Some more commands may be
int gi 0/3 added or changed according to
switchport acceptable-frame-type tagged the configuration required
no shut
exit
int ra 2/1
no shut
vlan 1
no ports
end
ws
124 AVIAT NETWORKS

VLAN USEFUL CLI COMMANDS
• To delete a Vlan via CLI: • To view one interface status via CLI:
• Command • Command
aos# show interfaces gi 0/2
aos# config
Aos(config)# no vlan 100 • Result
--------------- Gi0/2 up, line protocol is down (not connect)
• To see total number of Vlan Vlan via CLI: Bridge Port Type: Customer Bridge Port
• Command Interface SubType: gigabitEthernet

aos# show vlan summary Interface Alias: Slot0/2
• Result
Switch default Hardware Address is 00:e0:e2:76:aa:23
MTU 1500 bytes, Full duplex, 1 Gbps, Auto-Negotiation
HOL Block Prevention disabled.
Number of vlans : 4 CPU Controlled Learning disabled.
--------------- Auto-MDIX on
Input flow-control is off,output flow-control is off
Link Up/Down Trap is enabled
Reception Counters
Octets :0
Unicast Packets :0
NonUnicast Packets :0
Discarded Packets :0
Error Packets :0
Unknown Protocol :0
Transmission Counters
Octets :0
Unicast Packets :0
NonUnicast Packets :0
Discarded Packets :0
125 AVIAT NETWORKS
CUSTOMER BRIDGE MODE TRANSPARENT MODE
TRANSPARENT BRIDGE MODE
• Operates through a port membership configuration on a customer
bridge that ensures tagged and untagged traffic is forwarded without
modification
• Creation of VLAN 4094 to which all ports are added as untagged. All
ports are set for a PVID of 4094 so that all untagged frames are
internally tagged as VLAN 4094 at ingress, and stripped at egress, to
provide transparent communication
• The adding of all ports to VLAN 1 as tagged. As all port members
belong to VLAN 1 they are included in the same broadcast group and
VLAN tags are ignored. Hence, communication between the ports is
'transparent' - all tagged frames received on one member port are
forwarded to all other member ports of VLAN 1
• Enable Command: aos(config)# set transparent enable (or disable)
126 AVIAT NETWORKS

VLANS WITH CTR PORTAL
• VLAN Screen – Add New or Edit Existing VLANs
127 AVIAT NETWORKS

VLANS WITH CTR PORTAL
• VLAN by Interface
Configuration
• View or configure
various VLAN
Parameters per
interface
• Add existing
VLANs to an
interface with the
Membership
button
128 AVIAT NETWORKS

129 AVIAT NETWORKS

PROVIDER EDGE MODE
AVIAT NETWORKS
PROVIDER-EDGE BRIDGING – Q-IN-Q/IEEE 802.1AD
• Warning - Changing bridge modes resets VLAN configuration.
You will lose remote and local management. Connectivity can
only be re-established via the serial port of the CTR
• Later SW versions allow for setting Provider Edge Mode with
CTR Portal, where the Management configuration is
automatically restored
• The default mode is customer bridge and this has no support for
S-Tags (Q in Q).
• If you think you’ll need Q-in-Q in the future, make sure you pick
provider edge mode right from the beginning
131 AVIAT NETWORKS

PROVIDER-EDGE BRIDGING – Q-IN-Q/IEEE 802.1AD
802.1ad is the standardized version of Q in Q
CTR currently only supports provider-edge mode.
The CLI command to enable this mode:
aos(config)# bridge-mode provider-edge
• Provider-edge bridges allow transparent communication between customer networks across
provider networks
• Each port is configured for a specific role that determines the type of frame expected on that
port.
E.g. untagged, C Tagged, or S Tagged.
• Frames entering and exiting the CTR at the customer facing ports of a provider-edge bridge are
generally expected to be C Tagged (0x8100) or Untagged.
• Frames entering and exiting the CTR at the provider facing ports of a provider-edge bridge are
always S Tagged (0x88A8)
132 AVIAT NETWORKS

PROVIDER-EDGE MODE
Like two switches in one. A provider bridge and an edge
Provider Edge bridge.
802.1ad
The provider part only pays attention to S-Tags and S-VLANs
(provider bridge), and the edge part only knows how to deal
with C-Tags.
Good for
Allowing customers (of the network) to use whatever VLANs they

like
e.g. Enterprise customers
Networks that need Q in Q
(S-tags) or need to process S-Tags
Hiding the internals of the provider network from end customers.
The only choice if you need to use QinQ in the future.
133 AVIAT NETWORKS

PROVIDER-EDGE MODE
A Provider Edge Bridge contains a C-VLAN component per customer port and a single S-VLAN component. The
C-VLAN components processes frames with C-Tags. The S-VLAN component switches frames on S-Tags.
S-VLAN
C-VLAN
Component
Component
To customer Networks C-VLAN To provider Network

Component
C-VLAN
Component
CTR (Provider Edge Bridge)
134 AVIAT NETWORKS

SCENARIO – VLAN TUNNELING
Transport customer VLANs using

service provider VLAN tags (S-VLAN)
Service provider network
•Ingressing frames (tagged with customer

VLAN ID) will be double tagged with a
service provider tag
•Outer tag (s-tag) will be stripped from
egressing frames and delivered with the
original customer tag
•Customer tags are not configured in the
service provider network
Customer networks
135 AVIAT NETWORKS
PROVIDER-EDGE MODE
• There are 5 supported port types that can be configured in
Provider-Edge Mode:
• CEP – Customer Edge Port
• A Customer facing port that maps customer VLANs to Service VLANs
• CNP – Customer Network Port (Port Based)
• A Customer facing port that maps all inbound frames to one service VLAN using the
configured PVID
• CNP – Customer Network Port (S-Tagged)
• A customer facing port the accepts only S-Tagged frames
• PNP – Provider Network Port
• A Provider facing port that transmits only S-Tagged frames
• PPNP – Proprietary Provider Network Port
• A Provider facing port that transmits S-Tagged and Untagged frames, usefil for local
NMS
136 AVIAT NETWORKS

MANAGEMENT ACCESS FOR PROVIDER BRIDGING
• To reset management to Port 1 and VLAN 2, the following needs to be configured
• For In-band-Management, radio interfaces may be added to the VLAN as Tagged

aos(config)# int gi 0/1
aos(config)# no shut
aos(config)# map switch default
aos(config)# bridge port-type propProviderNetworkport
aos(config)# vlan 2
aos(config-vlan)# ports add gi 0/1 ra x/x untagged gi 0/1
aos(config-vlan)# management
aos(config-if)# switchport pvid 2
aos(config-if)# end
aos# w s
137 AVIAT NETWORKS
SCENARIO – VLAN TUNELLING
mode
Shutdown spanning tree aos(config)# shutdown spanning-
tree
Disable gvrp (Generic VLAN Registration aos(config)# set gvrp disable
Protocol)
Disable gmrp (GARP Multicast Registration aos(config)# set gmrp disable

Protocol)
Shutdown garp (General Attrribut aos(config)# shutdown garp

Registration Protocol)
Shutdown Ethernet CFM aos(config)# no ethernet cfm

start
Change bridge mode to provider aos(config)# bridge-mode All the above protocols must be
edge provider-edge shut down before the bridge mode
of the switch can be changed
Exit to go to Privileged EXEC aos(config)# end
mode
138 AVIAT NETWORKS
mode
Enter the VLAN configuration aos(config)# vlan 500
mode
Add member ports to VLAN aos(config-vlan)# ports add gi Member ports represent the set of
0/2, ra 3/1 untagged gi 0/2 ports permanently assigned to the
VLAN egress list. Frames
belonging to the specified VLAN
are forwarded to the ports in the
egress list. Gi 0/2 is added to vlan
500 on the radio link but stripped
at the egress port gi 0/2
mode
139 AVIAT NETWORKS

Configure the bridge port type for aos(config-if)# bridge port-type Changing the port mode
port 5 as CustomerNetworkPort customerNetworkPort port-based
(port-based)
Configure the PVID for port gi 0/5 aos(config-if)# switchport pvid 500
Activating the interface aos(config-if)# no shut
Go back one context aos(config-if)# exit
Enter the interface configuration aos(config)# int ra 3/1 Ensure the radio link is
mode for radio link ra 3/1 configured
Configure the bridge port type for aos(config-radio)# bridge port-type This is the deafult bridge
radio link as ProviderNetworkPort providerNetworkPort port-type for all interfaces in
provider bridge mode
140 AVIAT NETWORKS

SCENARIO – RESULTS
Site A Site B
Cust_1 Cust_1
Traffic P2 Ra Ra P2 Traffic
Vlan 100/200 2/1 2/1 Vlan 100/200
untagged untagged
Radio Link
Cust_2 Cust_2
Traffic P3 P3 Traffic
Vlan 100/200 Vlan 100/200
untagged untagged
CTR8540 CTR8540
Cust_1 Cust_1
Traffic Traffic
Cust_2 Cust_2
Traffic Traffic
Ingress Egress
141 AVIAT NETWORKS

SCENARIO – TEST OBSERVATIONS
• All ingressing traffic (untagged, single/double tagged) at Site A traffic

passed through to site B unaltered.
• To confirm Q-in-Q tagging, an additional test can be conducted to drop

one double tagged stream (VLAN 501) at Site B:
Change the VLAN membership configuration to "aos (config-vlan)# ports add gi
0/3 ra 3/1"
Results:
Untagged traffic from Site A P3 port is delivered to Site B P3 port with the outer tag 501
Single tagged traffic from Site A P3 port is delivered to Site B P3 double tagged with 501
as the outer tag
142 AVIAT NETWORKS

!
shutdown spanning-tree
set gvrp disable
set gmrp disable
shutdown garp
no ethernet cfm start
bridge-mode provider-edge
vlan 500
vlan active
ports add gi 0/2 ra 2/1 untagged gi 0/2 Value to change according
end need
!
int gi 0/2
bridge port-type customerNetworkPort port-based
switchport pvid 500
no shut
end
!
int ra 2/1
bridge port-type providerNetworkPort
end
ws
143 AVIAT NETWORKS

ENABLING PROVIDER EDGE VLANS WITH CTR PORTAL
To Enable Provider Edge Mode with CTR

Portal:
1. Enable a Revert Timer
2. Click “Enable Provider Edge Mode” Button
3. A Pop Up screen will display explaining what
will happen, if in agreement, click start • Warning, this method only results
in resetting of the default
4. Disable Revert Timer Management VLAN and IP
Address
144 AVIAT NETWORKS
PROVIDER EDGE VLANS WITH CTR PORTAL
• VLAN Screen – Add New or Edit Existing VLANs
145 AVIAT NETWORKS

PROVIDER EDGE VLANS WITH CTR PORTAL
• VLAN by Interface
Configuration
• View or configure
various VLAN
Parameters per
interface including
Port Type
• Options vary per
Port Type
146 AVIAT NETWORKS

Module 7
Ethernet QoS
AVIAT NETWORKS
CTR QOS MECHANISMS
Classifier Shaper
Storm Protection
Policer
Queuing Buffer Identify QoS capabilities of each network protocol layer
Scheduler Match QoS features of each network element to the desired QoS
policy design
Shaper
Seamlessly map QoS functions of all connected network
elements
148 AVIAT NETWORKS

QOS PRIORITIZATION
• Mechanism to ensure high priority traffic is delivered ahead of
low priority traffic when a network becomes congested.
• As traffic loads increase, port buffers begin to fill, which adds
to delay
• If the buffers overflow packets are dropped
• Prioritization assists by forwarding high-priority and delay-
sensitive traffic before other traffic
• Requires that traffic is tagged with a priority marker so that it
can be identified and moved into queues with the appropriate
service level for onward transmission
149 AVIAT NETWORKS

CTR QOS PRIORITIZATION PROCESS
• Ingressing Frames are classified per port or VLAN by reading their
markings or creating a marking and mapping them to the proper
internal queue.
• Marking options:
VLAN 802.1P (P-bits) (L2)
IP TOS (L3)
IP DSCP (L3)
• CTR interfaces have 8 Internal Priority queues, 0 = Lowest, 7 =

Highest
• The scheduler determines how frames are forwarded from the
transmission queues
Strict– Higher priority queues are emptied before moving to the next lower priority queue
Weighted Round Robin- Queues are weighted and each queue in serviced in a round robin
fashion according to it’s weighting
Other options, including combinations of strict and weighted round robin
150 AVIAT NETWORKS

CTR FUNCTIONAL QOS BLOCK DIAGRAM
151 AVIAT NETWORKS

QOS PRIORITY CLASSIFICATION CONFIGURATION
• QoS may be configured on the CTR8540/8300 via CLI or CTR
Portal:
• CLI Configuration requires creating multiple priority maps and
class maps for each port or interface
• This requires many lines of similar code and is best done via
script
• Non script configuration would be best done with CTR Portal
• CLI Configuration process is as follows:
1. Create a QoS Priority Map entry for each interface (Gi and Radio) and each
priority queue
2. For each entry create a map interface to map incoming frame markings to a
transmission queue
3. For each entry create a class map
4. If necessary, configure scheduler, default is Strict
152 AVIAT NETWORKS

QOS CONFIGURATION EXAMPLE COMMANDS
Enter Configuration Mode aos# configure terminal
Create 8 Priority map for each aos(config)# priority-map 10 This will be

interface. repeated for
1 per queue per interface each queue and
Typically the map number used interface and if
will be based on a slot necessary,
number/port number and queue priority type
number
Create at least one map interface aos(config-pri-map)# map int gi 0/2 in-priority-type
entry under each priority map vlanPri in-priority 0 regen-priority 0
Verifying Priority maps aos# show priority-map
153 AVIAT NETWORKS

QOS CONFIGURATION EXAMPLE FOR SITE A (3/5)
Create class maps for priority aos(config)# class-map 10
maps earlier created
Configure each class map aos(config-class-map)# match access-group
priority-map 10 set class 1 pre-color none
Set Marking and Pre-Coloring aos(config-class-map)# set class 3 pre-color
none
Verify class map aos# show class-map
• Traffic class is set with Policy maps

• Pre-coloring is optional and is done before metering
154 AVIAT NETWORKS

CONFIGURATION SUMMARY FOR QOS
aos(config)# priority-map 10
aos(config-pri-map)# map interface <TRAFFIC PORT ID> in-Priority-type vlanPri in-priority 0 regen-priority 0
aos(config-pri-map)# exit
aos(config)# priority-map 11
aos(config-pri-map)# map interface <TRAFFIC PORT ID> in-Priority-type vlanPri in-priority 1 regen-priority 1
aos(config-pri-map)# exit
…
…
…
aos(config)# class-map 10
aos(config-class-map)# match access-group priority-map 10
aos(config-class-map)# set class 1 pre-color none
aos(config-class-map)# exit
aos(config)# class-map 11
aos(config-class-map)# match access-group priority-map 11
aos(config-class-map)# set class 1 pre-color none
aos(config-class-map)# exit
…
…
… 155 AVIAT NETWORKS
QOS CLASSIFICATION MAPPING WITH CTR PORTAL
• Add, View, or edit

VLAN 802.1p, IP ToS
or IP DSCP policy
mapping
• Apply to ports or
interfaces
156 AVIAT NETWORKS

SCHEDULING CONFIGURATION
• Scheduling can be configured with CLI or CTR Portal
• The default scheduler (Scheduler 1) is configured for each
interface and queue and is Strict
• New Schedulers can be created or Scheduler 1 can be
modified per interface for options other than strict
scheduling CLI Configuration
scheduler 1 interface <iftype> <ifnum> [schedalgo{ strict-priority
| rr | wrr | wfq |strict-rr | strict-wrr | strict-wfq }]
# scheduler <integer(1-65535)> interface<iftype> <ifnum>

[sched-algo {strict-priority |rr | wrr | wfq | strict-rr | strict-wrr
|strict-wfq | deficit-rr}] [shaper <integer(0-65535)>] [hierarchy-
level <integer(0-10)>]
157 AVIAT NETWORKS

QOS SCHEDULING WITH CTR PORTAL
• Scheduling– View or Edit Scheduler, default is Strict Priority on all ports and interfaces
158 AVIAT NETWORKS
Module 8
L1 LINK AGGREGATION
AVIAT NETWORKS
LINK AGGREGATION
• When more capacity is needed than can be transported over one physical link,
link aggregation provides a solution
• Two or more physical (RF) links are established, and link aggregation is used
to provide one logical link with a capacity that is the sum of the individual links
• CTR supports link aggregation options at Layer 1 and Layer 2
• Link aggregation also provides redundancy
160 AVIAT NETWORKS

LAYER 1 LINK AGGREGATION (L1LA)
• L1LA employs Ethernet frame segmentation to
achieve uniform, balanced distribution
• L1LA is the most efficient option for Aggregating
Radio Links
• L1LA is feature licensed
• A maximum of 2 groups can be configured
• If one group is configured a maximum of eight
interfaces (radio or protected) may be grouped
together
• If two groups are configured, each group may only
contain four interfaces
• Only radio ports can be included, not Ethernet ports
• The far end configuration must match that of near
end
• L1LA is best configured with CTR Portal
161 AVIAT NETWORKS
L1LA CONFIGURATION IN CTR PORTAL
Select included
Radio interfaces
Click on Add to create Chose a Group ID and Enable and click

a group optional Description Apply
162 AVIAT NETWORKS

163 AVIAT NETWORKS

Module 9
Maintenance
AVIAT NETWORKS
ODU MAINTENANCE
• ODU replacement
• Ensure that ODUs are replaced with the same part number and re-installed with the
same orientation to prevent cross-polarization
• Before removal of IF cable always disable RFU Power in the Radio Diagnostics screen.
For protected systems, make sure the correct RAC port is disabled
• Always weatherproof re-connections with new Mastic and Vinyl tape and also use
conductive grease/paste on ground connections and silicon grease on feedhead O-
rings
165 AVIAT NETWORKS

PREVENTATIVE MAINTENANCE
• All sites must be inspected annually, or more frequently if
subject to abnormal operating conditions
• Preventative maintenance includes the following:
• Ensure that all modules are tightly inserted in the shelf
• Verify that all connectors and cables are tight and in good condition
• Via the Pro Vision, CTR Portal or CLI, verify that the TX power and RSLs are within
acceptable/design limits and view link history via event logs and performance/history screens to
check for problems.
• Check to make sure the system software is up to date and upgrade if necessary
166 AVIAT NETWORKS

SOFTWARE MANAGEMENT
• Software is easily upgradeable from the GUI (Recommended)

• Upgrade is possible locally by connecting a PC to the CTR or
remotely by pointing the CTR to a Software URI (Uniform Resource
Identifier)
• Software can be upgraded using the CLI command
• Activation of a new software or doing a software rollback will

be traffic affecting
167 AVIAT NETWORKS

SOFTWARE MANAGEMENT (VIA CTR PORTAL)
The new downloaded

software will be
tranfered to the
Inactive Version
Progress of the
software transfer
Select the folder

where the software is
stored on your PC
Select the control

mode you want to
used
168 AVIAT NETWORKS

SOFTWARE MANAGEMENT (VIA CLI)
• Software upgrade via CLI
• The new software must be copied in a specific folder on your PC
• You must install and HTTP server on your PC (IIS on Windows)
Getting in software management aos(config)# swload Connecting the software
menu management
Showing the way to access to the aos(config-swl)# load-uri http:// Use the IP address of your
software pack 11.150.1.1/ctr8540- PC and the software name
2.2.1.12.1675.swpack Showing the route where
software is stored
Software transfert aos(config-swl)# load Transferring the software
Checking the download progress aos(config-swl)# load See next slide
To activate the software aos(config-swl)# activate This will activate the new soft
Getting out config mode aos(config-if)# end
169 AVIAT NETWORKS

SOFTWARE MANAGEMENT (VIA CLI)
EXAMPLE
• aos# configure terminal
• aos(config)# swload
• aos(config-swl)# load-uri http:// 11.150.1.1/ctr8540-2.2.1.12.1675.swpack
• aos(config-swl)# load
• aos(config-swl)# show swl
• aos(config-swl)# activate
• aos(config)# end
# script for software load#
!
swload
load-uri http:// 11.150.1.1/ctr8540-2.2.1.12.1675.swpack Value to change according
load need
show swl
end
170 AVIAT NETWORKS

LICENSE MANAGEMENT
• CTR Licensing is easily upgradeable from the GUI
(Recommended)
• Once a license is uploaded it is committed. A license cannot be

unloaded from a CTR
• License Key upgrades are not traffic affecting but configuring a

new license feature may be
• Licensing is tied to the SD cards serial number and a license is

only valid on one SD card
171 AVIAT NETWORKS
LICENSE MANAGEMENT
• Feature licenses are easily uploaded via the GUI

SD/License Serial
number
Activated License
License not activated
Select the folder

where the software is
stored on your PC
172 AVIAT NETWORKS

LICENSE MANAGEMENT
• License can also be uploaded via the CLI but this would require
opening the license file with a text editor then copy and paste the
content between quotes in the command as shown below:
Care should be taken that no changes are made, when opening a file with a text editor
aos# license install license.txt contents “paste the license file here”
As an example we would look at the command below:
aos# license install license.txt contents “# License -- 484# License , Features CZG-
60016Version=2SerialNumber=LKC13480090CidNumber=0941504146205344101340416100
d34bHardware=CTR8540XPIC=1====== SIGNATURE FOLLOWS
======cRL+Eum+ngexOzZRlvwBgDvpRIEcH88zcvm9CiyiDJAhUyHXHu8EHlr6K2F3DcN6g
SVGzkfHjEYMAp6d8UlP0CLkJ2qE29MqCCphjnCNxakPtXDypd+LoixK5at64erIrHCZSoSa77
vRNJqN6C9369XlIoWs04Ee4vMRU+KrKpdP0XU5G4ygjGuO8g186/b+DcAROEdcxfyq4/J3IN
7RycV3/hh5xNFMHU0GEBEosJ7jhsrLYNN9acv2OlrnQlIuMqYEzsdx9V8ZWB8pmCFqNy7pr6
/B9aArkNfVk9B9vNPQr+cwnA/mImwX9z1utilLpH7u4TXkWd59RGv242o8WA==”
173 AVIAT NETWORKS

CONFIGURATION MANAGEMENT
• A backup of the configuration can be stored and this backup can be restored to the
radio either connecting locally with a PC or remotely from a config repository
• Configuration Restoration is traffic affecting and requires a revert timer to be enabled
Saving the config to a

file
Restoring the config

from a file on PC or
server PV
174 AVIAT NETWORKS

Module 10
Diagnostics and
Troubleshooting
AVIAT NETWORKS
RADIO LINK DIAGNOSTICS AND TROUBLESHOOTING
• A number of diagnostics tests
can be ran on the radio link.
This includes:
• Muting the Transmitter
• Locking Modulation states when
configuring ACM
• Loopbacks – Digital and IF
• Determination of XPD
• Carrier Only - For measuring carrier
frequency
• RFU Power Disable – For
disconnecting IF Cable to replace
ODU (No -48v on Line)
• Use Safety Timers for remote
diagnostics
176 AVIAT NETWORKS
SENSORS
• View Operating
thresholds and
Values such as:
• Temperature
• Voltage
• Current
• Memory Usage
• CPU Usage
177 AVIAT NETWORKS

LINK PERFORMANCE
• Checking the radio

link performance
• Two modes:
Real time
RSL / SNR / TX power /
Modulation……
Captured (start and stop

the test for certain
duration)
• RSL / SNR / TX power /
Modulation……
178 AVIAT NETWORKS

LINK PERFORMANCE HISTORY
• Checking the radio link performance history
Select the
interface you
want to monitor
179 AVIAT NETWORKS

RADIO LINK PERFORMANCE USING CLI
Checking the link performance aos# show rxperf realtime Performance for real time
aos# show rxperf qhour 15 mn performance data
aos# show rxperf day Day performance data
aos# show rxperf day interface rad 3/1

+----------------------------------------------------------+
| Radio Interface 1/3/1 2014/09/25 00:00:00 |
+----------------------------------------------------------+
| Max BER 0.500000000 |
| Mean BER 0.000005263 |
| Min BER 0.500000000 |
| Max RSL -46.4294967291 |
| Mean RSL -46.4294967291 |
| Min RSL -50.4294967292 |
| Frame Loss Seconds 1 |
| Data Invalid |
+----------------------------------------------------------+
180 AVIAT NETWORKS

INTERFACE STATISTICS
• The performance statistics of all the interfaces on the CTR can
be retrieved from the Statistics > Interface screen of CTR Portal
181 AVIAT NETWORKS

MAC ADDRESS TABLE
• The MAC Address
table shows all
Learned MAC
addresses per VLAN
• Can be used to
troubleshoot
connectivity issues to
CSRs and other
Routers and Ethernet
devices
182 AVIAT NETWORKS

CTR ALARMS
• System Alarms are shown in CTR Portal, go to Status – Alarms
• Options to show All Alarms or only Active Alarms
• Alarm severity is indicated by the color tag on each alarm:
Green: No alarm
Red: Critical
Orange: Major
Yellow: Minor
Blue: Warning
• A listing of all events and alarms, including probable cause and

recommended action is in the CTR Portal manual, Appendix A
183 AVIAT NETWORKS
BEFORE GOING TO SITE
If possible, log in remotely, to obtain the following information:
• Does the fault require immediate attention?
• Determine who is the best-placed person to attend the fault.
• Confirm the nature & severity of the reported fault

Ask:
- Is just one link affected, or a number of links in the same location?
- Is the path down completely or is traffic passing but with a BER alarm?
- Could the fault be in the equipment connected to CTR?
- Is it a hard or intermittent fault?
- Do alarms confirm which end of an alarmed link is faulty?
- Could weather be a factor in the reported fault?
- Could recent work be a cause of the fault?
184 AVIAT NETWORKS

TROUBLESHOOTING BASICS
• Check the basics first:
• Check current (active) alarms
• Component Failure Alarms- Many hardware specific alarms will indicate
the need to replace a plug-in module or RFU/ODU
• For intermittent problems check the Event Log, which shows a history of
all alarms and configuration changes.
• Use your protection as a troubleshooting tool. Check both receivers for
the presence of alarms, Switch the transmitter
• Check the RSL and the presence of path related alarms on the RACs.
Use the History screen to view the RSL, Tx Power, and Alarm history of
the link
• RAC before an RFU - If there is doubt about whether a fault is in a RAC,
or RFU/ODU, always replace the RAC first; it is quicker and easier
185 AVIAT NETWORKS

TROUBLESHOOTING PATH PROBLEMS
•Path Problems on a Commissioned Link
A path problem on an existing link that has been operating normally may be caused by:
- Weather-related path degradation If BER alarms are fleeting & RSL returns to its normal,
commissioned level after the alarm is cleared, rain, diffraction, or multipath fading is
indicated. Rain fade is the likely cause for links of 11 GHz and higher. Diffraction & multipath /
ducting for links of 11 GHz & lower. If these alarms are persistent, there could be a problem
with the link design or original installation
- Changed antenna alignment or antenna feed problem. If RSLs do not return to

commissioned levels after a period of strong winds, suspect antenna alignment. Also, check
the antenna for physical damage, such as may occur with ice-fall. For a remote-mounted
ODU, check its flex-twist waveguide. For Indoor Mounted RFUs, check the elliptical
waveguide, which can swept with specialized test equipment
186 AVIAT NETWORKS

RECEIVE ALARMS
• Receive alarms are the most
common type of alarms and can
be caused by the far end
transmitter or a path related
problem. Don’t assume it’s the
receiver
• Check RSL first when these
alarms appear
• Modulation mismatches will also
cause these alarms
• On protected links, both RACs
must have a “Demodulator is not
Locked” alarm for the “Traffic
Path Lost’ alarm to set
187 AVIAT NETWORKS
TROUBLESHOOTING PATH PROBLEMS
•Path Problems on a Commissioned Link - continued
- New path obstruction Where all

other parameters check as normal,
& the path could be obstructed by
new construction works and / or trees,
view / survey the path for possible
new obstructions.
-RF Interference from other signal sources. RF Interference usually effects traffic in just one
direction. Unlike other path problems, RSL is not affected. If suspected, check for new link
installations at the same site or in the same geographical area. To Check for interference, a mute
test can be run by muting the far end transmitter and checking the RSL locally. A spectrum
analyzer can also be used, connected to the antenna port.
-Low level interference can effect long term performance even if there is no BER at normal RSL
188 AVIAT NETWORKS

189 AVIAT NETWORKS

Module 11
SYNCHRONIZATION
AVIAT NETWORKS
SYNCHRONIZATION CAPABILITIES
• Synchronization Status Messaging (SSM) via ESMC (Ethernet Synchronization Messaging
Channel) in order to allow multiple redundant clock sources and avoid timing loops
• Synchronous Ethernet input (slave) and output (master) capable
• Automatic clock source switching between all supported input types
Synchronous Ethernet
E1/T1 tributary
Local oscillator (holdover)
• Local oscillator provides SEC frequency stability in accordance with G.781 Option I or EEC
stability in accordance with G.8262 Option I
• Ability to failover between multiple Synchronous Ethernet sources distributed across a
redundant CTR8540 pair
• IEEE 1588v2 prioritized transport and hardware-ready for native 1588v2 client
• QoS guideline: Up to 150 - 200 kbps traffic load should be factored in per 1588v2 node
• Requires a SyncE License
191 AVIAT NETWORKS

SYNCHRONIZATION STATES
At least one reference
is qualified
Free-Run
Power on
Lock
or reset Lock on the selected
Acquisition
reference is achieved
Another reference is qualified

and available for selection
Normal
Holdover (Locked)
No references are qualified

and available for selection Selected reference signals
DNU (Do Not Use) or
Selected reference fails degraded quality, and
alternative reference is
available
192 AVIAT NETWORKS

SYNCHRONIZATION CONFIGURATION EXAMPLE
Up to four external clock sources can be configured per CTR

• The quality level (QL) is used to determine the clock selection order when
multiple clock sources are provided
• A clock priority is also set for multiple clock sources to assist the selection
process when SSM is not enabled or where two or more sources have the same
QL
• Should all external clock sources fail, an internal clock is used
193 AVIAT NETWORKS
CONFIGURATION SUMMARY FOR SITE A
aos(config-if)# synchronous mode esmc-enabled
aos(config-if)# exit
aos(config-if)# synchronous mode esmc-enabled
aos(config-if)# exit
aos(config)# network-clock wait-to-restore 1
aos(config)# network-clock quality-level rx ql-ssua int gi 0/4
aos(config)# network-clock input-source 1 int gi 0/4
aos(config)# network-clock input-source 2 int gi 0/7
aos(config)# int ra 2/1
aos(config-radio)# synchronous mode esmc-enabled
aos(config-radio)# end
194 AVIAT NETWORKS

SYNCHRONIZATION CONFIGURATION IN CTR PORTAL
195 AVIAT NETWORKS

Module 12
TDM TRANSPORT
AND
PSEUDOWIRE CONFIGURATION
AVIAT NETWORKS
TDM TRANPSORT – PSEUDOWIRE
• Pseudowire (aka PWE) is an emulation of a point-to-point

connection over a packet-switching network (PSN)
• “Point to Point” may be TDM, ATM, Ethernet …
• “PSN” may be Ethernet, IP or MPLS
• Standardization is by IETF, MEF, ITU
197 AVIAT NETWORKS

PSEUDOWIRE TYPES
• CESoPSN (RFC5086) – Circuit Emulation Service over Packet
Switched Network
Pseudowire technology supports framed and channelized TDM services over
packet switched networks. CESoPSN uses multiples of the TDM frame itself for
packetization
• SAToP (RFC4553) – Structure Agnostic TDM over Packet
It treats the TDM traffic as a data stream and ignores the framing or the timeslots
• The CTR8540/8300 supports SAToP as the TDM Pseudowire

based on IETF RFC4553, ITU-T Y.1413 and Y.1453 and MEF
8 standards
• NOTE: all Pseudowire types require a synchronization
mechanism to recover the bit stream
• SyncE should be enabled on all Pseudowire transport
interfaces (radio Links and Ethernet transport interfaces)
198 AVIAT NETWORKS
mode
Inter in the E1 interface aos(config)# int cem 0/1 E1 port number (CEM 0/1 to 0/16)
configuration mode for the
selected TDM circuit
Create a cross connection aos(config-if)# xconnect The remote CTR’s mac address is
between the TDM circuits for 00:e0:e2:76:27:01 vcid 1 required to create a PW cross
source and destination encapsulation mef8 vlan 10 connect between source and
VCID: virtual circuit Identifier destination-(show switch detail)
Enable RTP Header aos(config-if-pw)# rtp enable RTP stands for Real-Time
Transport Protocol
Enable Packet-reordering aos(config-if-pw)# packet-
reorder
Set Jitter Buffer Size aos(config-if-pw)# jitter-buffer 32 Size is incremental in powers of 2
Set payload size according to E1 aos(config-if-pw)# payload-size E1: 256 bytes
or T1 rates 256 T1: 192 bytes
199 AVIAT NETWORKS

Set a unique id for the E1 or T1 aos(config-if-pw)# ecid 1 This unique id differs for each E1/T1
connection connection (integer(1-1048575))
ECID: Emulated Circuit IDentifier
Set the TDM circuit to have aos(config-if-pw)# clock Two options
access to a common high quality recovered differential Adaptive: extract from incoming E1/T1
timing source Differential: from high quality Eth clock
Commission the TDM circuit by aos(config-if-pw)# no shut
exiting to the interface
configuration mode
Enter the controller configuration aos(config)# controller e1
mode 0/1
Configure the line impedance aos(config-controller)# line The options are:
and commission the controller impedance balanced100ohms for T1 links only
unbalanced75ohms balanced120ohms for E1 links only
unbalanced75ohms for E1 links only
aos(config-controller)# no
shut
200 AVIAT NETWORKS
!
controller mode e1
interface cem 0/1
xconnect 00:e0:e2:76:a1:01 vcid 1 encapsulation mef8 vlan 10
rtp enable
packet-reorder
jitter-buffer 32
payload-size 256
Value to change according
ecid 1
need
clock recovered differential
no shut
end
!
controller e1 0/1
line impedance unbalanced75ohms
clock source internal
no shut
end
ws
201 AVIAT NETWORKS

TDM USEFUL CLI COMMAND
• To view TDM interface status via CLI:
• Command
aos# show cem cem0/2 up, line protocol is up
(connected)
• Result Interface SubType: Not Applicable
cem0/1 up, line protocol is up (connected)
Interface SubType: Not Applicable
Pseudo Wire Type - e1satop
Pseudo Wire Type - e1satop Data Rate: 32Kb
Data Rate: 32Kb PW Psn Type: 6
PW Psn Type: 6 Payload Size: 256Bytes
Payload Size: 256Bytes JitterBuffer Size: 32ms
JitterBuffer Size: 32ms Time Stamp mode: DIFFERENTIAL
Time Stamp mode: DIFFERENTIAL
RTP Header: Used RTP Header: Used
Packet Reorder: Enabled Packet Reorder: Enabled
Destination Mac: 00:e0:e2:76:a1:01 Destination Mac: 00:e0:e2:76:27:01
Vlan Id: 10 Vlan Id: 10
Destination Port: interface radio 3/1 ECID: 2
ECID: 1
VCID RxValid RxDrop RxErrors VCID RxValid RxDrop RxErrors
---- ------- ------ ------- - ---- ------- ------ --------
1 9519 0 0 2 529116 0 0
VCID TxValid TxDrop TxErrors VCID TxValid TxDrop TxErrors
---- ------- ------ -------- ---- ------- ------ --------
1 9507 19 53 2 0 0 19315
202 AVIAT NETWORKS

TDM USEFUL CLI COMMAND
• To view TDM interface
status via CLI: TX:
----
• Command Valid Packets: 881109
aos# show pseudowire Dummy Packets: 0
counters vcid1 Underrun Dataunit: 51
Buffer Underrun: 5
Forwarded Packets: 881110
• Result Out Of Window Packets: 0
Window Switchover: 0
Stray Packets: 0
RX: AIS Drop Packets: 0
---- MPLS Drop Packets: 0
Valid Packets: 881122 Out Of Sequence Packets: 0
Channel Out Of Sync: 0 RAI Packets: 0
Empty FBP: 0 FBP Drop packets: 0
Forwarded Packets: 881122 Buffer Overun Dropped Packets: 0
Buffer Overun Events: 0
FBP Drop Packets: 0 Malformed Packets: 19
MTU Drop Packets: 0 Multiple Packets: 0
TX Queue Drop Packets: 0 Denied Packets: 0
Out Of Band CAS Packets: 0
RDI Dropped Packets: 0
203 AVIAT NETWORKS

TDM CONFIGURATION WITH CTR PORTAL
• Click add to configure new interfaces

• Displays Local Switch MAC – useful for remote end configuration
204 AVIAT NETWORKS
CTR PORTAL TRIBUTARY DIAGNOSTICS
205 AVIAT NETWORKS

LAB SESSION
206 AVIAT NETWORKS

AviatCare
SUPPORT
AVIAT NETWORKS
AVIAT GLOBAL
facts and figures
SERVICES
#1 #1 #1
Rated Service
microwave turnkey Infonetics rated for partner by our largest
provider in NA/Africa Service & Support customers
5 $130+ 200+
regional technical million dedicated service
support centers FY13 services delivery resources
business
50 years 17+ 95%

countries with
quality service of our public safety
extensive service
delivery projects are turnkey
presence
NOC ISO TL9000

built out global certified
and back-up
With Proven Capabilities in the following industries:

Emergency Response Networks
Low Latency Solutions
Security & Video Surveillance
Carrier Level 3G / LTE Backhaul
AVIAT NETWORKS
AVIATCARE EDUCATE
facts and figures - FY2014
5 ~100 210+
technical training customer locations training sessions
centers served worldwide conducted
~1000 80+ 9.36

certified individuals customer satisfaction
individuals trained and growing average
With proven capabilities and training programs covering

following areas:
Microwave Switching and Routing Solutions
IP Networking
Microwave Trunking
Pathloss and PCR
AVIAT NETWORKS
AVIAT NETWORKS GLOBAL SERVICES
AVIATDESIGN AVIATDEPLOY
CUSTOMER AVIATCARE
ASSURANCE
EXTENDED /
CORRECTIVE / CUSTOMER
ENHANCED
PREVENTATIVE TRAINING
WARRANTY
AVIATCARE
MANAGED NETWORK
SPARES
NETWORK OPTIMIZATION
MANAGEMENT
OPERATIONS SERVICES
210
AVIAT NETWORKS
WAYS TO ACCESS TECHNICAL SUPPORT
1. Self Service using Aviat Knowledge Base
2. Submit a case online at http://support.aviatnetworks.com/
3. Email to open a case
4. Call Aviat Technical Help Desk

• Americas
– Toll-free in US: +1 800 227 8332
– TAC.AM@aviatnet.com
• EMEA
– +44 1698 717 230 UK
– +33 177 31 00 33 France
– TAC.EMEA@aviatnet.com
• Asia Pacific
– +63 45 599 5192
– TAC.APAC@aviatnet.com
211 AVIAT NETWORKS

AVIATCARE CUSTOMER SUPPORT SITE
Access AviatCARE EDUCATE

Elearning content (needs
separate subscription)
Technical support Repairs Tracking

site – Access and & new RMA
open new service Requests
requests Access latest Software
Releases,
Customer SW Release Notes,
Product Instruction Manuals &
To register, go to Product Bulletins
www.support.aviatnetworks.com click on the
link to “Request a new Aviat Support
Account”
After registration, the user can select the product or
products they wish to receive automatic e-mail
notifications on when new postings are made on the
Web site.
212 AVIAT NETWORKS

SUPPORT HOME PAGE
HTTP://SUPPORT.AVIATNETWORKS.COM/
213 AVIAT NETWORKS

EASY ANSWER – KB SOLUTION AT YOUR FINGERTIPS
What is the best choice for quick answers to

known issues?
Search the KB
or
Look for the “Suggested Answers” that
are displayed when opening up a ticket.
When you fill the summary with information
on the suspected faulty units, the system
will automatically propose some known
solution registered in the knowledge base.
You may have your answer right away and
get a speedy resolution to the issue.
214 AVIAT NETWORKS

YOUR FEEDBACK IS VERY IMPORTANT!
215 AVIAT NETWORKS

ONLINE SUPPORT AT HTTP://SUPPORT.AVIATNETWORKS.COM/
216 AVIAT NETWORKS

Need documentation?
Manuals
Release Note
News update
Need Software
Latest version?
Previous version?
Just go to the
Download page and
you will get everything
you need
217 AVIAT NETWORKS

218 AVIAT NETWORKS

219 AVIAT NETWORKS

W W W. AV I AT N E T W O R K S . C O M

CTR 8540 - 8300 E0.3.4

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 8540 - 8300 E0.3.4

Uploaded by

Copyright:

Available Formats

CTR8540/8300 L2

What does this mean?

• Upon completion of this module, participants would be able to :

All Indoor IRU 600

1. Fan Module (mandatory)

8. Slot 3. RACX2 module (installed)

9. 4x SFP Switch Ports

• Ultra-compact, ultra-powerful CTR 8300

• Ethernet and serial (console) management access

4 x Gigabit Ethernet ports

16 x TDM ports (T1 or E1)

IF connections for ODU/IRU (single IF as standard)

Mounting bracket with earth stud

5 to 42 GHz • Over air compatibility with ODU 300hp and

• Mounts directly to antenna

• Equal Loss 3.5 / 3.5 dB splitter

• Un-Equal Loss 1.5 / 6.5 dB splitter

• Splitter losses effect both Tx and Rx

• Also used for 2+0 co-polar arrangements

• ODUs are fixed for TX low or TX high operation

• ODUs are sub-banded by their internal diplexers

* Specifications shown for 13-

• Synthesized Local Oscillators for software controlled

Multiple Channel Alternate Channel Co-Channel

RACx2 or 2 x RACx1 RACx2 or 2 x RACx1 RACx2 with XPIC

0dBm, 1mw • Fade Margin – Difference between RSL

Normal RSL: -40dBm • Low level modulation (QPSK)

Modulation Scheme Airlink Capacity Max Transmit Power 10-6 RX Threshold

Specifications for ODU 600, High Power, L6 GHz, 30MHz BW (ANSI)

Modulation Scheme Airlink Capacity Max Transmit Power 10-6 RX Threshold

Specifications for ODU 600, High Power, 7GHz, 28MHz BW (ETSI)

• Full CTR configuration is supported under CLI where two

Switch port 1 for telnet connection

V.24 front panel for

• Connect PC serial port to CTR Maintenance V.24 port

• Use a Terminal Emulation

Using Tera Term as the serial

Switch port 1 for telnet connection

• Connect PC Ethernet port to switch port 1 of the CTR8540

Switch port 1 for telnet connection

• The default login for the CTR8540 and 8311/12:

• To show the current management VLAN 2 and its IP

• Commands to change the management IP address:

# script for IP address change#

• As an example, we will change:

• This example is Out-Of-Band management where the

Action Command Remark

exit aos (config-vlan)# exit Exit VLAN 2 configuration mode

Action Command Remark

Exit aos (config-if)# exit Exit Interface VLAN 2

exit aos (config-vlan)#exit Exit VLAN 20 Configuration

exit aos (config-if)#exit Exit int vlan 20 config mode

Enable the port aos (config)# no shutdown Enable interface Gi 0/4

Action Command Remark

Getting out config mode aos(config-if)# end

Action Command Remark

aos# configure terminal

aos# show running-config Displays the configuration file

aos# configure terminal Goes into the global configuration mode

aos# exit Goes back one context

• Resetting the configuration to factory

• To revert to the out-of-box default factory settings:

• The system will reboot with a default configuration file.