CUSTOMER TRAINING

TECHNICAL TRAINING STUDENT LAB WORKBOOK

Lab Workbook CTR 8500/8300 Installation, Operation and

Maintenance
LWB-CTR-E0.3

LWB-CTR-E0.3
Revision History
Issue No. Issue Date ECO Description of Change / Revision
01 06-01-15 E0.1 Initial Release

02 08-28-15 E0.2 Update

03 09-18-15 E0.3 Update

Part Number LWB-CTR-E0.3

Copyright 2015 Aviat Networks, Inc. All rights reserved
Data subject to change without prior notice

Aviat Networks, Inc. www.Aviatnetworks.com

5200 Great America Parkway TAC US/Canada 800-227-8332
Santa Clara, CA 95054 EMEA UK +44(0)1698 717 230
United States France +33 (0) 1 77 31 00 33
Tel: 408 567 7000 Asia/Pacific +63 45 599 5192

LWB-CTR-E0.3
Lab 1: CLI Connectivity
Topology Diagram

Learning Objectives

Upon completion of this lab, you will be able to:

Log into CTR with a serial connection

Reset the CTR to factory defaults
Change the Management IP Address
Change the Management VLAN
Change the Management Port

Scenario

In this lab activity, you will create a network that is similar to the one shown in the Topology Diagram and
configure various parameters such as the Management IP Address, VLAN, and Port.

Begin by connecting to the CTR V.24 Port via a serial connection using the provided Aviat DB-9 to RJ-45
converter. Use a terminal emulation program such as Putty set to 115200, 8, 1, and none (see CTR SHB). The
default username and password are: Username: root, Password: admin123
1 of 4
Task 1: Reset the device to factory default

1. Connect to the Device with a serial connection and a terminal emulation program such as Putty.
2. Enter the following commands to load factory defaults with a revert timer of 3600 seconds.

aos#configure terminal
aos(config)#config load factory-defaults revert-timer 3600

1. After the reboot, log back in and disable the revert timer with the following commands:
aos#configure terminal
aos(config)#no revert-timer

Task 2:

1. Log in and try some basic show commands from the aos# prompt
2. Use the ? to see some of your options for commands, both from the aos# prompt and after typing show
from the prompt
For example:

aos#show management
aos#show running-config
aos#show vlan
aos#locateme (Look at Aviat Logo on unit)
aos#no locateme
aos# ?
aos# show ?

Task 3:

1. Change the management IP Address with the following commands:

Example:

aos#configure terminal
aos(config)#interface vlan 2
aos(config-if)#ip address 192.168.1.20 255.255.255.0
aos(config-if)# end
aos# write startup-config
#######

2. Verify the new IP address with the following command:

aos#show running-config int vlan 2

2 of 4
Task 4:

1. Change the management VLAN, Port, and IP address. In this example we will use VLAN 20, port 4 and IP
Address 10.10.1.X/24. A different address will be used for each CTR in the classroom, all in the same
subnet. After adding the new VLAN and VLAN Interface, the old one (VLAN 2) must be removed. Also the
default management port gi 0/1 must be removed from management and can be added to VLAN 1 as an
untagged port, as all the other ports are by default. The first line shuts down spanning tree protocol,
which could potentially cause problems if the devices are connected to the same switch.

Example:

aos# c t
aos(config)#shutdown spanning-tree
aos(config)#vlan 20
aos(config-vlan)#ports gi 0/4 untagged gi 0/4
aos(config-vlan)#management
aos(config-vlan)#no ports gi 0/1 untagged gi 0/1
aos(config-vlan)# exit
aos(config)#interface vlan 20
aos(config-if)#ip address 10.10.1.X 255.255.255.0
aos(config-if)#no shut
aos(config-if)# exit
aos(config)#interface gi 0/4
aos(config-if)#description MGMT_Port
aos(config-if)#switchport acceptable-frame-type untaggedAndPrioritytagged
aos(config-if)#switchport pvid 20
aos(config-if)#no shut
aos(config-if)# exit
aos(config)#interface vlan 2
aos(config-if)#shut
aos(config-if)# exit
aos(config)#no int vlan 2
aos(config)#no vlan 2
aos(config)# interface gi 0/1
aos(config-if)#shut
aos(config-vlan)#end
aos# w s
#######

3 of 4
Task 5: Verify the new Management Port and IP Address

Configure a static IP address on the LAN port of a computer in the same subnet as the new
management port, connect an Ethernet cable, and verify connectivity with a telnet session.
Once in enter the following commands to show the new management, VLAN, and interface
status and configuration. Also notice that some of the following commands have been
shortened.

aos#show management
aos#show vlan
aos#show run int vlan 20
aos#show int gi 0/4
aos#show int gi 0/1

4 of 4
Lab 2: CTR Portal and Radio Link
Configuration
Topology Diagram

