Harmony Enhanced, 1 Plus 1 Configuration Method of Procedure - TN-000045-01-En-01-01

Technical Note
Harmony Enhanced 1+1 Configuration

Method of Procedure - Generic
OMNI Release 3.1.0
Revision 1.1
Document Number: TN-000045-01-EN
Date: 12/05/2017
Supersedes: None
Issuer: DragonWave-X Customer Support
Harmony Enhanced 1+1 HSB Configuration MOP
NOTICE
This document contains DragonWave-X proprietary information. Use, disclosure, copying or distribution of any
part of the information contained herein, beyond that for which it was originally furnished, requires the written
permission of DragonWave-X.
The information in this document is subject to change without notice and relates only to the product defined in
the introduction of this document. DragonWave-X intends that information contained herein is, to the best of its
knowledge, correct and accurate. However, any/all liabilities associated with the use or accuracy of the
information contained herein must be defined in a separate agreement between DragonWave-X and the
customer/user.
DragonWave®, Horizon® and Avenue® are registered trademarks of DragonWave-X. ©2017 DragonWave-X.
All rights reserved
TN-000045-01-EN Page 2 of 32 12.2017

Copyright 2017 DragonWave-X. All rights reserved.
TABLE OF CONTENTS
1 HISTORY........................................................................................................... 4
2 PRE-INSTALLATION CONFIGURATION......................................................... 5
2.1 Software Confirmation ........................................................................................................................... 5
2.2 Licenses ................................................................................................................................................. 6
3 1+1 CONFIGURATION (REDUNDANCY CONFIG).......................................... 7

3.1 System Type Configuration .................................................................................................................... 7
3.2 System Identifier Configuration .............................................................................................................. 8
3.3 Switch Mode Configuration .................................................................................................................... 9
3.4 Standby Interface Mode Configuration ................................................................................................ 10
3.5 Revertive Radio Switching and Radio Link Priority Configuration ....................................................... 11
3.6 Interface Group Configuration .............................................................................................................. 12
4 BASIC RF CONFIGURATION ........................................................................ 13

4.1 RF Profile Configuration ....................................................................................................................... 13
4.2 Management Configuration .................................................................................................................. 15
5 POST-ALIGNMENT CONFIGURATION ......................................................... 17

5.1 Reserved Management VLAN ID ......................................................................................................... 17
5.2 Payload VLAN Configuration ............................................................................................................... 19
6 VERIFYING THE 1+1 LINK IS OPERATIONAL ............................................. 21

6.1 Verifying Primary to Secondary Radio Communication ....................................................................... 21
6.2 Verifying 1+1 Radio Link is Operational ............................................................................................... 23
7 FIRMWARE COMMIT ..................................................................................... 32
TN-000045-01-EN Page 3 of 32 12.2017

1 History
Revision Update Date Updates Reason
1.0 07/05/2017 Initial Version Document Created.

Updates and pagination.
Small Edits and formatting. Add new section, and update
1.1 12/05/2017 Added a section on Reserved branding. Reformatted
Management VLAN. consistent with Advanced
Config Manual
TN-000045-01-EN Page 4 of 32 12.2017

2 Pre-Installation Configuration
With the exception of software/license key upgrades and system type and system identifier configurations, all other
configuration changes are dynamic, and take event immediately.
Note: A “save” is still required after dynamic configuration changes to ensure that settings are maintained after a
system reset.
2.1 Software Confirmation

Harmony Enhanced OMNI software version 3.1.x or later is required for 1+1 HSB, 2+0 1CR and 2+0 XPIC support.
OMNI and Target Configuration File (TCF) versions must be the same on both radios on both ends of the link.
Software Confirmation: Validate OMNI and TCF software

Note – OMNI and Target Configuration File (TCF) versions must be the same on both radios at both ends of the link.
Web GUI Commands CLI Equivalent Commands
1. Log into the Web GUI, navigate to the “Home” menu and make note of the
“Active” OMNI Release and Target Configuration File (TCF) versions. The
radios at either end of a link MUST be running the same OMNI Release, TCF enhanced# show software inventory
and Security versions
CLI will return the following:
Verify that the TCF file is 2.12.00 or later. Verify that the TCF file is 2.12.00 or later.
TN-000045-01-EN Page 5 of 32 12.2017

2.2 Licenses
Licenses: Ensure required license for 1+1 feature support is installed.
Note – One license is required for 1+1: Diversity Support (includes HSB, SD, and FD).
Web GUI Commands CLI Equivalent Commands
1. Log into the Web GUI of all four radios, navigate to the “Configuration -> enhanced# show license features
System -> Licensing” menu. CLI will return the following:
2. Confirm that the “Diversity Support” feature is check marked (licensed). enhanced# show license feature
Verify that the required license (Diversity

3. ACM license is also recommended if using modulations above 256QAM Support) is shown in the “Is Licensed”
or in applications where high availability is required. column as “Yes”.
4. If the Diversity Support feature is not licensed, enter or copy/paste the

“Diversity Support” license key (alphanumeric string) into the “key” field
and click “Upgrade”.
enhanced# configure
Contact your DragonWave-X Sales prime to purchase the required
(config)# license upgrade key [Diversity Support
license if you have not already received the required license. key-string]
5. A system reset is required after the license keys are initially installed to
make the features active.
enhanced# reset system
TN-000045-01-EN Page 6 of 32 12.2017

3 1+1 Configuration (Redundancy Config)

With the exception of software/license key upgrades and system type and system identifier configurations,
all other configuration changes are dynamic. Note: A “save” is still required after dynamic configuration
changes to ensure that settings are maintained after a system reset.
3.1 System Type Configuration

The system type configuration will determine whether the radio will operate in 1+0, 1+1, 2+0 or XPIC mode.
While a majority of the radio settings can be dynamically changed, any change to the system type
configuration will require a “save” and “reset system” before the changes will take effect.
Note: The “System Type” and the “System Identifier” (next step) settings both require a reset system to
become active. It is recommended that these both be configured, followed by a single “reset system”,
to avoid unnecessary reboots.
System Type Configuration: Selecting 1+1 1CR HSB mode

Note – Changing the “system type” will require a save and reset
Web GUI Configuration CLI Equivalent Commands
1. Login to all four radios and navigate to the “Configuration -> System -> General”
tab. enhanced# config
(config)# system type ?
2. Under System Type, select “1+1 1CR HSB”.
<0> 1+0 1CR
<4> 2+0 1CR
<5> 2+0 1CR XPIC
<6> 1+1 1CR HSB
(config)# system type <#>

(config)# end
Example:
enhanced# configure
(config)# system type 6
(config)# end
3. Click the “Submit” button (which will turn grey when the changes have been
applied) then proceed to the next step to set the “System Identifier”.
Note: The system type “1+1 1CR HSB” should turn red to indicate that it has been configured
but will not be applied until the system is reset.
4. Proceed to next step to configure the System Identifier.
TN-000045-01-EN Page 7 of 32 12.2017

3.2 System Identifier Configuration

In a 1+1 HSB configuration, the System Identifier has no bearing on performance except in rare cases of
synchronous acquisition where the Primary will be allocated “active” status.
For the purposes of consistency, it is recommended that the radios mounted on the “Primary” side of the
PSRM be configured as “Primary”, and their partner radio mounted on the “Secondary” side be configured
as “Secondary”. Most PSRMs introduce extra attenuation on the Secondary side (~1dB Primary, ~4-6dB
Secondary), so keeping the configuration and mounting practices consistent will allow the expected RSL to
be calculated more easily/accurately.
Note: The “System Type” (previous step) and the “System Identifier” settings both require a reset system to
become active. It is recommended that these both be configured, followed by a single “save” and
“reset system”, to avoid unnecessary reboots.
System Identifier Configuration: Designating Primary/Secondary radio

Note – Changing the “system identifier” will require a save and reset
1. Login to the radios that will be mounted on the “Primary” side
of the PSRMs and navigate to the “Configuration -> System -> enhanced# show redundancy config
Redundancy” tab. Local:
2. Under System Identifier, select “Primary”.
System identifier :primary
Radio link priority :main
Switch mode :auto
Standby interface mode :off
Revertive radio switching :enable
Hardware protection mode :mode_2
Interface group :gi0/1
Radio monitor parameters :50 50
Radio switch parameters :90 900 90 600
enhanced# config
(config)# redundancy system identifier [primary | secondary]
(config)# end
enhanced# save running-config

Enter “y” when prompted to confirm the reset
3. Click the “Submit” button (which will turn grey when the
changes have been applied) then proceed to the next step to set
Example:
the “System Identifier”.
enhanced# configure
(config)# redundancy system identifier primary
Note: The system identifier “primary” should turn red to indicate that it
** Requires ‘save running-config’ and ‘reset system’ for this
has been configured but will not be applied until the system is
change to take effect.
reset.
(config)# end
4. Click the “Save” button in the upper left corner of the Web GUI. enhanced# save running-config
Once the changes have been saved, select “Reset System” enhanced# reset system
button and Click “yes” to complete the reset.
TN-000045-01-EN Page 8 of 32 12.2017

5. Login to the radios that will be mounted on “Secondary” side of

the PSRMs and repeat the above steps, this time selecting
“Secondary”.
3.3 Switch Mode Configuration

This parameter configures how the system determines which radio will be actively processing ethernet data
(no effect on wireless).
Note: The system uses different criteria to independently determine which radio will be the active “wireless”
radio and which will be the active “ethernet” radio, so these two functions will often be separated
between the two radios depending on current and historical fault conditions.
Options include:
• Auto (recommended): Node can switch between active and standby state based on partner fault
conditions
• Force-active: The node always processes the user data (ethernet payload) and will NOT change for
any reason.
• Force-standby: The node does NOT process user data (ethernet ports will be in standby mode) and
will not change for any reason.
Switch Mode Configuration: Determine how the “active” ethernet port is controlled
1. Once the radios have been reset following the previous
two configuration steps (System Type and System
Identifier), log back into the units and navigate to the
“Configuration -> System -> Redundancy” tab. enhanced# config
(config)# redundancy switch mode [auto | force-active | force-standby]
2. Under Switch Mode, select “Auto”.
(config)# end
Example:
enhanced# configure
(config)# redundancy switch mode auto
(config)# end
Note: During normal operation, it is recommended

that all units be configured with switch mode
“auto”. The other switch modes of “force-
active” and “force-standby” should only be used
TN-000045-01-EN Page 9 of 32 12.2017

for maintenance or testing purposes as

necessary.
3.4 Standby Interface Mode Configuration