Learning Objectives

Upon completion of this lab, you will be able to:

Log into CTR with CTR Portal

Set slots to detected cards
Configure an RF link with CRT Portal
Configure a protected link with CTR Portal
Enable and test Ethernet Ports with CTR Portal

1 of 5
Scenario

In this lab activity you will log into CTR with the Web Browser GUI, CTR Portal. Once in you will detect all installed
cards and configure an RF link. Typically this will be done with one or a group of students on each end of the link.
The ODUs should be connected back to back with transitions, cables and attenuators. If applicable; the link can
also be protected. A pair of ODUs can either be protected first, and then configured as a protected pair, or the
primary ODU can be configured first and then protected. There is no need to configure the secondary unit as it
will take on the configuration of the primary unit when protected. The one exception is factory mute, which will
have to be disabled independently on each unit. Frequencies, bandwidth, modulation, and power will vary
depending on equipment, licensing, and student requirements.

After the link is up and running (good RSL on each end and no RF alarms) an Ethernet port will be configured on
each end and tested with either an Ethernet tester or a pair of laptops. The default VLAN settings will be used.

Task 1: Set slots to detected cards

1. Connect to the management port with an Ethernet cable and the computer in the same subnet.
2. Open a browser such and IE or Chrome and type the CTRs address in the address bar.
3. Log in with the CTR username and password.
4. Click System Configuration > Admin > Configuration Management and save a configuration file for future
use ( this configuration will contain management settings and base configuration from Lab 1, but no RF
configuration, and will be used in other labs)
5. Right click on any slots with detected cards and set all slots to detected plug-in types.
6. Click Save to save the change.

2 of 5
Task 2: Configure the ODU

1. Click on the Radio Configuration Menu and choose Radio Links.

2. Configure the following:
a. Enable the interface
b. Optionally add a description, typically where the link is connecting to
c. Choose a regulatory standard
d. Set a bandwidth
e. Choose fixed or adaptive modulation and set the modulation parameters
f. Assign a licensed capacity, typically matching the configured max capacity
g. Set a Transmit and Receive frequency, typically maintaining the ODUs T/R spacing
h. Set the power, high power mode, and ATPC if required, for example when running ACM
i. Un-tick the factory mute box
j. Click apply
3. Once both ends of the link are configured correctly, the RSL should be in an acceptable range and all RF
alarms should clear, indicating the link is up.
4. Click Save to save configuration.

3 of 5
Task 3: Optionally protect the link

1. If a protected pair of ODUs is to be used in the class, they need to be protected.

2. This step can be done before or after the primary ODU is configured
3. Click on the Radio Configuration Menu and choose Radio Protection.
4. Click Add to add a protected pair and choose the ID (1-4), the primary and secondary interfaces,
protection type, splitter type and loss, and revert mode.
5. Click Apply
6. The secondary ODU will take on the configuration parameters of the primary ODU and may need a factory
mute turned off.
7. Click Save to save configuration

Task 4: Enable an Ethernet Port and test Ethernet connectivity

8. Click on the Switching and Routing Configuration Menu and choose Port Manager.
9. Enable a port other than the management port.
10. Optionally give the port a description.
11. Notice the port is defaulted to Auto Negotiate, depending on the settings of the tester or computer you
plan to connect, the setting may need to be changed to a fixed speed and duplex setting.
4 of 5
12. Click Apply and notice the port going into alarm.
13. Connect a device and notice the port alarm clear.
14. Once the other end is ready, ping or test across the link.

5 of 5
Lab 3: CTR Radio Link Script Loading
Topology Diagram

Learning Objectives

Upon completion of this lab, you will be able to:

Load RF Link Configuration Script files

Verify RF link with CRT Portal

Scenario

In this lab activity you will practice editing and loading various RF script files and verify them with CTR Portal.

1 of 2
Task 1: Reset the device to factory default

1. Connect to the Device with a serial connection and a terminal emulation program such as Putty.
2. Enter the following commands to load factory defaults with a revert timer of 3600 seconds.

aos#configure terminal
aos(config)#config load factory-defaults revert-timer 3600

1. After the reboot, log back in and disable the revert timer with the following commands:
aos#configure terminal
aos(config)#no revert-timer

Task 2: View or edit the script file

2. View or edit one of the script files from the class flash drive that best fits the RF Hardware installed.
3. Parameters to be edited will be in < > brackets and are parameters such as radio interface number, radio
frequencies, modulation, and bandwidth.

Task 3: Load the script file

1. Open a telnet or serial CLI session and paste the contents of the edited script file.
2. If errors appear, try to figure out why or ask the instructor for help.

Task 2: Verify the configuration

1. After the script has been successfully loaded, verify it by logging in with a CTR Portal session and going to
the Radio Link Configuration screen.
2. Optionally, repeat with other sample RF script files.