This parameter determines the link state of the interface group ethernet ports on the standby radio.
Options include “On”, “Off”, or “Pulse”.
Depending on the connected 3rd party device, it may be preferable that only the member port(s) of the
active unit be on at any given time (standby interface mode “off”) thus aiding the connected switch in
determining traffic direction and reducing the need for advanced switch port configuration.
Options include:
• On: the payload Ethernet Link will remain "on" when the node transitions from active to standby
state.
• Off: the payload Ethernet Link will turn "off" when the node transitions from active to standby
state, and will remain "off" in the standby state.
• Pulse: the payload Ethernet link will be momentarily shutdown (turned off for ~6 seconds) when
the node changes its state from active to standby. After 6 seconds the node will re-establish the
connection on its Payload port while it has changed its state to standby.
Switch Mode Configuration: Determine the port status of the “standby” ethernet interface.
1. Navigate to the “Configuration -> System -> Redundancy” tab.
2. Under Standby Interface Mode, select “On”, “Off” or “Pulse” as enhanced# config
desired. (config)# redundancy standby interface mode [on | off | pulse]
(config)# end
Example: (Used when attached Switch or Equip needs to have

the ethernet port always stay on, and uses
connectivity or ring protocols to recognize an activity
switch)
enhanced# configure
(config)# redundancy standby interface mode on
(config)# end
Example: (Used when attached Switch or Equip needs to see

the ethernet link go off and stay off to recognize
an activity switch)
enhanced# configure
(config)# redundancy standby interface mode off
(config)# end
Example: (Used when attached Switch or Equip needs a pulse

transition to recognize an activity switch)
TN-000045-01-EN Page 10 of 32 12.2017

Note: All units should be configured the same. Read the mode enhanced# configure
descriptions above to determine which choice is the optimal (config)# redundancy standby interface mode pulse
choice for your network architecture. (config)# end
3.5 Revertive Radio Switching and Radio Link Priority Configuration

When Revertive radio switching is enabled, the Radio Link Priority must be configured with a “Main” and a
“Protection” radio on each side. For consistency, it is recommended to set the Primary radios to “Main”
and the Secondary radios to “Protection”.
When this feature is enabled, the system will always use the “Main” radio to form the radio link, provided
there is no radio fault, the “Protection” radio will remain in standby mode unless a radio fault is detected on
the “main” radio.
When disabled, the “radio link priority” setting is ignored and the system will use either of the available
radios to form the link.
Note: In 2+0 and XPIC configurations, Revertive Radio Switching and Radio Link Priority settings are NOT used
and will be ignored. In a 1+1 HSB 2-wire configuration, either radio can handle the payload data. This is
determined independently of the radio link, and is NOT controlled by the Revertive radio switching.
Switch Mode Configuration: Determines Revertive Radio Switching behavior.

1. Navigate to the “Configuration -> System -> Redundancy”
(config)# redundancy revertive radio switching [enable | disable]
2. Under Revertive Radio Switching, select “enable”. (config)# redundancy radio link priority [main | protection]
(config)# end
3. Under Radio Link Priority:
• Select “main” if the System Identifier is “primary”
• Select “protection” if the System Identifier is
“secondary”.
Example:
enhanced# configure
(config)# redundancy revertive radio switching enable
(config)# redundancy radio link priority main
(config)# end
TN-000045-01-EN Page 11 of 32 12.2017

3.6 Interface Group Configuration

This parameter designates the port(s) that will carry user data. These ports will be protected by the
redundancy configurations and affected by the “standby interface mode” setting.
When multiple ports are selected (required for >1Gbps), a protection switch will only occur if a failure
condition is detected on ALL ports in the group.
• This will result in the ethernet data processing switching to the partner radio.
• The radio processing the wireless traffic (RF link) are not affected unless a failure condition is also
detected on a wireless link.
• OOB management ports should not be selected as a member of the interface group since OOB
management ports cannot pass payload traffic over the radio link.
Interface Group Configuration: Designates the protected payload data port(s)

1. Navigate to the “Configuration -> System -> Redundancy”
(config)# redundancy interface group [gi0/1] [gi0/2] [gi0/3] [gi0/4]
2. Under Interface Group, select all the ports that will be
(config)# end
carrying payload data.
Example: (single port per Interface Group)
enhanced# config
(config)# redundancy interface group gi0/1
(config)# end
Example: (multiple ports per Interface Group)
enhanced# config
(config)# redundancy interface group gi0/1 gi0/2
(config)# end
TN-000045-01-EN Page 12 of 32 12.2017

4 Basic RF Configuration
Minimum RF configuration requirements - prior to alignment
4.1 RF Profile Configuration

Radio Profile Configuration:
Define radio band, channel size, modulation, channel frequencies, and transmit power
1. Under the “Quick Configuration” menu, enter the radio profile
configuration as per link design documentation and click the “submit”
button at the bottom of the page to apply the configurations.
NOTE: RF configuration changes are applied dynamically and do not
require a reset.
Example:
enhanced# configure
(config)# radio profile ansi 50 en50_66_qpsk
(config)# radio acm tx-profile en50_66_qpsk

en50_454_2048qam
(config)# radio acm enable
2. Once the radio profile has been submitted, enter both transmit & receive
frequencies (as per link design documentation). Click “submit” to apply
changes. The “Radio Frequency” section is located directly below the Ensure that for 1+1 configurations, the Tx
“Radio Profile” configuration section. Ensure that the Tx Frequencies and Frequencies and Rx Frequencies are the same on
Rx Frequencies are exactly the same on both the Primary and Secondary the Primary and Secondary Links.
Links. See example below:
Primary Link Configuration: (TxLow)

(config)# radio frequency [Tx freq KHz] [Rx freq KHz]
Example:
Primary Link (TxLow)
(config)# radio frequency 21500000 22750000
Primary Link (TxHigh)
Secondary Link Configuration: (TxLow)
Secondary Link (TxLow)
Secondary Link (TxHigh)
TN-000045-01-EN Page 13 of 32 12.2017

Radio Profile Configuration:

Define radio band, channel size, modulation, channel frequencies, and transmit power
NOTE: In a 1+1 configuration, the same frequency pair will be used on all
radios but swapped at each end. Since only one link will be actively
transmitting at a time.
3. Navigate to the “Transmitter Settings” page, enable the transmitter and (config)# radio transmit state enable
(config)# radio transmit power [dB]
enter the transmit power (as per link design documentation). Click
“submit” to apply changes.
Example:
enhanced# configure
(config)# radio transmit state enable
(config)# radio transmit power 1.0
4. Once the transmitter has been enabled, save the configuration by selecting
the “Save” button in the upper left hand corner of the Web GUI. Click
“yes” in the subsequent pop-up window. The save will take approx. 10
seconds to complete. All RF configuration changes are dynamic so no reset
is required.
(config)# end
TN-000045-01-EN Page 14 of 32 12.2017

4.2 Management Configuration

Management Port Assignment and Type: Defining the Management Interface/Ports, VLAN & Type
NOTE: The Harmony Enhanced will arrive with the following factory default
management settings:
Port 1: Inband Management – Untagged (no management VLAN assigned)
Port 4: Out-of-band Management – Untagged (no management VLAN assigned)
1. The management type (inband/OOB), port assignment and VLAN can be

configured by navigating to the “Quick Configuration” menu. Under the
“Management Configuration” tab, select the management type (inband/out-
of-band) and management VLAN/priority as desired. Click the “submit” to
apply.
Note that all management configuration changes will be applied immediately

and management access may be dropped depending on the changes
applied.
2. In the example below, port 4 will remain as an out-of-band management port

with no VLAN tagging (it will act as a “tech port” to allow direct access for a
technician on site without interrupting traffic), and port 1 will be an inband
management port with a management vlan of 200. Once submitted, only
switches/routers/laptops tagged with VLAN 200 will be able to access port 1.
This inband management port will be protected by the redundancy Interface
Group setting,
Example:
enhanced# config
(config)# management interface vlan-id 200 gi0/1

inband vlan-tag gi0/2 none no-vlan-tag gi0/3 none
no-vlan-tag gi0/4 out-of-band no-vlan-tag
In this example, ports 2 & 3 (fiber SFP) are unused so

the management type can be set to “none” and “no-
vlan-tag”. By default, port 4 is set as an out-of-band
management port. Unless required as an additional
data port, it can be left as an out-of-band mgmt.
maintenance port.
(config)# management vlan-priority 7
IMPORTANT: Any port assigned as an out-of-band management port will not pass traffic.
TN-000045-01-EN Page 15 of 32 12.2017

Management IP Assignment: Defining the Management IP, Subnet Mask & Gateway
NOTE: The Harmony Enhanced will arrive with the following
Factory default management settings:
IP address: 192.168.10.100
Netmask: 255.255.0.0
Gateway: 192.168.10.1
1. Navigate to the “IPv4 Configuration” tab and enter the

IP, subnet mask and default gateway as desired. In the
example below, the IP address is changed to
192.168.10.200. Once the desired IP has been entered,
Click the submit button to apply the changes.
NOTE: All management configuration changes are

dynamic and will be applied immediately. Web
GUI and CLI sessions will be dropped immediately
once the IP address changes have been applied.
Example:
enhanced# configure
(config)# management ip 192.168.10.200 netmask 255.255.0.0 gateway
192.168.10.1
Once the IP assignment has been submitted, a new

Web GUI or CLI session can be opened with the new
address. Ensure that static IP of the connecting device
(laptop) is within the new IP range & subnet mask.
NOTE: Once the basic configuration has been completed, proceed with the link
alignment procedure and link verification as outlined in the “Installation
MOP”.
TN-000045-01-EN Page 16 of 32 12.2017

5 Post-Alignment Configuration
5.1 Reserved Management VLAN ID
The Enhanced ODU has a default reserved Management VLAN used to communicate between the two ODUs on
a link to support the WEB GUI Link View display, ACM, ATPC, and Redundancy communications. The default
Reserved Management VLAN ID is 4091.
If the default Reserved Management VLAN ID (eg. 4091) corresponds to the same VLAN ID required for use
by the end customer or service provider to transfer customer payload traffic, or customer/service provider non-
ODU management traffic over the deployed Enhanced ODUs, then the admin user can reconfigure the radios
to use a new different reserved VLAN ID between 2 and 4094 using CLI commands.
Note: Whatever alternative Reserved Management VLAN ID is selected, it is essential to ensure both
ends of the link are reconfigured to match the new Reserved Management VLAN ID, and that
the change is saved and committed to both banks on the ODUs at each end of the link.
The Reserved Management VLAN ID can be viewed, and configured only using the Enhanced Command Line
Interface (CLI) using the following steps:
How to View and Configure the Reserved Management VLAN ID