2 of 2
Lab 4: Port Based VLANs
Topology Diagram

Learning Objectives

Upon completion of this lab, you will be able to:

Configure Customer Bridged Port Based Untagged VLANs on CTR Edge ports
Configure Customer Bridged Tagged VLANs CTR Microwave Radio Links

Scenario

In this lab activity, you will create a network that is similar to the one shown in the Topology Diagram. With CLI,
configure Customer Bridged Port Based Untagged VLAN 200 on port Gi 0/1 and VLAN 300 on Gi 0/2. Both VLANs
will be configured as Tagged across the microwave link.

Task 1: Configure 2 port based VLANs

1. Enter the following CLI commands to configure untagged VLAN 200 on port Gi 0/1 and untagged VLAN
300 on port Gi 0/2. Both ports will have a PVID set to tag untagged frames that ingress the ports. Both
VLANS will be configured as tagged across the microwave link.

1 of 2
Example:

aos#configure terminal
aos(config)#vlan 200
aos(config-vlan)#ports add gi 0/1 untagged gi 0/1
aos(config-vlan)#ports add ra 3/1 (or ra 0/1 on 8312, or prot 1 on Protected links)
aos(config-vlan)# exit
aos(config)#vlan 300
aos(config-vlan)#ports add gi 0/2 untagged gi 0/2
aos(config-vlan)#ports add ra 3/1 (or ra 0/1 on 8312, or prot 1 on Protected links)
aos(config-vlan)# exit
aos(config)#interface gi 0/1
aos(config-if)#switchport pvid 200
aos(config-if)#switchport acceptable-frame-type untaggedAndPrioritytagged
aos(config-if)# no shut
aos(config-if)# exit
aos(config)#interface gi 0/2
aos(config-if)#switchport pvid 300
aos(config-if)#switchport acceptable-frame-type untaggedAndPrioritytagged
aos(config-if)# no shut
aos(config-if)# exit
aos(config)#interface ra 3/1 (or ra 0/1 on 8312, or prot 1 on Protected links)
aos(config-radio)#switchport acceptable-frame-type tagged
aos(config-radio)# no shut
aos(config-radio)# exit
aos(config)#vlan 1
aos(config-vlan)#no ports gi 0/1-2 untagged gi 0/1-2
aos(config-vlan)# end
aos# w s
#######

Task 2: Try to pass traffic between the ports and over the radio link

1. Test the link with untagged traffic from port 1 to 1, 2 to 2, and 1 to 2 across the link and verify that only 1
to 1 and 2 to 2 pass traffic or ping across the link.
2. Test with tagged traffic and verify that traffic will not pass from ports 1 to 1 or 2 to 2.

Task 3: Verify with CTR Portal

1. Connect with CTR Portal and go to routing and switching/VLANs by interface and verify the
configuration.

2 of 2
Lab 5: Customer Bridged VLANs
Topology Diagram

Learning Objectives

Upon completion of this lab, you will be able to:

Configure Customer Bridged Tagged VLANs on CTR Edge ports

Configure Customer Bridged Tagged VLANs CTR Microwave Radio Links

Scenario

In this lab activity, you will create a network that is similar to the one shown in the Topology Diagram. With CLI,
configure Customer Bridged Tagged VLANs 200 and 300 on port Gi 0/1 and VLAN 300 on Gi 0/2. Tagged VLAN
200 will be configured across the microwave link.

Task 1: Configure 2 tagged VLANs

1. Enter the following CLI commands to configure tagged VLAN 200 on port Gi 0/1 and the radio link and
tagged VLAN 300 on ports Gi 0/1 and Gi 0/2.

1 of 2
Example:

aos#configure terminal
aos(config)#vlan 200
aos(config-vlan)#ports add gi 0/1 ra 3/1 (or ra 0/1 on 8312, or prot 1 on Protected links)
aos(config-vlan)# exit
aos(config)#vlan 300
aos(config-vlan)#ports add gi 0/1 gi 0/2
aos(config-vlan)# exit
aos(config)#interface gi 0/1
aos(config-if)#switchport acceptable-frame-type tagged
aos(config-if)# no shut
aos(config-if)# exit
aos(config)#interface gi 0/2
aos(config-if)#switchport acceptable-frame-type tagged
aos(config-if)# no shut
aos(config-if)# exit
aos(config)#interface ra 3/1 (or ra 0/1 on 8312, or prot 1 on Protected links)
aos(config-radio)#switchport acceptable-frame-type tagged
aos(config-radio)# no shut
aos(config-radio)# exit
aos(config)#vlan 1
aos(config-vlan)#no ports gi 0/1-2 untagged gi 0/1-2
aos(config-vlan)# end
aos# w s
#######

Task 2: Try to pass traffic between the ports and over the radio link