Note: In OMNI 3.1.0, viewing and configuring the Reserved To display current configured Reserved Management VLAN
Management VLAN is NOT supported via the Web GUI, for the Enhanced Radio use the following CLI commands:
it is ONLY supported through Enhanced CLI Commands.
A CLI session can be initiated from the Web GUI by clicking on enhanced# show system reserved vlan
the WebCLI link for the selected ODU on the Link View
Example:
graphics window as shown below: enhanced# show system reserved vlan
Reserved Vlans User Config Running Config
--------------------- ---------------- ---------------------
Res-vlan1 4091 4091
enhanced#
Note: In Release 3.1.0 OMNI software release the

default Reserved Management VLAN is
This will then open a CLI window that can be used to access VLAN ID 4091.
the Enhanced ODU CLI as shown below:
TN-000045-01-EN Page 17 of 32 12.2017

How to View and Configure the Reserved Management VLAN ID

Alternatively, a CLI session can be accessed by a Telnet session, or
using applications like Putty to open SSH sessions.
CLI Commands to Configure the Reserved Management VLAN ID

1. The user can modify or change the Reserved Management VLAN using the following CLI command:
enhanced# configure
(config)# system reserved vlan update <vlan (2-4094)>
Note: By default, the Reserved Management VLAN = 4091. This value is configurable for any VLAN ID between 2 and 4094.
Recommendation: Always change the remote ODU first because after the change you may lose management access to the remote
ODUs until you change the Reserved Management VLAN on the local ODU.
Example:
enhanced# configure
(config)# system reserved vlan update 4093
% Requires ‘save running-config’ and ‘reset system’ for this change to take effect.
(config)# end
If you pick an invalid VLAN ID the following error message will appear.
Example:
(config)# system reserved vlan update 4096

% Invalid parameter. The maximum value is 4094.
(config)#
2. If the Reserved Management VLAN is changed from default, make sure the change to the new selected reserved VLAN is made
on all ODUs in the system. In 1+1 HSB, 2+0, or 2+0 XPIC systems make the configuration changes starting with the Remote
Secondary ODU, Local Secondary ODU, then the Remote Primary ODU, and lastly the Local Primary ODU.
Warning: IF only one ODU has the Reserved Management VLAN changed, ACM, and ATPC will stop working until the other peer
ODU has its Reserved Management VLAN changed to match Reserved Management VLAN on the other “Enhanced
ODU”.
Warning: IF only one ODU has the Reserved Management VLAN changed, Link View will stop displaying the remote ODU(s) until
the other peer ODU(s) have the Reserved Management VLAN changed to match Reserved Management VLAN on the
first ODU(s).
TN-000045-01-EN Page 18 of 32 12.2017

5.2 Payload VLAN Configuration

The Harmony Enhanced has a built in 4-port switch. For this reason, the VLAN IDs for tagged payload traffic
must be added to the allowed list on all of the ports in the Interface Group and their corresponding modem
“data ports”. In a 1+1 configuration, all radios must have the VLANs allowed on the Interface Group member
port(s) and the corresponding modem interface port(s).
Payload VLAN Configuration: Define the range of VLANs that can pass on a given Ethernet port
1. Under the “Configuration -> Packet Switch -> VLAN” tabs, either enter
the specific VLAN or select the “bulk” VLAN box and enter the desired To view the current VLAN config:
VLAN range (eg, VLAN 2-4094). enhanced# show switch vlan
NOTE: If it is required, VLANs 4092-4094 can be added separately with

“bulk” mode deselected. Alternatively VLANs 2-4094 can be To configure a single VLAN on single port:
added in bulk mode.
enhanced# configure
(config)# switch
2. Select the ports to apply this VLAN or VLAN range to. In this example,
(config-switch)# vlan [vid]
port 1 has been selected as the port for payload traffic. Ensure that the (config-switch-vlan)# port add gigabitethernet [x]
VLAN range is applied to port 1 (gi 0/1) and the associated modem port (config)# end
(gi 0/5).
3. Select the “Add/Modify” button and then Click “Submit” Example: (single VLAN on multiple GigE ports)
enhanced# configure
(config)# switch
(config-switch)# vlan 200
(config-switch-vlan)# port add gigabitethernet 0/1
gigabitethernet 0/5
(config-switch-vlan)# end
(config)# end
To configure a VLAN range on g0/1 and g0/5:
enhanced# config
Note : Adding the full VLAN range to a port can take upwards of several (config)# switch
minutes to complete. It is recommended to keep the VLAN range as (config-switch)# vlan range vlan [vid] – [vid]
small as conveniently possible to reduce reboot times. (config-switch-vlan-range)# port add gigabitethernet
[0/x]
Example: (VLAN range on multiple GigE ports)
enhanced# config
(config)# switch
(config-switch)# vlan range vlan 2 - 4090
(config-switch-vlan-range)# port add gigabitethernet 0/1
gigabitethernet 0/5
(config-switch-vlan-range)# end
(config)# end
TN-000045-01-EN Page 19 of 32 12.2017

If a management VLAN has been configured on the same port that If the Reserved management VLAN ID is 4091 and the
the VLANs are being been applied and it falls under the desired bulk previous VLAN range command is executed the
following CLI message will be displayed:
VLAN range, the following error message will be displayed.
Example:
In this example, if port 1 had been configured with a management
VLAN of 200, the following message would occur. enhanced# config
(config)# switch
(config-switch)# vlan range vlan 2 - 4094
%Configuration prohibited for Vlan4091
A similar message would be displayed if the range

overlaps the Reserved Management VLAN ID regardless
of the VLAN ID configured for management over the link.
Note: This is simply a warning to inform the user of the conflict, but
it will not effect the creation of the remaining vlans. In this
example, VLAN’s 2-199 and 201-4090 will be successfully
added.
TN-000045-01-EN Page 20 of 32 12.2017

6 Verifying the 1+1 Link is Operational
To verify the 1+1 configuration is correct requires a few checks either via Web GUI or CLI including:
1) Verification that the local primary and secondary radio can communicate via the ODU-ODU
interconnect cable.
2) Verification that the remote primary and secondary radio can communicate via the ODU-ODU
interconnect cable.
3) Verification that the primary link is operational and running error-free
4) Verification that the secondary link is operational and running error-free (separately).
5) Verification that the RSL, and SNR values are optimal.
6.1 Verifying Primary to Secondary Radio Communication
Verification of primary to secondary communication would need to be done first at the local end, and then at the
remote end. If the link is already up and LinkView is up then verification can be done for both ends easily.
If the link is not yet up, then access to the remote radios is required possibly via a second person at the remote
end of the link.
Local Primary to Secondary Radio Communication Verification: Verify that the local primary and secondary
radios can communicate via the ODU-ODU cable.
Web GUI Verification of Primary to Secondary Communication CLI Equivalent Commands
1. Under the Link View “Graphic” or “Both” display window verify that the To verify that the Primary to Secondary Communication
ODU-to-ODU cable or line connecting the primary and secondary local radios is working in CLI, use the “show redundancy status”
is shown as “green” (see example below). command to successfully show the partner status.
If partner status is shown the connection between the

primary and secondary radios is working.
Example:
enhanced# show redundancy status
Local:
System Identifier :primary
System Status :active
Radio Status :up
Interface cross Link Status : not active
Interface group status : gi0/1->up
Partner:
System Identifier :secondary
System Status :standby
Radio Status :up
Interface cross Link Status : active
Interface group status : gi0->down
To verify that the Primary to Secondary Communication

is NOT working in CLI, use the “show redundancy
status” command for error message display.
TN-000045-01-EN Page 21 of 32 12.2017

Local Primary to Secondary Radio Communication Verification: Verify that the local primary and secondary
radios can communicate via the ODU-ODU cable.
Web GUI Verification of Primary to Secondary Communication CLI Equivalent Commands
2. If the cable between the ODUs is NOT connected or faulty, the ODU-to-ODU
link on the ODU will show up as “red” in the Link View – Graphic or Both If the radio fails to retrieve its partner status the
views as shown in the example below. connection between the primary and secondary radios
is not working. The ODU-to-ODU cable may be
disconnected or faulty.
Example:
enhanced# show redundancy status
Local:
System Identifier :primary
Radio Status :up
Interface group status : gi0/1->down
Partner:
Failure to retrieve partner redundancy status. Please
check your partner connection.
Peer:
System Identifier :invalid
Radio Status :down
Interface group status :
3. The ODU-ODU Connection Status can also be determined using the Web GUI To verify that the Primary to Secondary Communication
using the “List Active Alarms” display window, if the following alarms are is not working in CLI, use the “show system alarms”
listed then the ODU-to-ODU cable or line connecting the primary and command to show “Redundancy partner
communication lost” alarm.
secondary local radios is not properly connected (see example below).
Example:
enhanced# show system alarms
Id Severity Component Alarm

__ _______ __________ ______________________
31 Major Redundancy Redundancy reduced radio

link
38 Major Redundancy Redundancy partner
communication lost
TN-000045-01-EN Page 22 of 32 12.2017

6.2 Verifying 1+1 Radio Link is Operational
Once the local and remote ODU-ODU cable connectivity has been verified then verification of 1+1 radio link will
need to be verified as operational. If the 1+1 link is already up and LinkView is up then verification can be done
for both ends easily.
Revertive Radio Switching – Enabled

When revertive Radio Switching is enabled, the wireless link should be up between the Primary radios (the “active”
ethernet port could be on either the Primary or Secondary).
Once this has been verified, the TX can be muted on the Primary radios in order to verify that the Secondary
radios are also operational. After Secondary verification, unmute the Primary TX and the wireless link should
return to the Primary radios.
1+1 Link Verification – Revertive enabled: Verify that the primary and secondary links are up and
operational.
Web GUI Verification of 1+1 Links
1. Under the Link View “Graphic” or “Both” display window verify that the ODU-to-ODU cables or line connecting the primary
and secondary local radios is shown as “green” (see example below).
2. The status of the link can be verified as double rows of green arrows present between the active wireless radios when the
1+1 link is up and operational as shown in the screen capture below. When revertive mode is enabled and all transmitters
are on, the active wireless link should be displayed between the two Primary radios as shown below:
TN-000045-01-EN Page 23 of 32 12.2017

operational.
The RSL values on the Primary radios should also be close to each other (typically within a 1-3 dBm) and consistent with the engineered link
design. The RSL of the Secondary radios will be 4-6dBm lower due to the added attenuation on the secondary side of the PSRM.
The SNR values should be as high as the link will support.
Link
RSL & SNR Status
3. Verify that no Rx Bad Frames are being displayed for ether of the active wireless radios (Primary-A and Primary-Z). The
radios that are currently carrying the ethernet traffic will display the Radio Port Statistics for both the Local and the
Partner radio.
Example: Primary-A: wireless link active, ethernet