1. With an Ethernet tester try to pass untagged traffic between ports 1 and 2 and over the radio link port 1
to port 1.
2. Set the testers to generate VLAN 200 traffic and verify that traffic will pass from port 1 to port 1 over the
radio link and will not pass port 1 to port 2 locally.
3. Set the testers to generate VLAN 300 traffic and verify that traffic will pass from port 1 to port 2 locally
and will not pass from port 1 to port 1 over the radio link .

Task 3: Verify with CTR Portal

1. Connect with CTR Portal and go to routing and switching/VLANs by interface and verify the
configuration.
2. Go to the VLANs screen and create a new VLAN and add it to port 1 and the radio link (tagged)
and verify it will pass over the link.

2 of 2
Lab 5: 2+0 L1LA Configuration
Topology Diagram

Learning Objectives

Upon completion of this lab, you will be able to:

Configure a 2+0 Layer 1 Link Aggregation link

Verify the capacity with a pair of Ethernet Testers

Scenario

In this lab activity you will configure a layer 1 Link Aggregation link pair (2+0) and verify the added capacity with
an Ethernet tester. This lab can only be accomplished on a system with 2 ODUs on each end (preferably with an
equal loss coupler). If the class only has one such link, students should take turns in groups to perform the lab.

1 of 2
Task 1: Configure 1+0 links

1. Configure two links as 1+0 non-protect, the frequencies of the two links should be separated as much as
possible. Assuming the ODUs are of the same sub-band, use one frequency at the bottom of the diplexer
(internal filter) range and the other at the top end. For more detail, see the ODU 600 Tuning guide.
2. Bandwidth and modulation should be the same on both.
3. Verify both links are up.

Task 2: configure L1LA

1. Go to Switching and Routing Configuration - Link Aggregation.

2. Add a new Link Aggregation group by clicking the Add button and using group 1.
3. Give the L1LA Group a Description, Enable, and choose the radio interfaces.
4. Click apply and Save

Task 3: Verify the configuration

1. Verify the added capacity with a pair of Ethernet Testers.

2. Additional Interface and VLAN configuration may be required.

2 of 2
Lab 6: Diagnostics and Troubleshooting
Topology Diagram

Learning Objectives

Upon completion of this lab, you will be able to:

View various CTR Portal screens to help troubleshoot the CTR system.
Use Various CTR Portal tools to help troubleshoot the CTR system.

Scenario

In this lab activity each group will log into one end of a CTR link with CTR Portal to run various tests to trouble shoot
the system.

Task 1: Verify system Parameters

1. Go to Status > Alarms and view any Active Alarms.

2. If there are any Ethernet port alarms for unused ports, de-activate those ports in port manager.
3. Go back to the alarms screen and verify they have cleared.
4. Click View all Alarms to see all available CTR Alarms.
5. Go to Status > Sensors and view various Parameters available on the screen.
6. Go to Statistics > Radio Link Performance and read the current Transmit power, RSL, and SNR, and view
other Parameters available on the screen.

1 of 3
Task 2: Test RFU Power Disable.

1. Go to Radio Configuration - Radio Link Diagnostics.

2. Choose RFU Power Disable for each RF interface, select a 15 minute safety timer and click apply.
3. Steps 4 and 5 should be skipped if working with equipment to be installed in a production environment.
4. Remove one of the IF cables and optionally remove the RAC and re-insert.
5. Reconnect the IF cable (the SMA connector should not be over-tightened, the torque spec is 8-9
inch/pounds).
6. Re-enable the RFU power.
7. After about a minute, Verify the link is up.

Task 3: Test RF Mute and IF Loopback

1. Go to Radio Configuration - Radio Link Diagnostics.

2. Apply an RF Mute to all Radio Links with a safety timer of 30 minutes.
3. When the group at the other end of the link has also applied their mute, go to the RF
Performance screen and verify a low RSL (< -90dBm)

2 of 3
4. Go to the Alarms screen and verify that there is a radio path lost and demodulator is not locked
alarm.

5. Go to Statistics - Radio G826. Select Captured. For Captured, click Start Collection.
6. After at least 10 seconds, verify the unavailable time is counting up and click Stop Collection.
7. Go to Radio Configuration - Radio Link Diagnostics, and apply an IF loopback to all radio interfaces for
10 minutes.
8. Go to Statistics - Radio G826. Select Captured. For Captured, click Start Collection.
9. After 1 minute verify that available time is counting up and there is no un-available time or errors. This
indicates an error free condition in IF loopback, which indicates most likely a good RAC. Also go to the
alarm screen and verify that the radio path and demodulator not locked alarms have cleared while in
loopback, another indicator of a good RAC. These tests would be used to determine if a RAC or ODU is
faulty. For intermittent conditions, the G826 collection period may be extended.
10. Remove the IF Loopbacks and RF Mutes and when the group on the other end has done the same, verify
the link is back to an error/alarm free condition.

3 of 3