standby.
TN-000045-01-EN Page 24 of 32 12.2017

operational.
4. Verify operational status of Secondary radios.
a. Disable the TX of the Primary-A (172.16.35.81 in this example) and ensure wireless link successfully switches
to the Secondary-A radio. This will likely result in an “HSB crosslink” between Secondary-A and Primary-Z.
TN-000045-01-EN Page 25 of 32 12.2017

operational.
b. Disable the TX of the Primary-Z radio (172.16.35.91 in this example), and ensure wireless link successfully
switches to the Secondary-Z radio. This should result in a link between Secondary-A and Secondary-Z.
TN-000045-01-EN Page 26 of 32 12.2017

operational.
c. Unmute the transmitters on both Primary radios. Verify that the link reverts back to the Primary radios.
TN-000045-01-EN Page 27 of 32 12.2017

1+1 Link Verification – Revertive disabled: Verify that the primary and secondary links are up and
operational.
1. Under the Link View “Graphic” or “Both” display window verify that the ODU-to-ODU cables or line connecting the
primary and secondary local radios is shown as “green” (see example below).
2. The status of the link can be verified as double rows of green arrows present between the active wireless radios when the
1+1 link is up and operational as shown in the screen capture below. When revertive mode is disabled and all transmitters
are on, the active wireless link could be between either of radios on the Local End (Primary-A or Secondary-A) and either of
the radios on Remote End (Primary-Z or Secondary-Z) depending on several acquisition timing factors.
Note: When revertive mode is disabled, “Main” and “Protection” will not appear above each radio in the Graphic View.
The RSL values on the Primary radios should also be close to each other (typically within a 1-3 dBm) and consistent with the
engineered link design.
The RSL of the Secondary radios will be 4-6dBm lower due to the added attenuation on the secondary side of the PSRM.
TN-000045-01-EN Page 28 of 32 12.2017

1+1 Link Verification – Revertive disabled: Verify that the primary and secondary links are up and
operational.
3. Verify that no Rx Bad Frames are being displayed for ether of the active wireless radios (Primary-A and Primary-Z). The
radios that are currently carrying the ethernet traffic will display the Radio Port Statistics for both the Local and the
Partner radio.
Example: Primary-A: wireless link active, ethernet

standby.
Example: Secondary-A: wireless link standby, ethernet

active inactive.
4. Verify operational status of all radios.

a. Disable the TX of the Primary-A and Primary-Z radios. This should result in a link between Secondary-A and
Secondary-Z.
b. Re-enable the TX of both Primary radios. The link should remain on the Secondary radios (revertive mode
disabled).
c. Disable the TX of the Secondary-A and Secondary-Z radios. This should result in a link between Primary-A and
Primary-Z.
d. Re-enable the TX of both Secondary radios. The link should remain on the Primary radios (revertive mode
disabled).
TN-000045-01-EN Page 29 of 32 12.2017

1+1 Link Verification – Revertive Disabled:

Verify that the primary and secondary links are up and operational.
CLI Verification of 1+1 Link
1. The “show radio status” command can be executed to see the status of the radio and corresponding link. Repeat
for each of the 4 radios
2. Alternatively “show system health” command can be executed to see the status of the radio and corresponding
link. Repeat for each of the 4 radios.
Example:
Primary-A (active wireless, standby ethernet) Secondary-A (standby wireless, active ethernet)
enhanced# show radio status enhanced# show radio status
Radio Instance : ch1 Radio Instance : ch1

-------------------------------------------- --------------------------------------
Equalizer Stress : 78 Equalizer Stress : 164

SNR : 43.3 dB SNR : 5.6 dB
Receiver RSL : -32.1 dBm Receiver RSL : -36.8 dBm
Actual Tx Profile : en56_500_2048qam Actual Tx Profile : en56_73_qpsk

Radio Operational State : up Radio Operational State : up
Transmitter State : Enabled Transmitter State : Disabled (redundancy)

Transmit Power : 2.0 dBm Transmit Power : 2.0 dBm
Radio Link State : up Radio Link State : down
XPIC Status : NA XPIC Status : NA

XPI : NA XPI : NA
enhanced# show system health enhanced# show system health
Radio Instance : ch1 Radio Instance : ch1

------------------------------ -------- ------------------------------------------
Radio Operational State : up Radio Operational State : up

Radio Link State : up Radio Link State : down
The RSL values should also be close to each other (typically within a 1-3 dBm) and consistent with the engineered link design,
and SNR values should be as high as the link will support.
TN-000045-01-EN Page 30 of 32 12.2017

1+1 Link Verification – Revertive Disabled:

Verify that the primary and secondary links are up and operational.
CLI Verification of 1+1 Link
3. Redundancy status can be determined by executing the “show redundancy status” CLI command:
“Partner” is the co-located local radio to the radio you are logged into.
“Peer” is the remote radio corresponding to the radio you are logged into. Only visible when “active ethernet” radio
(radio processing the ethernet traffic).
Example:
Primary-A (active wireless, standby ethernet) Secondary-A (standby wireless, active ethernet)
enhanced# show redundancy status enhanced# show redundancy status
Local: Local:
System identifier :primary System identifier :secondary

System status :standby System status :active
Radio status :up Radio status :down
Interface cross link status :not active Interface cross link status :not active
Interface group status :gi0/1->down Interface group status :gi0/1->up
Partner: Partner:
System identifier :secondary System identifier :primary

System status :active System status :standby
Radio status :down Radio status :up
Interface cross link status :not active Interface cross link status :not active
Interface group status :gi0/1->up Interface group status :gi0/1->down
Peer:
System identifier :secondary

System status :active
Radio status :down
Interface cross link status :not active
Interface group status :gi0/1->up
TN-000045-01-EN Page 31 of 32 12.2017

7 Firmware Commit
The Enhanced consists of two firmware banks, active and backup.
These memory banks are designed to contain the system firmware and configuration. The current running
configuration will only save to the active bank when selecting “save” from the top left corner of the Web GUI or
issuing the “save running-config” command via CLI.
To copy the contents of the active bank to the backup bank, the “firmware commit” command must be issued via
CLI. This will copy the configuration stored in the active bank to the backup bank, making both banks equal.
NOTE: It is very important to ensure the “firmware commit” command is issued after making changes to
the active bank configuration, and saving those changes. Failure to do a commit operation which
copies the active configuration to the backup configuration, may result in an undesired running
configuration if the backup bank becomes the active bank.
Firmware Commit
The commit operation will copy the active OMNI and saved configuration to the backup bank. Click on
the “Firmware Commit” in the import SW window to copy the active configuration to the inactive enhanced# firmware commit
flash memory bank.
The commit operation will copy the
Repeat for each of the 4 radios in the 1+1 link. active OMNI and saved configuration
to the backup bank. You will not be
able to switch back to the previous
OMNI.
Would you like to save the running
config and commit? [y/n]: y
Validating OMNI in active bank...

Copying OMNI from active bank to
backup bank...
Validating OMNI in backup bank...
TN-000045-01-EN Page 32 of 32 12.2017


Harmony Enhanced, 1 Plus 1 Configuration Method of Procedure - TN-000045-01-En-01-01

Uploaded by

Document Information

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

Harmony Enhanced, 1 Plus 1 Configuration Method of Procedure - TN-000045-01-En-01-01

Uploaded by

Copyright:

Available Formats

Technical Note

Harmony Enhanced 1+1 Configuration

TN-000045-01-EN Page 2 of 32 12.2017

3 1+1 CONFIGURATION (REDUNDANCY CONFIG).......................................... 7

4 BASIC RF CONFIGURATION ........................................................................ 13

5 POST-ALIGNMENT CONFIGURATION ......................................................... 17

6 VERIFYING THE 1+1 LINK IS OPERATIONAL ............................................. 21

7 FIRMWARE COMMIT ..................................................................................... 32

TN-000045-01-EN Page 3 of 32 12.2017

Revision Update Date Updates Reason

1.0 07/05/2017 Initial Version Document Created.

TN-000045-01-EN Page 4 of 32 12.2017

2.1 Software Confirmation

Software Confirmation: Validate OMNI and TCF software

TN-000045-01-EN Page 5 of 32 12.2017

Verify that the required license (Diversity

4. If the Diversity Support feature is not licensed, enter or copy/paste the

enhanced# reset system

TN-000045-01-EN Page 6 of 32 12.2017

3 1+1 Configuration (Redundancy Config)

3.1 System Type Configuration

System Type Configuration: Selecting 1+1 1CR HSB mode

(config)# system type <#>

4. Proceed to next step to configure the System Identifier.

TN-000045-01-EN Page 7 of 32 12.2017

3.2 System Identifier Configuration

System Identifier Configuration: Designating Primary/Secondary radio

enhanced# save running-config

TN-000045-01-EN Page 8 of 32 12.2017

5. Login to the radios that will be mounted on “Secondary” side of

3.3 Switch Mode Configuration

Note: During normal operation, it is recommended

TN-000045-01-EN Page 9 of 32 12.2017

for maintenance or testing purposes as

3.4 Standby Interface Mode Configuration

Example: (Used when attached Switch or Equip needs to have

Example: (Used when attached Switch or Equip needs to see

Example: (Used when attached Switch or Equip needs a pulse

TN-000045-01-EN Page 10 of 32 12.2017

3.5 Revertive Radio Switching and Radio Link Priority Configuration

Switch Mode Configuration: Determines Revertive Radio Switching behavior.

TN-000045-01-EN Page 11 of 32 12.2017

3.6 Interface Group Configuration

Interface Group Configuration: Designates the protected payload data port(s)

Example: (single port per Interface Group)

Example: (multiple ports per Interface Group)

TN-000045-01-EN Page 12 of 32 12.2017

4.1 RF Profile Configuration

(config)# radio profile ansi 50 en50_66_qpsk

(config)# radio acm tx-profile en50_66_qpsk

Primary Link Configuration: (TxLow)

TN-000045-01-EN Page 13 of 32 12.2017

Radio Profile Configuration:

TN-000045-01-EN Page 14 of 32 12.2017

4.2 Management Configuration

1. The management type (inband/OOB), port assignment and VLAN can be

Note that all management configuration changes will be applied immediately

2. In the example below, port 4 will remain as an out-of-band management port

(config)# management interface vlan-id 200 gi0/1

In this example, ports 2 & 3 (fiber SFP) are unused so

(config)# management vlan-priority 7

TN-000045-01-EN Page 15 of 32 12.2017

1. Navigate to the “IPv4 Configuration” tab and enter the

NOTE: All management configuration changes are